|
|
This chapter describes how to identify faults or alarms generated by a Cisco DSLAM. When a fault occurs on a managed object in the network, CDM receives immediate notification. When you open the Cisco EMF Browser (Events) from the launchpad, the presence of an alarm is indicated by the color used to depict the network objects. The color code of an object indicates its operational status.
SNMP traps raise alarms on CDM. You can detect the source of an alarm by using the Event Browser to navigate through the network object hierarchy to the affected object. Alarms are propagated up the element hierarchy according to severity (see Table 10-2). All alarms are stored within the Event Browser, which displays both current and historical data. For further information on the Event Browser, refer to the Cisco Element Management Framework User Guide.
This chapter includes information on the following topics pertaining to Cisco DSLAM alarms:
You can detect the source of an alarm by using the Event Browser window, or Event Browser, to navigate through the network object hierarchy to the affected object. Alarms propagate up the element hierarchy according to severity. The Event Browser displays events that the system flags.
The Event Browser window is shown in Figure 10-1.

The Event Browser stores all alarms and displays current as well as historical data. You can detect the presence of an alarm by the color that Cisco EMF uses to represent network objects. The color of an object indicates its operational status. SNMP traps raise alarms on CDM.
For further information on the Event Browser, you can refer to the Cisco Element Manager Framework User Guide.
The Event Browser window displays the following information in a table format:
You can navigate directly from a single event to the affected object to perform detailed configuration activities.
To view events in the Event Browser window, follow these steps:

If you click the Events icon, you can view all alarms on all objects. Doing this opens the Query Editor window, which is shown in Figure 10-3.

Step 2 Set your query criteria on the window.
The Query Editor contains many tabs that you can use to define and refine your alarm search criteria. You can use the >> or << arrows to move the available values to the right side of the tab to select them.
Step 3 Always click Activate after you specify the values for the alarms that you want to view.
The Event Browser displays all alarms that match your query criteria.
![]() |
Note Refer to the Cisco Element Manager Framework User Guide for more detailed information about using the Query Editor. |
You can view faults on ATM Interfaces for a specified interface.
The ATM Interface Faults window appears (Figure 10-4).

Step 2 From the list boxes at the left, select the relevant chassis, card, and ATM interface. The fault information for the selected ATM interface appears to the right.
The ATM Interface Faults window contains three areas:
Table 10-1 defines the fields located in the ATM Interface Faults window.
| Field | Definition |
|---|---|
Transmitted Message Errors | The number of incorrect messages transmitted on the interface. The Incorrect Messages counter reflects any sort of incorrect information in a message. |
Detected Message Errors | The number of incorrect messages detected on the interface. The Incorrect Messages counter reflects any sort of incorrect information in a message. |
SSCOP Errored PDUs | The sum of the following errorsInvalid PDUs are defined in SSCOP and consist of PDUs with incorrect length (MAA-ERROR code U); undefined PDU type code; or not 32-bit aligned. PDUs that result in MAA error codes are discarded. |
SONET Frame Errors area | Not applicable to Cisco DSLAMs. |
DS1/E1/DS3/E3 Errors area | Not applicable to Cisco DSLAMs. |
Table 10-2 lists the possible alarm colors and the alarm severity each color represents.
| Color | Severity of Alarms |
|---|---|
Red | Critical |
Orange | Major |
Yellow | Minor |
Cyan | Warning |
Green | No alarms (Normal) |
Blue | Card decommissioned or not installed |
White | Informational |
Dark Green | Preprovisioned |
The following tables list alarms that potentially can be reported through CDM against specific objects in a Cisco Digital Subscriber Line Access Multiplexer (DSLAM) chassis.
| Severity | Description |
|---|---|
Major | A card is missing from a provisioned slot. |
| A card has been detected but it is not communicating with the system control processor. |
Minor | A card was inserted in the slot that did not match the type that was preprovisioned for the slot. |
A card is detected in this slot but it is not a valid card for this slot or is invalid for the system configuration. | |
The card reset unexpectedly. | |
Info | The card was detected (card software was loaded). |
| Severity | Description |
|---|---|
Major | Multiple fans have failed. |
One or both of the fan trays have been removed or are missing. | |
The two power units installed are not compatible. | |
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 | A single fan has failed. |
The power module is not detected by the NI-2 card. This only occurs if the power module has been provisioned. | |
The power module installed does not match the provisioned type. | |
An alarm has been detected on the station alarm 2 input. | |
An alarm has been detected on the station alarm 3 input. | |
NA | The circuit breaker on the power module has tripped due to an over-current fault. |
| Severity | Description |
Minor | 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, LOCD, or a far end LPR failure |
| Severity | Description |
Major | Loss of timing reference |
Various buffer overflows |
| Severity | ATU-C port failure. |
|---|---|
Major | Upstream rate not above Min_rate. |
| Downstream rate not above Min_rate. |
| The modem is reporting a near end LOS, LOF, LOCD, or a far end LPR failure. |
| 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 an OC-3 card) or STM1 (if this is an STM1 card) port has failed. |
| SONET: Incorrect Payload type Signal Label Mismatch. |
Minor | ATU-C port failure. |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Sep 5 09:32:34 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.