Coastcom D/I Mux III System, User Manual

Page: 307 / 329

D/I Mux III User’s Manual Appendix I. Traps and Modem Dial Out Configuration
287
TRAPS
The normal communication path in an SNMP system is from the manager(s) to a specific node (the
agent). Usually the manager initiates communication by sending a request (
set, get, get-next ) and the
agent ( AMCU ) responds.
A Trap is used to indicate a change in the operating environment, such as an alarm or an event
message. Traps are unsolicited messages from the agent to the manager.
The 5 traps as defined in RFC 1157 and used in this implementation are:
1) coldStart Trap: Signifies that the agent is reinitializing itself and that some or all of the configuration
information may be changed.
2) warmStart Trap: Signifies that the agent is doing a warm boot and that the configuration information
has not changed.
3) linkDown Trap: Signifies that the agent recognizes that one of its communication links has failed.
4)
linkUp Trap: Signifies that the agent recognizes that one of its communication links is back in service.
5) authenticationFailure Trap: Signifies that the agent has the correct IP address but the community string is
not recognized.
When an SMNP manager receives a trap message, it can be displayed on a terminal screen, or into a
log file, etc. depending on how the manager site is configured. At this point the manager site can
request further information from the agent (using
get , get-next ) or, reroute traffic, or reconfigure the
agent (using set ) as is necessary to keep the network running.
MODIFY ALARMS
MA
The MA command allows the user to specify what type of alarms will be used as the criteria for
determining if a link has failed, triggering a linkDown Trap. When all of the specified alarms have
cleared a linkUp Trap will be sent.
The MA screens shown are for Channel Bank Mode. In Dual Channel Bank or Drop and Insert mode,
T1-2 would be offered as a choice.