|
|
This chapter describes the event severity guidelines, alarm event status changes, and the system event definitions associated with events generated by the Cisco 6100 Series system.
There are four types of events generated by the Cisco 6100 Series system and viewed in the ViewRunner management software:
The following sections describe the guidelines for each type of event.
The following are guidelines used to distinguish information events from other events:
An exception to the above guidelines is as follows.
Alarm event severity is based on guidelines set forth in TR-NWT-000057, Functional Criteria for DLC Systems. The guidelines are as follows:
Normally, an alarm event causes a service impairment or a service outage. However, some alarm events do not affect service. A service impairment typically results in a loss of end-to-end traffic for some number of subscriber connections (one to several) for a brief period of time (milliseconds to seconds, but normally less than one minute unless repeat occurrences are encountered). A service outage is the absolute loss of the ability to connect one or more subscribers.
In the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser, alarm events are followed by an additional event showing a Cleared event status, which means the alarm event is corrected.
The following are guidelines used to distinguish minor alarm events from other events:
The following is a guideline used to distinguish major alarm events from other events:
The following is a guideline used to distinguish critical alarm events from other events:
Alarm events that have been asserted by the Cisco 6100 Series system are followed by:
For example, you can clear some alarm events if the problem is caused by congestion or a single parity error. At other times, you must reset or reinsert the module generating the alarm event. In this case, the only event returned is the Event 128, "Module was detected," which clears whatever outstanding alarm events were asserted against that module.
The following tables define the entities and their relevant system events:
The following tables include the ID, definition, severity, and description of the each event. Each table is repeated in an entity chapter with detailed information including event summary, description, impact, and action.
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SAC_SOFTWARE_FAILED_CRC | Major | Software failed CRC 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 did not respond to system monitor |
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | SAC_OLD_CPE_DETECT | Critical | Improper version signature on CPE modem |
4 | CCNX_MODEM_DISCONNECTED | Info | CPE modem disconnected |
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 |
| 1The above event codes apply to all modem types. |
| ID | Definition | Severity | Description |
|---|---|---|---|
19 | CCNX_MODEM_LATENCY_PATH_NOT_AVAIL | Major | CPE modem unable to support provisioned latency path (Interleaved/Fast) |
20 | SAD_EVENT_NE_FAST_FEC | Info | Near end fast path FEC Correction |
21 | SAD_EVENT_NE_INTL_FEC | Info | Near end interleaved path FEC Correction |
22 | SAD_EVENT_NE_FAST_CRC | Info | Near end fast path CRC error |
23 | SAD_EVENT_NE_INTL_CRC | Info | Near end interleaved path CRC error |
24 | SAD_EVENT_NE_SEF_DEFECT | Minor | Near end loss of framing defect |
25 | SAD_EVENT_NE_SEF_FAILURE | Major | Near end loss of framing failure |
28 | SAD_EVENT_NE_INTL_LOD | Info | Near end interleave path LOD 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 HEC 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 correction |
33 | SAD_EVENT_FE_INTL_FEC | Info | Far end interleave path FEC correction |
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 |
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 |
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SC_IP_MISMATCH | Minor | The IP number assigned to the Cisco 6100 Series system is unusable |
3 | SC_SUBNET_ERROR | Minor | The subnet mask is incorrect |
4 | SC_DOWNLOAD_DONE | Info | Download to the SC module is complete |
127 |
| Critical | Loss of communication with SC module |
| ID | Definition | Severity | Description |
|---|---|---|---|
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module did not respond to the system monitor |
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | MC_FAN_FAILURE | Critical | A fan tray is supposed to be present, but it is not detected as present and operational |
2 | MC_FAN_REQUIRED | Critical | No fan tray has been detected or pre-provisioned, but the current configuration requires one (for example, DMT-2 cards are present) |
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | CCNX_OLD_CPE_DETECT | Critical | CPE not timer enabled |
| 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 UTOPIA 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_TIMEOUT_ERR | Minor | ATM Chipset: parity error detected on policing EU 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_PORT_OVERRUN | Minor | ATM Chipset: ingress UTOPIA synchronization error detected |
8 | FC_ALM_IN_FIFO_FULL | Minor | ATM Chipset: ingress cells are being dropped due to ingress capture FIFO 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: an ingress capture FIFO synchronization error is detected |
11 | FC_ALM_INSERT_SYNC_ERR | Minor | ATM Chipset: ingress insertion FIFO synch error |
12 | FC_ALM_FULL_MEM_TEST_FAILURE | Minor | ATM Chipset: diagnostic memory test detects memory failure |
13 | FC_ABM_SEQ_ERROR_ILL | Minor | ATM Chipset: a sequence error in the 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_ING_STORED | Minor | ATM Chipset: parity error detected in ingress buffer RAM |
17 | FC_ABM_PAR_ERR_EG_STORED | 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 halts until pointers become available |
20 | FC_ABM_PRAM_ELL_ERROR | Minor | ATM Chipset: egress linked list empty---cell processing halts until pointers become available |
21 | FC_ABM_PRAM_EIPLL_ERROR | Minor | ATM Chipset: egress IP free list empty---cell processing halts 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_TEST_FAILURE | 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-3c hardware initialization failure |
31 | NO_IPC_QUEUE_DEFINED | Minor | IPC 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: backpressure 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_BUFFER_OVERFLOW | Info | Buffer overflow in the cell buffer on the subtend module |
43 | FC_SUBTEND_PORT_UTOPIA_ERROR | Info | Error in UTOPIA chip |
44 | FC_SUBTEND_PORT_INGRESS_HEC | Info | Subtend port ingress HEC error |
45 | FC_FUBTEND_PORT_INGRESS_2_HEC | Info | Subtend port ingress HEC error |
46 | FC_SUBTEND_PORT_EGRESS_PARITY | Info | Parity error in cell egress path |
| ID | Definition | Severity | Description |
|---|---|---|---|
48 | FC_OC3_LCD_FAULT | Info | SONET: 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 RDI received |
53 | FC_OC3_PAIS | Critical | SONET: Path AIS received |
54 | FC_OC3_APS_CHANGE | Critical | SONET: Auto Protection Switch |
55 | FC_OC3_APS_IAB | Minor | SONET: Auto Protection Switch byte is corrupted 3 of 12 reads |
56 | FC_OC3_POINTER_CHANGE | 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 | Info | 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 |
| ID | Definition | Severity | Description |
|---|---|---|---|
81 | FC_DS3_OCD | Critical | DS3: Out of Cell Delineation |
82 | FC_DS3_FIFO_FULL | Minor | DS3: Framer FIFO overflow |
83 | FC_DS3_IDLE | Critical | DS3: receiving idle signal |
84 | FC_DS3_RAI | Critical | DS3: receiving Remote Alarm Indication |
90 | FC_DS3_YELLOW | Critical | DS3: receiving Yellow Alarm |
91 | FC_DS3_AIS | Critical | DS3: receiving AIS |
93 | FC_DS3_OOF | Critical | DS3: Out of Frame condition detected |
94 | FC_DS3_LIU_LOS | Critical | DS3: Loss of Signal detected at LIU |
95 | FC_DS3_LOS | Critical | DS3: Loss of Signal detected at framer |
96 | FC_DS3_TX_PARITY | Minor | DS3: Parity error detected on TX UTOPIA bus |
97 | FC_DS3_RX_HEC_ERROR | Minor | DS3: HEC error detected on RX UTOPIA bus |
99 | FC_DS3_CPAR | Info | DS3: Unexpected frame format |
101 | FC_DS3_PLCP_OOF | Critical | DS3: PLCP Out of Frame condition detected |
102 | FC_DS3_PLCP_LOF | Minor | DS3: PLCP Loss of Frame error detected |
125 | MFANI_ABM_ALM0_CONGESTED | Critical | ABM 0: Device congested---active connections exist |
126 | MFANI_ABM_ALM1_CONGESTED | Critical | ABM 1: Device congested---active connections exist |
127 | MFANI_ABM_ALM2_CONGESTED | Critical | ABM 2: Device congested---active connections exist |
| ID | Definition | Severity | Description |
|---|---|---|---|
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module did not respond to the system monitor |
42 | FC_SUBTEND_PORT_BUFFER_OVERFLOW | Info | Buffer overflow in the cell buffer on the subtend module |
43 | FC_SUBTEND_PORT_UTOPIA_ERROR | Info | Error in UTOPIA chip |
44 | FC_SUBTEND_PORT_INGRESS_HEC | Info | Subtend port ingress HEC error |
| 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 did not respond to system monitor |
| ID | Definition | Severity | Description |
|---|---|---|---|
1 | CCNX_OLD_CPE_DETECT | Critical | Improper version signature on CPE modem |
| ID | Definition | Severity | Description |
|---|---|---|---|
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 did not respond to system monitor |
| 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 RRQ or ACK 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 Cisco 6100 Series 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 |
| 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 that 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 |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Nov 16 15:32:55 PST 1999
Copyright 1989-1999©Cisco Systems Inc.