
Chapter 11. SNMP Management
Filtering (Disabling) Traps
You can disable trap generating events in three ways:
1.Disable Trap Transmission. From the terminal menu, select SNMP and set Trap Transmission to DISABLED.
OR
2.Define trap thresholds to disable specific trap events. Refer to the ATLAS MIB in System Event Logging on page
For example, consider the coldStart trap, a system controller event. If you defined for destination 0 a trap filtering threshold of Warning for the system controller, the coldStart trap would not generate to that destination because the coldStart trap severity level is defined as Normal. (Recall that each trap event has a severity level: Disabled, Informational, Normal, Warning, Minor, Major, and Critical.)
OR
3.Control certain traps through SNMP of specific MIB variables. These variables are outlined in the remainder of this chapter.
Standard Traps
Table
|
|
| Table |
|
|
|
|
Index | Trap Name | Severity | Description |
|
|
|
|
|
|
|
|
0 | coldStart | Normal | ATLAS is such that its configuration may be |
|
|
| altered; this trap is generated on power up. |
|
|
|
|
1 | warmStart | Normal | ATLAS is reinitializing without altering its |
|
|
| configuration. |
|
|
|
|
2 | linkDown | Warning | One of the ATLAS communication links has |
|
|
| failed. |
|
|
|
|
3 | linkUp | Normal | One of the ATLAS communication links has |
|
|
| come up. |
|
|
|
|
4 | authenticationFailure | Informational | ATLAS has received a protocol message |
|
|
| that has failed authentication. |
|
|
|
|
RFC1213, or MIB II, defines the object type snmpEnabledAuthenTraps. If you set this value to 2, the generation of the authenticationFailure trap is disabled. This trap is enabled by setting snmpEnableAuthenTraps to 1. One possible rea- son for an authentication failure would be an invalid community name in the received protocol message.
ATLAS 810PLUS User Manual |