cc/td/doc/product/dsl_prod/scm/scm221
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Cisco 6400 Trap and Alarm Management

Cisco 6400 Trap and Alarm Management

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

Viewing Cisco 6400 SCM Alarms

The Cisco 6400 Universal Access Concentrator (UAC) supports a number of alarm sources, including SNMP traps and SNMP alarm tables from Cisco 6400 MIBs. In addition, the Cisco 6400 SCM can make a number of event derivations.

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.

Event Browser Alarms

Event Browser (Figure 6-2) is a Cisco Element Manager Framework (CEMF) application that allows you to view and track network events flagged by the system. All information, including source network elements, time of event, severity, and event description are clearly displayed. More detailed information is available at the click of a mouse. Events can be sorted on severity, time, event state, network element, and other categories, so that all reports are clear and focused, and can be printed at any time.

Right-click the Events icon in the CEMF Launchpad (Figure 6-1) to open the Event Browser window.


Figure 6-1: Launching Event Browser


The Event Browser window appears (Figure 6-2).


Figure 6-2: Event Browser Window


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

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 6-1 identifies alarm types and their associated color codes.


Table 6-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 (Figure 6-3).


Figure 6-3: Full 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:

Clearing Details

The Full Event description window displays the following information:

Acknowledgement Details

The Full Event description window displays the following information:

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, which is 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:

Table 6-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 6-2: Chassis 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

Presence 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 6-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   To raise and clear alarms 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 6-3 shows the alarm conditions available from the Cisco 6400 SNMP tables:


Table 6-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.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue May 29 10:36:52 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.