cc/td/doc/product/dsl_prod/6260
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Fault Management

Fault Management

This chapter describes the Fault Management system on the CDM used to view alarms generated by the physical entities containing the chassis, slots, modules and ports. The agent sends notifications, which are recognized by CEMF, and alarms are raised on the objects. Tables list the alarms associated with objects.

To view the objects that propagated the alarm, select the Severity On option from the Severity menu.


Note The full event description screen provides a more in-depth description of the alarm, refer to the CEMF User Guide for more information.

Viewing the Fault Generated

An alarm will generate a fault. To view a fault:

Step 1 Right click on the object that generated the alarm, a drop down list appears.

Step 2 Place the cursor on the Open Event Browser option and release the mouse button. The Event Browser screen appears:


Figure 7-1: Example Event Browser Screen


The following information appears:

Object Name

Displays the name of the object/physical entity that generated the alarm.

Time

Displays the system time when the alarm was generated.

Severity

Each alarm type defined by a vendor type employed by the system has an associated severity. This object specifies the severity of the alarm generated.

A colored square appears to the left-hand-side of the Object Name. The color of the square depends on the severity of the alarm.

An alarm used to indicate a severe, service-affecting condition has occurred and that immediate corrective action is imperative, regardless of the time of day or day of the week.
An alarm used for hardware or software conditions that indicate a serious disruption of service or the malfunctioning or failure of important hardware. These problems require the immediate attention and response of a technician to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance.
An alarm used for conditions that do not have a serious effect on service to customers or for conditions in hardware that are not essential to the operation of the system.
An alarm used to raise attention to an impending condition that can not be classified as a problem.
That part of the network setup before the service is actually provisioned.
Description

Displays the description that is associated with the alarm.


Table 7-1: Alarms associated with a DMT Card
Severity Description Notes

Minor

A module was inserted in the slot that did not match the type that was pre-provisioned for the slot

Major

Card missing from a provisioned slot

Major

A module has been detected but it is not communicating with the system control processor

>R1

Minor

A module is detected in this slot but it is not a valid module for this slot or is invalid for the system configuration


Table 7-2: Alarms associated with a Chassis
Severity Description Notes

Major

An over temperature conditions has been detected. This is measured on the NI-2 card

TBD

An alarm has been detected on the station alarm 1 input

>R1

TBD

An alarm has been detected on the station alarm 2 input

>R1

TBD

An alarm has been detected on the station alarm 3 input

>R1

Minor

A single fan has failed

The power module will force the fan fans to full speed upon seeing one or more fan faults. This will occur independent of SW.

Major

Multiple fans have failed

The power module will force the fan fans to full speed upon seeing one or more fan faults. This will occur independent of SW.

Major

One or both of the fan trays have been removed or are missing

Minor

The power module is not detected by the NI-2. This will only occur if the Power Module has been provisioned.

>R1

Minor

The power module installed does not match the provisioned type

>R1

Major

The two power units installed are not compatible

>R1

NA

The circuit breaker on the power module has tripped due to an over-current fault

this condition triggers a separate (from critical/major/minor) relay contact closure. It will not be signalled through any other means (no SNMP or LED indicators)

Major

The input voltage to one or both of the power modules is outside of its acceptable range

Major

The current through one or both of the power modules is excessive.

Major

The fan output voltage from one or both of the power modules is outside of its acceptable range

Major

One or both of the power units are reporting a fault condition. The fault is either over temp, output failure or input failure.

Major

The power supply is over its temperature limit


Table 7-3: Alarms associated with a DMT Card
Severity Description Notes

Info

Module was detected (Module software was loaded)

Minor

Module reset unexpectedly


Table 7-4: Alarms associated with an ADSL Line
Severity Description Notes

Minor

ATU-C port failure

Minor

Upstream Rate not above Min_rate

Minor

Downstream Rate not above Min_rate

Minor

The modem is reporting an near end LOS, LOF, or LOCD or a far end LPR failure.

This only occurs if the line is enabled to alarm on failures.


Table 7-5: Alarms associated with an NI2
Severity Description Notes

Major

Loss of timing reference

Various buffer overflows

>R1


Table 7-6: Alarms associated with an OC3 Port
Severity Description Notes

Critical

SONET: Loss of Cell Delineation

Minor

SONET: Incorrect Payload type Signal Label Mismatch

Critical

SONET: Path RDI received. This is equivalent to Path FERF

Critical

SONET: Path AIS received

Critical

SONET: Loss of Pointer condition

Critical

SONET: Line RDI received. This is equivalent to Line FERF

Critical

SONET: Line AIS received

Critical

SONET: Loss of Frame condition

Critical

SONET: Loss of Signal detected by SONET device

Critical

The OC3 (if this is a OC3 module) or STM1 (if this is an STM1 module) port has failed.

>R1


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Sep 15 08:30:59 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.