![]() ![]() ![]() |
OpManager enables you to process the traps from the managed devices. When a trap is received from a managed device, OpManager notifies the administrator with an alarm. You can configure the severity and the message of the alarm generated for the traps. Some of the common traps are automatically processed in OpManager into alarms. You can see all these trap processing configuration from Admin --> SNMP Trap Processors.
The devices must be SNMP-enabled so that it can send traps to OpManager when there is a problem. You can configure more trap processors in OpManager for other type of traps.
Different Trap Types
Trap Name
|
Trap Description
|
Severity
|
LinkUp |
A communication interface has been enabled. |
Clear |
LinkDown |
A communication interface has been disabled. |
Critical |
AuthenticationFailure |
A message that cannot be authenticated has been received. |
Trouble |
EgpNeighborLoss |
An Exterior Gateway Protocol (EGP) neighbor has been lost. |
Trouble |
ColdStart |
The agent is reinitializing. The SNMP data and configuration might have changed. |
|
WarmStart |
The agent is reinitializing without any change in the SNMP data and configuration. |
Attention |
Cisco Voltage Change Status |
The voltage measured at a given testpoint is outside the normal range for the testpoint (i.e. is at the warning, critical, or shutdown stage). Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the Cisco Shutdown trap. |
Trouble |
Cisco Config Management Event |
The Cisco configuration has been changed. |
Trouble |
Cisco Temperature Change Status |
The temperature measured at a given testpoint is outside the normal range for the testpoint (i.e. is at the warning, critical, or shutdown stage). Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the Cisco Shutdown trap | Trouble |
Redundant Supply Notification |
The redundant power supply (where extant) fails. Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the Cisco Shutdown trap. |
Trouble |
Cisco Fan Status |
One of the fans in the fan array (where extant) fails. Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the Cisco Shutdown trap. |
Trouble |
Cisco Shutdown |
The environmental monitor detects a testpoint reaching a critical state and is about to initiate a shutdown. This notification contains no objects so that it may be encoded and sent in the shortest amount of time possible. Even so, management applications should not rely on receiving such a notification as it may not be sent before the shutdown completes. |
Critical |
Loading Traps from other MIBs
Following are the steps to load the traps from various MIBs.
Under the Admin tab, select SNMP Trap Processors. All the configured processors are listed here.
On the right, select Load From Mibs under Actions
From the list of MIBs, select the MIB from which you would like to load the trap variable. The traps in that MIB are listed.
Select the required trap variable, and click Add Trap Processor(s).
A Processor for the selected trap is added, and is listed under the SNMP Trap Processors.
Adding New Processors Directly
You can add processors for traps from any custom SNMP MIB. OpManager can extract useful information that is sent with SNMP traps as variable bindings (SNMP varbinds). So if you have bought devices from different vendors, all you need to do is get access to those vendor-specific MIBs and you can easily have OpManager monitor critical variables on that device.
If a managed device sends a trap that has not been defined, you can view them in the Unsolicited Traps view until a processor is configured.
To create a trap processor, follow the steps given below:
Click SNMP Trap Processors under the Admin Tab.
Click Add Custom under Actions.
Fill in the values for the text fields in this dialog.
Click Add.
The processor is added.
![]() ![]() ![]() |