Cisco 7000 Series Manager Alarm Model Programming Reference Guide, 2.1

Cisco 7000 Series Manager Version 2.1
Alarm Model Document

This document consists of the following sections:

• Trap Reception Alarms

• State Behavior Alarms

• Alarm Class Hierarchy

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

• Obtaining Additional Publications and Information

Trap Reception Alarms

This section provides the trap reception alarms Cisco 7000 Series Manager version 2.1 supports in tabular format (see the following page).

Alarm descriptions are made up of more information than previously available. In some cases all the description is made up of the varbinds, for example the description only displays these varbinds in an order. In order to determine what the description for any given alarm will be, simply insert the relevant varbind value where ever a varbind appears in the description.

For example, the BgpEstablished trap with an "opensent" and last error of 0x0010 would be received as:

BGPEstablished: peer connection state is <bgpPeerState = 4>, peer last error is 
<bgpPeerLastError = 0x0010>

The description for this example would display as:

BGPEstablished: peer connection state is opensent, peer last error is 0x0010

Table 1 Trap Reception Alarms


MIB	Trap	Trap Varbind Value	Maps to Alarm Class	Alarm Description	Alarm Severity	Raised on	Clear Correlation Rules¹
BGP4-MIB	BgpEstablished	bgpPeerState 1 = idle bgpPeerState 2 = connect bgpPeerState 3 = active bgpPeerState 4 = opensent bgpPeerState 5 = openconfirm bgpPeerState 6 = established bgpPeerLastError = OctetString value	ciscoBgpEstablishedAlarm	BGPEstablished: peer connection state is <bgpPeerState>, peer last error is <bgpPeerLastError >	Normal	Chassis	BgpBackwardTransition
BGP4-MIB	BgpBackwardTransition	bgpPeerState 1 = idle bgpPeerState 2 = connect bgpPeerState 3 = active bgpPeerState 4 = opensent bgpPeerState 5 = openconfirm bgpPeerState 6 = established bgpPeerLastError = OctetString value	ciscoBgpBackwardTransitionAlarm	BgpBackwardTransition: peer connection state is <bgpPeerState>, peer last error is <bgpPeerLastError >	Major	Chassis	ciscoBgpEstablishedAlarm
CISCO-CONFIG-MAN-MIB	CiscoConfigManEventNotification	ccmHistoryEventCommandSource = {1,2} {commandLine,snmp} ccmHistoryEventConfigSource = {1..7} ccmHistoryEventConfigDestination = {1..7} 1 = erase 2 = commnadSource 3 = running 4 = startup 5 = local 6 = networkTftp 7 = networkRcp	ciscoConfigManEventAlarm	Config Change, Command Source: <ccmHistoryEventCommandSource >, Config Source: <ccmHistoryEventConfigSource>, Config Destination: <ccmHistoryEventConfigDestination>	Info	Chassis
CISCO-ENVMON-MIB	ciscoChassisChangeEntity		ciscoChassisChangeEntityAlarm	Chassis Configuration has changed	Info	Chassis
	ciscoEnvMonVoltageNotification		ciscoChassisShutdownEnvmonAlarm	Environmental Monitor: Initiating Chassis Shutdown	Critical	Chassis
	CiscoEnvMonVoltage Notification	ciscoEnvMonVoltageStatusDescr = OctetString ciscoEnvMonVoltageStatusValue = Integer in mV ciscoEnvMonVoltageState = integer {1..5} 1 = normal	CiscoChassis VoltageNormal EnvmonAlarm	<ciscoEnvMonVoltageStatusDescr>, <ciscoEnvMonVoltageState>, <ciscoEnvMonVoltageStatusValue> mV	Normal	Chassis	•CiscoChassisVoltageWarningEnvmonAlarm •CiscoChassisVoltageCriticalEnvmonAlarm •CiscoChassisVoltageShutdownEnvmonAlarm
		2 = warning	ciscoChassisVoltageWarningEnvmonAlarm	Same as above	Warning	Chassis
		3 = critical	ciscoChassisVoltageCriticalEnvmonAlarm	Same as above	Critical	Chassis
		4 = shutdown	ciscoChassisVoltageShutdownEnvmonAlarm	Same as above	Critical	Chassis
		5 = notPresent	ciscoChassisVoltageNotPresentEnvmonAlarm	Same as above	Informational	Chassis
CISCO-ENVMON-MIB (continued)	CiscoEnvMonTemperatureNotification	ciscoEnvMonTemperatureStatusDescr = OctetString ciscoEnvMonTemperatureState = Integer in mV ciscoEnvMonTemperatureStatusValue = Integer {1..5} 1 = normal	CiscoChassisTempOKEnvmon Alarm	<ciscoEnvMonTemperatureStatusDescr>, <ciscoEnvMonTemperatureState>, <ciscoEnvMonTemperatureStatusValue> Celsius	Normal	Chassis	•CiscoChassisTempWarningEnvmonAlarm •CiscoChassisTempCriticalEnvmonAlarm •CiscoChassisTempShutdownEnvmonAlarm
		2 = warning	CiscoChassisTempWarning EnvmonAlarm	Same as above	Warning	Chassis
		3 = critical	CiscoChassisTemp CriticalEnvmon Alarm	Same as above	Critical	Chassis
		4 = shutdown	CiscoChassisTemp ShutdownEnvmon Alarm	Same as above	Critical	Chassis
		5 = notPresent	ciscoChassisTemperatureNotPresentEnvmonAlarm	Same as above	Informational	Chassis
CISCO-ENVMON-MIB (continued)	CiscoEnvMonFanNotification	ciscoEnvMonFanStatusDescr = OctetString ciscoEnvMonFanStatusValue = Integer {1..5} 1 = normal	CiscoChassisFan NormalEnvmon Alarm	<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>	Normal	Chassis	•CiscoChassisFanWarningEnvmonAlarm •CiscoChassisFanCriticalEnvmonAlarm •CiscoChassisFanShutdownEnvmonAlarm
		2 = warning	CiscoChassisFan WarningEnvmon Alarm	Same as above	Warning	Chassis
		3 = critical	CiscoChassisFan CriticalEnvmon Alarm	Same as above	Critical	Chassis
		4 = shutdown	CiscoChassisFan ShutdownEnvmon Alarm	Same as above	Critical	Chassis
		5 = notPresent	CiscoChassisFanNotPresentEnvmonAlarm	Same as above	Informational	Chassis
CISCO-ENVMON-MIB (continued)	CiscoEnvMonRedundantSupplyNotification	ciscoEnvMonRedundatSupplyStatusDescr = OctetString ciscoEnvMonRedundatSupplyStatusValue = Integer {1..5} 1 = normal	CiscoChassisPowerSupply RedundantSupply OKEnvMonAlarm	<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>	Normal	Chassis	•CiscoChassisPowerSupplyRedundantSupplyWarningEnvMonAlarm •CiscoChassisPowerSupplyRedundantSupplyCriticalEnvMonAlarm •CiscoChassisPowerSupplyRedundantSupplyShutdownEnvMonAlarm •CiscoChassisPowerSupplyRedundantSupplyNotPresentEnvMonAlarm
		2 = warning	CiscoChassisPowerSupplyRedundant SupplyWarningEnvMonAlarm	Same as above	Warning	Chassis
		3 = critical	CiscoChassisPowerSupplyRedundant SupplyCriticalEnv MonAlarm	Same as above	Critical	Chassis
		4 = shutdown	CiscoChassisPowerSupplyRedundant SupplyCriticalEnv MonAlarm	Same as above	Critical	Chassis
		5 = notPresent	CiscoChassisPowerSupplyRedundant SupplyNotPresent EnvMonAlarm	Same as above	Informational	Chassis
CISCO-SYSLOG-MIB	ClogMessageGenerated	clogHistMsgText = OctetString clogHistFacility = OctetString clogHistMsgName =OctetString clogHistTimestamp = TimeTicks clogHistSeverity = integer {1-8} 1 = SeverityEmergency	CiscoSyslogSeverityEmergency	Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]	Critical	Chassis
		2 = SeverityAlert	CiscoSyslogSeverityAlert	Same as above	Critical	Chassis
		3 = SeverityCritical	CiscoSyslogSeverityCritical	Same as above	Critical	Chassis
		4 =SeverityError	CiscoSyslogSeverityError	Same as above	Major	Chassis
		5 = SeverityWarning	CiscoSyslogSeverityWarning	Same as above	Minor	Chassis
		6 = SeverityNotice	CiscoSyslogSeverityNotice	Same as above	Minor	Chassis
		7 = SeverityInfo	CiscoSyslogSeverityInfo	Same as above	Informational	Chassis
		8 = SeverityDebug	CiscoSyslogSeverityDebug	Same as above	Informational	Chassis
IF-MIB	LinkDown	<ifIndex> = Integer {1..x} = uniquie interface number	LinkDown	Link <ifIndex> down	Major	Interface (Chassis if interface discovery is off)
IF-MIB	LinkUp	<ifIndex> = Integer {1..x} = uniquie interface number	LinkUp	Link <ifIndex> up	Normal	Interface (Chassis if interface discovery is off)	LinkDown
SNMPv2-MIB	ColdStart		CiscoColdStart Alarm	"Cold Start: Agent reinitializing; configuration may have changed."	Major	Chassis
	WarmStart		CiscoWarmStart Alarm	"Warm Start: Agent reinitializing; configuration is unaltered."	Major	Chassis
	Authentication Failure		CiscoAuthenticationFailureAlarm	�Authentication Failure�	Major	Chassis
ENTITY	EntConfigChange		CiscoChassis ChangeEntity Alarm	"Chassis Configuration has changed"	Informational	Chassis
CISCO-ENTITY-ALARM-MIB	CeAlarmAsserted	ceAlarmHistEntPhysicalIndex integer {1..x} ceAlarmHistAlarmType = integer {1..x} ceAlarmHistSeverity = integer {1..4} ceAlarmHistTimeStamp = timeticks ceAlarmHistSeverity 1 = critical	CeAlarmAsserted	Asserted:<ceAlarmHistEntPhysicalIndex><ceAlarmHistAlarmType>	Critical	Chassis Module Interface
		CeAlarmHistSeverity 2 = major	ceAlarmAsserted		Major	Chassis Module Interface
		CeAlarmHistSeverity 3 = minor	ceAlarmAsserted		Minor	Chassis Module Interface
		CeAlarmHistSeverity 4 = info	ceAlarmAsserted		Informational	Chassis Module Interface
	CeAlarmCleared	ceAlarmHistEntPhysicalIndex integer {1..x} ceAlarmHistAlarmType = integer {1..x} ceAlarmHistSeverity = integer {1} ceAlarmHistTimeStamp = timeticks ceAlarmHistAlarmType varies according to card.	ceAlarmCleared	Cleared:<ceAlarmHistEntPhysicalIndex > <ceAlarmHistAlarmType>	Normal	Chassis Module Interface	CeAlarmAsserted where values of ceAlarmHistEntPhysicalIndex and ceAlarmHistAlarmType varbinds match
CISCO-RHINO-MIB	CiscoLS1010ChassisFailureNotification	CiscoLS1010ChassisPs0Status = ok (2)	CiscoChassisPowerSupplyPS0OKRhinoAlarm	�Chassis Power Supply PS0 OK�	Normal		•ciscoChassisPower •SupplyPS0RhinoAlarm •CiscoChassisPowerSupplyPS0OKRhinoAlarm
		CiscoLS1010ChassisPs0Status = fault (3)	CiscoChassisPowerSupplyPS0Rhino Alarm	�Chassis Power Supply PS0 Fault"	Major
		CiscoLS1010ChassisPs0Status = partialFault (5)	CiscoChassisPowerSupplyPS0Rhino Alarm	�Chassis Power Supply PS0 Fault"	Major
		ciscoLS1010ChassisPs1Status = ok (2)	CiscoChassisPowerSupplyPS1OKRhinoAlarm	�Chassis Power Supply PS1 OK�	Normal		•CiscoChassisPowerSupplyPS1RhinoAlarm •CiscoChassisPowerSupplyPS1OKRhinoAlarm
		CiscoLS1010ChassisPs1Status = fault (3)	CiscoChassisPowerSupply PS1RhinoAlarm	�Chassis Power Supply PS1 Fault"	Major
		CiscoLS1010ChassisPs1Status = partialFault (5)	CiscoChassisPowerSupplyPS1Rhino Alarm	�Chassis Power Supply PS1 Fault"	Major
		ciscoLS1010ChassisFanStatus = ok (2)	CiscoChassisFan NormalRhinoAlarm	"Chassis Fan Normal"	Normal		•CiscoChassisFanFaultRhinoAlarm •CiscoChassisFanPartialFaultRhinoAlarm •CiscoChassisFanNormalRhinoAlarm
		ciscoLS1010ChassisFanStatus = fault (3)	CiscoChassisFan FaultRhinoAlarm	"Chassis Fan Alarm"	Major
		ciscoLS1010ChassisFanStatus = partialFault (5)	CiscoChassisFan PartialFaultRhino Alarm	"Chassis Fan has Partial Fault"	Major
		ciscoLS1010ChassisFanStatus = empty (6)	CiscoChassisFanNotPresentRhinoAlarm	"Chassis Fan Not Present"	Informational
CISCO-RHINO-MIB (continued)	CiscoLS1010ChassisFailureNotification (continued)	CiscoLS1010Chassis12VoltStatus = ok (1)	CiscoChassisVoltage12VoltOKRhino Alarm	"Chassis 12Volt Line OK"	Normal		•ciscoChassisVoltage12VoltRhinoAlarm •ciscoChassisVoltage12VoltOKRhinoAlarm
		CiscoLS1010Chassis12VoltStatus = outOfTolerance (2)	CiscoChassis Voltage12Volt RhinoAlarm	"Chassis 12Volt Line Out Of Tolerance"	Major
		CiscoLS1010Chassis12VoltStatus = unknown (3)	CiscoChassis Voltage12Volt UnknownRhino Alarm	"Chassis Voltage 12Volt Unknown Alarm"	Informational
		CiscoLS1010ChassisTempStatus =ok (1)	CiscoChassisTempOKRhinoAlarm	"Chassis Temperature OK"	Normal		•CiscoChassisOverTempRhinoAlarm •ciscoChassisTempWarningRhinoAlarm •ciscoChassisTempMinorRhinoAlarm •ciscoChassisTempMajorRhinoAlarm •ciscoChassisTempCriticalRhinoAlarm •ciscoChassisTempOKRhinoAlarm
		CiscoLS1010ChassisTempStatus = overTemperature (2)	CiscoChassisOver TempRhinoAlarm	"Chassis Over Temperature"	Warning
		CiscoLS1010ChassisTempStatus = minorWarning (3)	CiscoChassisTempMinorRhinoAlarm	"Chassis Temperature Minor Warning"	Minor
		CiscoLS1010ChassisTempStatus = majorWarning (4)	CiscoChassisTempMajorRhinoAlarm	"Chassis Temperature Major Warning"	Major
		CiscoLS1010ChassisTempStatus = criticalWarning (5)	CiscoChassisTemp CriticalRhino Alarm	"Chassis Temperature at Critical stage"	Critical

¹Clears alarms of the class(es) listed.

State Behavior Alarms

This section provides the state behavior alarms Cisco 7000 Series Manager version 2.1 supports in tabular format.

Table 2 State Behavior Alarms


When Raised	Alarm Description	Alarm Class	Alarm Severity	Raised On	Clear Correlation Rules¹
Chassis moves into Normal State	Chassis Operational Status is Up	CiscoChassisNormalAlarm	Normal	Chassis	•CiscoChassisDiscoveryLost CommsAlarm •CiscoChassisCommissioningAlarm •CiscoChassisPerformanceLoggingOnAlarm •CiscoChassisMismatchedAlarm •ciscoChassisNormalAlarm
Chassis moves into Lost Comms State	Connection to device Lost	CiscoChassisLostCommsAlarm	Major	Chassis	•CiscoChassisLostCommsAlarm
Chassis moves into Mismatch State	Deployed chassis does not match actual device	CiscoChassisMismatchedAlarm	Critical	Chassis	•ciscoChassisLostCommsAlarm •ciscoChassisDiscoveryLostCommsAlarm •ciscoChassisMismatchedAlarm
Chassis moves into Discovery Lost Comms State	Connection to device lost during Discovery	CiscoChassisDiscoveryLostCommsAlarm	Major	Chassis	•CiscoChassisDiscoveryAlarm •CiscoChassisDiscoveryLostCommsAlarm
Sub Chassis Discovery fails	Chassis commissioning failed	CiscoChassisCommissionFailAlarm	Critical	Chassis	•CiscoChassisCommissionFailAlarm •ciscoChassisCommissionFailAlarm
Sub Chassis Discovery is successful	Chassis commissioning successful	CiscoChassisCommissionOKAlarm	Normal	Chassis	•CiscoChassisCommissionFailAlarm •CiscoChassisCommissionOKAlarm
Change is detected in a Chassis being managed via the OLD-CISCO-CHASSIS MIB	Chassis Configuration has changed	CiscoChassisChangeHeartbeatFailOldChassisAlarm"	Informational	Chassis	•CiscoChassisChangeHeartbeatFailOldChassisAlarm
Change is detected in a Chassis being managed via the ENTITY MIB	Chassis Configuration has changed	CiscoChassisChangeEntityAlarm	Informational	Chassis	•CiscoChassisChangeEntityAlarm •ciscoChassisChangeEntityAlarm
Change is detected in a Chassis being managed via the RHINO MIB	Chassis Configuration has changed	CiscoChassisChangeRhinoAlarm	Informational	Chassis	•CiscoChassisChangeRhinoAlarm
Currently NOT Raised	Chassis is Decommissioned	CiscoChassisDecommissionedAlarm	Not Applicable	Chassis	Not Applicable
Currently NOT Raised	Chassis is Discovering	CiscoChassisDiscoveryAlarm	Not Applicable	Chassis	Not Applicable
Currently NOT Raised	Deployed Chassis does not match actual device	CiscoChassisMismatchedAlarm	Not Applicable	Chassis	Not Applicable
Currently NOT Raised	Chassis is logging Performance Data	CiscoChassisPerformanceLoggingOnAlarm	Not Applicable	Chassis	Not Applicable
Currently NOT Raised	Software Download to Chassis in progress	CiscoChassisDownloadAlarm	Not Applicable	Chassis	Not Applicable
Currently NOT Raised	Chassis is Resetting	CiscoChassisResetAlarm	Not Applicable	Chassis	•CiscoChassisDownloadAlarm •ciscoChassisResetAlarm
Currently NOT Raised	Chassis Change Heartbeat OK Alarm	CiscoChassisChangeHeartbeatFailOldChassisAlarm	Not Applicable	Chassis	Not Applicable

Module moves into Errored State	Module Operational Status is Down	CiscoModuleHeartbeatPollingFailAlarm	Major	Module	•ciscoModuleLostCommsAlarm •CiscoModuleDiscoveryLostCommsAlarm
Module moves into Normal State	Module Operational Status is Up	CiscoModuleHeartbeatPollingOKAlarm	Normal	Module	•ciscoModuleHeartbeatPollingFailAlarm •ciscoModuleLostCommsAlarm •ciscoModuleDiscoveryLostCommsAlarm •ciscoModuleLostCommsNoPollAlarm •CiscoModuleCommissioningAlarm •ciscoModulePerformanceLoggingOnAlarm •ciscoModuleMismatchedAlarm •ciscoModuleInvalidAlarm •ciscoModulePreprovisionedAlarm •ciscoModuleHeartbeatPollingOKAlarm
Currently NOT Raised	Module is determining state	CiscoModuleCommissioningAlarm	Normal	Module	•CiscoModuleCommissioningAlarm •CiscoModuleMismatchedAlarm •CiscoModuleDecommissionedAlarm •CiscoModuleDiscoveryAlarm •CiscoModuleDiscoveryLost •CommsAlarm •CiscoModuleLostCommsAlarm •CiscoModuleHeartbeatPolling •FailAlarm •CiscoModuleDownloadAlarm •CiscoModuleResetAlarm •CiscoModuleCommissioningAlarm
Module moves into Mismatched State	Deployed module does not match actual module	CiscoModuleMismatchedAlarm	Major	Module	•CiscoModuleMismatchedAlarm
Module moves into Lost Comms State	Connection to device lost	CiscoModuleLostCommsAlarm	Major	Module	•CiscoModuleDiscoveryLostCommsAlarm •ciscoModuleHeartbeatPollingFailAlarm
Module moves into Discovery Lost Comms State	Connection to device lost during Discovery	CiscoModuleDiscoveryLostCommsAlarm	Major	Module	•CiscoModuleDiscoveryAlarm •CiscoModuleLostCommsAlarm •CiscoModuleHeartbeatPollingFailAlarm
Sub Module Discovery fails	Module commissioning failed	CiscoModuleCommissionFailAlarm	Critical	Module	•CiscoModuleCommissionFailAlarm
Sub Module Discovery is successful	Module commissioning successful	CiscoModuleCommissionOKAlarm	Normal	Module	•CiscoModuleCommissionFailAlarm •CiscoModuleCommissionOKAlarm
Currently NOT Raised	Serial number of module on device has changed	CiscoModuleSerialNumberChangeAlarm	Not Applicable	Module	•CiscoModuleSerialNumberChangeAlarm
Currently NOT Raised	Module is resetting	CiscoModuleResetAlarm	Not Applicable	Module	•CiscoModuleDownloadAlarm
Currently NOT Raised	Module is Decommissioned	CiscoModuleDecommissionedAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Module is Discovering	CiscoModuleDiscoveryAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Module is logging Performance Data"	CiscoModulePerformanceLoggingOnAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Connection to device lost - Module Heartbeat Polling is Off	CiscoModuleLostCommsNoPollAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Module is Invalid	CiscoModuleInvalidAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Module is Preprovisioned"	CiscoModulePreprovisionedAlarm	Not Applicable	Module	Not Applicable
Currently NOT Raised	Software Download to Module in progress	CiscoModuleDownloadAlarm	Not Applicable	Module	Not Applicable

Interface moves into Normal State	Interface Operational Status is Up	CiscoInterfaceNormalAlarm	Normal	Interface	•CiscoInterfaceErroredAlarm •CiscoInterfaceLostCommsAlarm •CiscoInterfaceDiscoveryLostCommsAlarm •CiscoInterfaceCommissioningAlarm •LinkDown
Interface moves into Errored State	Interface Operational Status is Down	CiscoInterfaceErroredAlarm	Major	Interface	•CiscoInterfaceLostCommsAlarm •CiscoInterfaceDiscoveryLostCommsAlarm •CiscoInterfaceCommissioningAlarm •LinkDown
Interface moves into Commissioning State	Interface is determining state	CiscoInterfaceCommissioningAlarm	Informational	Interface	•CiscoInterfaceErroredAlarm •CiscoInterfaceDiscoveryLostCommsAlarm •CiscoInterfaceLostCommsAlarm •LinkDown
Interface moves into Lost Comms State	Connection to device lost	CiscoInterfaceLostCommsAlarm	Major	Interface	•CiscoInterfaceErroredAlarm •CiscoInterfaceDiscoveryLostCommsAlarm •CiscoInterfaceCommissioningAlarm •LinkDown
Interface moves into Discovery Lost Comms State	Connection to device lost during Discovery	CiscoInterfaceDiscoveryLostCommsAlarm	Major	Interface	•CiscoInterfaceErroredAlarm •CiscoInterfaceCommissioningAlarm •CiscoInterfaceLostCommsAlarm •LinkDown
Currently NOT Raised	Interface is Decommissioned	CiscoInterfaceDecommissionedAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Interface is Discovering	CiscoInterfaceDiscoveryAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Interface is logging Performance Data	CiscoInterfacePerformanceLoggingOnAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Deployed interface does not match actual	CiscoInterfaceMismatchedAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Interface is Invalid	CiscoInterfaceInvalidAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Interface is Preprovisioned	CiscoInterfacePreprovisionedAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Software Download to Interface is in progress	CiscoInterfaceDownloadAlarm	Not Applicable	Interface	Not Applicable
Currently NOT Raised	Interface is Resetting	CiscoInterfaceResetAlarm	Not Applicable	Interface	Not Applicable

¹Clears alarms of the class(es) listed.

Alarm Class Hierarchy

This section contains the following alarm class hierarchy diagrams:

• Figure 1, Base Alarm Class Hierarchy

• Figure 2, Chassis Voltage Alarm Class Hierarchy

• Figure 3, Chassis Fan Alarm Class Hierarchy

• Figure 4, Chassis Power Supply Alarm Class Hierarchy

• Figure 5, Chassis Temperature Alarm Class Hierarchy

• Figure 6, Chassis Shutdown Alarm Class Hierarchy

• Figure 7, Chassis Change Alarm Class Hierarchy

• Figure 8, Chassis State Change Alarm Class Hierarchy

• Figure 9, Module Change Alarm Class Hierarchy

• Figure 10, Interface State Change Alarm Class Hierarchy

Figure 1 Base Alarm Class Hierarchy

Figure 2 Chassis Voltage Alarm Class Hierarchy

Figure 3 Chassis Fan Alarm Class Hierarchy

Figure 4 Chassis Power Supply Alarm Class Hierarchy

Figure 5 Chassis Temperature Alarm Class Hierarchy

Figure 6 Chassis Shutdown Alarm Class Hierarchy

Figure 7 Chassis Change Alarm Class Hierarchy

Figure 8 Chassis State Change Alarm Class Hierarchy

Figure 9 Module Change Alarm Class Hierarchy

Figure 10 Interface State Change Alarm Class Hierarchy

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order annual or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can send your comments in e-mail to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.

Cisco TAC Website

The Cisco TAC website ( http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

The online TAC Case Open Tool ( http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.

For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

•iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

•Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Table Of Contents

Cisco 7000 Series Manager Version 2.1
Alarm Model Document

Contents

Trap Reception Alarms

State Behavior Alarms

Alarm Class Hierarchy

Related Documentation

Cisco EMF Documentation

Cisco 7000 Series Manager Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Copyright � 2003 Cisco Systems, Inc. All rights reserved.

Table Of Contents

Cisco 7000 Series Manager Version 2.1Alarm Model Document

Contents

Trap Reception Alarms

State Behavior Alarms

Alarm Class Hierarchy

Related Documentation

Cisco EMF Documentation

Cisco 7000 Series Manager Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Copyright � 2003 Cisco Systems, Inc. All rights reserved.

Cisco 7000 Series Manager Version 2.1
Alarm Model Document