|
|
This chapter explains how to diagnose and handle DS3 port and subtend port events that are generated by the Cisco 6100 Series system. The following information is presented for each of the events:
If none of the actions presented for the event are successful, contact the Cisco Technical Assistance Center (TAC) for additional support.
 |
Note Refer to the ViewRunner for Windows User Guide or the ViewRunner for HP OpenView User Guide for detailed information on viewing events in the ViewRunner management software. Refer to "Event Guidelines and Definitions" for detailed information on event severity guidelines and alarm event status changes. |
Table 10-1 lists DS3 port and subtend port events and their IDs, definition, severity, and description. A detailed explanation of these events and the corrective actions that are required (if any) is located in this chapter.
| 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 | Minor | DS3: Unexpected frame format |
101 | FC_DS3_PLCP_OOF | Critical | DS3: PLCP Out of Frame condition detected |
102 | FC_DS3_PLCP_LOF | Critical | DS3: PLCP Loss of Frame error detected |
112 | FC_DS3_FE_EQPT | Critical | DS3: Far end equipment failure indication |
113 | FC_DS3_FE_LOS | Critical | DS3: Far end receiving Loss of Signal |
114 | FC_DS3_FE_OOF | Critical | DS3: Far end receiving Out of Frame |
115 | FC_DS3_FE_AIS | Critical | DS3: Far end receiving AIS |
116 | FC_DS3_FE_IDLE | Critical | DS3: Far end receiving idle signal |
117 | FC_DS3_FE_NSA_EQPT | Info | DS3: Far end receiving non-service affecting equipment failure indication |
118 | FC_DS3_FE_ENA_LB | Info | DS3: Far end receiving enable loopback indication |
119 | FC_DS3_FE_DIS_LB | Info | DS3: Far end receiving disable loopback indication |
122 | MFANI_ABM_ALM0_CRC_FAIL | Critical | ABM 0: ATM Chipset---Sequence error in linked list detected |
123 | MFANI_ABM_ALM1_CRC_FAIL | Critical | ABM 1: ATM Chipset---Sequence error in linked list detected |
124 | MFANI_ABM_ALM2_CRC_FAIL | Critical | ABM 2: ATM Chipset---Sequence error in linked list 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 |
|
Note Events with an ID less than 128 are specific to the module in alarm. Events with an ID value greater than or equal to 128 are system-wide events. |
| ID | Event Name | Severity |
|---|---|---|
81 | FC_DS3_OCD | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Out of Cell DelineationDefined by the ANSI T1.107-1995 standard as critical.
Alarm events of this type are typically caused by short-term (milliseconds in duration) incidents that clear as part of the normal course of traffic management. Examples of traffic management events include the freeing of buffer space, recovery from parity errors at a higher level, and recover after a brief loss of signal.
Each of these alarm events is followed by an additional event showing a Cleared event status, meaning the alarm event has been corrected.
Step 2 If a problem persists, replace the module.
| ID | Event Name | Severity |
|---|---|---|
82 | FC_DS3_FIFO_FULL | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Framer FIFO overflowAn event of this type causes an automatic recovery attempt by the network interface module fabric control driver software. The automatic recovery should take no more than milliseconds. Service is only momentarily impaired, and recovery is possible at higher layers. The problem is likely to be transparent to the user.
This is an information event, not an alarm event. Information events do not represent a state change and therefore are not followed by a Cleared event.
Information events are typically one-time occurrences that are corrected by the module without a reset. They do not cause service degradation.
No craft action is required.
| ID | Event Name | Severity |
|---|---|---|
83 | FC_DS3_IDLE | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: receiving idle signalDefined by the ANSI T1.107-1995 standard as critical. User traffic is not being received. Far end is out of service or in a maintenance mode.
Check far-end equipment to ensure that it is not out of service or in a maintenance mode.
| ID | Event Name | Severity |
|---|---|---|
84 | FC_DS3_RAI | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: receiving Remote Alarm IndicationDefined by the ANSI T1.107-1995 standard as critical. The alarm event indicates that the far-end equipment is receiving several errored frames.
Complete the following steps to clear the alarm event:
Step 2 Complete the following actions to clear the alarm event:
a. Replace the network interface module.
b. Check the system I/O card.
c. Contact TAC.
Step 3 If the alarm event does not clear, check the far-end and the DS3 cabling that is coming from the system I/O card.
| ID | Event Name | Severity |
|---|---|---|
90 | FC_DS3_YELLOW | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: receiving Yellow AlarmDefined by the ANSI T1.107-1995 standard as critical. The alarm event indicates that the far-end equipment is receiving several errored frames.
Complete the following steps to clear the alarm event:
Step 2 Complete the following actions to clear the alarm event:
a. Replace the network interface module.
b. Check the system I/O card.
c. Contact TAC.
Step 3 If the alarm event does not clear, check the far-end and the DS3 cabling that is coming from the system I/O card.
| ID | Event Name | Severity |
|---|---|---|
91 | FC_DS3_AIS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: receiving AISDefined by the ANSI T1.107-1995 standard as critical. User traffic is not being received. Far end is out of service or in a maintenance mode.
Check far-end equipment to ensure that it is not out of service or in a maintenance mode.
| ID | Event Name | Severity |
|---|---|---|
93 | FC_DS3_OOF | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Out of Frame condition detectedDefined by the ANSI T1.107-1995 standard as critical. Receiver cannot frame to the incoming signal. The system stops passing traffic in the receive direction.
Complete the following steps to clear the alarm event:
Step 2 If the signal is good, check the wiring between the far-end and near-end equipment for continuity.
Step 3 If continuity is good, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
94 | FC_DS3_LIU_LOS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Loss of Signal detected at LIUDefined by the ANSI T1.107-1995 standard as critical. The receiver is not detecting a DS3 signal. The system stops passing traffic in the receive direction.
Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, replace the network interface module.
Step 3 If the alarm event does not clear, check the far-end equipment to ensure it is transmitting a good DS3 signal.
Step 4 If the signal is good, check the wiring between the far-end and near-end equipment for continuity.
| ID | Event Name | Severity |
|---|---|---|
95 | FC_DS3_LOS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Loss of Signal detected at framerDefined by the ANSI T1.107-1995 standard as critical. The receiver is not detecting a DS3 signal. The system stops passing traffic in the receive direction.
Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, replace the network interface module.
Step 3 If the alarm event does not clear, check the far-end equipment to ensure it is transmitting a good DS3 signal.
Step 4 If the signal is good, check the wiring between the far-end and near-end equipment for continuity.
| ID | Event Name | Severity |
|---|---|---|
96 | FC_DS3_TX_PARITY | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Parity error detected on TX UTOPIA busAn alarm event of this type will likely result in the loss of a single cell. Loss of a single cell is a transient event, affecting only one subscriber. Recovery is possible at higher layers in the protocol stack. Multiple occurrences of the alarm event are more serious and typically indicate the failure of a hardware component on the network interface module.
The term multiple occurrences is applied if several occurrences take place within a few seconds. If a problem with cell loss, and ultimately subscriber traffic throughout is suspected, service personnel should review the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser for multiple occurrences. In a future software release, multiple occurrences of events in this category will generate a higher severity alarm.
Each of these alarm events is followed by an additional event that shows a Cleared event status, which means that the alarm event has been corrected.
Step 2 If a problem persists, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
97 | FC_DS3_RX_HEC_ERROR | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: HEC error detected on RX UTOPIA busAn alarm event of this type will likely result in the loss of a single cell. Loss of a single cell is a transient event, affecting only one subscriber. Recovery is possible at higher layers in the protocol stack. Multiple occurrences of the alarm event are more serious and typically indicate the failure of a hardware component on the network interface module.
The term multiple occurrences is applied if several occurrences take place within a few seconds. If a problem with cell loss, and ultimately subscriber traffic throughout is suspected, service personnel should review the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser for multiple occurrences. In a future software release, multiple occurrences of events in this category will generate a higher severity alarm.
Each of these alarm events is followed by an additional event that shows a Cleared event status, which means that the alarm event has been corrected.
Step 2 If a problem persists, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
99 | FC_DS3_CPAR | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Unexpected frame formatThe far-end detects an unexpected frame type.
Confirm the far-end framing type.
| ID | Event Name | Severity |
|---|---|---|
101 | FC_DS3_PLCP_OOF | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: PLCP Out of Frame condition detectedAn event of this type results in the loss of all cell traffic until the PLCP convergence protocol is able to resynchronize to the beginning of the frame pointer. This condition could last for up to 5 seconds.
Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, check the far-end configuration to ensure that PLCP is enabled.
Step 3 If the alarm event does not clear, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
102 | FC_DS3_PLCP_LOF | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: PLCP Loss of Frame error detectedAn event of this type results in the loss of all cell traffic until the PLCP convergence protocol is able to resynchronize to the beginning of the frame pointer. This condition could last for up to 5 seconds.
A loss of frame error becomes an out-of-frame condition if the error exists for more than 5 seconds. If the loss of frame continues and does not become an out-of-frame condition, complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, check the far-end configuration to ensure that PLCP is enabled.
Step 3 If the alarm event does not clear, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
112 | FC_DS3_FE_EQPT | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end equipment failure indicationDefined by the ANSI T1.107-1995 standard as critical. The far-end equipment has experienced a failure. User traffic may be stopped or degraded.
No action is required.
| ID | Event Name | Severity |
|---|---|---|
113 | FC_DS3_FE_LOS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving Loss of SignalDefined by the ANSI T1.107-1995 standard as critical. This alarm event indicates that the far-end equipment is not receiving a DS3 signal.
Complete the following steps to clear the alarm event:
Step 2 Complete the following actions to clear the alarm event:
a. Replace the network interface module.
b. Contact TAC.
Step 3 If the alarm event does not clear, check the far-end equipment.
| ID | Event Name | Severity |
|---|---|---|
114 | FC_DS3_FE_OOF | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving Out of FrameDefined by the ANSI T1.107-1995 standard as critical. This alarm event indicates that the far-end equipment cannot frame to the incoming DS3 signal.
Complete the following steps to clear the alarm event:
Step 2 Complete the following actions to clear the alarm event:
a. Replace the network interface module.
b. Contact TAC.
Step 3 If the alarm event does not clear, check the far-end equipment.
| ID | Event Name | Severity |
|---|---|---|
115 | FC_DS3_FE_AIS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving AISDefined by the ANSI T1.107-1995 standard as critical. The alarm event indicates that the far-end is receiving an alarm indication signal.
Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, check to see if there are any local alarms. If there are no local alarms, replace the network interface module.
Step 3 If the alarm event does not clear, check the far-end cabling and verify that the cable type is correct.
| ID | Event Name | Severity |
|---|---|---|
116 | FC_DS3_FE_IDLE | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving idle signalDefined by the ANSI T1.107-1995 standard as critical. The alarm event indicates that the far-end is receiving an idle signal.
Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, check to see if there are any local alarms. If there are no local alarms, replace the network interface module.
Step 3 If the alarm event does not clear, check the far-end cabling and verify that the cable type is correct.
| ID | Event Name | Severity |
|---|---|---|
117 | FC_DS3_FE_NSA_EQPT | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end non-service affecting equipment failure indicationEvents of this type do not affect service, because the far-end equipment has experienced a non-service affecting problem.
Determine the nature of the failure at the far end and correct it when possible (for example, a maintenance window). No action is required at the near end.
| ID | Event Name | Severity |
|---|---|---|
118 | FC_DS3_FE_ENA_LB | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving enable loopback indicationNone.
None.
| ID | Event Name | Severity |
|---|---|---|
119 | FC_DS3_FE_DIS_LB | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
DS3: Far end receiving disable loopback indicationNone.
None.
| ID | Event Name | Severity |
|---|---|---|
122 | MFANI_ABM_ALM0_CRC_FAIL | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 0: ATM Chipset---Sequence error in linked list detectedAn event of this type causes a network interface module reset. Service is usually affected for about 45 seconds. ADSL layer 1 connections are not lost, but subscriber data traffic (ATM AAL5 cells) does not move across the switch fabric during this period.
If this alarm event continues to occur repeatedly, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
123 | MFANI_ABM_ALM1_CRC_FAIL | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 1: ATM Chipset---Sequence error in linked list detectedAn event of this type causes a network interface module reset. Service is usually affected for about 45 seconds. ADSL layer 1 connections are not lost, but subscriber data traffic (ATM AAL5 cells) does not move across the switch fabric during this period.
If this alarm event continues to occur repeatedly, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
124 | MFANI_ABM_ALM2_CRC_FAIL | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 2: ATM Chipset---Sequence error in linked list detectedAn event of this type causes a network interface module reset. Service is usually affected for about 45 seconds. ADSL layer 1 connections are not lost, but subscriber data traffic (ATM AAL5 cells) does not move across the switch fabric during this period.
If this alarm event continues to occur repeatedly, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
125 | MFANI_ABM_ALM0_CONGESTED | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 0: Device congested---Active connections existPermanent congestion on the indicated ATM Buffer Manager (ABM) device is occurring. Therefore, no cells are flowing through the indicated ABM device.
If this alarm event continues to occur repeatedly, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
126 | MFANI_ABM_ALM1_CONGESTED | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 1: Device congested---Active connections existPermanent congestion on the indicated ABM device is occurring. Therefore, no cells are flowing through the indicated ABM device.
If this alarm event continues to occur repeatedly, replace the network interface module.
| ID | Event Name | Severity |
|---|---|---|
127 | MFANI_ABM_ALM2_CONGESTED | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
ABM 2: Device congested---Active connections existPermanent congestion on the indicated ABM device is occurring. Therefore, no cells are flowing through the indicated ABM device.
If this alarm event continues to occur repeatedly, replace the network interface module.
Posted: Wed May 10 13:40:55 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.