Table Of Contents

Processed and Pass-Through Traps, and Unidentified Traps and Events

Processed SNMP Traps

Pass-Through SNMP Unidentified Traps

Unidentified Traps

Clearing an Unidentified Trap

Processed and Pass-Through Traps, and Unidentified Traps and Events

---

For some SNMP traps, Device Fault Manager (DFM) either processes them or treats them as pass-through traps. These traps, and how DFM treats them, are described in these topics:

•Processed SNMP Traps

•Pass-Through SNMP Unidentified Traps

•Unidentified Traps

Processed SNMP Traps

When DFM receives certain SNMP traps, it analyzes the data found in the following fields of each SNMP trap message, and changes the property value of the object property if required:

•Enterprise (the sysObjectID of the agent or object)

•Generic Trap Identifier

•Specific Trap Identifier

•Variable-Bindings

•IP address of the SNMP agent

---

Note Use Notification Services to forward specific traps to e-mail recipients or host machines. See Using Notification Services

---

All processed traps are forwarded in V1 format. For more information on Processed Traps, see:

•Processed Standard SNMP Traps (RFC 1215)

•Processed CISCO-STACK-MIB Traps

•Processed CISCO-ISDN-MIB Traps

•Processed CISCO-ENTITY-FRU-CONTROL-MIB Trap

Processed Standard SNMP Traps (RFC 1215)

SNMP Trap	Corresponding DFM Event
Cold Start	RepeatedRestarts
Warm Start
Link Up	Flapping
Link Down

Processed CISCO-STACK-MIB Traps

SNMP Trap	Corresponding DFM Event
Module Up	CardDown
Module Down

Processed CISCO-ISDN-MIB Traps

SNMP Trap	Corresponding DFM Event
demandNbrLayer2Change	OperationallyDown

Processed CISCO-ENTITY-FRU-CONTROL-MIB Trap

SNMP Trap	Corresponding DFM Event
cefcModuleStatusChange	OperationallyDown

Pass-Through SNMP Unidentified Traps

Pass-through traps are the traps that are generated from devices and are not processed by DFM. The traps appear in the alerts and activities page, if they are generated from the devices that are managed by DFM. DFM cannot process these traps and map them to a topology element such as cards and interfaces. However, DFM can forward the traps irrespective of the device state is either managed or unmanaged. Forwarding these traps is controlled using Configuration > Other Configurations > SNMP Trap Forwarding.

Pass-through traps are displayed as follows:

•As one of the following events:

–InformAlarm

–MinorAlarm

–MajorAlarm

•With the device type and the device name from which it was generated

---

Note Pass-through traps will be cleared after a default interval of 10 minutes to one hour. If DFM does not know which device generated the trap, it ignores the trap.

---

For more information on Pass-Through Traps, see:

•Pass-Through Standard SNMP Traps (RFC 1215)

•Pass-Through CISCO-STACK-MIB Traps

•Pass-Through STP Traps

•Pass-Through Repeater MIB Traps

•Pass-Through CISCO-RHINO-MIB Traps

•Pass-Through CISCO-VTP-MIB Traps

•Pass-Through CISCO-ENVMON-MIB Traps

•Pass-Through CISCO-VLAN-MEMBERSHIP-MIB Traps

•Pass-Through CISCO-ACCESS-ENVMON-MIB Traps

•Pass-Through CISCO-CONFIG-MAN-MIB Traps

•Pass-Through CISCO-ENTITY-FRU-CONTROL-MIB Traps

•Pass-Through CISCO-CONTENT-ENGINE-MIB Traps

•Pass-Through CISCO-DEVICE-EXCEPTION-REPORTING-MIB Traps

Pass-Through Standard SNMP Traps (RFC 1215)

SNMP Trap	Corresponding DFM Event
Authentication Failure	MinorAlarm

Pass-Through CISCO-STACK-MIB Traps

SNMP Trap	Corresponding DFM Event
lerAlarmOn	MinorAlarm
lerAlarmOff	MinorAlarm
ipPermitDeniedTrap	InformAlarm
sysConfigChangeTrap	InformAlarm

Pass-Through STP Traps

SNMP Trap	Corresponding DFM Event
STPnewRoot	MajorAlarm
STPtopologyChange	MinorAlarm

Pass-Through Repeater MIB Traps

SNMP Trap	Corresponding DFM Event
rptrHealth	MinorAlarm
rptrGroupChange	InformAlarm
rptrResetEvent	InformAlarm

Pass-Through CISCO-RHINO-MIB Traps

SNMP Trap	Corresponding DFM Event
ciscoLS1010ChassisFailureNotification	MajorAlarm
ciscoLS1010ChassisChangeNotification	InformAlarm

Pass-Through CISCO-VTP-MIB Traps

SNMP Trap	Corresponding DFM Event
vtpConfigRevNumberError	InformAlarm
rvtpConfigDigestError	InformAlarm
vtpServerDisabled	MinorAlarm
vtpMtuTooBig	MinorAlarm
vtpVlanRingNumberConfigConflict	MinorAlarm
vtpVersionOneDeviceDetected	InformAlarm
vlanTrunkPortDynamicStatusChange	InformAlarm

Pass-Through CISCO-ENVMON-MIB Traps

SNMP Trap	Corresponding DFM Event
ciscoEnvMonShutdownNotification	InformAlarm

Pass-Through CISCO-VLAN-MEMBERSHIP-MIB Traps

SNMP Trap	Corresponding DFM Event
vmVmpsChange	MajorAlarm

Pass-Through CISCO-ACCESS-ENVMON-MIB Traps

SNMP Trap	Corresponding DFM Event
caemTemperatureNotification	InformAlarm
caemVoltageNotification	MinorAlarm

Pass-Through CISCO-CONFIG-MAN-MIB Traps

SNMP Trap	Corresponding DFM Event
ciscoConfigManEvent	InformAlarm

Pass-Through CISCO-ENTITY-FRU-CONTROL-MIB Traps

SNMP Trap	Corresponding DFM Event
cevFanONS15540FanTray8	MajorAlarm
cevPortTransparent	MajorAlarm
cevPortWave	MajorAlarm

Pass-Through CISCO-CONTENT-ENGINE-MIB Traps

SNMP Trap	Corresponding DFM Event
ciscoContentEngineWriteTransFailed	MajorAlarm
ciscoContentEngineOverloadBypass	MajorAlarm

Pass-Through CISCO-DEVICE-EXCEPTION-REPORTING-MIB Traps

SNMP Trap	Corresponding DFM Event
cderMonitoredExceptionEvent	InformAlarm

Unidentified Traps

DFM may display an event as an Unidentified Trap. Normally an Unidentified Trap is reported when an event occurs on a device that is being discovered by DFM. To get more information on an Unidentified Trap see the corresponding Events page.

Clearing an Unidentified Trap

You can manually clear Unidentified Traps from the DFM. To do this:

---

Step 1 Select the Unidentified Trap and click Clear

A message appears prompting you to confirm the clearing

Step 2 Enter your user ID.

This will be used as a reference to identify who cleared the Unidentified Trap.

Step 3 Click OK to confirm

The Unidentified trap is cleared

To retain the trap click Cancel .

---