Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide Product and Documentation Release 7.0 Last Updated: September 3, 2007 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS About this Guide Revision History xxv xxv Document Objectives Audience xxvi xxvi Document Organization xxvi Related Documentation xxvi Document Conventions xxvii Obtaining Optical Networking Information xxxiii Where to Find Safety and Warning Information xxxiii Cisco Optical Networking Product Documentation CD-ROM xxxiii Obtaining Documentation, Obtaining Support, and Security Guidelines CHAPTER 1 General Troubleshooting xxxiv 1-1 1.1 Network Troubleshooting Tests 1-2 1.1.
Contents Test the Facility Loopback Circuit Test the Electrical Cabling 1-13 1-13 1.3 Identify Points of Failure on an OC-N Circuit Path 1-14 1.3.1 Perform a Facility Loopback on a Source-Node OC-N Port 1-14 Create the Facility Loopback on the Source OC-N Port 1-14 Test the Facility Loopback Circuit 1-15 1.3.2 Perform a Cross-Connect Loopback on the Source OC-N Port 1-15 Create the Cross-Connect Loopback on the Source OC-N Port 1-16 Test the Cross-Connect Loopback Circuit 1-16 1.3.
Contents Test the Ethernet Card 1-33 1.6.3 Perform a Facility Loopback on an Intermediate-Node OC-N Port 1-33 Create a Facility Loopback on an Intermediate-Node OC-N Port 1-34 Test and Clear the OC-N Facility Loopback Circuit 1-35 Test the OC-N (Controller) Card 1-35 1.6.4 Perform a Terminal Loopback on Intermediate-Node OC-N Ports 1-36 Create a Terminal Loopback on Intermediate-Node OC-N Ports 1-37 Test and Clear the OC-N Terminal Loopback Circuit 1-38 Test the OC-N Card 1-38 1.6.
Contents Disable the VirusScan Download Scan 1-54 1.9.4 CTC Does Not Launch 1-54 Redirect the Netscape Cache to a Valid Directory 1-54 1.9.5 Sluggish CTC Operation or Login Problems 1-55 Delete the CTC Cache File Automatically 1-55 Delete the CTC Cache File Manually 1-56 1.9.6 Node Icon is Gray on CTC Network View 1-57 1.9.7 Java Runtime Environment Incompatible 1-58 Launch CTC to Correct the Core Version Build 1-58 1.9.
Contents 1.12.1 Power Supply Problems 1-73 1.12.2 Power Consumption for Node and Cards 1.12.3 Lamp Tests for Card LEDs 1-75 Verify Card LED Operation 1-75 CHAPTER 2 Alarm Troubleshooting 1-74 2-1 2.1 Alarm Index by Default Severity 2-1 2.1.1 Critical Alarms (CR) 2-2 2.1.2 Major Alarms (MJ) 2-2 2.1.3 Minor Alarms (MN) 2-3 2.1.4 Not Alarmed Conditions 2-4 2.1.5 Not Reported (NR) Conditions 2-6 2.2 Alarms and Conditions Indexed By Alphabetical Entry 2.3 Alarm Logical Objects 2-6 2-9 2.
Contents Clear the APSCINCON Alarm 2-21 2.7.11 APSCM 2-21 Clear the APSCM Alarm 2-21 2.7.12 APSCNMIS 2-22 2.7.13 APSIMP 2-22 Clear the APSIMP Alarm 2-22 2.7.14 APS-INV-PRIM 2-23 2.7.15 APSMM 2-23 Clear the APSMM Alarm 2-23 2.7.16 APS-PRIM-FAC 2-24 Clear the APS-PRIM-FAC Condition 2-24 2.7.17 APS-PRIM-SEC-MISM 2-24 Clear the APS-PRIM-SEC-MISM Alarm 2-24 2.7.18 AS-CMD 2-24 Clear the AS-CMD Condition 2-25 2.7.19 AS-MT 2-25 Clear the AS-MT Condition 2-26 2.7.20 AS-MT-OOG 2-26 2.7.
Contents 2.7.33 BAT-FAIL 2-31 Clear the BAT-FAIL Alarm 2-32 2.7.34 BKUPMEMP 2-32 Clear the BKUPMEMP Alarm 2-32 2.7.35 BLSROSYNC 2-33 2.7.36 CARLOSS (CE100T) 2-33 lear the CARLOSS (CE100T) Alarm 2-33 2.7.37 CARLOSS (EQPT) 2-35 Clear the CARLOSS (EQPT) Alarm 2-36 2.7.38 CLDRESTART 2-37 Clear the CLDRESTART Condition 2-37 2.7.39 COMIOXC 2-37 Clear the COMIOXC Alarm 2-37 2.7.40 CONTBUS-CLK-A 2-38 Clear the CONTBUS-CLK-A Alarm 2-38 2.7.41 CONTBUS-CLK-B 2-38 Clear the CONTBUS-CLK-B Alarm 2-39 2.7.
Contents 2.7.54 ELWBATVG 2-46 Clear the ELWBATVG Alarm 2-47 2.7.55 ENCAP-MISMATCH-P 2-47 Clear the ENCAP-MISMATCH-P Alarm 2-48 2.7.56 EOC 2-48 Clear the EOC Alarm 2-49 2.7.57 EOC-L 2-50 Clear the EOC-L Alarm 2-51 2.7.58 EQPT 2-51 Clear the EQPT Alarm 2-51 2.7.59 EQPT-MISS 2-52 2.7.60 ERFI-P-CONN 2-52 Clear the ERFI-P-CONN Condition 2-52 2.7.61 ERFI-P-PAYLD 2-53 Clear the ERFI-P-PAYLD Condition 2-53 2.7.62 ERFI-P-SRVR 2-53 Clear the ERFI-P-SRVR Condition 2-53 2.7.
Contents Clear the FE-DS1-SA Condition 2-59 2.7.77 FE-DS1-SNGLLOS 2-60 Clear the FE-DS1-SNGLLOS Condition 2-60 2.7.78 FE-DS3-NSA 2-60 Clear the FE-DS3-NSA Condition 2-60 2.7.79 FE-DS3-SA 2-61 Clear the FE-DS3-SA Condition 2-61 2.7.80 FE-EQPT-NSA 2-61 Clear the FE-EQPT-NSA Condition 2-61 2.7.81 FE-FRCDWKSWBK-SPAN 2-61 Clear the FE-FRCDWKSWBK-SPAN Condition 2-62 2.7.82 FE-FRCDWKSWPR-SPAN 2-62 2.7.83 FE-IDLE 2-62 Clear the FE-IDLE Condition 2-62 2.7.84 FE-LOCKOUTOFPR-SPAN 2-62 2.7.
Contents Clear the GFP-LFD Alarm 2-68 2.7.102 GFP-UP-MISMATCH 2-68 Clear the GFP-UP-MISMATCH Alarm 2-69 2.7.103 HELLO 2-69 Clear the HELLO Alarm 2-69 2.7.104 HIBATVG 2-70 Clear the HIBATVG Alarm 2-70 2.7.105 HI-LASERBIAS 2-70 Clear the HI-LASERBIAS Alarm 2-70 2.7.106 HI-LASERTEMP 2-71 Clear the HI-LASERTEMP Alarm 2-71 2.7.107 HI-RXPOWER 2-72 Clear the HI-RXPOWER Alarm 2-72 2.7.108 HITEMP 2-72 Clear the HITEMP Alarm 2-72 2.7.109 HI-TXPOWER 2-73 Clear the HI-TXPOWER Alarm 2-73 2.7.
Contents Clear the LCAS-CRC Condition 2-82 2.7.125 LCAS-RX-FAIL 2-82 0.0.1 LCAS-RX-FAIL 2-82 Clear the LCAS-RX-FAIL Condition 2-82 Clear the LCAS-RX-FAIL Condition 2-83 2.7.126 LCAS-TX-ADD 2-83 2.7.127 LCAS-TX-DNU 2-83 2.7.128 LKOUTPR-S 2-84 Clear the LKOUTPR-S Condition 2-84 2.7.129 LOA 2-84 Clear the LOA Alarm 2-84 2.7.130 LOCKOUT-REQ 2-85 Clear the LOCKOUT-REQ Condition 2-85 2.7.131 LOF (BITS) 2-85 Clear the LOF (BITS) Alarm 2-85 2.7.132 LOF (DS1) 2-86 Clear the LOF (DS1) Alarm 2-86 2.7.
Contents Clear the LOS (BITS) Alarm 2-93 2.7.146 LOS (DS1) 2-94 Clear the LOS (DS1) Alarm 2-94 2.7.147 LOS (DS3) 2-95 Clear the LOS (DS3) Alarm 2-95 2.7.148 LOS (EC1) 2-96 Clear the LOS (EC1) Alarm 2-97 2.7.149 LOS (FUDC) 2-97 Clear the LOS (FUDC) Alarm 2-98 2.7.150 LOS (OCN) 2-98 Clear the LOS (OCN) Alarm 2-99 2.7.151 LO-TXPOWER 2-100 Clear the LO-TXPOWER Alarm 2-100 2.7.152 LPBKCRS 2-100 Clear the LPBKCRS Condition 2-101 2.7.153 LPBKDS3FEAC 2-101 Clear the LPBKDS3FEAC Condition 2-101 2.7.
Contents 2.7.167 MANSWTOPRI 2-107 2.7.168 MANSWTOSEC 2-107 2.7.169 MANSWTOTHIRD 2-108 2.7.170 MANUAL-REQ-SPAN 2-108 Clear the MANUAL-REQ-SPAN Condition 2.7.171 MATECLK 2-108 Clear the MATECLK Alarm 2-109 2.7.172 MEA (EQPT) 2-109 Clear the MEA (EQPT) Alarm 2-109 2.7.173 MEA (FAN) 2-110 2.7.174 MEA (PPM) 2-110 2.7.175 MEM-GONE 2-111 2.7.176 MEM-LOW 2-111 2.7.177 MFGMEM 2-111 2.7.178 NO-CONFIG 2-111 Clear the NO-CONFIG Condition 2-112 2.7.179 NOT-AUTHENTICATED 2-112 2.7.
Contents Clear the RFI-P Condition 2-119 2.7.193 RFI-V 2-120 Clear the RFI-V Condition 2-120 2.7.194 ROLL 2-120 2.7.195 ROLL-PEND 2-121 2.7.196 RPRW 2-121 Clear the RPRW Condition 2-121 2.7.197 RUNCFG-SAVENEED 2-121 2.7.198 SD 2-122 Clear the SD (DS1, DS3) Condition 2-123 2.7.199 SD-L 2-123 Clear the SD-L Condition 2-124 2.7.200 SD-P 2-124 Clear the SD-P Condition 2-125 2.7.201 SD-V 2-125 Clear the SD-V Condition 2-125 2.7.202 SF 2-125 Clear the SF (DS1, DS3) Condition 2-126 2.7.
Contents 2.7.218 SSM-ST2 2-131 2.7.219 SSM-ST3 2-131 2.7.220 SSM-ST3E 2-131 2.7.221 SSM-ST4 2-132 2.7.222 SSM-STU 2-132 Clear the SSM-STU Condition 2-132 2.7.223 SSM-TNC 2-132 2.7.224 STS-SQUELCH-L 2-133 2.7.225 SW-MISMATCH 2-133 2.7.226 SWMTXMOD-PROT 2-133 Clear the SWMTXMOD-PROT Alarm 2-133 2.7.227 SWMTXMOD-WORK 2-134 Clear the SWMTXMOD-WORK Alarm 2-134 2.7.228 SWTOPRI 2-134 2.7.229 SWTOSEC 2-134 Clear the SWTOSEC Condition 2-134 2.7.230 SWTOTHIRD 2-135 Clear the SWTOTHIRD Condition 2-135 2.7.
Contents 2.7.243 TX-LOF 2-141 Clear the TX-LOF Condition 2-141 2.7.244 TX-RAI 2-142 Clear the TX-RAI Condition 2-142 2.7.245 UNEQ-P 2-142 Clear the UNEQ-P Alarm 2-142 2.7.246 UNEQ-V 2-144 Clear the UNEQ-V Alarm 2-144 2.7.247 VCG-DEG 2-144 Clear the VCG-DEG Condition 2-145 2.7.248 VCG-DOWN 2-145 Clear the VCG-DOWN Condition 2-145 2.7.249 VT-SQUELCH-L 2-145 2.7.250 WKSWPR 2-146 Clear the WKSWPR Condition 2-146 2.7.251 WTR 2-146 2.8 DS-1 Line Alarms 2-146 2.9 Traffic Card LED Activity 2-147 2.9.
Contents 2.10.4 Generic Signal and Circuit Procedures 2-155 Verify the Signal BER Threshold Level 2-155 Delete a Circuit 2-155 Verify or Create Node DCC Terminations 2-155 Clear an OC-N Port Facility or Terminal Loopback Circuit Clear an OC-N Port XC Loopback Circuit 2-156 Clear a DS-3 or DS-1 Port Loopback Circuit 2-156 Clear an EC-1 Port Loopback 2-157 Clear an Ethernet Card Loopback Circuit 2-157 CHAPTER 3 Transient Conditions 2-156 3-1 3.1 Transients Indexed By Alphabetical Entry 3.
Contents 3.3.24 3.3.25 3.3.26 3.3.27 3.3.28 3.3.29 3.3.30 3.3.31 3.3.32 3.3.33 3.3.34 3.3.35 CHAPTER 4 PS 3-7 PSWD-CHG-REQUIRED 3-7 RMON-ALARM 3-7 RMON-RESET 3-8 SESSION-TIME-LIMIT 3-8 SFTWDOWN-FAIL 3-8 USER-LOCKOUT 3-8 USER-LOGIN 3-8 USER-LOGOUT 3-8 WKSWBK 3-8 WKSWPR 3-9 WRMRESTART 3-9 Error Messages 4-1 INDEX Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
F I G U R E S Figure 1-1 Accessing FEAC Functions on the DS3 ports of WBE-28/WBE-84 Cards Figure 1-2 Diagram of FEAC Circuit Figure 1-3 Accessing Far End troubleshooting Functions on the WBE Cards Figure 1-4 Deleting the CTC Cache Figure 1-5 RJ-45 Pin Numbers Figure 1-6 LAN Cable Layout Figure 1-7 Cross-Over Cable Layout Figure 4-1 Error Dialog Box 1-26 1-26 1-27 1-56 1-71 1-72 1-72 4-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
Figures Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
T A B L E S Table 1-1 Restore the Node Database Table 1-2 Unable to Verify the IP Configuration of Your Windows PC Table 1-3 Browser Login Does Not Launch Java Table 1-4 Unable to Verify the NIC Connection on Your Windows PC Table 1-5 Verify Windows PC Connection to ONS 15310-CL or ONS 15310-MA (Ping) Table 1-6 Unable to Launch CTC Help After Removing Netscape Table 1-7 Unable to Change Node View to Network View Table 1-8 Browser Stalls When Downloading JAR File from Port Table 1-9 CTC Doe
Tables Table 1-32 LAN Cable Pinout Table 1-33 Cross-Over Cable Pinout 1-72 Table 1-34 Power Supply Problems 1-74 Table 1-35 Power Consumption for Node and Cards Table 1-36 Lamp Test for Optical and Electrical Card LEDs Table 2-1 ONS 15310-CL and ONS 15310-MA Critical Alarm List Table 2-2 ONS 15310-CL and ONS 15310-MA Major Alarm List 2-2 Table 2-3 ONS 15310-CL and ONS 15310-MA Minor Alarm List 2-3 Table 2-4 ONS 15310-CL and ONS 15310-MA NA Conditions List Table 2-5 ONS 15310-CL and O
About this Guide Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
About this Guide Document Objectives Date Notes 08/01/2007 Replaced TX Power High column name with OPT-HIGH in the HI-TX Power section of the Alarm Troubleshooting chapter. 09/03/2007 Added a note on AIS downstream limitations on the of terminal loopback in the General Troubleshooting chapter.
About this Guide Document Conventions • Cisco ONS SONET TL1 Command Guide Provides a full TL1 command and autonomous message set including parameters, AIDs, conditions and modifiers for the Cisco ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and ONS 15310-MA systems. • Cisco ONS SONET TL1 Reference Guide Provides general information, procedures, and errors for TL1 in the Cisco ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and ONS 15310-MA systems.
About this Guide Document Conventions Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document. Caution Means reader be careful. In this situation, the user might do something that could result in equipment damage or loss of data. Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury.
About this Guide Document Conventions Warnung WICHTIGE SICHERHEITSHINWEISE Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut.
About this Guide Document Conventions Varning! VIKTIGA SÄKERHETSANVISNINGAR Denna varningssignal signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna anordning.
About this Guide Document Conventions Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA Este símbolo de aviso significa perigo. Você se encontra em uma situação em que há risco de lesões corporais. Antes de trabalhar com qualquer equipamento, esteja ciente dos riscos que envolvem os circuitos elétricos e familiarize-se com as práticas padrão de prevenção de acidentes.
About this Guide Document Conventions Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
About this Guide Obtaining Optical Networking Information Obtaining Optical Networking Information This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation, Obtaining Support, and Security Guidelines section.
About this Guide Obtaining Documentation, Obtaining Support, and Security Guidelines Obtaining Documentation, Obtaining Support, and Security Guidelines For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.
C H A P T E R 1 General Troubleshooting Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 1 General Troubleshooting 1.1 Network Troubleshooting Tests • 1.9 CTC Operation Troubleshooting—Provides troubleshooting procedures for Cisco Transport Controller (CTC) login or operation problems. • 1.10 Circuits and Timing—Provides troubleshooting procedures for circuit creation and error reporting as well as timing reference errors and alarms. • 1.11 Fiber and Cabling—Provides troubleshooting procedures for fiber and cabling connectivity errors. • 1.
Chapter 1 General Troubleshooting 1.1.2 Terminal Loopback 1.1.2 Terminal Loopback A terminal loopback tests a circuit path as it passes through the cross-connect pathways of the node and loops back from the port where the loopback originates. A terminal loopback on an OC-N port turns the signal around before it reaches the LIU and sends it back through the card. This test verifies that the card’s cross-connect circuit paths are valid.
Chapter 1 General Troubleshooting 1.2.1 Perform a Facility Loopback on a Source-Node Port The tests in this section can be used to test DS-1, DS-3, or EC-1 circuits on a path protection. Using a series of facility loopbacks, hairpin circuits, and terminal loopbacks, the path of the circuit is traced and the possible points of failure are tested and eliminated. A logical progression of network test procedures applies to this scenario: 1. Facility loopback on the source-node port 2.
Chapter 1 General Troubleshooting 1.2.1 Perform a Facility Loopback on a Source-Node Port Step 3 Use CTC to create the facility loopback on the port being tested: a. In node view, double-click the card where you are performing the loopback, then click the appropriate tab: • Maintenance > DS1 > Loopback • Maintenance > DS3 > Loopback • Maintenance > EC1 > Loopback b. Choose OOS,MT from the Admin State column for the port being tested. c.
Chapter 1 General Troubleshooting 1.2.2 Perform a Hairpin on a Source-Node Port Test the Electrical Cabling Step 1 Replace the suspect cabling (the cables from the test set to the electrical port) with a cable known to be good. If a cable known to be good is not available, test the suspect cable with a test set. Remove the suspect cable from the electrical port and connect the cable to the Tx and Rx terminals of the test set. Run traffic to determine whether the cable is good or suspect.
Chapter 1 General Troubleshooting 1.2.2 Perform a Hairpin on a Source-Node Port c. Set the circuit Type and Size to the normal preferences, such as STS and STS1. d. Uncheck the Bidirectional check box and click Next. e. In the Circuit Source dialog box, select the same Node, Slot, Port, and Type where the test set is connected and click Next. f. In the Circuit Destination dialog box, use the same Node, Slot, Port, and Type used for the Circuit Source dialog box and click Finish.
Chapter 1 General Troubleshooting 1.2.3 Perform a Terminal Loopback on a Destination-Node Port Test the Hairpin Circuit Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit. Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating. Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin loopback circuit.
Chapter 1 General Troubleshooting 1.2.3 Perform a Terminal Loopback on a Destination-Node Port Step 4 Step 5 e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next. f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the electrical port in the destination node) and click Finish. Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Chapter 1 General Troubleshooting 1.2.4 Perform a Hairpin Test on a Destination-Node Port Step 3 Step 4 Step 5 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback: a. Double-click the 15310-CL-CTX or CTX2500 in the destination node with the terminal loopback. b.
Chapter 1 General Troubleshooting 1.2.4 Perform a Hairpin Test on a Destination-Node Port e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next. f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the port in the destination node) and click Finish. Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Chapter 1 General Troubleshooting 1.2.5 Perform a Facility Loopback on a Destination Port 1.2.5 Perform a Facility Loopback on a Destination Port The final facility loopback test is performed on the last port in the circuit— in this case the port in the destination node. Completing a successful facility loopback on this port isolates the possibility that the destination-node cabling, card, or LIU is responsible for a faulty circuit.
Chapter 1 General Troubleshooting 1.2.5 Perform a Facility Loopback on a Destination Port Test the Facility Loopback Circuit Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit. Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating. Step 3 If the test set indicates a good circuit, no further testing is necessary with the loopback circuit. a.
Chapter 1 General Troubleshooting 1.3 Identify Points of Failure on an OC-N Circuit Path d. Click Apply. e. Click Yes in the confirmation dialog box. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. 1.
Chapter 1 General Troubleshooting 1.3.2 Perform a Cross-Connect Loopback on the Source OC-N Port Step 2 Use CTC to create the facility loopback circuit on the port being tested: a. In node view, double-click the controller card (15310-CL-CTX or CTX2500) to display the card view. b. Click the Maintenance > Optical > Loopback > Port tabs. c. Choose OOS,MT from the Admin State column for the port being tested. d. Choose Facility from the Loopback Type column for the port being tested. e.
Chapter 1 General Troubleshooting 1.3.2 Perform a Cross-Connect Loopback on the Source OC-N Port Create the Cross-Connect Loopback on the Source OC-N Port Step 1 Step 2 Step 3 Step 4 Connect an optical test set to the port you are testing: a. If you just completed the “1.3.1 Perform a Facility Loopback on a Source-Node OC-N Port” procedure on page 1-14, leave the optical test set connected to the OC-N port in the source node. b.
Chapter 1 General Troubleshooting 1.3.3 Perform a Terminal Loopback on a Source-Node OC-N Port Step 4 If the test set indicates a faulty circuit, there might be a problem with the cross-connect portion of the 15310-CL-CTX or CTX2500. Complete the “1.3.3 Perform a Terminal Loopback on a Source-Node OC-N Port” procedure on page 1-17. 1.3.
Chapter 1 General Troubleshooting 1.3.4 Perform a Facility Loopback on an Intermediate-Node OC-N Port Step 5 d. Select Terminal from the Loopback Type column. e. Click Apply. f. Click Yes in the confirmation dialog box. Continue with the “Test the Terminal Loopback Circuit” procedure on page 1-18. Test the Terminal Loopback Circuit Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit. Step 2 Examine the test traffic being received by the test set.
Chapter 1 General Troubleshooting 1.3.4 Perform a Facility Loopback on an Intermediate-Node OC-N Port Create the Facility Loopback on an Intermediate-Node OC-N Port Step 1 Step 2 Step 3 Connect an optical test set to the port you are testing: a. If you just completed the “1.3.3 Perform a Terminal Loopback on a Source-Node OC-N Port” procedure on page 1-17, leave the optical test set connected to the OC-N port in the source node. b.
Chapter 1 General Troubleshooting 1.3.5 Perform a Terminal Loopback on an Intermediate-Node OC-N Port Test the Facility Loopback Circuit Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit. Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Chapter 1 General Troubleshooting 1.3.5 Perform a Terminal Loopback on an Intermediate-Node OC-N Port Step 2 Step 3 Use CTC to set up the terminal loopback circuit on the port being tested: a. Click the Circuits tab and click Create. b. Give the circuit an easily identifiable name, such as OCN1toOCN4. c. Set circuit Type and Size to the normal preferences, such as STS and STS1. d. Leave the Bidirectional check box checked and click Next. e.
Chapter 1 General Troubleshooting 1.3.6 Perform a Facility Loopback on a Destination-Node OC-N Port Step 4 Step 5 e. Click Apply. f. Click Yes in the confirmation dialog box. Clear the terminal loopback circuit: a. Click the Circuits tab. b. Choose the loopback circuit being tested. c. Click Delete. d. Click Yes in the Delete Circuits dialog box. If the test set indicates a faulty circuit, the problem might be a faulty controller card (15310-CL-CTX or CTX2500). Continue with the “1.3.
Chapter 1 General Troubleshooting 1.3.6 Perform a Facility Loopback on a Destination-Node OC-N Port It is normal for a 2.7.158 LPBKFACILITY (OCN) condition to appear during a loopback setup. The condition clears when you remove the loopback. Note Step 4 Create the facility loopback on the destination port being tested: a. Go to the node view of the destination node: • From the View menu, choose Go To Other Node. • Choose the node from the drop-down list in the Select Node dialog box and click OK.
Chapter 1 General Troubleshooting 1.3.7 Perform a Terminal Loopback on a Destination-Node OC-N Port Step 5 If the test set indicates a faulty circuit, the problem might be a faulty OC-N port. Continue with the “1.3.7 Perform a Terminal Loopback on a Destination-Node OC-N Port” procedure on page 1-24. 1.3.7 Perform a Terminal Loopback on a Destination-Node OC-N Port The terminal loopback test is performed on the destination OC-N port in the destination node.
Chapter 1 General Troubleshooting 1.4 Troubleshooting Wideband Electrical Card(WBE-28 and WBE-84 Cards) FEAC on DS3 Ports Step 5 b. In node view, double-click the controller card (15310-CL-CTX or CTX2500) with the OC-N port that requires the loopback, such as the 15310-CL-CTX in the destination-node ONS 15310-CL. c. Click the Maintenance > Optical > Loopback > Port tabs. d. Select OOS,MT from the Admin State column. e. Select Terminal from the Loopback Type column. f. Click Apply. g.
Chapter 1 General Troubleshooting 1.4.1 FEAC Send Code Figure 1-1 Accessing FEAC Functions on the DS3 ports of WBE-28/WBE-84 Cards The "far end" in FEAC refers to the equipment connected to the WBE card and not to the far end of a circuit. In Figure 1-2, if a WBE-28/WBE-84 DS3 (near-end) port is configured to send a line loop code, the code will be sent to the connected test set, not the WBE-28/WBE-84 DS3 (far-end) port.
Chapter 1 General Troubleshooting 1.4.2 WBE-28/WBE-84 Inhibit FEAC Loopback 1.4.2 WBE-28/WBE-84 Inhibit FEAC Loopback WBE-28/WBE-84 DS3 ports initiate loopbacks when they receive FEAC line loop codes. If the Inhibit FE Lbk check box is checked for a DS3 port, that port ignores any FEAC line loop codes it receives and will not loop back (return them). If you inhibit a DS3 port's far end loopback response, this DS3 port is not restricted from terminal or facility loopbacks. 1.4.
Chapter 1 General Troubleshooting 1.5.1 FEAC Send Code Note The term "Far End" refers to the equipment connected to the WBE card and not to the far end of a circuit. 1.5.1 FEAC Send Code The Send Code column on the WBE-28/WBE-84 card Maintenance tab only applies to OOS-MA,MT ports configured for ESF framing. The column lets a user select No Code (the default) or line loop code.
Chapter 1 General Troubleshooting 1.6.1 Perform a Facility Loopback on a Source-Node Ethernet Port 1.6.1 Perform a Facility Loopback on a Source-Node Ethernet Port The facility loopback test is performed on the node source port in the network circuit. Completing a successful facility loopback on this port isolates the port as a possible failure point. Note Caution Facility loopbacks require on-site personnel. Performing a loopback on an in-service circuit is service-affecting.
Chapter 1 General Troubleshooting 1.6.1 Perform a Facility Loopback on a Source-Node Ethernet Port Step 3 Step 4 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback: a. Double-click the CE100T-8 card, then click the Maintenance > Loopback tabs. b. Choose None from the Loopback Type column for the port being tested. c.
Chapter 1 General Troubleshooting 1.6.2 Perform a Terminal Loopback on a Source-Node Ethernet Port 1.6.2 Perform a Terminal Loopback on a Source-Node Ethernet Port The terminal loopback test is performed on the node source Ethernet port. To do this, you create a bidirectional circuit that starts on the node destination CE100T-8 port and loops back on node source CE100T-8 port. You then proceed with the terminal loopback test.
Chapter 1 General Troubleshooting 1.6.2 Perform a Terminal Loopback on a Source-Node Ethernet Port Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit. Note Step 5 Step 6 It is normal for the “LPKTERMINAL (CE100T)” condition on page 2-104 to appear during a loopback setup. The condition clears when you remove the loopback. Create the terminal loopback on the destination port being tested: a.
Chapter 1 General Troubleshooting 1.6.3 Perform a Facility Loopback on an Intermediate-Node OC-N Port Test the Ethernet Card Step 1 Caution Complete the “Physically Replace a Card” procedure on page 2-154 for the suspected bad card and replace it with a known-good one. Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the procedures in the “2.10.
Chapter 1 General Troubleshooting 1.6.3 Perform a Facility Loopback on an Intermediate-Node OC-N Port Create a Facility Loopback on an Intermediate-Node OC-N Port Step 1 Connect a test set to the OC-N port you are testing. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.
Chapter 1 General Troubleshooting 1.6.3 Perform a Facility Loopback on an Intermediate-Node OC-N Port Note Step 6 It is normal for the “LPBKFACILITY (OCN)” condition on page 2-103. The condition clears when you remove the loopback. Complete the “Test and Clear the OC-N Facility Loopback Circuit” procedure on page 1-35. Test and Clear the OC-N Facility Loopback Circuit Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.
Chapter 1 General Troubleshooting 1.6.4 Perform a Terminal Loopback on Intermediate-Node OC-N Ports Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447). Step 4 Complete the “Physically Replace a Card” procedure on page 2-154 for the faulty card. Step 5 Clear the facility loopback from the port: Step 6 Step 7 a.
Chapter 1 General Troubleshooting 1.6.4 Perform a Terminal Loopback on Intermediate-Node OC-N Ports Create a Terminal Loopback on Intermediate-Node OC-N Ports Step 1 Connect a test set to the 15310-CL-CTX or CTX2500 port you are testing: For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer. Note a. If you just completed the “1.6.
Chapter 1 General Troubleshooting 1.6.4 Perform a Terminal Loopback on Intermediate-Node OC-N Ports Step 6 d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port. e. Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port. f. Click Apply. g. Click Yes in the confirmation dialog box.
Chapter 1 General Troubleshooting 1.6.5 Perform a Facility Loopback on a Destination-Node Ethernet Port Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the procedures in the “2.10.1 Protection Switching, Lock Initiation, and Clearing” section on page 2-147.
Chapter 1 General Troubleshooting 1.6.5 Perform a Facility Loopback on a Destination-Node Ethernet Port Create the Facility Loopback on a Destination-Node Ethernet Port Step 1 Connect a test set to the CE100T-8 card that you are testing: For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer. Note a. If you just completed the “1.6.
Chapter 1 General Troubleshooting 1.6.5 Perform a Facility Loopback on a Destination-Node Ethernet Port Step 6 e. Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port. f. Click Apply. g. Click Yes in the confirmation dialog box. Complete the “Test and Clear the Ethernet Facility Loopback Circuit” procedure on page 1-41.
Chapter 1 General Troubleshooting 1.6.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447). Step 4 Complete the “Physically Replace a Card” procedure on page 2-154 for the faulty card. Step 5 Clear the facility loopback on the port: Step 6 Step 7 a.
Chapter 1 General Troubleshooting 1.6.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port b. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port. Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.
Chapter 1 General Troubleshooting 1.6.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port Test and Clear the Ethernet Terminal Loopback Circuit Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit. Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Chapter 1 General Troubleshooting 1.7 Restore the Database and Default Settings Step 5 Step 6 Clear the terminal loopback on the port: a. Double-click the source-node CE100T-8 card with the terminal loopback. b. Click the Maintenance > Loopback tabs. c. Select None from the Loopback Type column for the port being tested. d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested. e. Click Apply. f. Click Yes in the confirmation dialog box.
Chapter 1 General Troubleshooting 1.8.1 Windows PC System Minimum Requirements 1.8.1 Windows PC System Minimum Requirements Workstations running CTC Software R7.0 for the ONS products on Windows platforms need to have the following minimum requirements: • Pentium III or higher processor • Processor speed of at least 700 MHz • 256 MB or more of RAM • 50 MB or more of available hard disk space • 20 GB or larger hard drive 1.8.
Chapter 1 General Troubleshooting 1.8.4 Unsupported Platforms and Browsers Note JRE 1.4.2 and JRE 5.0 for Windows and Sun (Solaris, UNIX) is available on Software R7.0 product CDs. 1.8.4 Unsupported Platforms and Browsers Software R7.0 does not support the following platforms: • Windows 95 • Sun, Solaris, or UNIX 2.5 • Sun, Solaris, or UNIX 2.6 Software R7.0 does not support the following browsers and JREs: • Netscape 4.73 for Windows. • Netscape 4.76 on Sun, Solaris, or UNIX is not supported.
Chapter 1 General Troubleshooting 1.8.6 Browser Login Does Not Launch Java If the DOS window displays multiple (usually four) replies, the IP configuration is working properly. If you do not receive a reply, your IP configuration might not be properly set. Contact your network administrator for instructions to correct the IP configuration of your Windows PC. 1.8.
Chapter 1 General Troubleshooting 1.8.7 Unable to Verify the NIC Connection on Your Windows PC Reconfigure the Browser Step 1 From the Windows Start Menu, launch your browser application. Step 2 If you are using Netscape Navigator: Step 3 a. From the Netscape Navigator menu bar, click the Edit > Preferences menus. b. In the Preferences window, click the Advanced > Proxies categories. c. In the Proxies window, click the Direct connection to the Internet check box and click OK. d.
Chapter 1 General Troubleshooting 1.8.8 Verify Windows PC Connection to the Node (Ping) Table 1-4 Unable to Verify the NIC Connection on Your Windows PC Possible Problem Solution The CAT-5 cable is not plugged in properly. Confirm that both ends of the cable are properly inserted. If the cable is not fully inserted due to a broken locking clip, the cable should be replaced. The CAT-5 cable is damaged. Ensure that the cable is in good condition. If in doubt, use a cable known to be good.
Chapter 1 General Troubleshooting 1.9 CTC Operation Troubleshooting Ping the ONS 15310-CL or ONS 15310-MA Step 1 Step 2 Open the command prompt: a. If you are using a Microsoft Windows operating system, from the Start Menu choose Run, type command prompt in the Open field of the Run dialog box, and click OK. b. If you are using a Sun, Solaris, or UNIX operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
Chapter 1 General Troubleshooting 1.9.2 Unable to Change Node View to Network View Set Internet Explorer as the Default Browser for CTC Step 1 Open the Internet Explorer browser. Step 2 From the menu bar, click Tools > Internet Options. The Internet Options window appears. Step 3 In the Internet Options window, click the Programs tab. Step 4 Click the Internet Explorer should check to see whether it is the default browser check box. Step 5 Click OK.
Chapter 1 General Troubleshooting 1.9.3 Browser Stalls When Downloading CTC JAR Files from port Step 4 Click the Environment Variables button to open the Environment Variables window. Step 5 Click the New button under the System variables field. Step 6 Type CTC_HEAP in the Variable Name field. Step 7 Type 512 in the Variable Value field, and then click the OK button to create the variable. Step 8 Again, click the New button under the System variables field.
Chapter 1 General Troubleshooting 1.9.4 CTC Does Not Launch Disable the VirusScan Download Scan Step 1 From the Windows start menu, choose Programs > Network Associates > VirusScan Console. Step 2 Double-click the VShield icon listed in the VirusScan Console dialog box. Step 3 Click Configure on the lower part of the Task Properties window. Step 4 Click the Download Scan icon on the left of the System Scan Properties dialog box. Step 5 Uncheck the Enable Internet download scanning check box.
Chapter 1 General Troubleshooting 1.9.5 Sluggish CTC Operation or Login Problems 1.9.5 Sluggish CTC Operation or Login Problems Symptom You experience sluggish CTC operation or have problems logging into CTC. Table 1-10 describes the potential cause of the symptom and the solution. Table 1-10 Sluggish CTC Operation or Login Problems Possible Problem Solution The CTC cache file might be corrupted or might need to be replaced. Delete the CTC cache file.
Chapter 1 General Troubleshooting 1.9.5 Sluggish CTC Operation or Login Problems Figure 1-4 Deleting the CTC Cache Delete the CTC Cache File Manually Caution All running sessions of CTC must be halted before deleting the CTC cache. Deleting the CTC cache might cause any CTC running on this system to behave in an unexpected manner. Step 1 To delete the JAR files manually, from the Windows Start menu choose Search > For Files or Folders. Step 2 Enter ctc*.jar or cms*.
Chapter 1 General Troubleshooting 1.9.6 Node Icon is Gray on CTC Network View 1.9.6 Node Icon is Gray on CTC Network View Symptom The CTC network view shows one or more node icons as gray in color and without a node name. Table 1-11 describes the potential causes of the symptom and the solutions. Table 1-11 Node Icon is Gray on CTC Network View Possible Problem Solution Different CTC releases are Correct the core version build as described in the “1.9.8 Different CTC not recognizing each other.
Chapter 1 General Troubleshooting 1.9.7 Java Runtime Environment Incompatible 1.9.7 Java Runtime Environment Incompatible Symptom The CTC application does not run properly. Table 1-12 describes the potential cause of the symptom and the solution. Table 1-12 Note Java Runtime Environment Incompatible Possible Problem Solution The compatible Java 2 JRE is not installed.
Chapter 1 General Troubleshooting 1.9.8 Different CTC Releases Do Not Recognize Each Other 1.9.8 Different CTC Releases Do Not Recognize Each Other Symptom Different CTC releases on the same network do not recognize each other. Table 1-13 describes the potential cause of the symptom and the solution.
Chapter 1 General Troubleshooting 1.9.9 Username or Password Does Not Match the Port Information 1.9.9 Username or Password Does Not Match the Port Information Symptom A mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm. Table 1-14 describes the potential causes of the symptom and the solutions. Table 1-14 Username or Password Does Not Match the Port Information Possible Problem Solution The username or password entered does not match the information stored in the port.
Chapter 1 General Troubleshooting 1.9.11 No IP Connectivity Exists Between Nodes Reset the ONS 15310-CL or ONS 15310-MA Password Note To complete this procedure, you must be on site and have IP connectivity to the node. Step 1 At the ONS 15310-CL or ONS 15310-MA shelf, locate the recessed button labeled LAMP TEST on the front of the unit. Step 2 Using a pen tip or something of similar size, press in and hold down the recessed button labelled LAMP TEST for five seconds.
Chapter 1 General Troubleshooting 1.9.12 DCC Connection Lost 1.9.12 DCC Connection Lost Symptom The node is usually accompanied by alarms and the nodes in the network view have a gray icon. Table 1-17 describes the potential cause of the symptom and the solution. Table 1-17 DCC Connection Lost Possible Problem Solution A lost DCC connection Usually, this condition is accompanied by an EOC alarm. Clear the EOC alarm and verify the DCC connection as described in the “EOC” alarm on page 2-48. 1.9.
Chapter 1 General Troubleshooting 1.9.14 Calculate and Design IP Subnets 1.9.14 Calculate and Design IP Subnets Symptom You cannot calculate or design IP subnets on the ONS 15310-CL or ONS 15310-MA. Table 1-19 describes the potential cause of the symptom and the solution. Table 1-19 Calculate and Design IP Subnets Possible Problem Solution The IP capabilities of the ONS 15310-CL and ONS 15310-MA require specific calculations to properly design IP subnets.
Chapter 1 General Troubleshooting 1.10.2 Circuits Remain in PARTIAL Status Table 1-20 Circuit in Partial Status (continued) Possible Problem Solution During an automatic transition, some path-level defects and/or alarms were detected on the circuit. Determine which node in the circuit is not changing to the desired state. Refer to the “View the State of Circuit Nodes” procedure on page 1-64.
Chapter 1 General Troubleshooting 1.10.3 AIS-V on Unused 15310-CL-CTX Card VT Circuits 1.10.3 AIS-V on Unused 15310-CL-CTX Card VT Circuits Symptom An incomplete circuit path causes an alarm indications signal (AIS). Table 1-22 describes the potential cause of the symptom and the solution. Table 1-22 AIS-V on Unused 15310-CL-CTX Card VT Circuits Possible Problem Solution The port on the reporting node is in-service but a node upstream on the circuit does not have an OC-N port in service.
Chapter 1 General Troubleshooting 1.10.4 Circuit Creation Error with VT1.5 Circuit 1.10.4 Circuit Creation Error with VT1.5 Circuit Symptom You might receive an “Error while finishing circuit creation. Unable to provision circuit. Unable to create connection object at node-name” message when trying to create a VT1.5 circuit in CTC. Table 1-23 describes the potential causes of the symptom and the solutions. Table 1-23 Circuit Creation Error with VT1.
Chapter 1 General Troubleshooting 1.10.6 ONS 15310-CL or ONS 15310-MA Switches Timing Reference 1.10.6 ONS 15310-CL or ONS 15310-MA Switches Timing Reference Symptom Timing references switch when one or more problems occur. Table 1-25 describes the potential causes of the symptom and the solutions.
Chapter 1 General Troubleshooting 1.10.8 Free-Running Synchronization Mode 1.10.8 Free-Running Synchronization Mode Symptom The clock is running at a different frequency than normal and the free-running synchronization(2.7.96 FRNGSYNC) alarm appears. Table 1-27 describes the potential cause of the symptom and the solution. Table 1-27 Free-Running Synchronization Mode Possible Problem Solution No reliable reference input is available.
Chapter 1 General Troubleshooting 1.11 Fiber and Cabling 1.11 Fiber and Cabling This section explains problems typically caused by cabling connectivity errors. It also includes instructions for crimping CAT-5 cable and lists the optical fiber connectivity levels. 1.11.1 Bit Errors Appear for a Traffic Card Symptom A traffic card has multiple bit errors. Table 1-30 describes the potential cause of the symptom and the solution.
Chapter 1 General Troubleshooting 1.11.2 Faulty Fiber-Optic Connections Warning Class 1 laser product. Statement 1008 Warning Laser radiation presents an invisible hazard, so personnel should avoid exposure to the laser beam. Personnel must be qualified in laser safety procedures and must use proper eye protection before working on this equipment.
Chapter 1 General Troubleshooting 1.11.2 Faulty Fiber-Optic Connections Step 5 Tip If no power level shows on the fiber, the fiber is bad or the transmitter on the optical port failed. Complete the following steps: a. Check that the Tx and Rx fibers are not reversed. LOS and EOC alarms normally accompany reversed Tx and Rx fibers. Switching reversed Tx and Rx fibers clears the alarms and restores the signal. b. Clean or replace the fiber patchcords.
Chapter 1 General Troubleshooting 1.11.2 Faulty Fiber-Optic Connections LAN Cable Layout 1 2 3 4 1 2 3 4 5 6 5 6 7 8 7 8 55415 Figure 1-6 Table 1-32 shows LAN cable pinouts.
Chapter 1 General Troubleshooting 1.12 Power and LED Tests Table 1-33 Note Cross-Over Cable Pinout (continued) Pin Color Pair Name Pin 3 White/green 3 Receive Data + 1 4 Blue 1 — 4 5 White/blue 1 — 5 6 Green 3 Receive Data – 2 7 White/brown 4 — 7 8 Brown 4 — 8 Odd-numbered pins always connect to a white wire with a colored stripe. 1.12 Power and LED Tests This section provides symptoms and solutions for power supply problems, power consumption, and LED indicators.
Chapter 1 General Troubleshooting 1.12.2 Power Consumption for Node and Cards Table 1-34 Power Supply Problems Possible Problem Solution Loss of power or low voltage See Chapter 2, “Alarm Troubleshooting,” for information about specific power alarms. Procedures for installing power supply and cables are located in the “Install Hardware” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.
Chapter 1 General Troubleshooting 1.12.3 Lamp Tests for Card LEDs 1.12.3 Lamp Tests for Card LEDs Symptom Optical (OC-N) ports LEDs do not light, or you are unsure whether the LEDs are working properly. The LED lamp test determines whether card-level LEDs are operational. For optical ports, this test also causes port-level LEDs to turn on. For Ethernet cards, only card-level LEDs light.
Chapter 1 1.12.3 Lamp Tests for Card LEDs Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
C H A P T E R 2 Alarm Troubleshooting Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 2 Alarm Troubleshooting 2.1.1 Critical Alarms (CR) Note The CTC default alarm profile in some cases contains two severities for one alarm (for example, Major/Minor [MJ/MN]). The default severity comes first (in this example, MJ), but the alarm can be demoted to the second severity in the presence of a higher-ranking alarm. This is in accordance with Telcordia GR-474-CORE. 2.1.1 Critical Alarms (CR) Table 2-1 alphabetically lists ONS 15310-CL and ONS 15310-MA Critical (CR) alarms.
Chapter 2 Alarm Troubleshooting 2.1.3 Minor Alarms (MN) Table 2-2 ONS 15310-CL and ONS 15310-MA Major Alarm List (continued) CARLOSS (EQPT) HIBATVG (ONS 15310-CL) SQM (VT-TERM) DBOSYNC (NE) INVMACADR (BPLANE) SYNCPRI (NE-SREF) DUP-SHELF-ID (SHELF) LOF (DS1) SYSBOOT (NE) EHIBATVG (PWR) LOM (VT-TERM) TIM-V (VT-TERM) ELWBATVG (PWR) LOP-V (VT-MON) TPTFAIL (CE100T) E-W-MISMATCH (OCN) LOP-V (VT-TERM) UNEQ-V (VT-MON) EXTRA-TRAF-PREEMPT (OCN) LOS (DS1) UNEQ-V (VT-TERM) 2.1.
Chapter 2 Alarm Troubleshooting 2.1.4 Not Alarmed Conditions Table 2-3 ONS 15310-CL and ONS 15310-MA Minor Alarm List (continued) FEPRLF (OCN) LOS (BITS) TIM-P (STSMON) HI-LASERBIAS (EQPT) — — 2.1.4 Not Alarmed Conditions Table 2-4 alphabetically lists ONS 15310-CL and ONS 15310-MA Not Alarmed (NA) conditions.
Chapter 2 Alarm Troubleshooting 2.1.
Chapter 2 Alarm Troubleshooting 2.1.5 Not Reported (NR) Conditions Table 2-4 ONS 15310-CL and ONS 15310-MA NA Conditions List (continued) FSTSYNC (NE-SREF) SF (DS1) WTR (EQPT) FULLPASSTHR-BI (OCN) SF (DS3) WTR (OCN) HELLO (OCN) SF-L (EC1) WTR (STSMON) HLDOVRSYNC (NE-SREF) SF-L (OCN) WTR (VT-MON) INC-ISD (DS3) SF-P (STSMON) — 2.1.5 Not Reported (NR) Conditions Table 2-2 alphabetically lists ONS 15310-CL and ONS 15310-MA Major (MJ) alarms.
Chapter 2 Alarm Troubleshooting 2.
Chapter 2 Alarm Troubleshooting 2.
Chapter 2 Alarm Troubleshooting 2.3 Alarm Logical Objects 2.3 Alarm Logical Objects The CTC alarm profile list organizes all alarms and conditions according to the logical objects they are raised against. These logical objects represent physical objects such as cards, logical objects such as circuits, or transport and signal monitoring entities such as the SONET overhead bits. One alarm can appear in multiple entries. It can be raised against multiple objects.
Chapter 2 Alarm Troubleshooting 2.4 Alarm List by Logical Object Type Table 2-7 Alarm Logical Object Type Definitions (continued) Type Definition STSTRM STS alarm detection at termination (downstream from the cross-connect). VCG Virtual concatenation group. VT-MON VT1 alarm detection at the monitor point (upstream from the cross-connect). VT-TERM VT1 alarm detection at termination (downstream from the cross-connect). 2.
Chapter 2 Alarm Troubleshooting 2.
Chapter 2 Alarm Troubleshooting 2.
Chapter 2 Alarm Troubleshooting 2.
Chapter 2 Alarm Troubleshooting 2.5 Trouble Notifications 2.5 Trouble Notifications The ONS 15310-CL and ONS 15310-MA systems report trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253-CORE, and graphical user interface (GUI) state indicators. These notifications are described in the following sections. The ONS 15310-CL and ONS 15310-MA use standard Telcordia categories to characterize levels of trouble.
Chapter 2 Alarm Troubleshooting 2.5.4 Alarm Hierarchy • Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but usually accompany primary alarms.
Chapter 2 Alarm Troubleshooting 2.5.4 Alarm Hierarchy Table 2-10 Facility Alarm Hierarchy (continued) Priority Condition Type — SD-P — UNEQ-P — TIM-P Lowest PLM-P Near-end failures and far-end failures follow different hierarchies. Near-end failures stand according to whether they are for the entire signal (LOS, loss of frame alignment [LOF]), facility (AIS-L), path (AIS-P, etc.) or VT (AIS-V, etc.). The full hierarchy for near-end failures is shown in Table 2-11.
Chapter 2 Alarm Troubleshooting 2.5.5 Service Effect 2.5.5 Service Effect Service-Affecting (SA) alarms—those that interrupt service—could be Critical (CR), Major (MJ), or Minor (MN) severity alarms. Service-Affecting (SA) alarms indicate service is affected. Non-Service-Affecting (NSA) alarms always have a Minor (MN) default severity. 2.5.6 States The State column on the Alarms or History tabs indicates the disposition of the alarm or condition as follows: • A raised (R) event is one that is active.
Chapter 2 Alarm Troubleshooting 2.7 Alarm Procedures 2.7 Alarm Procedures This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition. Note When you check the status of alarms for cards and ports, ensure that the alarm filter tool in the lower right corner of the GUI is not indented.
Chapter 2 Alarm Troubleshooting 2.7.3 AIS-P This condition can also be raised in conjunction with the “TIM-S” alarm on page 2-139 if AIS-L is enabled. Clear the AIS-L Condition Step 1 Complete the “Clear the AIS Condition” procedure on page 2-18. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.5 ALS 2.7.5 ALS For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. That guide discusses all dense wavelength division multiplexing (DWDM) alarms. 2.7.6 APC-END For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. That guide discusses all DWDM alarms. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.10 APSCINCON 2.7.10 APSCINCON Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: OCN An APS Inconsistent alarm means that an inconsistent APS byte is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15310-CL and ONS 15310-MA, to switch the SONET signal from a working to a protect path when necessary.
Chapter 2 Alarm Troubleshooting 2.7.12 APSCNMIS Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA system. Step 2 If the fibers are correctly connected, verify that the protection-port channel fibers are physically connected directly to the adjoining node protection-port channel fibers. Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.14 APS-INV-PRIM 2.7.14 APS-INV-PRIM Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Optimized 1+1 APS Primary Facility condition occurs on OC-N ports in an optimized 1+1 protection system if the incoming primary section header does not indicate whether it is primary or secondary. Note APS-INV-PRIM is an informational condition and does not require troubleshooting.
Chapter 2 Alarm Troubleshooting 2.7.16 APS-PRIM-FAC 2.7.16 APS-PRIM-FAC Default Severity: Not Alarmed (NA) Logical Objects: OCN The Optimized 1+1 APS Invalid Primary Section condition occurs on OC-N ports in an optimized 1+1 protection system if there is an APS status switch between the primary and secondary facilities to identify which port is primary. Note APS-PRIM-FAC is an informational condition and does not require troubleshooting.
Chapter 2 Alarm Troubleshooting 2.7.19 AS-MT The Alarms Suppressed by User Command condition applies to the network element (NE object), a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects. For example, suppressing alarms on a card also suppresses alarms on its ports. Note For more information about suppressing alarms, refer to the “Manage Alarms” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.
Chapter 2 Alarm Troubleshooting 2.7.20 AS-MT-OOG DWDM Logical Objects: PPM, SHELF The Alarms Suppressed for Maintenance Command condition applies to OC-3, OC-12, and electrical ports and occurs when a port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations. Clear the AS-MT Condition Step 1 Complete the “Clear an OC-N Port Facility or Terminal Loopback Circuit” procedure on page 2-156.
Chapter 2 Alarm Troubleshooting 2.7.22 AUD-LOG-LOW You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc. Step 6 Click Save. The 640 entries are saved in this file. New entries continue with the next number in the sequence, rather than starting over. Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.25 AUTOSW-AIS Note Step 3 When you replace a card with the identical type of card, you do not need to make any changes to the database. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.27 AUTOSW-LOP (VT-MON) Clear the AUTOSW-LOP (STSMON) Condition Step 1 Complete the “Clear the LOP-P Alarm” procedure on page 2-91. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.29 AUTOSW-SDBER Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.31 AUTOSW-UNEQ (STSMON) 2.7.31 AUTOSW-UNEQ (STSMON) Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: STSMON The Automatic Path Protection Switch Caused by Unequipped condition indicates that an UNEQ alarm caused automatic path protection switching to occur (see the “UNEQ-P” condition on page 2-142). If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Chapter 2 Alarm Troubleshooting 2.7.34 BKUPMEMP The Battery Fail alarm occurs when the power supply is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so onsite information about the conditions is necessary for troubleshooting. Clear the BAT-FAIL Alarm Step 1 At the site, determine which battery is not present or operational. Step 2 Remove the power cable from the faulty supply.
Chapter 2 Alarm Troubleshooting 2.7.35 BLSROSYNC Step 3 If the 15310-CL-CTX or CTX2500 card does not reboot successfully, or the alarm has not cleared, call Cisco TAC (1-800-553-2447). 2.7.35 BLSROSYNC The BLSROSYNC alarm is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.36 CARLOSS (CE100T) b. Confirm that the attached Ethernet device configuration allows reception of flow control frames. Step 8 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. (The autonegotiation process restarts.) Step 9 If the alarm does not clear and the “TPTFAIL (CE100T)” alarm on page 2-140 is also reported, complete the “Clear the TPTFAIL (CE100T) Alarm” procedure on page 2-141.
Chapter 2 Alarm Troubleshooting 2.7.37 CARLOSS (EQPT) • Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit connects the Ethernet port to an OC-N port at the same node. e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded. f.
Chapter 2 Alarm Troubleshooting 2.7.37 CARLOSS (EQPT) Clear the CARLOSS (EQPT) Alarm Step 1 If the reporting entity is a pluggable port module (PPM) port, confirm that the PPM is correctly configured by completing the following steps: a. Double-click the controller card (15310-CL-CTX or CTX2500 card). b. Click the Provisioning > Pluggable Port Modules tabs. c.
Chapter 2 Alarm Troubleshooting 2.7.38 CLDRESTART 2.7.38 CLDRESTART Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: EQPT The Cold Restart condition occurs when an Ethernet card is reseated or replaced, or when the ONS 15310-CL or ONS 15310-MA power is initialized. Clear the CLDRESTART Condition Step 1 If the condition is raised on the controller card, it should clear after booting.
Chapter 2 Alarm Troubleshooting 2.7.40 CONTBUS-CLK-A Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.42 CONTBUS-DISABLED Clear the CONTBUS-CLK-B Alarm Step 1 If a single traffic port is reporting the alarm and it is part of a path protection, complete the “Initiate a Force Switch for All Circuits on a Path Protection Span” procedure on page 2-151. If the traffic port is part of a 1+1 protection group, complete the “Clear a 1+1 Force or Manual Switch Command” procedure on page 2-149.
Chapter 2 Alarm Troubleshooting 2.7.43 CONTBUS-IO-A Clear the CONTBUS-DISABLED Alarm Step 1 If the IMPROPRMVL alarm is raised, complete the “Physically Replace a Card” procedure on page 2-154. (For general information about card installation, refer to the “Install Hardware” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.) Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.44 CTNEQPT-PBPROT Step 5 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1-800-553-2447). 2.7.44 CTNEQPT-PBPROT Default Severity: Critical (CR), Service-Affecting (SA) for ONS 15310-MA SONET Logical Object: EQPT The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the protect CTX2500 card Slot 4 cross-connect card and the reporting traffic card.
Chapter 2 Alarm Troubleshooting 2.7.45 CTNEQPT-PBWORK Step 6 If the reporting traffic card is the active card in the protection group, complete the “Initiate an ONS 15310-MA 1:1 Card Switch Command” procedure on page 2-150. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps. Step 7 Complete the “Soft- or Hard-Reset an Ethernet or Electrical Card in CTC” procedure on page 2-153 for the reporting card.
Chapter 2 Alarm Troubleshooting 2.7.46 DATAFLT When you replace a card with the identical type of card, you do not need to make any changes to the database. Note Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.48 DISCONNECTED Step 2 Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm: a. In node view, click the Provisioning > General > General tabs. b. In the Description field, make a small change such as adding a period to the existing entry. The change causes a database write but does not affect the node state. The write could take up to a minute.
Chapter 2 Alarm Troubleshooting 2.7.50 DUP-IPADDR Step 5 Click Apply. Step 6 If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the node matches the expected incoming signal. For specific procedures to use the test set equipment, consult the manufacturer. Step 7 If the condition does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.52 DUP-SHELF-ID Clear the DUP-NODENAME Alarm Step 1 In node view, click the Provisioning > General tabs. Step 2 In the Node Name/TID field, enter a unique name for the node. Step 3 Click Apply. Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.55 ENCAP-MISMATCH-P Clear the ELWBATVG Alarm Step 1 The problem is external to the ONS 15310-CL or ONS 15310-MA. Troubleshoot the power source supplying the battery leads. Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.56 EOC Note For more information about the ML-100T-8 Ethernet card, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. Clear the ENCAP-MISMATCH-P Alarm Step 1 Step 2 Step 3 Ensure that the correct line type is in use on the receive card by completing the following steps: a. In node view, double-click the receive ML-100T-8 card to display the card view. b. Click the Provisioning > Card tabs. c.
Chapter 2 Alarm Troubleshooting 2.7.56 EOC Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard.
Chapter 2 Alarm Troubleshooting 2.7.57 EOC-L Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT. Step 7 For all nodes, if the card is in service, use an optical test set to determine whether signal failures are present on fiber terminations. For specific procedures to use the test set equipment, consult the manufacturer.
Chapter 2 Alarm Troubleshooting 2.7.58 EQPT Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard.
Chapter 2 Alarm Troubleshooting 2.7.59 EQPT-MISS Step 3 Caution Step 4 If the CTC reset does not clear the alarm, complete the “Remove and Reinsert (Reseat) a Card” procedure on page 2-154 for the reporting card. Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA. If the physical reseat of the card fails to clear the alarm, complete the “Physically Replace a Card” procedure on page 2-154 for the reporting card.
Chapter 2 Alarm Troubleshooting 2.7.61 ERFI-P-PAYLD Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.63 ERROR-CONFIG Note • The user stored the configuration for one type of ML-100T-8 Ethernet card in the database and then installed another type in its slot. • The configuration file contained a syntax error. For information about provisioning the ML-100T-8 Ethernet cards from the Cisco IOS interface, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide.
Chapter 2 Alarm Troubleshooting 2.7.64 ETH-LINKLOSS 2.7.64 ETH-LINKLOSS Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: NE The Rear Panel Ethernet Link Removed condition, if enabled in the network defaults, is raised under the following conditions: • The node.network.general.AlarmMissingBackplaneLAN field in NE default is enabled. • The node is configured as a gateway network element (GNE). • The LAN cable is removed.
Chapter 2 Alarm Troubleshooting 2.7.67 EXT Step 2 If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the node and the network management LAN. Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.70 FAILTOSW-PATH 2.7.70 FAILTOSW-PATH Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: STSMON, VTMON The Fail to Switch to Protection Path condition occurs when the circuit does not switch from the working path to the protect path on a path protection.
Chapter 2 Alarm Troubleshooting 2.7.73 FE-AIS If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.73 FE-AIS Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far-End AIS condition occurs when an AIS has occurred at the far-end node. FE-AIS usually occurs in conjunction with a downstream LOS alarm (see the “LOS (OCN)” alarm on page 2-98).
Chapter 2 Alarm Troubleshooting 2.7.75 FE-DS1-NSA Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.77 FE-DS1-SNGLLOS 2.7.77 FE-DS1-SNGLLOS Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far-End Single DS-1 LOS condition occurs when a single DS-1 signal is lost on a far-end 15310-CL-CTX, ONS 15310-MA DS1-28/DS3-EC1-3, or ONS 15310-MA DS1-84/DS3-EC1-3 DS-1 port (within a DS3). Signal loss also causes the “LOS (OCN)” alarm on page 2-98.
Chapter 2 Alarm Troubleshooting 2.7.79 FE-DS3-SA 2.7.79 FE-DS3-SA Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far End DS-3 Equipment Failure Service-Affecting condition occurs when there is a far-end equipment failure on a 15310-CL-CTX, ONS 15310-MA DS1-28/DS3-EC1-3, or ONS 15310-MA DS1-84/DS3-EC1-3 DS-1 port that affects service because traffic is unable to switch to the protect port.
Chapter 2 Alarm Troubleshooting 2.7.82 FE-FRCDWKSWPR-SPAN The Far End Forced Switch Back to Working—Span condition is raised on a far-end 1+1 protect port when it is Force switched to the working port. Note WKSWBK-type conditions apply only to nonrevertive circuits. Clear the FE-FRCDWKSWBK-SPAN Condition Step 1 Complete the “Clear a 1+1 Force or Manual Switch Command” section on page 2-149 for the far-end port. If the condition does not clear, log into the Technical Support Website at http://www.
Chapter 2 Alarm Troubleshooting 2.7.85 FE-LOF 2.7.85 FE-LOF Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far End LOF condition occurs when a far-end node reports the “LOF (DS3)” alarm on page 2-87 in C-bit line type mode. Clear the FE-LOF Condition Step 1 To troubleshoot an FE condition, determine which node and port link directly to the card reporting the FE condition. Step 2 Log into the node that links directly to the port reporting the FE condition.
Chapter 2 Alarm Troubleshooting 2.7.88 FE-MANWKSWPR-SPAN 2.7.88 FE-MANWKSWPR-SPAN The FE-MANWKSWPR-SPAN condition is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.89 FEPRLF Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Far End Protection Line Failure alarm occurs when an APS channel “SF-L” condition on page 2-126 occurs on the protect port coming into the node.
Chapter 2 Alarm Troubleshooting 2.7.91 FORCED-REQ-SPAN 2.7.91 FORCED-REQ-SPAN Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Force Switch Request Span condition applies to optical trunk cards in spans when the Force Span command is applied to a span to force traffic from working to protect or from protect to working. This condition appears on the network view Alarms, Conditions, and History tabs.
Chapter 2 Alarm Troubleshooting 2.7.94 FRCDSWTOSEC 2.7.94 FRCDSWTOSEC Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: EXT-SREF, NE-SREF The Force Switch to Second Timing Source condition occurs when the user issues a Force command to switch to a second timing source. Note FRCDSWTOSEC is an informational condition. It does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.97 FSTSYNC 2.7.97 FSTSYNC Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: NE-SREF A Fast Start Synchronization Mode condition occurs when the ONS 15310-CL or ONS 15310-MA is choosing a new timing reference. The previous timing reference has failed. The FSTSYNC condition disappears after approximately 30 seconds. If the condition does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.101 GFP-LFD The GFP Extension Header Mismatch alarm is raised on Fibre Channel/fiber connectivity (FICON) GFP ports when it receives frames with an extension header that is not null. The alarm occurs when a provisioning error causes all GFP frames to be dropped for 2.5 seconds. To clear this alarm, ensure that both end ports are sending a null extension header for a GFP frame.
Chapter 2 Alarm Troubleshooting 2.7.103 HELLO The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type.
Chapter 2 Alarm Troubleshooting 2.7.104 HIBATVG Step 2 b. Ensure that the IP address in the Area ID column matches the other nodes. c. If the address does not match, click the incorrect cell and correct it. d. Click Apply. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.106 HI-LASERTEMP Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the “2.10.1 Protection Switching, Lock Initiation, and Clearing” section on page 2-147 for commonly used traffic-switching procedures. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.107 HI-RXPOWER Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.107 HI-RXPOWER Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Equipment High Receive Power alarm is an indicator for OCN port received optical signal power.
Chapter 2 Alarm Troubleshooting 2.7.109 HI-TXPOWER 2.7.109 HI-TXPOWER Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Objects: EQPT, OCN DWDM Logical Object: PPM The Equipment High Transmit Power alarm is an indicator on the OC-N port transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.
Chapter 2 Alarm Troubleshooting 2.7.111 I-HITEMP The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished.
Chapter 2 Alarm Troubleshooting 2.7.112 IMPROPRMVL The Industrial High Temperature alarm occurs when the temperature of the ONS 15310-CL or ONS 15310-MA is above 149 degrees F (65 degrees C) or below –40 degrees F (–40 degrees C). This alarm is similar to the HITEMP alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.
Chapter 2 Alarm Troubleshooting 2.7.112 IMPROPRMVL Note CTC does not allow you to delete the reporting card if the card is in service, does have circuits mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference. Step 3 If any ports on the card are in service, put them out of service (OOS,MT) by completing the following steps: Caution Before placing a port out of service (OOS,MT or OOS,DSBLD), ensure that no live traffic is present.
Chapter 2 Alarm Troubleshooting 2.7.113 INC-ISD 2.7.113 INC-ISD Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The DS-3 Idle condition indicates that the DS-3 port is receiving an idle signal from a 15310-CL-CTX, ONS 15310-MA DS1-28/DS3-EC1-3, or ONS 15310-MA DS1-84/DS3-EC1-3 DS-1 port, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has an OOS-MA,MT service state.
Chapter 2 Alarm Troubleshooting 2.7.116 INHSWPR 2.7.116 INHSWPR Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) for ONS 15310-MA SONET Logical Object: EQPT The Inhibit Switch To Protect Request on Equipment condition occurs on traffic cards when the ability to switch to protect has been disabled. If the port is part of a 1+1 protection scheme, traffic remains locked onto the working system.
Chapter 2 Alarm Troubleshooting 2.7.119 INVMACADR Clear the INTRUSION-PSWD Condition Step 1 In node view, click the Provisioning > Security tabs. Step 2 Click Clear Security Intrusion Alarm. Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.121 ISIS-ADJ-FAIL The Open System Interconnection (OSI) Intermediate System to Intermediate-System (IS-IS) Adjacency Failure alarm is raised by an intermediate system (node routing IS Level 1 or Level 1 and 2) when no IS or end system (ES) adjacency is established on a point-to-point subnet. The Intermediate-System Adjacency Failure alarm is not supported by ES. It is also not raised by IS for disabled routers.
Chapter 2 Alarm Troubleshooting 2.7.122 KB-PASSTHR b. Tip Step 9 Record the primary MAA and secondary MAAs, if configured. You can record long strings of information such as the MAA address by using the CTC export and print functions. Export it by choosing File > Export > html. Print it by choosing File > Print. c. Log into the other node and record the primary MAA and secondary MAAs, if configured. d. Compare this information.
Chapter 2 Alarm Troubleshooting 2.7.125 LCAS-RX-FAIL Step 1 Look for and clear any bit error rate conditions at the transmit node. Step Note2 If equipment or SONET errorscards, exist,refer ensure thatCisco the remote node has and LCAS enabled on the Fornomore information about path Ethernet to the ONS 15310-CL Cisco ONS 15310-MA circuit completing following steps: EthernetbyCard Softwarethe Feature and Configuration Guide. a. In node view, click the Circuits tab. b.
Chapter 2 Alarm Troubleshooting 2.7.126 LCAS-TX-ADD Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. Note ONS 15310-CL ML-100T-8-Series cards are LCAS-enabled. Clear the LCAS-RX-FAIL Condition Step 1 Check for and clear any line or path alarms using the procedures in this chapter. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.128 LKOUTPR-S 2.7.128 LKOUTPR-S Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Lockout of Protection Span condition occurs when path protection traffic is locked out of a protect span using the “Lockout of Protect” command. This condition is visible on the network view Alarms, Conditions, and History tabs after the lockout has occurred and accompanies the FE-LOCKOUTPR-SPAN condition.
Chapter 2 Alarm Troubleshooting 2.7.130 LOCKOUT-REQ Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.132 LOF (DS1) b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself. c. Click the Provisioning > Timing > BITS Facilities tabs. d. Verify that the Coding setting matches the coding of the BITS timing source, either B8ZS or AMI. e.
Chapter 2 Alarm Troubleshooting 2.7.133 LOF (DS3) f. Verify that the reporting Line Coding matches the signal source line coding (AMI and AMI or B8ZS and B8ZS). If the signal source line coding does not match the reporting port, click the Line Coding cell and choose the correct type from the drop-down list. g. Click Apply. Note Step 2 On the Line tab, the B8ZS coding field is normally paired with ESF in the Line Type field. AMI coding is normally paired with SF (D4) in the Line Type field.
Chapter 2 Alarm Troubleshooting 2.7.135 LOF (OCN) The EC1-1 LOF alarm occurs when a port on the reporting EC-1 port has an LOF condition. LOF indicates that the receiving ONS 15310-CL or ONS 15310-MA has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm. Clear the LOF (EC1) Alarm Step 1 Verify cabling continuity to the port reporting the alarm.
Chapter 2 Alarm Troubleshooting 2.7.137 LOGBUFR90 SONET Logical Object: STSTRM A Loss of Frame alarm for an STS circuit termination indicates that the LOF has occurred at the terminating point of the circuit (such as an OC-N port). It is similar to the “LOF (OCN)” alarm on page 2-88. Clear the LOF (STSTRM) Alarm Step 1 Complete the “Clear the LOF (OCN) Alarm” procedure on page 2-88. Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.139 LO-LASERBIAS 2.7.139 LO-LASERBIAS Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Objects: EQPT, OCN DWDM Logical Object: PPM The Equipment Low Transmit Laser Bias Current alarm is raised against OCN port or PPM laser performance. The alarm indicates that the laser has reached the minimum laser bias tolerance. If the LO-LASERBIAS alarm threshold is set at 0 percent (the default), the laser's usability has ended.
Chapter 2 Alarm Troubleshooting 2.7.141 LOM 2.7.141 LOM Default Severity: Critical (CR), Service-Affecting (SA) for STSMON and STSTRM; Major (MJ) for VT-TERM SONET Logical Objects: STSMON, STSTRM, VT-TERM The Optical Transport Unit (OTU) Loss of Multiframe is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.
Chapter 2 Alarm Troubleshooting 2.7.143 LOP-V Step 4 If the error is not due to an incorrectly configured test set, the error is in the provisioned CTC circuit size. Complete the “Delete a Circuit” procedure on page 2-155. Step 5 Recreate the circuit for the correct size. For procedures, refer to the “Create Circuits” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting 2.7.145 LOS (BITS) Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.146 LOS (DS1) Step 2 If wiring is good, verify that the BITS clock is operating properly. Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.147 LOS (DS3) Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT. Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving port as possible. For specific procedures to use the test set equipment, consult the manufacturer.
Chapter 2 Alarm Troubleshooting 2.7.148 LOS (EC1) Step 3 Step 4 If the port is not currently assigned, place the port out of service using the following steps: a. In node view, double-click the card to display the card view. b. Click the Maintenance > DS3 tabs. c. In the Admin State column, click OOS,DSBLD. d. Click Apply. If the port is assigned, verify that the correct port is in service by completing the following steps: a. To confirm this physically, confirm that the green ACT LED is on.
Chapter 2 Alarm Troubleshooting 2.7.149 LOS (FUDC) Note If a circuit shows a partial status when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm. Clear the LOS (EC1) Alarm Step 1 Caution Step 2 Using site practice, verify cabling continuity to the port reporting the alarm.
Chapter 2 Alarm Troubleshooting 2.7.150 LOS (OCN) The LOS (FUDC) alarm is raised if there is a user data channel (UDC) circuit created but the port is not receiving signal input. The downstream node raises an AIS condition raised against the port transmitting the UDC. FUDC refers to the 64-kb user data channel using the F1 byte. Clear the LOS (FUDC) Alarm Step 1 Caution Using site practices, verify cable continuity to the UDC port.
Chapter 2 Alarm Troubleshooting 2.7.150 LOS (OCN) Warning Note Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 If a circuit shows a partial status when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Chapter 2 Alarm Troubleshooting 2.7.151 LO-TXPOWER Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.151 LO-TXPOWER Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Objects: EQPT, OCN DWDM Logical Object: PPM The Equipment Low Transmit Power alarm is an indicator for OCN port transmitted optical signal power.
Chapter 2 Alarm Troubleshooting 2.7.153 LPBKDS3FEAC The Cross-Connect Loopback condition indicates that there is a software cross-connect loopback active between two OC-3 or OC-12 optical ports. A cross-connect loopback test occurs below line speed and does not affect traffic. For more information on loopbacks, see the “1.2 Identify Points of Failure on an Electrical Circuit Path” section on page 1-3. Note Cross-connect loopbacks occur below line speed. They do not affect traffic.
Chapter 2 Alarm Troubleshooting 2.7.155 LPBKFACILITY (CE100T) SONET Logical Object: DS3 The DS-3 Loopback Command Sent To Far End condition occurs on a near-end 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card when you send a DS-3 FEAC loopback. Note LPBKDS3FEAC-CMD is an informational condition and does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.157 LPBKFACILITY (EC1) Clear the LPBKFACILITY (DS1, DS3) Condition Step 1 Complete the “Clear a DS-3 or DS-1 Port Loopback Circuit” procedure on page 2-156. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.159 LPKTERMINAL (CE100T) Caution Note CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA). Before performing a facility (line) loopback on an OC-3 or OC-12 port, ensure the card contains at least two DCC paths to the node where the card is installed. A second DCC path provides a nonlooped path to log into the node after the loopback is applied, thus enabling you to remove the facility loopback.
Chapter 2 Alarm Troubleshooting 2.7.161 LPBKTERMINAL (EC1) For information about troubleshooting optical circuits with loopbacks, refer to the “1.2 Identify Points of Failure on an Electrical Circuit Path” section on page 1-3. Facility loopbacks are described in the “1.1 Network Troubleshooting Tests” section on page 1-2. Clear the LPBKTERMINAL (DS1, DS3) Condition Step 1 Complete the “Clear a DS-3 or DS-1 Port Loopback Circuit” procedure on page 2-156.
Chapter 2 Alarm Troubleshooting 2.7.163 LWBATVG Note Performing a loopback on an in-service circuit is Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the LPBKTERMINAL condition can also be accompanied by a more serious alarm such as LOS. For information about troubleshooting electrical circuits with loopbacks, refer to the “1.2 Identify Points of Failure on an Electrical Circuit Path” section on page 1-3; for optical circuits, refer to the “1.
Chapter 2 Alarm Troubleshooting 2.7.165 MANRESET Clear the MAN-REQ Condition Step 1 Complete the “Initiate a 1+1 Manual Switch Command” procedure on page 2-148. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.169 MANSWTOTHIRD The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to a second timing source. Note MANSWTOSEC is an informational condition and does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.172 MEA (EQPT) Clear the MATECLK Alarm Step 1 Complete the “Soft- or Hard-Reset a Controller Card” procedure on page 2-153 for the standby CTX2500 card and wait 15 minutes. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-MA. Plug the wristband cable into either of the ESD jacks, on the far left and right faceplates in the shelf.
Chapter 2 Alarm Troubleshooting 2.7.173 MEA (FAN) Step 4 Caution Step 5 Caution Step 6 If any ports on the card are in service, place them out of service (OOS) by completing the following steps: Before placing ports out of service, ensure that live traffic is not present. a. Double-click the reporting card to display the card view. b. Click the Provisioning tab. c. Click the Admin State column for any in-service ports. d. Choose OOS,MT to take the ports out of service.
Chapter 2 Alarm Troubleshooting 2.7.175 MEM-GONE 2.7.175 MEM-GONE Default Severity: Major (MJ), Non-Service-Affecting (NSA) SONET Logical Object: EQPT The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the 15310-CL-CTX or CTX2500 card. CTC does not function properly until the alarm clears. The alarm clears when additional memory becomes available. The alarm does not require user intervention.
Chapter 2 Alarm Troubleshooting 2.7.179 NOT-AUTHENTICATED The No Startup Configuration condition applies to ML-100T-8 Ethernet cards and occurs when no startup configuration file has been downloaded to the 15310-CL-CTX or CTX2500 card, whether or not you preprovision the card slot. This alarm can occur during provisioning. When the startup configuration file is copied to the 15310-CL-CTX or CTX2500 card, the alarm clears.
Chapter 2 Alarm Troubleshooting 2.7.181 OPEN-SLOT The Out of Use Transport Failure alarm is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) This condition is raised when a member circuit in a VCAT is unused. It occurs in conjunction with the “VCG-DEG” alarm on page 2-144. Clear the OOT-TPT Condition Step 1 Complete the “Clear the VCG-DEG Condition” procedure on page 2-145.
Chapter 2 Alarm Troubleshooting 2.7.182 PDI-P A PDI-P condition reported on an OC-3 or OC-12 port supporting an ONS 15310-CL or ONS 15310-MA Ethernet card circuit could result from the end-to-end Ethernet link integrity feature of the Ethernet card. If the link integrity is the cause of the path defect, it is typically accompanied by the “CARLOSS (EQPT)” alarm on page 2-35 reported against one or both Ethernet ports terminating the circuit.
Chapter 2 Alarm Troubleshooting 2.7.183 PLM-P Step 8 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.183 PLM-P Default Severity: Critical (CR), Service-Affecting (SA) SONET Logical Objects: STSMON, STSTRM A Payload Label Mismatch Path alarm indicates that signal does not match its label. The condition is indicated by an invalid C2 byte value in the SONET path overhead.
Chapter 2 Alarm Troubleshooting 2.7.185 PRC-DUPID Clear the PLM-V Alarm Step 1 Verify that your signal source matches the signal allowed by the traffic card. For example, the alarm will occur if your signal source uses VT6 or VT9 mapping, because this is not supported by a 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card. Step 2 If the signal source matches the card, verify that the SONET VT path originator is sending the correct VT label value.
Chapter 2 Alarm Troubleshooting 2.7.187 PROV-MISMATCH Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447). 2.7.187 PROV-MISMATCH For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. That guide discusses all DWDM alarms. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.189 PWR-FAIL-B Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.189 PWR-FAIL-B Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: EQPT The Equipment Power Failure at Connector B alarm occurs when there is no power supply from the main power connector to the equipment.
Chapter 2 Alarm Troubleshooting 2.7.192 RFI-P A Remote Fault Indication (RFI) Line condition occurs when the ONS 15310-CL or ONS 15310-MA detects an RFI in OC-3 or OC-12 port SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-L condition in the reporting node. RFI-L indicates that the condition is occurring at the line level. Clear the RFI-L Condition Step 1 Log into the node at the far-end of the reporting ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.193 RFI-V 2.7.193 RFI-V Default Severity: Not Reported (NR), Non-Service-Affecting (NSA) SONET Logical Objects: VT-MON, VT-TERM An RFI VT Layer condition occurs when the ONS 15310-CL or ONS 15310-MA detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-V condition in the reporting node. RFI-V indicates that an upstream failure has occurred at the VT layer.
Chapter 2 Alarm Troubleshooting 2.7.195 ROLL-PEND The ROLL condition indicates that circuits are being rolled. This is typically done to move traffic for a maintenance operation or to perform bandwidth grooming. The condition indicates that a good signal has been received on the roll destination leg, but the roll origination leg has not yet been dropped. The condition clears when the roll origination leg is dropped. Note ROLL is an informational condition and does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.198 SD SONET Logical Object: EQPT The Run Configuration Save Needed condition occurs when you change the running configuration file for ML-100T-8 card. It is a reminder that you must save the change to the startup configuration file for it to be permanent. The condition clears after you save the running configuration to the startup configuration, such as by entering the following command at the CLI: copy run start at the privileged EXEC mode of the Cisco IOS CLI.
Chapter 2 Alarm Troubleshooting 2.7.199 SD-L Note The recommended test set for use on all SONET ONS electrical ports is the Omniber 718. Clear the SD (DS1, DS3) Condition Step 1 Complete the “Clear a DS-3 or DS-1 Port Loopback Circuit” procedure on page 2-156. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA. Step 2 Ensure that the fiber connector for the port is completely plugged in.
Chapter 2 Alarm Troubleshooting 2.7.200 SD-P Clear the SD-L Condition Step 1 Complete the “Clear an OC-N Port Facility or Terminal Loopback Circuit” procedure on page 2-156. Step 2 Ensure that the fiber connector for the port is completely plugged in. For more information about fiber connections, refer to the “Install Hardware” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.
Chapter 2 Alarm Troubleshooting 2.7.201 SD-V Clear the SD-P Condition Step 1 Complete the “Clear the SD-L Condition” procedure on page 2-124. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.203 SF-L Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 Clear the SF (DS1, DS3) Condition Step 1 Caution Step 2 Complete the “Clear the SD (DS1, DS3) Condition” procedure on page 2-123. Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.205 SFTWDOWN Clear the SF-P Condition Step 1 Complete the “Clear the SD-L Condition” procedure on page 2-124. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.208 SNTP-HOST 2.7.208 SNTP-HOST Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: NE The Simple Network Timing Protocol (SNTP) Host Failure alarm indicates that an ONS 15310-CL or ONS 15310-MA serving as an IP proxy for the other nodes in the ring is not forwarding SNTP information to the other nodes in the network.
Chapter 2 Alarm Troubleshooting 2.7.211 SQM 2.7.211 SQM Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Major (MJ), Service-Affecting (SA) for VT-TERM SONET Logical Objects: STSTRM, VT-TERM The Sequence Mismatch alarm is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when the expected sequence numbers of VCAT members do not match the received sequence numbers.
Chapter 2 Alarm Troubleshooting 2.7.214 SSM-OFF Clear the SSM-FAIL Alarm Step 1 Verify that SSM is enabled on the external timing source. Step 2 If timing is enabled, use an optical test set to determine that the external timing source is delivering SSM. For specific procedures to use the test set equipment, consult the manufacturer. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting 2.7.217 SSM-SMC The SSM Reserved (RES) For Network Synchronization Use condition occurs when the synchronization message quality level is changed to RES. Note SSM-RES is an informational condition. It does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.221 SSM-ST4 Note SSM-ST3E is an informational condition. It does not require troubleshooting. 2.7.221 SSM-ST4 Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: BITS, DS1, NE-SREF, OCN The SSM Stratum 4 (ST4) Traceable condition occurs when the synchronization message quality level is lowered to ST4. The message quality is not used because it is below ST3. Note SSM-ST4 is an informational condition.
Chapter 2 Alarm Troubleshooting 2.7.224 STS-SQUELCH-L 2.7.224 STS-SQUELCH-L Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Ring is Squelching STS traffic condition is raised on an OC-N facility. If the node failure scenario includes the source or destination node, then switching nodes squelches all the STS which originate from or destinate to the failure node. The condition resolves when the node is no longer failing.
Chapter 2 Alarm Troubleshooting 2.7.227 SWMTXMOD-WORK 2.7.227 SWMTXMOD-WORK Default Severity: Critical (CR), Service-Affecting (SA) SONET Logical Object: EQPT The Switching Matrix Module Failure on Working Slot alarm is raised by the 15310-CL-CTX or CTX2500 card when a logic component internal to the card’s cross connect is OOF with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.
Chapter 2 Alarm Troubleshooting 2.7.230 SWTOTHIRD Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.230 SWTOTHIRD Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: EXT-SREF, NE-SREF The Synchronization Switch to Third Reference condition occurs when the ONS 15310-CL or ONS 15310-MA has switched to a third timing source (reference 3).
Chapter 2 Alarm Troubleshooting 2.7.233 SYNCSEC A Loss of Timing on Primary Reference alarm occurs when the ONS 15310-CL or ONS 15310-MA loses the primary timing source (reference 1). The system uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the system should switch to its secondary timing source (reference 2). Switching to a secondary timing source also triggers the “SWTOSEC” alarm on page 2-134.
Chapter 2 Alarm Troubleshooting 2.7.234 SYNCTHIRD 2.7.234 SYNCTHIRD Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Objects: EXT-SREF, NE-SREF A Loss of Timing on Third Reference alarm occurs when the ONS 15310-CL or ONS 15310-MA loses the third timing source (reference 3). If SYNCTHIRD occurs and the system uses an internal reference for source three, the 15310-CL-CTX card or CTX2500 card could have failed.
Chapter 2 Alarm Troubleshooting 2.7.236 TIM SONET Logical Object: OCN The Section TIM alarm occurs when the expected J0 section trace string does not match the received section trace string. This occurs because the data being received is not correct or the receiving port could not connect to the correct transmitter port.
Chapter 2 Alarm Troubleshooting 2.7.237 TIM-MON 2.7.237 TIM-MON Default Severity: Minor (MN) SONET Logical Object: OCN The TIM Section Monitor TIM alarm applies to TXP and MXP cards. For information about this alarm, refer to the “Alarm Troubleshooting” chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.240 TIM-V In Auto mode on the receiving port, the card sets the expected string to the value of the received string. If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Complete the following procedure to clear either problem.
Chapter 2 Alarm Troubleshooting 2.7.242 TX-AIS Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. Clear the TPTFAIL (CE100T) Alarm Step 1 Clear any alarms being reported by the OC-N port on the CE100T-8 circuit. Step 2 If no alarms are reported by the OC-N port, or if the “PDI-P” condition on page 2-113 is reported, the problem could be on the far-end G-Series Ethernet port.
Chapter 2 Alarm Troubleshooting 2.7.244 TX-RAI If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447). 2.7.244 TX-RAI Default Severity: Not Alarmed (NA) SONET Logical Objects: DS1, DS3 The Transmit Direction RAI condition is transmitted by the backplane when it receives a 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 DS-1 TX-AIS.
Chapter 2 Alarm Troubleshooting 2.7.245 UNEQ-P Step 5 If the Type column does not contain VTT, there are no VT tunnels connected with the alarm. Go to Step 7. Step 6 If the Type column does contain VTT, attempt to delete these rows by completing the following steps: Note Step 7 The node does not allow you to delete a valid VT tunnel or one with a valid VT circuit inside. a. Click the VT tunnel circuit row to highlight it. Complete the “Delete a Circuit” procedure on page 2-155. b.
Chapter 2 Alarm Troubleshooting 2.7.246 UNEQ-V Step 13 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting 2.7.248 VCG-DOWN Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. Clear the VCG-DEG Condition Step 1 Look for and clear any Critical (CR) alarms that apply to the errored card or port. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447). 2.7.
Chapter 2 Alarm Troubleshooting 2.7.250 WKSWPR 2.7.250 WKSWPR Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: EQPT, OCN, STSMON, VT-MON The Working Switched To Protection condition occurs when a line experiences the “LOS (OCN)” alarm on page 2-98. This condition is also raised when you use the FORCE SPAN or MANUAL SPAN command at the network level. WKSWPR is visible on the network view Alarms, Conditions, and History tabs.
Chapter 2 Alarm Troubleshooting 2.9 Traffic Card LED Activity Table 2-13 DS-1 Alarms by Line Type (continued) Alarm UNFRAMED D4 ESF Facility Lpbk Yes Yes Yes FE Lpbk No No Yes FE Common Equipment Failure No No Yes FE Equipment Failure-SA No No Yes FE LOS No No Yes FE LOF No No Yes FE AIS No No Yes FE IDLE No No Yes FE Equipment Failure-NSA No No Yes 2.
Chapter 2 Alarm Troubleshooting 2.10.1 Protection Switching, Lock Initiation, and Clearing Initiate a 1+1 Protection Port Force Switch Command This procedure switches 1+1 protection group traffic from one port in the group to the other using a Force switch. Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages. Caution Traffic is not protected during a Force protection switch.
Chapter 2 Alarm Troubleshooting 2.10.1 Protection Switching, Lock Initiation, and Clearing Clear a 1+1 Force or Manual Switch Command Note If the 1+1 protection group is configured as revertive, clearing a Force switch to protect (or working) moves traffic back to the working port. In revertive operation, the traffic always switches back to working. There is no revert to the protect. If ports are not configured as revertive, clearing a Force switch to protect does not move traffic back.
Chapter 2 Alarm Troubleshooting 2.10.1 Protection Switching, Lock Initiation, and Clearing Initiate a Card or Port Lockout Command Note For ONS 15310-MA 1:1 electrical protection groups, working or protect cards can be placed in the Lock Out state. For a 1+1 optical protection group, only the protect port can be placed in the Lock Out state. Step 1 In node view, click the Maintenance > Protection tabs.
Chapter 2 Alarm Troubleshooting 2.10.1 Protection Switching, Lock Initiation, and Clearing Initiate a Force Switch for All Circuits on a Path Protection Span This procedure forces all circuits in a path protection from the working span to the protect. It is used to remove traffic from a card that originates or terminates path protection circuits. Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.
Chapter 2 Alarm Troubleshooting 2.10.1 Protection Switching, Lock Initiation, and Clearing In the Circuits on Span dialog box, the switch state for all circuits is Manual. Unprotected circuits do not switch. Initiate a Lockout for All Circuits on a Protect Path Protection Span This procedure prevents all circuits in a path protection working span from switching to the protect span. It is used to keep traffic off cards that originate or terminate path protection circuits.
Chapter 2 Alarm Troubleshooting 2.10.2 CTC Card Resetting and Switching In the Circuits on Span dialog box, the switch state for all circuits is Clear. Unprotected circuits do not switch. 2.10.2 CTC Card Resetting and Switching Caution Avoid soft resetting more than one ONS 15310-MA card at a time. Instead, issue a soft reset command for a single card, then wait until CTC shows the card is back up. You can then issue a soft reset on another card if needed.
Chapter 2 Alarm Troubleshooting 2.10.3 Physical Card Reseating and Replacement Note The reset options are enabled only in the OOS-MA,MT service state. Note Before you reset the 15310-CL-CTX or CTX2500 card, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database. Step 1 Log into a node on the network. If you are already logged in, continue with Step 2. Step 2 Right-click the active 15310-CL-CTX or CTX2500 card in CTC.
Chapter 2 Alarm Troubleshooting 2.10.4 Generic Signal and Circuit Procedures Step 4 Slide the replacement card into the slot along the guide rails. Step 5 Close the ejectors. 2.10.4 Generic Signal and Circuit Procedures Verify the Signal BER Threshold Level Step 1 Log into a node on the network. If you are already logged in, continue with Step 2. Step 2 In node view, double-click the card reporting the alarm to display the card view.
Chapter 2 Alarm Troubleshooting 2.10.4 Generic Signal and Circuit Procedures d. Verify that the Disable OSPF on Link check box is unchecked. e. Click OK. Clear an OC-N Port Facility or Terminal Loopback Circuit Step 1 Log into a node on the network. If you are already logged in, continue with Step 2. Step 2 Double-click the 15310-CL-CTX or CTX2500 card in CTC to display the card view. Step 3 Click the Maintenance > Optical > Loopback > Port tabs.
Chapter 2 Alarm Troubleshooting 2.10.4 Generic Signal and Circuit Procedures Step 7 If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS. Step 8 Click Apply. Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT. Clear an EC-1 Port Loopback Step 1 Log into a node on the network.
Chapter 2 Alarm Troubleshooting 2.10.4 Generic Signal and Circuit Procedures Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT. Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
C H A P T E R 3 Transient Conditions This chapter gives a description, entity, Simple Network Management Protocol (SNMP) number, and SNMP trap for each commonly encountered Cisco ONS 15310-CL and Cisco ONS 15310-MA transient condition. 3.1 Transients Indexed By Alphabetical Entry Table 3-1 alphabetically lists all ONS 15310-CL and ONS 15310-MA transient conditions and their entity, SNMP number, and SNMP trap.
Chapter 3 Transient Conditions 3.1 Transients Indexed By Alphabetical Entry Table 3-1 ONS 15310-CL and ONS 15310-MA Transient Condition Alphabetical List (continued) Transient Condition Entity SNMP Number SNMP Trap 3.3.14 INTRUSION, page 3-6 NE 5250 securityIntrusionDetUser 3.3.15 INTRUSION-PSWD, page 3-6 NE 5240 securityIntrusionDetPwd 3.3.16 LOGIN-FAILURE-LOCKOUT, page 3-6 NE 5080 securityInvalidLoginLocke dOutSeeAuditLog 3.3.
Chapter 3 Transient Conditions 3.2 Trouble Notifications Table 3-1 ONS 15310-CL and ONS 15310-MA Transient Condition Alphabetical List (continued) Transient Condition Entity SNMP Number SNMP Trap 3.3.34 WKSWPR, page 3-9 2650 2R, TRUNK, EQPT, ESCON, FC, GE, ISC, OCN, STSMON, VT-MON switchedToProtection 3.3.35 WRMRESTART, page 3-9 NE warmRestart 2660 3.
Chapter 3 Transient Conditions 3.3 Transient Conditions 3.3 Transient Conditions This section lists in alphabetical order all the transient conditions encountered in Software Release 7.0. The description, entity, SNMP number, and SNMP trap accompany each condition. 3.3.1 ADMIN-DISABLE The Disable Inactive User (ADMIN-DISABLE) condition occurs when the administrator disables the user or the account is inactive for a specified period. This transient condition does not result in a standing condition. 3.3.
Chapter 3 Transient Conditions 3.3.7 ADMIN-SUSPEND-CLR 3.3.7 ADMIN-SUSPEND-CLR The Suspend User Clear (ADMIN-SUSPEND-CLR) condition occurs when the user or administrator changes the password. This transient condition does not result in a standing condition. 3.3.8 AUD-ARCHIVE-FAIL The Archive of AuditLog Failed (AUD-ARCHIVE-FAIL) condition occurs when the software fails to archive the audit log.
Chapter 3 Transient Conditions 3.3.13 FRCDWKSWPR-NO-TRFSW 3.3.13 FRCDWKSWPR-NO-TRFSW The Forced Switch to Protection Resulted in No Traffic Switch (FRCDWKSWPR-NO-TRFSW) condition occurs when you perform a Force Switch to the protect port/card, and the protect port/card is already active. This transient condition does not result in a standing condition. 3.3.14 INTRUSION The Invalid Login Username (INTRUSION) condition occurs when you attempt to log in with an invalid user ID.
Chapter 3 Transient Conditions 3.3.20 LOGOUT-IDLE-USER This transient condition is equivalent to a security warning. You must check the security log (audit log) for other security-related actions that have occurred. 3.3.20 LOGOUT-IDLE-USER The Automatic Logout of Idle User (LOGOUT-IDLE-USER) condition occurs when a user session is idle for too long (the idle timeout expires) and the session terminates as a result. You must log in again to restart your session. 3.3.
Chapter 3 Transient Conditions 3.3.27 RMON-RESET 3.3.27 RMON-RESET The RMON Histories and Alarms Reset Reboot (RMON-RESET) condition occurs when the time-of-day settings on the 15310-CL-CTX or CTX2500 card are increased or decreased by more than five seconds. This invalidates all the history data and RMON must restart. It can also occur when you reset a card. 3.3.
Chapter 3 Transient Conditions 3.3.34 WKSWPR 3.3.34 WKSWPR The Switched to Protection (WKSWPR) condition occurs when traffic switches to the protect port/card in a nonrevertive protection group. This transient condition does not result in a standing condition. 3.3.35 WRMRESTART The Warm Restart (WRMRESTART) condition occurs when the node restarts while it is powered up. A restart can be caused by provisioning, such as database-restore and IP changes, or software defects.
Chapter 3 3.3.35 WRMRESTART Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
C H A P T E R 4 Error Messages Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 4 Table 4-1 Error Messages Error Messages Error Warning ID Error Warning Message Description EID-0 Invalid error ID. The error ID is invalid. EID-1 Null pointer encountered in {0}. Cisco Transport Controller (CTC) encountered a null pointer in the area described by the specified item. EID-1000 The host name of the network element cannot be resolved to an Refer to the error message text. address. EID-1001 Unable to launch CTC due to applet security restrictions.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-1023 Refer to the error message text. This session has been terminated. Terminations are caused when the session has timed out, the card resets, there is already a session with the slot, or password configuration is required. EID-1025 Unable to create Help Broker. CTC was unable to create the help broker for the online help. EID-1026 Error found in the Help Set file.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2003 Error deleting roll. There was an error when CTC tried to delete the roll. EID-2004 No IOS slot selected. You did not select a Cisco IOS slot. EID-2005 CTC cannot find the online help files for {0}. The files may have been moved, deleted, or not installed. To install online help, run the setup program on the software or documentation CDs.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2025 This feature cannot be used. Verify that each of the endpoints of this circuit are running software that supports this feature. Refer to the error or warning message text. For example, this error is generated from the node view Provisioning> WDM-ANS> tabs to indicate that the selected ring type is not supported by the endpoints of the circuit.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2043 This node is not selectable. Only the source node and nodes attached to included spans (blue) are selectable. Selecting a selectable node will enable its available outgoing spans. Refer to the error message text. EID-2044 This link may not be included in the required list. Constraints only apply to the primary path.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2066 Unable to store profile. Error writing to {0}. CTC encountered an error while trying to store the profile. EID-2067 File write error. {0} CTC encountered an error while writing the specified file. EID-2068 Unable to load alarm profile from node. CTC encountered an error trying to load the alarm profile from the node. EID-2069 File not found or I/O exception.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2090 No nodes selected. Please select the node(s) on which to store the profile(s). You must select one or more nodes on which you can store the profile. EID-2091 Unable to switch to node {0}. CTC is unable to switch to the specified node. EID-2092 General exception error. CTC encountered a general exception error while trying to complete the task.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2116 Invalid extension byte setting for ring. {0} The extension byte set for the specified ring is invalid. EID-2118 Cannot delete ring. There is a protection operation set. All protection operations must be clear for ring to be deleted. Clear all the protection operations for the ring before deleting it.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2130 The ring ID value, {0}, is not valid. Please enter a valid number Enter a ring ID value between 0 and 9999. between 0 and 9999. EID-2131 Cannot set reversion to INCONSISTENT. You must select another reversion type. EID-2135 Unable to store overhead circuit preferences: Input/Output error. Unable to store overhead circuit preferences. {0} EID-2137 Circuit merge error.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2159 Roll not ready for completion. {0} The roll is not ready for completion. EID-2160 Roll not connected. {0} Refer to error messge text. EID-2161 Sibling roll not complete. {0} One of the rolls is not completed for the dual roll. If it is auto roll, it will be completed when a valid signal is detected.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description WID-2175 Extension byte mismatch. {0} WID-2176 Refer to the warning message text. Not all spans have the same OSPF Area ID. This will cause problems with protection switching. To determine the OSPF Area for a given span, click on the span and the OSPF Area will be displayed in the pane to the left of the network map. WID-2178 Only one edit pane can be opened at a time.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2195 The circuit VLAN list cannot be mapped to one spanning tree. Refer to the error message text. You can view the VLAN/Spanning Tree table or reassign VLANs. EID-2196 Unable to relaunch the CTC. {0} There is an error relaunching CTC. EID-2197 CORBA failure. Unable to proceed. There was a CORBA failure, and the task cannot proceed. Verify the Java version.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2218 Bandwidth must be between {0} and {1} percent. The bandwidth must be within the specified parameters. EID-2219 Protection operation failed, XC loopback is applied on cross-connection. As the protection operation failed, a cross-connect (XC) loopback will be applied on cross-connection. EID-2220 The tunnel status is PARTIAL.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-2328 Circuit reconfigure error. {0} The attempt to reconfigure the specified circuit has failed. EID-2329 {0} of {1} circuits could not be successfully created. A few circuits could not be created. EID-2330 Circuit verification: selected {0} invalid! The selected item, specified by {0}, is invalid as per the details, specified in {1}.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3021 An error was encountered while retrieving the diagnostics: {0} Refer to the error message text. EID-3022 Requested action not allowed. The requested action is not allowed. EID-3023 Unable to retrieve low order cross connect mode. Refer to the error message text. EID-3024 Unable to switch {0} cross connect mode. EID-3025 Error while retrieving thresholds.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3050 An exception was caught trying to save the file to your local file Check whether the file already exists and system. cannot be over written, or there isa space constraint in the file system. EID-3051 The maximum size for a config file in bytes is: {0} The size of the configuration file should not exceed the specified number of bytes.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3072 Clear Learned Address Failure attempting to clear the learned MAC address from a specific card or Ether group. EID-3073 Clear Selected Rows Failure attempting to clear the learned MAC address from a specific card or Ether group. EID-3074 Clear By {0} Error encountered trying to clear the learned MAC address from either a VLAN or a port.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3097 The ring termination is in use. The ring termination you are trying to access is in use. Try after sometime. EID-3098 No ring terminations selected. Select one of the ring terminations. EID-3099 Sorry, entered key does not match existing authentication key. Check the authentication key and reenter. EID-3100 Error encountered during authentication.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3120 No object of type {0} selected to delete. Choose an object of the specified type to delete. EID-3121 Error Deleting {0} There is an error deleting the item. EID-3122 No object of type {0} selected to edit. Choose an object of the specified type to edit. EID-3123 Error Editing {0} There was an error editing the item. EID-3124 {0} termination is in use.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3144 Max number of static routes exceeded. The number of static routes has exceeded its limit. EID-3145 RIP Metric is not in the range 1-15. The Routing Information Protocol (RIP) metric should be in the range of 1 to 15. EID-3146 Invalid RIP Metric Refer to the error message text. EID-3147 Error creating summary address. There was an error while creating the summary address.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3165 The Ring ID provided is already in use. Ring IDs must be unique Refer to the error message text. EID-3166 Error refreshing {0} table CTC encountered an error while refreshing the specified table. EID-3167 Slot already in use Refer to the error message text. EID-3168 Provisioning Error An error was encountered while attempting the specified provisioning operation.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3214 Could not get number of HOs for line. The number of High Orders (STS/STM) for the line is not available. EID-3215 Error in refreshing. Used frequently in pane classes to indicate a general error condition when trying to refresh from the model. EID-3216 Invalid proxy port. Refer to the error message text. EID-3217 Could not refresh stats.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3237 Database Backup failed. {0} CTC failed to backup the specified database. EID-3238 Send PDIP setting on {0} is inconsistent with that of control node {1} The send payload defect indicator path (PDI-P) setting on the specified item should be consistent with that of the specified control node. EID-3239 The overhead termination is invalid Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description WID-3256 Could not assign timing reference(s) because - at least one timing reference has already been used and/or - a timing reference has been attempted to be used twice. Please verify the settings. Refer to the warning message text. EID-3257 Duplicate DCC number detected: {0}. CTC detected more than one occurene of the a DCC number. Remove one of them.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description WID-3275 Make sure the Remote Interface ID and the Local Interface ID Refer to the warning message text. on the two sides are matched. (Local Interface ID on this node should equal Remote Interface ID on the neighbor node and vice-versa.) WID-3276 Both {0} and {1} exist on the same selected port. {2} WID-3277 The description cannot contain more than {0} characters.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3294 No RMON thresholds available for selected port. Refer to the error message text. EID-3295 This card does not support RMON thresholds. Refer to the error message text. EID-3296 Buffer-to-buffer credit is only supported for Fibre Channel (FC) Refer to the error message text. and FICON. EID-3298 ALS Auto Restart is not supported by this interface.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3323 APC system is busy. Automatic Power Control (APC) system is busy. EID-3324 No path to regulate. There is no circuit path to regulate. EID-3325 Requested action not allowed. Generic DWDM provisioning failure message. EID-3326 Wrong input value. The input value is incorrect. EID-3327 Error in getting thresholds. There was an error retrieving the thresholds.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3353 There is no such interface available. The interface specified is not present in CTC. EID-3354 Specified endpoint is in use. Select another endpoint that is not in use. EID-3355 Specified endpoint is incompatible. Refer to the error message text. EID-3357 Unable to calculate connections. Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3383 GFP Buffers Available must be between {0} and {1} and may be increased in increments of {2}. WID-3384 You are about to force the use of Secure Mode for this chassis. Refer to the warning message text. You will not be able to undo this operation. OK to continue? EID-3385 {0}. Delete circuits, then try again. Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-3402 Unable to complete the switch request. The {0} card is either not present or is not responding. Try again after ensuring that the {0} card is present and is not resetting. Refer to the error message text. EID-3403 Admin state transition has not been attempted on the monitored Refer to the error message text. port.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-4011 Provisioning error: {0} Refer to the error message text. EID-5000 Cannot find a valid route for tunnel change request. Refer to the error message text. EID-5001 Tunnel could not be changed. Refer to the error message text. EID-5002 Tunnel could not be restored and must be recreated manually. Refer to the error message text. EID-5003 Circuit roll failure.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-5018 {0} is {1} node and cannot be added to {2} network. You cannot add the node {0} of type {1} to the host node of type {2}. This prevents you from hosting both SONET and SDH nodes in the same session. EID-5019 Manual mode for this equipment does not support an expected The path trace mode does not support string consisting of all null characters.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-5033 Unable to load profile. Error decoding characters. CTC detected an error while decoding characters and could not load the profile. EID-5034 Unable to load profile. File format error. CTC detected an error and could not load the profile. EID-5035 Unable to load profile. File read error. CTC could not read the file and is therefore unable to load the profile.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description WID-5051 Unable to transition port state indirectly because the port aggregates OCH CC circuits: if the port state should be changed, edit it directly via port provisioning Refer to the warning message text. EID-5052 The operation is not valid for the connection type You may have selected the incorrect switch.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6006 Could not assign timing references: - NE reference can only be used if timing mode is LINE. - A BITS reference can only be used if timing mode is not LINE. - A line reference can only be used if timing mode is not EXTERNAL. Refer to the error message text. EID-6008 SF BER and SD BER are not provisionable on the protect line Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6024 The destination of a {0} route cannot be a class D (224.0.0.0/4) The destination of a static route must not be or class E (240.0.0.0/4) address. a class D or class E address. EID-6025 The destination of a {0} route cannot be a class A broadcast address (x.255.255.255/8) The destination of a static route must not be a class A broadcast address. It should be (xxx.0.0.0).
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6049 Mode {0} is not supported. CTC does not support the mode of operation requested on the card. EID-6050 Some {0} terminations were not {1}d. {2} Refer to the error message text. WID-6051 All {0} terminations were {1}d successfully. {2} Refer to the warning message text. EID-6052 The authentication key can not be blank. Enter an authentication key.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6074 End System mode only supports one subnet. Refer to the error message text. EID-6075 Trying to remove MAT entry that does not exit. CTC is removing the MAT entry. EID-6076 Cannot {0} TARP manual adjacency entry: {1} CTC cannot add the specified adjacency entry for reasons unknown. EID-6077 Area address shall be 1 to 13 bytes long.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6097 The authorization key does not comply with IOS password restrictions. {0} Specify another authorization key. EID-6098 Default static route is not allowed when default IP Over CLNS Refer to the error message text. tunnel exists EID-6099 You cannot create a subnet on a disabled router. Create the subnet on an active router.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6113 Cannot delete shelf, {0} One or more of the equipment modules (provisioned virtual links, provisioned server trails, provisioned protection groups, or provisioned DCCs) in the shelf is currently in use. Delete cards from all the slots and try again. EID-6114 The maximum number of supported shelves have already been Refer to the error message text. provisioned.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error Warning ID Error Warning Message Description EID-6137 Cannot disable multishelf. Multishelf is not supported on equipment, is already disabled, or modules on the shelf are currently in use. EID-6138 Invalid LAN configuration. Verify the LAN configuration. EID-6139 Invalid card(s) present. Please remove all non-MSTP cards and try again. Non-DWDM cards cannot be added to an a DWDM node. Remove the cards.
INDEX list of Minor Numerics 1+1 optical port protection, deleting 2-76 15310-CL-CTX card line alarms resetting 2-146 2-153 list of Not-Alarmed conditions 2-4 list of Not-Reported conditions 2-6 logical objects 2-9 service effect 2-17 severities states TL1 A 2-3 2-14 2-17 2-1 troubleshooting ADMIN-DISABLE ALS description 3-4 ADMIN-DISABLE-CLR ADMIN-LOCKOUT ADMIN-LOGOUT AMI coding 3-4 2-86, 2-87 APSB description APSCDFLTK 3-4 ADMIN-SUSPEND-CLR APSC-IMP 3-5 2-20 2-20 2-20 AP
Index byte failure BKUPMEMP description 2-20 channel failure on protect card channel mismatch BLSR 2-64 Force Span condition 2-21 mode mismatch failure 2-23 path protection alarms 2-28, 2-29, 2-30, 2-31 cannot launch CTC after removing Netscape 2-31 cannot launch Java reconfiguring 2-27 AUTOSW 1-48 1-49 stalls during download AUTOSW-AIS description supported by CTC 2-28 AUTOSW-LOP (STSMON) description 2-28 AUTOSW-LOP (VT-MON) description 2-29 AUTOSW-LOP description AUTOSW-PDI des
Index generic procedures LED behavior after insertion 2-155 identifying circuit state testing 1-64 identifying failure points on electrical identifying failure points on optical path-in-use error repairing rolled 1-35, 1-38 correcting the CTC core version build 1-3 CRC 1-14 PARTIAL status remains unchanged 1-58, 1-59 2-32 creating 1-64 cross-connect loopback on a source-node OC-N port 1-16 1-62 1-64 DCC terminations 2-121 VT1.
Index does not launch gray node icon list of alarms login errors limitations with OC-3 1-54 two-DCC requirement during facility loopback 1-57 verifying DCC terminations 2-1 loss of TCP/IP connection circuits 2-35 node view to network view change unsuccessful release interoperability problems requirements for Windows PC 2-155 CTC cache 1-52 1-59 requirements for UNIX workstation 1-46 1-55 DCC terminations 2-76 protection groups 2-76 designing IP subnets 1-46 setting Internet Explorer
Index See also DS1-84/DS3-EC1-3 card initiating a path protection lockout resetting initiating a path protection Manual switch 2-153 electrical circuits.
Index FE-LOCKOUTOFPR-SPAN FE-LOF description 2-63 FE-LOS description 2-63 2-62 H hairpin circuit FE-MANWKSWBK-SPAN 2-63 creating on a destination-node electrical port FE-MANWKSWPR-SPAN 2-64 creating on a source-node electrical port FEPRLF description definition 2-64 fiber and cabling errors testing 1-69 fiber-optic connections, faulty firewall, invalid port number FIREWALL-DIS flash manager 1-8, 1-11 half-duplex 1-69 hard reset 4-11 HDLC 3-5 2-55 2-153 2-47 HELLO description 2-
Index 1:1 card switch (ONS 15310-MA only) lock-on 2-149 lockout 2-150 2-150 KB-PASSTHR path protection Force switch path protection lockout 2-81 2-151 2-152 path protection manual switch L 2-151 Internet Explorer lamp test See also browser 1-75 LAN cable setting as the default CTC browser crimping 1-52 interoperability between CTC releases INTRUSION K 1-71 damaged cable 1-59 faulty cable 3-6 INTRUSION-PSWD laser bias 3-6 INTRUSION-PSWD description 1-69 2-70, 2-90 LASEREOL
Index LOF (OCN) 2-88 LOF (STSTRM) LOF (STSTRM) LOGBUFR90 2-88 2-88 2-94 LOS (DS3) 2-95 LOS (EC1) 2-96 LOS (FUDC) 2-89 LOGBUFROVFL LOS (DS1) LOS (OCN) 2-89 login errors 2-97 2-98 loss of pointer. See LOP browser login does not launch Java browser stalls when downloading JAR file corrupt cache file loss of signal.
Index MEA (FAN) description 2-110 clearing a loopback MEA (PPM) description 2-110 OC-3 and DCC limitations MEM-GONE description MEM-LOW description OOU-TPT description 2-111 OSPF hello 2-111 mismatch between received and expected C2 byte ML-100T-8 card replacing 2-154 reseating 2-154 resetting 2-153 1-66 2-112 OPEN-SLOT description 2-111 MFGMEM description 2-156 2-113 2-69 2-47 P password incorrect startup configuration error 2-53 2-78 mismatch with username modifying.
Index facility loopback on a source-node Ethernet port facility loopback on a source-node OC-N port hairpin on a destination-node electrical port hairpin on a source-node electrical port 1-29 redirecting the CTC cache removing the NIC card 1-14 repairing circuits 1-10 1-6 terminal loopback on a destination-node electrical port 1-8 2-154 reseating cards 2-154 resetting terminal loopback on a destination-node OC-N port 1-24 ping controller cards 2-153 electrical cards 2-153 Ethernet cards
Index SF description SWTOPRI description 2-125 2-134 SF-L description 2-126 SWTOSEC description SF-P description 2-126 SWTOTHIRD description SF-V description 2-127 SYNC-FREQ description SFTWDOWN description SFTWDOWN-FAIL SF-V description signal failure soft reset SYNCPRI description SYSBOOT description SQUELCH 2-129 TCP/IP failure 1-50, 2-35 Telcordia 2-128 signal degrade definition SSM degrade 2-137 T 2-127 2-128 SQUELCHED 2-137 2-128 2-153 SQM description 2-136 SYNCTHIR
Index See also power switch error cross-connect loopback circuit TIM-MON 1-16 1-67 2-139 electrical cabling 1-6, 1-13 TIM-P description 2-139 electrical circuits 1-4 TIM-S description 2-139 TIM-V description 2-140 Ethernet cards 1-30, 1-33, 1-41, 1-44 Ethernet facility loopback circuit Ethernet terminal loopback circuit facility loopback circuit hairpin circuit 1-5, 1-13, 1-15, 1-20, 1-23, 1-29 transient conditions alphabetical list characteristics 1-2 to 1-3 OC-N (controller) card
Index V VCCG-DOWN description VCG-DEG description 2-145 2-144 verifying BER threshold level DCC terminations passwords 2-155 2-155 1-60 Windows PC connection to the node VirusScan 1-50 1-53, 1-54 voltage. See battery VT1.5 creation error 1-66 VT-SQUELCH-L description 2-145 W warnings definition xxviii WKSWBK 3-8 WKSWPR 3-9 WKSWPR description WRMRESTART 3-9 WTR description 2-146 2-146 Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
Index Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.
