Configuring SNMP traps

The

component uses TRAP protocol operations to send information to your managing system. It supports the v1, v2c, and v3 versions of the SNMP protocol.

To use SNMP trap-based alerting, you must configure a server address as the recipient for all traps generated by the component. You must also define the trap dispatching settings for the component to follow when it sends alerts.

You must configure the component so that it uses the same protocol level as the recipient to send traps.

To configure dispatching of SNMP traps

1. In the

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   interface, point to Administration > Integration, and click Network management (SNMP).
2. On the Action menu for the Traps section, click Edit.
3. Select the type of SNMP compatible traps that you want the server to send: v1, v2, or v3 (secure type).
4. In the Trap manager address box, enter the IP address of the receiving server.
5. In the Trap manager port box, enter the port number that the receiving server uses.
    If you are unsure of the port number, use the default SNMP port value (162).
6. In the Trap queue size box, enter a value between 1,000 and 10,000 to specify the queue size.
    Increasing the size of the trap queue provides more buffering when the device generates a large number of alerts. The default queue size is 1,000.
7. In the Trap drain rate text box, enter a number between 1 and 1,000 to limit the number of traps sent per second.
    This mechanism protects the trap manager from being overwhelmed. Set the trap drain rate based on the capacity of the receiving host and network. The default value is 10 traps per second.
8. Click Save.

To turn on the SNMP traps

1. In the

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   interface, point to Administration > Integration, and click Network management (SNMP).
2. On the Action menu for the Traps section, click ON.
   
   The system sends traps whenever trap-enabled conditions occur. If the ON and OFF buttons are both unavailable, it means that the Security role has not enabled the use of the SNMP service for this system.