|
|
This chapter describes the alarms and error messages that can be raised on the Cisco 10000 ESR.
The Cisco 10000 ESR interface, environment, and system alarms provide feedback on the functional status of a chassis, PRE, and line cards. Furthermore, alarms and error messages alert users to less serious conditions that can degrade the performance of networks.
The following topics are addressed in this chapter:
This section describes alarm and error messages associated with the OC-12 POS line card. Where possible, the source of the error message is explained and a corrective action is suggested.
The OC-12 POS line card provides standard SONET alarms to monitor the health of OC-12 POS trunk links. Table 5-1 describes these alarms and suggests responses to each.
| Alarm Type and Severity | Alarm Symptoms | Recommendation |
|---|---|---|
SLOS Section Loss of Signal Critical | 1. Alarm messages appear in the CLI and logs. 2. Service on the SONET line card is lost. 3. If APS 1+1 redundancy is enabled, trunk service cuts over to the alternate line card. | 1. Check the fiber optic cable to make sure it is plugged in. 2. Verify that the local fiber optic cable is not damaged. 3. Make sure that the remote end of the fiber optic cable is connected, undamaged and that the remote port is configured properly. |
SLOF Section Loss of Frame Critical | 1. Alarm messages appear in the CLI and logs. 2. Service on the SONET trunk is lost. 3. If APS is enabled, trunk service cuts over to the alternate line card. | 1. Check the fiber optic cable to make sure it is plugged in. 2. Verify that the fiber is not damaged. 3. Make sure that the remote end of the fiber optic cable is connected and the router properly configured. |
LAIS Alarm Indicate Signal - Line Major | 1. This alarm is indicative of a remote problem. 2. Alarm messages appear in the CLI and logs. | 1. Verify that the remote configuration is correct. 2. Check the line status the remote end of the link. |
LRDI Remote Defect Indication - Line Major | Alarm messages appear in the CLI and logs. | RDI - Line problems arise from the remote interface. Check the remote site for alarm conditions. |
PAIS Alarm Indicate Signal - Path Minor | 1. Alarm messages appear in the CLI and logs. 2. This is sent by a site that has received LAIS. | This is sent by a site that has received LAIS. This is a minor warning, and no action needs to be taken except to monitor the far end. If the alarms are persistent, verify the interface configurations on both ends of the trunk. |
PLOP Loss of Pointer - Path Minor | Alarm messages appear in the CLI and logs. | This is an error in the data. As with the PAIS, you should monitor for more of the same messages. If the alarms are persistent, verify the interface configurations on both ends of the trunk. |
PRDI Remote Defect Indication - Path Minor | Alarm messages appear in the CLI and logs. | A PRDI alarm usually indicates a problem two sites away. If the alarm is persistent, check the alarm status of neighboring sites, beginning with the nearest neighbor. |
Table 5-2 describes a separate set of alarm messages raised when BER thresholds exceed specified limits. The BER monitors help identify signal degrading BER levels.
| Alarm Type and Severity | Alarm Symptoms | Recommendation |
|---|---|---|
TCA_B1 Threshold crossing alarm - B1 Minor | For alarm types:
Alarm messages appear in the CLI and logs. | In all cases, test the quality of the cables and connections. |
TCA_B2 Threshold crossing alarm - B2 Minor |
|
|
TCA_B3 Threshold crossing alarm - B3 Minor |
|
|
BER_SF Signal Fail condition Minor | BER_SF and BER_SD alarms result in APS cutovers. | In both cases, test the quality of the cables and connections. |
BER_SD Signal degrade condition Minor |
| For more information on signal fail (BER_SF) and signal degrade (BER_SD) alarms, refer to the APS chapter in the Cisco 10000 ESR Software Configuration Guide. These BER thresholds can be specified by the user. |
Table 5-3 describes hardware-related error messages that the OC-12 POS line card can report. It also defines the problem causing the error message and suggests a corrective action.
| Error Message | Cause of Error Message | Corrective Action |
|---|---|---|
| These alarm messages announce unrecoverable OC-12 POS line card hardware failures. | In all cases, follow this procedure: 1. Replace the OC-12 POS line card. 2. Call the Cisco TAC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 5-4 describes the software-related error messages that the OC-12 POS line card might generate. It also defines the problem causing the error message and suggests a corrective action.
| Error Message | Cause of Error Message | Corrective Action |
|---|---|---|
| The most likely cause of these messages is an incompatible version of IOS. | In both cases: 1. Type Router#show version 2. Verify that the version of IOS is a valid release for the Cisco 10000. 3. If the version is bad, get the most recent known IOS image for the Cisco 10000. 4. If the version is correct, Call the Cisco TAC. |
|
|
|
This section describes alarm and error messages that can be generated by the Channelized T3 (CT3) line card. Where possible, the source of the error message is explained and a corrective action is suggested below.
Table 5-5 describes the standard T1 alarms that can be raised on the CT3 line card.
| Alarm Type | Cause of Alarm | Corrective Action |
|---|---|---|
AIS Receive Alarm Indication Signal Major | A received alarm indication signal (AIS) indicates an alarm raised on a line upstream from the Cisco 10000. | 1. Check the status of the adjacent network element to determine if the problem is there. If the problem is not in the adjacent network element, go to Step 2. 2. Ask your T1 service provider to trace the source of the AIS signal. 3. Contact the Cisco TAC. |
LOF Loss of Frame Major | A loss of frame (LOF) condition typically happens in one of two situations: 1. The configuration settings on the port are not correct for the line. 2. The port configuration is correct but the line is experiencing other errors that result in an LOF alarm. | 1. Check to see if the framing format configured on the port matches the framing format on the line. 2. Try the other framing format and see if the alarm clears. 3. Configure a remote loopback on the affected interface, then run an unframed T1 BERT. This will help determine if there are problems on the line. |
RAI Receive Remote Alarm Indication Major | RAI indicates a problem between the C10000 T3 transmitter and the far end T3 receiver, but it may not be in the segment between the C10000 and the adjacent node. | 1. Connect an external loopback cable to the port. If there are no alarms, the problem is not on the Cisco 10000. (Refer to the "Using Loopback Tests" section) 2. Examine adjacent network elements and check for LOS or LOF alarms. |
Table 5-6 lists the error messages that the CT3 line card can generate.
| Error Message | Corrective Action |
|---|---|
| In all cases, contact the Cisco TAC for assistance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 5-7 describes the error messages associated with the gigabit Ethernet uplink line card (GE). Where possible, the source of the error message is explained and a corrective action is suggested.
| Error Message | Possible Cause | Corrective Action |
|---|---|---|
| GBIC failure. GBIC transmit failure is characterized by a steadily blinking Fail LED on the gigabit Ethernet line card. | 1. Replace the GBIC. |
| There are several types of GBICs. If the software cannot determine the type, this error is displayed. This does not mean that the GBIC will not function. | 1. If this message is accompanied by a GBIC failure, replace the GBIC with a model supported by the Cisco 10000. 2. If the GBIC is Cisco supplied, it may be faulty. Try replacing the GBIC. 3. If none of the suggestions above work, call the Cisco TAC. See the Cisco 10000 ESR Hardware Installation Guide for a list of GBIC part numbers. |
| Occurs if a GBIC (containing an EEPROM) type cannot be determined. | 1. Reinsert the GBIC. 2. Insert a new GBIC. 3. Try the GBIC in a different gigabit Ethernet line card. |
| Occurs if there is a problem with the hardware. | Call the Cisco TAC. |
%C10KGE-3-GBIC_MISSING:Interface GigabitEthernet1/0/0, Gigabit Interface Converter (GBIC) missing | Error messages appear in the logs and the CLI. | 1. Make sure the GBIC is properly inserted. 2. Replace the GBIC. |
Posted: Fri May 12 10:44:04 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.