Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Enabling SNMP Categories and Setting Trap Destinations

 

SNMP traps must be enabled on network devices for Connectivity Services Director to collect and manage event and error information from these devices.

Connectivity Services Director organizes switch and controller traps by categories. These categories must be enabled and deployed in order to forward trap information to Connectivity Services Director.

Note

Connectivity Services Director uses protocol port 10162 for receiving traps from devices. This port must be open on the devices.

This topic describes:

Viewing Eligible Devices for Trap Forwarding

Traps are enabled on the Devices page in Deploy mode. To locate this page:

  1. Select Deploy in the Connectivity Services Director banner.
  2. Select Set SNMP Trap Configuration in the Tasks pane. The Devices page opens. For a description of fields in the Devices page, view Table 1.

Table 1: Device Page Fields

Field

Description

Name

Either the hostname or the IP address of the device.

IP Address

Device IP address.

Model

Device model number.

OS Version

Version and release level of the operating system running on the device.

Connection State

State of connection to the device. Valid states are:

  • Up—Connectivity Services Director is in communication with the device.

  • Down—Connectivity Services Director cannot communicate with the device. You cannot enable traps on devices that are in this state.

Configuration State

Either the device’s configuration is in sync or out-of-sync with Connectivity Services Director’s version:

  • IN_SYNC—The configuration is in-sync with the database.

  • OUT_OF_SYNC—The configuration is out-of-sync with the database.

Enabling Trap Forwarding

Select Set SNMP Trap Configuration in Deploy mode to enable your network devices to pass SNMP traps and events to Connectivity Services Director. Connectivity Services Director creates a target group called networkdirector_trap_group using target port 10162. The Community name is public and the access is read-write-notify..

Before enabling trap forwarding, complete device discovery for all the devices and ensure they are in the up state. Down devices cannot be enabled for trap forwarding.

Selecting Set SNMP Trap Configuration displays the Devices page which contains a table of all discovered switches and routers in the network. To enable SNMP traps on switches and routers:

  1. Either select individual check boxes for devices, or select the check box next to the Name heading to select all devices. These devices must be up and in the same device family.
  2. Click Deploy Trap Configuration. The Deploy Options window opens.
  3. Fill in a new deployment job name or accept the default name of Deploy SNMP Targets.
  4. Either select check boxes for individual traps, or select the check box next to the Trap Name heading to select all traps. These traps are discussed further in Deploying SNMP Trap Configurations.Tip

    To clear an existing configuration, do not select any of the check boxes.

  5. Click Ok. The Deploy Configuration window opens, which shows the status of deploying the configuration change.
  6. Review the outcome of the deployment.

After enabling the traps, enable the alarms and establish the alarm retention period. These tasks are located in Preferences in the Connectivity Services Director banner.

Deploying SNMP Trap Configurations

The Deploy Options for trap forwarding enable you to select individual traps or all traps for the selected device family.

The device family determines which traps are displayed in the Deploy Options window. The following tables map the trap to one or more MIBs being used.

  • EX Series switches traps and related MIBs are shown in Table 2.

Table 2: EX Series Switches Traps

Trap

MIB

Chassis

jnxExMibRoot.mib

Link

snmpTraps.mib

Configuration

jnxCfgMgnt.mib

Authentication

jnxJsAuth.mib

Remote operations

jnxPing.mib

Routing

jnx-ipv6.mib

Startup

snmpTraps.mib

Rmon-alarm

jnxRmon.mib

Vrrp-events

rfc2787a.mib

Services

jnxServices.mib

Sonet-alarms

jnx-sonetaps.mib

Otn-alarms

jnxMIbs.mib