|
|
This chapter explains how to diagnose and handle OC-3c 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 11-1 lists OC-3c 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 |
|---|---|---|---|
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 | Event Name | Severity |
|---|---|---|
48 | FC_OC3_LCD_FAULT | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Loss of Cell DelineationAn event of this severity causes loss of service for more than four subscribers. Here are two examples of this type of event:
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 |
|---|---|---|
49 | FC_OC3_OCD_FAULT | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: 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 |
|---|---|---|
50 | FC_OC3_FIFO_FULL | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Framer FIFO OverflowDefined 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 |
|---|---|---|
51 | FC_OC3_C2_MISMATCH | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: received incorrect payload typeDefined 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 |
|---|---|---|
52 | FC_OC3_PRDI | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Path RDI receivedDefined 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 |
|---|---|---|
53 | FC_OC3_PAIS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Path AIS receivedDefined 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 |
|---|---|---|
54 | FC_OC3_APS_CHANGE | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Auto Protection SwitchEvents 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 |
|---|---|---|
55 | FC_OC3_APS_IAB | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Auto Protection Switch byte is corrupted 3 of 12 readsEvents 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 |
|---|---|---|
56 | FC_OC3_POINTER_CHANGE | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Data pointer changedThe event is not propagated from the module to Fault Manager, and will not be registered in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser.
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 |
|---|---|---|
57 | FC_OC3_LOP | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Loss of Pointer conditionDefined 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 |
|---|---|---|
58 | FC_OC3_LRDI | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Line RDI receivedDefined 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 |
|---|---|---|
59 | FC_OC3_LAIS | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Line AIS receivedDefined 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 |
|---|---|---|
60 | FC_OC3_LOF | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Loss of Frame conditionThe event is not propagated from the module to Fault Manager, and will not be registered in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser.
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 |
|---|---|---|
61 | FC_OC3_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:
SONET: 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 |
|---|---|---|
62 | FC_OC3_LOSY | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
SONET: Loss of Signal detected by optical transceiverDefined 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 |
|---|---|---|
63 | FC_OC3_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:
SONET: Loss of Signal detected by SONET deviceDefined 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.
Posted: Tue Nov 16 15:40:48 PST 1999
Copyright 1989-1999©Cisco Systems Inc.