Aa.3.2 snmp community strings, Aa.3.3 snmp traps – Comtech EF Data CSAT-5060 User Manual
Page 167

CSAT-5060 C-Band Transceiver
Revision 1
Ethernet-based Remote Product Management
MN/CSAT5060.IOM
AA–3
Compile these MIB files in a user-supplied MIB Browser or SNMP Network Monitoring System
server.
AA.3.2
SNMP Community Strings
CAUTION: In SNMP v1/v2c, the SNMP Community String is sent unencrypted in the
SNMP packets. The network administrator must make sure that SNMP packets travel
only over a secure and private network, if security is a concern.
The unit 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 correct SNMP operation, make sure to use the MIB files with the correct version
of the M&C. Refer to the Firmware Release Notes for information on this required
firmware/software compatibility.
AA.3.3
SNMP Traps
The unit sends out SNMP traps both when a fault occurs and when it is cleared.
The SNMP agent supports SNMP v1 and v2c.
If SNMP v1 traps are to be used, then make sure to compile the traps file.
Use the csat-5060SNMPTrapVersion OID to configure the type of traps that the unit will send.
The unit uses these MIB2 v1 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