|
|
This chapter describes the Fault Management system on the Cisco Digital Subscriber Line Manager (CDM), which you use to view alarms generated by the physical entities containing the chassis, slots, modules and ports. The agent sends notifications, which are recognized by Cisco EMF, 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.
The full event description window provides a more in-depth description of the alarm, refer to the Cisco Element Management Framework User Guide for more information.
An alarm generates a fault. To view a fault:
Step 2 Right-click the object icon and select AV Tools --\> Open Event Browser from the pop-up menu. The Event Browser window appears (Figure 9-1).

The Event Browser window contains the following information:
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 of the Object Name. The color of the square depends on the severity of the alarm.
Description
Displays the description that is associated with the alarm (Table 9-1).
| Equipment with which Alarm is Associated | Severity | Alarm Description |
|---|---|---|
ADSL Line | Minor (yellow) | ATU-C port failure |
Upstream Rate not above Min_rate | ||
Downstream Rate not above Min_rate | ||
The modem is reporting a near end LOS, LOF, or LOCD or a far end LPR failure (This only occurs if the line is enabled to alarm on failures) | ||
DMT Card | Major (orange) | Card missing from a provisioned slot |
A module has been detected but it is not communicating with the system control processor (>R1) | ||
Minor (yellow) | A module was inserted in the slot that did not match the type that was pre-provisioned for the slot | |
A module is detected in this slot but it is not a valid module for this slot or is invalid for the system configuration | ||
Module reset unexpectedly | ||
Info (white) | Module was detected (module software was loaded) | |
NI-2 | Major (orange) | Loss of timing reference |
| Various buffer overflows (>R1) | |
Chassis | Major (orange) | An over temperature conditions has been detected. This is measured on the NI-2 card |
Multiple fans have failed (The power module forces the fan to full speed upon seeing one or more fan faults. This occurs independent of the software.) | ||
One or both of the fan trays have been removed or are missing | ||
The two power units installed are not compatible (>R1) | ||
The input voltage to one or both of the power modules is outside of its acceptable range | ||
The current through one or both of the power modules is excessive. | ||
The fan output voltage from one or both of the power modules is outside of its acceptable range | ||
One or both of the power units are reporting a fault condition. The fault is either over temp, output failure or input failure. | ||
The power supply is over its temperature limit | ||
Minor (yellow) | A single fan has failed (The power module forces the fan to full speed upon seeing one or more fan faults. This occurs independent of the software.) | |
The power module is not detected by the NI-2. This only occurs if the Power Module is provisioned (>R1) | ||
The power module installed does not match the provisioned type (>R1) | ||
TBD | An alarm has been detected on the station alarm 1 input (>R1) | |
An alarm has been detected on the station alarm 2input (>R1) | ||
An alarm has been detected on the station alarm 3 input (>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 is not signaled through any other means (no SNMP or LED indicators).) | |
OC-3 Port | Minor (yellow) | SONET: Incorrect Payload type Signal Label Mismatch |
Critical (red) | SONET: Loss of Cell Delineation | |
SONET: Path RDI received. This is equivalent to Path FERF | ||
SONET: Path AIS received | ||
SONET: Loss of Pointer condition | ||
SONET: Line RDI received. This is equivalent to Line FERF | ||
SONET: Line AIS received | ||
SONET: Loss of Frame condition | ||
SONET: Loss of Signal detected by SONET device | ||
The OC-3 (if this is a OC-3 module) or STM1 (if this is an STM1 module) port has failed (>R1) |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Wed May 17 12:05:13 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.