Cisco 6400 Trap and Alarm Management

Viewing Cisco 6400 SCM Alarms

Event Browser Alarms

Clearing Details

Acknowledgement Details

Traps from the Cisco 6400 Network Elements

Presence Poll Failure Alarms

Alarms from Cisco 6400 SNMP Tables

Cisco 6400 Trap and Alarm Management

This chapter describes the traps and alarms used in Cisco 6400 SCM application.

Vi ewing Cisco 6400 SCM Alarms

The Cisco 6400 UAC supports a number of alarm sources, including SNMP traps and SNMP alarm tables from Cisco 6400 MIBs. Additionally, a number of event derivations can be made by the Cisco 6400 SCM.

All alarm sources of the Cisco 6400 SCM display in windows, providing an integrated fault management solution.

This section outlines the sources of Cisco 6400 SCM alarm information and shows how these sources are represented within the Cisco 6400 SCM and Cisco EMF applications.

E vent Browser Alarms

Event Browser is an application that allows you to view events flagged by the system.

Figure 7-1: Launching Event Browser

Click the Events icon in the CEMF Launchpad (see Figure 7-1) to open the Event Browser window. The Event Browser window appears (see Figure 7-2).

Figure 7-2: Event Browser Window

The Event Browser window displays the following information in a tabular format:

Time and date when an event was reported
Object name that was affected
Description and severity of the event

All events are saved within the Event Browser, which displays both current and historical data.

All network objects are color-coded reflecting their operational status. Alarms are raised up the element hierarchy according to severity. Table 7-1 identifies alarm types and their associated color codes.

Table 7-1: Alarm Color Codes

Alarm Type	Color
Critical	Red
Major	Orange
Minor	Yellow
Informational	White

You can navigate directly from a single event to the affected object to perform detailed configuration activities.

One example of a major (orange) alarm is loss of connectivity to any Cisco 6400 component. This appears as an orange alarm in the Map Viewer window. When this occurs, you should view the Event Browser window for details of the alarm.

Double-click on an event for further details of the alarm event. The Full Event Description window appears (see Figure 7-3).

Figure 7-3: F ull Event Description Window

Note When the event has not been cleared, the Event State displays Active and the Clearing Method, User Responsible for Clearing, Clearing Time and Date, and Acknowledgement Details sections are disabled. The information displayed cannot be altered. When an event has been cleared, you can view the method used to clear it by clicking the Clearing Event button.

The Full Event description window displays the following information:

Object name--Name of the Cisco EMF managed object the event was reported against
Time and Date--Time and date the event was reported
Severity--Severity of the reported event
Source Domain--Indicates from which Communications domain the event was reported
Management Domain--Indicates from which Management domain the event was reported
Event Description--Provides a brief description of the reported event
Event State--Indicates whether the event is active or cleared. When the event has been cleared, the Clearing Method, User Responsible for Clearing, and Clearing Time and Date sections become active.

Clearing Details

The Full Event description window displays the following information:

Clearing Method--Indicates when the event was cleared by the network or by a user
User Responsible for Clearing--Displays the user name responsible for clearing the event
Clearing Time and Date--Indicates the time and date the event was cleared
Reason for clearing--The information that was entered in the Events Clearing window, which is completed when the Clear indicator is selected.

Ac knowledgement Details

The Full Event description window displays the following information:

Acknowledgement User--Displays the name of the user that acknowledged the alarm
Acknowledgement Time and Date--Displays the time and date that the alarm was acknowledged
Acknowledgement Comment--Displays acknowledgement comments

Click Close to exit the Full Event Description window. Click Close to exit the Event Browser window.

Refer to the Cisco Element Management Framework User Guide for further information on Event Browser.

Traps from the Cisco 6400 Network Elements

Cisco EMF events is the primary information used by Network Operations Center (NOC) personnel for fault management tasks. Alarms (or Cisco EMF events) are generated from three sources of fault information, as follows:

1. SNMP traps

2. Trap directed polling, where alarm information is retrieved from Cisco 6400 UAC SNMP tables

3. Presence polling: SNMP polling of the Cisco 6400 hardware components to detect whether they are still functional (at least at a basic level)

The Cisco 6400 SCM software processes four traps sent from the Cisco 6400 UAC hardware:

1. Cisco6400ChassisChangeNotification trap received--Raised when a Cisco 6400 UAC component (such as an NRP) fails or is removed for various reasons (for example, a hot swap component change). This trap stimulates chassis rediscovery and ensures that the Cisco 6400 chassis map accurately reflects the status of the Cisco 6400 UAC components.

2. Cisco6400ChassisFailureNotification trap received--Raised on Power Supply Units (PSUs), fan or chassis temperature failure to show an event condition against the appropriate Cisco 6400 UAC component. This trap facilitates simpler problem diagnosis and stimulates chassis rediscovery.

3. LinkUp trap received--Signifies that the SNMPv2 entity (acting in an agent role) has detected that the ifOperStatus object for one of its communication links left the down state and changed into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.

4. LinkDown trap received--Signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.

Table 7-2 describes mapping between the alarms raised in the chassis alarm table and the traps that are dispatched from the Cisco 6400 UAC. For a simple integrated fault management solution, the SCM uses mapping to raise alarms on Cisco EMF objects.

Table 7-2: C hassis Alarm and Trap Mapping

Alarm	Trap	Meaning
coreTemp	ChassisFail	Core temperature exceeding limit
inletTemp	ChassisFail	Inlet temperature exceeding limit
totalFanFail	ChassisFail	Cisco chassis fan fault alarm
partialFanFail	ChassisFail	Cisco chassis fan partial fault alarm
fanMissing	ChassisFail	Cisco chassis fan not present alarm
pem0Fail	ChassisFail	Failure of power module 1
pem1Fail	ChassisFail	Failure of power module 2
sonetLineFail	linkUp / linkDown	SONET line failure
cardOIRAlarm	ChassisChange	Alarm card online insertion/removal (OIR) or wrong card
cardFail	ChassisChange	Card failure for non-redundant card, redundant primary card
cardPartialFail	ChassisChange	This alarm is raised when a secondary NSP is resident, and the primary NSP has detected a failure condition in the secondary NSP

P resence Poll Failure Alarms

The Cisco 6400 SCM displays "Lost Comms" alarms when SNMP polls to the affected module fail.

Alarms from Cisco 6400 SNMP Tables

The Cisco 6400 SCM uses both traps (detailed in Table 7-2) and the alarms raised in the chassis alarm table sent from the Cisco 6400 UAC to raise event conditions against the appropriate Cisco 6400 component. Alarms on the Faults tab in the Cisco 6400 Chassis Management window are represented explicitly against each object on which they occur. This allows any problems that exist involving the chassis, NSP, NRP, node line card or ATM port objects to be quickly identified by the change of color severity.When an alarm exists its color severity is either yellow (indicating a minor alarm), orange (indicating a major alarm), or red (indicating a critical alarm). Full alarm descriptions can then be viewed using Event Browser.

Alarms that occur on physical objects are raised on the objects in the Cisco 6400 SCM as they occur. Similarly, as the alarm condition on the physical object is cleared, then the alarm against the object is cleared both in the Event Browser and by the color severity.

Note In order for alarms to be raised and cleared as intended, the Cisco 6400 NSP hardware must be configured to send SNMPv2c traps to your management station.

The Cisco 6400 also stores alarm information in SNMP tables. Because Cisco EMF is based on a protocol-independent event model, these alarm conditions are presented to you in the same manner as SNMP traps.

Table 7-3 shows the alarm conditions available from the Cisco 6400 SNMP tables:

Table 7-3: SNMP Alarms

Alarm Message	Alarm Description	Relevant Objects
coreTemp	Core temperature exceeding limit	NSP
inletTemp	Inlet temperature exceeding limit	NSP
totalFanFail	Cisco chassis fan fault alarm	NSP
partialFanFail	Cisco chassis fan partial fault alarm	NSP
fanMissing	Cisco chassis fan not present alarm	NSP
pem0Fail	Cisco chassis power supply PS0 alarm	NSP
pem1Fail	Cisco chassis power supply PS1 alarm	NSP
sonetLineFail	SONET line failure	ATM Port
cardOIRAlarm	Alarm card online insertion/removal (OIR) or wrong card	NSP, NRP, LineCard
cardFail	Card failure for non-redundant card, redundant primary card	NSP, NRP, LineCard
cardPartialFail	Card partial failure alarm for redundancy secondary card failure	NSP, NRP, LineCard

Note There are other alarms that can be raised against the ATM port that currently have no corresponding message string.

These alarms are available through the Cisco EMF Event Browser and through the Cisco EMF Map Viewer. These applications serve as a single integrated fault management interface for the Cisco 6400 UAC.

Table of Contents

Cisco 6400 Trap and Alarm Management