Comtech EF Data LPOD - Manual (Page 67)

LPOD C-, X-, or Ku-Band Outdoor Amplifier / Block Up Converter MN-LPOD
Ethernet-based Remote Product Management Revision 10
4–3
MIB File/Name (where
‘x’ is revision letter)
Description
FW-0000289x.mib
LPOD MIB file
MIB file consists of all of the OID’s for management of the LPOD functions
FW-0000290x.mib
LPOD Traps MIB file
Trap MIB file provides SNMPv1 traps common for LPOD.
4.3.2 SNMP Community Strings
In SNMP v1/v2c, the SNMP Community String is sent unencrypted in the SNMP
packets. Caution must be taken by the network administrator to ensure that SNMP
packets travel only over a secure and private network if security is a concern.
The LPOD uses Community Strings as a password scheme that provides authentication before
gaining access to the router agent’s MIBs. They are used to authenticate users and determine
access privileges to the SNMP agent. The LPOD defines three Community Strings for SNMP
access:
• Read Community default = public
• Write Community default = private
• Trap Community default = comtech
Type the SNMP Community String into the user-supplied MIB Browser or Network Node `
Management software.
For proper SNMP operation, the LPOD MIB files must be used with the associated
version of the LPOD M&C. Please refer to the LPOD FW Release Notes for information
on the required FW/SW compatibility.
4.3.3 SNMP Traps
The LPOD has the ability to send out SNMP traps both when a fault occurs and when a fault
clears in the unit. The SNMP agent supports both “SNMPv1” and “v2c”. The “Traps” file only
needs to be compiled if “SNMPv1” traps are to be used.
You may configure which style of traps the LPOD sends by using the lpodSNMPTrapVersion OID.
The LPOD supports the following MIB2 v1traps and v2 notifications:
MIB2 SNMPv1 trap: Authentication Failure 5
MIB2 SNMPv2 notifications: Authentication Failure 1.3.6.1.6.3.1.1.5.5