Table Of Contents

Processed and Pass-Through Traps

Processed SNMP Traps

Multiple Processed SNMP Traps and the Event Details Displayed for Them

Processed SNMP Traps and Corresponding Operations Manager Events

Pass-Through and Unidentified Traps

Processed and Pass-Through Traps

---

For some SNMP traps, Cisco Unified Operations Manager (Operations Manager) either processes them or treats them as pass-through traps.

Traps and how Operations Manager treats them are described in these topics:

•Processed SNMP Traps

•Pass-Through and Unidentified Traps

Processed SNMP Traps

When Operations Manager 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 Notifications to forward specific traps to e-mail recipients or host machines. See Chapter 15, "Using Notifications."

---

Multiple Processed SNMP Traps and the Event Details Displayed for Them

For every specific trap, Operations Manager generates one event (see Processed SNMP Traps and Corresponding Operations Manager Events). For subsequent traps with the same specific trap identifier, but different object values, Operations Manager does nothing more until the trap clears. Operations Manager takes about ten minutes to clear an SNMP trap.

As a result, the Event Details display (accessible from the Alerts and Events display) shows the information obtained from the first trap that caused the event. For example, if the first trap contains Extension 101, and subsequent traps contain Extension 102 and Extension 103, Extension 101 continues to be displayed. Operations Manager updates this information only after clearing the trap and receiving the same specific trap from the device.

Processed SNMP Traps and Corresponding Operations Manager Events

This section lists the traps that Operations Manager processes and the event that Operations Manager generates for each trap.

Processed Standard SNMP Traps (RFC 1215)

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

Processed CISCO-STACK-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
Module Up	CardDown
Module Down

Processed CISCO-ISDN-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
demandNbrLayer2Change	OperationallyDown

Processed CISCO-NotificationEvent-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
QoVMOSViolation	ServiceQualityIssue
SMLostContactWithSensor	Cisco1040SensorDown

Processed CPQHLTH-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
cpqHeThermalSystemFanFailed	FanDown
cpqHeThermalSystemFanDegraded	FanDegraded
cpqHeThermalTempFailed	TemperatureSensorDown
cpqHeThermalTempDegraded	TemperatureSensorDegraded

Processed CISCO-UNITY-EXPRESS-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
ciscoUnityExpressApplAlert	CUEApplicationStatusChange
ciscoUnityExpressStorageAlert	CUEStorageIssue
ciscoUnityExpressSecurityAlert	CUESecurityIssue
ciscoUnityExpressCallMgrAlert	CUECCMConnectionLost
ciscoUnityExpressRescExhausted	CUEResourceExhausted
ciscoUnityExpressBackupAlert	CUEBackupFailed
ciscoUnityExpressNTPAlert	CUENTPIssue

Processed CISCO-CCME-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
ccmeEPhoneDeceased	CCMEEphoneDeceased
ccmeEphoneLoginFailed	CCMEEphoneLoginFailed
ccmeEPhoneRegFailed	CCMEEphoneRegistrationFailed
ccmeEphoneUnRegThresholdExceed	CCMEEphoneRegistrationsExceeded
ccmeKeyEphoneRegChangeNotif	CCMEKeyEphoneRegistrationChange
ccmeLivefeedMohFailedNotif	CCMELivefeedMOHFailed
ccmeMaxConferenceNotif	CCMEMaximumConferencesExceeded
ccmeNightServiceChangeNotif	CCMENightServiceChange
ccmeStatusChangeNotif	CCMEStatusChange

Processed CISCO-SRST-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
csrstFailNotif	SRSTRouterFailure

Processed CISCO-CONTACT-CENTER-APPS-MIB Traps

SNMP Trap	Corresponding Operations Manager Event
cccaIcmEvent	IPCCSingleStateNotification/IPCCDualStateNotification

The following are the values (as part of trap varbinds) which Operations Manager receives as part of the trap cccaIcmEvent:

•cccaEventComponentId

•cccaEventState

•cccaEventMessageId

•cccaEventOriginatingProcessName

•cccaEventTimestamp

•cccaEventText

The value cccaEventState is used to identify whether to raise IPCCSingleStateNotification or IPCCDualStateNotification based on the following:

•Raise—A raise state identifies a notification received as a result of a health-impacting condition, such as a process failure. A subsequent clear state notification will follow when the error condition is resolved.

•SingleStateRaise—The single state raise indicates that a health-impacting error has occurred and that a subsequent clear state notification will not be forthcoming. An example of a single state raise condition is an application configuration error that requires the system to be stopped and the problem resolved by an administrator before the affected component will function properly.

For additional information on the supported list of dual state traps, see the Serviceability Best Practices Guide for Unified ICME, Unified ICMN, Unified CCE, and Unified CCH.

Pass-Through and Unidentified Traps

Pass-through traps are traps that Operations Manager does not process. Operations Manager only forwards the trap on to another Manager of Managers application. Pass-through traps are shown in the Alerts and Events display as one of the following:

•InformAlarm

•MinorAlarm

•MajorAlarm

Traps that appear in the Alerts and Events display as unidentified traps are the result of events that are generated from processed traps (see Processed SNMP Traps) for devices that are not monitored by Operations Manager.