Low Power Outdoor (LPOD) Amplifier/Block Up Converter (BUC)
Revision 15
Ethernet Interface Operation
4–3
MN-LPOD
4.2.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 correct SNMP operation, the LPOD MIB files must be used with the
associated version of the LPOD M&C. See the LPOD FW Release Notes for
information on the required FW/SW compatibility.
4.2.3 SNMP Traps
The LPOD SNMP agent supports both SNMPv1 and v2c. The LPOD Traps file
needs to be compiled only if SNMPv1 traps are to be used.
The LPOD has the ability to send out SNMP traps both when a fault occurs and when a fault
clears in the unit. You may configure which style of traps the LPOD sends by using the
lpodSNMPTrapVersion
OID.
The LPOD supports the following MIB2 SNMPv1 traps and v2 notifications:
MIB2 SNMPv1 trap: Authentication Failure
5
MIB2 SNMPv2 notifications: Authentication Failure
1.3.6.1.6.3.1.1.5.5
The LPOD supports the following Faults SNMPv1 traps and v2 notifications:
Faults SNMPv1 traps:
lpodPowerSupply24V1StatusV1
62474801
lpodPowerSupply24V2StatusV1
62474802
lpodPowerSupplyLNBStatusV1
62474803
lpodPowerSupply13VStatusV1
62474804
lpodPowerSupply10VStatusV1
62474805
