User Guide for Cisco Unified Operations Manager 8.5
Processed SNMP Traps
Downloads: This chapterpdf (PDF - 136.0KB) The complete bookPDF (PDF - 14.64MB) | Feedback

Processed SNMP Traps

Table Of Contents

Processed SNMP Traps

Processed SNMP Traps

Multiple Processed SNMP Traps and the Event Details Displayed for Them

Processed SNMP Traps and Corresponding Operations Manager Events

Unidentified Traps


Processed SNMP Traps


How Cisco Unified Operations Manager (Operations Manager) treats SNMP traps are described in these topics:

Processed SNMP Traps

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 14, "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 Fault Monitor) 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. This section contains:

Processed Standard SNMP Traps (RFC 1215)

Processed CISCO-STACK-MIB Traps

Processed CISCO-ISDN-MIB Traps

Processed CISCO-NotificationEvent-MIB Traps

Processed CPQHLTH-MIB Traps

Processed IBM-SYSTEM-RAID MIB

Processed CISCO-UNITY-EXPRESS-MIB Traps

Processed CISCO-CCME-MIB Traps

Processed CISCO-SRST-MIB Traps

Processed CISCO-MEETINGPLACE-MIB Traps

Processed CISCO-CONTACT-CENTER-APPS-MIB Traps

Processed CISCO-TELEPRESENCE-MIB SNMP Trap

Processed CISCO-ACCESS-ENVMON-MIB Traps

Processed CISCO-CONFIG-MAN-MIB Traps

Processed CISCO-CONTENT-ENGINE-MIB Traps

Processed CISCO-DEVICE-EXCEPTION-REPORTING-MIB Traps

Processed CISCO-ENTITY-FRU-CONTROL-MIB Traps

Processed CISCO-ENVMON-MIB Traps

Processed Repeater MIB Traps

Processed CISCO-RHINO-MIB Traps

Processed CISCO-RTTMON-MIB Traps

Processed CISCO-STP-MIB Traps

Processed CISCO-VLAN-MEMBERSHIP-MIB Traps

Processed CISCO-VPDN-MGMT-MIB Traps

Processed CISCO-VTP-MIB Traps

Processed Standard SNMP Traps (RFC 1215)

SNMP Trap
Corresponding Operations Manager Event

Cold Start

RepeatedRestarts

Warm Start

Link Up

Flapping

Link Down

Authentication Failure

MinorAlarm


Processed CISCO-STACK-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

Module Up

CardDown

Module Down

lerAlarmOn

MinorAlarm

lerAlarmOff

ipPermitDeniedTrap

MinorAlarm

sysConfigChangeTrap


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

SensorDown


Processed CPQHLTH-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

cpqHeThermalSystemFanFailed

FanDown

cpqHeThermalSystemFanDegraded

FanDegraded

cpqHeThermalTempFailed

TemperatureSensorDown

cpqHeThermalTempDegraded

TemperatureSensorDegraded


Processed IBM-SYSTEM-RAID MIB

SNMP Trap
Corresponding Operations Manager Event

ibmServeRaidDefunctDrive

IBMDiskTrapEvent


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-MEETINGPLACE-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

mpMajSwAlarm

MeetingPlaceSwAlarm


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.

Processed CISCO-TELEPRESENCE-MIB SNMP Trap

SNMP Trap
Corresponding Operations Manager Event

ctpPeripheralErrorNotification

ctpPeripheralCableError

ctpPeripheralPowerError

ctpPeripheralLinkError

ctpPeripheralConfigError

ctpPeripheralDeviceError

ctpPeripheralSystemError

ctpPeripheralInError


The ctpPeripheralErrorNotification trap could result in any of the events listed above.

The ctpPeripheralInError event is generated when the device is not managed or if a component is not discovered in Operations Manager. Operations Manager clears the event after one hour.

All other events are generated based on the error code received from the trap or from polling when the device is managed in Operations Manager. Operations Manager clears these events when polling detects noError.

Processed CISCO-ACCESS-ENVMON-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

caemTemperatureNotification

InformAlarm

caemVoltageNotification

MinorAlarm


Processed CISCO-CONFIG-MAN-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

ciscoConfigManEvent

InformAlarm


Processed CISCO-CONTENT-ENGINE-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

ciscoContentEngineWriteTransFailed

MajorAlarm

ciscoContentEngineOverloadBypass


Processed CISCO-DEVICE-EXCEPTION-REPORTING-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

cderMonitoredExceptionEvent

InformAlarm


Processed CISCO-ENTITY-FRU-CONTROL-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

cevFanONS15540FanTray8

MajorAlarm

cevPortTransparent

cevPortWave


Processed CISCO-ENVMON-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

ciscoEnvMonShutdownNotification

InformAlarm


Processed Repeater MIB Traps

SNMP Trap
Corresponding Operations Manager Event

rptrHealth

MinorAlarm

rptrGroupChange

InformAlarm

rptrResetEvent


Processed CISCO-RHINO-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

ciscoLS1010ChassisFailureNotification

MajorAlarm

ciscoLS1010ChassisChangeNotification

InformAlarm


Processed CISCO-RTTMON-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

CiscoRTTMon_rttMonConnectionChange
Notification

InformAlarm

CiscoRTTMon_rttMonTimeoutNotification

CiscoRTTMon_rttMonThresholdNotification

MajorAlarm

CiscoRTTMon_rttMonVerifyErrorNotification

InformAlarm

CiscoRTTMon_rttMonNotification

MajorAlarm


Processed CISCO-STP-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

STPnewRoot

MajorAlarm

STPtopologyChange

MinorAlarm


Processed CISCO-VLAN-MEMBERSHIP-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

vmVmpsChange

MajorAlarm


Processed CISCO-VPDN-MGMT-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

CiscoVpdnMgmt_cvpdnNotifSession

MajorAlarm


Processed CISCO-VTP-MIB Traps

SNMP Trap
Corresponding Operations Manager Event

vtpConfigRevNumberError

InformAlarm

rvtpConfigDigestError InformAlarm

vtpServerDisabled MinorAlarm

MinorAlarm

vtpMtuTooBig MinorAlarm

vtpVlanRingNumberConfigConflict MinorAlarm

vtpVersionOneDeviceDetected InformAlarm

InformAlarm

vlanTrunkPortDynamicStatusChange InformAlarm



NoteMost, but not all, trap-based events are automatically cleared by Operations Manager after 60 minutes. Auto-clearing the event does not indicate that the issue is resolved in the network.

In some cases, events remain active for more than 60 minutes. This indicates these traps may be reoccurring.Operations Manager processes the event to update the last time the fault occurred, hence those events remain active for a longer duration than the default 60 minutes.


Unidentified Traps

The "Unidentified Trap" bucket may contain events that may be raised under the following circumstances:

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

When an event occurs because of certain traps, sent by a device that Operations Manager does not manage.