SNMP Traps in Networks

Receiving SNMP Traps

Networks module receives alerts in the form of SNMP traps, from devices on the default port 162. So, it automatically acts as a Trap Receiver, and based on the trap processors defined in the Networks, the traps are processed and shown as Network alarms.

Processing SNMP Traps into Alarms

IT360 enables you to process traps from the managed network devices. When a trap is received from a managed device, IT360 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 into alarms. You can see all these trap processing configurations from 'Admin --> Networks --> SNMP Trap Processors'.

The devices must be SNMP-enabled, so that they can send traps to the IT360, when there is a problem. You can configure more Trap Processors in IT360, for other type of traps, as shown in the below table:

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.

  1. Go to 'Admin --> Networks --> SNMP Trap Processors'. All the configured processors are listed here.

  2. On the right, select 'Load From Mibs' under Actions.

  3. 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.

  4. 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. The Networks module 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 the Networks module monitor the critical variables on those devices.

If a managed network device sends a trap that has not been defined, you can view them in the Unsolicited Traps View, until a processor is configured.

Creating a Trap Processor:

To create a Trap Processor, follow the steps given below: 

  1. Go to 'Admin --> Networks --> SNMP Trap Processors'.

  2. Click 'Add Custom' under Actions.

  3. Fill in the values for the text fields in this dialog box.

  4. Click 'Add'. The processor is added.

[Top]



Copyright © 2013, ZOHO Corp. All Rights Reserved.