User Guide for IP Communications Operations Manager
Processed and Pass-through Traps, and Unidentified Traps and Events
Downloads: This chapterpdf (PDF - 194.0KB) The complete bookPDF (PDF - 7.58MB) | Feedback

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

Table Of Contents

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

Processed SNMP Traps

Multiple Processed SNMP Traps and the Event Details Displayed for Them

Processed SNMP Traps and Corresponding Operations Manager Events

Pass-Through SNMP Unidentified Traps

Other Unidentified Traps and Events


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


For some SNMP traps, IP Communications Operations Manager (Operations Manager) either processes them or treats them as pass-through traps. Pass-through traps are placed into an Unidentified Trap group or bucket. In other words, Operations Manager displays pass-through traps in the Alert and Events display with both a device type and the event name Unidentified Trap.

The Unidentified Trap bucket is also the holding place for other unusual traps and events. These traps and events, and how Operations Manager treats them, are described in these topics:

Processed SNMP Traps

Pass-Through SNMP Unidentified Traps

Other Unidentified Traps and Events

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 "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-SYSLOG-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

MOSviolation

ServiceQualityIssue

ProbeUnreachable

Cisco1040ProbeDown


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

IPCCNotification


Pass-Through SNMP Unidentified Traps

Pass-through traps are traps that Operations Manager receives from devices that are not in the Operations Manager inventory. These traps are shown in the Alerts and Events 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 name Unidentified Trap.

Because Operations Manager cannot identify these traps as being sent from devices being managed by Operations Manager, they are displayed in the All Alerts view.


Note Not all events that fall under Unidentified Trap are pass-through traps. See the Other Unidentified Traps and Events.


To view the actual trap in the event properties display, follow this procedure.


Step 1 Locate the alert ID for the unidentified trap in the Alerts and Events display.

Step 2 Click the alert ID corresponding to the unidentified trap. The Alert Details page appears.

Step 3 Click the event ID. The event properties page appears, displaying information about the pass-through trap.


Operations Manager treats the following traps as pass-through traps.

Pass-Through Standard SNMP Traps (RFC 1215)

Authentication Failure

Pass-Through CISCO-STACK-MIB Traps

lerAlarmOn

lerAlarmOff

ipPermitDeniedTrap

sysConfigChangeTrap

Pass-Through STP Traps

STPnewRoot

STPtopologyChange

Pass-Through Repeater MIB Traps

rptrHealth

rptrGroupChange

rptrResetEvent

Pass-Through CISCO-RHINO-MIB Traps

ciscoLS1010ChassisFailureNotification

ciscoLS1010ChassisChangeNotification

Pass-Through CISCO-VTP-MIB Traps

vtpConfigRevNumberErro

rvtpConfigDigestError

vtpServerDisabled

vtpMtuTooBig

vtpVlanRingNumberConfigConflict

vtpVersionOneDeviceDetected

vlanTrunkPortDynamicStatusChange

Pass-Through CISCO-ENVMON-MIB Traps

ciscoEnvMonShutdownNotification

Pass-Through CISCO-VLAN-MEMBERSHIP-MIB Traps

vmVmpsChange

Pass-Through CISCO-ACCESS-ENVMON-MIB Traps

caemTemperatureNotification

caemVoltageNotification

Pass-Through CISCO-CONFIG-MAN-MIB Traps

ciscoConfigManEvent

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

cevFan15540FTMP

cevPortTransparent

cevPortWave

Pass-Through CISCO-VOICE-APPS-MIB Traps

cvaModuleStart

cvaModuleStop

cvaProcessStart

cvaProcessStop

cvaModuleRunTimeFailure

Pass-Through CISCO-CCM-MIB Traps

ccmGatewayFailed

ccmMediaResourceListExhausted

ccmCallManagerFailed

ccmGatewayLayer2Change

Pass-Through UMSEVENT-MIB Traps

iBMPSGFanEventBindings

iBMPSGTemperatureEventBindings

iBMPSGVoltageEventBindings

Other Unidentified Traps and Events

The Unidentified Trap bucket may contain nonpass-through traps, along with other unexpected Operations Manager events. This can happen under the following circumstances:

When an event occurs on a device that is being discovered by Operations Manager.

When an event occurs on a device that Operations Manager does not monitor, such as the Cisco 1040 Sensor.

When Operations Manager encounters problems in its operation.

When the Operations Manager server is busy, and synthetic tests cannot run. (The SyntheticTestNotRun event is displayed as an Unidentified Trap because it does not relate to a specific device.)