Table of Contents (Start)

Trap Destinations

The Trap Destination page enables you to define the destinations where you want SevOne NMS to send traps. Trap destinations can be third party applications such as your company's event console or fault management system. Each trap can be sent to multiple destinations. After you define a trap destination, you associate devices to the trap destination from the Trap Destination Associations page to have devices send traps to the destinations you define here.

To access the Trap Destination page from the navigation bar, click the Events menu, select Configuration, and then select Trap Destinations.

Manage Trap Destinations

The Trap Destinations pop-up enables you to manage trap destinations.

Click and select Add New Destination or select the check box for a trap destination, click , and then select Edit Selected to display the Trap Destination Settings pop-up.
In the Destination Name field, enter the trap destination name.
In the IP Address field, enter the IP address of the trap destination device.
In the Port Number field, enter the port number to which to send the trap.
Click the SNMP Version drop-down and select an SNMP version. For example, choose 1 for SNMPv1, 2 for SNMPv2, and 3 for SNMPv3.
1. If SNMPv1 or SNMPv2 are chosen from the drop-down, in the SNMP Read Community String field, enter the read community string SevOne NMS needs to authenticate onto the device.
2. If SNMPv3 is chosen from the drop-down, the following fields are available.
  1. In the User Name field, enter a username.
  2. In Engine ID field, enter the engine id which uniquely identifies the host. Enter the URL for the SevOne appliance (i.e. the trap destination device) into your web browser. On the navigation bar, click the Administration menu, select Cluster Manager, and then select Cluster Overview tab to obtain the Engine ID.
  3. Click the Authentication Protocol drop-down and select from NONE, MD5, SHA, SHA224, SHA256, SHA384, or SHA512.
  4. In the Authentication Key field, enter the password for the user.
  5. Click the Privacy Protocol drop-down and select from NONE, AES, AES192, AES192C, AES256, AES256C, DES, or 3DES to encrypt the trap.
    
    IMPORTANT
    
    If you are upgrading from SevOne NMS 5.7.2.x to SevOne NMS 6.3 or above, no action is required; trap destinations specified as AES192 or AES256 are automatically migrated to their Cisco equivalents, AES192C or AES256C respectively. New trap destinations against Cisco device(s) that use AES192 or AES256 , need to be specified as AES192C or AES256C respectively.
  6. In the Privacy Key field, enter the privacy key.
Select the Default check box to send traps to the destination by default. You can designate multiple default trap destination and you can define individual thresholds and policies to not use a default destination for specific traps when you define thresholds and policies.
Select the Enable check box to enable the trap destination.
Click Save.