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/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, page 5-1

---

All processed traps are forwarded in V1 format.

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 traps that DFM receives from devices that are not in the DFM inventory. These traps are shown in the Alerts and Activities display because of their relevance to fault monitoring. 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

If DFM does not know which device generated the trap, it ignores the trap.

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. You can get more information on an Unidentified Trap by looking at its Events page.

Clearing an Unidentified Trap

You can manually clear Unidentified Traps. Select the Unidentified Trap and click Clear to remove it from DFM. 

---

Note You are asked to confirm if you want to clear the Unidentified Trap. Enter your user ID. This will be used as a reference to identify who cleared the Unidentified Trap. Click OK to confirm and clear the Unidentified Trap, or click Cancel to retain the Unidentified Trap.

---