|
|
This chapter describes how to view and manage alarms and events in CDM. You can identify errors, alarms, or events that a Cisco DSLAM chassis generates. When an error occurs on a managed object in the network, CDM receives immediate notification.
This chapter includes the following sections:
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 icon on the Launchpad is shown in Figure 7-1.
The Event Browser window is shown in Figure 7-2.
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. Simple Network Management Protocol (SNMP) traps raise alarms on CDM.
For further information on the Event Browser, 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.
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. |
To view a specific alarm on one object, follow these steps:
Step 2 Choose Tools > Open Event Browser from the object menu.
Only the alarm for the object that you selected displays.
You can open the Query Editor from this window to modify your criteria.
You can get more specific information about events that display in the Event Browser window by opening the Full Event Description window, shown in Figure 7-5.
The Full Event Description window fields are described in Table 7-1.
| Field | Description |
|---|---|
Object name | Displays the name of the Cisco EMF managed object for the event. |
Severity | Displays the severity of the reported event. |
Time and Date | Displays the time and date that the system reports the event. |
Event State | Indicates whether the event is active or cleared. When the event is cleared, the Clearing Method, User Responsible for Clearing, and Clearing Time and Date fields become active. |
Management Domain | Indicates the management domain that is the source of the event. |
Communication Domain | Indicates the communications domain that is the source of the event. |
Event Description | Provides a summary description of the reported event. |
Acknowledgement User | An operator who acknowledges the alarm can use this field to enter his or her name. When other operators view that alarm, they can see that this alarm has been acknowledged and by whom. |
Acknowledgement Time and Date | An operator who acknowledges the alarm can use this field to enter the time and date of acknowledgement; when other users view that alarm, they can see when this alarm was acknowledged. |
Acknowledgement Comment | An operator who acknowledges the alarm can use this field to enter any comments; other users can see any comments about this alarm. |
Clearing Method | Identifies when the network or user cleared the event. |
User Responsible for Clearing | Displays the user name responsible for clearing the event. |
Clearing Time and Date | Indicates the time and date the event was cleared. |
Clearing Reason | Identifies the information that was entered in the Events Clearing window, which is completed when the Clear indicator is selected. |
To open the Full Event Description window, follow these steps:
Step 2 Choose Event Information > Event Information dialog from the object menu.
If the event is not cleared, the Event State field displays Active and the other fields are dimmed.
You cannot modify the displayed information.
Step 3 When the system has cleared an event, you can view the method used to clear it by clicking Clearing Event.
Step 4 Click Close to exit the Full Event Description window.
Step 5 Click Close to exit the Event Browser window.
Additionally, you can use the Cisco EMF Event Manager to complement CDM. This optional application enables you to set thresholds and monitor any supported CDM management information database (MIB) variable (that is, those variables that appear on the CDM windows).
The associated colors that indicate alarm severity are described in Table 7-2.
| Color | Severity of Alarm |
|---|---|
Red | Critical |
Orange | Major |
Yellow | Minor |
Green | Normal |
White | Informational |
Potential alarms that CDM reports against specific managed objects in a DSLAM chassis are described in this section. The alarms are categorized by module type and are organized within tables. The alarm tables list the alarms sequentially by ID number, then give the definition (alarm parameter), the level of severity, and a description of the event that caused the alarm. These tables can be useful for troubleshooting DSLAM chassis management.
|
Note Refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide for more information on events and alarms that are specific to the Cisco 6100 Series system DSLAM chassis hardware. |
Alarms that are specific to ATU-C modules are described in Table 7-3.
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SAC_SOFTWARE_ | Major | Software failed CRC1 check during download |
3 | SAC_OUT_OF_MEMORY | Critical | Application was unable to allocate memory |
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module failed to respond to system monitor |
| 1CRC = cyclic redundancy check |
Alarms that are specific for xTU-C port modems are described in Table 7-4.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | SAC_OLD_CPE_DETECT | Major | Improper version signature on CPE1 modem |
2 | MODEM_LOCKOUT | Minor | CPE modem disconnected due to session length |
3 | MODEM_IDLE_TIMEOUT | Info | CPE modem disconnected due to inactivity |
4 | CCNX_MODEM_DISCONNECTED | Info | CPE modem disconnected |
5 |
|
| Reserved |
6 | SAD_EVENT_NE_LPR_DEFECT | Minor | Near end loss of power defect |
7 | SAD_EVENT_NE_LPR_FAILURE | Major | Near end loss of power failure |
8 | SAD_EVENT_NE_LOS_DEFECT | Minor | Near end loss of signal defect |
9 | SAD_EVENT_NE_LOS_FAILURE | Major | Near end loss of signal failure |
10 | SAD_EVENT_FE_LOS_DEFECT | Minor | Far end loss of signal defect |
11 | SAD_EVENT_FE_LOS_FAILURE | Major | Far end loss of signal failure |
12 | SAD_EVENT_FE_LPR_DEFECT | Minor | Far end loss of power defect |
13 | SAD_EVENT_FE_LPR_FAILURE | Major | Far end loss of power failure |
| 1CPE = customer premises equipment |
Alarms that are specific to ATU-C DMT-2 port modems are described in Table 7-5.
| ID | Definition | Severity | Description |
|---|---|---|---|
19 | CCNX_MODEM_LATENCY_PATH_ | Major | CPE modem unable to support provisioned latency path (Interleaved/Fast) |
20 | SAD_EVENT_NE_FAST_FEC | Info | Near end fast path FEC1 |
21 | SAD_EVENT_NE_INTL_FEC | Info | Near end interleaved path FEC |
22 | SAD_EVENT_NE_FAST_CRC | Info | Near end fast path CRC error |
23 | SAD_EVENT_NE_INTL_CRC | Info | Near end fast path CRC error |
24 | SAD_EVENT_NE_SEF_DEFECT | Major | Near end loss of framing defect |
25 | SAD_EVENT_NE_SEF_FAILURE | Major | Near end loss of framing failure |
26 |
|
| Reserved for future growth |
27 |
|
| Reserved for future growth |
28 | SAD_EVENT_NE_INTL_LOD | Info | Near end interleave path LOD2 error |
29 | SAD_EVENT_NE_FAST_LOD | Info | Near end fast path LOD error |
30 | SAD_EVENT_NE_INTL_HEC | Info | Near end interleave path HEC3 error |
31 | SAD_EVENT_NE_FAST_HEC | Info | Near end fast path HEC error |
32 | SAD_EVENT_FE_FAST_FEC | Info | Far end fast path FEC |
33 | SAD_EVENT_FE_INTL_FEC | Info | Far end interleave path FEC |
34 | SAD_EVENT_FE_FAST_CRC | Info | Far end fast path CRC error |
35 | SAD_EVENT_FE_INTL_CRC | Info | Far end interleave path CRC error |
36 | SAD_EVENT_FE_SEF_DEFECT | Minor | Far end loss of framing defect |
37 | SAD_EVENT_FE_SEF_FAILURE | Major | Far end loss of framing failure |
38 |
|
| Reserved for future growth |
39 |
|
| Reserved for future growth |
40 | SAD_EVENT_FE_INTL_LOD | Info | Far end interleave path LOD error |
41 | SAD_EVENT_FE_FAST_LOD | Info | Far end fast path LOD error |
42 | SAD_EVENT_FE_INTL_HEC | Info | Far end interleave path HEC error |
43 | SAD_EVENT_FE_FAST_HEC | Info | Far end fast path HEC error |
| 1FEC = forward error correction 2LOD = loss of data 3HEC = header error control |
Alarms that are specific to the System Controller module are described in Table 7-6.
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SC_IP_MISMATCH | Minor | The IP number assigned to the 6100 is unusable |
3 | SC_SUBNET_ERROR | Minor | The subnet mask is incorrect |
4 | SC_DOWNLOAD_DONE | Info | Download to the system controller is complete |
127 |
| Critical | Loss of communication with system controller |
Alarms that are specific to the Network Interface module are described in Table 7-7.
| ID | Definition | Severity | Description |
|---|---|---|---|
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module failed to respond to the system monitor |
Alarms that are specific to the Cisco 6100/6130 Chassis are described in Table 7-8.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | MC_FAN_FAILURE | Major | A fan tray is supposed to be present, but it is not detected as present and operational. |
2 | MC_FAN_REQUIRED | Major | No fan tray has been detected or preprovisioned, but the current configuration requires one (for example, DMT-2 cards are present). |
Alarms that are specific to ATM are described in Table 7-9.
| ID | Definition | Severity | Description |
|---|---|---|---|
0 | FC_ALM_EXT_MEM_PAR_ERR | Minor | ATM chipset---External memory parity error |
1 | FC_ALM_IN_RCV_PAR_ERR | Minor | ATM chipset---Cell dropped due to ingress receive UTOPIA1 bus parity error |
2 | FC_ALM_EG_RCV_PAR_ERR | Minor | ATM chipset---Cell dropped due to egress receive side UTOPIA bus parity error |
3 | FC_ALM_UTOPIA_SYNC_ERR | Minor | ATM chipset---UTOPIA bus synchronization error detected |
4 | FC_ALM_POL_EU_ | Minor | ATM chipset---Parity error detected on policing EU2 word access |
5 | FC_ALM_VCI_SIZE_ERR | Minor | ATM chipset---Ingress VCI value above max value |
6 | FC_ALM_VPI_SIZE_ERR | Minor | ATM chipset---Ingress VPI value above max value |
7 | FC_ALM_MPHY_ | Minor | ATM chipset---Ingress UTOPIA synchronization error detected |
8 | FC_ALM_IN_FIFO_FULL | Critical | ATM chipset---Ingress cells are being dropped due to ingress capture FIFO3 full condition |
9 | FC_ALM_EG_CAP_SYNC_ERR | Minor | ATM chipset---An egress capture FIFO synchronization error is detected |
10 | FC_ALM_IN_CAP_SYNC_ERR | Minor | ATM chipset---Ingress capture FIFO synchronization error detected |
11 | FC_ALM_INSERT_SYNC_ERR | Minor | ATM chipset---Ingress insertion FIFO synchronization error |
12 | FC_ALM_FULL_MEM_ | Minor | ATM chipset---Diagnostic memory test detects memory failure |
13 | FC_ABM_SEQ_ERROR_ILL | Minor | ATM chipset---Sequence error in ingress linked list was detected |
14 | FC_ABM_PAR_ERR_ING_CELL | Minor | ATM chipset---Cell dropped due to ingress parity error |
15 | FC_ABM_SEQ_ERROR_ELL | Minor | ATM chipset---Sequence error in egress linked list detected |
16 | FC_ABM_PAR_ERR_ | Minor | ATM chipset---Parity error detected in ingress buffer RAM |
17 | FC_ABM_PAR_ERR_ | Minor | ATM chipset---Parity error detected in egress buffer RAM |
18 | FC_ABM_PAR_ERR_PRAM | Minor | ATM chipset---External pointer RAM parity error detected |
19 | FC_ABM_PRAM_ILL_ERROR | Minor | ATM chipset---Ingress linked list empty; cell processing halted until pointers become available |
20 | FC_ABM_PRAM_ELL_ERROR | Minor | ATM chipset---Egress linked list empty; cell processing halted until pointers become available |
21 | FC_ABM_PRAM_ | Minor | ATM chipset---Egress IP free list empty; cell processing halted until pointers become available |
22 | FC_ABM_ING_SYNC_ERROR | Minor | ATM chipset---Cell dropped due to ingress UTOPIA sync error |
23 | FC_ABM_EG_SYNC_ERROR | Minor | ATM chipset---Cell dropped due to egress UTOPIA sync error |
24 | FC_ABM_PTR_MEM_ | Minor | ATM chipset---Diagnostic detected external memory failure |
25 | FC_ASX_CRCERR | Minor | ATM chipset---CRC error detected on incoming cell; cell dropped |
26 | FC_ASX_IPRTOERR | Minor | ATM chipset---Input port overrun error |
27 | FC_ASX_LLERR | Minor | ATM chipset---Linked list error detected |
28 | FC_ASX_PARITY_ERR | Minor | ATM chipset---Input parity error detected; cell dropped |
29 | FC_CD_INIT_FAILURE | Minor | Cell delineator---Initialization failure |
30 | FC_SONET_INIT_FAILURE | Minor | OC-3 hardware initialization failure |
31 | NO_IPC_QUEUE_DEFINED | Minor | IPC4 does not recognize user plane queue request |
32 | FC_CD_RX_ERROR | Minor | Cell delineator---Receive error |
33 | FC_CD_TX_ERROR | Minor | Cell delineator---Transmit error |
34 | FC_CD_CFG_FAILURE | Minor | Cell delineator---Initialization failed |
35 | FC_OS_ERROR | Minor | Operating system resource allocation failed |
36 | FC_ALM_INIT_FAILURE | Minor | Fabric control init software was unable to acquire necessary resources |
37 | FC_OC3_ERROR | Minor | General fault |
38 | FC_ABM_BP_OVERRIDE | Minor | ATM chipset---Back pressure indications from switch are being overridden to prevent cell loss |
39 | FC_ATM_CNX_FAIL_ERROR | Info | Fabric control was unable to complete a requested connection |
40 | FC_ATM_ERROR | Minor | Unspecified error or problem on ATM switch |
41 | FC_ALM_HEC_ERROR | Minor | ALM HEC error |
42 | FC_SUBTEND_PORT_ | Info | Buffer overflow in the cell buffer on the subtend module |
43 | FC_SUBTEND_PORT_ | Info | Error in UTOPIA chip |
44 | FC_SUBTEND_PORT_ | Info | Subtend port ingress HEC error |
45 | FC_SUBTEND_PORT_ | Info | Subtend port ingress HEC error |
46 | FC_SUBTEND_PORT_ | Info | Parity error in cell egress path |
| 1UTOPIA = Universal Test and Operations Interface for ATM 2EU = European, or EUnet, European internet 3FIFO = first in, first out 4IPC = Interprocess Communications |
Alarms that are specific to OC-3 ports are described in Table 7-10.
| ID | Definition | Severity | Description |
|---|---|---|---|
48 | FC_OC3_LCD_FAULT | Critical | SONET1---Loss of cell delineation |
49 | FC_OC3_OCD_FAULT | Critical | SONET---Out of cell delineation |
50 | FC_OC3_FIFO_FULL | Critical | SONET---Framer FIFO overflow |
51 | FC_OC3_C2_MISMATCH | Critical | SONET---Received incorrect payload type |
52 | FC_OC3_PRDI | Critical | SONET---Path RDI2 received |
53 | FC_OC3_PAIS | Critical | SONET---Path AIS3 received |
54 | FC_OC3_APS_CHANGE | Info | SONET---Auto protection switch |
55 | FC_OC3_APS_IAB | Info | SONET---Auto protection switch byte is corrupted 3 of 12 reads |
56 | FC_OC3_ | Info | SONET---Data pointer changed |
57 | FC_OC3_LOP | Critical | SONET---Loss of pointer condition |
58 | FC_OC3_LRDI | Critical | SONET---Line RDI received |
59 | FC_OC3_LAIS | Critical | SONET---Line AIS received |
60 | FC_OC3_LOF | Critical | SONET---Loss of frame condition |
61 | FC_OC3_OOF | Critical | SONET---Out of frame condition detected |
62 | FC_OC3_LOSY | Critical | SONET---Loss of signal detected by optical transceiver |
63 | FC_OC3_LOS | Critical | SONET---Loss of signal detected by SONET device |
| 1SONET = Synchronous Optical NETwork 2RDI = remote defect indication 3AIS = alarm indicator signal |
Alarms that are specific to DS-3 and subtend ports are described in Table 7-11.
| ID | Definition | Severity | Description |
|---|---|---|---|
81 | FC_DS3_OCD | Critical | DS-3---Out of cell delineation |
82 | FC_DS3_FIFO_FULL | Minor | DS-3---Framer FIFO overflow |
83 | FC_DS3_IDLE | Critical | DS-3---Receiving idle signal |
84 | FC_DS3_RAI | Critical | DS-3---Receiving remote alarm indication |
90 | FC_DS3_YELLOW | Critical | DS-3---Receiving yellow alarm |
91 | FC_DS3_AIS | Critical | DS-3---Receiving AIS |
93 | FC_DS3_OOF | Critical | DS-3---Out of frame condition detected |
94 | FC_DS3_LIU_LOS | Critical | DS-3---Loss of signal detected at LIU1 |
95 | FC_DS3_LOS | Critical | DS-3---Loss of signal detected at framer |
96 | FC_DS3_TX_PARITY | Minor | DS-3---Parity error detected on TX UTOPIA bus |
97 | FC_DS3_RX_HEC_ERROR | Minor | DS-3---HEC error detected on RX UTOPIA bus |
99 | FC_DS3_CPAR | Minor | DS-3---Unexpected frame format |
101 | FC_DS3_PLCP_OOF | Critical | DS-3---PLCP2 out of frame condition detected |
102 | FC_DS3_PLCP_LOF | Critical | DS-3---PLCP loss of frame error detected |
112 | FC_DS3_FE_EQPT | Critical | DS-3---Far end receiving equipment failure indication |
113 | FC_DS3_FE_LOS | Critical | DS-3---Far end receiving loss of signal |
114 | FC_DS3_FE_OOF | Critical | DS-3---Far end receiving out of frame |
115 | FC_DS3_FE_AIS | Critical | DS-3---Far end receiving AIS |
116 | FC_DS3_FE_IDLE | Critical | DS-3---Far end receiving idle signal |
117 | FC_DS3_FE_NSA_EQPT | Info | DS-3---Far end receiving nonservice affecting equipment failure indication |
118 | FC_DS3_FE_ENA_LB | Info | DS-3---Far end receiving enable loopback indication |
119 | FC_DS3_FE_DIS_LB | Info | DS-3---Far end receiving disable loopback indication |
122 | MFANI_ABM_ALM0_ | Critical | ABM3 0---ATM chipset sequence error in linked list detected |
123 | MFANI_ABM_ALM1_ | Critical | ABM 1---ATM chipset sequence error in linked list detected |
124 | MFANI_ABM_ALM2_ | Critical | ABM 2---ATM chipset sequence error in linked list detected. |
125 | MFANI_ABM_ | Critical | ABM 0---Device congested; active connections exist |
126 | MFANI_ABM_ | Critical | ABM 1---Device congested; active connections exist |
127 | MFANI_ABM_ | Critical | ABM 2---Device congested; active connections exist |
| 1LIU = line interface unit 2PLCP = physical layer convergence procedure 3ABM = asynchronous balanced mode |
Alarms that are specific to the Subtend Host module are described in Table 7-12.
| ID | Definition | Severity | Description |
|---|---|---|---|
42 | FC_SUBTEND_PORT_ | Info | Buffer overflow in the cell buffer on the subtend module |
43 | FC_SUBTEND_PORT_ | Info | Error in UTOPA chip |
44 | FC_SUBTEND_PORT_ | Info | Subtend port ingress HEC error |
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module failed to respond to the system monitor |
Alarms that are specific to the LIM Controller module are described in Table 7-13.
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SCL_SOFTWARE_FAILED_CRC | Minor | Software failed CRC check during download |
3 | SCL_OUT_OF_MEMORY | Critical | Application was unable to allocate memory |
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module failed to respond to the system monitor |
Alarms that are specific to Line Interface Module ports are described in Table 7-14.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | CCNX_OLD_CPE_DETECT | Major | Improper version signature on CPE modem |
2 | LINE_LOCKOUT | Minor | Line disconnected due to session length |
3 | LINE_IDLE_TIMEOUT | Info | Line disconnected due to inactivity |
Alarms that are specific to Line Interface modules are described in Table 7-15.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | FMEVENT_LIM_DOH_CALIBRATION_ | Major | LIM was not able to perform Digital Off-Hook calibration |
3 | FMEVENT_LIM_CONNECT_FAILURE | Major | LIM was not able to connect to the switching matrix |
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module failed to respond to the system monitor |
Alarms that are specific to the software image are described in Table 7-16.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | MUM_TFTPING_FAULT | Minor | TFTP file transfer started |
2 | MUM_TFTP_SUCCESSFUL | Info | TFTP file transfer was successful |
3 | MUM_TFTP_TIMEOUT_FAULT | Minor | No data packet from server for 5 seconds after a RRQ1 or ACK2 packet was sent |
4 | MUM_FILE_NOT_FOUND_FAULT | Minor | Received something other than a DATA packet or received a out of sequence DATA packet |
5 | MUM_CHKSUM_FAIL_FAULT | Minor | TFTP file transfer failed---Checksum was incorrect |
6 | MUM_SIZE_CHK_FAULT | Minor | TFTP file transfer failed---File size was incorrect |
7 | MUM_DB_WRITE_FAULT | Minor | TFTP file transfer failed---Image could not be written to 6100 database |
8 | MUM_DB_CLEAN_FAULT | Minor | TFTP file transfer failed---Could not clean database for TFTP retry |
9 | MUM_TFTP_GENERAL _FAULT | Minor | TFTP device driver init or open failed |
| 1RRQ = relative rate queue 2ACK = acknowledgement (of packet received) |
Slot alarms are described in Table 7-17.
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | SLOT_MISMATCH_EVENT | Minor | A module was inserted in the slot that did not match the type that was pre-provisioned for the slot |
2 | SLOT_INVALID_EVENT | Minor | A module that was not valid for the slot was inserted in the slot |
3 | SLOT_NO_IMAGE_EVENT | Minor | No image exists for the type module present in the slot |
4 | SLOT_IMAGE_NOT_READY | Minor | Image for download is not ready |
5 | SLOT_DOWNLOAD_START | Info | Download for module in slot is underway |
6 | SLOT_DOWNLOAD_COMP | Info | Download for module in slot is complete |
7 | SLOT_DOWNLOAD_FAIL | Info | Image download failed for module in slot |
8 | SLOT_CURR_IMG_FAIL | Minor | Image could not be obtained for module in slot |
9 | SLOT_INVALID_XTUC_TYPE | Minor | The line encoding for the physical pool does not match the modem card |
Posted: Tue Jul 18 08:42:49 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.