|
|
The CDM enables you to identify faults or alarms generated by a Cisco DSLAM. When a fault occurs on a managed object in the network, the 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 the 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 (refer to Table 6-1). All alarms are stored within the Event Browser, which displays both current and historical data. For further information on Event Browser, refer to the Cisco Element Management Framework User Guide.
This chapter includes information on the following topics pertaining to Cisco DSLAM alarms:
a. To view all alarms on all objects, click the Events application.
b. To view a specific alarm on one object, open the Map Viewer application (Viewer), right-click the object that generated the alarm, and select Tools > Open Event Browser. Only the selected object/alarm is displayed. If you wish, you can open the Query Editor from this window to modify your criteria. To access the Query Editor from the Event Browser window, click the Query Editor icon in the toolbar.
You can view faults on ATM Interfaces for a specified interface.
The ATM Interface Faults window appears (Figure 6-1).
Step 2 From the list boxes at left, select the relevant chassis, card, and ATM interface. The fault information for the selected ATM interface appears in the Fault tab at right.
The Fault tab consists of three areas: General Errors, SONET Frame Errors (not applicable to Cisco DSLAMs), and DS1 / E1 / DS3 / E3 Errors (not applicable to Cisco DSLAMs).
General Errors
The General Errors area displays the following error information:
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 errors: Invalid 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
The Sonet Frame Errors area is not applicable to Cisco DSLAMs.
DS1 / E1 / DS3 / E3 Errors
The DS1 / E1 / DS3 / E3 Errors area is not applicable to Cisco DSLAMs.
The following table 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 | Pre-Provisioned |
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 | Card 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 pre-provisioned 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. |
Minor | Card reset unexpectedly |
Info | 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. 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. |
| Severity | Description |
Minor | ATU-C port failure |
Upstream Rate not above Min_rate | |
Downstream Rate not above Min_rate | |
The modem is reporting an near end LOS, LOF, or LOCD or a far end LPR failure. |
| Severity | Description |
Major | Loss of timing reference |
Various buffer overflows |
| Severity | Description |
|---|---|
Major | ATU-C port failure |
| Upstream Rate not above Min_rate |
| Downstream Rate not above Min_rate |
| The modem is reporting an near end LOS, LOF, or 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 a OC-3 card) or STM1 (if this is an STM1 card) port has failed. |
Minor | SONET: Incorrect Payload type Signal Label Mismatch |
Posted: Sat Jul 29 06:36:17 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.