OpManager DE enables you to process the traps from the managed devices. When a trap is received from a managed device, the Probe notifies to the Central. The Central, then raises the alarm to notify the administrator. You can configure the severity and the message of the alarm generated for the traps. Some of the common traps are automatically processed by the Probe. 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 the Probe when there is a problem. You can configure more trap processors 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.	Attention
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 Event Management	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

From the Probe web client, go to Admin-> SNMP Trap Processors. All the configured processors are listed here.
On the right, select Load From Mibs under Actions. MIBs are listed.
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 on Add Trap Processor(s) button.

A Processor for the selected trap is added, and is listed under the SNMP Trap Processors.

Adding Custom Trap Processor
You can add processors for traps from any custom SNMP MIB. Probe 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 have the Probe to easily monitor the 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 custom trap processor, follow the steps given below:

Click SNMP Trap Processors under the Admin Tab.
Click Add Custom Trap Processor under Actions. Trap Processor Properties page opens.
Enter the Trap Name.
Select the SNMP Trap Version.
Select the Generic Trap Type.
Enter the Specific Trap Type value.
Enter the Distributed OID or click on Select button to open the MIB browser.
Enter the Trap Message and select the variables to be displayed when the trap is received
Select the Severity of the trap.
Select the Status of this trap processor.
Click on Add button.

The trap processor is added.

Attachments (3)

RSS of this page