|
|
This chapter explains how to diagnose and handle DS3 port and subtend port events 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.
Table 12-1 lists DS3 port and subtend port events and their IDs, definition, severity, and description. A detailed explanation of these events and corrective actions required (if any) is located in subsections 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 | 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 | 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
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 ATM switch module (ASM) 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 OC-3c 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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| 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 is likely the result in 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 ATM switch module (ASM).
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.
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 |
|---|---|---|
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 is likely the result in 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 ATM switch module (ASM).
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.
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 |
|---|---|---|
99 | FC_DS3_CPAR | 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: Unexpected frame formatEvents of this type do not affect subscriber traffic. The event is truly informational; there is no state change and therefore no assert/clear cycle.
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 |
|---|---|---|
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.
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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| ID | Event Name | Severity |
|---|---|---|
102 | FC_DS3_PLCP_LOF | 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: 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.
Wait for resyncronization.
| 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 existPermant congestion on the indicated ABM device is occurring. Therefore, no cells are flowing through the indicated Asynchronous Balanced Mode (ABM) device.
Reset the network interface (NI) 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 existPermant congestion on the indicated ABM device is occurring. Therefore, no cells are flowing through the indicated Asynchronous Balanced Mode (ABM) device.
Reset the network interface (NI) 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 existPermant congestion on the indicated ABM device is occurring. Therefore, no cells are flowing through the indicated Asynchronous Balanced Mode (ABM) device.
Reset the network interface (NI) module.
Posted: Tue Nov 16 15:42:25 PST 1999
Copyright 1989-1999©Cisco Systems Inc.