Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide Product and Documentation Release 9.0 August 2012 Americas 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 Preface xxvii Revision History xxvii Document Objectives Audience xxviii xxviii Related Documentation xxviii Document Conventions xxix Obtaining Optical Networking Information xxxv Where to Find Safety and Warning Information xxxv Cisco Optical Networking Product Documentation CD-ROM Obtaining Documentation and Submitting a Service Request CHAPTER 1 General Troubleshooting xxxv xxxv 1-1 1.1 Network Troubleshooting Tests 1-2 1.1.1 Facility Loopback 1-2 1.1.
Contents Create the Hairpin Loopback Circuit on the Destination-Node Port Test the Hairpin Circuit 1-14 1.2.6 Perform a Facility Loopback on a Destination Port 1-14 Create a Facility Loopback Circuit on a Destination Port 1-14 Test the Facility Loopback Circuit 1-15 Test the Electrical Cabling 1-16 1-13 1.3 Identify Points of Failure on an OC-N Circuit Path 1-16 1.3.
Contents Test the Ethernet Card 1-32 1.6.2 Perform a Terminal Loopback on a Source-Node Ethernet Port 1-33 Create the Terminal Loopback on a Source-Node Ethernet Port 1-33 Test and Clear the Ethernet Terminal Loopback Circuit 1-35 Test the Ethernet Card 1-35 1.6.
Contents 1.7.3.3 Provision the Handheld Receiver and Perform Automatic Mode Testing 1.7.3.4 View Automatic Mode Test Results During the Test 1-60 1.7.4 Retrieving Test Results from Automatic Tests 1-61 1.7.4.1 Reviewing the Results on the Handheld Receiver Screen 1-62 1.7.4.2 Sending the Results to a Computer 1-62 1.7.5 Perform Loop Tests 1-62 1.8 Restore the Database and Default Settings 1.8.1 Restore the Node Database 1-63 1-60 1-63 1.9 PC Connectivity Troubleshooting 1-63 1.9.
Contents 1.10.9 Username or Password Does Not Match the Port Information Verify Correct Username and Password 1-77 1.10.10 Superuser Password Needs to Be Reset 1-77 Reset the ONS 15310-CL or ONS 15310-MA Password 1-78 1.10.11 No IP Connectivity Exists Between Nodes 1-78 1.10.12 DCC Connection Lost 1-79 1.10.13 “Path in Use” Error When Creating a Circuit 1-79 Cancel the Circuit Creation and Start Over 1-79 1.10.14 Calculate and Design IP Subnets 1-80 1.11 Circuits and Timing 1-80 1.11.
Contents 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-10 2.4 Alarm List by Logical Object Type 2-12 2.5 Trouble Notifications 2-16 2.5.1 Alarm Characteristics 2-16 2.5.2 Condition Characteristics 2-16 2.5.3 Severities 2-17 2.5.4 Alarm Hierarchy 2-17 2.5.5 Service Effect 2-19 2.5.6 States 2-19 2.6 Safety Summary 2-19 2.7 Alarm Procedures 2-20 2.7.
Contents Clear the APS-PRIM-FAC Condition 2-27 2.7.16 APS-PRIM-SEC-MISM 2-27 Clear the APS-PRIM-SEC-MISM Alarm 2-27 2.7.17 AS-CMD 2-27 Clear the AS-CMD Condition 2-28 2.7.18 AS-MT 2-29 Clear the AS-MT Condition 2-29 2.7.19 AS-MT-OOG 2-29 2.7.20 AUD-LOG-LOSS 2-29 Clear the AUD-LOG-LOSS Condition 2-29 2.7.21 AUD-LOG-LOW 2-30 2.7.22 AUTOLSROFF 2-30 2.7.23 AUTORESET 2-30 Clear the AUTORESET Alarm 2-30 2.7.24 AUTOSW-AIS 2-31 Clear the AUTOSW-AIS Condition 2-31 2.7.
Contents Clear the CARLOSS (EQPT) Alarm 2-39 2.7.39 CARLOSS (ML100T) 2-40 Clear the CARLOSS (ML100T) Alarm 2-41 2.7.40 CLDRESTART 2-41 Clear the CLDRESTART Condition 2-42 2.7.41 COMIOXC 2-42 Clear the COMIOXC Alarm 2-42 2.7.42 CONTBUS-CLK-A 2-43 Clear the CONTBUS-CLK-A Alarm 2-43 2.7.43 CONTBUS-CLK-B 2-43 Clear the CONTBUS-CLK-B Alarm 2-43 2.7.44 CONTBUS-DISABLED 2-44 Clear the CONTBUS-DISABLED Alarm 2-44 2.7.45 CONTBUS-IO-A 2-45 Clear the CONTBUS-IO-A Alarm 2-45 2.7.46 CONTBUS-IO-B 2-45 2.7.
Contents Clear the ENCAP-MISMATCH-P Alarm 2-54 2.7.60 EOC 2-54 Clear the EOC Alarm 2-55 2.7.61 EOC-L 2-56 Clear the EOC-L Alarm 2-57 2.7.62 EQPT 2-57 Clear the EQPT Alarm 2-57 2.7.63 EQPT-MISS 2-58 2.7.64 ERFI-P-CONN 2-58 Clear the ERFI-P-CONN Condition 2-58 2.7.65 ERFI-P-PAYLD 2-59 Clear the ERFI-P-PAYLD Condition 2-59 2.7.66 ERROR-CONFIG 2-59 Clear the ERROR-CONFIG Alarm 2-59 2.7.67 ETH-LINKLOSS 2-60 Clear the ETH-LINKLOSS Condition 2-61 2.7.68 EXCCOL 2-61 Clear the EXCCOL Alarm 2-61 2.7.
Contents 2.7.81 FE-EQPT-NSA 2-67 Clear the FE-EQPT-NSA Condition 2-67 2.7.82 FE-FRCDWKSWBK-SPAN 2-67 Clear the FE-FRCDWKSWBK-SPAN Condition 2-67 2.7.83 FE-FRCDWKSWPR-SPAN 2-68 2.7.84 FE-IDLE 2-68 Clear the FE-IDLE Condition 2-68 2.7.85 FE-LOCKOUTOFPR-SPAN 2-68 2.7.86 FE-LOF 2-68 Clear the FE-LOF Condition 2-68 2.7.87 FE-LOS 2-69 Clear the FE-LOS Condition 2-69 2.7.88 FE-MANWKSWBK-SPAN 2-69 2.7.89 FE-MANWKSWPR-SPAN 2-69 2.7.90 FEPRLF 2-69 Clear the FEPRLF Alarm 2-70 2.7.
Contents Clear the HIBATVG Alarm 2-76 2.7.107 HI-LASERBIAS 2-76 Clear the HI-LASERBIAS Alarm 2-76 2.7.108 HI-LASERTEMP 2-77 Clear the HI-LASERTEMP Alarm 2-77 2.7.109 HI-RXPOWER 2-78 Clear the HI-RXPOWER Alarm 2-78 2.7.110 HITEMP 2-78 Clear the HITEMP Alarm 2-78 2.7.111 HI-TXPOWER 2-78 Clear the HI-TXPOWER Alarm 2-79 2.7.112 HLDOVRSYNC 2-79 Clear the HLDOVRSYNC Alarm 2-80 2.7.113 I-HITEMP 2-80 Clear the I-HITEMP Alarm 2-80 2.7.114 IMPROPRMVL 2-81 Clear the IMPROPRMVL Alarm 2-81 2.7.115 INC-ISD 2-82 2.7.
Contents 2.7.130 LCAS-TX-DNU 2-90 2.7.131 LINK-KEEPALIVE 2-90 Clear the LINK-KEEPALIVE Alarm 2-91 2.7.132 LKOUTPR-S 2-91 Clear the LKOUTPR-S Condition 2-91 2.7.133 LOA 2-91 Clear the LOA Alarm 2-92 2.7.134 LOCKOUT-REQ 2-92 Clear the LOCKOUT-REQ Condition 2-92 2.7.135 LOF (BITS) 2-92 Clear the LOF (BITS) Alarm 2-93 2.7.136 LOF (DS1) 2-93 Clear the LOF (DS1) Alarm 2-94 2.7.137 LOF (DS3) 2-94 Clear the LOF (DS3) Alarm 2-94 2.7.138 LOF (EC1) 2-95 Clear the LOF (EC1) Alarm 2-95 2.7.
Contents Clear the LOS (DS3) Alarm 2-103 2.7.152 LOS (EC1) 2-104 Clear the LOS (EC1) Alarm 2-104 2.7.153 LOS (FUDC) 2-105 Clear the LOS (FUDC) Alarm 2-105 2.7.154 LOS (OCN) 2-106 Clear the LOS (OCN) Alarm 2-106 2.7.155 LO-TXPOWER 2-107 Clear the LO-TXPOWER Alarm 2-107 2.7.156 LPBKCRS 2-108 Clear the LPBKCRS Condition 2-108 2.7.157 LPBKDS3FEAC 2-108 Clear the LPBKDS3FEAC Condition 2-109 2.7.158 LPBKDS3FEAC-CMD 2-109 2.7.
Contents Clear the MANUAL-REQ-SPAN Condition 2-115 2.7.175 MATECLK 2-116 Clear the MATECLK Alarm 2-116 2.7.176 MEA (EQPT) 2-116 Clear the MEA (EQPT) Alarm 2-116 2.7.177 MEA (FAN) 2-117 2.7.178 MEA (PPM) 2-118 2.7.179 MEA (SHELF) 2-118 2.7.180 MEM-GONE 2-118 2.7.181 MEM-LOW 2-118 2.7.182 MFGMEM 2-118 2.7.183 NO-CONFIG 2-119 Clear the NO-CONFIG Condition 2-119 2.7.184 NON-CISCO-PPM 2-119 Clear the NON-CISCO-PPM Condition 2-120 2.7.185 NOT-AUTHENTICATED 2-120 2.7.
Contents Clear the RFI-P Condition 2-127 2.7.200 RFI-V 2-127 Clear the RFI-V Condition 2-128 2.7.201 ROLL 2-128 2.7.202 ROLL-PEND 2-129 2.7.203 ROUTE-OVERFLOW 2-129 Clear the ROUTE-OVERFLOW Condition 2-129 2.7.204 RPR-PASSTHR 2-129 2.7.205 RPRW 2-129 Clear the RPRW Condition 2-130 2.7.206 RUNCFG-SAVENEED 2-130 2.7.207 SD 2-130 Clear the SD (DS1, DS3) Condition 2-131 2.7.208 SD-L 2-132 Clear the SD-L Condition 2-132 2.7.209 SD-P 2-133 Clear the SD-P Condition 2-133 2.7.
Contents 2.7.224 SSM-PRS 2-139 2.7.225 SSM-RES 2-139 2.7.226 SSM-SDH-TN 2-139 2.7.227 SSM-SETS 2-139 2.7.228 SSM-SMC 2-139 2.7.229 SSM-ST2 2-140 2.7.230 SSM-ST3 2-140 2.7.231 SSM-ST3E 2-140 2.7.232 SSM-ST4 2-140 2.7.233 SSM-STU 2-141 Clear the SSM-STU Condition 2-141 2.7.234 SSM-TNC 2-141 2.7.235 SW-MISMATCH 2-141 Clear the SW-MISMATCH Condition 2-141 2.7.236 SWMTXMOD-PROT 2-142 Clear the SWMTXMOD-PROT Alarm 2-142 2.7.237 SWMTXMOD-WORK 2-142 Clear the SWMTXMOD-WORK Alarm 2-142 2.7.238 SWTOPRI 2-143 2.7.
Contents Clear the TIM-V Alarm 2-149 2.7.251 TPTFAIL 2-149 Clear the TPTFAIL Alarm 2-149 2.7.252 TX-AIS 2-150 Clear the TX-AIS Condition 2-150 2.7.253 TX-LOF 2-150 Clear the TX-LOF Condition 2-150 2.7.254 TX-RAI 2-151 Clear the TX-RAI Condition 2-151 2.7.255 UNEQ-P 2-151 Clear the UNEQ-P Alarm 2-151 2.7.256 UNEQ-V 2-153 Clear the UNEQ-V Alarm 2-153 2.7.257 UNQUAL-PPM 2-153 Clear the UNQUAL-PPM Condition 2-153 2.7.258 VCG-DEG 2-154 Clear the VCG-DEG Condition 2-154 2.7.
Contents 2.10.2 CTC Card Resetting and Switching 2-162 Soft- or Hard-Reset an Ethernet or Electrical Card in CTC 2-162 Soft- or Hard-Reset a Controller Card 2-162 2.10.3 Physical Card Reseating and Replacement 2-163 Remove and Reinsert (Reseat) a Card 2-163 Physically Replace a Card 2-163 2.10.
Contents 3.3.18 3.3.19 3.3.20 3.3.21 3.3.22 3.3.23 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 3.3.36 3.3.37 3.3.38 3.3.39 3.3.
Contents Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
F I G U R E S Figure 1-1 Accessing FEAC Functions on the DS1 ports of WBE-28/WBE-84 Cards Figure 1-2 Diagram of FEAC Circuit Figure 1-3 Accessing FEAC Functions on the DS3 ports of WBE-28/WBE-84 Cards Figure 1-4 Diagram of FEAC Circuit Figure 1-5 Accessing Far End troubleshooting Functions on the WBE Cards Figure 1-6 Hairpin Loopback on a Source-Node Ethernet Port Figure 1-7 Hairpin on a Destination-Node Ethernet Port Figure 1-8 TST-DSX and Remote Receiver Faceplates Figure 1-9 Handheld Re
Figures Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
T A B L E S Table 1-1 Messages and Probable Indications Table 1-2 Automatic Test Mode Results Table 1-3 Restore the Node Database Table 1-4 Unable to Verify the IP Configuration of Your Microsoft Windows PC Table 1-5 Browser Login Does Not Launch Java Table 1-6 Unable to Verify the NIC Connection on Your Microsoft Windows PC Table 1-7 Verify Microsoft Windows PC Connection to ONS 15310-CL or ONS 15310-MA (Ping) Table 1-8 Unable to Launch CTC Help After Removing Netscape Table 1-9 Unable to
Tables Table 1-31 Blinking STAT LED on Installed Card Table 1-32 Bit Errors Appear for a Line Card Table 1-33 Faulty Fiber-Optic Connections Table 1-34 LAN Cable Pinout Table 1-35 Cross-Over Cable Pinout 1-89 Table 1-36 Power Supply Problems 1-90 Table 1-37 Power Consumption for Node and Cards Table 1-38 Lamp Test for Optical and Electrical Card LEDs Table 1-39 Diagnostic Files Retrieved Based on User Privilege Table 1-40 List of Diagnostic Files Table 2-1 ONS 15310-CL and ONS 15310-
Preface 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.
Preface Date Notes June 2010 Updated the table “Alarm Logical Object Type Definitions” in the chapter “Alarm Troubleshooting”. July 2010 Updated table in Chapter Error Messages. February 2012 Updated the section “IMPROPRMVL” in the chapter “Alarm Troubleshooting”. August 2012 The full length book-PDF was generated.
Preface • Release Notes for the Cisco ONS 15310-MA Release 9.0 Provides caveats, closed issues, and new feature and functionality information. Refer to the following standards documentation referenced in this publication: • Telcordia GR-253 CORE For an update on End-of-Life and End-of-Sale notices, refer to http://www.cisco.com/en/US/products/hw/optical/ps2001/prod_eol_notices_list.html.
Preface Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.
Preface Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti. Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
Preface 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. Use o número da declaração fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham o dispositivo.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
Preface 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 and Submitting a Service Request section. Where to Find Safety and Warning Information For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
CH 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 Network Troubleshooting Tests • 1.8 Restore the Database and Default Settings—Explains how to restore software data and restore the node to the default setup. • 1.9 PC Connectivity Troubleshooting—Provides troubleshooting procedures for Microsoft Microsoft Windows PC and network connectivity to the ONS 15310-CL or ONS 15310-MA. • 1.10 CTC Operation Troubleshooting—Provides troubleshooting procedures for Cisco Transport Controller (CTC) login or operation problems.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path 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 Identify Points of Failure on an Electrical Circuit Path The tests in this section can be used to test DS-1, DS-3, or EC-1 circuits on a path protection configuration. 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 Identify Points of Failure on an Electrical Circuit Path 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 Identify Points of Failure on an Electrical Circuit Path 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 Identify Points of Failure on an Electrical Circuit Path 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 Identify Points of Failure on an Electrical Circuit Path b. If you are starting the current procedure without the electrical test set connected to the port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the connectors for the electrical port you are testing. Step 2 Adjust the test set accordingly. Step 3 Use CTC to set up the terminal loopback circuit on the port being tested: Step 4 Step 5 a.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path Test the Terminal Loopback Circuit on the Destination-Node Port 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 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 Identify Points of Failure on an Electrical Circuit Path DS1 Inhibit FEAC Backplane Loopback DS1 ports initiate loopbacks when they receive FEAC loop codes. If the Inhibit FE Backplane Lbk check box is checked for a DS1 port, that port ignores any FEAC loop codes it receives and will not loop back (return them). Create the NIU Loopback on a Destination-Node DS1 Port Step 1 Connect a test set to the near end DS1 port.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path Figure 1-1 d. Step 6 Accessing FEAC Functions on the DS1 ports of WBE-28/WBE-84 Cards Click Apply. Send activate loop codes from the test set. The destination port senses the loop codes form the test set and creates NIU terminal loopback on that port. It is normal for a 2.7.164 LPBKTERMINAL (DS1, DS3) condition to appear during a loopback setup. The condition clears when you remove the loopback.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path Step 7 Complete the "Test and Clear the DS1 NIU Loopback Circuit" procedure. Test and Clear the DS1 NIU 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 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 Identify Points of Failure on an Electrical Circuit Path 1.2.5 Perform a Hairpin Test on a Destination-Node Port The hairpin test is performed on the port in the destination node. To perform this test, you must also create a bidirectional circuit in the transmit direction from the destination ONS 15310-CL or ONS 15310-MA to the source node.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path Step 7 Verify that the circuits connect to the correct slots. For example, verify that source node OC-N port (east slot) is connected to the destination node (west slot). If two east slots or two west slots are connected, the circuit does not work. Except for the distinct slots, all other circuit information, such as ports, should be identical.
Chapter 1 General Troubleshooting Identify Points of Failure on an Electrical Circuit Path c. Step 2 Adjust the test set accordingly. 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. Select Facility from the Loopback Type column for the port being tested.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Test the Electrical Cabling Step 1 Replace the suspect cabling (the cables from the test set to the DS-1, DS-3, or EC-1 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 Identify Points of Failure on an OC-N Circuit Path Note The test sequence for your circuits differs according to the type of circuit and network topology. Note Facility and terminal loopback tests require on-site personnel. 1.3.1 Perform a Facility Loopback on a Source-Node OC-N Port The facility loopback test is performed on the node source port in the network circuit, in this example, the source 15310-CL-CTX or CTX2500 card OC-N port in the source node.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path h. Choose None from the Loopback Type column for the port being tested. i. Choose the appropriate state (IS,AINS; OOS,DSBLD; or OOS,MT) from the Admin State column for the port being tested. j. Click Apply. k. Click Yes in the confirmation dialog box. l. Continue with the “1.3.2 Perform a Cross-Connect Loopback on the Source OC-N Port” procedure on page 1-18. 1.3.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Test the Cross-Connect 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 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 cross-connect.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path g. Step 3 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit. Note Step 4 Step 5 In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the source node) and click Finish. It is normal for a 2.7.166 LPBKTERMINAL (OCN) condition to appear during a loopback setup. The condition clears when you remove the loopback.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path 1.3.4 Perform a Facility Loopback on an Intermediate-Node OC-N Port The facility loopback test is performed on the node source port in the network circuit, in this example, the source OC-N port in the intermediate node. Completing a successful facility loopback on this port isolates the OC-N port as a possible failure point. Caution Performing a loopback on an in-service circuit is service-affecting.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path f. Click Apply. g. Click Yes in the confirmation dialog box. Note Step 5 It is normal for a 2.7.162 LPBKFACILITY (OCN) condition to appear during loopback setup. The condition clears when you remove the loopback. Continue with the “Test the Facility Loopback Circuit” procedure on page 1-22.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Create the Terminal 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.4 Perform a Facility Loopback on an Intermediate-Node OC-N Port” procedure on page 1-21, leave the optical test set connected to the OC-N port in the source node. b.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path 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. Look for errors or any other signal information that the test set is capable of indicating. If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path c. Step 2 Step 3 Adjust the test set accordingly. Use CTC to set up the facility 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 OCN1toOCN5. 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 Identify Points of Failure on an OC-N Circuit Path Step 3 Step 4 Step 5 Clear the facility loopback: a. Click the Maintenance > Optical > Loopback > Port tabs. b. Choose None from the Loopback Type column for the port being tested. c. Choose the appropriate state (IS,AINS; OOS,DSBLD; or OOS,MT) from the Admin State column for the port being tested. d. Click Apply. e. Click Yes in the confirmation dialog box. Clear the facility loopback circuit: a.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Step 3 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 OC-N 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. It is normal for a 2.7.
Chapter 1 General Troubleshooting Troubleshooting Wideband Electrical Card(WBE-28 and WBE-84 Cards) FEAC on DS3 Ports • Click Delete. • Click Yes in the Delete Circuits dialog box. If no fault is found, the entire OC-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. 1.
Chapter 1 General Troubleshooting Troubleshooting WBE-28 and WBE-84 Cards with Far End Loopcodes on DS1 Ports Figure 1-4 Diagram of FEAC Circuit CE-MR-10 XC OC-N OC-N XC CE-MR-10 159522 Test Set 1.4.1 FEAC Send Code The Send Code column on the WBE-28/WBE-84 cards Maintenance tab only applies to OOS-MA,MT ports configured for CBIT framing. The column lets a user select No Code (the default) or line loop code.
Chapter 1 General Troubleshooting Troubleshooting WBE-28 and WBE-84 Cards with Far End Loopcodes on DS1 Ports Figure 1-5 Note Accessing Far End troubleshooting Functions on the WBE Cards 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.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks 1.6 Troubleshooting Ethernet Circuit Paths With Loopbacks Facility loopbacks, terminal loopbacks, and cross-connect loopback circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. The Tx and Rx terminals connect to the same port. Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.) Step 3 In CTC node view, double-click the CE100T-8 card to display the card view. Step 4 Click the Maintenance > Loopback tabs.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks 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-156.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer. a. If you just completed the “1.6.1 Perform a Facility Loopback on a Source-Node Ethernet Port” procedure on page 1-31, leave the test set hooked up to the Ethernet port in the source node. b.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 6 Complete the “Test and Clear the Ethernet Terminal Loopback Circuit” procedure on page 1-35. 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 Troubleshooting Ethernet Circuit Paths With Loopbacks Step 5 Step 6 Step 7 Clear the terminal loopback on the port before testing the next segment of the network circuit path: a. Double-click the CE100T-8 card with the terminal loopback in the source node. b. Click the Maintenance > Loopback tabs. c. Select None from the Loopback Type column for the port being tested. d.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Create the Hairpin Circuit on the Source-Node Ethernet Port Step 1 Step 2 Connect an Ethernet test set to the port you are testing: a. If you just completed the “1.6.2 Perform a Terminal Loopback on a Source-Node Ethernet Port” procedure on page 1-33, leave the Ethernet test set hooked up to the Ethernet port in the source node. b.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks e. Step 4 Confirm that the hairpin circuit is deleted from the Circuits tab list. Complete the “Test the Standby Cross-Connect Card” procedure on page 1-38. Test the Standby Cross-Connect Card Note Step 1 Two cross-connect cards (active and standby) must be in use on a node to use this procedure. Perform a reset on the Active cross-connect card to make the Standby card Active: a.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks c. From the Cross-Connect Cards menu, choose Switch. d. Click Yes in the Confirm Switch dialog box. Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber. Step 2 Resend test traffic on the loopback circuit.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.) Step 3 Use CTC to set up the facility loopback on the OC-N port: a. In node view, click the Circuits tab and click Create. b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1. c. Click Next. d.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks 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. Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: Step 4 Step 5 a.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 6 Step 7 Clear the facility 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. Do not check any check boxes. Complete the “1.6.5 Perform a Terminal Loopback on Intermediate-Node OC-N Ports” procedure on page 1-42. 1.6.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 4 d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as C1C1toC1C4. e. Leave the Bidirectional check box checked. f. Click Next. g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. h. Click Next. i.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 4 Step 5 b. Click the Maintenance > Optical > Loopback > Port 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. Clear the terminal loopback circuit: a. Click the Circuits tab. b.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 7 c. Click Delete. d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes. Complete the “1.6.6 Perform a Facility Loopback on a Destination-Node Ethernet Port” procedure on page 1-45. 1.6.6 Perform a Facility Loopback on a Destination-Node Ethernet Port You perform a facility loopback test at the destination port to determine whether this local port is the source of circuit trouble.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 4 h. Click Next. i. In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. j. Click Next. k. In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish. Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit. It is normal for the 2.7.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 5 b. Choose the loopback circuit being tested. c. Click Delete. d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes. Complete the “Test the Ethernet Card” procedure on page 1-47. Test the Ethernet Card Step 1 Caution Complete the “Physically Replace a Card” procedure on page 2-163 for the suspected bad card and replace it with a known-good one.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks 1.6.7 Perform a Terminal Loopback on a Destination-Node Ethernet Port The terminal loopback at the destination-node port is the final local hardware error elimination in the circuit troubleshooting process. If this test is completed successfully, you have verified that the circuit is good up to the destination port. Caution Note Performing a loopback on an in-service circuit is service-affecting.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit. It is normal for the “LPKTERMINAL (CE100T, CEMR)” condition on page 2-111 to appear during a loopback setup. The condition clears when you remove the loopback. Note Step 5 Create the terminal loopback on the destination port being tested: a.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. Step 5 If the test set indicates a faulty circuit, the problem might be a faulty card. Step 6 Complete the “Test the Ethernet Card” procedure on page 1-50.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks 1.6.8 Perform a Hairpin Test on a Destination-Node Ethernet Port The hairpin test is performed on the cross-connect card in the network circuit. A hairpin circuit uses the same port as source as well as destination. Completing a successful hairpin through the card isolates the possibility that the cross-connect card is the cause of the faulty circuit.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks h. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. Leave Use Secondary Source unchecked. i. Click Next. j. In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. Leave Use Secondary Destination unchecked. k. Click Next. l.
Chapter 1 General Troubleshooting Troubleshooting Ethernet Circuit Paths With Loopbacks Note Step 2 After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber. Resend test traffic on the loopback circuit. The test traffic now travels through the alternate cross-connect card.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel b. Choose the hairpin circuit being tested. c. Click Delete. d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes. e. Confirm that the hairpin circuit is deleted from the Circuits tab list. The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. 1.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel Figure 1-8 shows the test setup. Figure 1-8 TST-DSX and Remote Receiver Faceplates ONS 15310-MA Shelf TST-DSX POWER TST-DSX Card ACTIVE CAUTION NEW SYSTEM APPLICATION ONLY (TESTING CAN AFFECT TRAFFIC) LOOP DS1 or DS3 Cable Bundles LOOP NORMAL 48VDC DSX Wiring Panel IN OUT Patch Cord DS1 PORT DS3 PORT ONS 15xxx REMOTE RECEIVER DSX WIRING VERIFIC ATION Press "MENU" to select options.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel Figure 1-9 Handheld Receiver Usage Flowchart Note: Command flow for 15454 shelf has other menu options. Power ON TEST SETTINGS MENU Mode:DS1 or DS3 ENTER/ ACCEPT Manual Test Mode DISPLAY (shows stored test result) (DS1 or DS3 port type, Tone On/Off, OK Prompts, Shelf Type, are saved from prior use.) (Display gives continuous test result for port.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel – 75-ohm male BNC connector to LCP connector • DS1 patch cords – 100-ohm male Bantam connector to 100-ohm male Bantam connector – 100-ohm male Bantam connector to 100-ohm 310 connector Step 3 Complete the “1.7.2 Perform Manual Mode Tests” procedure on page 1-57 or the “1.7.3 Perform Automatic Mode Tests” procedure on page 1-59, as needed. 1.7.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel 1.7.2.3 View and Troubleshoot Manual Test Results The handheld receiver screen displays the test result for one DSX port and its DSX wiring, as shown in Table 1-1. Each port is uniquely identified and reported. If a test signal generated from the TST-DSX card is properly detected, the handheld receiver decodes the signal and the screen displays the port type and number and gives an OK indication.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel Table 1-1 General Indication Messages and Probable Indications (continued) Definition and Probable Cause Specific Sample Message Definition and Probable Cause OUTR or REV For DS-1 output wires: Tip and Ring reversal. DS1 => OUT A:10 REV DS 1 output A side, port 10 is detected, but the tip and ring are reversed. WE or WIRE ERR A wiring error is detected.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel 1.7.3.3 Provision the Handheld Receiver and Perform Automatic Mode Testing Step 1 Turn on the handheld receiver and observe the display. Adjust the settings (DS l/DS3 or OK PROMPT) as needed: a. To change from DS-1 to DS-3 or from DS-3 to DS-1, press the MENU key once, use the DISPLAY key to change the selection, and the ENTER/ACCEPT key to save the selection. b.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel Table 1-2 Automatic Test Mode Results Result Meaning GOTO A:15 OUT The next port to be tested is side A, port 15 OUT direction. This prompt is displayed in the upper half of the screen. DS1 OPEN OR NC The handheld receiver does not detect any signal. This message is displayed and alternates on the bottom half of the screen.
Chapter 1 General Troubleshooting Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel 1.7.4.1 Reviewing the Results on the Handheld Receiver Screen At the conclusion of the automatic test or if you press the EXIT TEST key, the handheld receiver enters the manual mode. Press DISPLAY to recall on the screen the last automated test results. Only “failed” ports are shown. Ports that either pass or are untested do not appear on the screen.
Chapter 1 General Troubleshooting Restore the Database and Default Settings introduces insertion loss. Depending on the total insertion loss and the receive sensitivity threshold of the test set, it may not always be possible for a given test set to recover the weakened signal at maximum cable lengths. Step 1 At the ONS 15310-MA shelf, set the TST-DSX card front panel switch to the LOOP position. The LOOP LED turns steady on and the ACTIVE LED blinks.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting 1.9.1 Microsoft Windows PC System Minimum Requirements Workstations running CTC Software R9.0 for the ONS products on Microsoft 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.9.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Note JRE 5.0 for Microsoft Windows and Sun (Solaris, UNIX) is available on Software R9.0 product CDs. 1.9.4 Unsupported Platforms and Browsers Software R9.0 does not support the following platforms: • Microsoft Windows 95 • Sun, Solaris, or UNIX 2.5 • Sun, Solaris, or UNIX 2.6 Software R9.0 does not support the following browsers and JREs: • Netscape 4.73 for Microsoft Windows. • Netscape 4.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Step 4 At the prompt in the DOS window, type ping followed by the IP address shown in the Microsoft Windows IP configuration information. Step 5 Press the Enter key to execute the command. 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.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Reconfigure the Browser Step 1 From the Microsoft 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 PC Connectivity Troubleshooting Table 1-6 Unable to Verify the NIC Connection on Your Microsoft 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 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 CTC Operation Troubleshooting 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 CTC Operation Troubleshooting Step 3 In the System Properties window, click the Advanced tab. 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 CTC Operation Troubleshooting Disable the VirusScan Download Scan Step 1 From the Microsoft 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.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting 1.10.5 Sluggish CTC Operation or Login Problems Symptom You experience sluggish CTC operation or have problems logging into CTC. Table 1-12 describes the potential cause of the symptom and the solution. Table 1-12 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 CTC Operation Troubleshooting Figure 1-10 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 Microsoft Windows Start menu choose Search > For Files or Folders. Step 2 Enter ctc*.jar or cms*.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-13 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.10.8 Different CTC not recognizing each other. Releases Do Not Recognize Each Other” section on page 1-76. Usually accompanied by an INCOMPATIBLE-SW alarm. Correct the username and password as described in the “1.10.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Note CTC will notify you if an older version JRE is running on your Microsoft Windows PC or UNIX workstation. Launch CTC to Correct the Core Version Build Step 1 Exit the current CTC session and completely close the browser. Step 2 Start the browser. Step 3 Type the node IP address of the node that reported the alarm. This can be the original IP address you logged in with or an IP address other than the original.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Step 4 Log into CTC. The browser downloads the JAR file from port. 1.10.9 Username or Password Does Not Match the Port Information Symptom A mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm. Table 1-16 describes the potential causes of the symptom and the solutions.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-17 No IP Connectivity Exists Between Nodes Possible Problem Solution A security breach or record-keeping error has occurred. Reset the node to the default Superuser UID and password combination using the lamp test button. 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.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-18 No IP Connectivity Exists Between Nodes Possible Problem Solution Lost Ethernet connection Usually, this condition is accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in Chapter 8, “CTC Network Connectivity,” of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. 1.10.
Chapter 1 General Troubleshooting Circuits and Timing Step 2 Check the list of available ports. The previously selected port no longer appears in the available list because it is now part of a provisioned circuit. Step 3 Select a different available port and begin the circuit creation process. 1.10.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-21 describes the potential cause of the symptom and the solution.
Chapter 1 General Troubleshooting Circuits and Timing Table 1-22 Circuit in Partial Status Possible Problem Solution During a manual transition, CTC cannot communicate with one of the nodes or one of the nodes is on a version of software that does not support the new state model. Repeat the manual transition operation. If the Partial status persists, determine which node in the circuit is not changing to the desired state. See the “View the State of Circuit Nodes” procedure on page 1-81.
Chapter 1 General Troubleshooting Circuits and Timing 1.11.3 AIS-V on Unused 15310-CL-CTX Card VT Circuits Symptom An incomplete circuit path causes an alarm indications signal (AIS). Table 1-24 describes the potential cause of the symptom and the solution. Table 1-24 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 Circuits and Timing 1.11.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-25 describes the potential causes of the symptom and the solutions. Table 1-25 Circuit Creation Error with VT1.
Chapter 1 General Troubleshooting Circuits and Timing Table 1-27 ONS 15310-CL or ONS 15310-MA Switches Timing Reference Possible Problem Solution The optical or building integrated timing supply The node internal clock operates at a (BITS) input is receiving loss of signal (LOS), loss of Stratum 3 level of accuracy. This gives the frame (LOF), or AIS alarms from its timing source. node a free-running synchronization accuracy of +/–4.
Chapter 1 General Troubleshooting Circuits and Timing 1.11.8 Free-Running Synchronization Mode Symptom The clock is running at a different frequency than normal and the free-running synchronization(2.7.98 FRNGSYNC) alarm appears. Table 1-29 describes the potential cause of the symptom and the solution. Table 1-29 Free-Running Synchronization Mode Possible Problem Solution No reliable reference input is available. The clock is using the internal oscillator as its only frequency reference.
Chapter 1 General Troubleshooting Fiber and Cabling 1.12 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.12.1 Bit Errors Appear for a Traffic Card Symptom A traffic card has multiple bit errors. Table 1-32 describes the potential cause of the symptom and the solution.
Chapter 1 General Troubleshooting Fiber and Cabling 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. Statement 300 Verify Fiber-Optic Connections Step 1 Ensure that a single-mode fiber connects to the ONS 15310-CL or ONS 15310-MA Small form-factor Pluggable (SFP).
Chapter 1 General Troubleshooting Fiber and Cabling 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 Fiber and Cabling LAN Cable Layout 1 2 3 4 1 2 3 4 5 6 5 6 7 8 7 8 55415 Figure 1-12 Table 1-34 shows LAN cable pinouts. Table 1-34 LAN Cable Pinout Pin Color Pair Name Pin 1 White/orange 2 Transmit Data + 1 2 Orange 2 Transmit Data - 2 3 White/green 3 Receive Data + 3 4 Blue 1 — 4 5 White/blue 1 — 5 6 Green 3 Receive Data – 6 7 White/brown 4 — 7 8 Brown 4 — 8 Figure 1-13 shows the layout of a cross-over cable.
Chapter 1 General Troubleshooting Power and LED Tests Table 1-35 Note Cross-Over Cable Pinout (continued) Pin Color Pair Name Pin 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.13 Power and LED Tests This section provides symptoms and solutions for power supply problems, power consumption, and LED indicators. 1.13.
Chapter 1 General Troubleshooting Power and LED Tests Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030 Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94 Caution Operations that interrupt power supply or short the power connections to the system are service-affecting. 1.13.
Chapter 1 General Troubleshooting Power and LED Tests Verify Card LED Operation Step 1 In CTC, click the Maintenance > Diagnostic tabs. Step 2 Click Lamp Test. Step 3 Watch to make sure all the port LEDs illuminate as previously noted for several seconds. Step 4 Click OK on the Lamp Test Run dialog box. With the exceptions previously described, if an OC-N or DS-N LED does not light up, the LED is faulty. Return the defective card to Cisco through the RMA process. Contact Cisco TAC at http://www.
Chapter 1 General Troubleshooting Power and LED Tests Table 1-39 User Privilege Level Retrieve Maintenance Provisioning Superuser Diagnostic Files Retrieved Based on User Privilege Diagnostic File Retrieval Operation • Export the unfiltered alarm table contents • Export the unfiltered conditions table contents • Export the unfiltered history table contents • Export the inventory table contents • CTC Dump Diagnostics log • All Retrieve level access operations • Save the node database •
Chapter 1 General Troubleshooting Power and LED Tests Table 1-40 Step 5 List of Diagnostic Files Diagnostic File Diagnostic File Content AlarmTableLog.html Alarm Table export HistoryTableLog.html Alarm Table export ConditionsTableLog.html Conditions Table export InventoryTableLog.html Inventory Table export AuditTableLog.html Audit Table export CTCDumpDiagLog.txt Audit Table export NodeDiagnostics.bin NodeDiagnostics.gz OBFLDiagnostics.bin OBFLDiagnostics.bin NodeDatabaseBackup.
CH 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 Alarm Index by Default Severity 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 Alarm Index by Default Severity Table 2-2 ONS 15310-CL and ONS 15310-MA Major Alarm List (continued) DATA-CRC (ML100T) LOF (DS1) TIM-V (VT-MON) DUP-SHELF-ID (SHELF) LOM (VT-TERM) TIM-V (VT-TERM) EHIBATVG (PWR) LOP-V (VT-MON) TPTFAIL (CE100T) ELWBATVG (PWR) LOP-V (VT-TERM) TPTFAIL (CEMR) FANDEGRADE (FAN) LOS (DS1) TPTFAIL (ML100T) GFP-CSF (CE100T) MEA (SHELF) UNEQ-V (VT-MON) GFP-CSF (CEMR) MEM-GONE (EQPT) UNEQ-V (VT-TERM) 2.1.
Chapter 2 Alarm Troubleshooting Alarm Index by Default Severity 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 Alarm Index by Default Severity Table 2-4 ONS 15310-CL and ONS 15310-MA NA Conditions List (continued) AUTOSW-SDBER (STSMON) LPBKTERMINAL (DS3) SSM-ST2 (DS1) AUTOSW-SDBER (VT-MON) LPBKTERMINAL (EC1) SSM-ST2 (NE-SREF) AUTOSW-SFBER (STSMON) LPBKTERMINAL (OCN) SSM-ST2 (OCN) AUTOSW-SFBER (VT-MON) MAN-REQ (STSMON) SSM-ST3 (BITS) AUTOSW-UNEQ (STSMON) MAN-REQ (VT-MON) SSM-ST3 (DS1) AUTOSW-UNEQ (VT-MON) MANRESET (EQPT) SSM-ST3 (NE-SREF) CLDRESTART (EQPT) MANSWT
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-4 ONS 15310-CL and ONS 15310-MA NA Conditions List (continued) FRCDSWTOTHIRD (NE-SREF) SD-P (STSTRM) WKSWPR (EQPT) FRNGSYNC (NE-SREF) SD-V (VT-MON) WKSWPR (OCN) FSTSYNC (NE-SREF) SD-V (VT-TERM) WKSWPR (STSMON) FULLPASSTHR-BI (OCN) SF (DS1) WKSWPR (VT-MON) HLDOVRSYNC (NE-SREF) SF (DS3) WTR (EQPT) IDLE (DS1) SF-L (EC1) WTR (OCN) INC-ISD (DS3) SF-L (OCN) WTR (STSMON) INHSWPR (EQPT) SF-P (STSMO
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-6 ONS 15310-CL and ONS 15310-MA Alarm and Condition Alphabetical List (continued) AIS-P (STSTRM) GFP-UP-MISMATCH (CEMR) ROLL-PEND (VT-TERM) AIS-V (VT-MON) GFP-UP-MISMATCH (ML100T) RPR-PASSTHR (RPRIF) AIS-V (VT-TERM) HELLO (OCN) RPRW (ML100T) ALS (OCN) HI-LASERBIAS (OCN) RUNCFG-SAVENEED (EQPT) APC-END (NE) HI-LASERBIAS (PPM) SD (DS1) APSB (OCN) HI-LASERTEMP (OCN) SD (DS3) APSCDFLTK (OCN) HI-LASE
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-6 ONS 15310-CL and ONS 15310-MA Alarm and Condition Alphabetical List (continued) AS-MT (SHELF) LCAS-TX-DNU (VT-TERM) SSM-PRC (BITS) AS-MT-OOG (STSTRM) LINK-KEEPALIVE (ML100T) SSM-PRC (NE-SREF) AS-MT-OOG (VT-TERM) LKOUTPR-S (OCN) SSM-PRC (OCN) AUD-LOG-LOSS (NE) LOA (VCG) SSM-PRS (BITS) AUD-LOG-LOW (NE) LOCKOUT-REQ (OCN) SSM-PRS (DS1) AUTOLSROFF (OCN) LOCKOUT-REQ (STSMON) SSM-PRS (NE-SREF) AUTOR
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-6 ONS 15310-CL and ONS 15310-MA Alarm and Condition Alphabetical List (continued) DATA-CRC (CE100T) LPBKDS3FEAC-CMD (DS3) SSM-STU (BITS) DATA-CRC (ML100T) LPBKFACILITY (CE100T) SSM-STU (DS1) DATAFLT (NE) LPBKFACILITY (CEMR) SSM-STU (NE-SREF) DS3-MISM (DS3) LPBKFACILITY (DS1) SSM-STU (OCN) DUP-IPADDR (NE) LPBKFACILITY (DS3) SSM-TNC (BITS) DUP-NODENAME (NE) LPBKFACILITY (EC1) SSM-TNC (NE-SREF) DUP
Chapter 2 Alarm Troubleshooting Alarm Logical Objects Table 2-6 ONS 15310-CL and ONS 15310-MA Alarm and Condition Alphabetical List (continued) FE-FRCDWKSWPR-SPAN (OCN) OOU-TPT (VT-TERM) TX-AIS (DS3) FE-IDLE (DS3) OPEN-SLOT (EQPT) TX-IDLE (DS1) FE-LOCKOUTOFPR-SPAN (OCN) PDI-P (STSMON) TX-LOF (DS1) FE-LOF (DS3) PDI-P (STSTRM) TX-RAI (DS1) FE-LOS (DS3) PLM-P (STSMON) TX-RAI (DS3) FE-MANWKSWBK-SPAN (OCN) PLM-P (STSTRM) UNEQ-P (STSMON) FE-MANWKSWPR-SPAN (OCN) PLM-V (VT-MON) UNEQ-P (STST
Chapter 2 Alarm Troubleshooting Alarm Logical Objects Table 2-7 Alarm Logical Object Type Definitions Type Definition BITS Building integrated timing supply (BITS) incoming references (BITS-1, BITS-2). BPLANE The backplane. CE100T The CE-100T-8 Ethernet card. CEMR The CE-MR-6 Ethernet card. DS1 A DS-1 port on the 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card. DS3 A DS-3 port on the 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card.
Chapter 2 Alarm Troubleshooting Alarm List by Logical Object Type Table 2-7 Alarm Logical Object Type Definitions (continued) Type Definition VCG Virtual concatenation group. VT-MON VT1 alarm detection at the monitor point (upstream from the cross-connect). Note VT-TERM The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side.
Chapter 2 Alarm Troubleshooting Alarm List by Logical Object Type Table 2-8 ONS 15310-CL and ONS 15310-MA Alarm List by Logical Object as Shown in Alarm Profile (continued) BITS: SSM-ST3E (NA) EXT-SREF: FRCDSWTOSEC (NA) OCN: WKSWPR (NA) BITS: SSM-ST4 (NA) EXT-SREF: FRCDSWTOTHIRD (NA) OCN: WTR (NA) BITS: SSM-STU (NA) EXT-SREF: MANSWTOPRI (NA) PPM: AS-CMD (NA) BITS: SSM-TNC (NA) EXT-SREF: MANSWTOSEC (NA) PPM: AS-MT (NA) BITS: SYNC-FREQ (NA) EXT-SREF: MANSWTOTHIRD (NA) PPM: EQPT (CR) BPLANE:
Chapter 2 Alarm Troubleshooting Alarm List by Logical Object Type Table 2-8 ONS 15310-CL and ONS 15310-MA Alarm List by Logical Object as Shown in Alarm Profile (continued) DS1: LPBKFACILITY (NA) NE: I-HITEMP (CR) STSMON: FORCED-REQ (NA) DS1: LPBKTERMINAL (NA) NE: INTRUSION-PSWD (NA) STSMON: LOCKOUT-REQ (NA) DS1: RAI (NA) NE: SNTP-HOST (MN) STSMON: LOM (CR) DS1: SD (NA) NE: SYSBOOT (MJ) STSMON: LOP-P (CR) DS1: SF (NA) NE-SREF: FRCDSWTOINT (NA) STSMON: LPBKCRS (NA) DS1: SSM-DUS (NA) NE-S
Chapter 2 Alarm Troubleshooting Alarm List by Logical Object Type Table 2-8 ONS 15310-CL and ONS 15310-MA Alarm List by Logical Object as Shown in Alarm Profile (continued) DS3: FE-LOS (NA) OCN: APSCDFLTK (MN) STSTRM: ROLL-PEND (NR) DS3: INC-ISD (NA) OCN: APSCINCON (MN) STSTRM: SD-P (NA) DS3: LOF (CR) OCN: APSCM (MN) STSTRM: SF-P (NA) DS3: LOS (CR) OCN: APSCNMIS (MJ) STSTRM: SQM (CR) DS3: LPBKDS3FEAC (NA) OCN: APSIMP (MN) STSTRM: TIM-P (CR) DS3: LPBKDS3FEAC-CMD (NA) OCN: APS-INV-PRIM (MN
Chapter 2 Alarm Troubleshooting Trouble Notifications Table 2-8 ONS 15310-CL and ONS 15310-MA Alarm List by Logical Object as Shown in Alarm Profile (continued) EQPT: CTNEQPT-PBPROT (CR) OCN: LO-RXPOWER (MN) VT-TERM: LCAS-TX-ADD (NA) EQPT: CTNEQPT-PBWORK (CR) OCN: LOS (CR) VT-TERM: LCAS-TX-DNU (NA) EQPT: EQPT (CR) OCN: LO-TXPOWER (MN) VT-TERM: LOM (MJ) EQPT: ERROR-CONFIG (MN) OCN: LPBKFACILITY (NA) VT-TERM: LOP-V (MJ) EQPT: EXCCOL (MN) OCN: LPBKTERMINAL (NA) VT-TERM: OOU-TPT (NA) EQPT: F
Chapter 2 Alarm Troubleshooting Trouble Notifications 2.5.3 Severities The ONS 15310-CL and ONS 15310-MA use Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are described as follows: • A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs immediate correction.
Chapter 2 Alarm Troubleshooting Trouble Notifications Facility (port) alarms also follow a hierarchy; lower-ranking alarms are closed by higher-ranking alarms. The facility alarm hierarchy used in the systems is shown in Table 2-10. Table 2-10 Facility Alarm Hierarchy Priority Condition Type Highest LOS — LOF — AIS-L — SF-L — SD-L — RFI-L — TIM-S — AIS-P — LOP-P — SF-P — SD-P — UNEQ-P — TIM-P Lowest PLM-P Near-end failures and far-end failures follow different hierarchies.
Chapter 2 Alarm Troubleshooting Safety Summary Table 2-11 Near-End Alarm Hierarchy Priority Condition Type — PLM-V Lowest DS-N AIS (if reported for outgoing DS-N signals) 1. Although it is not defined as a defect or failure, all-ones STS pointer relay is also higher priority than LOP-P. Similarly, all-ones VT pointer relay is higher priority than LOP-V. 2. LOP-P is also higher priority than the far-end failure RFI-P, which does not affect the detection of any near-end failures.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures Generally, an AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when the node sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.4 AIS-V Default Severity: Not Reported (NR), Non-Service-Affecting (NSA) Logical Objects: VT-MON, VT-TERM The AIS VT condition means that this node is detecting AIS in the incoming VT-level path. See the “1.11.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the APSB Alarm Step 1 Use an optical test set to examine the incoming SONET overhead to confirm inconsistent or invalid K bytes. For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15310-CL and ONS 15310-MA.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures Clear the APSIMP Alarm Step 1 Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group. For procedures, refer to the “Turn Up Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the APSMM Alarm Step 1 For the reporting system, in node view verify the protection scheme provisioning by completing the following steps: a. In node view, click the Provisioning > Protection tabs. b. Click the 1+1 protection group configured for the OC-3 or OC-12 ports. The chosen protection group is the protection group that is optically connected (with data communication channel [DCC] connectivity) to the far end. Step 2 Click Edit.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.15 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 Alarm Procedures 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 Alarm Procedures 2.7.18 AS-MT Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: CE100T, CEMR, DS1, DS3, EC1, EQPT, ML100T, OCN 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.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 3 Click Archive. Step 4 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file. Step 5 Enter a name in the File Name field. 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.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 If the reporting card is an ML-100T-8, CE-MR-6, or CE-100T-8 card and automatically resets more than once a month with no apparent cause, complete the “Physically Replace a Card” procedure on page 2-163. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.25 AUTOSW-LOP (STSMON) Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: STSMON The Automatic Path Protection Switch Caused by LOP condition for the STS monitor (STSMON) condition indicates that automatic UPSR switching occurred because of the “LOP-P” alarm on page 2-98. If the UPSR is configured for revertive switching, it reverts to the working path after the fault clears.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic UPSR switching occurred because of a “PDI-P” alarm on page 2-121. If the UPSR is configured for revertive switching, it reverts to the working path after the fault clears. Note This condition is only reported if the path protection is set up for revertive switching.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note This condition is only reported if the path protection is set up for revertive switching. Clear the AUTOSW-SFBER Condition Step 1 Complete the “Clear the SF-P Condition” procedure on page 2-135. 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 Alarm Procedures Clear the AUTOSW-UNEQ (VT-MON) Alarm Step 1 Complete the “Clear the UNEQ-V Alarm” procedure on page 2-153. 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 Alarm Procedures 2.7.33 BERT-ENBL Default Severity: Not Reported (NR), Non-Service-Affecting (NSA) SONET Logical Object: DS1/DS3 The Bert Enabled alarm specifies that the bit error rate testing (BERT) feature is enabled. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.36 BLSROSYNC The BLSROSYNC alarm is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.37 CARLOSS (CE100T, CEMR) Default Severity: Major (MJ), Service-Affecting (SA) SONET Logical Objects: CE100T, CEMR The Carrier Loss alarm is raised on CE-Series cards in Mapper mode when the port is In-Service (IS) state and if there is no carrier signal. Circuit need not be present to raise the alarm. In releases prior to 6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 9 If the alarm does not clear and the “TPTFAIL” alarm on page 2-149 is also reported, complete the “Clear the TPTFAIL Alarm” procedure on page 2-149. If the TPTFAIL alarm is not raised, continue with the next step. When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition could be the CE-Series card's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures f. If one of the circuit sizes is incorrect, complete the “Delete a Circuit” procedure on page 2-164 and reconfigure the circuit with the correct circuit size. Refer to the “Create Circuits” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for detailed procedures to do this. Step 13 If a valid Ethernet signal is present, complete the “Remove and Reinsert (Reseat) a Card” procedure on page 2-163.
Chapter 2 Alarm Troubleshooting Alarm Procedures d. If the rate does not match the actual equipment, you must delete and recreate the selected PPM. Select the PPM, click Delete, then click Create and choose the correct rate for the port rate. Step 2 If the reporting port is an OC-3 or OC-12 port, verify connectivity by pinging the node that is reporting the alarm by completing the procedure in the “1.9.8 Verify Microsoft Windows PC Connection to the Node (Ping)” section on page 1-68.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note • The cable is not properly connected to the near or far port. • Autonegotiation is failing. • The speed (10/100 ports only) is set incorrectly. For information about provisioning 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 Alarm Procedures Clear the CLDRESTART Condition Step 1 If the condition is raised on the controller card, it should clear after booting. If the condition is raised on an Ethernet card, complete the “Remove and Reinsert (Reseat) a Card” procedure on page 2-163. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.42 CONTBUS-CLK-A Default Severity: Minor (MN), Non-Service-Affecting (NSA) for ONS 15310-MA SONET Logical Object: EQPT An Inbound Interconnection Timing Control Bus 1 Failure alarm on the Slot 3 CTX2500 card occurs if the timing signal from the Slot 4 CTX2500 card has an error.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 Complete the appropriate procedure in the “2.10.3 Physical Card Reseating and Replacement” section on page 2-163 for the reporting card. 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).
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures 2.7.47 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. The cross-connect card and the reporting card are no longer communicating through the backplane.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Avoid soft-resetting multiple ONS 15310-MA cards at one time; doing so might cause an unexpected traffic hit. For the LED behavior, see the “2.9.2 Typical Card LED Activity During Reset” section on page 2-156. Step 8 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures The Software Data Integrity Fault alarm occurs when the 15310-CL-CTX card or CTX2500 card exceeds its flash memory capacity. Clear the DATAFLT Alarm Step 1 Caution Step 2 Complete the “Soft- or Hard-Reset a Controller Card” procedure on page 2-162. Avoid soft-resetting multiple ONS 15310-MA cards at one time; doing so might cause an unexpected traffic hit. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures SONET Logical Object: SYSTEM The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm is cleared when CTC is reconnected to the node. Clear the DISCONNECTED Alarm Step 1 Restart the CTC application. 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). 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Duplicate IP Address alarm indicates that the alarmed node IP address is already in use within the same DCC area. When this happens, CTC no longer reliably connects to either node. Depending on how the packets are routed, CTC could connect to either node (having the same IP address). If CTC has connected to both nodes before they shared the same address, it has two distinct NodeModel instances (keyed by the node ID portion of the MAC address).
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.56 DUP-SHELF-ID 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.57 EHIBATVG Default Severity: Major (MJ), Service-Affecting (SA) SONET Logical Object: PWR The Extreme High Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage exceeds the extreme high power threshold.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.59 ENCAP-MISMATCH-P Default Severity: Critical (CR), Service-Affecting (SA) SONET Logical Object: STSTRM The Encapsulation C2 Byte Mismatch Path alarm applies to the ML-100T-8 Ethernet card.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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. In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 state 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 Alarm Procedures 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. Caution Using an optical test set disrupts service on the OC-N port. It could be necessary to manually switch traffic carrying circuits over a protection path. See the “2.10.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures 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-163 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-163 for the reporting card.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures Step 2 Upload the configuration file to the controller card (15310-CL-CTX or CTX2500 card) by completing the following steps: a. In node view, right-click the ML-100T-8 Ethernet card graphic. b. Choose IOS Startup Config from the shortcut menu. c. Click Local > TCC and navigate to the file location in the Open dialog box. Step 3 Complete the “Soft- or Hard-Reset an Ethernet or Electrical Card in CTC” procedure on page 2-162.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the ETH-LINKLOSS Condition Step 1 To clear this condition, reconnect the LAN cable on the front of the node. 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 Alarm Procedures 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). 2.7.70 FAILTOSW Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN The Failure to Switch to Protection Facility condition occurs when a working or protect optical facility switches to its companion port by using a MANUAL command.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.72 FAN Default Severity: Critical (CR), Service-Affecting (SA) SONET Logical Object: FAN The Fan Failure alarm indicates a problem with the internal fan of the ONS 15310-CL or ONS 15310-MA.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the FE-AIS Condition Step 1 Complete the “Clear the AIS Condition” procedure on page 2-21. 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 Alarm Procedures Step 2 Log into the node that links directly to the port reporting the FE condition. Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions. 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 Alarm Procedures 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 Alarm Procedures 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 Alarm Procedures 2.7.83 FE-FRCDWKSWPR-SPAN The FE-FRCDWKSWPR-SPAN condition is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.84 FE-IDLE Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far End Idle condition occurs when a far-end node detects an idle far-end 15310-CL-CTX, ONS 15310-MA DS1-28/DS3-EC1-3, or ONS 15310-MA DS1-84/DS3-EC1-3 card DS-3 signal in C-bit line type mode.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.87 FE-LOS Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: DS3 The Far End LOS condition occurs in C-bit line type mode when a far-end node reports the “LOS (DS3)” alarm on page 2-102.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the FEPRLF Alarm Step 1 To troubleshoot the FE alarm, determine which node and port link directly to the port reporting the FE alarm. Step 2 Log into the node that links directly to the port reporting the FE condition. Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for instructions. Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.93 FP-LINK-LOSS The FP-LINK-LOSS alarm is not used in the Cisco ONS 15310 platforms in this release. It is reserved for development. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.97 FRCDSWTOTHIRD Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: EXT-SREF, NE-SREF The Force Switch to Third Timing Source condition occurs when the user issues a Force command to switch to a third timing source. Note FRCDSWTOTHIRD is an informational condition. It does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note FSTSYNC is an informational condition. It does not require troubleshooting. 2.7.100 FULLPASSTHR-BI The FULLPASSTHR-BI condition is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the GFP-EX-MISMATCH Alarm Step 1 Ensure that the vendor equipment is provisioned to send a null extension header in order to interoperate with the Fibre Channel/FICON GFP ports. Step 2 If the GFP-EX-MISMATCH 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) to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 GFP-UP-MISMATCH Alarm Step 1 Step 2 Step 3 Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps: a. Double-click the card to display the card view. b.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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). 2.7.106 HIBATVG Default Severity: Major (MJ), Service-Affecting (SA) for ONS 15310-CL SONET Logical Object: PWR The High Voltage Battery alarm occurs in a –48 VDC environment for the ONS 15310-CL platform when a battery lead input voltage exceeds the high power threshold.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL or ONS 15310-MA. Note Step 2 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 Alarm Procedures 2.7.109 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. HI-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable. Clear the HI-RXPOWER Alarm Step 1 Complete the “Clear the LO-RXPOWER Alarm” procedure on page 2-100.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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. Note For information about this alarm that applies to DWDM objects, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the HLDOVRSYNC Alarm Step 1 Clear additional alarms that relate to timing, such as: • 2.7.98 FRNGSYNC, page 2-72 • 2.7.99 FSTSYNC, page 2-72 • 2.7.112 HLDOVRSYNC, page 2-79 • 2.7.135 LOF (BITS), page 2-92 • 2.7.149 LOS (BITS), page 2-101 • 2.7.170 MANSWTOINT, page 2-114 • 2.7.171 MANSWTOPRI, page 2-114 • 2.7.172 MANSWTOSEC, page 2-115 • 2.7.173 MANSWTOTHIRD, page 2-115 • 2.7.238 SWTOPRI, page 2-143 • 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures 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. Step 4 Caution Step 5 Step 6 Step 7 Step 8 a. In node view, double-click the controller card (15310-CL-CTX or CTX2500 card) to display the card view. b. Click the Provisioning > Optical > Line tabs. c.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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. It is resolved when the OOS-MA,MT state ends. Note INC-ISD is a condition and not an alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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. Clear the INHSWPR Condition Step 1 If the condition is raised against a 1+1 port, complete the “Initiate a 1+1 Manual Switch Command” procedure on page 2-157.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.121 INVMACADR Default Severity: Major (MJ), Service-Affecting (SA) SONET Logical Object: BPLANE The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15310-CL or ONS 15310-MA MAC address is invalid.
Chapter 2 Alarm Troubleshooting Alarm Procedures The alarm is typically caused by a misconfigured router manual area adjacency (MAA) address. For more information about IS-IS OSI routing and MAA configuration, refer to the “Cisco Transport Controller Operation” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. For more information about configuring OSI, refer to the “Turn Up Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.
Chapter 2 Alarm Troubleshooting Alarm Procedures Tip Step 9 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. There should be at least one common primary or secondary MAA in order to establish an adjacency. e.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 LCAS-CRC Condition Step 1 Look for and clear any associated equipment failures, such as the EQPT alarm, on the receive node or transmit node. Step 2 Look for and clear any bit error rate conditions at the transmit node.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-100T-8 Ethernet cards and CE-series cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed. The condition clears after provisioning is completed. The remote likely reports a path condition such as an “AIS-P” condition on page 2-21 or an “UNEQ-P” alarm on page 2-151.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the LINK-KEEPALIVE Alarm Step 1 Verify that no SONET or GFP circuit alarms that could impact Ethernet data traffic are present. If any are present, clear them using the relevant procedures in this chapter. Step 2 Verify that the “DATA-CRC;” alarm on page 2-48 is not present. If it is present, complete the trouble-clearing procedure. Step 3 Verify that the keep-alive timer on this IEEE RPR 802.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the LOA Alarm Step 1 In network view, click the Circuits tab. Step 2 Click the alarmed VCG and then click Edit. Step 3 In the Edit Circuit window, view the source and destination circuit slots, ports, and STSs. Step 4 Identify whether the STS travels across different fibers. If it does, complete the “Delete a Circuit” procedure on page 2-164.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the LOF (BITS) Alarm Note Step 1 This procedure assumes that the BITS timing reference signal is functioning properly. It also assumes the alarm is not appearing during node turn-up. Verify that the line type and line coding match between the BITS port and the 15310-CL-CTX or CTX2500 card by completing the following steps: a. In node view or card view, note the slot and port reporting the alarm. b.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the LOF (DS1) Alarm Step 1 Verify that the line type and line coding match between the DS-1 port and the signal source by completing the following steps: a. In CTC, note the slot and port reporting the alarm. b. Find the coding and line type formats of the signal source for the port reporting the alarm. You might need to contact your network administrator for the format information. c.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 d. If the signal source line type does not match the reporting port, click Line Type and choose C Bit from the drop-down list. e. 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) in order to report a Service-Affecting (SA) problem. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures When the alarm is raised on an OC-3 or OC-12 port, it is sometimes an indication that the OC-3 or OC-12 port expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver. Clear the LOF (OCN) Alarm Step 1 Complete the “Clear the LOF (EC1) Alarm” procedure on page 2-95.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Log Buffer Overflow alarm indicates that the CTC per-NE queue of incoming alarm, event, or updates, which has a capacity of 5000 entries, has overflowed. This happens only very rarely. However if it does, you must restart the CTC session. It is likely that some updates will have been missed if this alarm occurs. Clear the LOGBUFROVFL Alarm Step 1 Restart the CTC session.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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). 2.7.144 LO-LASERTEMP The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. For more information about this alarm, refer to the “Alarm Troubleshooting” chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the LOP-P Alarm Step 1 In node view, click the Circuits tab and view the alarmed circuit. Step 2 Verify the circuit size listed in the Size column. If the size is different from what is expected, such as an STS3c instead of an STS1, this raises the alarm. Step 3 If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Equipment Low Receive Power alarm is an indicator for OCN port received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls below the threshold value, which is user-provisionable. Clear the LO-RXPOWER Alarm Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits. Step 2 Find out whether new channels have been added to the fiber.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.149 LOS (BITS) Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: BITS The LOS (BITS) alarm indicates that the 15310-CL-CTX or CTX2500 card has an LOS from the BITS timing source. The LOS (BITS-N) means the BITS clock or the connection to it failed. Clear the LOS (BITS) Alarm Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15310-CL or ONS 15310-MA to the timing source.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 DS-1 card (15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3) to display the card view. b. Click the Maintenance > DS1 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.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 (DS3) Alarm Step 1 Verify that the cable is properly connected and attached to the correct port.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 9 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 Alarm Procedures Step 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the “Install Hardware” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Step 5 Repeat Steps 1 through 4 for any other port on the card that reports the LOS (EC1).
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.154 LOS (OCN) Default Severity: Critical (CR), Service-Affecting (SA) SONET Logical Object: OCN An LOS alarm on an OC-3 or OC-12 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS alarm means the upstream transmitter has failed. If an OC-3 or OC-12 LOS alarm is not accompanied by additional alarms, a fiber break is usually the cause of the alarm. It clears when two consecutive valid frames are received.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 3 If the correct port is in service, clean the fiber 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. Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the OC-3 or OC-12 port receiver specifications.
Chapter 2 Alarm Troubleshooting Alarm Procedures When you replace a card with the identical type of card, you do not need to make any changes to the database. Note Step 5 If no ports are shown bad and 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 Alarm Procedures Clear the LPBKDS3FEAC Condition Step 1 In node view, double-click the DS-3 card (15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3) to display the card view. Step 2 Click the Provisioning > DS3 > Line tabs. Step 3 Click the cell for the port in the Send Code column and click No Code from the drop-down list. Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures A Loopback Facility condition for a DS-1 or DS-3 signal occurs when a software facility (line) loopback is active for a DS-1 or DS-3 port on a 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card. 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.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.162 LPBKFACILITY (OCN) Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN A Loopback Facility condition for an OC-N signal occurs when a software facility (line) loopback is active for an OC-3 or OC-12 port on the 15310-CL-CTX or CTX2500 card. For information about troubleshooting optical circuits with loopbacks, refer to the “1.3 Identify Points of Failure on an OC-N Circuit Path” section on page 1-16.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures 2.7.166 LPBKTERMINAL (OCN) Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: OCN A Loopback Terminal condition for an OC-N port occurs when a software terminal (inward) loopback is active for an OC-3 or OC-12 port on the 15310-CL-CTX or CTX2500 card. Note OC-N terminal loopbacks do not typically return an AIS. Note Performing a loopback on an in-service circuit is Service-Affecting (SA).
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.168 MAN-REQ Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: STSMON, VT-MON The Manual Switch Request condition occurs when a user initiates a Manual switch request on an OC-N port.
Chapter 2 Alarm Troubleshooting Alarm Procedures SONET Logical Objects: EXT-SREF, NE-SREF The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary timing source. Note MANSWTOPRI is an informational condition and does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.175 MATECLK Default Severity: Minor (MN) for ONS 15310-MA SONET Logical Object: EQPT The Mate Clock alarm occurs when the active CTX2500 card cannot detect the clock from the standby CTX2500 card. Clear the MATECLK Alarm Step 1 Complete the “Soft- or Hard-Reset a Controller Card” procedure on page 2-162 for the standby CTX2500 card and wait 15 minutes.
Chapter 2 Alarm Troubleshooting Alarm Procedures The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot. If the card is in service, does have a circuit mapped to it, is paired in a working protection scheme, has DCC communications turned on, or is used as a timing reference, CTC does not allow you to delete the card.
Chapter 2 Alarm Troubleshooting Alarm Procedures This alarm is not user-serviceable. 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.178 MEA (PPM) 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 Alarm Procedures The Manufacturing Data Memory Failure alarm occurs when the electronically erasable programmable read-only memory (EEPROM) fails on a card or component, or when the 15310-CL-CTX or CTX2500 card cannot read this memory. EEPROM stores manufacturing data that a 15310-CL-CTX card uses to determine system compatibility and shelf inventory status. Unavailability of this information can cause less-significant problems.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the NON-CISCO-PPM Condition Step 1 Obtain the correct Cisco PPM and replace the existing PPM with the new one. 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 Alarm Procedures The Open Slot condition indicates that there is an open slot in the system shelf. Slot covers assist with airflow and cooling. Clear the OPEN-SLOT Condition Step 1 To install a slot cover and clear this condition, refer to the procedures located in the “Install Hardware” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the PDI-P Condition Step 1 Verify that all circuits terminating in the reporting card are in an active state by completing the following steps: a. Click the Circuits tab. b. Verify that the Status column lists the port as active. c. If the Status column lists the port as incomplete, wait 10 minutes for the ONS 15310-CL or ONS 15310-MA to initialize fully.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures 2.7.192 PRC-DUPID The PRC-DUPID alarm is not used in the ONS 15310 platforms in this release. It is reserved for development. 2.7.193 PROTNA Default Severity: Minor (MN) for ONS 15310-MA SONET Logical Object: EQPT The Protection Unit Not Available alarm is caused by an OOS protection card when a CTX2500 card that has been provisioned as part of a protection group is not available.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.195 PWR-FAIL-A Default Severity: Minor (MN), Non-Service-Affecting (NSA) SONET Logical Object: EQPT The Equipment Power Failure at Connector A alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the electrical line card or the controller card. Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches).
Chapter 2 Alarm Troubleshooting Alarm Procedures Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals. Statement 43 Clear the PWR-FAIL-B Alarm Step 1 Complete the “Clear the PWR-FAIL-A Alarm” procedure on page 2-125.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.199 RFI-P Default Severity: Not Reported (NR), Non-Service-Affecting (NSA) SONET Logical Objects: STSMON, STSTRM An RFI Path condition occurs when the ONS 15310-CL or ONS 15310-MA detects an RFI in the an STS-1 signal SONET overhead because of a fault in another node.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the RFI-V Condition Step 1 Verify that the fiber connectors are securely fastened and connected to the correct slot. For more information, 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 Alarm Procedures 2.7.202 ROLL-PEND Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) for STSMON, VT-MON, VT-TERM; Not Reported (NR), Non-Service-Affecting (NSA) for STSTRM SONET Logical Objects: STSMON, VT-MON, VT-TERM ROLL-PEND indicates that a roll process has been started, but a good signal has not been received yet by the roll destination leg. This condition can be raised individually by each path in a bulk circuit roll.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the RPRW Condition Step 1 Look for and clear any service-affecting SONET path-level alarms on the affected circuit, such as the “LOP-P” alarm on page 2-98, “PLM-P” alarm on page 2-122, or the “TIM-P” alarm on page 2-148. Clearing this alarm can also clear RPRW.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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 Alarm Procedures Step 10 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 Alarm Procedures 2.7.209 SD-P Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: STSMON, STSTRM An SD Path condition applies to the path (STS) layer of the SONET overhead. A path or ST-level SD alarm travels on the B3 byte of the SONET overhead. For UPSR-protected circuits, the BER threshold is user-provisionable and has a range for SD from 1E–9 dBm to 1E–5 dBm.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.211 SF Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: DS1, DS3 A Signal Fail condition occurs when the quality of the signal has exceeded the BER signal failure threshold. Signal failure is defined by Telcordia as a “hard failure” condition. The SD and SF conditions both monitor the incoming BER error rate and are similar conditions, but SF is triggered at a higher BER than SD.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the SF-L Condition Step 1 Complete the “Clear the SD-L Condition” procedure on page 2-132. 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 Alarm Procedures An SF-V condition is similar to the “SF” condition on page 2-134, but it applies to the VT layer of the SONET overhead. Clear the SF-V Condition Step 1 Complete the “Clear the SD-L Condition” procedure on page 2-132. 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 Alarm Procedures Step 5 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.218 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.
Chapter 2 Alarm Troubleshooting Alarm Procedures The SSM Failed alarm occurs when the synchronization status messaging received by the ONS 15310-CL or ONS 15310-MA fails. The problem is external to the system. This alarm indicates that although the system is set up to receive SSM, the timing source is not delivering valid SSM messages. Clear the SSM-FAIL Alarm Step 1 Verify that SSM is enabled on the external timing source.
Chapter 2 Alarm Troubleshooting Alarm Procedures The SSM Primary Reference Source (PRS) Traceable condition occurs when the SSM transmission level is changed to Stratum 1 Traceable. Note SSM-PRC is an informational condition. It does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note SSM-SMC is an informational condition. It does not require troubleshooting. 2.7.229 SSM-ST2 Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: BITS, DS1, NE-SREF, OCN The SSM Stratum 2 (ST2) Traceable condition occurs when the synchronization message quality level is changed to ST2. Note SSM-ST2 is an informational condition. It does not require troubleshooting. 2.7.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.233 SSM-STU Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Objects: BITS, DS1, NE-SREF, OCN The SSM Synchronization Traceability Unknown (STU) condition occurs when the reporting node is timed to a reference that does not support SSM, but the ONS 15310-CL or ONS 15310-MA has SSM support enabled. SSM-STU can also occur if the timing source is sending out SSM messages but SSM is not enabled on the system.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 Click Yes in the Resetting Card dialog box. Step 5 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 Alarm Procedures 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 Alarm Procedures Clear the SWTOTHIRD Condition Step 1 To clear the condition, clear alarms related to failures of the primary source, such as the “SYNCPRI” alarm on page 2-144 or the “SYNCSEC” alarm on page 2-145. 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 Alarm Procedures Step 3 If the primary timing reference is a BITS input, complete the “Clear the LOS (BITS) Alarm” procedure on page 2-101. Step 4 If the primary reference clock is an incoming port on the ONS 15310-CL or ONS 15310-MA, complete the “Clear the LOS (OCN) Alarm” procedure on page 2-106. Step 5 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).
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the SYNCTHIRD Alarm Step 1 In node view, click the Provisioning > Timing > General tabs. Step 2 Verify that the current configuration of REF-3 for the NE Reference. For more information about references, refer to the “Turn Up Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Step 3 If the third timing source is a BITS input, complete the “Clear the LOS (BITS) Alarm” procedure on page 2-101.
Chapter 2 Alarm Troubleshooting Alarm Procedures TIM occurs on a port that has previously been operating without alarms if someone switches optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the “LOF (OCN)” alarm on page 2-95 or the “UNEQ-P” alarm on page 2-151. If these alarms accompany a TIM alarm, reattach or replace the original cables/fibers to clear the alarms. If a Transmit or Expected String was changed, restore the original string.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.248 TIM-P Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Minor (MN), Non-Service-Affecting (NSA) for STSMON SONET Logical Objects: STSMON, STSTRM The TIM Path alarm occurs when the expected path trace string does not match the received path trace string. Path Trace Mode must be set to Manual or Auto for the TIM-P alarm to occur.
Chapter 2 Alarm Troubleshooting Alarm Procedures Clear the TIM-S Alarm Step 1 Double-click the 15310-CL-CTX or CTX2500 card to display the card view. Step 2 For the 15310-CL-CTX, click the Maintenance > EC1 > Path Trace tabs; for the CTX2500 card, click the Maintenance > Optical > Path Trace tabs. Step 3 In the Expected String column, enter the correct string information. Step 4 Click Apply. Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 If no alarms are reported by the OC-N port, or if the “PDI-P” condition on page 2-121 is reported, the problem could be on the far-end G-Series Ethernet port. Clear any alarms, such as CARLOSS, reported against the far-end port or card. Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.254 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. This alarm is raised only at the transmit side, but RAI is raised at both ends. Clear the TX-RAI Condition Step 1 Complete the “Clear the TX-AIS Condition” procedure on page 2-150.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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-164. b. If an error message dialog box appears, the VT tunnel is valid and not the cause of the alarm. c. If any other columns contain VTT, repeat Step 6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.7.256 UNEQ-V Default Severity: Major (MJ), Service-Affecting (SA) SONET Logical Objects: VT-MON, VT-TERM An SLMF UNEQ VT alarm indicates that the node is receiving SONET path overhead with Bits 5, 6, and 7 of the V5 overhead byte all set to zeroes. The source of the problem is not the node raising the alarm, but the node transmitting the VT signal to it. The V in UNEQ-V indicates that the failure has occurred at the VT layer.
Chapter 2 Alarm Troubleshooting Alarm Procedures 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.258 VCG-DEG Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) SONET Logical Object: VCG The VCAT Group Degraded alarm is a VCAT group alarm. The condition occurs when one member circuit carried by the ML-100T-8 Ethernet card is down.
Chapter 2 Alarm Troubleshooting DS-1 Line Alarms 2.7.260 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-106. 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 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 Frequently Used Alarm Troubleshooting Procedures 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 Frequently Used Alarm Troubleshooting Procedures 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 Frequently Used Alarm Troubleshooting Procedures 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. Step 2 In the Protection Groups list, click the protection group that contains the card you want to lock out.
Chapter 2 Alarm Troubleshooting Frequently Used Alarm Troubleshooting Procedures Initiate a Force Switch for All Circuits on a Path Protection Span This procedure forces all circuits in a UPSR from the working span to the protect. It is used to remove traffic from a card that originates or terminates UPSR circuits. Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.
Chapter 2 Alarm Troubleshooting Frequently Used Alarm Troubleshooting Procedures 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 UPSR working span from switching to the protect span. It is used to keep traffic off cards that originate or terminate UPSR circuits.
Chapter 2 Alarm Troubleshooting Frequently Used Alarm Troubleshooting Procedures 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 Frequently Used Alarm Troubleshooting Procedures 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 Frequently Used Alarm Troubleshooting 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 Frequently Used Alarm Troubleshooting 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 Frequently Used Alarm Troubleshooting 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 Frequently Used Alarm Troubleshooting 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, Release 9.
Chapter 2 Alarm Troubleshooting Frequently Used Alarm Troubleshooting Procedures Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 9.
CH 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 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.12 EFM-FRM-PER, page 3-6 ML100T, ML1000, MLFX, ML2 6810 efmLinkMonitoringErrored FramePeriodEvent 3.3.13 EFM-FRM-SEC, page 3-6 ML100T, ML1000, MLFX, ML2 6820 efmLinkMonitoringErrored FrameSecondsSummary 3.3.
Chapter 3 Transient Conditions 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.30 RMON-ALARM, page 3-9 — 2720 rmonThresholdCrossing Alarm 3.3.31 RMON-RESET, page 3-9 — 2710 rmonHistoriesAndAlarms ResetReboot 3.3.32 SESSION-TIME-LIMIT, page 3-9 NE 6270 sessionTimeLimitExpired 3.3.33 SFTWDOWN-FAIL, page 3-9 EQPT 3480 softwareDownloadFailed 3.3.
Chapter 3 Transient Conditions Transient Conditions For a comprehensive list of conditions, refer to the Cisco ONS SONET TL1 Command Guide. 3.2.2 Condition States The History tab state (ST) column indicates the disposition of the condition, as follows: • A raised (R) event is active. • A cleared (C) event is no longer active. • A transient (T) event is automatically raised and cleared in CTC during system changes such as user login, log out, and loss of connection to node view.
Chapter 3 Transient Conditions Transient Conditions 3.3.5 ADMIN-LOGOUT The Admin Logout of User (ADMIN-LOGOUT) condition occurs when the administrator logs off a user session. This transient condition does not result in a standing condition. 3.3.6 ADMIN-SUSPEND The Suspend User (ADMIN-SUSPEND) condition occurs when the password for a user account expires. This transient condition does not result in a standing condition. 3.3.
Chapter 3 Transient Conditions Transient Conditions 3.3.11 EFM-ERR-FRM The EFM Link Monitoring - Errored Frame Event condition occurs when the number of error frames detected on the remote NE crosses the configured threshold for a configured period or time interval, and the remote NE notifies the local NE of the threshold crossing. This transient condition does not result in a standing condition. 3.3.
Chapter 3 Transient Conditions Transient Conditions 3.3.17 FRCDWKSWBK-NO-TRFSW The Forced Switch Back to Working Resulted in No Traffic Switch (FRCDWKSWBK-NO-TRFSW) condition occurs when you perform a Force Switch to the working port/card and the working port/card is already active. This transient condition might result in a Force Switch (Ring or Span) standing condition. 3.3.
Chapter 3 Transient Conditions Transient Conditions This transient condition does not result in a standing condition. 3.3.24 LOGIN-FAILURE-USERID The Invalid Login–Username (LOGIN-FAILURE-USERID) condition occurs when a user login (CTC, Cisco Transport Manager [CTM], or TL1) fails because the login username is not present on the node database. You must log in again with an existing user ID. This transient condition is equivalent to a security warning.
Chapter 3 Transient Conditions Transient Conditions 3.3.30 RMON-ALARM The Remote Monitoring Threshold Crossing Alarm (RMON-ALARM) condition occurs when the remote monitoring (RMON) variable crosses the threshold. 3.3.31 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.
Chapter 3 Transient Conditions Transient Conditions 3.3.37 WORK-QUEUE-FULL The Work Queue Full(WORK-QUEUE-FULL) condition occurs when the netTask Queue in VxWorks has filled up and task operations for the card are postponed. This transient condition does not result in a standing condition. 3.3.38 WKSWBK The Switched Back to Working (WKSWBK) condition occurs when traffic switches back to the working port/card in a nonrevertive protection group.
CH 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 A 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 IOS 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 WID-1044 Warning: there is a discrepancy in the build timestamp between Refer to the warning message text. the NE cached jar file ({0}) and the NE ({1}). Your CTC jar cache should be emptied. EID-1046 Selected CTC version ({0}) must be greater than or equal{to the login NE version ({1}). EID-1047 No additional Pseudo IOS windows may be opened at this time.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2013 The circuit creation failed. The circuit creation cannot proceed due to changes in the network which affected the circuit(s) being created. The dialog box will close. Please try again. Refer to the error message text. EID-2014 No circuit(s) were selected. {0} You must select a circuit to complete this function.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2030 An error occurred during provisioning. There was an error during provisioning. EID-2031 An error occurred while adding the node. There was an error while adding a node. EID-2032 The circuit could not be renamed. {0} CTC could not rename the circuit. EID-2033 An error occurred during validation.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2052 An error occurred during circuit processing. There was an error during the circuit processing. EID-2054 An error occurred while selecting an endpoint. There was an error during the endpoint selection. EID-2055 No endpoints are available for this selection. Please make another selection.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2073 This column is permanent and cannot be removed. You cannot delete a permanent column. EID-2074 Select one or more profiles. You have not selected any profile or column. Reset operation is done by right-clicking the selected column. EID-2075 This column is permanent and cannot be reset. A permanent column is non resettable.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2096 The user must have a security level. You must have an assigned security level to perform this task. EID-2097 No user name was specified. You did not specify a user name. EID-2099 An error occurred while ring switching. There was an error during the ring switch. EID-2100 Please select at least one profile to delete. You have not selected the profile to delete.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2121 The ring cannot be upgraded. {0} CTC cannot upgrade the specified ring. EID-2122 The ring speed for is inadequate for the upgrade procedure. Only {0} (or higher) {1} can be upgraded to four-fiber. You have selected an incorrect ring speed for upgrade. Only rings within the specified parameters can be upgraded to 4-fiber BLSR.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2143 No online help version was selected. The online help book cannot be deleted. Select the version of online help, and proceed. EID-2144 An error occurred while deleting the online help book(s). {0} You cannot delete the specified online help. EID-2145 No nodes appear to have a Cisco IOS card. Refer to error message. EID-2146 This is a security violation.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2161 The sibling roll is 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. If it is a manual roll, you must complete the roll from CTC if Bridge and Roll is operated from CTC, or from TL1 if Bridge and Roll is operated from TL1. EID-2162 An error occurred during roll acknowledgement.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description 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. The existing pane Refer to the warning message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2193 A valid route cannot be found for the circuit drop creation request. Refer to the error message text. EID-2194 A valid route cannot be found for the roll creation request. Refer to the error message text. 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.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-2215 An error occurred while leaving the {0} page. There was an error while leaving the specified page. EID-2216 An error occurred while entering the {0} page. There was an error while entering the specified page. EID-2217 Some conditions could not be retrieved from the network view Refer to the error message text. EID-2218 The bandwidth must be between {0} and {1} percent.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-2326 Currently, CTC does not support bridge and roll on circuits that Refer to the warning message text. are entirely created by TL1. To continue with bridge and roll in CTC, the selected circuits must be upgraded.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3016 The subnet address is invalid. Refer to the error message text. EID-3017 The subnet address already exists. Refer to the error message text. EID-3019 The internal subnet address is incomplete. Enter the complete internal subnet address. EID-3020 The subnet address cannot be the same for both TSC cards. The requested action is not allowed.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3047 The file {0} could not be read. Please verify the name and try again. Refer to the error message text. EID-3048 There is no Cisco IOS startup configuration file available to download. CTC could not find the configuration file for IOS startup. EID-3049 The download cannot be done at this time because an update in Refer to the error message text. progress.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3068 The falling threshold must be between 1 and {0}. This is an invalid falling threshold entry. The valid range is from 1 to the specified value. EID-3069 The rising threshold must be greater than or equal to the falling Refer to the error message text. threshold.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3090 The operation cannot be performed because the {0} is {1}LOCKED_ON/LOCKED_OUT. You cannot perform operation. EID-3091 The operation cannot be performed because the protect card is Refer to the error message text. active. EID-3092 The requested action cannot be applied because the service state is invalid. Select another service state and proceed.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3113 The retransmit interval must be between 1 and 3600 seconds. The retransmit interval should be in the range of 1 to 3600 seconds. EID-3114 The retransmit interval is invalid. The retransmit interval is invalid. EID-3115 The LAN metric must be between 1 and 65535. The LAN metric should be in the range of 1 to 65535. EID-3116 The LAN metric is invalid.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3133 The maximum number of OSPF area ranges has been exceeded. OSPF area ranges exceeded the maximum number. EID-3134 The area ID is invalid. Use the DCC OSPF area ID, LAN port area ID, or 0.0.0.0. Refer to the error message text. EID-3135 The mask is invalid. Refer to the error message text. EID-3136 The range address is invalid. The range address is invalid. Try again.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3156 An error occurred while building the menu. Cards were not found for the {0} group. CTC encountered an error while building the menu, as cards could not be found for the specified group). EID-3157 The selected model could not be set because of an unexpected model class: {0}. CTC encountered an unexpected model class while trying to complete the task.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3175 The operator identifier ''{0}'' cannot exceed {1} characters. The specified operator identifier exceeds the specified character limit. EID-3176 The operator specific information ''{0}'' cannot exceed {1} characters. The specified operator specific information exceeds the specified character limit. EID-3177 The node name cannot be empty. The specified name is empty.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3226 The {0} termination(s) could not be deleted. {1} Refer to the error message text. EID-3227 A baseline could not be recorded. Performance metrics will remain unchanged. CTC failed to set the baseline values while provisioning NE. Previous values remain unchanged. EID-3228 The {0} termination(s) could not be created. {1} Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-3243 The port you have chosen as an {0} endpoint already supports The same port can not be used by multiple DCCs. an {1}. The port cannot support both DCCs. After the {0} is created, verify that no EOC alarms are present and then delete the {1} to complete the downgrade. EID-3244 An {0} exists on the selected ports. Therefore, you must create the {1}s one by one.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3260 An error occurred while provisioning the internal subnet: {0} The specified internal subnet could not be provisioned. EID-3261 The port rate provisioning cannot be changed while circuits exist on this port. Refer to the error message text. EID-3262 The port provisioning cannot be changed when the port status is {0}.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-3282 Refer to the warning message text. Performing a software upgrade while TSC 5 is active could result in a service disruption. It is recommended that you make TSC 10 the active TSC by performing a soft reset of TSC 5. The following ONS 15600s are currently unsafe to upgrade...
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3304 The DCC number is out of range. Enter a DCC number that is within the range EID-3305 OSPF cannot be active on the LAN interface when the backbone area is set on a DCC interface. You cannot have the default OSPF area on a DCC while OSPF is enabled on the LAN. EID-3306 Ethernet circuits must be bidirectional. Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3328 An error occurred while applying changes to row {0}. The value is out of range. There was an error applying the changes to the specified row. The value is out of range. EID-3330 Unable to switch to the byte because an overhead channel is present on this byte of the port. Refer to the error message text. EID-3331 An error occurred while applying changes to the row.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3360 ANS cannot be performed. Please check {0} parameter value. Refer to the error message text. EID-3361 The ring termination is in use. An error occurred while deleting the ring termination. You cannot delete a ring in use. EID-3362 An error occurred while deleting the ring termination. There was an error while deleting ring termination.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description 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. Is it OK to continue? EID-3385 {0}. Delete the circuits and try again. Refer to the error message text. EID-3386 The transponder mode could not be provisioned: {0} The specified transponder mode cannot be provisioned.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-3403 The administrative state transition has not been attempted on the monitored port. Refer to the error message text. EID-3404 The far end IP address could not be set on the {0} termination. Refer to the error message text. The IP address cannot be: loopback (127.0.0.0/8) class D (224.0.0.0/4) class E (240.0.0.0/4) broadcast (255.255.255.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-4012 Node management for {0} is not provided. Refer to the warning message text. EID-4013 CAUTION: Reverting to an earlier software release may result Refer to the error message text. in TRAFFIC LOSS and loss of connectivity to the node. It may requireonsite provisioning to recover.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5002 The tunnel could not be restored and must be recreated manually. Refer to the error message text. EID-5003 The circuit roll failed. {0} Refer to the error message text. EID-5004 There is already one four-fiber {0} provisioned on the set of There is already one 4F BLSR provisioned nodes involved in {1}.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5019 The manual path trace mode for this equipment does not support an expected string consisting of all null characters. Please change the expected string or the path trace mode. EID-5020 Software activation is in progress. Provisioning is not allowed. Refer to the warning message text. EID-5021 Software activation is in progress. {0} is not allowed.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5036 The GNE hostname {0} is invalid. The specified host name is invalid. CTC could not resolve the host name to any valid IP address EID-5037 Provisionable patchcords cannot be created between You must create provisionable patchcords transponder trunk ports and multiplexer/demultiplexer ports on between transponder trunk ports and the same node.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5052 The operation is not valid for the connection type. You may have selected the incorrect switch. EID-5053 The operation cannot be performed because the connection is under test access. Refer to the error message text. EID-5054 The TL1 tunnel could not be opened. {0} Refer to the error message text. EID-5055 Some patchcords were not deleted.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5069 A source node cannot be added to either of these lists. Select a node other than the source node to add to the route. EID-5070 A destination node cannot be added to either of these lists. Select a node other than the destination node to add to the route. EID-5071 This node already belongs to one of these lists.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5087 You cannot use same slot for east working and west protect ports. Refer to the error message text. EID-5088 You cannot use same slot for east working and west protect ports. Refer to the error message text. WID-5089 The maximum number of circuits that can be deleted at a time is 200.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5109 The demultiplexer associated with the protect path for the selected endpoint: {0} is missing or not connected. Refer to the error message text. EID-5110 The card selection is invalid. No cards were selected. Refer to the error message text. EID-5111 An error was occurred while configuring SNMPv3 proxy server. Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-5134 On node {0} the calculated gain is much greater than expected. Refer to the error message text. The wizard cannot operate under this condition. Please call TAC for support. EID-6001 One of the XC cards has failures or is missing. Check whether all the cross-connect cards are installed and working. EID-6002 One of the XC cards is locked. Unlock the cross-connect card.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6017 The destination of a {0} route cannot be a node IP address. A node IP address cannot be the destination for a static route. EID-6018 The destination of a {0} route cannot be the same as the subnet Refer to the error message text. used by the node. EID-6019 The destination of a static route cannot be 255.255.255.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6040 Out of memory. Refer to the error message text. EID-6041 The port is already present. Refer to the error message text. EID-6042 The port is used as timing source. Choose another port because the selected port is being used as a timing source. EID-6043 A DCC or GCC is present. Refer to the error message text. EID-6044 The card or port is part of protection group.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6065 The selected area address is duplicated. Enter another area address. EID-6066 The primary area address cannot be removed. Refer to the error message text. EID-6067 The selected area address does not exist. Choose another area address. EID-6068 The IP-over-CLNS NSEL cannot be modified while there are IP-over-CLNS tunnel routes provisioned.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6087 The card cannot be changed because the card type is invalid or Refer to the error message text. incompatible. EID-6088 This line cannot be put into loopback while it is in use as a timing source. Refer to the error message text. EID-6089 The interface was not found. {0} CTC cannot find the specified interface. EID-6090 The interface type is not valid for this operation.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6108 That port is already in use. Restart a TELNET session. EID-6109 A section trace is active on the trunk port. The action cannot be Actions such as putting the port in an completed. incomplete state are not permitted while a section trace is active. EID-6110 The maximum number of TARP requests has been reached. You have exceeded the maximum number of TARP requests.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6124 The ALS recovery pulse interval is invalid. Refer to the error message text. EID-6125 The ALS recovery pulse duration is invalid. Refer to the error message text. EID-6126 The current setting does not support the specified ALS mode. Refer to the error message text. EID-6127 All enabled routers are required to have the same area. Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6151 The minimum span loss must be less than the maximum span loss. Refer to the error message text. EID-6152 The “Use NTP/SNTP Server” field is checked. Enter the NTP/SNTP server IP address or server name. Enter the NTP/SNTP server name. To leave this field empty, uncheck the “Use NTP/SNTP Server” and proceed. EID-6153 The maximum frame size is invalid.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6213 It is not possible to associate the side to the two ports. During the creation of a side it is not possible to associate the selected ports to the new side. EID-6214 The port is already assigned to a side. The selected port is already assigned to a side. EID-6215 Error provisioning the CVLAN ID. Enter a valid number or range between 0 and 4094.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6235 This is not a valid VLAN name. The entered VLAN name exceeds the number of characters (32) allowed. EID-6236 The protected VLAN number exceeds the maximum allowed. The user enters more than 256 protected VLAN in the VLAN database. EID-6237 The port is not in OOS disabled admin state Refer to the error message text. EID-6238 The VLAN ID is in use.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6263 The equipment requires two slots. The user provisions a double footprint card in a single slot. EID-6264 The patchcord is duplicated. Refer to the error message text. EID-6265 The wavelength is in use by an OCH trail, a virtual link, or an internal patchcord. Refer to the error message text. EID-6266 The card cannot be changed because the port has not been provisioned.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-6284 Refer to the error message text. Changing the timing standard will re-initialize the shelf timing and might affect traffic. OK to continue? WID-6285 Refer to the error message text.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description WID-6307 You have only selected one trunk-to-trunk patchcord. For complete deletion, you must select both patchcords that are attached to the 10GE_XP/GE_XP cards. Do you want to continue? Refer to the warning message text. WID-6308 You have only selected one trunk-to-OCH patchcord. For complete deletion, you must select both patchcords that are attached to the TXP/MXP card.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6329 Protection/AIS action cannot be both set to squelch. Refer to the error message text. EID-6330 The node failed to restart the Pseudo IOS CLI service on the selected port. Try using another unreserved port that is not being used within the 1024 - 65535 range. Refer to the error message text. EID-6331 That port is already in use.
Chapter 4 Table 4-1 Error Messages Error Messages (continued) Error/Warning ID Error/Warning Message Description EID-6347 A patchcord was expected for a successful operation. Refer to the error message text. EID-6348 A Virtual link already exists on the same path. Refer to the error message text. EID-6349 The overhead creation has failed. Refer to the error message text. EID-6350 The unprotected line is not present Refer to the error message text. EID-6351 The port status is active.
INDEX characteristics Numerics 2-16 frequently used troubleshooting procedures 1+1 optical port protection, deleting 2-82 15310-CL-CTX card line alarms resetting hierarchy 2-17 list arranged by logical object type 2-155 list of Critical 2-162 15xxx RR handheld receiver list of Major 2-2 list of Minor 2-3 list of Not-Alarmed conditions 2-4 automatic mode tests list of Not Reported conditions 2-6 default 1-59 logical objects manual mode tests usage flow chart 1-57 2-10 service eff
Index APS-PRIM-SEC-MISM AS-CMD AS-MT LWBATVG 2-27 BER 2-27 2-29 AS-MT-OOG 2-113 2-29 AUTOSW-SDBER 2-33 AUTOSW-SFBER 2-33 asynchronous mapping 2-123 SD AUD-ARCHIVE-FAIL 3-5 SD-L 2-132 2-130 AUD-LOG-LOSS 2-29 SD-P 2-133 AUD-LOG-LOW 2-30 SD-V 2-133 AUTOLSROFF SF 2-30 automatic protection switching byte failure 2-22 channel failure on protect card channel mismatch FEPRLF 2-69 path protection 2-135 SF-V 2-135 2-36 2-69 bit error rate.
Index calculating IP subnets Ethernet facility loopback circuit 1-80 CARLOSS Ethernet loopback circuit CARLOSS (ML100T) CE-100T-8 card 1-46 2-166 Ethernet terminal loopback circuit 2-40 facility loopback circuit 2-37 1-35, 1-49 1-32 CE100T-8 card 2-37 lock-on or lockout CE-MR-6 card 2-37 OC-N port cross-connect loopback circuit equipment carrier loss 2-159 OC-N port facility loopback circuit 2-39 CAT-5 cable.
Index facility loopback on an intermediate-node OC-N port 1-21, 1-39 gray node icon list of alarms facility loopback on a source-node electrical port 1-4 facility loopback on a source-node Ethernet port 1-31 facility loopback on a source-node OC-N port hairpin on a destination-node electrical port hairpin on a source-node electrical port login errors 1-74 2-1 1-66, 1-71, 1-77 loss of TCP/IP connection 1-17 2-39 node view to network view change unsuccessful 1-13 release interoperability probl
Index limitations with OC-3 EFM-FRM-SEC 1-83 two-DCC requirement during facility loopback verifying DCC terminations 2-164 deleting 1-2 EFM-RLBK-FAIL EFM-SYM-PER EHIBATVG circuits 3-6 2-52 See also electrical wiring verification 1-73 DCC terminations 2-82 protection groups 2-82 designing IP subnets test during a facility loopback See also DS1-28/DS3-EC1-3 card 1-80 See also DS1-84/DS3-EC1-3 card resetting 1-92 DISCONNECTED automatic mode test 2-135 DS1-28/DS3-EC1-3 card line alarm
Index Ethernet cards LPBKFACILITY (OCN) LED behavior after insertion resetting testing EXCCOL EXT performing on a destination-node Ethernet port 2-156 performing on a destination-node OC-N port 2-162 performing on a source-node Ethernet port 2-61 external switching commands clearing a 1+1 Force or Manual switch clearing a lock-on or lockout 2-158 1-21 initiating a 1+1 Manual switch 2-161 2-157 initiating a 1+1 protection port Force switch 2-157 1-17 perform on a source-node electrical por
Index FE-LOS 2-69 H FE-MANWKSWBK-SPAN 2-69 FE-MANWKSWPR-SPAN 2-69 FEPRLF hairpin circuit creating on a destination-node electrical port 2-69 fiber and cabling errors creating on a source-node electrical port 1-86 definition fiber-optic connections faulty firewall, invalid port number FIREWALL-DIS 4-12 3-6 1-3 performing on a source-node electrical port 1-6 perform on a destination-node Ethernet port 1-51 testing 2-36 flash memory, capacity exceeded flow rate half-duplex 2-70 FOR
Index INCOMPATIBLE-SW INHSWPR JRE 1-76, 2-83 cannot launch 2-83 INHSWWKG description 2-84 initiating 1-66 1-75 incompatibility 1+1 Manual switch launch failure 2-157 1+1 protection port Force switch 2-157 1:1 card switch (ONS 15310-MA only) lock-on 2-158 lockout 2-159 path protection Force switch path protection lockout 2-159 1-66 unsupported in this release 1-65 versions supported by CTC 1-64 K 2-160 2-161 path protection manual switch 1-75 KB-PASSTHR 2-87 2-160 Interne
Index blinking STAT LED lamp test LOM 1-91 typical activity line coding 2-98 See also cross-connect loopback See also facility loopback 2-93, 2-94 line interface unit See also terminal loopback 1-2 LINK-KEEPALIVE LKOUTPR-S 2-98 loopback 2-156 2-93 line framing LOA LO-LASERTEMP 1-85 clearing a DS-1 or DS-3 port loopback 2-90 clearing an EC-1 port loopback 2-91 lock initiation description 2-156 lock-on.
Index LPBKCRS MEM-GONE 2-108 LPBKDS3FEAC MEM-LOW 2-108 LPBKDS3FEAC-CMD MFGMEM 2-109 LPBKFACILITY 2-118 2-118 mismatch between received and expected C2 byte LPBKFACILITY (CE100T, CEMR) LPBKFACILITY (DS1, DS3) LPBKFACILITY (EC1) LPBKFACILITY (OCN) 2-109 CE100T-8 card CARLOSS 2-109 2-110 2-111 2-40 replacing 2-163 reseating 2-163 resetting 2-162 startup configuration error 2-111 CEMR-6 card 2-53 ML-100T-8 card LPBKTERMINAL 2-59 modifying.
Index APS-PRIM-SEC-MISM AS-CMD WTR 2-27 AS-MT EOC FAILSTOSW OOU-TPT 2-70 2-78 2-91 LOCKOUT-REQ 2-120 optical power alarms 2-75 LKOUTPR-S 1-83 2-120 OPEN-SLOT FORCED-REQ-SPAN 2-92 HI-RXPOWER 2-78 HI-TXPOWER 2-78 LO-RXPOWER 2-99 LO-TXPOWER 2-107 2-95 LO-RXPOWER 2-99 P 2-106 LO-TXPOWER 2-107 LPBKFACILITY password 2-111 LPBKTERMINAL incorrect 2-113 MANUAL-REQ-SPAN RFI-L 2-67 2-69 HI-TXPOWER 2-165 OC-3 and DCC limitations 2-62 FE-FRCWKSWBK-SPAN LOS 1-86 clearing
Index Ping 2-136 PS ping 1-65, 1-68, 1-69, 2-40, 2-136 PWR-FAIL-A 2-125 PWR-FAIL-B 2-125 platform unsupported in this release 1-65 PLM R PLM-P 2-122 PLM-V 2-123 PM-TCA 3-8 RAI 3-8 2-126 TX-RAI PORT-MISMATCH 2-123 2-151 receiver, for testing wiring See 15xxx RR handheld receiver 1-57 power reconfiguring See also battery cannot power up node or cards supply problems browsers 1-91 1-67 Java plug-in control panel 1-90 redirecting the CTC cache power alarms BAT-FAIL removing
Index S safety 2-139 SSM-RES 2-139 SSM-SDN-TN warnings 2-19 safety information SD SSM-PRS 2-19 2-130 AUTOSW-SDBER 2-33 2-139 SSM-SETS 2-139 SSM-SMC 2-139 SSM-ST2 2-140 SSM-ST3 2-140 SD-L 2-132 SSM-ST3E SD-P 2-133 SSM-ST4 2-140 SD-V 2-133 SSM-STU 2-141 SSM-TNC 2-141 SDCC termination failure 2-54 timing switch security alarms 1-84 STM-N alarms INTRUSION-PSWD 2-84 SESSION-TIME-LIMIT severities, alarm SSM-PRC 3-9 setting the default CTC browser SF 2-140 2-138 sw
Index SYNC-FREQ temperature alarms 2-144 synchronization alarms DBOSYNC FAN 2-49 FRNGSYNC 2-72 FSTSYNC FAN-DEGRADE 2-63 HI-LASERTEMP 2-77 HITEMP 2-72 HLDOVRSYNC 2-63 2-78 I-HITEMP 2-79 2-80 SSM-DUS 2-137 LO-LASERTEMP SSM-FAIL 2-137 SSM-LNC 2-138 clearing Ethernet circuit SSM-OFF 2-138 clearing OC-N circuit SSM-RES 2-139 creating on a destination-node electrical port 1-7, 1-10 1-48 2-98 terminal loopback 1-35, 1-49 1-43 SSM-SETS 2-139 creating on a destination-node Et
Index termination failure LDCC 2-56 testing MANSWTOINT 2-114 MANSWTOPRI 2-114 MANSWTOSEC 2-115 See also lamp test MANSWTOTHIRD See also loopback MATECLK See also power SSM-PRC 2-138 SSM-PRS 2-139 cross-connect loopback circuit 1-19 electrical cabling 1-6, 1-16 SWTOPRI electrical circuits 1-4 SWTOSEC Ethernet cards Ethernet facility loopback circuit hairpin circuit 1-5, 1-15, 1-17, 1-22, 1-25, 1-32 1-2 to 1-3 OC-N terminal loopback circuit 1-40 1-43 timing reference automati
Index trouble notifications TST-DSX card TX-AIS safety summary 2-16 wiring, verify 1-54 2-150 1-54 WKSWBK 3-10 2-155, 3-10 TX-LOF 2-150 WKSWPR TX-RAI 2-151 WRMRESTART WTR 2-19 3-10 2-155 U UNEQ AUTOSW-UNEQ (STSMON) 2-34 AUTOSW-UNEQ (VT-MON) 2-34 UNEQ-P 2-151 UNEQ-V 2-153 UNQUAL-PPM 2-153 USER-LOCKOUT USER-LOGIN 3-9 3-9 USER-LOGOUT 3-9 username/password mismatch 1-77 V VCCG-DOWN VCG-DEG 2-154 2-154 verifying BER threshold level DCC terminations 2-164 2-164 electrical
