|
|
This chapter explains how to diagnose and handle OC-3c 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 9-1 lists OC-3c 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 |
|---|---|---|---|
48 | FC_OC3_LCD_FAULT | Critical | 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 RDI1 received |
53 | FC_OC3_PAIS | Critical | SONET: Path AIS2 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_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 | 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 |
| 1RDI = remote defect indication 2AIS = alarm indication signal |
|
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 |
|---|---|---|
48 | FC_OC3_LCD_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: 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 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 ATM Forum UNI specification standard as critical.
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 Loop the transmit signal back to the receiver at the network interface module to verify that the framing, section, line, and path are good.
Step 3 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 OverflowThe alarm event could indicate a problem on the network interface module that would interrupt downstream traffic flow.
Complete the following steps to clear the alarm event:
Step 2 If a problem persists, replace the network interface 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 typeTraffic flow could be prevented in either direction.
This alarm event is typically encountered at initial turn-up or when the far-end equipment is inadvertently reconfigured. Check the far end to ensure it is configured for OC-3c payload.
| 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 receivedThis alarm event indicates that the far-end equipment is having trouble with the signal being received from the near-end equipment.
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 To check the near-end signal quality, use optical test equipment or loop the transmit signal back to the receiver at the network interface module. Look for a near-end RDI alarm when the loopback is in place.
a. If an RDI alarm is present, the optical transmitter on the network interface module is defective and the module needs to be replaced.
b. If an RDI alarm is not present, check the optical fiber between the far-end and the near-end equipment for continuity.
Step 3 To check the far-end optical receiver for proper operation, use optical test equipment or loop the transmit signal back to the receiver at the network interface 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 receivedThis alarm event indicates a loss of user traffic flow.
The AIS is typically sent by the far-end equipment to indicate a defect or a far-end equipment failure. Check the far-end equipment to determine if a failure has occurred or if an alarm is being generated on the received signal. If an alarm is present on the received signal, follow diagnostic steps similar to the steps in the "SONET: Path RDI Received" section.
| ID | Event Name | Severity |
|---|---|---|
54 | FC_OC3_APS_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: Auto Protection SwitchThe auto protection switch feature is not supported in this release.
This alarm event indicates that the far-end is attempting to switch to a redundant OC-3 link. OC-3 redundancy is not supported in this software release.
| ID | Event Name | Severity |
|---|---|---|
55 | FC_OC3_APS_IAB | 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: Auto Protection Switch byte is corrupted 3 of 12 readsThe auto protection switch feature is not supported in this release.
None.
| 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. All downstream traffic is lost.
A loss of pointer condition usually indicates that the far-end equipment is malfunctioning. Complete the following steps to clear the alarm event:
Step 2 If the alarm event clears, the problem is with the far-end equipment. Troubleshoot the equipment as necessary.
Step 3 If the alarm event does not clear, replace the network interface 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 that shows a Cleared event status, which means that the alarm event has been corrected.
Step 2 To check the near-end signal quality, use optical test equipment or loop the transmit signal back to the receiver at the network interface module. Look for a near-end RDI alarm when the loopback is in place.
a. If an RDI alarm is present, the optical transmitter on the network interface module is defective and the module needs to be replaced.
b. If an RDI alarm is not present, check the optical fiber between the far-end and the near-end equipment for continuity.
Step 3 To check the far-end optical receiver for proper operation, use optical test equipment or loop the transmit signal back to the receiver at the network interface 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.
The AIS is typically sent by the far-end equipment to indicate a defect or a far-end equipment failure. Check the far-end equipment to determine if a failure has occurred or if an alarm is being generated on the received signal. If an alarm is present on the received signal, follow diagnostic steps similar to the steps in the "SONET: Line RDI Received" section.
| ID | Event Name | Severity |
|---|---|---|
60 | FC_OC3_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:
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.
Complete the following steps to clear the alarm event:
Step 2 Check the far-end equipment to ensure that it is transmitting a valid OC-3 signal.
Step 3 Check the optical fiber between the far-end and near-end equipment for continuity.
Step 4 If a problem persists, replace the network interface 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. Downstream traffic flow is interrupted.
This alarm event indicates that the receiver on the network interface module is no longer receiving an optical signal.
Complete the following steps to clear the alarm event:
Step 2 Check the optical fiber between the far-end and near-end equipment for continuity.
Step 3 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. Downstream traffic flow is interrupted.
This alarm event indicates that the receiver on the network interface module is no longer receiving an optical signal.
Complete the following steps to clear the alarm event:
Step 2 Check the optical fiber between the far-end and near-end equipment for continuity.
Step 3 If a problem persists, replace the module.
Posted: Wed May 10 13:39:55 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.