2 snmp community strings, 3 sspa snmp traps – Comtech EF Data LPODnet User Manual
Page 33
LPODnet M&C Netbook Accessory
Revision 3
Ethernet-Based M&C using the LPODnet
MN-LPODNET
3–3
MIB File/Name
(where ‘x’ is
revision letter)
Description
FW-0000289x.mib
SSPA MIB file
MIB file consists of all of the OID’s for management of the SSPA functions
FW-0000290x.mib
SSPA Traps MIB file Trap MIB file is provided for SNMPv1 traps common for the SSPA.
3.4.2 SNMP Community Strings
In SNMP v1/v2c, the SNMP Community String is sent unencrypted in the SNMP
packets. The network administrator must take caution to ensure that SNMP packets
travel only over a secure and private network if security is a concern.
The SSPA 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.
Type the SNMP Community String into the user-supplied MIB Browser or Network Node
Management software.
Three Community Strings are defined for SNMP access:
• Read Community
default = public
• Write Community
default = private
• Trap Community
default = comtech
For proper SNMP operation, the SSPA MIB files must be used with the associated
version of the SSPA M&C. Please see the “SSPA FW Release Notes” for information
on the required FW/SW compatibility.
3.4.3 SSPA SNMP Traps
The SSPA has the ability to send out SNMP traps when certain events occur in the unit. The SSPA
sends out traps when a fault occurs in the unit. A trap is sent both when a fault occurs and is
cleared.
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 SSPA sends by using the SSPASNMPTrapVersion OID.
The MIB2 v1traps / v2 notifications supported by the SSPA are as follows: