Cisco ONS 15327 Troubleshooting Guide Product and Documentation Release 3.4 April 2003 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S About this Guide xxi Document Objectives Audience xxi xxi Related Documentation xxi Document Conventions xxii Where to Find Safety and Warning Information xxiii Obtaining Documentation xxiii Cisco.com xxiii Documentation CD-ROM xxiii Ordering Documentation xxiv Documentation Feedback xxiv Obtaining Technical Assistance xxiv Cisco.
Contents Create the Terminal Loopback on a Destination XTC Port 1-12 Test the Terminal Loopback Circuit on the Destination XTC Port 1-13 Test the Destination XTC Card 1-14 1.2.4 Perform a Hairpin on a Destination Node XTC Port 1-14 Create the Hairpin Loopback Circuit on the Destination Node XTC Card Test the Hairpin Circuit 1-16 Test the Alternate Destination XTC Card 1-16 Retest the Original Destination XTC Card 1-17 1.2.
Contents Create the Terminal Loopback on a Destination Node OC-N Port Test the Terminal Loopback Circuit 1-40 Test the OC-N Card 1-40 1-39 1.4 Restoring the Database and Default Settings 1-41 1.4.1 Restore the Node Database 1-41 Restore the Database 1-41 1.4.2 Restore the Node to Factory Configuration 1-43 Use the Reinitialization Tool to Clear the Database and Upload Software (Windows) 1-43 Use the Reinitialization Tool to Clear the Database and Upload Software (UNIX) 1-45 1.
Contents Launch CTC to Correct the Core Version Build 1-60 1.6.10 Username or Password Does Not Match the XTC Information 1-60 Verify Correct Username and Password 1-61 1.6.11 No IP Connectivity Exists Between Nodes 1-61 1.6.12 DCC Connection Lost 1-61 1.6.13 “Path in Use” Error When Creating a Circuit 1-61 Cancel the Circuit Creation and Start Over 1-62 1.6.14 Calculate and Design IP Subnets 1-62 1.6.15 Ethernet Connections 1-62 Verify Ethernet Connections 1-63 1.6.
Contents Verify Card LED Operation CHAPTER 2 Alarm Troubleshooting 1-80 2-1 2.1 Alarm Index by Default Severity 2-1 2.1.1 Critical Alarms (CR) 2-1 2.1.2 Major Alarms (MJ) 2-2 2.1.3 Minor Alarms (MN) 2-2 2.1.4 Conditions (NA or NR) 2-3 2.2 Alarms and Conditions Indexed By Alphabetical Entry 2.3 Alarm Index by Alarm Type 2-6 2.3.1 Alarm Type/Object Definition 2-4 2-13 2.4 Trouble Notifications 2-14 2.4.1 Conditions 2-14 2.4.2 Severities 2-14 2.5 Safety Summary 2-15 2.6 Alarm Procedures 2-15 2.6.
Contents Clear the AS-CMD Condition 2-23 2.6.13 AS-MT 2-23 Clear the AS-MT Condition 2-24 2.6.14 AUD-LOG-LOSS 2-24 Clear the AUD-LOG-LOSS Condition 2-24 2.6.15 AUD-LOG-LOW 2-24 2.6.16 AUTORESET 2-25 Clear the AUTORESET Alarm 2-25 2.6.17 AUTOSW-AIS 2-25 Clear the AUTOSW-AIS Condition 2-25 2.6.18 AUTOSW-LOP (STSMON) 2-26 Clear the AUTOSW-LOP (STSMON) Condition 2-26 2.6.19 AUTOSW-LOP (VTMON) 2-26 Clear the AUTOSW-LOP (VTMON) Alarm 2-26 2.6.20 AUTOSW-PDI 2-26 Clear the AUTOSW-PDI Condition 2-26 2.6.
Contents 2.6.33 CARLOSS (G Series) 2-33 Clear the CARLOSS (G Series) Alarm 2-34 2.6.34 CLDRESTART 2-36 Clear the CLDRESTART Condition 2-36 2.6.35 COMIOXC 2-37 Clear the COMIOXC Alarm 2-37 2.6.36 CONTBUS-A-18 2-37 Clear the CONTBUS-A-18 Alarm 2-37 2.6.37 CONTBUS-B-18 2-38 Clear the CONTBUS-B-18 Alarm 2-38 2.6.38 CONTBUS-IO-A 2-38 Clear the CONTBUS-IO-A Alarm 2-39 2.6.39 CONTBUS-IO-B 2-40 Clear the CONTBUS-IO-B Alarm 2-40 2.6.40 CTNEQPT-PBPROT 2-41 Clear the CTNEQPT-PBPROT Alarm 2-42 2.6.
Contents Clear the E-W-MISMATCH Alarm in CTC 2-52 2.6.53 EXCCOL 2-53 Clear the EXCCOL Alarm 2-53 2.6.54 EXERCISE-RING-REQ 2-53 2.6.55 EXERCISE-SPAN-REQ 2-53 2.6.56 EXT 2-54 Clear the EXT Alarm 2-54 2.6.57 EXTRA-TRAF-PREEMPT 2-54 Clear the EXTRA-TRAF-PREEMPT Alarm 2-54 2.6.58 FAILTOSW 2-54 Clear the FAILTOSW Condition 2-55 2.6.59 FAILTOSW-PATH 2-55 Clear the FAILTOSW-PATH Condition in a UPSR Configuration 2-55 2.6.60 FAILTOSWR 2-56 Clear the FAILTOSWR Condition in a BLSR Configuration 2-56 2.6.
Contents Clear the FE-FRCDWKSWPR-RING Condition 2.6.75 FE-FRCDWKSWPR-SPAN 2-65 Clear the FE-FRCDWKSWPR-SPAN Condition 2.6.76 FE-IDLE 2-66 Clear the FE-IDLE Condition 2-66 2.6.77 FE-LOCKOUTOFPR-SPAN 2-66 Clear the FE-LOCKOUTOFPR-SPAN Condition 2.6.78 FE-LOF 2-67 Clear the FE-LOF Condition 2-67 2.6.79 FE-LOS 2-67 Clear the FE-LOS Condition 2-67 2.6.80 FE-MANWKSWPR-RING 2-68 Clear the FE-MANWKSWPR-RING Condition 2.6.81 FE-MANWKSWPR-SPAN 2-68 Clear the FE-MANWKSWPR-SPAN Condition 2.6.
Contents Clear the INHSWPR Condition 2-75 2.6.98 INHSWWKG 2-75 Clear the INHSWWKG Condition 2-76 2.6.99 INVMACADR 2-76 2.6.100 KB-PASSTHR 2-76 Clear the KB-PASSTHR Condition 2-76 2.6.101 LKOUTPR-S 2-76 Clear the LKOUTPR-S Condition 2-76 2.6.102 LOCKOUT-REQ 2-77 Clear the LOCKOUT-REQ Condition 2-77 2.6.103 LOCKOUT-REQ-RING 2-77 Clear the LOCKOUT-REQ-RING Condition 2-77 2.6.104 LOF (BITS) 2-77 Clear the LOF (BITS) Alarm 2-78 2.6.105 LOF (DS-1) 2-78 Clear the LOF (DS-1) Alarm 2-78 2.6.
Contents 2.6.118 LPBKTERMINAL (G-Series) 2-88 Clear the LPBKTERMINAL (G-Series) Condition 2-88 2.6.119 MAN-REQ 2-88 Clear the MAN-REQ Condition 2-88 2.6.120 MANRESET 2-88 2.6.121 MANSWTOINT 2-89 2.6.122 MANSWTOPRI 2-89 2.6.123 MANSWTOSEC 2-89 2.6.124 MANSWTOTHIRD 2-89 2.6.125 MANUAL-REQ-RING 2-89 Clear the MANUAL-REQ-RING Condition 2-90 2.6.126 MANUAL-REQ-SPAN 2-90 Clear the MANUAL-REQ-SPAN Condition 2-90 2.6.127 MEA (EQPT) 2-90 Clear the MEA (EQPT) Alarm 2-90 2.6.128 MEM-GONE 2-91 2.6.129 MEM-LOW 2-92 2.
Contents Clear the RCVR-MISS Alarm 2-101 2.6.142 RFI-L 2-101 Clear the RFI-L Condition 2-101 2.6.143 RFI-P 2-102 Clear the RFI-P Condition 2-102 2.6.144 RFI-V 2-102 Clear the RFI-V Condition 2-103 2.6.145 RING-MISMATCH 2-103 Clear the RING-MISMATCH Alarm 2-103 2.6.146 RING-SW-EAST 2-104 2.6.147 RING-SW-WEST 2-104 2.6.148 SD 2-104 Clear the SD Condition 2-105 2.6.149 SD-L 2-105 Clear the SD-L Condition 2-105 2.6.150 SD-P 2-105 Clear the SD-P Condition 2-106 2.6.151 SF 2-106 Clear the SF Condition 2-106 2.6.
Contents 2.6.167 SSM-ST2 2-112 2.6.168 SSM-ST3 2-112 2.6.169 SSM-ST3E 2-112 2.6.170 SSM-ST4 2-113 2.6.171 SSM-STU 2-113 Clear the STU Condition 2-113 2.6.172 SSM-TNC 2-113 2.6.173 SWMTXMOD 2-113 Clear the SWMTXMOD Alarm 2-114 2.6.174 SWTOPRI 2-115 2.6.175 SWTOSEC 2-115 Clear the SWTOSEC Condition 2-115 2.6.176 SWTOTHIRD 2-115 Procedure: Clear the SWTOTHIRD Condition 2.6.177 SYNC-FREQ 2-116 Clear the SYNC-FREQ Condition 2-116 2.6.178 SYNCPRI 2-117 Clear the SYNCPRI Alarm 2-117 2.6.
Contents Identify a Ring ID or Node ID Number 2-125 Change a Ring ID Number 2-125 Change a Node ID Number 2-126 Verify Node Visibility for Other Nodes 2-126 Verify or Create Node DCC Terminations 2-126 Lock Out a BLSR Span 2-127 Clear a BLSR Span Lock Out 2-127 Clear a UPSR Lock Out 2-127 Switch Protection Group Traffic with an External Switching Command Clear an External Switching Command 2-128 Delete a Circuit 2-128 Clear a Loopback 2-128 Reset the Active XTC Card in CTC 2-129 Reset a Traffic Card in CTC
F I G U R E S Figure 1-1 Facility Loopback Process on an XTC Card Figure 1-2 Facility Loopback Process on an OC-N Card Figure 1-3 Terminal Loopback Process on an OC-N Card Figure 1-4 Terminal Loopback Process on a G1000-2 Card Figure 1-5 Hairpin Circuit Process on an OC-N Card Figure 1-6 Cross-Connect Loopback Process on an OC-N Port Figure 1-7 Facility Loopback on a Source XTC Port Figure 1-8 Hairpin Circuit on a Source Node XTC Port Figure 1-9 Terminal Loopback on a Destination XTC Port
Figures Figure 3-4 Replacing the Reusable Fan-Tray Air Filter 3-5 Cisco ONS 15327 Troubleshooting Guide, R3.
T A B L E S Table 1-1 Restore the Node Database Table 1-2 Restore the Node to Factory Configuration Table 1-3 Unable to Verify the IP Configuration of Your PC Table 1-4 Browser Login Does Not Launch Java Table 1-5 Unable to Verify the NIC Connection on Your PC Table 1-6 Verify PC Connection to ONS 15327 (Ping) Table 1-7 Retrieve the Unknown IP Address of the Node Table 1-8 Unable to Launch CTC Help After Removing Netscape Table 1-9 Browser Stalls When Downloading Files From XTC Table 1-10
Tables Table 1-32 Free-Running Synchronization Mode 1-70 Table 1-33 Daisy-Chained BITS Not Functioning 1-70 Table 1-34 Blinking STAT LED on Installed Card 1-71 Table 1-35 Bit Errors Appear for a Line Card Table 1-36 Faulty Fiber-Optic Connections Table 1-37 LAN Cable Pinout Table 1-38 Cross-Over Cable Pinout Table 1-39 Available SFP Connectors Table 1-40 Optical Card Transmit and Receive Levels Table 1-41 Power Supply Problems Table 1-42 Power Consumption for Node and Cards Table 1
About this Guide This section explains the objectives, intended audience, and organization of this publication and describes the conventions that convey instructions and other information.
About this Guide Document Conventions • Cisco ONS 15327 Procedure Guide, Release 3.4 Provides installation, turn up, provisioning, and maintainence procedures for Cisco ONS 15327 nodes and networks • Cisco ONS 15327 Reference Manual, Release 3.4 Provides reference information including detailed card specifications, feature descriptions, and topology information • Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide, Release 3.
About this Guide Where to Find Safety and Warning Information 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. To see translations of the warnings that appear in this publication, refer to the translated safety warnings that accompanied this device.
About this Guide Obtaining Technical Assistance Ordering Documentation You can find instructions for ordering documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm You can order Cisco documentation in these ways: • Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace: http://www.cisco.com/en/US/partner/ordering/index.shtml • Nonregistered Cisco.
About this Guide Obtaining Technical Assistance • Register for online skill assessment, training, and certification programs To obtain customized information and service, you can self-register on Cisco.com at this URL: http://tools.cisco.com/RPF/register/register.do Technical Assistance Center The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution.
About this Guide Obtaining Additional Publications and Information Cisco TAC Escalation Center The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
C H A P T E R 1 General Troubleshooting This chapter provides procedures for troubleshooting the most common problems encountered when operating a Cisco ONS 15327. To troubleshoot specific ONS 15327 alarms, see Chapter 2, “Alarm Troubleshooting.” If you cannot find what you are looking for contact the Cisco Technical Assistance Center (Cisco TAC). This chapter includes the following sections on network problems: • Note 1.
Chapter 1 General Troubleshooting Network Troubleshooting Tests 1.1 Network Troubleshooting Tests Use loopbacks and hairpins to test newly created circuits before running live traffic or to logically locate the source of a network failure. All ONS 15327 line (traffic) cards, except Ethernet cards, allow loopbacks and hairpins. Caution On OC-N cards, a facility loopback applies to the entire card and not an individual circuit. Exercise caution when using loopbacks on an OC-N card carrying live traffic.
Chapter 1 General Troubleshooting Network Troubleshooting Tests terminal loopback on the OC-N card turns the signal around before it reaches the LIU and sends it back through the XTC card to the MIC card. This test verifies that the XTC card cross-connect circuit paths are valid, but does not test the LIU on the OC-N card. Figure 1-3 Terminal Loopback Process on an OC-N Card Terminal loopback XTC Test Set A DS-N MIC OC-N 76191 DS-N Figure 1-4 shows a terminal loopback on a G1000-2 card.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path A cross-connect loopback tests a circuit path as it passes through the cross-connect card and loops back to the port being tested. Testing and verifying circuit integrity often involves taking down the whole line; however, a cross-connect loopback allows you to create a loopback on any embedded channel at supported payloads at the STS-1 granularity and higher.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path 1.2.1 Perform a Facility Loopback on a Source XTC Port The facility loopback test is performed on the node source port in the network circuit; in this example, the test is routed through the MIC card and performed on the XTC port in the source node. Completing a successful facility loopback on this port isolates the cabling, MIC card, and XTC card as possible failure points.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 3 Proceed to the “Test the Facility Loopback” procedure on page 1-6. Procedure: Test the Facility Loopback Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit. Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path c. Proceed to the “Perform a Cross-Connect Loopback on the Source OC-N Port” procedure on page 1-23. Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card. Step 5 Proceed to the “Test the XTC Card” procedure on page 1-7. Procedure: Test the XTC Card Step 1 Replace the suspect card with a card known to be good.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path b. c. Clear the facility loopback: • Click the Maintenance > Loopback tabs. • Choose None from the Loopback Type column for the port being tested. • Choose the appropriate state (IS, OOS, or OOS_AINS) from the State column for the port being tested. • Click the Apply button. • Click the Yes button in the Confirmation Dialog box.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Figure 1-8 Hairpin Circuit on a Source Node XTC Port ONS 15327 Source ONS 15327 Destination Hairpin XTC DS-N MIC OC-N OC-N DS-N Note MIC 76188 Test Set A XTC An XTC card is required to operate the ONS 15327 and can be used in a redundant or nonredundant configuration. Procedure: Create the Hairpin on the Source Node Port Step 1 Connect an electrical test set to the port you are testing.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin loopback circuit: a. b. Clear the hairpin circuit: • Click the Circuits tab. • Choose the hairpin circuit being tested. • Click the Delete button. • Click the Yes button in the Delete Circuits dialog box. • Confirm that the hairpin circuit is deleted from the Circuits tab list.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 4 If the test set indicates a good circuit, the problem might be a defective card. Step 5 To confirm a defective original XTC card, proceed to the “Retest the Original Source XTC Card” procedure on page 1-11. Procedure: Retest the Original Source XTC Card Step 1 Perform a side switch of the XTC cards to make the original card the active card. Step 2 Resend test-set traffic on the loopback circuit.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Terminal Loopback on a Destination XTC Port ONS 15327 Source ONS 15327 Destination XTC Terminal loopback XTC Test Set A DS-N MIC OC-N OC-N MIC DS-N Caution 76190 Figure 1-9 Performing a loopback on an in-service circuit is service-affecting. Procedure: Create the Terminal Loopback on a Destination XTC Port Step 1 Step 2 Step 3 Connect an electrical test set to the port you are testing: a.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 4 Create the terminal loopback on the destination port being tested: a. Step 5 Go to the node view of the destination node: • Choose View > Go To Other Node from the menu bar. • Choose the node from the drop-down list in the Select Node dialog box and click the OK button. b. In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node. c.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card. Step 5 Proceed to the “Test the Destination XTC Card” procedure on page 1-14. Procedure: Test the Destination XTC Card Step 1 Replace the suspect card with a good card. See the “Physically Replace a Card” procedure on page 2-130 for details. Step 2 Resend test-set traffic on the loopback circuit with a good card.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Figure 1-10 Hairpin on a Destination Node XTC Card ONS 15327 Source Unidirectional circuit ONS 15327 Destination XTC Test Set A DS-N Slot 1 MIC DS-N Hairpin XTC Slot 2 OC-N OC-N Slot 2 MIC Slot 1 76189 Bidirectional circuit Procedure: Create the Hairpin Loopback Circuit on the Destination Node XTC Card Step 1 Connect an electrical test set to the port you are testing.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 6 Verify that the circuits connect to the correct slots. For example, verify that source node/Slot 1 OC-N card (east slot) is connected to destination node/Slot 2(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 a DS-N Circuit Path b. • Click the Delete button. • Click the Yes button in the Delete Circuits dialog box. • Confirm that the hairpin circuit is deleted from the Circuits tab list. Proceed to the “Perform a Facility Loopback on a Destination XTC Card” procedure on page 1-18. Step 4 If the test set indicates a good circuit, the problem might be a defective card.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path 1.2.5 Perform a Facility Loopback on a Destination XTC Card The facility loopback test is performed on the last port in the circuit, in this case the XTC port in the destination node. Completing a successful facility loopback on this port isolates the possibility that the destination node cabling, MIC card, or line interface is responsible for a faulty circuit.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path Step 3 Proceed to the “Test the Facility Loopback Circuit” procedure on page 1-19. Procedure: Test the Facility Loopback Circuit Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit. Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Chapter 1 General Troubleshooting Identify Points of Failure on a DS-N Circuit Path c. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card. Step 5 Proceed to the “Test the XTC Card” procedure on page 1-20. Procedure: Test the XTC Card Step 1 Replace the suspect card with a card known to be good.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path d. Step 4 • Choose the appropriate state (IS, OOS, or OOS_AINS) from the State column for the port being tested. • Click the Apply button. • Click the Yes button in the Confirmation Dialog box. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic. If the test set indicates a faulty circuit, contact the Cisco TAC. 1.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Figure 1-12 Facility Loopback on a Circuit Source OC-N Port Source ONS Node OC-N XTC Intermediate ONS Node OC-N OC-N XTC Destination ONS Node OC-N OC-N XTC OC-N 90639 Test Set Caution Performing a loopback on an in-service circuit is service-affecting. Procedure: Create the Facility Loopback on the Source OC-N Port Step 1 Connect an optical test set to the port you are testing.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path b. • Choose None from the Loopback Type column for the port being tested. • Choose the appropriate state (IS, OOS, or OOS_AINS) from the State column for the port being tested. • Click the Apply button. • Click the Yes button in the Confirmation Dialog box. Proceed to the “Perform a Cross-Connect Loopback on the Source OC-N Port” procedure on page 1-23.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Figure 1-13 Cross-Connect Loopback on a Source OC-N Port Source ONS Node OC-N XC Intermediate ONS Node OC-N OC-N XC Destination ONS Node OC-N OC-N XC OC-N 90643 Test Set Step 1 Step 2 Step 3 Step 4 Connect an optical test set to the port you are testing: a. If you just completed the “1.3.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path b. • Click Apply. • Click Yes in the confirmation dialog. Proceed to the “Perform a Terminal Loopback on a Source-Node OC-N Port” procedure on page 1-27. Step 4 If the test set indicates a faulty circuit, there might be a problem with the cross-connect card. Step 5 Proceed to the “Test the Standby XTC Card” procedure on page 1-25.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Procedure: Retest the Original XTC Card Step 1 Do a manual switch of the XTC cards to make the original XTC card the active card: a. Determine the active cross-connect card. On both the physical node and the CTC window, the active XTC has a green ACT LED, and the standby XTC has an amber SBY LED. b. Position the cursor over the active cross-connect card. c. Right-click and choose Reset from the shortcut menu. d.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path 1.3.3 Perform a Terminal Loopback on a Source-Node OC-N Port The terminal loopback test is performed on the node destination port in the circuit, in this example, the destination OC-N port in the source node. First, create a bidirectional circuit that starts on the node source OC-N port and loops back on the node destination OC-N port. Then proceed with the terminal loopback test.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Step 3 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit. It is normal for a LPBKTERMINAL condition to appear during a loopback setup. The condition clears when you remove the loopback. Note Step 4 Step 5 Create the terminal loopback on the destination port being tested: a.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card. Step 5 Proceed to the “Test the OC-N Card” procedure on page 1-29. Procedure: Test the OC-N Card Step 1 Replace the suspect card with a card known to be good. See the “Physically Replace a Card” procedure on page 2-130 for details. Step 2 Resend test traffic on the loopback circuit with a good card.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Figure 1-15 Facility Loopback on an Intermediate-Node OC-N Port XTC OC-N OC-N XTC Destination ONS Node OC-N OC-N XTC OC-N 90636 OC-N Intermediate ONS Node Test Set Caution 90637 Source ONS Node 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 c. Click the Maintenance > Loopback tabs. d. Select OOS_MT from the State column. If this is a multiport card, select the row appropriate for the desired port. e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port. f. Click the Apply button. g. Click the Yes button in the Confirmation Dialog box.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Procedure: Test the OC-N Card Step 1 Replace the suspect card with a card known to be good. See the “Physically Replace a Card” procedure on page 2-130 for details. Step 2 Resend test traffic on the loopback circuit with a good card installed. Step 3 If the test set indicates a good circuit, the problem is probably the defective card: a.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Figure 1-16 Terminal Loopback on an Intermediate-Node OC-N Port Source ONS Node OC-N XTC Intermediate ONS Node OC-N OC-N XTC Destination ONS Node OC-N OC-N XTC OC-N 90638 Test Set 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 Step 5 c. Click the Maintenance > Loopback tabs. d. Select OOS_MT from the State column. If this is a multiport card, select the row appropriate for the desired port. e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port. f. Click the Apply button. g. Click the Yes button in the Confirmation Dialog box.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Step 2 Resend test traffic on the loopback circuit with a good card. Step 3 If the test set indicates a good circuit, the problem is probably the defective card: a. Return the defective card to Cisco through the returned materials authorization (RMA) process. Contact the Cisco TAC. b. Replace the defective OC-N card. See the “Physically Replace a Card” procedure on page 2-130 for details. c.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Procedure: Create the Facility Loopback on a Destination 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 “Perform a Terminal Loopback on an Intermediate-Node OC-N Port” procedure on page 1-32, leave the optical test set hooked up to the OC-N port in the source node. b.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path g. Click the Yes button in the Confirmation Dialog box. It is normal for a LPBKFACILITY condition to appear during loopback setup. The condition clears when you remove the loopback. Note Step 5 Proceed to the “Test the Facility Loopback Circuit” procedure on page 1-31. Procedure: Test the Facility Loopback Circuit Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path b. Replace the faulty card. See the “Physically Replace a Card” procedure on page 2-130 for details. c. Clear the facility loopback: d. Step 4 • Click the Maintenance > Loopback tabs. • Choose None from the Loopback Type column for the port being tested. • Choose the appropriate state (IS, OOS, or OOS_AINS) from the State column for the port being tested. • Click the Apply button.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Procedure: Create the Terminal Loopback on a Destination 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 “Perform a Facility Loopback on a Destination-Node OC-N Port” procedure on page 1-35, leave the optical test set hooked up to the OC-N port in the source node. b.
Chapter 1 General Troubleshooting Identify Points of Failure on an OC-N Circuit Path Procedure: 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. Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit: a. b. c.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings d. Step 4 • Select the appropriate state (IS, OOS, or OOS_AINS) in the State column for the port being tested. • Click the Apply button. • Click the Yes button in the Confirmation Dialog box. Clear the terminal loopback circuit: • Click the Circuits tab. • Choose the loopback circuit being tested. • Click the Delete button. • Click the Yes button in the Delete Circuits dialog box.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings Caution Step 1 If you are restoring the database on multiple nodes, wait until the XTC reboot has completed on each node before proceeding to the next node. Log into the node where you are restoring the database. a. On the PC connected to the ONS 15327, start Netscape or Internet Explorer. b. In the Netscape or Internet Explorer Web address (URL) field, enter the ONS 15327 IP address.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings 1.4.2 Restore the Node to Factory Configuration Symptom A node has both XTC cards in standby state, and you are unable reset the XTC cards to make the node functional. Table 1-2 describes the potential cause(s) of the symptom and the solution(s). Table 1-2 Restore the Node to Factory Configuration Possible Problem Solution Failure of both XTC cards in the node.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings Step 1 Insert the system software CD containing the reinit tool (Figure 1-19) into the local craft interface PC drive. If the CTC Installation Wizard opens, click Cancel. Step 2 To find the recovery tool file, go to Start > Run > Browse and select the CD drive. Step 3 On the CD drive, go to the CISCO15454 folder and set the Files of Type drop-down menu to All Files. Step 4 Select the RE-INIT.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings Figure 1-20 Confirm NE Restoration Step 11 The status bar at the bottom of the window displays Complete when the node has activated the software and uploaded the database. Note The Complete message only indicates that the XTC successfully uploaded the database, not that the database restore is successful. The XTC then tries to restore the database after it reboots.
Chapter 1 General Troubleshooting Restoring the Database and Default Settings Figure 1-21 Reinitialization Tool in UNIX Step 4 If the node you are reinitializing is an ENE in a proxy server network, enter the IP address of the GNE in the GNE IP field. If not, leave it blank. Step 5 Enter the node name or IP address of the node you are reinitializing in the Node IP field (Figure 1-21). Step 6 Verify that the Re-Init Database, Upload Package, and Confirm check boxes are checked.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Step 13 Manually set the node name and network configuration to site-specific values. Refer to the Cisco ONS 15327 Procedure Guide for information on setting the node name, IP address, mask and gateway, and IIOP port. 1.5 PC Connectivity Troubleshooting This section contains troubleshooting procedures for PC and network connectivity to the ONS 15327. 1.5.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting If you do not receive a reply, your IP configuration might not be properly set. Contact your Network Administrator for instructions to correct the IP configuration of your PC. 1.5.2 Browser Login Does Not Launch Java Symptom The message “Loading Java Applet” does not appear and the JRE does not launch during the initial login. Table 1-4 describes the potential cause(s) of the symptom and the solution(s).
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Step 2 Step 3 If you are using Netscape Navigator: 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 the OK button. d. From the Netscape Navigator menu bar, click the Edit > Preferences menus. e.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Table 1-5 Unable to Verify the NIC Connection on Your PC (continued) Possible Problem Solution Incorrect type of Category 5 cable is being used. If connecting an ONS 15327 directly to your laptop/PC or a router, use a straight-through Category 5 cable. When connecting the ONS 15327 to a hub or a LAN switch, use a crossover Category 5 cable. For details on the types of Category 5 cables, see the “1.8.2.
Chapter 1 General Troubleshooting PC Connectivity Troubleshooting Step 3 If the workstation has connectivity to the ONS 15327, the ping is successful and displays a reply from the IP address. If the workstation does not have connectivity, a “Request timed out” message displays. Step 4 If the ping is successful, an active TCP/IP connection exists. Restart CTC.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting 1.6 CTC Operation Troubleshooting This section contains troubleshooting procedures for CTC login or operation problems. 1.6.1 Unable to Launch CTC Help After Removing Netscape Symptom After removing Netscape and running CTC using Internet Explorer, the user is unable to launch the CTC Help and receives an “MSIE is not the default browser” error message. Table 1-8 describes the potential cause of the symptom and the solution.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-9 Browser Stalls When Downloading Files From XTC Possible Problem Solution The large, multinode BLSR requires more memory for the graphical user interface (GUI) environment variables. Reset the system or user CTC_HEAP environment variable to increase the memory limits.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting 1.6.3 Browser Stalls When Downloading CTC JAR Files from XTC Symptom The browser stalls or hangs when downloading a CTC JAR file from the XTC card. Table 1-10 describes the potential cause of the symptom and the solution. Table 1-10 Browser Stalls When Downloading JAR File from XTC Possible Problem Solution Disable the VirusScan Download Scan feature. See the “Disable the McAfee VirusScan VirusScan Download Scan” procedure on page 1-54.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Procedure: Redirect the Netscape Cache to a Valid Directory Step 1 Launch Netscape. Step 2 Display the Edit menu. Step 3 Choose Preferences. Step 4 Under the Category column on the left side, expand Advanced and select the Cache tab. Step 5 Change your disk cache folder to point to the cache file location. The cache file location is usually C:\ProgramFiles\Netscape\Users\yourname\cache.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Figure 1-22 Deleting the CTC Cache Procedure: Delete the CTC Cache File Manually Caution All running sessions of CTC must be halted before deleting the CTC cache. Deleting the CTC cache might cause any CTC running on this system to behave in an unexpected manner. Step 1 To delete the JAR files manually, from the Windows Start menu choose Search > For Files or Folders. Step 2 Enter *.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting 1.6.6 Node Icon is Gray on CTC Network View Symptom The CTC network view shows one or more node icons as gray in color and without a node name. Table 1-13 describes the potential cause(s) of the symptom and the solution(s). Table 1-13 Node Icon is Gray on CTC Network View Possible Problem Solution Different CTC releases Usually accompanied by an INCOMPATIBLE-SW alarm.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Procedure: Manually Edit the java.policy File Step 1 Search your computer for this file and open it with a text editor (Notepad or Wordpad). Step 2 Verify that the end of this file has the following lines: // Insert this into the system-wide or a per-user java.policy file. // DO NOT OVERWRITE THE SYSTEM-WIDE POLICY FILE--ADD THESE LINES! grant codeBase "http://*/fs/LAUNCHER.jar" { permission java.security.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-16 on page 1-59 shows JRE compatibility with ONS 15327 software releases. Table 1-16 JRE Compatibility ONS Software Release JRE 1.2.2 Compatible JRE 1.3 Compatible ONS 15327 Release 1.0.0 Yes No ONS 15327 Release 1.0.1 Yes Yes ONS 15327 Release 2.2.1 and earlier Yes No ONS 15327 Release 2.2.2 Yes Yes ONS 15327 Release 3.0 Yes Yes ONS 15327 Release 3.1 Yes Yes ONS 15327 Release 3.2 Yes Yes ONS 15327 Release 3.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-17 Different CTC Releases Do Not Recognize Each Other Possible Problem Solution The software loaded on the connecting workstation and the software on the XTC card are incompatible. This occurs when the XTC software is upgraded but the PC has not yet upgraded the compatible CTC JAR file. It also occurs on login nodes with compatible software that encounter other nodes in the network that have a newer software version.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Procedure: Verify Correct Username and Password Step 1 Ensure that your keyboard Caps Lock key is not turned on and affecting the case-sensitive entry of the username and password. Step 2 Contact your system administrator to verify the username and password. Step 3 Call Cisco TAC to have them enter your system and create a new user name and password. 1.6.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-21 “Path in Use” Error When Creating a Circuit Possible Problem Solution Another user has already selected the same source port to create another circuit CTC does not remove a card or port from the available list until a circuit is completely provisioned. If two users simultaneously select the same source port to create a circuit, the first user to complete circuit provisioning gets use of the port.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-23 Ethernet Connections Possible Problem Solution Improperly seated connections You can fix most connectivity problems in an Ethernet network by following a few guidelines. See Figure 1-23 when consulting the steps in the “Verify Ethernet Connections” procedure on page 1-63. Incorrect connections Figure 1-23 Ethernet Connectivity Reference Device "B" 192.168.1.75 255.255.255.0 VLAN #1 Member Device "A" 192.168.1.25 255.255.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Step 7 Verify connectivity between device A and device C by pinging between these locally attached devices (see the “1.5.4 Verify PC Connection to the ONS 15327 (Ping)” section on page 1-50). If the ping is unsuccessful: a. Verify that device A and device C are on the same IP subnet. b.
Chapter 1 General Troubleshooting CTC Operation Troubleshooting Table 1-24 VLAN Cannot Connection to Network Device from Untag Port Possible Problem Solution The Tagged ONS 15327 adds the IEEE 802.1Q tag and the Untag ONS 15327 removes the Q-tag without replacing the bytes. The NIC of the network device categorizes the packet as a runt and drops the packet. See the “Change VLAN Port Tag and Untagged Settings” procedure on page 1-65.
Chapter 1 General Troubleshooting Circuits and Timing Step 4 At the VLAN port set to Untag, click the port and choose Tagged. Note Step 5 The attached external devices must recognize IEEE 802.1Q VLANs. After each port is in the appropriate VLAN, click Apply. 1.7 Circuits and Timing This section provides solutions to circuit creation and reporting errors, as well as common timing reference errors and alarms. 1.7.
Chapter 1 General Troubleshooting Circuits and Timing Table 1-25 Circuit in Partial State (continued) Possible Problem Solution During an automatic transition, some path-level defects and/or alarms were detected on the circuit. Determine which node in the circuit is not changing to the desired state. Refer to the “View the State of Circuit Nodes” procedure on page 1-67.
Chapter 1 General Troubleshooting Circuits and Timing Step 4 Uncheck the bidirectional check box in the circuit creation window. Step 5 Give the unidirectional VT circuit an easily recognizable name, such as “delete me.” Step 6 Display the XTC-28-3 card in CTC card view. Click the Maintenance > DS1 tabs. Step 7 Locate the VT that is reporting the alarm (for example, DS3 #2, DS1 #13). Step 8 From the Loopback Type list, choose Facility (line) and click Apply. Step 9 Click Circuits.
Chapter 1 General Troubleshooting Circuits and Timing Table 1-28 DS3 Card Does Not Report AIS-P From External Equipment Possible Problem Solution The card is functioning as designed. This card terminates the port signal at the backplane so STS AIS-P is not reported from the external equipment/line side. DS-3 cards have DS-3 header monitoring functionality, which allows you to view performance monitoring (PM) on the DS-3 path. Nevertheless, you cannot view AIS-P on the STS path.
Chapter 1 General Troubleshooting Circuits and Timing 1.7.7 Holdover Synchronization Alarm Symptom The clock is running at a different frequency than normal and the HLDOVRSYNC alarm appears. Table 1-31 describes the potential cause of the symptom and the solution. Table 1-31 Holdover Synchronization Alarm Possible Problem Solution The last reference input The clock is running at the frequency of the last valid reference input. This has failed. alarm is raised when the last reference input fails.
Chapter 1 General Troubleshooting Fiber and Cabling 1.7.10 Blinking STAT LED after Installing a Card Symptom After installing a card, the STAT LED blinks continuously for more than 60 seconds. Table 1-34 describes the potential cause of the symptom and the solution. Table 1-34 Blinking STAT LED on Installed Card Possible Problem Solution The card cannot boot because it failed the Power On Shelf Test (POST) diagnostics. The blinking STAT LED indicates that POST diagnostics are being performed.
Chapter 1 General Troubleshooting Fiber and Cabling 1.8.2 Faulty Fiber-Optic Connections Symptom A line card has multiple SONET alarms and/or signal errors. Table 1-36 describes the potential cause(s) of the symptom and the solution(s). Table 1-36 Faulty Fiber-Optic Connections Possible Problem Solution Faulty fiber-optic connections. Faulty fiber-optic connections can be the source of SONET alarms and signal errors. See the “Verify Fiber-Optic Connections” procedure on page 1-72.
Chapter 1 General Troubleshooting Fiber and Cabling Step 4 c. Determine the power level of fiber with the fiber-optic power meter. d. Verify that the power meter is set to the appropriate wavelength for the optical card being tested (either 1310 nm or 1550 nm depending on the specific card). e. Verify that the power level falls within the range specified for the card; see the “1.8.2.3 Optical Card Transmit and Receive Levels” section on page 1-77.
Chapter 1 General Troubleshooting Fiber and Cabling Tip To prevent overloading the receiver, use an attenuator on the fiber between the card transmitter and the receiver. Place the attenuator on the receive transmitter of the cards. Refer to the attenuator documentation for specific instructions. Tip Most fiber has text printed on only one of the two fiber strands. Use this to identify which fiber is connected to Tx and which fiber is connected to Rx. 1.8.2.
Chapter 1 General Troubleshooting Fiber and Cabling Table 1-37 shows the pinout of a LAN cable. Table 1-37 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 7 White/brown 4 7 8 Brown 4 8 Receive Data - 6 Figure 1-28 on page 1-75 shows the layout of a cross-over cable.
Chapter 1 General Troubleshooting Fiber and Cabling 1.8.2.2 Replace Faulty SFP Connectors Small Form-factor Pluggable (SFP) connectors are hot-swappable and can be installed or removed while the card or shelf assembly is powered and running. Warning Class I laser products. These products have been tested and comply with Class I limits. Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected.
Chapter 1 General Troubleshooting Fiber and Cabling Step 4 Grip the sides of the SFP with your thumb and forefinger and insert the SFP into the slot on the G1000-2 card. Note SFPs are keyed to prevent incorrect installation. Step 5 Slide the SFP through the flap that covers the opening until you hear a click. The click indicates the SFP is locked into the slot.
Chapter 1 General Troubleshooting Power and LED Tests 1.9 Power and LED Tests This section provides symptoms and solutions for power supply problems, power consumption, and LED indicators. 1.9.1 Power Supply Problems Symptom Loss of power or low voltage, resulting in a loss of traffic and causing the LCD clock to reset to the default date and time. Table 1-41 describes the potential cause(s) of the symptom and the solution(s).
Chapter 1 General Troubleshooting Power and LED Tests Procedure: Isolate the Cause of Power Supply Problems Step 1 Step 2 If a single ONS 15327 show signs of fluctuating power or power loss: a. Verify that the –48 VDC #8 power terminals are properly connected to a fuse panel. These power terminals are located on the lower section of the backplane EIA under the clear plastic cover. b. Verify that the power cable is #12 or #14 AWG and in good condition. c.
Chapter 1 General Troubleshooting Power and LED Tests 1.9.3 Lamp Test for Card LEDs Symptom Card LED does not light or you are unsure if LEDs are working properly. Table 1-43 describes the potential cause of the symptom and the solution. Table 1-43 Lamp Test for Card LEDs Possible Problem Solution Faulty LED A lamp test verifies that all the card LEDs work.
C H A P T E R 2 Alarm Troubleshooting This chapter gives a description, severity, and troubleshooting procedure for commonly encountered Cisco ONS 15327 alarms and conditions. Table 2-1 on page 2-1 through Table 2-4 on page 2-3 give lists of ONS 15327 alarms organized by severity. Table 2-5 on page 2-4 gives a list of alarm organized alphabetically. Table 2-6 on page 2-6 gives a list of alarms organized by alarm type.
Chapter 2 Alarm Troubleshooting Alarm Index by Default Severity Table 2-1 Critical Alarm Index (continued) EQPT, page 2-50 LOP-P, page 2-80 TIM-P, page 2-119 EQPT-MISS, page 2-51 LOS (DS-3), page 2-83 UNEQ-P, page 2-122 FAN, page 2-59 LOS (OC-N), page 2-84 2.1.2 Major Alarms (MJ) Table 2-2 lists Major alarms.
Chapter 2 Alarm Troubleshooting Alarm Index by Default Severity 2.1.4 Conditions (NA or NR) Table 2-4 lists Not Alarmed or Not Reported conditions.
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-4 Conditions Index (continued) FE-EQPT-NSA, page 2-64 MANSWTOSEC, page 2-89 SYNC-FREQ, page 2-116 FE-EXERCISING-RING, page 2-64 MANSWTOTHIRD, page 2-89 WKSWPR, page 2-124 FE-EXERCISING-SPAN, page 2-64 MANUAL-REQ-RING, page 2-89 WTR, page 2-124 FE-FRCDWKSWPR-RING, page 2-65 2.
Chapter 2 Alarm Troubleshooting Alarms and Conditions Indexed By Alphabetical Entry Table 2-5 Alphabetical Alarm Index (continued) BAT-A-HGH-VLT, page 2-28 FRCDSWTOSEC, page 2-71 SF, page 2-106 BAT-A-LOW-VLT, page 2-28 FRCDSWTOTHIRD, page 2-71 SF-L, page 2-106 BAT-B-HGH-VLT, page 2-29 FRNGSYNC, page 2-71 SF-P, page 2-107 BAT-B-LOW-VLT, page 2-29 FSTSYNC, page 2-71 SFTWDOWN, page 2-107 BKUPMEMP, page 2-29 FULLPASSTHR-BI, page 2-72 SNTP-HOST, page 2-108 BLSROSYNC, page 2-30 HITEMP, page 2-
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-5 Alphabetical Alarm Index (continued) FAILTOSWS, page 2-58 MANSWTOTHIRD, page 2-89 UNEQ-V, page 2-123 FAN, page 2-59 MANUAL-REQ-RING, page 2-89 WKSWPR, page 2-124 FANDEGRADE, page 2-60 MANUAL-REQ-SPAN, page 2-90 WTR, page 2-124 2.3 Alarm Index by Alarm Type Table 2-6 gives the name and page number of every alarm in the chapter organized by alarm type.
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) DS3:: AIS, page 2-16 DS3:: AS-CMD, page 2-23 DS3:: AS-MT, page 2-23 DS3:: DS3-MISM, page 2-45 DS3:: FE-AIS, page 2-60 DS3:: FE-DS1-MULTLOS, page 2-61 DS3:: FE-DS1-NSA, page 2-61 DS3:: FE-DS1-SA, page 2-62 DS3:: FE-DS1-SNGLLOS, page 2-62 DS3:: FE-DS3-NSA, page 2-63 DS3:: FE-DS3-SA, page 2-63 DS3:: FE-EQPT-NSA, page 2-64 DS3:: FE-IDLE, page 2-66 DS3:: FE-LOF, page 2-67 DS3:: FE-LOS, page 2-67 DS3:: IN
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) EQPT:: FORCED-REQ, page 2-69 EQPT:: HITEMP, page 2-72 EQPT:: IMPROPRMVL, page 2-73 EQPT:: INHSWPR, page 2-75 EQPT:: INHSWWKG, page 2-75 EQPT:: LOCKOUT-REQ, page 2-77 EQPT:: MAN-REQ, page 2-88 EQPT:: MANRESET, page 2-88 EQPT:: MEA (EQPT), page 2-90 EQPT:: MEM-GONE, page 2-91 EQPT:: MEM-LOW, page 2-92 EQPT::PEER-NORESPONSE, page 2-94 EQPT:: PROTNA, page 2-97 EQPT:: PWR-REDUN, page 2-100 EQPT:: SD, pa
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) FAN:: MEM-GONE, page 2-91 FAN:: MFGMEM, page 2-92 HDGE [G1000]:: AS-CMD, page 2-23 HDGE [G1000]:: AS-MT, page 2-23 HDGE [G1000]:: CARLOSS (G Series), page 2-33 HDGE [G1000]:: LPBKTERMINAL (G-Series), page 2-88 HDGE [G1000]:: TPTFAIL (G-Series), page 2-120 NBR:: SD, page 2-104 NE:: AS-CMD, page 2-23 NE:: AUD-LOG-LOW, page 2-24 NE:: AUD-LOG-LOSS, page 2-24 NE:: BAT-A-HGH-VLT, page 2-28 NE:: BAT-A-LOW-
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) NESYNCH:: FSTSYNC, page 2-71 NESYNCH:: HLDOVRSYNC, page 2-73 NESYNCH:: MANSWTOINT, page 2-89 NESYNCH:: MANSWTOPRI, page 2-89 NESYNCH:: MANSWTOSEC, page 2-89 NESYNCH:: MANSWTOTHIRD, page 2-89 NESYNCH:: SSM-PRS, page 2-111 NESYNCH:: SSM-RES, page 2-112 NESYNCH:: SSM-SMC, page 2-112 NESYNCH:: SSM-ST2, page 2-112 NESYNCH:: SSM-ST3, page 2-112 NESYNCH:: SSM-ST3E, page 2-112 NESYNCH:: SSM-ST4, page 2-113
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) OCN:: FAILTOSWR, page 2-56 OCN:: FAILTOSWS, page 2-58 OCN:: FE-EXERCISING-RING, page 2-64 OCN:: FE-EXERCISING-SPAN, page 2-64 OCN:: FE-FRCDWKSWPR-RING, page 2-65 OCN:: FE-FRCDWKSWPR-SPAN, page 2-65 OCN:: FE-LOCKOUTOFPR-SPAN, page 2-66 OCN:: FE-MANWKSWPR-RING, page 2-68 OCN:: FE-MANWKSWPR-SPAN, page 2-68 OCN:: FEPRLF, page 2-69 OCN:: FORCED-REQ-RING, page 2-69 OCN:: FORCED-REQ-SPAN, page 2-70 OCN:: L
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) OCN:: SSM-ST3E, page 2-112 OCN:: SSM-ST4, page 2-113 OCN:: SSM-STU, page 2-113 OCN:: SSM-TNC, page 2-113 OCN:: SYNC-FREQ, page 2-116 OCN:: WKSWPR, page 2-124 OCN:: WTR, page 2-124 STSMON:: AIS-P, page 2-17 STSMON:: AUTOSW-AIS, page 2-25 STSMON:: AUTOSW-LOP (STSMON), page 2-26 STSMON:: AUTOSW-PDI, page 2-26 STSMON:: AUTOSW-SDBER, page 2-27 STSMON:: AUTOSW-SFBER, page 2-27 STSMON:: AUTOSW-UNEQ (STSMO
Chapter 2 Alarm Troubleshooting Alarm Index by Alarm Type Table 2-6 Alarm Index by Alarm Type (continued) STSTERM:: UNEQ-P, page 2-122 VT-MON:: AIS-V, page 2-17 VT-MON:: AUTOSW-AIS, page 2-25 VT-MON:: AUTOSW-LOP (VTMON), page 2-26 VT-MON:: AUTOSW-UNEQ (VTMON), page 2-28 VT-MON:: FAILTOSW-PATH, page 2-55 VT-MON:: FORCED-REQ, page 2-69 VT-MON:: LOCKOUT-REQ, page 2-77 VT-MON:: LOP-V, page 2-81 VT-MON:: MAN-REQ, page 2-88 VT-MON:: UNEQ-V, page 2-123 VT-MON:: WKSWPR, page 2-124 VT-MON:: WTR, page 2-124 VT-TE
Chapter 2 Alarm Troubleshooting Trouble Notifications Table 2-7 NERING Alarm Type/Object Definition (continued) Represents the ring status in the NE NE-SYNCH Represents the timing status of the NE OCN An OC-N line on an OCN card STSMON STS alarm detection at the monitor point (upstream from the cross-connect) STSTERM STS alarm detection at termination (downstream from the cross-connect) VT-MON VT1 alarm detection at the monitor point (upstream from the cross-connect) VT-TERM VT1 alarm detect
Chapter 2 Alarm Troubleshooting Safety Summary Minor alarms, such as the FSTSYNC alarm (see page 2-71), do not have a serious affect on service. FSTSYNC lets you know that the ONS 15327 is choosing a new timing reference because the old reference failed. The loss of the prior timing source is something a user needs to look at, but it should not immediately disrupt service. Telcordia standard severities are the default settings for the ONS 15327.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note When checking alarms, make sure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, see the Cisco ONS 15327 Procedure Guide. 2.6.1 AIS • Not Reported (NR), Non-Service Affecting (NSA) The Alarm Indication Signal (AIS) condition in the SONET overhead is secondary to another alarm occurring simultaneously in an upstream node.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.3 AIS-P • Not Reported (NR), Non-Service Affecting (NSA) The AIS Path (AIS-P) condition means there is an error in the SONET overhead at the path layer. The AIS-P condition is secondary to another alarm occurring simultaneously in an upstream node. The AIS-P is caused by an incomplete circuit path, for example, when the port on the reporting node is in service (IS), but a node upstream on the circuit does not have its port in service.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.5 APSB • Minor (MN), Non-Service Affecting (NSA) The Automatic Protection Switching (APS) Channel Byte Failure (APSB) alarm occurs when line terminating equipment detects protection switching byte failure in the incoming APS signal. The failure occurs when an inconsistent APS byte or invalid code is detected.
Chapter 2 Alarm Troubleshooting Alarm Procedures Warning Invisible laser radiation might 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 might pose an eye hazard.
Chapter 2 Alarm Troubleshooting Alarm Procedures Warning Invisible laser radiation might 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 might pose an eye hazard.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.9 APSCM • Major (MJ), Service Affecting (SA) The APS Channel Mismatch (APSCM) alarm occurs when the ONS 15327 expects a working channel but receives a protection channel. In many cases, the working and protection channels are crossed and the protect channel is active. If the fibers are crossed and the working line is active, the alarm does not occur.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 If two nodes have the same node ID number, complete the “Change a Node ID Number” procedure on page 2-126 to change one node’s ID number so that each node ID is unique. Note If the node names shown in the network view do not correlate with the node IDs, log into each node and click the Provisioning > BLSR tabs. The BLSR window shows the node ID of the login node.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.12 AS-CMD • Not Alarmed (NA), Non-Service Affecting (NSA) The Alarms Suppressed by User Command (AS-CMD) condition applies to the network element (NE, or node) and cards. It occurs when alarms are suppressed for one or more cards or for the entire shelf. Procedure: Clear the AS-CMD Condition Step 1 In node view, click the Conditions tab. Step 2 Click Retrieve.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the AS-MT Condition Step 1 Complete the “Clear a Loopback” procedure on page 2-128. Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.16 AUTORESET • Minor (MN), Non-Service Affecting (NSA) The Automatic System Reset (AUTORESET) alarm occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot. This alarm typically clears after a card reboots (up to ten minutes). If the alarm does not clear, complete the following procedure. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.18 AUTOSW-LOP (STSMON) • Not Alarmed (NA), Non-Service Affecting (NSA) The Automatic UPSR Switch Caused by Loss of Pointer (LOP) condition indicates that automatic UPSR protection switching occurred because of an LOP-P alarm (see page 2-80). If the UPSR is configured for revertive switching, it will revert to the working path after the fault clears.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.21 AUTOSW-SDBER • Not Alarmed (NA), Non-Service Affecting (NSA) The Automatic UPSR Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that an SD condition (see page 2-104) caused automatic UPSR protection switching to occur. The UPSR is configured for revertive switching and reverts to the working path when the SD is resolved.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.24 AUTOSW-UNEQ (VTMON) • Minor (MN), Service Affecting (SA) AUTOSW-UNEQ (VTMON) indicates that an UNEQ-V alarm (see page 2-123) caused automatic UPSR protection switching to occur. If the UPSR is configured for revertive switching, it will revert to the working path after the fault clears. Procedure: Clear the AUTOSW-UNEQ (VTMON) Alarm Step 1 Complete the “Clear the UNEQ-V Alarm” procedure on page 2-124.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.27 BAT-B-HGH-VLT • Not Reported (NR), Non-Service Affecting (NSA) The High Voltage Battery B (BAT-B-HGH-VLT) condition occurs when the voltage level on battery lead B is between –52 VDC and –56.7 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains under this range for 120 seconds. Procedure: Clear the BAT-B-HGH-VLT Condition Step 1 The problem is external to the ONS 15327.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the BKUPMEMP Alarm Step 1 Verify that both XTC cards are powered and enabled by confirming lighted ACT/STBY LEDs on the XTC cards. Step 2 If both XTC cards are powered and enabled, reset the active XTC card to it standby and make the standby XTC card active. Complete the “Reset the Active XTC Card in CTC” procedure on page 2-129. Verify that the active card you reset is now standby.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.31 CARLOSS (EQPT) • Major (MJ), Service Affecting (SA) A Carrier Loss on the LAN Equipment (CARLOSS) alarm occurs when the ONS 15327 and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the XTC card. The CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the ONS 15327.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 7 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.32 CARLOSS (E Series) • Major (MJ), Service Affecting (SA) A Carrier Loss alarm on the LAN E-series Ethernet (traffic) card is the data equivalent of an LOS (OC-N) alarm (see page 2-84). The Ethernet card has lost its link and is not receiving a valid signal.
Chapter 2 Alarm Troubleshooting Alarm Procedures When replacing a card with an identical type of card, no additional CTC provisioning is required. Note Step 8 If a CARLOSS alarm repeatedly appears and clears, use the following steps to examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect.
Chapter 2 Alarm Troubleshooting Alarm Procedures the reporting card. If a turned-off transmitter causes the CARLOSS alarm, other alarms such as a TPTFAIL (G-Series) alarm (see page 2-120) or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G-Series) alarm. Refer to the Cisco ONS 15327 Reference Manual for a description of the G1000-2 card's end-to-end Ethernet link integrity capability.
Chapter 2 Alarm Troubleshooting Alarm Procedures When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition might be the G1000-2's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm. Note Step 9 Step 10 If the TPTFAIL alarm was not reported, verify whether a terminal loopback has been provisioned on the port: a. In node view, click the card to go to card view. b. Click the Conditions tab and the Retrieve Conditions button. c.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 13 If the alarm does not clear, complete the “Physically Replace a Card” procedure on page 2-130 for the Ethernet (traffic) card. Note Step 14 When replacing a card with an identical type of card, no additional CTC provisioning is required. If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.35 COMIOXC • Critical (CR), Service Affecting (SA) The Input/Output Slot To XTC Communication Failure (COMIOXC) alarm is caused by a communication error in the XTC card to a high-speed traffic card slot. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 Position the cursor over the XTC card in Slot 6 and complete the “Reset the Active XTC Card in CTC” procedure on page 2-129 to make the standby XTC in Slot 5 active. Step 3 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the “Remove and Reinsert (Reseat) the Standby XTC” procedure on page 3-3.
Chapter 2 Alarm Troubleshooting Alarm Procedures An XTC A to Shelf Slot Communication Failure alarm occurs when the XTC card in Slot 5 (XTC A) has lost communication with another card in the shelf The other card is identified by the Object column in the CTC alarm window.. The CONTBUS-IO-A alarm can appear briefly when the ONS 15327 switches to the standby XTC card. In the case of an XTC protection switch, the alarm clears after the other cards establish communication with the new active XTC card.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 9 If the reset card or replaced card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the “Remove and Reinsert (Reseat) the Standby XTC” procedure on page 3-3. If the TAC technician tells you to remove the card and reinstall a new one, follow the “Physically Replace a Card” procedure on page 2-130.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 5 Verify the following LED behavior: • The FAIL LED blinks for approximately 30 seconds. • All LEDs blink once and turn off. • The ACT/STBY LED is green (active). Step 6 If CONTBUS-IO-B is raised on several cards at once, complete the “Reset the Active XTC Card in CTC” procedure on page 2-129. Verify that the card reboots as the standby card.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the CTNEQPT-PBPROT Alarm Step 1 Perform a CTC reset on the standby XTC card. Complete the “Reset a Traffic Card in CTC” procedure on page 2-129. (The procedure is the same for the standby XTC as for the traffic card.) Resetting the standby XTC card will not make it active. Verify that its LED is amber once the reset is complete.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.41 CTNEQPT-PBWORK • Critical (CR), Service Affecting (SA) The Interconnection Equipment Failure Working XTC Card Payload Bus (CTNEQPT-PBWORK) alarm indicates a failure in the main payload bus between the active XTC card the reporting traffic card. The XTC card and the reporting card are no longer communicating. The problem exists in the XTC card or the reporting traffic card.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 7 Verify that the reset is complete and error-free: • No new alarms appear in the Alarms window in CTC. • If you are looking at the physical ONS 15327, the ACT/STBY LED is illuminated. • If you are looking at the node view of the ONS 15327, an amber LED depiction with “Sby” has replaced the white “LDG” depiction on the card in CTC.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.43 DBOSYNC • Major (MJ), Non-Service Affecting (NSA) The Standby Database Out of Synchronization (DBOSYNC) alarm occurs when the standby XTC “To be Active” database does not synchronize with the “Active” database on the active XTC. Caution If you reset the active XTC while this alarm is raised, you will lose current provisioning. Procedure: Clear the DBOSYNC Alarm Step 1 Save a backup copy of the active XTC database.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the DS3-MISM Condition Step 1 Display the CTC card view for the reporting (active) XTC-28-3 card. Step 2 Click the Provisioning > DS1 > Line tabs. Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal (ESF, D4, or unframed). Step 4 If the Line Type drop-down menu does not match the expected incoming signal, select the correct Line Type in the drop-down menu.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the EHIBATVG-B Alarm Step 1 The problem is external to the ONS 15327. Troubleshoot the power source supplying battery lead B. Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.49 EOC • Major (MJ), Non-Service Affecting (NSA) The SONET DCC Termination Failure (EOC) alarm occurs when the ONS 15327 loses its data communications channel. The DCC is three bytes, D1 through D3, in the SONET overhead that convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15327 uses the DCC on the SONET section layer to communicate network management information.
Chapter 2 Alarm Troubleshooting Alarm Procedures e. Step 7 If the State column lists the port as OOS, click the column and click IS from the drop-down menu. Click Apply. If the OC-N card is in service, use an optical test set to verify 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 (traffic) card.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.50 EQPT • Critical (CR), Service Affecting (SA) An Equipment Failure (EQPT) alarm indicates that a hardware failure has occurred on the reporting card. If the EQPT alarm occurs with a BKUPMEMP alarm, see the “BKUPMEMP” section on page 2-29. The BKUPMEMP procedure also clears the EQPT alarm. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.51 EQPT-MISS • Critical (CR), Service Affecting (SA) The Replaceable Equipment or Unit Missing (EQPT-MISS) alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or not fully inserted. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 7 Change the West Line drop-down menu to the slot you recorded for the East Line in Step 3. Step 8 Change the East Line drop-down menu to the slot you recorded for the West Line in Step 3. Step 9 Click OK. Step 10 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note EXERCISE-SPAN-REQ is an informational condition. It does not require troubleshooting. 2.6.56 EXT • Minor (MN), Non-Service Affecting (NSA) A Failure Detected External to the NE (EXT) alarm occurs because an environmental alarm is present, for example, a door is open or flooding has occurred. Procedure: Clear the EXT Alarm Step 1 In node view, click the Maintenance tab to gather further information about the EXT alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the FAILTOSW Condition Step 1 Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the 1:N electrical card or 1+1 optical card and clears the FAILTOSW.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 If the condition does not clear, replace the active OC-N card that is reporting the higher priority alarm. Complete the “Physically Replace a Card” procedure on page 2-130. Replacing the active OC-N card that is reporting the higher priority alarm allows traffic to revert to the active slot. Reverting frees the standby card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW-PATH alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 5 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards are active and in service: a. Confirm that the OC-N card shows a green LED in CTC or on the physical card. A green LED indicates an active card. An amber LED indicates a standby card. b. To determine whether the OC-N port is in service, double-click the card in CTC to display the card view. c. Click the Provisioning > Line tabs. d.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.61 FAILTOSWS • Not Alarmed (NA), Non-Service Affecting (NSA) The Failure to Switch to Protection Span (FAILTOSWS) condition signals an APS span switch failure. FAILTOSWS clears when one of the following actions occur: a higher priority event such as an external switch command occurs; the next span switch succeeds; or an SD condition (see page 2-104) or SF condition (see page 2-106) causing an APS switch clears.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 8 b. To determine whether the OC-N port is in service, double-click the card in CTC to display the card view. c. Click the Provisioning > Line tabs. d. Verify that the State column lists the port as in service (IS). e. If the State column lists the port as OOS, click the column and choose IS. Click Apply. If the correct port is in service, use an optical test set to verify that a valid signal exists on the line.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the FAN Alarm Step 1 Verify whether the air filter needs replacement. Complete the “Inspect, Clean, and Replace the Reusable Air Filter” procedure on page 3-3. Step 2 If the filter is clean, complete the “Remove and Reinsert Fan-Tray Assembly” procedure on page 2-130. Note The fan-tray assembly should run immediately when correctly inserted.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.65 FE-DS1-MULTLOS • Not Alarmed (NA), Non-Service Affecting (NSA) The Far-End Multiple DS-1 LOS Detected (FE-DS1-MULTLOS) condition occurs when multiple DS-1 signals are lost at the far-end node. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-MULTLOS condition. Troubleshoot the FE condition or condition by troubleshooting the main alarm at its source.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.67 FE-DS1-SA • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End DS-1 Equipment Failure Service Affecting (FE-DS1-SA) condition occurs when there is a far-end equipment failure on an XTC card that affects service because traffic is unable to switch to the protect port. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-SA alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.69 FE-DS3-NSA • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End DS-3 Equipment Failure Non-Service Affecting (FE-DS3-NSA) condition occurs when a far-end XTC-28-3 card equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting FE-DS3-NSA alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.71 FE-EQPT-NSA • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End Common Equipment Failure Non-Service Affecting (FE-EQPT-NSA) condition occurs when a non-service affecting equipment failure is detected on a far-end XTC card. The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-EQPT-NSA alarm. Troubleshoot the FE condition or condition by troubleshooting the main alarm at its source.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note FE-EXERCISING-SPAN is an informational condition. It does not require troubleshooting. 2.6.74 FE-FRCDWKSWPR-RING • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End Ring Working Facility Forced to Switch to Protection (FE-FRCDWKSWPR-RING) condition occurs from a far-end node when a ring is forced from working to protect using the FORCE RING command.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.76 FE-IDLE • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End Idle (FE-IDLE) condition occurs when a far-end node detects an idle DS-3 signal. The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-IDLE condition.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.78 FE-LOF • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End LOF (FE-LOF) condition occurs when a far-end node reports an LOF (DS-3) alarm (see page 2-79). The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-LOF condition. Troubleshoot the FE condition or condition by troubleshooting the main alarm at its source. Both alarms or conditions clear when the main alarm clears.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.80 FE-MANWKSWPR-RING • Not Alarmed (NA), Non-Service Affecting (NSA) The Far End Ring Manual Switch of Working Facility to Protect (FE-MANWKSWPR-RING) condition occurs when a BLSR working ring is switched from working to protect at a far-end node using the MANUAL RING command. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-MANWKSWPR-RING condition.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.82 FEPRLF • Minor (MN), Non-Service Affecting (NSA) The Far End Protection Line Failure (FEPRLF) alarm occurs when an APS channel SF condition (see page 2-106) occurs on the protect card coming into the node. Note The FEPRLF alarm occurs only on the ONS 15327 when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration or BLSR configuration.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the FORCED-REQ-RING Condition Step 1 Complete the “Clear the FORCED-REQ Condition” procedure on page 2-69. Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.88 FRCDSWTOSEC • Not Alarmed (NA), Non-Service Affecting (NSA) The Force Switch to Second Timing Source (FRCDSWTOSEC) condition occurs when the user issues a Force command to switch to the second timing source. Note FRCDSWTOSEC is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). Note FSTSYNC is an informational alarm. The alarm does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note The fan-tray assembly should run immediately when correctly inserted. Step 6 If the fan does not run or the alarm persists, complete the “Replace the Fan-Tray Assembly” procedure on page 3-1. Step 7 If the replacement fan-tray assembly does not operate correctly, log onto http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot. Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots.
Chapter 2 Alarm Troubleshooting Alarm Procedures c. Step 7 Click Delete and click Yes in the dialog box that appears. If the card is used as a timing reference, change the timing reference: a. Click the Provisioning > Timing tabs. b. Under NE Reference, click the drop-down menu for Ref-1. c. Change Ref-1 from the listed OC-N card to Internal Clock. d. Click Apply. Step 8 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the INHSWWKG Condition Step 1 Complete the “Clear an External Switching Command” procedure on page 2-128. Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.99 INVMACADR • Major (MJ), Non-Service Affecting (NSA) The Equipment Failure Invalid MAC Address (INVMACADR) alarm occurs when the ONS 15327 MAC Address is invalid.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.102 LOCKOUT-REQ • Not Alarmed (NA), Non-Service Affecting (NSA) The Lock Out Switch Request on Facility/Equipment (LOCKOUT-REQ) condition occurs when a user initiates a lock out switch request for an OC-N card or a lock out switch request on a UPSR at the path level. A lock out prevents protection switching. Clearing the lock out again allows protection switching and clears the LOCKOUT-REQ condition.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the LOF (BITS) Alarm Step 1 Verify that the framing and line coding match between the BITS input and the XTC: a. In node view or card view, note the slot and port reporting the alarm. b. Find the framing and coding formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself. c.
Chapter 2 Alarm Troubleshooting Alarm Procedures e. Verify that the line type of the reporting port matches the line type of the signal source (DS4 and DS4, unframed and unframed, or ESF and ESF). If the signal source line type does not match the reporting port, click the Line Type cell to reveal a drop-down menu and choose the matching type. f. Verify that the reporting Line Coding matches the signal source’s line coding (AMI and AMI or B8ZS and B8ZS).
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.107 LOF (OC-N) • Critical (CR), Service Affecting (SA) The OC-N LOF alarm occurs when a port on the reporting OC-N card has an LOF condition. LOF indicates that the receiving ONS 15327 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the LOP-P Alarm Step 1 In node view, click the Circuits tab and view the alarmed circuit. Step 2 Verify that the correct circuit size is listed in the Size column.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the LOS (BITS) Alarm Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15327 MIC to the timing source. Step 2 If wiring is correct, verify that the BITS clock is operating properly.
Chapter 2 Alarm Troubleshooting Alarm Procedures For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible. Step 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected. Step 5 If a valid signal exists, replace the DS-N connector on the MIC card. Step 6 Repeat Steps 1 through 5 for any other port on the card that reports the LOS.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 If the cabling is correct, verify that the correct port is in service (IS): Step 3 Confirm that the OC-N card shows a green LED in CTC or on the physical card. A green LED indicates an active card. An amber LED indicates a standby card. Step 4 f. To determine whether the OC-N port is in service, double-click the card in CTC to display the card view. g. Click the Provisioning > Line tabs. h.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Note Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. If a circuit shows an incomplete state when this alarm is raised, the logical circuit is in place and will be 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 2.6.114 LPBKCRS • Not Alarmed (NA), Non-Service Affecting (NSA) The Loopback XTC (LPBKCRS) condition indicates that there is a software cross-connect loopback active between a traffic card and an XTC card. A cross-connect loopback is a sub-line speed test that does not affect traffic. For more information on loopbacks, see the “Identify Points of Failure on a DS-N Circuit Path” section on page 1-4.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.116 LPBKFACILITY (OC-N) • Not Alarmed (NA), Non-Service Affecting (NSA) An OC-N Loopback Facility condition occurs when a software facility loopback is active for a port on the reporting card. For more information about loopbacks, see the “Identify Points of Failure on an OC-N Circuit Path” section on page 1-21. Procedure: Clear the LPBKFACILITY (OC-N) Condition Step 1 Complete the “Clear a Loopback” procedure on page 2-128.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.118 LPBKTERMINAL (G-Series) • Not Alarmed (NA), Non-Service Affecting (NSA) A G-Series Loopback Terminal condition occurs when a software terminal loopback is active for a port on the reporting card. When a port in terminal loopback, its outgoing signal is redirected into the receive direction on the same port, and the externally received signal is ignored.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.121 MANSWTOINT • Not Alarmed (NA), Non-Service Affecting (NSA) The Manual Switch To Internal Clock (MANSWTOINT) condition occurs when the NE timing source is manually switched to the internal timing source. Note MANSWTOINT is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Clear the MANUAL-REQ-RING Condition Step 1 Complete the “Clear a BLSR Span Lock Out” procedure on page 2-127. Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 If you prefer the card that physically occupies the slot and the card is not in service, has no circuits mapped, and is not part of a protection group, put the cursor over the provisioned card in CTC and right-click to choose Delete Card. The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.129 MEM-LOW • Minor (MN), Non-Service Affecting (NSA) The Free Memory of Card Almost Gone (MEM-LOW) alarm occurs when data generated by software operations is close to exceeding the memory capacity of the XTC card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the XTC card is exceeded, CTC ceases to function. The alarm does not require user intervention.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.131 PDI-P • Not Alarmed (NA), Non-Service Affecting (NSA) A PDI Path (PDI-P) condition indicates a signal label mismatch failure (SLMF). An invalid signal label C2 byte in the SONET path overhead causes an SLMF. The C2 byte tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15327 Procedure Guide for detailed procedures to create circuits. Step 5 If circuit deletion and recreation does not clear the condition, verify that the far-end OC-N card providing STS payload to the reporting card is not errored. Step 6 If the condition does not clear, confirm the cross-connect between the OC-N card and the reporting card.
Chapter 2 Alarm Troubleshooting Alarm Procedures • Step 5 If you are looking at the node view of the ONS 15327, an amber LED depiction with “Sby” has replaced the white “LDG” depiction on the card in CTC. If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.133 PLM-P • Critical (CR), Service Affecting (SA) A Payload Label Mismatch Path (PLM-P) alarm indicates that signal does not match its label.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 5 If the circuit deletion and recreation does not clear the alarm, verify the far-end OC-N card that provides STS payload to the XTC card. Step 6 If the alarm does not clear, verify the cross-connect between the OC-N card and the XTC card. Step 7 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15327 Procedure Guide.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 2 Find the node ID by completing the “Identify a Ring ID or Node ID Number” procedure on page 2-125. Step 3 Repeat Step 2 for all the nodes on the ring. Step 4 If two nodes have an identical node ID number, complete the “Change a Node ID Number” procedure on page 2-126 so that each node ID is unique. Step 5 If the alarm does not clear, log onto http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 7 • All LEDs blink once and turn off. • The ACT/STBY LED is green (active). If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 6 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.138 PWR-B • Minor (MN), Non-Service Affecting (NSA) An NE Power Failure at Connector B alarm indicates that the power is out of the specified 48 VDC input range and is either too high (overvoltage) or too low (undervoltage), requiring you to check the incoming power feed or separate power distribution equipment, or both.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.139 PWR-REDUN • Minor (MN), Non-Service Affecting (NSA) The Redundant Power Capability Lost (PWR-REDUN) alarm applies to cards that have two built-in fuses (such as newer optical cards). The alarm indicates that one of the fuses has blown and must be serviced. When this alarm occurs, the card’s power redundancy is lost because only one card power connection can contact one of the redundant power supplies.
Chapter 2 Alarm Troubleshooting Alarm Procedures A Facility Termination Equipment Receiver Missing (RCVR-MISS) alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its connector. Incorrect impedance usually occurs when a receive cable is missing from the XTC DS-1 port or a possible mismatch of equipment occurs. Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 4 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.143 RFI-P • Not Reported (NR), Non-Service Affecting (NSA) An RFI Path condition occurs when the ONS 15327 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-P condition in the reporting node. RFI-P occurs in the node that terminates a path.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the RFI-V Condition Step 1 Verify that the connectors are securely fastened and connected to the correct slot. For more information, refer to the Cisco ONS 15327 Procedure Guide.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 6 Complete the “Change a Ring ID Number” procedure on page 2-125. Step 7 Verify that the ring map is correct. Step 8 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the SD Condition Step 1 Complete the “Verify BER Threshold Level” procedure on page 2-129.
Chapter 2 Alarm Troubleshooting Alarm Procedures For UPSR protected circuits, the BER threshold on the ONS 15327 is user provisionable and has a range for SD from 10–9 to 10–5. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user provisionable and the error rate is hard-coded to 10–6. On UPSR, an SD-P condition causes a switch from the working card to the protect card at the path (STS) level. On BLSR 1+1 or on unprotected circuits, an SD-P condition does not cause switching.
Chapter 2 Alarm Troubleshooting Alarm Procedures An SF Line (SF-L) condition is similar to an SF condition (see page 2-106) but it applies to the line layer of the signal. Procedure: Clear the SF-L Condition Step 1 Complete the “Clear the SD Condition” procedure on page 2-105. Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note SFTWDOWN is an informational alarm. 2.6.155 SNTP-HOST • Minor (MN), Non-Service Affecting (NSA) The Simple Network Timing Protocol (SNTP) Host Failure (SNTP-HOST) alarm indicates that an ONS node serving as an IP proxy for the other ONS nodes in the ring is not forwarding SNTP information to the other ONS nodes in the network.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Span Switch is Active West Side (SPAN-SW-WEST) condition occurs when a span switch occurs at the west side of a BLSR span. The condition clears when the switch is cleared. Note SPAN-SW-EAST is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 5 If the signal is valid, verify that the power level of the optical signal is within the optical card’s receiver specifications. Refer to the Cisco ONS 15327 Reference Manual for card specifications. Step 6 If the receiver levels are correct, ensure that the optical transmit and receive fibers are connected properly. Step 7 If the connectors are correct, complete the “Physically Replace a Card” procedure on page 2-130 for the OC-N card.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.161 SSM-LNC • Not Alarmed (NA), Non-Service Affecting (NSA) The SSM Local Node Clock (LNC) Traceable condition occurs when the SSM (S1) byte of the SONET overhead multiplexing section has been changed to signify that the line or BITS timing source is LNC-quality. Note SSM-LNC is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.165 SSM-RES • Not Alarmed (NA), Non-Service Affecting (NSA) The SSM Reserved (RES) For Network Synchronization Use condition occurs when the synchronization message quality level is changed to RES. Note SSM-RES is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Note SSM-ST3E is an informational condition. It does not require troubleshooting. 2.6.170 SSM-ST4 • Not Alarmed (NA), Non-Service Affecting (NSA) The SSM Stratum 4 (ST4) Traceable condition occurs when the synchronization message quality level is lowered to ST4. The message quality is not used because it is below ST3. Note SSM-ST4 is an informational condition. It does not require troubleshooting. 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures The Switching Matrix Module Failure (SWMTXMOD) alarm occurs on the XTC card or a traffic card. If the alarm reports against a traffic card, it occurs when the logic component on the XTC card is out of frame (OOF) with the logic component on the reporting traffic card. All traffic on the reporting traffic card is lost.
Chapter 2 Alarm Troubleshooting Alarm Procedures • If you are looking at the node view of the ONS 15327, an amber LED depiction with “Sby” has replaced the white “LDG” depiction on the card in CTC. Step 8 If the alarm does not clear, complete the “Remove and Reinsert (Reseat) a Card” procedure on page 2-130 for the traffic card. Step 9 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Procedure: Procedure: Clear the SWTOTHIRD Condition Step 1 To clear the condition, clear alarms related to failures of the primary source, such as a SYNCPRI alarm (see page 2-117) or a SYNCSEC alarm (see page 2-117). Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 3 If the SYNC-FREQ alarm continues to report after replacing the XTC card, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.178 SYNCPRI • Minor (MN), Non-Service Affecting (NSA) A Loss of Timing on Primary Reference (SYNCPRI) alarm occurs when the ONS 15327 loses the primary timing source (reference 1). The ONS 15327 uses three ranking timing references.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 5 If the secondary timing source is an incoming port on the ONS 15327, complete the “Clear the LOS (OC-N) Alarm” procedure on page 2-85. Step 6 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447). 2.6.180 SYNCTHIRD • Minor (MN), Non-Service Affecting (NSA) A Loss of Timing on Third Reference (SYNCTHIRD) alarm occurs when the ONS 15327 loses the third timing source (reference 3).
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.181 SYSBOOT • Major (MJ), Service Affecting (SA) The System Reboot (SYSBOOT) alarm indicates that new software is booting on the XTC card. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 10 minutes if the same version of software is present on both cards, or up to 30 minutes if the software is being updated from one XTC to the other. If it does not clear, log onto http://www.cisco.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 8 Click Close. Step 9 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.183 TPTFAIL (G-Series) • Major (MJ), Service Affecting (SA) The Transport (TPT) Layer Failure alarm for the G-series Ethernet (traffic) cards indicates a break in the end-to-end Ethernet link integrity feature of the G1000-2 cards.
Chapter 2 Alarm Troubleshooting Alarm Procedures Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots. Procedure: Clear the TRMT Alarm Step 1 Complete the “Physically Replace a Card” procedure on page 2-130 for the reporting XTC-14 card. Note Step 2 When replacing a card with an identical type of card, no additional CTC provisioning is required.
Chapter 2 Alarm Troubleshooting Alarm Procedures 2.6.186 UNEQ-P • Critical (CR), Service Affecting (SA) An SLMF UNEQ Path alarm occurs when the path does not have a valid sender. The UNEQ-P indicator is carried in the C2 signal path byte in the SONET overhead. The source of the problem is the node that is transmitting the signal into the node reporting the UNEQ-P. The alarm might result from an incomplete circuit or an empty VT tunnel. UNEQ-P occurs in the node that terminates a path.
Chapter 2 Alarm Troubleshooting Alarm Procedures Step 7 Step 8 If all ONS nodes in the ring appear in the CTC network view, verify or not whether there are incomplete circuits: a. Click the Circuits tab. b. Verify that INCOMPLETE is not listed in the State column of any circuits. If you find circuits listed as incomplete, use an optical test set to verify that these circuits are not working circuits that continue to pass traffic.
Chapter 2 Alarm Troubleshooting XTC Line Alarms Procedure: Clear the UNEQ-V Alarm Step 1 Complete the “Clear the UNEQ-P Alarm” procedure on page 2-122. Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447). 2.6.
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting Table 2-8 DS3-12E Line Alarms Alarm UNFRAMED D4 ESF LOS Yes Yes Yes AIS Yes Yes Yes LOF No Yes Yes IDLE No Yes Yes RAI No Yes Yes Terminal Lpbk Yes Yes Yes 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
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting Step 4 Highlight the ring and click Edit. Step 5 In the BLSR window, enter the new ID in the Ring ID field. Step 6 Click Apply. Step 7 Click Yes at the Changing Ring ID dialog box. Procedure: Change a Node ID Number Step 1 Log into a node on the network. If you are already logged in, go to Step 2. Step 2 In node view, click View > Go to Network View. Step 3 Click the Provisioning > BLSR tabs.
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting c. In the Port State area, click the Set to IS radio button. d. Verify that the Disable OSPF on Link check box is unchecked. e. Click OK. Procedure: Lock Out a BLSR Span Step 1 Log into a node on the network. If you are already logged in, go to Step 2. Step 2 In node view, click the Maintenance > BLSR tabs. Step 3 Click the BLSR row table cell under the West Switch column to reveal the drop-down menu.
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting Step 2 Display the node view. Step 3 In node view, click the Maintenance > Protection tabs. Step 4 Double-click the protection group that contains the reporting card. Step 5 Click the working/active card of the selected groups. Step 6 Click FORCE and Yes in the Confirmation dialog box. Procedure: Clear an External Switching Command Step 1 Log into a node on the network. If you are already logged in, go to Step 2.
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting Procedure: Reset the Active XTC Card in CTC Caution Note Resetting the active XTC card can be service-affecting. Before you reset the XTC, 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, go to Step 2. Step 2 Identify the active XTC.
Chapter 2 Alarm Troubleshooting Common Procedures in Alarm Troubleshooting Step 4 Under the SD BER (or SF BER) column on the Provisioning window, verify that the cell entry is consistent with the originally provisioned threshold. The default setting is 1E–7. Step 5 If the entry is consistent with what the system was originally provisioned for, go back to your original procedure.
C H A P T E R 3 Replace Hardware This chapter provides procedures for replacing Cisco ONS 15327 hardware. • 3.1 Replace the Fan-Tray Assembly, page 3-1—Complete this procedure to replace the fan-tray assembly. • 3.2 Remove and Reinsert (Reseat) the Standby XTC, page 3-3—Complete this procedure as needed to reset the XTC by performing a card pull. • 3.3 Inspect, Clean, and Replace the Reusable Air Filter, page 3-3—Complete this procedure to replace a reusable or disposable air filter. 3.
Chapter 3 Replace Hardware Replace the Fan-Tray Assembly Removing the Fan-Tray Assembly OC12/STM-4 IR 1310 FAIL SF LAN CRAFT ACO E10/100-T 1 3 4 Rx 1 SF 2 3 MIC B ACT 1 CRAFT FAN STATUS FAIL Rx 2 CISCO ON OPTICAL Rx 3 4 BITS FAIL ACT Tx 1 MIC A SF DS3 SF DS1 SF PWR A PWR B CRIT MAJ MIN REM LAN ACO 2 ACT/STBY SYNC ACO XTC-28-3 OC48/STM-16 IR 1310 ACT SF E10/100-T FAIL LAMP TEST FAIL Tx 2 S 15327 NETWORKI NG SYSTE FAIL LAMP TEST ACT/STBY SYNC ACO M DS3 SF DS1 SF
Chapter 3 Replace Hardware Remove and Reinsert (Reseat) the Standby XTC Note The FAN STATUS LED only illuminates when an XTC card is installed. 3.2 Remove and Reinsert (Reseat) the Standby XTC Caution Note Do not perform this action without the supervision and direction of the Cisco Technical Assistance Center (TAC). The Cisco TAC can be reached at (1-800-553-2447). To determine whether you have an active or standby XTC, position the cursor over the XTC card graphic to display the status.
Chapter 3 Replace Hardware Inspect, Clean, and Replace the Reusable Air Filter Step 1 Move any cables that are routed in front of the fan-tray assembly and air filter so you can easily slide the filter out, as shown in Figure 3-3 on page 3-4. Step 2 Grasp the metal tab at the edge of the filter and slide the filter out of the bracket while being careful not to dislodge any dust that may have collected on the filter.
Chapter 3 Replace Hardware Inspect, Clean, and Replace the Reusable Air Filter Replacing the Reusable Fan-Tray Air Filter OC12/STM-4 IR 1310 FAIL SF LAN CRAFT ACO 3 4 Rx 1 1 2 3 MIC B ACT SF Rx 2 FAIL BITS FAIL ACT Tx 1 Tx 2 ACT/STBY SYNC ACO Rx 3 4 SF CRAFT LAMP TEST FAIL DS3 SF DS1 SF PWR A PWR B CRIT MAJ MIN REM LAN ACO 2 MIC A E10/100-T 1 ACT/STBY SYNC ACO XTC-28-3 OC48/STM-16 IR 1310 ACT SF E10/100-T FAIL LAMP TEST FAIL DS3 SF DS1 SF PWR A PWR B CRIT MAJ MIN REM
Chapter 3 Replace Hardware Inspect, Clean, and Replace the Reusable Air Filter Cisco ONS 15327 Troubleshooting Guide, R3.
I N D EX alarm troubleshooting A AMI coding air filter, replacing 3-3 APSB alarm 2-16 troubleshooting description 2-16 description 2-16 2-18 troubleshooting AIS-P condition description 1-68 troubleshooting 2-19 troubleshooting 2-17 1-69 description AIS-V 2-20 troubleshooting on XTC-28-3 unused VT circuits 1-67 description 2-17 2-21 troubleshooting 2-17 Alarm Indication Signal 2-16 description 2-16 Alarm Indication Signal Path 2-17 2-21 troubleshooting 2-17 description ala
Index Audit Trail Log Low Automatic UPSR Switch Caused by Unequipped Path (STSMON) 2-27 2-24 AUD-LOG-LOSS condition description Automatic UPSR Switch Caused by Unequipped Virtual Tributary (VTMON) 2-28 2-24 troubleshooting 2-24 AUD-LOG-LOW 2-24 Automatic UPSR Switched Caused by Alarm Indication Signal 2-25 automatic protection switching byte failure AUTORESET alarm 2-18 description channel failure on protect card channel mismatch inconsistent code invalid k bytes 2-69 2-25 troubleshooting
Index troubleshooting BLSROSYNC alarm 2-28 BAT-A-LOW-VLT condition description description troubleshooting 2-28 troubleshooting BNC connector 2-121 applet security restrictions 2-29 BAT-B-LOW-VLT condition cannot launch Java troubleshooting 1-54 2-29 battery high-voltage alarm C 2-28 low voltage alarm 2-28 cache (Netscape), redirect low-voltage alarm 2-47 CARLOSS (EQPT) alarm BER caused by TPTFAIL 2-106 SF-P condition description 2-107 verify threshold level 2-129 1-54 2-1
Index conditions indexed individually by name gray node icon CONTBUS-A-18 alarm list of alarms description troubleshooting verifying PC connection 2-38 CONTBUS-IO-A alarm description 1-50, 1-51 2-41 troubleshooting 2-39 CONTBUS-IO-B alarm 2-42 CTNEQPT-PBWORK alarm description 2-40 troubleshooting 1-60 CTNEQPT-PBPROT alarm 2-38 troubleshooting CRC 1-59 username and password mismatch troubleshooting description 2-31 release interoperability problems 2-38 description 1-48, 1-54
Index description E-Series Ethernet Carrier Loss on LAN 2-45 troubleshooting E-Series Ethernet Carrier Loss on the LAN 2-46 DS-N cards, loss of signal DS-N Facility Loopback ESF 2-82, 2-83 2-46, 2-78, 2-79, 2-124 carrier loss 2-87 2-32, 2-33 configuring VLANs 1-65 connectivity problems E E10/100-4 card, CARLOSS alarm 2-32 description 2-47 2-47 2-47 2-47 Exercise Request on Ring 2-53 Exercise Request on Span 2-53 EXERCISE-RING-REQ 2-53 EXERCISE-SPAN-REQ 2-53 description 2-48
Index OC-N port Far-End DS-3 Equipment Failure Non-Service Affecting 2-63 1-22 test a destination XTC card test the circuit 1-18 Far-End DS-3 Equipment Failure Service Affecting 1-22 Facility Termination Equipment Receiver Missing 2-101 Far-End DS-3 Idle 2-66 Facility Termination Equipment Transmitter Missing 2-121 Far-End Exercising Ring 2-64 Far-End Exercising Span 2-64 FAILTOSW condition Far-End Lock Out of Protection Span description 2-54 troubleshooting 2-55 FAILTOSW-PATH conditi
Index troubleshooting troubleshooting 2-63 FE-EQPT-NSA condition description FORCED-REQ-RING condition description 2-64 troubleshooting 2-64 FE-EXERCISING-SPAN condition 2-64 FE-FRCDWKSWPR-RING condition 2-65 FE-FRCDWKSWPR-SPAN condition description 2-66 FRCDSWTOPRI 2-70 FSTSYNC 2-67 2-70 2-70 2-71 2-71 2-71 2-71 2-71 2-71 1-70 2-71 2-71 FULLPASSTHR-BI condition description 2-72 troubleshooting 2-68 2-69 2-71 troubleshooting 2-68 troubleshooting 2-70 description FE-MANWKSW
Index H hairpin circuit 2-89 MANSWTOPRI 2-89 MANSWTOSEC create on a destination node create on a source node definition MANSWTOINT 1-14 1-8 1-3 hard reset (card pull) High Temperature 3-3 MANSWTOTHIRD 2-89 RING-SW-EAST 2-104 RING-SW-WEST 2-104 SFTWDOWN 2-72 2-89 2-107 SPAN-SW-EAST 2-108 High Voltage Battery A 2-28 SPAN-SW-WEST 2-108 High Voltage Battery B 2-29 SSM-DUS 2-110 SSM-LNC 2-111 SSM-PRC 2-111 SSM-PRS 2-111 SSM-RES 2-112 HITEMP alarm description 2-72 troubl
Index IP perform a lockout on a BLSR connectivity working span lockout 1-61 designing subnets 2-76 Lock Out of Protection Span 1-62 2-127 2-76 LOCKOUT-REQ condition description J 2-77 troubleshooting 2-77 LOCKOUT-REQ-RING condition Java browser will not launch description 1-48 Java Runtime Environment.
Index LOP-V alarm description troubleshooting 2-81 troubleshooting 2-81 M LOS (BITS) alarm description 2-81 troubleshooting MAC address 2-82 invalid LOS (DS-1) alarm description 2-82 APSCM 2-83 2-21 BLSROSYNC 2-83 2-30 CARLOSS (EQPT) 2-84 troubleshooting 2-21 APSCNMIS LOS (OC-N) alarm description 1-65 major alarms LOS (DS-3) alarm troubleshooting 2-76 mismatch 2-82 troubleshooting description 2-88 2-85 2-31 CARLOSS (E Series) 2-32 CARLOSS (G Series) 2-33 CONTBUS-A-18 2
Index MAN-REQ condition description AUTOSW-LOP (VTMON) AUTOSW-UNEQ (VTMON) 2-88 troubleshooting MANRESET DATAFLT 2-88 2-46 MANSWTOINT 2-89 ELWBATVG-A 2-47 MANSWTOPRI 2-89 ELWBATVG-B 2-47 MANSWTOSEC EXCCOL 2-89 MANSWTOTHIRD EXT 2-89 MANUAL-REQ-RING condition description 2-89 troubleshooting MANUAL-REQ-SPAN condition description 2-54 FE-PRLF 2-69 HITEMP 2-72 PLM-V 2-90 manual switch.
Index not alarmed conditions AS-CMD AS-MT FRCDSWTOPRI FRCDSWTOSEC 2-23 2-71 FRCDSWTOTHIRD 2-23 AUD-LOG-LOSS FRNGSYNC 2-24 AUTOSW-LOP (STSMON) AUTOSW-PDI 2-26 FSTSYNC 2-71 FULLPASSTHR-BI 2-26 2-27 HLDOVRSYNC AUTOSW-SFBER 2-27 INC-ISD AUTOSW-UNEQ (STSMON) CLDRESTART 2-27 INHSWPR 2-75 2-76 EXERCISE-RING-REQ 2-53 LKOUTPR-S EXERCISE-SPAN-REQ 2-53 LOCKOUT-REQ FAILTOSW 2-73 2-75 KB-PASSTHR 2-45 2-72 2-75 INHSWWKG 2-36 2-71 2-71 AUTOSW-SDBER DS3-MISM 2-70 2-76 2-77 LOCKO
Index SQUELCH LOF 2-109 2-80 SSM-DUS 2-110 loopback caveat SSM-FAIL 2-110 OC-3 and DCC limitations SSM-LNC 2-111 replace SSM-OFF 2-111 reseat SSM-PRC 2-111 test SSM-PRS 2-111 transmit and receive levels SSM-RES 2-112 See also specific card names SSM-SMC 1-2 2-130 2-130 1-23, 1-32, 1-37 OC-N Facility Loopback 2-112 SSM-ST2 2-112 OC-N Loss of Frame 2-80 SSM-ST3 2-112 OC-N Loss of Signal 2-84 SSM-ST3E 2-113 SSM-STU 2-113 SWTOPRI 2-115 SWTOSEC 2-87 P Partial Fan F
Index description reset 2-96 troubleshooting automatic card-level reboot 2-96 Primary Non-Volatile Backup Memory Flash Procedural Error Duplicate Node ID retrieve IP address 2-96 Procedural Error Mismatch East/West Direction Procedural Error Mismatch Ring reseat the standby XTC 2-29 2-51 description 2-103 description 2-127 protection switching, UPSR alarms Protection Unit Not Available change identify 2-98 2-125 2-125 RING-MISMATCH alarm 2-98 description PWR-B alarm 2-103 Ring Squ
Index troubleshooting primary reference clock traceable 2-106 SF-L condition description primary reference source traceable quality level degrade 2-106 troubleshooting SFP 2-111 2-110 reserved for network synchronization use 2-107 SONET minimum clock traceable 1-76 SF-P condition description Stratum 2 traceable 2-112 2-112 Stratum 3 traceable 2-112 side switch.
Index description troubleshooting 2-115 troubleshooting SYNCTHIRD alarm 2-116 description SYNC-FREQ condition description SYSBOOT 2-116 Synchronization Frequency Out of Bounds 2-118 troubleshooting 2-116 troubleshooting 2-117 2-119 System Reboot 2-116 2-118 2-119 synchronization status message.
Index manual switch to third source (condition) switch error 2-89 LOP alarm description PDI alarm 2-119 troubleshooting 2-55 2-26 2-26 SD alarm 2-119 2-27 signal failure alarm 2-1 TPTFAIL (G-Series) alarm description 2-127 failed switch path 1-69 TIM-P alarm TL1 alarms clear a lockout 2-27 User-Initiated Manual Reset 2-88 username/password mismatch 2-120 1-60 TPTFAIL (G-Series) condition troubleshooting 2-120 Trace Identifier Mismatch Path transmission failure transmit levels
Index Flash memory exceeded frame format mismatch idle DS-3 signal 2-44 2-45 2-66 JAR file dowload problem line alarms LOF 1-54 2-124 2-79 loss of signal from BITS low memory 2-81 2-92 memory capacity exceeded 2-91 removing and reinserting the standby card reset 3-3 2-129 switching matrix failure 2-114 terminal loopback alarm 2-87 XTC cards facility loopback test 1-2 1-25 XTC loopback 2-86 Cisco ONS 15327 Troubleshooting Guide, R3.