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 Network Director to collect and manage event and error information from these devices.

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

Note

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

Note

Network Director only supports SNMP V1 and V2C traps.

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 Network 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—Network Director is in communication with the device.

  • Down—Network 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 Network 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 Network Director. Network 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 controllers in the network. To enable SNMP traps on switches and controllers:

  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. So if you have both wireless devices and switches, you need to deploy the trap configurations in separate passes.
  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 Network 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.

  • Controllers traps and related MIBs are shown in Table 3.

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

PoE-alarms

mib-rfc3621.mib

Table 3: Controllers Traps

Trap

MIB

LinkDown

snmpTraps.mib

LlinkUp

snmpTraps.mib

Authentication

snmpTraps.mib

DeviceFail

trpzTrapsV2.mib

DeviceOkay

trpzTrapsV2.mib

PoEFail

trpzTrapsV2.mib

MobilityDomainJoin

trpzTrapsV2.mib

MobilityDomainTimeout

trpzTrapsV2.mib

RFDetectAdhocUser

trpzTrapsV2.mib

ClientAuthenticationFailure

trpzTrapsV2.mib

ClientAuthorizationFailure

trpzTrapsV2.mib

ClientAssociationFailure

trpzTrapsV2.mib

ClientDeAssociation

trpzTrapsV2.mib

ClientRoaming

trpzTrapsV2.mib

AutoTuneRadioPowerChange

trpzTrapsV2.mib

AutoTuneRadioChannelChange

trpzTrapsV2.mib

CounterMeasureStart

trpzTrapsV2.mib

CounterMeasureStop

trpzTrapsV2.mib

ClientDot1xFailure

trpzTrapsV2.mib

RFDetectDoS

trpzTrapsV2.mib

RFDetectDoSPort

trpzTrapsV2.mib

ClientIpAddrChange

trpzTrapsV2.mib

ClientAssociationSuccess

trpzTrapsV2.mib

ClientAuthenticationSuccess

trpzTrapsV2.mib

ClientDeAuthentication

trpzTrapsV2.mib

RFDetectBlacklisted

trpzTrapsV2.mib

RFDetectAdhocUserDisappear

trpzTrapsV2.mib

ApRejectLicenseExceeded

trpzTrapsV2.mib

ClientDynAuthorChangeSuccess

trpzTrapsV2.mib

ClientDynAuthorChangeFailure

trpzTrapsV2.mib

ClientDisconnect

trpzTrapsV2.mib

MobilityDomainFailOver

trpzTrapsV2.mib

MobilityDomainFailBack

trpzTrapsV2.mib

RFDetectRogueDeviceDisappear

trpzTrapsV2.mib

RFDetectSuspectDeviceDisappear

trpzTrapsV2.mib

RFDetectedClientViaRogueWiredAP

trpzTrapsV2.mib

RFDetectedClassificationChange

trpzTrapsV2.mib

ConfigurationSaved

trpzTrapsV2.mib

APNonOperStatus

trpzTrapsV2.mib

MichaelMICFailure

trpzTrapsV2.mib

ApManagerChange

trpzTrapsV2.mib

ClientCleared

trpzTrapsV2.mib

MobilityDomainResiliencyStatus

trpzTrapsV2.mib

ApOperRadioStatus

trpzTrapsV2.mib

ClientAuthorizationSuccess

trpzTrapsV2.mib

RFDetectRogueDevice

trpzTrapsV2.mib

RFDetectSuspectDevice

trpzTrapsV2.mib

ClusterFailure

trpzTrapsV2.mib

MultimediaCallFailure

trpzTrapsV2.mib

ApTunnelLimitExceeded

trpzTrapsV2.mib

WsTunnelLimitExceeded

trpzTrapsV2.mib

RFNoiseSource

trpzTrapsV2.mib

M2UConvNotPossibleTrap

trpzTrapsV2.mib

M2UConvAvailablityRestored

trpzTrapsV2.mib