Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Guide
Reklam
Reklam
Cisco ONS 15454 Troubleshooting Guide
Product and Documentation Release 7.2
Last Updated: September 2010
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA http://www.cisco.com
800 553-NETS (6387)
Text Part Number: 78-17734-01
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.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
• Turn the television or radio antenna until the interference stops.
• Move the equipment to one side or the other of the television or radio.
• Move the equipment farther away from the television or radio.
• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks . Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Cisco ONS 15454 Troubleshooting Guide, Release 7.2
©2006–2011 Cisco Systems Inc. All rights reserved.
November 2009
C O N T E N T S
About this Guide
xxxv
xxxv
xxxvi
xxxvi
xxxvii
xxxvii
Obtaining Optical Networking Information
xliii
Where to Find Safety and Warning Information
xliii
Cisco Optical Networking Product Documentation CD-ROM
xliii
Obtaining Documentation, Obtaining Support, and Security Guidelines
xliv
General Troubleshooting
1-1
1.1 Troubleshooting Circuit Paths with Loopbacks
1-2
1-3
1-3
1.1.1.2 ONS 15454 Card Behavior
1-4
1-5
1-5
1.1.2.2 ONS 15454 Card Behavior
1-6
1-8
1-8
1.2 Troubleshooting Electrical Circuit Paths With Loopbacks
1-9
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
1-10
Create the Facility Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port
1-10
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit
1-11
Create the Facility Loopback on the Source DS3E or DS3XM Port
1-11
Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit
1-12
1-13
1-13
1-14
1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to East)
1-15
Create the Hairpin Circuit on the Source-Node Electrical Port
1-15
Test and Delete the Electrical Port Hairpin Circuit
1-16
Test the Standby Cross-Connect Card
1-16
Cisco ONS 15454 Troubleshooting Guide, R7.2
iii
Contents iv
Retest the Original Cross-Connect Card
1-17
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical
1-18
Create the XC Loopback on a Destination-Node OCN STS
1-19
Test and Clear the XC Loopback Circuit
1-20
Test the Standby Cross-Connect Card
1-20
Retest the Original Cross-Connect Card
1-21
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
1-22
Create the Terminal Loopback on a Destination DS-3, DS3N-12, DS3i-N-12, or EC1 Port
1-23
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal Loopback
1-24
Create the Terminal Loopback on a Destination DS-3E or DS3XM Port
1-25
Test and Clear the DS-3E or DS3XM Destination Port Terminal Loopback Circuit
1-26
Test the Destination Electrical Card
1-27
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
1-27
Create the Facility Loopback on the Destination DS-1, DS-3, DS3N-12, DS3i-N-12, or EC-1
1-28
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC-1 Port Facility Loopback Circuit
1-29
Create the Facility Loopback on the Source DS3E or DS3XM Port
1-29
Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit
1-30
1-30
1-31
1-32
1.2.6 Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)
1-33
Create the Hairpin Circuit on the Destination-Node Port
1-33
Test and Delete the Electrical Hairpin Circuit
1-34
Test the Standby Cross-Connect Card
1-34
Retest the Original Cross-Connect Card
1-35
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West)
Carrying an Electrical Circuit
1-36
Create the XC Loopback on the Source OC-N Port Carrying an Electrical Circuit
1-37
Test and Clear the XC Loopback Circuit
1-38
Test the Standby Cross-Connect Card
1-38
Retest the Original Cross-Connect Card
1-39
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
1-40
Create the Terminal Loopback on a Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port
1-41
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Terminal Loopback
1-42
Create the Terminal Loopback on a Source DS3E or DS3XM Port
1-43
Test and Clear the DS3E or DS3XM Port Terminal Loopback Circuit
1-44
Test the Source Electrical Card
1-45
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks
1-45
1-46
1.3.2 DS-3E and DS3i-N-12 Inhibit Loopback
1-47
1.3.3 DS3XM-6 and DS3XM-12 Inhibit FEAC Loopback
1-47
1-47
1.4 Troubleshooting Optical Circuit Paths With Loopbacks
1-47
1.4.1 Perform a Facility Loopback on a Source-Node Optical Port
1-48
Create the Facility Loopback on the Source Optical Port
1-48
Test and Clear the Facility Loopback Circuit
1-49
1-49
1.4.2 Perform a Terminal Loopback on a Source-Node Optical Port
1-50
Create the Terminal Loopback on a Source-Node Optical Port
1-50
Test and Clear the Terminal Loopback Circuit
1-52
1-52
1.4.3 Perform an XC Loopback on the Source Optical Port
1-53
Create the XC Loopback on the Source-Node Optical Port
1-53
Test and Clear the XC Loopback Circuit
1-54
Test the Standby Cross-Connect Card
1-55
Retest the Original Cross-Connect Card
1-56
1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port
1-57
Create a Facility Loopback on an Intermediate-Node Optical Port
1-57
Test and Clear the Facility Loopback Circuit
1-58
1-59
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
1-59
Create a Terminal Loopback on Intermediate-Node Optical Ports
1-60
Test and Clear the Optical Terminal Loopback Circuit
1-61
1-62
1.4.6 Perform a Facility Loopback on a Destination-Node Optical Port
1-63
Create the Facility Loopback on a Destination-Node Optical Port
1-63
Test and Clear the Optical Facility Loopback Circuit
1-64
1-65
1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port
1-65
Create the Terminal Loopback on a Destination-Node Optical Port
1-66
Test and Clear the Optical Terminal Loopback Circuit
1-67
1-68
1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks
1-68
1.5.1 Perform a Facility Loopback on a Source-Node Ethernet Port
1-69
Create the Facility Loopback on the Source-Node Ethernet Port
1-70
Test and Clear the Facility Loopback Circuit
1-70
1-71
Cisco ONS 15454 Troubleshooting Guide, R7.2
v
Contents vi
1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port
1-71
Create the Terminal Loopback on a Source-Node Ethernet Port
1-72
Test and Clear the Ethernet Terminal Loopback Circuit
1-73
1-74
1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port
1-74
Create a Facility Loopback on an Intermediate-Node Ethernet Port
1-75
Test and Clear the Ethernet Facility Loopback Circuit
1-76
1-77
1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports
1-77
Create a Terminal Loopback on Intermediate-Node Ethernet Ports
1-78
Test and Clear the Ethernet Terminal Loopback Circuit
1-79
1-80
1.5.5 Perform a Facility Loopback on a Destination-Node Ethernet Port
1-80
Create the Facility Loopback on a Destination-Node Ethernet Port
1-81
Test and Clear the Ethernet Facility Loopback Circuit
1-82
1-83
1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port
1-83
Create the Terminal Loopback on a Destination-Node Ethernet Port
1-84
Test and Clear the Ethernet Terminal Loopback Circuit
1-85
1-86
1.6 Troubleshooting FC_MR Circuit Paths With Loopbacks
1-86
1.6.1 Perform a Facility Loopback on a Source-Node FC_MR Port
1-87
Create the Facility Loopback on the Source-Node FC_MR Port
1-88
Test and Clear the FC_MR Facility Loopback Circuit
1-88
1-89
1.6.2 Perform a Terminal Loopback on a Source-Node FC_MR Port
1-89
Create the Terminal Loopback on a Source-Node FC_MR Port
1-90
Test and Clear the FC_MR Port Terminal Loopback Circuit
1-90
1-91
1.6.3 Create a Facility Loopback on an Intermediate-Node FC_MR Port
1-91
Create a Facility Loopback on an Intermediate-Node FC_MR Port
1-92
Test and Clear the FC_MR Port Facility Loopback Circuit
1-92
1-93
1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports
1-93
Create a Terminal Loopback on Intermediate-Node FC_MR Ports
1-94
Test and Clear the FC_MR Terminal Loopback Circuit
1-95
1-95
1.6.5 Perform a Facility Loopback on a Destination-Node FC_MR Port
1-96
Create the Facility Loopback on a Destination-Node FC_MR Port
1-96
Test and Clear the FC_MR Facility Loopback Circuit
1-97
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
1-97
1.6.6 Perform a Terminal Loopback on a Destination-Node FC_MR Port
1-98
Create the Terminal Loopback on a Destination-Node FC_MR Port
1-98
Test and Clear the FC_MR Terminal Loopback Circuit
1-99
1-100
1-100
1-101
Verify General Card LED Operation
1-101
Verify G-Series Ethernet or FC_MR Card Port-Level LED Operation
1-102
Verify E-Series and ML-Series Ethernet Card Port-Level LED Operation
1-102
1.7.2 Retrieve Diagnostics File Button
1-103
1-103
1.7.3 Bidirectional Diagnostic Circuit
1-103
Create a Bidirectional Diagnostic Circuit
1-104
1.7.4 Data Communications Network Tool
1-106
1.8 Restoring the Database and Default Settings
1-107
1.8.1 Restore the Node Database
1-107
1.9 PC Connectivity Troubleshooting
1-108
1.9.1 PC System Minimum Requirements
1-108
1.9.2 Sun System Minimum Requirements
1-108
1.9.3 Supported Platforms, Browsers, and JREs
1-108
1.9.4 Unsupported Platforms and Browsers
1-109
1.9.5 Unable to Verify the IP Configuration of Your PC
1-109
Verify the IP Configuration of Your PC
1-109
1.9.6 Browser Login Does Not Launch Java
1-110
Reconfigure the PC Operating System Java Plug-in Control Panel
1-110
1-111
1.9.7 Unable to Verify the NIC Connection on Your PC
1-111
1.9.8 Verify PC Connection to the ONS 15454 (ping)
1-112
1-112
1.9.9 The IP Address of the Node is Unknown
1-113
Retrieve Unknown Node IP Address
1-113
1.10 CTC Operation Troubleshooting
1-113
1.10.1 CTC Colors Do Not Appear Correctly on a UNIX Workstation
1-114
1-114
1.10.2 Unable to Launch CTC Help After Removing Netscape
1-114
Reset Internet Explorer as the Default Browser for CTC
1-114
1.10.3 Unable to Change Node View to Network View
1-115
Reset the CTC_HEAP Environment Variable for Windows
1-115
Cisco ONS 15454 Troubleshooting Guide, R7.2
vii
Contents viii
Reset the CTC_HEAP Environment Variable for Solaris
1-115
1.10.4 Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P Card
1-116
Disable the VirusScan Download Scan
1-116
1-116
Redirect the Netscape Cache to a Valid Directory
1-117
1.10.6 Slow CTC Operation or Login Problems
1-117
Delete the CTC Cache File Automatically
1-117
Delete the CTC Cache File Manually
1-118
1.10.7 Node Icon is Gray on CTC Network View
1-119
1.10.8 CTC Cannot Launch Due to Applet Security Restrictions
1-119
Manually Edit the java.policy File
1-119
1.10.9 Java Runtime Environment Incompatible
1-120
Launch CTC to Correct the Core Version Build
1-121
1.10.10 Different CTC Releases Do Not Recognize Each Other
1-121
Launch CTC to Correct the Core Version Build
1-121
1.10.11 Username or Password Do Not Match
1-122
Verify Correct Username and Password
1-122
1.10.12 No IP Connectivity Exists Between Nodes
1-122
1-123
1.10.14 “Path in Use” Error When Creating a Circuit
1-123
1.10.15 Calculate and Design IP Subnets
1-123
1-124
1-124
1.10.17 VLAN Cannot Connect to Network Device from Untag Port
1-125
Change VLAN Port Tagged and Untag Settings
1-126
1-127
1.11.1 OC-N Circuit Transitions to Partial State
1-127
View the State of OC-N Circuit Nodes
1-127
1.11.2 AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits
1-128
Clear AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits
1-128
1.11.3 Circuit Creation Error with VT1.5 Circuit
1-129
1.11.4 Unable to Create Circuit From DS-3 Card to DS3XM-6 or DS3XM-12 Card
1-129
1.11.5 DS-3 Card Does Not Report AIS-P From External Equipment
1-129
1.11.6 OC-3 and DCC Limitations
1-130
1.11.7 ONS 15454 Switches Timing Reference
1-130
1.11.8 Holdover Synchronization Alarm
1-130
1.11.9 Free-Running Synchronization Mode
1-131
1.11.10 Daisy-Chained BITS Not Functioning
1-131
1.11.11 Blinking STAT LED after Installing a Card
1-131
1-131
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Contents
November 2009
1.12.1 Bit Errors Appear for a Traffic Card
1-132
1.12.2 Faulty Fiber-Optic Connections
1-132
Verify Fiber-Optic Connections
1-132
1.12.2.1 Crimp Replacement LAN Cables
1-134
1.12.2.2 Replace Faulty GBIC, SFP, or XFP Connectors
1-136
Remove GBIC, SFP, or XFP Connectors
1-137
Install a GBIC or SFP/XFP Device
1-137
1.12.3 OC-N Card Transmit and Receive Levels
1-140
1-142
Isolate the Cause of Power Supply Problems
1-142
1.13.1 Power Consumption for Node and Cards
1-143
Alarm Troubleshooting
2-1
2.1 Alarm Indexes by Default Severity
2-1
2-2
2-3
2-4
2-6
2-10
2.2 Alarms and Conditions Listed By Alphabetical Entry
2-10
2-18
2.4 Alarm List by Logical Object Type
2-21
2-29
2-30
2.5.2 Condition Characteristics
2-30
2-30
2-31
2-33
2-33
2-33
2-34
2-34
2-35
2-35
2-35
2-36
2-36
2-36
2-36
Cisco ONS 15454 Troubleshooting Guide, R7.2
ix
Contents x
2-36
2-36
2-37
2-37
2-37
2-37
2-37
2-37
2-38
2-38
2-39
2-40
2-40
2-40
2-41
2-41
2-41
2-42
2-42
2-42
2-43
2-43
2-43
Clear the APS-PRIM-FAC Condition
2-44
2-44
Clear the APS-PRIM-SEC-MISM Alarm
2-44
2-44
2-44
2-45
2-46
2-46
2-46
Clear the AUD-LOG-LOSS Condition
2-46
2-47
2-47
2-47
2-48
2-48
2-49
2-49
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-49
Clear the AUTOSW-AIS Condition
2-50
2-50
Clear the AUTOSW-LOP (STSMON) Condition
2-50
2-50
Clear the AUTOSW-LOP (VT-MON) Condition
2-51
2-51
Clear the AUTOSW-PDI Condition
2-51
2-51
Clear the AUTOSW-SDBER Condition
2-51
2-52
Clear the AUTOSW-SFBER Condition
2-52
2-52
Clear the AUTOSW-UNEQ (STSMON) Condition
2-52
2-53
Clear the AUTOSW-UNEQ (VT-MON) Condition
2-53
2-53
2-53
2-53
2-53
2-53
2-54
2-54
2-54
2-55
2-55
Clear the BLSR-SW-VER-MISM Alarm
2-55
2-55
2-56
2.7.47 CARLOSS (CE1000, CE100T)
2-56
Clear the CARLOSS (CE100T) Alarm
2-56
2.7.48 CARLOSS (E1000F, E100T)
2-57
Clear the CARLOSS (E1000F, E100T) Alarm
2-57
2-58
Clear the CARLOSS (EQPT) Alarm
2-59
2-60
2-60
Clear the CARLOSS (G1000) Alarm
2-61
2-62
2-63
Cisco ONS 15454 Troubleshooting Guide, R7.2
xi
Contents xii
2.7.54 CARLOSS (ML1000, ML100T, MLFX)
2-63
Clear the CARLOSS (ML1000, ML100T, MLFX) Alarm
2-63
2-64
2-64
2-64
Clear the CLDRESTART Condition
2-64
2-64
2-65
2-65
2-65
2-65
2-66
2-66
2-66
2-66
Clear the CONTBUS-DISABLED Alarm
2-67
2-67
2-68
2-68
2-68
2-69
Clear the CTNEQPT-MISMATCH Condition
2-70
2-70
Clear the CTNEQPT-PBPROT Alarm
2-70
2-71
Clear the CTNEQPT-PBWORK Alarm
2-72
2-73
2-73
2-73
2-73
2-74
2-74
2-74
2-74
2-75
2-75
2-75
2-75
2-75
2-76
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-76
2-76
2-77
2-77
2-77
2-77
2-77
2-77
Clear the ENCAP-MISMATCH-P Alarm
2-78
2-79
2-80
2-81
2-82
2-82
2-83
2-83
2-83
2-83
2-84
2-84
Clear the ERFI-P-CONN Condition
2-84
2-84
Clear the ERFI-P-PAYLD Condition
2-85
2-85
Clear the ERFI-P-SRVR Condition
2-85
2-85
2-86
2-86
Clear the ETH-LINKLOSS Condition
2-87
2-87
Clear the E-W-MISMATCH Alarm with a Physical Switch
2-87
Clear the E-W-MISMATCH Alarm in CTC
2-88
2-89
2-89
2-89
Clear the EXERCISE-RING-FAIL Condition
2-90
2-90
Clear the EXERCISE-SPAN-FAIL Condition
2-90
2-90
2-91
Cisco ONS 15454 Troubleshooting Guide, R7.2
xiii
Contents xiv
2-91
Clear the EXTRA-TRAF-PREEMPT Alarm
2-91
2-91
2-92
2-92
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
2-92
2-93
Clear the FAILTOSWR Condition in a BLSR Configuration
2-93
2-95
2-95
2-96
2-96
2-97
2-97
2-98
2-98
2-98
2-98
2-99
Clear the FE-DS1-MULTLOS Condition
2-99
2-99
Clear the FE-DS1-NSA Condition
2-99
2-100
2-100
2-100
Clear the FE-DS1-SNGLLOS Condition
2-100
2-100
Clear the FE-DS3-NSA Condition
2-101
2-101
2-101
2-101
Clear the FE-EQPT-NSA Condition
2-102
2-102
Clear the FE-FRCDWKSWBK-SPAN Condition
2-102
2-102
Clear the FE-FRCDWKSWPR-RING Condition
2-103
2-103
Clear the FE-FRCDWKSWPR-SPAN Condition
2-103
2-103
2-104
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-104
Clear the FE-LOCKOUTOFPR-SPAN Condition
2-104
2-104
2-105
2-105
2-105
2-105
Clear the FE-MANWKSWBK-SPAN Condition
2-106
2-106
Clear the FE-MANWKSWPR-RING Condition
2-106
2-106
Clear the FE-MANWKSWPR-SPAN Condition
2-107
2-107
Clear the FEPRLF Alarm on a Four-Fiber BLSR
2-107
2-107
2-107
Clear the FORCED-REQ Condition
2-108
2-108
Clear the FORCED-REQ-RING Condition
2-108
2-109
Clear the FORCED-REQ-SPAN Condition
2-109
2-109
2-109
2-110
2-110
2-110
2-110
2-111
2-111
Clear the FULLPASSTHR-BI Condition
2-111
2-111
2-111
2-111
2-112
2-112
2-112
2-112
2-112
2-112
Clear the GFP-DE-MISMATCH Alarm
2-113
Cisco ONS 15454 Troubleshooting Guide, R7.2
xv
Contents xvi
2-113
Clear the GFP-EX-MISMATCH Alarm
2-114
2-114
2-114
2-114
Clear the GFP-NO-BUFFERS Alarm
2-115
2-115
Clear the GFP-UP-MISMATCH Alarm
2-115
2-116
2-116
2-116
2-116
2-117
2-117
2-117
2-117
2-118
2-118
2-118
2-119
2-120
2-120
2-120
2-121
2-121
Clear the HLDOVRSYNC Condition
2-121
2-122
2-122
2.7.157 INCOMPATIBLE-SEND-PDIP
2-122
Clear the INCOMPATIBLE-SEND-PDIP Alarm
2-122
2-123
Clear the INCOMPATIBLE-SW Alarm
2-123
2-123
2-124
2-125
2-125
2-125
2-125
2-125
2-126
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
Clear the INTRUSION-PSWD Condition
2-126
2-126
2-127
2-128
2-128
2-129
2-130
Clear the KB-PASSTHR Condition
2-130
2.7.168 KBYTE-APS-CHANNEL-FAILURE
2-130
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
2-131
2-131
Clear the LAN-POL-REV Condition
2-131
2-131
2-132
2-132
2-132
2-132
2-132
2-132
2-133
2-133
Clear the LCAS-RX-FAIL Condition
2-134
2-134
2-134
2-135
Clear the LINK-KEEPALIVE Alarm
2-135
2-136
2-136
2-136
2-137
2-137
2-138
2-138
2-139
2-140
2-140
2-140
2-141
Clear the LOCKOUT-REQ Condition
2-141
2-141
Cisco ONS 15454 Troubleshooting Guide, R7.2
xvii
Contents xviii
2-141
2-142
2-142
2-143
2-143
2-143
2-144
2-144
2-145
2-145
2-145
2-146
2-146
2-146
2-146
2-146
2-147
2-147
2-147
2-147
2-148
2-148
2-148
2-149
2-149
2-149
2-150
2-150
2-150
2-151
2-151
2-151
2-152
2-152
2-153
2-154
2-155
2-155
2-156
2-156
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-157
2-157
2-157
2-158
2-158
2-158
2-159
2-160
2-160
2-160
2-160
2-160
2-160
2-160
2-161
2-161
2-161
2-162
2-162
Clear the LPBKDS3FEAC Condition
2-162
2-162
2.7.225 LPBKFACILITY (CE1000, CE100T)
2-163
Clear the LPBKFACILITY (CE1000, CE100T) Condition
2-163
2.7.226 LPBKFACILITY (DS1, DS3)
2-163
Clear the LPBKFACILITY (DS1, DS3) Condition
2-164
2-164
Clear the LPBKFACILITY (E1) Condition
2-164
2-165
Clear the LPBKFACILITY (EC1) Condition
2-165
2-165
2-165
2-165
Clear the LPBKFACILITY (FCMR) Condition
2-166
2-166
Clear the LPBKFACILITY (G1000) Condition
2-166
2-166
2-166
2-167
Clear the LPBKFACILITY (OCN) Condition
2-167
2-167
Cisco ONS 15454 Troubleshooting Guide, R7.2
xix
Contents xx
2.7.237 LPBKTERMINAL (CE1000, CE100T)
2-167
Clear the LPBKTERMINAL (CE1000, CE100T) Condition
2-168
2.7.238 LPBKTERMINAL (DS1, DS3)
2-168
Clear the LPBKTERMINAL (DS1, DS3) Condition
2-168
2-168
Clear the LPBKTERMINAL (E1) Condition
2-169
2-169
Clear the LPBKTERMINAL (EC1) Condition
2-169
2-169
2-169
2-170
Clear the LPBKTERMINAL (FCMR) Condition
2-170
2-170
Clear the LPBKTERMINAL (G1000) Condition
2-170
2-171
2-171
2-171
Clear the LPBKTERMINAL (OCN) Condition
2-171
2-171
2-171
2-172
2-172
2-172
2-173
2-173
2-173
2-173
2-174
2-174
Clear the MANUAL-REQ-RING Condition
2-174
2-174
Clear the MANUAL-REQ-SPAN Condition
2-174
2-175
2-175
2-175
2-175
2-176
2-176
2-177
2-177
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-179
2-179
2-180
2-180
2-180
2-180
2-181
2-181
2-181
2-182
2-182
2-182
2-182
2-183
2-183
2-183
2-183
2-183
2-183
2-183
2-183
2-184
2-184
2-184
2-184
2-184
2-184
2-185
2-185
2-185
2-185
2-185
2-185
2-185
2-185
2-186
2-186
2-186
2-186
2-186
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxi
Contents xxii
2-186
2-186
2-186
2-187
2-188
Clear the PEER-NORESPONSE Alarm
2-188
2-189
2-189
2-190
2-190
2-190
2-190
2-190
2.7.306 PORT-ADD-PWR-FAIL-HIGH
2-191
2-191
2-191
2-191
2-191
2-192
2-192
2-192
2-193
2-193
2-193
2-193
2-194
2-194
2-195
2-195
Clear the PWR-FAIL-RET-A Alarm
2-195
2-195
Clear the PWR-FAIL-RET-A Alarm
2-196
2-196
2-196
2-196
2-197
2.7.320 RESERVED-RATE-EXCEEDED-RINGLET0
2-197
Clear the RESERVED-RATE-EXCEEDED-RINGLET0 Alarm
2-197
2.7.321 RESERVED-RATE-EXCEEDED-RINGLET1
2-198
Clear the RESERVED-RATE-EXCEEDED-RINGLET1 Alarm
2-198
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-198
2-198
2-198
2-199
2-199
2-199
2-200
2-200
2-201
2-201
2-201
2-201
2-202
2-202
2-202
2-203
Clear the RPR-PASSTHR Condition
2-203
2-204
Clear the RPR-PEER-MISS Condition
2-204
2-205
Clear the RPR-PROT-ACTIVE Condition
2-205
2.7.335 RPR-PROT-CONFIG-MISMATCH
2-206
Clear the RPR-PROT-CONFIG-MISMATCH Alarm
2-206
2-206
Clear the RPR-RI-FAIL Condition
2-206
2-207
2-207
2-207
2-208
2-208
Clear the RPR-SPAN-MISMATCH Alarm
2-209
2-209
2-209
2-210
2-210
Clear the SD (DS1, DS3) Condition
2-211
2-212
2-213
2-213
2-213
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxiii
Contents xxiv
2-214
2-214
2-214
2-214
2-215
2-215
2-215
Clear the SF (DS1, DS3) Condition
2-216
2-216
2-216
2-217
2-217
2-217
2-217
2-217
2-217
2-218
2-218
2-218
2-218
2.7.358 SH-INS-LOSS-VAR-DEG-HIGH
2-219
2.7.359 SH-INS-LOSS-VAR-DEG-LOW
2-219
2-219
2-219
2-219
2-219
2-220
2.7.363 SPANLENGTH-OUT-OF-RANGE
2-220
2-220
2-221
2-221
2-221
2-222
2-224
2-224
2-225
2-225
2-225
2-226
2-226
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-226
2-226
2-226
2-227
2-227
2-227
2-227
2-227
2-228
2-228
2-228
2-229
2-229
2-229
2-229
2-230
2-230
Clear the SW-MISMATCH Condition
2-230
2-230
2-231
2-231
2-231
2-232
2-232
2-232
2-232
2-232
2-233
2-233
2-233
2-234
2-234
2-234
2-235
2-235
2-235
2-235
2-236
2-236
2-237
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxv
Contents xxvi
2-237
2-237
2-238
2-238
2-238
2-239
2-239
2-239
2-240
2-240
2.7.404 TPTFAIL (CE100T, CE1000)
2-240
Clear the TPTFAIL (CE100T, CE1000) Alarm
2-240
2-240
Clear the TPTFAIL (FCMR) Alarm
2-241
2-241
Clear the TPTFAIL (G1000) Alarm
2-241
2.7.407 TPTFAIL (ML100T, ML1000, MLFX)
2-242
Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm
2-242
2-243
2-243
2-243
2-243
2-244
2-244
2-244
2-244
2-244
2-245
2-245
2-245
2-245
2-247
2-247
2.7.416 UNREACHABLE-TARGET-POWER
2-248
2-248
2-248
2-248
2-248
2-249
2-249
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
Contents
2-249
2-249
2-249
2-250
2-250
2-250
2-250
2-250
2-251
2-251
Clear the WTR Condition on an IEEE 802.17b-Based RPR Span
2-251
2-252
2-252
2.8.1 Typical Traffic Card LED Activity After Insertion
2-252
2.8.2 Typical Traffic Card LED Activity During Reset
2-252
2.8.3 Typical Card LED State After Successful Reset
2-252
2.8.4 Typical Cross-Connect LED Activity During Side Switch
2-253
2.9 Frequently Used Alarm Troubleshooting Procedures
2-253
2.9.1 Node and Ring Identification, Change, Visibility, and Termination
2-253
Identify a BLSR Ring Name or Node ID Number
2-253
2-253
2-254
Verify Node Visibility for Other Nodes
2-254
2.9.2 Protection Switching, Lock Initiation, and Clearing
2-254
Initiate a 1+1 Force Switch Command
2-254
Initiate a 1+1 Manual Switch Command
2-255
Clear a 1+1 Force or Manual Switch Command
2-256
2-256
Initiate a Card or Port Lockout Command
2-257
Clear a Lock-On or Lockout Command
2-257
Initiate a 1:1 Card Switch Command
2-257
Initiate a Force Switch for All Circuits on a Path Protection Span
2-258
Initiate a Manual Switch for All Circuits on a Path Protection Span
2-258
Initiate a Lockout for All Circuits on a Protect Path Protection Span
2-259
Clear an External Switching Command on a Path Protection Span
2-259
Initiate a Force Ring Switch on a BLSR
2-260
Initiate a Force Span Switch on a Four-Fiber BLSR
2-260
Initiate a Manual Span Switch on a BLSR
2-260
Initiate a Manual Ring Switch on a BLSR
2-261
Initiate a Lockout on a BLSR Protect Span
2-261
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxvii
Contents
Initiate an Exercise Ring Switch on a BLSR
2-261
Initiate an Exercise Ring Switch on a Four Fiber BLSR
2-262
Clear a BLSR External Switching Command
2-262
2.9.3 CTC Card Resetting and Switching
2-262
2-263
Reset an Active TCC2/TCC2P Card and Activate the Standby Card
2-263
Side Switch the Active and Standby Cross-Connect Cards
2-264
2.9.4 Physical Card Reseating, Resetting, and Replacement
2-264
Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card
2-265
Remove and Reinsert (Reseat) Any Card
2-266
Physically Replace a Traffic Card
2-266
Physically Replace an In-Service Cross-Connect Card
2-266
2.9.5 Generic Signal and Circuit Procedures
2-267
Verify the Signal BER Threshold Level
2-267
2-268
Verify or Create Node Section DCC Terminations
2-268
Clear an OC-N Card Facility or Terminal Loopback Circuit
2-268
Clear an OC-N Card Cross-Connect (XC) Loopback Circuit
2-269
Clear a DS3XM-6, DS3XM-12, or DS3E-12 Card Loopback Circuit
2-269
Clear Other Electrical Card or Ethernet Card Loopbacks
2-270
Clear an MXP, TXP, or FC_MR-4 Card Loopback Circuit
2-270
2.9.6 Air Filter and Fan Procedures
2-271
Inspect, Clean, and Replace the Reusable Air Filter
2-271
Remove and Reinsert a Fan-Tray Assembly
2-272
2-273
2-274
Replace the Electrical Interface Assembly
2-274
Replace the Alarm Interface Panel
2-274
Transient Conditions
3-1
3.1 Transients Indexed By Alphabetical Entry
3-1
3-3
3.2.1 Condition Characteristics
3-3
3-3
3-4
3-4
3-4
3-4
3-4 xxviii
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Contents
3-4
3-4
3-5
3-5
3-5
3-5
3-5
3-5
3-6
3-6
3-6
3-6
3-6
3-6
3-6
3-7
3-7
3-7
3-7
3-7
3-7
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-9
3-9
3-9
3-9
3-9
3-9
3-10
Error Messages
4-1
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxix
Contents xxx
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Figure 1-17
Figure 1-18
Figure 1-19
Figure 1-20
Figure 1-21
Figure 1-22
Figure 1-23
Figure 1-24
Figure 1-25
Figure 1-26
Figure 1-27
Figure 1-28
Figure 1-29
Figure 1-30
Figure 1-31
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 1-5
Figure 1-6
Figure 1-7
Figure 1-8
Figure 1-9
Figure 1-10
Figure 1-11
Figure 1-12
Figure 1-13
Figure 1-14
Figure 1-15
Figure 1-16
November 2009
F I G U R E S
Facility Loopback Path on a Near-End DS-N Card 1-3
Facility Loopback Path on a Near-End OC-N Card 1-3
OC-N Facility Loopback Indicator 1-3
Terminal Loopback Path on an OC-N Card 1-5
Terminal Loopback Indicator 1-5
Terminal Loopback Path on a DS-N Card 1-6
Terminal Loopback on a DS-N Card with a Bridged Signal 1-7
Terminal Loopback on an OC-N Card with a Bridged Signal 1-7
Hairpin Circuit Path on a DS-N Card 1-8
Network Element with SONET Cross-Connect Loopback Function 1-9
Facility Loopback on a Circuit Source DS-N Port 1-10
Hairpin on a Source-Node Port 1-15
XC Loopback on a Destination OC-N Port 1-19
Terminal Loopback to a Destination DS-N Port 1-22
Facility Loopback on a Circuit Destination DS-N Port 1-28
Hairpin on a Destination-Node DS-N Port 1-33
XC Loopback on a Source OC-N Port 1-37
Terminal Loopback on a Source DS-N Port 1-40
Accessing FEAC Functions on the DS3XM-6 Card 1-46
Diagram of FEAC Circuit 1-46
Facility Loopback on a Circuit Source OC-N Port 1-48
Terminal Loopback on a Source-Node OC-N Port 1-50
Terminal Loopback Indicator 1-50
XC Loopback on a Source OC-N Port 1-53
Facility Loopback Path to an Intermediate-Node OC-N Port 1-57
Terminal Loopback Path to an Intermediate-Node OC-N Port 1-60
Facility Loopback Indicator 1-60
Facility Loopback Path to a Destination-Node OC-N Port 1-63
Terminal Loopback Path to a Destination-Node OC-N Port 1-66
Facility Loopback on a Circuit Source Ethernet Port 1-69
Terminal Loopback on a G-Series Port 1-72
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxxi
Figures
Figure 1-32
Figure 1-33
Figure 1-34
Figure 1-35
Figure 1-36
Figure 1-37
Figure 1-38
Figure 1-39
Figure 1-40
Figure 1-41
Figure 1-42
Figure 1-43
Figure 1-44
Figure 1-45
Figure 1-46
Figure 1-47
Figure 1-48
Figure 1-49
Figure 1-50
Figure 1-51
Figure 1-52
Figure 1-53
Figure 2-1
Figure 2-2
Figure 4-1
Hairpin on a Source-Node Ethernet Port 1-75
Facility Loopback on an Intermediate-Node Ethernet Port 1-78
Terminal Loopback on an Intermediate-Node Ethernet Port 1-81
Facility Loopback on a Destination-Node Ethernet Port 1-84
Terminal Loopback on a Destination-Node Ethernet Port 1-87
Hairpin on a Destination-Node Ethernet Port 1-89
Facility Loopback on a Circuit Source FC_MR Port 1-91
Terminal Loopback on a Source-Node FC_MR Port 1-94
Facility Loopback on an Intermediate-Node FC_MR Port 1-96
Terminal Loopback on an Intermediate-Node FC_MR Port 1-98
CTC Node View Diagnostic Window 1-101
CTC Node View Diagnostic Window 1-104
Network View Circuit Creation Dialog Box 1-105
DCN Tools OSPF Dump 1-107
Deleting the CTC Cache 1-118
Ethernet Connectivity Reference 1-124
VLAN with Ethernet Ports at Tagged and Untag 1-126
Configuring VLAN Membership for Individual Ethernet Ports 1-126
RJ-45 Pin Numbers 1-134
LAN Cable Layout 1-135
Cross-Over Cable Layout 1-135
GBICs 1-136
Shelf LCD Panel 2-48
Shelf LCD Panel 2-120
Error Dialog Box 4-1 xxxii
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
T A B L E S
Table 2-9
Table 2-10
Table 2-11
Table 2-12
Table 2-13
Table 2-14
Table 2-15
Table 2-16
Table 2-17
Table 2-18
Table 3-1
Table 4-1
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 1-1
Table 1-2
Table 1-3
Table 1-4
Table 1-5
Table 1-6
Table 1-7
Table 1-8
ONS 15454 Card Facility Loopback Behavior 1-4
ONS 15454 Card Terminal Loopback Behavior 1-6
JRE Compatibility 1-120
LAN Cable Pinout 1-135
Cross-Over Cable Pinout 1-135
Available GBICs 1-138
Available SFPs and XFPs 1-138
Optical Card Transmit and Receive Levels 1-141
ONS 15454 Critical Alarm List 2-2
ONS 15454 Major Alarm List 2-3
ONS 15454 Minor Alarm List 2-4
ONS 15454 NA Conditions List 2-6
ONS 15454 NR Conditions List 2-10
ONS 15454 Alarm and Condition Alphabetical List 2-10
Alarm Logical Object Type Definitions 2-18
Alarm List by Logical Object in Alarm Profile 2-21
Path Alarm Hierarchy 2-31
Facility Alarm Hierarchy 2-31
Near-End Alarm Hierarchy 2-32
Far-End Alarm Hierarchy 2-32
Transponder Trunk Alarms that Cause LMP-SD 2-138
Transponder Client Alarm that Causes LMP-SD 2-138
Transponder Card Alarms that Cause LMP-SF 2-139
Transponder Trunk Alarms that Cause LMP-SF 2-139
Transponder Client Alarms that Cause LMP-SF 2-139
BIC Compatibility Matrix 2-176
ONS 15454 Transient Condition Alphabetical Index 3-1
Error Messages 4-2
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxxiii
Tables xxxiv
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
About this Guide
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration.
Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This section explains the objectives, intended audience, and organization of this publication and describes the conventions that convey instructions and other information.
This section provides the following information:
•
•
•
•
•
•
•
Obtaining Optical Networking Information
Obtaining Documentation, Obtaining Support, and Security Guidelines
Revision History
Date
March 2007
April 2007
Notes
Revision History Table added for the first time
Added CE-Series Ethernet card information to Tables 1-1 and 1-2 in the “General
Troubleshooting” chapter.
Changed description for LOA and VCG-DOWN alarms, and description and alarm-clearing procedure for LOM alarm in the “Alarm Troubleshooting” chapter.
Added additional description for APSCM alarm in the “Alarm Troubleshooting” chapter.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxxv
About this Guide
Date
August 2007
Notes
Replaced TX Power High column name with OPT-HIGH in the HI-TX Power section of the “Alarm Troubleshooting” chapter. Added Ethernet ports to which the GFP-LFD alarm applies to, in the GFP-LFD section of the “Alarm
Troubleshooting” chapter. Changed the alarm severity of RPR-PEER-MISS and
RPR-RI-FAIL alarms from Not Alarmed (NA) to Major (MJ). Added the
ROUTE-OVERFLOW alarm to the “Alarm Troubleshooting” chapter.
September 2007 Updated the caution in the Side Switch the Active and Standby Cross-Connect
Cards section of the “Alarm Troubleshooting” chapter. Added a note, caution, and rule in the Side Switch the Active and Standby Cross-Connect Cards section of the “Alarm Troublesooting” chapter.
June 2008 Updated FAILTOSW alarm in Chapter 2, Alarm Troubleshooting.
February 2009
June 2009
Updated PORT-MISMATCH alarm details in Chapter 2, Alarm Troubleshooting.
Updated PWR-FAIL-A, PWR-FAIL-B, PWR-FAIL-RET-A, and
PWR-FAIL-RET-B alarm details in Chapter 2, Alarm Troubleshooting.
July 2009
August 2009
November 2009
Updated the COMIOXC alarm details in Chapter 2, Alarm Troubleshooting.
Updated MEM-GONE alarm description in Chapter 2, Alarm Troubleshooting.
• Updated the card details for LCAS alarms in Chapter 2, Alarm
Troubleshooting.
June 2010
July 2010
September 2010
• Added a caution in “Perform a Terminal Loopback on a Destination Electrical
Port (West to East)” and “Perform a Terminal Loopback on a Source-Node
Electrical Port (East to West)” sections in the chapter, “General
Troubleshooting”.
• Added a note in “TX-RAI” section in the chapter, “Alarm Troubleshooting”.
Updated the table “Alarm Logical Object Type Definitions” in the chapter “Alarm
Troubleshooting”.
Updated table in Chapter Error Messages.
Updated the “Clear the COMIOXC Alarm” procedure in the chapter, “Alarm
Troubleshooting”.
Document Objectives
This guide gives general troubleshooting instructions, alarm troubleshooting instructions, equipment replacement instructions, and a list of error messages that apply to the ONS 15454. This information is contained in four chapters. Use this guide in conjunction with the appropriate publications listed in the
Related Documentation section.
Audience
To use this publication, you should be familiar with Cisco or equivalent optical transmission hardware and cabling, telecommunications hardware and cabling, electronic circuitry and wiring practices, and preferably have experience as a telecomunications technician.
xxxvi
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
About this Guide
Related Documentation
Use the Cisco ONS 15454 Troubleshooting Guide in conjunction with the following publications:
• Cisco ONS 15454 Procedure Guide
Provides procedures to install, turn up, test, and maintain an ONS 15454 node and network.
•
•
Cisco ONS 15454 Reference Manual
Provides card, node, and network-level reference information, including specifications and network element defaults.
Cisco ONS 15454 DWDM Procedure Guide
Provides procedures to install, turn-up, test, and maintain an ONS 15454 ANSI (SONET) or ETSI
(SDH) shelf in a DWDM network.
•
•
•
Cisco ONS 15454 DWDM Reference Manual
Provides card, node, and network-level reference information for ONS 15454 DWDM configurations.
Cisco ONS SONET TL1 Command Guide
Provides a full TL1 command and autonomous message set including parameters, AIDs, conditions and modifiers for the Cisco ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and
ONS 15310-MA systems.
Cisco ONS SONET TL1 Reference Guide
Provides general information, procedures, and errors for TL1 in the Cisco ONS 15454, ONS 15327,
ONS 15600, ONS 15310-CL, and ONS 15310-MA systems.
•
•
Ethernet Card Software Feature and Configuration G uide for the Cisco ONS 15454, Cisco ONS
15454 SDH, and Cisco ONS 15327
Provides software features for all Ethernet cards and configuration information for Cisco IOS on
ML-Series cards.
Release Notes for the Cisco ONS 15454 Release 7.2
Provides caveats, closed issues, and new feature and functionality information.
Refer to the following standards documentation referenced in this publication:
• Telcordia GR-253 CORE
For an update on End-of-Life and End-of-Sale notices, refer to http://cisco.com/en/US/products/hw/optical/ps2006/prod_eol_notices_list.html
.
Document Conventions
This publication uses the following conventions:
Convention boldface italic
[ ]
Application
Commands and keywords in body text.
Command input that is supplied by the user.
Keywords or arguments that appear within square brackets are optional.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxxvii
About this Guide
Convention
{ x | x | x }
Ctrl screen font boldface screen font
< >
Application
A choice of keywords (represented by x) appears in braces separated by vertical bars. The user must select one.
The control key. For example, where Ctrl + D is written, hold down the
Control key while pressing the D key.
Examples of information displayed on the screen.
Examples of information that the user must enter.
Command parameters that must be replaced by module-specific codes.
Note Means reader take note . Notes contain helpful suggestions or references to material not covered in the document.
Caution Means reader be careful . In this situation, the user might do something that could result in equipment damage or loss of data.
Warning IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071
SAVE THESE INSTRUCTIONS
Waarschuwing BELANGRIJKE VEILIGHEIDSINSTRUCTIES
Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van de standaard praktijken om ongelukken te voorkomen. Gebruik het nummer van de verklaring onderaan de waarschuwing als u een vertaling van de waarschuwing die bij het apparaat wordt geleverd, wilt raadplegen.
BEWAAR DEZE INSTRUCTIES xxxviii
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
About this Guide
Varoitus
Attention
Warnung
Avvertenza
Advarsel
TÄRKEITÄ TURVALLISUUSOHJEITA
Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa ruumiillisia vammoja. Ennen kuin käsittelet laitteistoa, huomioi sähköpiirien käsittelemiseen liittyvät riskit ja tutustu onnettomuuksien yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät laitteen mukana toimitettujen käännettyjen turvallisuusvaroitusten joukosta varoitusten lopussa näkyvien lausuntonumeroiden avulla.
SÄILYTÄ NÄMÄ OHJEET
IMPORTANTES INFORMATIONS DE SÉCURITÉ
Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant entraîner des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers liés aux circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions des avertissements figurant dans les consignes de sécurité traduites qui accompagnent cet appareil, référez-vous au numéro de l'instruction situé à la fin de chaque avertissement.
CONSERVEZ CES INFORMATIONS
WICHTIGE SICHERHEITSHINWEISE
Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am Ende jeder
Warnung angegebenen Anweisungsnummer nach der jeweiligen Übersetzung in den übersetzten
Sicherheitshinweisen, die zusammen mit diesem Gerät ausgeliefert wurden.
BEWAHREN SIE DIESE HINWEISE GUT AUF.
IMPORTANTI ISTRUZIONI SULLA SICUREZZA
Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti.
Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento.
CONSERVARE QUESTE ISTRUZIONI
VIKTIGE SIKKERHETSINSTRUKSJONER
Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til skade på person. Før du begynner å arbeide med noe av utstyret, må du være oppmerksom på farene forbundet med elektriske kretser, og kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret i slutten av hver advarsel for å finne oversettelsen i de oversatte sikkerhetsadvarslene som fulgte med denne enheten.
TA VARE PÅ DISSE INSTRUKSJONENE
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xxxix
About this Guide
Aviso
¡Advertencia!
Varning!
INSTRUÇÕES IMPORTANTES DE SEGURANÇA
Este símbolo de aviso significa perigo. Você está em uma situação que poderá ser causadora de lesões corporais. Antes de iniciar a utilização de qualquer equipamento, tenha conhecimento dos perigos envolvidos no manuseio de circuitos elétricos e familiarize-se com as práticas habituais de prevenção de acidentes. Utilize o número da instrução fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham este dispositivo.
GUARDE ESTAS INSTRUÇÕES
INSTRUCCIONES IMPORTANTES DE SEGURIDAD
Este símbolo de aviso indica peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considere los riesgos de la corriente eléctrica y familiarícese con los procedimientos estándar de prevención de accidentes. Al final de cada advertencia encontrará el número que le ayudará a encontrar el texto traducido en el apartado de traducciones que acompaña a este dispositivo.
GUARDE ESTAS INSTRUCCIONES
VIKTIGA SÄKERHETSANVISNINGAR
Denna varningssignal signalerar fara. Du befinner dig i en situation som kan leda till personskada.
Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna anordning.
SPARA DESSA ANVISNINGAR xl
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
About this Guide
Aviso
Advarsel
INSTRUÇÕES IMPORTANTES DE SEGURANÇA
Este símbolo de aviso significa perigo. Você se encontra em uma situação em que há risco de lesões corporais. Antes de trabalhar com qualquer equipamento, esteja ciente dos riscos que envolvem os circuitos elétricos e familiarize-se com as práticas padrão de prevenção de acidentes. Use o número da declaração fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham o dispositivo.
GUARDE ESTAS INSTRUÇÕES
VIGTIGE SIKKERHEDSANVISNINGER
Dette advarselssymbol betyder fare. Du befinder dig i en situation med risiko for legemesbeskadigelse. Før du begynder arbejde på udstyr, skal du være opmærksom på de involverede risici, der er ved elektriske kredsløb, og du skal sætte dig ind i standardprocedurer til undgåelse af ulykker. Brug erklæringsnummeret efter hver advarsel for at finde oversættelsen i de oversatte advarsler, der fulgte med denne enhed.
GEM DISSE ANVISNINGER
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xli
About this Guide xlii
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
About this Guide
Obtaining Optical Networking Information
This section contains information that is specific to optical networking products. For information that
pertains to all of Cisco, refer to the Obtaining Documentation, Obtaining Support, and Security
Where to Find Safety and Warning Information
For safety and warning information, refer to the Cisco Optical Transport Products Safety and
Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.
Cisco Optical Networking Product Documentation CD-ROM
Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product
Documentation CD-ROM is updated periodically and may be more current than printed documentation.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
xliii
About this Guide
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
xliv
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
C H A P T E R
1
General Troubleshooting
November 2009
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration.
Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This chapter provides procedures for troubleshooting the most common problems encountered when
operating a Cisco ONS 15454. To troubleshoot specific ONS 15454 alarms, see Chapter 2, “Alarm
If you cannot find what you are looking for, contact the Cisco Technical Assistance
Center (TAC) at 1 800 553-2447 .
For an update on End-of-Life and End-of-Sale notices, refer to http://cisco.com/en/US/products/hw/optical/ps2006/prod_eol_notices_list.html.
This chapter includes the following sections on network problems:
•
1.1 Troubleshooting Circuit Paths with Loopbacks, page 1-2
—Describes loopbacks and hairpin circuits, which you can use to test circuit paths through the network or logically isolate faults.
Note For dense wavelength division multiplexing (DWDM) network acceptance tests, refer to the
Cisco ONS 15454 DWDM Procedure Guide .
•
•
•
•
•
1.2 Troubleshooting Electrical Circuit Paths With Loopbacks, page 1-9 —Explains how to use
loopback tests described in “1.1 Troubleshooting Circuit Paths with Loopbacks”
to isolate trouble on DS-1, DS-3, or EC-1 electrical circuits.
1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks, page
1-45 —Describes how DS3XM-6 and DS3XM-12 card far-end alarm and control (FEAC) functions.
1.4 Troubleshooting Optical Circuit Paths With Loopbacks, page 1-47
—Explains how to use
loopback tests described in “1.1 Troubleshooting Circuit Paths with Loopbacks”
to isolate trouble on OC-N optical circuits.
1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks, page 1-68
—Explains how to use
loopback tests described in “1.1 Troubleshooting Circuit Paths with Loopbacks”
to isolate trouble on G-Series or CE-Series Ethernet circuits.
1.6 Troubleshooting FC_MR Circuit Paths With Loopbacks, page 1-86 —Explains how to use
loopbacks tests described in “1.1 Troubleshooting Circuit Paths with Loopbacks”
to isolate trouble on Fibre Channel (FC_MR) circuits.
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-1
Chapter 1 General Troubleshooting
1.1 Troubleshooting Circuit Paths with Loopbacks
The remaining sections describe symptoms, problems, and solutions that are categorized according to the following topics:
•
•
1.7 Using CTC Diagnostics, page 1-100 —Explains how to perform card LED tests, download a
diagnostic file for Cisco Technical Support, and create a bidirectional diagnostic VT circuit.
1.8 Restoring the Database and Default Settings, page 1-107
—Provides procedures for restoring software data and restoring the node to the default setup.
•
•
•
•
•
1.9 PC Connectivity Troubleshooting, page 1-108
—Provides troubleshooting procedures for PC and network connectivity to the ONS 15454.
1.10 CTC Operation Troubleshooting, page 1-113 —Provides troubleshooting procedures for
Cisco Transport Controller (CTC) login or operation problems.
1.11 Circuits and Timing, page 1-127 —Provides troubleshooting procedures for circuit creation
and error reporting as well as timing reference errors and alarms.
1.12 Fiber and Cabling, page 1-131
—Provides troubleshooting procedures for fiber and cabling connectivity errors.
1.13 Power Supply Problems, page 1-142
—Provides troubleshooting procedures for power supply problems.
1.1 Troubleshooting Circuit Paths with Loopbacks
Use loopbacks and hairpin circuits to test newly created SONET circuits before running live traffic or to logically locate the source of a network failure. All ONS 15454 electrical cards, OC-N cards, G-Series
Ethernet cards, and FC_MR-4 cards allow loopbacks and hairpin test circuits. Other cards do not allow loopbacks, including E-Series Ethernet, ML-Series Ethernet, and DWDM cards such as Optical Booster
(OPT-BST), Optical Preamplifier (OPT-PRE), Optical Service Channel and Combiner/Splitter Module
(OSC-CSM), Band Optical Add/Drop Multiplexing (AD-xB-xx.x), and Channel Optical Add/Drop
Multiplexing (AD-xC-xx.x) cards. For transponder (TXP) or muxponder (MXP) loopback information, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide .
To create a loopback on a port, the port must be in the Out-of-Service and Management, Maintenance
(OOS-MA,MT) service state. After you create the loopback, the service state becomes Out-of-Service and Management, Loopback and Maintenance (OOS-MA,LPBK & MT).
Caution Facility or terminal loopbacks can be service-affecting. To protect traffic, apply a lockout or Force switch to the target loopback port. Basic directions for these procedures are in
For more information about these operations, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Note Do not use a physical loopback to verify circuit switching time or to determine whether a situation causes a traffic hit. Testing in this manner can cause a hit that exceeds 60 m/sec. To test switching times, place a test set at both physical ends of the circuit.
Caution On all 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.
1-2
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.1.1 Facility Loopbacks
1.1.1 Facility Loopbacks
The following sections give general information about facility loopback operations and specific information about ONS 15454 card loopback activity.
1.1.1.1 General Behavior
A facility loopback tests the line interface unit (LIU) of a card, the electrical interface assembly (EIA), and related cabling. After applying a facility loopback on a port, use a test set to run traffic over the loopback. A successful facility loopback isolates the LIU, the EIA, or the cabling plant as the potential cause of a network problem.
shows a facility loopback on a DS-N electrical card.
Figure 1-1 Facility Loopback Path on a Near-End DS-N Card
DS-N XC OC-N
Test Set
To test an OC-N card LIU, connect an optical test set to the OC-N port and perform a facility loopback.
Alternately, use a loopback or hairpin circuit on a card that is farther along the circuit path.
shows a facility loopback on an OC-N card.
Figure 1-2 Facility Loopback Path on a Near-End OC-N Card
DS-N XC OC-N
Test Set
In CTC, OC-N cards with facility loopbacks show an icon (
Figure 1-3 ). Loopback icons are not shown
on other cards in this release.
Figure 1-3 OC-N Facility Loopback Indicator
Caution Before performing a facility loopback on an OC-N card, be sure the card contains at least two data communications channel (DCC) paths to the node where the card is installed. A second DCC provides a nonlooped path to log into the node after the loopback is applied, enabling you to remove the facility loopback. Ensuring a second DCC is not necessary if you are directly connected to the ONS 15454 containing the loopback OC-N card.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-3
Chapter 1 General Troubleshooting
1.1.1 Facility Loopbacks
Caution Ensure that the facility being loopbacked is not line-timing the node. If it is, a timing loop will be created.
Note CTC sometimes refers to facility loopbacks as facility (line) loopbacks. “Line” is meant to clarify that the loopback signal travels away from the facility where it originates and outward toward the span.
1.1.1.2 ONS 15454 Card Behavior
ONS 15454 port loopbacks either terminate or bridge the loopback signal. All ONS 15454 optical, electrical, Ethernet, and FC_MR-4 facility loopbacks are terminated as shown in
.
When a port terminates a facility loopback signal, the signal only loops back to the originating port and is not transmitted downstream. When a port bridges a loopback signal, the signal loops back to the originating port and is also transmitted downstream.
Note In
Table 1-1 , no alarm indication signal (AIS) is injected if the signal is bridged. If the signal is
terminated, an applicable AIS is injected downstream for all cards except Ethernet cards.
Table 1-1 ONS 15454 Card Facility Loopback Behavior
Card/Port
DS-1
DS-3
DS3XM-6 or DS3XM-12
All OC-N cards
EC-1
G-Series Ethernet
C-Series Ethernet
Facility Loopback Signal
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
1
Terminated
2
1.
G-Series facility loopback is terminated and no AIS is sent downstream. However, the Cisco Link Integrity signal continues to be sent downstream.
2.
C-Series facility loopback is terminated and no AIS is sent downstream. However, the Cisco Link Integrity signal continues to be sent downstream.
The loopback itself is listed in the Conditions window; for example, the Conditions window would list the LPBKFACILITY condition for a tested port. (The Alarms window will show AS-MT, which means that alarms are suppressed on the facility during loopback.)
The following behaviors also occur during loopback:
• If an electrical or optical port is in the Out-of-Service and Management, Disabled
(OOS-MA,DSBLD) service state, the port injects an AIS signal upstream and downstream.
• When an electrical or optical port is placed in the OOS-MA,MT service state before loopback testing, the port clears the AIS signal upstream and downstream unless there is a service-affecting defect that causes an AIS signal to be injected. For more information about placing ports into alternate states for testing, refer to the “Change Card Settings” chapter in the Cisco ONS 15454
Procedure Guide .
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-4 November 2009
Chapter 1 General Troubleshooting
1.1.2 Terminal Loopbacks
FC_MR-4 card facility loopbacks behave differently from other ONS 15454 cards. With a client-side facility loopback, the client port service state is OOS-MA,LPBK & MT; however the remaining client and trunk ports can be in any other service state. For cards in a trunk-side facility loopback, the trunk port service state is OOS-MA,LPBK & MT service state and the remaining client and trunk ports can be in any other service state.
Caution A lock out of protection must be executed before putting a two-fiber or four-fiber bidirectional line switched ring (BLSR) span into a facility loopback state. That is, a span lockout of one side (such as the east side) of a two-fiber BLSR is required before operating a facility loopback on the same (east) side of the ring. A span lockout of one protection side (such as the east protection side) of a four-fiber BLSR is required before operating a facility loopback on the same (east) side of the ring. If you do not execute the lockout prior to creating the loopback, the ring can become stuck in an anomalous state after you release the loopback.
1.1.2 Terminal Loopbacks
The following sections give general information about terminal loopback operations and specific information about ONS 15454 card loopback activity.
1.1.2.1 General Behavior
A terminal loopback tests a circuit path as it passes through the cross-connect card and loops back from the card with the loopback.
Figure 1-4 shows a terminal loopback on an OC-N card. The test-set traffic
comes into the electrical port and travels through the cross-connect card to the optical card. The terminal loopback on the optical card turns the signal around before it reaches the LIU and sends it back through the cross-connect card to the electrical card. This test verifies that the cross-connect card and terminal circuit paths are valid, but does not test the LIU on the optical card.
Figure 1-4 Terminal Loopback Path on an OC-N Card
DS-N XC OC-N
Test Set
In CTC, OC-N cards with terminal loopbacks show an icon (
Figure 1-5 ). Loopback icons are not shown
on other cards in this release.
Figure 1-5 Terminal Loopback Indicator
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-5
Chapter 1 General Troubleshooting
1.1.2 Terminal Loopbacks
shows a terminal loopback on a DS-N electrical card. The test-set traffic comes in on the optical card and travels through the cross-connect card to the electrical card. The terminal loopback on the electrical card turns the signal around before it reaches the LIU and sends it back through the cross-connect card to the optical card. This test verifies that the cross-connect card and terminal circuit paths are valid, but does not test the LIU on the electrical card.
Note CTC sometimes refers to terminal loopbacks as terminal (inward) loopbacks. “Inward” is meant to clarify that the loopback signal travels inward toward the facility where it originates and not outward toward the span.
Figure 1-6 Terminal Loopback Path on a DS-N Card
DS-N XC OC-N
Test Set
1.1.2.2 ONS 15454 Card Behavior
ONS 15454 terminal port loopbacks can either terminate or bridge the signal. In the ONS 15454 system, all optical, electrical, Ethernet, and FC_MR-4 terminal loopbacks are terminated as shown in
During terminal loopbacks, some ONS 15454 cards bridge the loopback signal while others terminate it.
If a port terminates a terminal loopback signal, the signal only loops back to the originating port and is not transmitted downstream. If the port bridges a loopback signal, the signal loops back to the originating port and is also transmitted downstream.
Table 1-2 lists ONS 15454 card terminal loopback bridging and terminating behaviors.
Note
AIS is injected downstream for all cards except Ethernet cards.
Table 1-2
Card/Port
ONS 15454 Card Terminal Loopback Behavior
DS-1
DS-3
DS3XM-6 or DS3XM-12
All OC-N cards
EC-1
G-Series Ethernet
C-Series Ethernet
Terminal Loopback Signal
Terminated
Bridged
Bridged
Bridged
Bridged
Terminated
1
Terminated
2
1.
G-Series Ethernet terminal loopback is terminated and Ethernet transmission is disabled. No
AIS is inserted for Ethernet, but a TPTFAIL alarm is raised on the far-end Ethernet port.
2.
C-Series Ethernet terminal loopback is terminated and Ethernet transmission is disabled. No
AIS is inserted for Ethernet, but a TPTFAIL alarm is raised on the far-end Ethernet port.
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-6 November 2009
Chapter 1 General Troubleshooting
1.1.2 Terminal Loopbacks
Figure 1-7
Test Set
Bridged DS-N and OC-N terminal loopback examples are shown in
.
Terminal Loopback on a DS-N Card with a Bridged Signal
DS-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC DS-N
Test Set
Figure 1-8 Terminal Loopback on an OC-N Card with a Bridged Signal
OC-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set Test Set
G-Series Ethernet cards placed in terminal loopback have different performance monitoring behaviors from other ONS 15454 cards. (For more information about performance monitoring counters, see the
“Performance Monitoring” chapter in the Cisco ONS 15454 Reference Manual .) Setting a terminal loopback on the G-Series Ethernet card might not stop the Tx Packets counter or the Rx Packet counters on the CTC card-level view Performance > Statistics page from increasing. The counters can increment even though the loopbacked port has temporarily disabled the transmit laser and is dropping any received packets.
The Tx Packet statistic continues to increment because the statistics are not based on packets transmitted by the transmit (Tx) laser but on the Tx signal inside the G-Series card. In normal in-service port operation, the Tx signal being recorded results in the Tx laser transmitting packets, but in a terminal loopback this signal is being looped back within the G-Series card and does not result in the Tx laser transmitting packets.
The Rx Packet counter might also continue to increment when the G-Series card is in terminal loopback.
Receive (Rx) packets from any connected device are dropped and not recorded, but the internally loopbacked packets follow the G-Series card’s normal receive path and register on the Rx Packet counter.
The loopback itself is listed in the Conditions window. For example, the Conditions window would list the LPBKTERMINAL condition or the LPBKFACILITY condition for a tested port. (The Alarms window would show AS-MT, which indicates that all alarms are suppressed on the port during loopback testing.)
The following behaviors also occur during loopback:
• If an electrical or optical port is in the OOS-MA,DSBLD service state, the port injects an AIS signal upstream and downstream.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-7
Chapter 1 General Troubleshooting
1.1.3 Hairpin Circuits
• When an electrical or optical port is placed in the OOS-MA,MT service state before loopback testing, the port clears the AIS signal upstream and downstream unless there is a service-affecting defect that also causes an AIS signal to be injected. For more information about placing ports into alternate states for testing, refer to the “Change Card Settings” chapter of the Cisco ONS 15454
Procedure Guide .
Caution A lock out of protection must occur before putting a two-fiber or four-fiber BLSR span into a terminal loopback state. That is, a span lockout of one side (such as the east side) of a two-fiber BLSR is required before operating a facility loopback on the same (east) side of the ring. A span lockout of one protection side (such as the east protection side) of a four-fiber BLSR is required before operating a terminal loopback on the same (east) side of the ring. If you do not perform the lockout prior to creating the loopback, the ring can become stuck in an anomalous state after you release the loopback.
1.1.3 Hairpin Circuits
A hairpin circuit sends traffic in and out an electrical port rather than sending the traffic onto the OC-N card. A hairpin loops back only the specific synchronous transport signal (STS) or virtual tributary (VT) circuit and does not cause an entire OC-N port to loop back, preventing all traffic on the OC-N port from dropping. The hairpin allows you to test a specific STS or VT circuit on nodes running live traffic.
shows the hairpin circuit path on a DS-N card.
Figure 1-9 Hairpin Circuit Path on a DS-N Card
DS-N XC OC-N
Test Set
1.1.4 Cross-Connect Loopbacks
A cross-connect (XC) loopback tests an OC-N circuit path as it passes through the cross-connect card and loops back to the port being tested without affecting other traffic on the optical port. Cross-connect loopbacks are less invasive than terminal or facility loopbacks. Facility and terminal loopback testing and circuit verification often involve taking down the whole line; however, a cross-connect loopback allows you to create a loopback on any embedded channel at supported payloads of STS-1 granularity and higher. For example, you can place a loopback on a single STS-6c on an optical facility without interrupting the other STS circuits.
This test can be conducted locally or remotely through the CTC interface without on-site personnel. It takes place only on an OC-N card and tests the traffic path on that STS (or higher) circuit through the port and cross-connect card. The signal path is similar to a facility loopback.
The XC loopback breaks down the existing path and creates a new cross-connect—a hairpin—while the source of the original path is set to inject a line-side AIS-P. The loopback signal path and AIS injection are shown in
1-8
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2 Troubleshooting Electrical Circuit Paths With Loopbacks
Figure 1-10 Network Element with SONET Cross-Connect Loopback Function
Equipment to perform framing, scrambling, etc.
(such as signal terminating equipment)
External signals from and to other equipment
OOS
O/E
E/O
R
T
AIS
Internal signals to and from other equipment in the NE
Consider the following rules when creating cross-connect loopbacks:
•
•
You can create a cross-connect loopback on all working or protect optical ports unless the protect port is used in a 1+1 protection group and is in working mode.
If a terminal or facility loopback exists on a port, you cannot use the cross-connect loopback.
1.2 Troubleshooting Electrical Circuit Paths With Loopbacks
Facility loopbacks, terminal loopbacks, and hairpin circuits are often used to test a circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure.
The example in this section tests an electrical circuit on a two-node BLSR. Using a series of facility loopbacks, terminal loopbacks, hairpins, and (where appropriate) cross-connect loopbacks on optical paths carrying electrical circuits, the path of the circuit is traced and the possible points of failure are tested and eliminated. A logical progression of eight network test procedures apply to this sample scenario:
Note These procedures apply to DS-1, DS-3, and EC-1 cards. The test sequence for your circuits will differ according to the type of circuit and network topology.
West-to-east direction (left to right):
1.
2.
3.
A facility loopback on the source-node electrical port (DS-N or EC-N)
A hairpin on the source-node electrical port
An XC loopback on the destination-node OC-N STS (carrying the electrical circuit)
4.
A terminal loopback on the destination-node electrical port
East-to-west direction (right to left):
1.
2.
3.
4.
A facility loopback on the destination-node electrical port
A hairpin on the destination-node electrical port
An XC loopback on the source-node OC-N STS (carrying the electrical circuit)
A terminal loopback on the source-node electrical port
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-9
Chapter 1 General Troubleshooting
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
Note Facility, hairpin, and terminal loopback tests require on-site personnel.
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
The facility loopback test is performed on the node’s source electrical port in the network circuit; in this example, the DS-N port in the source node. Completing a successful facility loopback on this port isolates the cabling, the electrical card, and the EIA as possible failure points.
example of a facility loopback on a source DS-N port.
Figure 1-11 Facility Loopback on a Circuit Source DS-N Port
DS-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC DS-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting. To protect traffic, apply a lockout or
Force switch to the target loopback port. For more information about these operations, refer to the
“Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Note Facility loopbacks require on-site personnel.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Depending on your card type, complete the
“Create the Facility Loopback on the Source DS-1, DS-3,
DS3N-12, DS3i-N-12, or EC1 Port” procedure on page 1-10
or the
“Create the Facility Loopback on the
Source DS3E or DS3XM Port” procedure on page 1-11 , then test and clear the loopbacks as instructed.
Create the Facility Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port
Step 1
Step 2
Step 3
Connect an electrical test set to the port you are testing.
Use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the EIA connectors or DSx panel for the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (For specific procedures to use the test set equipment, consult the manufacturer.)
In node view, double-click the card to open the card view.
1-10
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
Step 4
Step 5
Step 6
Step 7
Step 8
Click the Maintenance > Loopback tabs.
Choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (DS1, DS3)” condition on page 2-163
to appear during loopback setup. The condition clears when you remove the loopback.
Step 9 Complete the
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback.
Double-click the card to open the card view.
Depending on the card type, click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the Electrical Cabling” procedure on page 1-13 .
Create the Facility Loopback on the Source DS3E or DS3XM Port
This procedure applies to DS3E, DS3XM-6, and DS3XM-12 cards. It does not use the DS3XM card
FEAC loopback functions. For FEAC information, refer to the
“1.3 Troubleshooting DS3XM-6 or
DS3XM-12 Card Electrical Paths With FEAC Loopbacks” section on page 1-45
.
Step 1
Step 2
Connect an electrical test set to the port you are testing.
Use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the EIA connectors or DSx panel for the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (For specific procedures to use the test set equipment, consult the manufacturer.)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-11
Chapter 1 General Troubleshooting
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
Step 3
Step 4
In node view, double-click the card to open the card view.
For any of these cards, click the Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
For the DS3 tab, choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested. For the DS1 tab, no state selection is necessary unless the DS-1 is in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (DS1, DS3)” condition on page 2-163
to appear during loopback setup. The condition clears when you remove the loopback.
Step 9
Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback.
Double-click the card to open the card view.
For any of these cards, click the Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test the Electrical Cabling” procedure on page 1-13
.
1-12
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
Test the Electrical Cabling
Step 1
Step 2
Step 3
Step 4
Replace the suspected bad cabling (the cables from the test set to the DSx panel or the EIA ports) with a known-good cable. For instructions, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If a known-good cable is not available, test the suspected bad cable with a test set. Remove the suspected bad cable from the DSx panel or the EIA and connect the cable to the Tx and Rx terminals of the test set. Run traffic to determine whether the cable is good or defective.
Resend test traffic on the loopback circuit with a known-good cable installed. If the test set indicates a good circuit, the problem was probably the defective cable.
Replace the defective cable.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs,
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the Electrical Card” procedure on page 1-13 .
Test the Electrical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the Return Materials Authorization (RMA) process. Contact Cisco Technical
Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs,
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 6
Step 7
Step 8
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-13
Chapter 1 General Troubleshooting
1.2.1 Perform a Facility Loopback on a Source Electrical Port (West to East)
Step 9
Step 10
Click Yes in the confirmation dialog box.
Complete the “Test the EIA” procedure on page 1-14
.
Test the EIA
Step 1
Step 2
Step 3
Remove and reinstall the EIA to ensure a proper seating: a.
Remove the lower backplane cover. Loosen the five screws that secure it to the ONS 15454 and pull it away from the shelf assembly.
b.
c.
Loosen the nine perimeter screws that hold the EIA panel in place.
Lift the EIA panel by the bottom to remove it from the shelf assembly.
d.
Follow the installation procedure for the appropriate EIA. Refer to the “Install the Shelf and
Backplane Cable” procedure in the Cisco ONS 15454 Procedure Guide for instructions.
Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the reinstalled EIA. If the test set indicates a good circuit, the problem was probably an improperly seated
EIA, and you can proceed to
. If the problem persists and the EIA is not shown to be improperly seated, proceed to
.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs,
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box. Proceed to
.
If the test set indicates a faulty circuit, the problem is probably a defective EIA. Return the defective EIA to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Replace the faulty EIA by completing the
“Replace the Electrical Interface Assembly” procedure on page 2-274
.
Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the replacement EIA. If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.
If the test set indicates a good circuit, the problem was probably the defective EIA. Clear the facility loopback by clicking the Maintenance > Loopback tabs, Maintenance > DS1 tabs, or Maintenance >
DS3 tabs.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
1-14
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to East)
Step 16 Complete the
1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to East)
The hairpin test is performed on the cross-connect card in the network circuit. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through the port isolates the possibility that the cross-connect card is the cause of the faulty circuit.
shows an example of a hairpin loopback on a source-node port.
Figure 1-12 Hairpin on a Source-Node Port
DS-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC DS-N
Test Set
Note The ONS 15454 does not support simplex operation on the cross-connect card. Two cross-connect cards of the same type must be installed for each node.
Note Hairpin loopbacks require on-site personnel.
Complete the
“Create the Hairpin Circuit on the Source-Node Electrical Port” procedure on page 1-15 .
Create the Hairpin Circuit on the Source-Node Electrical Port
Step 1
Step 2
Step 3
Connect an electrical test set to the port you are testing: a.
If you just completed the “1.2.1 Perform a Facility Loopback on a Source Electrical Port
(West to East)” procedure on page 1-10
, leave the electrical test set hooked up to the electrical port in the source node.
b.
If you are starting the current procedure without the electrical test set hooked up to the DS-N port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the hairpin circuit on the test port: a.
In node view, click the Circuits tab and click Create .
b.
c.
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-15
Chapter 1 General Troubleshooting
1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to East)
Step 4
Step 5 d.
e.
f.
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as Hairpin1.
Choose the Size, such as STS-1.
Uncheck the Bidirectional check box. Leave the default values for State, SD Threshold, and
SF Threshold.
g.
h.
i.
j.
k.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. Leave Use Secondary Source unchecked.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. Leave Use Secondary Destination unchecked.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
l.
Confirm that the newly created circuit appears on the Circuits tab and that the Dir column describes it as a one-way circuit.
Complete the “Test and Delete the Electrical Port Hairpin Circuit” procedure on page 1-16
.
Test and Delete the Electrical Port Hairpin Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
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.
If the test set indicates a good circuit, no further testing is necessary with the hairpin circuit. Clear the hairpin circuit: a.
b.
c.
d.
Click the Circuits tab.
Choose the hairpin circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
e.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
Complete the “Test the Standby Cross-Connect Card” procedure on page 1-16 .
Test the Standby Cross-Connect Card
1-16
Note Two cross-connect cards (active and standby) must be in use on a node to use this procedure.
Step 1 Perform a reset on the standby cross-connect card to make it the active card: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to East)
Step 2 b.
c.
d.
Position the cursor over the standby cross-connect card.
Right-click and choose RESET CARD .
Click Yes in the confirmation dialog box.
Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:
Caution Cross-connect side switches, with the exception of side switches using XC-VXC-10G cards, are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms. XC-VXC-10G side switches are errorless. b.
c.
d.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
In the node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Step 3
Step 4
Step 5
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Resend test traffic on the loopback circuit.
The test traffic now travels through the alternate cross-connect card.
If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem. Clear the hairpin circuit: a.
Click the Circuits tab.
b.
c.
d.
Choose the hairpin circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
e.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
To confirm a defective original cross-connect card, complete the
“Retest the Original Cross-Connect
Card” procedure on page 1-17 .
Retest the Original Cross-Connect Card
Step 1 Initiate an external switching command (side switch) on the cross-connect cards: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
In node view, select the Maintenance > Cross-Connect > Cards tabs.
From the Cross-Connect Cards menu, choose Switch .
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-17
Chapter 1 General Troubleshooting
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal d.
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 2
Step 3
Step 4
Step 5
Step 6
Resend test traffic on the loopback circuit.
If the test set indicates a faulty circuit, the problem is probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 and
. If the test does not indicate a faulty circuit, proceed to
Complete the
“Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266 for the
defective card.
If the test set indicates a good circuit, the cross-connect card might have had a temporary problem that was cleared by the side switch. Clear the hairpin circuit: a.
b.
Click the Circuits tab.
Choose the hairpin circuit being tested.
c.
d.
e.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
Complete the “1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East)
Carrying an Electrical Signal” procedure on page 1-18
.
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East)
Carrying an Electrical Signal
The XC loopback tests whether any problem exists on the circuit’s OC-N span, isolating this span from others present on the card. The loopback occurs on the cross-connect card in a network circuit.
shows an example of an XC loopback on a destination OC-N port. The traffic pattern looks similar to a terminal loopback but traffic is only carried on one STS instead of affecting the entire port.
Note The XC loopback on an OC-N card does not affect traffic on other circuits.
Note XC loopbacks do not require on-site personnel.
Note You can perform an XC loopback on either the circuit source working or the protect port of a 1+1 protection group.
1-18
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal
Figure 1-13 XC Loopback on a Destination OC-N Port
DS-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC DS-N
Test Set
Create the XC Loopback on a Destination-Node OCN STS
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5 a.
b.
If you just completed the “1.2.2 Perform a Hairpin Test on a Source-Node Electrical Port (West to
East)” procedure on page 1-15 , leave the optical test set hooked up to the destination-node port.
If you are starting the current procedure without the optical test set hooked up to the destination port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to put the circuit being tested out of service: a.
b.
In node view, click the Circuits tab.
Click the circuit and then click Edit .
c.
d.
e.
In the Edit Circuit dialog box, click the State tab.
Choose OOS,MT from the Target Circuit Admin State drop-down list.
Click Apply .
Click Yes in the confirmation dialog box.
f.
Use CTC to set up the XC loopback on the circuit being tested: a.
In node view, double-click the OC-N card to open the card view.
b.
c.
d.
Click the Maintenance > Loopback > SONET STS
Click the check box in the XC Loopback tabs.
column for the port being tested.
e.
Check Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the XC Loopback Circuit” procedure on page 1-20
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-19
Chapter 1 General Troubleshooting
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal
Test and Clear the XC Loopback Circuit
Note This procedure is performed only on OC-N cards.
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
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.
If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the
XC loopback: a.
b.
c.
d.
In card view, click the Maintenance > Loopback > SONET STS tabs.
Uncheck the check box in the
Click Apply .
Click Yes
XC Loopback
in the confirmation dialog box.
column for the circuit being tested.
Complete the “Test the Standby Cross-Connect Card” procedure on page 1-20 .
Test the Standby Cross-Connect Card
Step 1
Step 2
Perform a reset on the standby cross-connect card: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
Position the cursor over the standby cross-connect card.
Right-click and choose RESET CARD .
Click Yes in the confirmation dialog box.
Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:
Caution Cross-connect side switches, with the exception of side switches using XC-VXC-10G cards, are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms. XC-VXC-10G side switches are errorless. b.
c.
d.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
In the node view, select the Maintenance > Cross-Connect > Card tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
1-20
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.3 Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal
Step 3
Step 4
Step 5
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Resend test traffic on the loopback circuit.
The test traffic now travels through the alternate cross-connect card.
If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem. Clear the XC loopback circuit: a.
Click the Circuits tab.
b.
c.
d.
Choose the XC loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
e.
Confirm that the XC loopback circuit is deleted from the Circuits tab list. If the test set indicates a good circuit, the problem might be a defective cross-connect card.
To confirm a defective original cross-connect card, complete the
“Retest the Original Cross-Connect
Card” procedure on page 1-21 .
Retest the Original Cross-Connect Card
Note This procedure is performed only on OC-N and cross-connect cards.
Step 1 Initiate an external switching command (side switch) on the cross-connect cards.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
In node view, select the Maintenance > Cross-Connect > Card tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 2
Step 3
Step 4
Resend test traffic on the loopback circuit.
If the test set indicates a faulty circuit, the problem is probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 and proceed to
. If the circuit is not shown to be faulty and the card is not shown to be defective, you are finished with testing.
Complete the “Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266
for the defective cross-connect card and perform
.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-21
Chapter 1 General Troubleshooting
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
Step 5
Step 6
If the test set indicates a good circuit, the cross-connect card might have had a temporary problem that was cleared by the side switch. Clear the XC loopback circuit: a.
b.
c.
d.
Click the
Choose the XC loopback circuit being tested.
Click
Circuits
Delete .
tab.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
If the tests indicate further problems, go to the
“1.2.4 Perform a Terminal Loopback on a Destination
Electrical Port (West to East)” procedure on page 1-22
.
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to
East)
The terminal loopback test is performed on the destination-node electrical port in the circuit, such as a destination-node electrical port. You create a bidirectional circuit that starts on the source-node electrical port and loops back on the destination-node electrical port. Then you proceed with the terminal loopback test. Completing a successful terminal loopback to a destination-node electrical port verifies that the circuit is good to the destination electrical port.
Figure 1-14 shows an example of a terminal loopback
on a destination DS-N port.
Figure 1-14 Terminal Loopback to a Destination DS-N Port
DS-N
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC DS-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting. To protect traffic, apply a lockout or
Force switch to the target loopback port. For more information about these operations, refer to the
“Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Caution In terminal loopback mode, DS3E-12 card does not support sending AIS toward the line side while looping back traffic at the same time, though NE defaults are the same.
Note Terminal loopbacks require on-site personnel.
1-22
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Depending upon your card type, complete the “Create the Terminal Loopback on a Destination DS-3,
DS3N-12, DS3i-N-12, or EC1 Port” procedure on page 1-23
or the
“Create the Terminal Loopback on a
Destination DS-3E or DS3XM Port” procedure on page 1-25
. Then test and clear the loopback as instructed.
Create the Terminal Loopback on a Destination DS-3, DS3N-12, DS3i-N-12, or EC1 Port
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 1
Step 10
Step 11
Step 12
Step 13
Step 14
Connect an electrical test set to the port you are testing: a.
If you just completed the
, leave the electrical test set hooked up to the source-node port. b.
If you are starting the current procedure without the electrical test set hooked up to the electrical port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS2.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the Node , card Slot , Port , and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears in the Dir column as a two-way circuit.
Note
It is normal for the “LPBKTERMINAL (DS1, DS3)” condition on page 2-168 to appear during
a loopback setup. The condition clears when you remove the loopback.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-23
Chapter 1 General Troubleshooting
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
Step 15
Step 16
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
d.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback, such as a DS-N card in the destination node.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
e.
f.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal
Loopback Circuit” procedure on page 1-24
.
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.
Double-click the electrical card in the destination node with the terminal loopback.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback: a.
b.
Click the Circuits tab.
Choose the loopback circuit being tested.
c.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Destination Electrical Card” procedure on page 1-27 .
1-24
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
Create the Terminal Loopback on a Destination DS-3E or DS3XM Port
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 1
Step 9
Step 10
Step 11
Step 12
Step 13
Connect an electrical test set to the port you are testing: a.
b.
If you just completed the
, leave the electrical test set hooked up to the electrical port in the source node.
If you are starting the current procedure without the electrical test set hooked up to the electrical port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. Both Tx and Rx connect to the same port.
c.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS3.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the Node , card Slot , Port , and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears in the Dir column as a two-way circuit.
Note
It is normal for the “LPBKTERMINAL (DS1, DS3)” condition on page 2-168 to appear during
a loopback setup. The condition clears when you remove the loopback.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided.
A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Step 14 Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.
Click the Maintenance > DS3 tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-25
Chapter 1 General Troubleshooting
1.2.4 Perform a Terminal Loopback on a Destination Electrical Port (West to East)
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 15 d.
e.
For the DS3 tab, choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested. For the DS1 tab, no state selection is necessary unless the DS-1 is in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
f.
g.
Click Apply .
Click Yes in the confirmation dialog box.
Test and Clear the DS-3E or DS3XM Destination Port Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.
Double-click the electrical card in the destination node with the terminal loopback.
Click the Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Destination Electrical Card” procedure on page 1-27 .
1-26
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Test the Destination Electrical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the defective electrical card.
Clear the terminal loopback state on the port: a.
b.
Double-click the electrical card in the destination node with the terminal loopback.
Depending upon the card type, click the Maintenance > Loopback tabs, Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 6
Step 7 c.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Delete the terminal loopback circuit: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to
West)
The facility loopback test is performed on the destination-node electrical port in the network circuit.
Completing a successful facility loopback on this port isolates the cabling, the electrical card, and the
EIA as possible failure points.
shows an example of a facility loopback on a destination
DS-N port.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-27
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Figure 1-15 Facility Loopback on a Circuit Destination DS-N Port
DS-N
Source
ONS Node
XC OC-N DS-N
Intermediate
ONS Node
XC OC-N
Test Set
DS-N
Destination
ONS Node
XC OC-N
Caution Performing a loopback on an in-service circuit is service-affecting. To protect traffic, apply a lockout or
Force switch to the target loopback port. For basic instructions, refer to the
Lock Initiation, and Clearing” section on page 2-254
. For more information about these operations, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Note Facility loopbacks require on-site personnel.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Depending on your card type, complete the
“Create the Facility Loopback on the Destination DS-1,
DS-3, DS3N-12, DS3i-N-12, or EC-1 Port” procedure on page 1-28 or the
“Create the Facility Loopback on the Source DS3E or DS3XM Port” procedure on page 1-29
. Then test and clear the loopback as instructed.
Create the Facility Loopback on the Destination DS-1, DS-3, DS3N-12, DS3i-N-12, or EC-1 Port
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Connect an electrical test set to the port you are testing: a.
b.
If you just completed the
“1.2.4 Perform a Terminal Loopback on a Destination Electrical Port
(West to East)” procedure on page 1-22 , leave the electrical test set hooked up to the
destination-node port.
Use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the EIA connectors or DSx panel for the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, double-click the card to open the card view.
Click the Maintenance > Loopback tabs.
Choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
1-28
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Step 7
Step 8
Click Apply .
Click Yes in the confirmation dialog box.
Note
It is normal for a “LPBKFACILITY (DS1, DS3)” condition on page 2-163 to appear during
loopback setup. The condition clears when you remove the loopback.
Step 9 Complete the
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC-1 Port Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback.
Double-click the card to open the card view.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the Electrical Cabling” procedure on page 1-30 .
Create the Facility Loopback on the Source DS3E or DS3XM Port
This procedure applies to DS3E, DS3XM-6, and DS3XM-12 cards. It does not utilize the DS3XM card
FEAC loopback functions. For FEAC information, refer to the
“1.3 Troubleshooting DS3XM-6 or
DS3XM-12 Card Electrical Paths With FEAC Loopbacks” section on page 1-45
.
Step 1
Step 2
Step 3
Connect an electrical test set to the port you are testing.
Use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the EIA connectors or DSx panel for the port you are testing. The Tx and Rx terminals connect to the same port. Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, double-click the card to open the card view.
For any of these cards, click the Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-29
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Step 4
Step 5
Step 6
Step 7
For the DS3 tab, choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested. For the DS1 tab, no state selection is necessary unless the DS-1 is in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (DS1, DS3)” condition on page 2-163
to appear during loopback setup. The condition clears when you remove the loopback.
Step 8
Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback.
Double-click the card to open the card view.
For any of these cards, click the Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test the Electrical Cabling” procedure on page 1-30
.
Test the Electrical Cabling
Step 1 Replace the suspected bad cabling (from the test set to the DSx panel or the EIA ports) with known-good cable. For instructions, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
1-30
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Step 2
Step 3
Step 4
If a known-good cable is not available, test the suspected bad cable with a test set. (Refer to manufacturer instructions for test-set use.) Remove the suspected bad cable from the DSx panel or the EIA and connect the cable to the Tx and Rx terminals of the test set. Run traffic to determine whether the cable is good or defective.
Resend test traffic on the loopback circuit with a known-good cable installed. If the test set indicates a good circuit, the problem was probably the defective cable.
Replace the defective cable.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs,
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the Electrical Card” procedure on page 1-31 .
Test the Electrical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 .
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs,
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 6
Step 7
Step 8
Step 9
Step 10
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the EIA” procedure on page 1-32 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-31
Chapter 1 General Troubleshooting
1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port (East to West)
Test the EIA
Step 1
Step 2
Step 3
Remove and reinstall the EIA to ensure a proper seating: a.
b.
c.
Remove the lower backplane cover. Loosen the five screws that secure it to the ONS 15454 and pull it away from the shelf assembly.
Loosen the nine perimeter screws that hold the EIA panel in place.
d.
Lift the EIA panel by the bottom to remove it from the shelf assembly.
Follow the installation procedure for the appropriate EIA. Refer to the “Install the Shelf and
Backplane Cable” chapter in the Cisco ONS 15454 Procedure Guide for instructions.
Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the reinstalled EIA. If the test set indicates a good circuit, the problem was probably an improperly seated
EIA, and you can proceed to
. If the problem persists and the EIA is not shown to be improperly seated, proceed to
.
In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tabs
Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
If the test set indicates a faulty circuit, the problem is probably a defective EIA. Return the defective EIA to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Replace the faulty EIA. Complete the
“Replace the Electrical Interface Assembly” procedure on page 2-274
.
Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the replacement EIA. If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.
If the test set indicates a good circuit, the problem was probably the defective EIA. Clear the facility loopback by clicking the Maintenance > Loopback tabs, Maintenance > DS1 tabs, or Maintenance >
DS3 tabs.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
1-32
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.6 Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)
1.2.6 Perform a Hairpin Test on a Destination-Node Electrical Port (East to
West)
The hairpin test is performed on the cross-connect card in the network circuit and uses the same port as source as well as destination. Completing a successful hairpin through the card isolates the possibility that the cross-connect card is the cause of the faulty circuit.
shows an example of a hairpin loopback on a destination-node port.
Figure 1-16 Hairpin on a Destination-Node DS-N Port
DS-N
Source
ONS Node
XC OC-N DS-N
Intermediate
ONS Node
XC OC-N DS-N
Destination
ONS Node
XC OC-N
Test Set
Note The ONS 15454 does not support simplex operation on the cross-connect card. Two cross-connect cards of the same type must be installed for each node.
Note Hairpin loopbacks require on-site personnel.
Complete the
“Create the Hairpin Circuit on the Destination-Node Port” procedure on page 1-33
.
Create the Hairpin Circuit on the Destination-Node Port
Step 1
Step 2
Step 3
Connect an electrical test set to the port you are testing: a.
b.
If you just completed the
“1.2.5 Perform a Facility Loopback on a Destination-Node Electrical Port
in the destination node.
If you are starting the current procedure without the electrical test set hooked up to the electrical port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the hairpin circuit on the test port: a.
d.
e.
b.
c.
In node view, click the Circuits
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
Choose the Size, such as STS-1.
tab and click Create .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as Hairpin1.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-33
Chapter 1 General Troubleshooting
1.2.6 Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)
Step 4
Step 5 f.
g.
h.
Uncheck the Bidirectional check box. Leave the default values for State, SD Threshold, and
SF Threshold.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. Leave Use Secondary Source unchecked.
i.
j.
k.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. Leave Use Secondary Destination unchecked.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
l.
Confirm that the newly created circuit appears on the Circuits tab and that the Dir column describes it as a one-way circuit.
Complete the “Test and Delete the Electrical Hairpin Circuit” procedure on page 1-34 .
Test and Delete the Electrical Hairpin Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
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.
If the test set indicates a good circuit, no further testing is necessary with the hairpin circuit. Clear the hairpin circuit: a.
b.
c.
Click the Circuits tab.
Choose the hairpin circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
d.
e.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
Complete the “Test the Standby Cross-Connect Card” procedure on page 1-34 .
Test the Standby Cross-Connect Card
1-34
Note Two cross-connect cards (active and standby) must be in use on a node to use this procedure.
Step 1 Perform a reset on the standby cross-connect card to make it the active card: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
Position the cursor over the standby cross-connect card.
Right-click and choose RESET CARD .
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.6 Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)
Step 2 d.
Click Yes in the confirmation dialog box.
Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:
Caution Cross-connect side switches, with the exception of side switches using XC-VXC-10G cards, are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms. XC-VXC-10G side switches are errorless. b.
c.
d.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
In the node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 3
Step 4
Step 5
Resend test traffic on the loopback circuit.
The test traffic now travels through the alternate cross-connect card.
If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem. Clear the hairpin circuit: a.
b.
Click the Circuits tab.
Choose the hairpin circuit being tested.
Click Delete . c.
d.
e.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
To confirm a defective original cross-connect card, complete the
“Retest the Original Cross-Connect
Card” procedure on page 1-35 .
Retest the Original Cross-Connect Card
Step 1 Initiate an external switching command (side switch) on the cross-connect cards: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
In node view, select the Maintenance > Cross-Connect > Cards tabs.
From the Cross-Connect Cards menu, choose Switch .
Click Yes in the Confirm Switch dialog box.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-35
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit
Chapter 1 General Troubleshooting
Step 2
Step 3
Step 4
Step 5
Step 6
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Resend test traffic on the loopback circuit.
If the test set indicates a faulty circuit, the problem is probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 and
. If the test does not indicate a faulty circuit, proceed to
Complete the
“Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266 for the
defective cross-connect card.
If the test set indicates a good circuit, the cross-connect card might have had a temporary problem that was cleared by the side switch. Clear the hairpin circuit: a.
b.
c.
Click the Circuits tab.
Choose the hairpin circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
e.
Confirm that the hairpin circuit is deleted from the Circuits tab list.
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West)
Carrying an Electrical Circuit
The XC loopback tests whether problem exists on the circuit’s OC-N span by isolating this span from others on the card. The loopback also eliminates the cross-connect card as the source of trouble for a faulty circuit. The loopback occurs on the cross-connect card in a network circuit.
example of an XC loopback on a source OC-N port.
Note The XC loopback on an OC-N card does not affect traffic on other circuits.
Note XC loopbacks do not require on-site personnel.
Note You can perform an XC loopback on either the circuit source working port or the protect port of a 1+1 protection group.
1-36
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit
Figure 1-17
Test Set
XC Loopback on a Source OC-N Port
OC-Nx XC OC-Ny
Complete the
Create the XC Loopback on the Source OC-N Port Carrying an Electrical Circuit
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5 a.
b.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to put the circuit being tested out of service: a.
d.
e.
b.
c.
f.
In node view, click the
Click the circuit and then click Edit .
In the Edit Circuit dialog box, click the State tab.
Choose OOS,MT from the Target Circuit Admin State drop-down list.
Click Apply .
Circuits tab.
Click Yes in the confirmation dialog box.
Use CTC to set up the XC loopback on the circuit being tested: a.
In node view, double-click the OC-N card to open the card view.
b.
c.
d.
e.
Click the Maintenance > Loopback > SONET STS tabs.
Check the
Click Yes
XC Loopback
Click Apply .
column check box for the port being tested.
in the confirmation dialog box.
Complete the
“Test and Clear the XC Loopback Circuit” procedure on page 1-38
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-37
Chapter 1 General Troubleshooting
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit
Test and Clear the XC Loopback Circuit
Note This procedure is performed only on OC-N cards.
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
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.
If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the
XC loopback: a.
b.
c.
d.
In card view, click the Maintenance > Loopback > SONET STS tabs.
Uncheck the check box in the
Click Apply .
Click Yes
XC Loopback
in the confirmation dialog box.
column for the circuit being tested.
Complete the “Test the Standby Cross-Connect Card” procedure on page 1-38 .
Test the Standby Cross-Connect Card
Step 1
Step 2
Perform a reset on the standby cross-connect card: a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
Position the cursor over the standby cross-connect card.
Right-click and choose RESET CARD .
Click Yes in the confirmation dialog box.
Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:
Caution Cross-connect side switches, with the exception of side switches using XC-VXC-10G cards, are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms. XC-VXC-10G side switches are errorless. b.
c.
d.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
In the node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
1-38
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit
Step 3
Step 4
Step 5
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Resend test traffic on the loopback circuit.
The test traffic now travels through the alternate cross-connect card.
If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem. Clear the XC loopback circuit: a.
Click the Circuits tab.
b.
c.
d.
Choose the XC loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
e.
Confirm that the XC loopback circuit is deleted from the Circuits tab list. If the test set indicates a good circuit, the problem might be a defective cross-connect card.
To confirm a defective original cross-connect card, complete the
“Retest the Original Cross-Connect
Card” procedure on page 1-39 .
Retest the Original Cross-Connect Card
Note This procedure is performed only on OC-N and cross-connect cards.
Step 1 Initiate an external switching command (side switch) on the cross-connect cards.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
In node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 2
Step 3
Step 4
Resend test traffic on the loopback circuit.
If the test set indicates a faulty circuit, the problem is probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 and proceed to
. If the circuit is not shown to be faulty and the card is not shown to be defective, you are finished with testing.
Complete the “Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266
for the defective cross-connect card. Perform
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-39
Chapter 1 General Troubleshooting
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
Step 5 If the test set indicates a good circuit, the cross-connect card might have had a temporary problem that was cleared by the side switch. Clear the XC loopback circuit: a.
d.
e.
b.
c.
Click the Circuits tab.
Choose the XC loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
If the problem is not resolved, go to the “1.2.8 Perform a Terminal Loopback on a Source-Node
Electrical Port (East to West)” section on page 1-40
.
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to
West)
The terminal loopback test is performed on the source-node electrical port in the circuit, such as a source-node electrical port. You first create a bidirectional circuit that starts on the destination-node electrical port and loops back on the source-node electrical port. Then you proceed with the terminal loopback test. Completing a successful terminal loopback to a source-node electrical port verifies that
the circuit is good to the source electrical port. Figure 1-18
shows an example of a terminal loopback on a source DS-N port.
Figure 1-18 Terminal Loopback on a Source DS-N Port
DS-N
Source
ONS Node
XC DS-N DS-N
Intermediate
ONS Node
XC DS-N DS-N
Destination
ONS Node
XC DS-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting. To protect traffic, apply a lockout or
Clearing” section on page 2-254 for basic instructions. For more information about these operations,
refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Caution In terminal loopback mode, DS3E-12 card does not support sending AIS toward the line side while looping back traffic at the same time, though NE defaults are the same.
Note Terminal loopbacks require on-site personnel.
1-40
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
November 2009
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Depending upon your card type, complete the
“Create the Terminal Loopback on a Source DS-1, DS-3,
DS3N-12, DS3i-N-12, or EC1 Port” procedure on page 1-41 or the
“Create the Terminal Loopback on a
Source DS3E or DS3XM Port” procedure on page 1-43 . Then test and clear the loopback as instructed.
Create the Terminal Loopback on a Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 1
Step 10
Step 11
Step 12
Connect an electrical test set to the port you are testing: a.
If you just completed the “1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to
to the DS-N port in the source node. b.
If you are starting the current procedure without the electrical test set hooked up to the DS-N port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS4.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the Node , card Slot , Port , and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
c.
Click Next .
d.
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears in the Dir column as a two-way circuit.
Note
It is normal for the “LPBKTERMINAL (DS1, DS3)” condition on page 2-168 to appear during
a loopback setup. The condition clears when you remove the loopback.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-41
Chapter 1 General Troubleshooting
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
Step 13
Step 14
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
d.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
e.
f.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Terminal Loopback
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.
Double-click the electrical card in the destination node with the terminal loopback.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback: a.
b.
Click the Circuits tab.
Choose the loopback circuit being tested.
c.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Source Electrical Card” procedure on page 1-45 .
1-42
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
Create the Terminal Loopback on a Source DS3E or DS3XM Port
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 1
Step 9
Step 10
Step 11
Connect an electrical test set to the port you are testing: a.
b.
If you just completed the “1.2.7 Perform an XC Loopback on a Source-Node OC-N STS (East to
to the DS-N port in the source node.
If you are starting the current procedure without the electrical test set hooked up to the DS-N port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. Both Tx and Rx connect to the same port.
c.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS5.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the Node , card Slot , Port , and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
d.
e.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears in the Dir column as a two-way circuit.
Note
It is normal for the “LPBKTERMINAL (DS1, DS3)” condition on page 2-168 to appear during
a loopback setup. The condition clears when you remove the loopback.
Note ONS 15454 DS-3 terminal loopbacks do not transmit an AIS in the direction away from the loopback.
Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Step 12 Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.
Click the Maintenance > DS3 tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-43
Chapter 1 General Troubleshooting
1.2.8 Perform a Terminal Loopback on a Source-Node Electrical Port (East to West)
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 13
Step 14
For the DS3 tab, choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the port being tested. For the DS1 tab, no state selection is necessary unless the DS-1 is in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.
d.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
Test and Clear the DS3E or DS3XM Port Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.
Double-click the electrical card in the destination node with the terminal loopback.
Depending upon the card type, click the Maintenance > Loopback tabs, Maintenance > DS1 tabs, or
Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Source Electrical Card” procedure on page 1-45 .
1-44
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks
Test the Source Electrical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the defective electrical card.
Clear the terminal loopback state on the port: a.
b.
Double-click the electrical card in the destination node with the terminal loopback.
Depending upon the card type, click the Maintenance > Loopback tabs, Maintenance > DS1 tabs, or Maintenance > DS3 tabs.
Note The DS-3 Admin State is the basis of the DS-1 Derived State.
Step 6 c.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Delete the terminal loopback circuit: a.
b.
Click the Circuits tab.
Choose the loopback circuit being tested.
c.
Click Delete .
All tests for this circuit are completed.
1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical
Paths With FEAC Loopbacks
The DS3XM-6 card and DS3XM-12 cards support FEAC functions that are not available on basic DS-3 cards. Click the DS3XM-6 or DS3XM-12 Maintenance > DS1 tabs at the card view to reveal the two
additional function columns. Figure 1-19
shows the DS3 subtab and the additional Send Code and
Inhibit FE Lbk function columns.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-45
1.3.1 FEAC Send Code
Figure 1-19 Accessing FEAC Functions on the DS3XM-6 Card
Chapter 1 General Troubleshooting
The “far end” in FEAC refers to the equipment connected to the DS3XM card and not to the far end of
, if a DS3XM-6 (near-end) port is configured to send a line loop code, the code will be sent to the connected test set, not the DS3XM-6 (far-end) port.
Figure 1-20
Test Set
Diagram of FEAC Circuit
Node A
Tx
Rx
DS3XM
(Near End)
Tx
Rx
OC48
OC48
Ring
Rx
Tx
OC48
Node B
Tx
Rx
DS3XM
(Far End)
CPE
1.3.1 FEAC Send Code
The Send Code column on the DS3XM-6 or DS3XM-12 card Maintenance tab only applies to
OOS-MA,MT ports configured for CBIT framing. The column lets a user select No Code (the default) or line loop code. Selecting line loop code inserts a line loop activate FEAC in the CBIT overhead transmitting to the connected facility. This code initiates a loopback from the facility to the ONS 15454.
Selecting No Code sends a line-loop-deactivate FEAC code to the connected equipment, which will remove the loopback. You can also insert a FEAC for the 28 individual DS-1 circuits transmuxed into a
DS-3 circuit.
1-46
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.3.2 DS-3E and DS3i-N-12 Inhibit Loopback
1.3.2 DS-3E and DS3i-N-12 Inhibit Loopback
DS-3E and DS-3i-N-12 cards respond to (but do not send) DS-3-level FEAC codes. You can inhibit
FEAC response on ports for these cards using the Inhibit Lbk check box on their Maintenance windows.
1.3.3 DS3XM-6 and DS3XM-12 Inhibit FEAC Loopback
DS3XM-6 and DS3XM-12 ports and transmuxed DS-1 circuits initiate loopbacks when they receive
FEAC line loop codes. If the Inhibit FE Lbk check box is checked for a DS-3 port, that port ignores any
FEAC line loop codes it receives and will not loop back (return them). Only DS-3 ports can be configured to inhibit FEAC loopback responses; individual DS-1 ports (accessed on the DS3XM DS1 tab) cannot inhibit their responses. If you inhibit a DS-3 port’s far end loopback response, this DS-3 port and the DS-1 lines it contains are not restricted from terminal or facility loopbacks.
1.3.4 FEAC Alarms
When an ONS 15454 port receives an activation code for a FEAC loopback, it raises the
“LPBKDS1FEAC-CMD” condition on page 2-162
or the
“LPBKDS3FEAC” condition on page 2-162 .
The condition clears when the port receives the command to deactivate the FEAC loopback. If a node sends a FEAC loopback command to the far end, the sending node raises a
1.4 Troubleshooting Optical Circuit Paths With Loopbacks
Facility loopbacks, terminal loopbacks, and cross-connect loopback circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure.
The procedures in this section apply to OC-N cards. For instructions on G-Series Ethernet cards, see the
“1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks” section on page 1-68
. The example in this section tests an OC-N circuit on a three-node BLSR. Using a series of facility, cross-connect, and terminal loopbacks, the example scenario traces the circuit path, tests the possible failure points, and eliminates them. The logical progression contains seven network test procedures:
Note The test sequence for your circuits will differ according to the type of circuit and network topology.
5.
6.
7.
3.
4.
1.
2.
A facility loopback on the source-node OC-N port
A terminal loopback on the source-node OC-N port
A cross-connect loopback on the source OC-N port
A facility loopback on the intermediate-node OC-N port
A terminal loopback on the intermediate-node OC-N port
A facility loopback on the destination-node OC-N port
A terminal loopback on the destination-node OC-N port
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-47
Chapter 1 General Troubleshooting
1.4.1 Perform a Facility Loopback on a Source-Node Optical Port
Note Facility and terminal loopback tests require on-site personnel.
1.4.1 Perform a Facility Loopback on a Source-Node Optical Port
The facility loopback test is performed on the node source port in the network circuit. In the testing situation used in this example, the source OC-N port in the source node. Completing a successful facility loopback on this port isolates the OC-N port as a possible failure point.
shows an example of a facility loopback on a circuit source OC-N port.
Figure 1-21 Facility Loopback on a Circuit Source OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Complete the “Create the Facility Loopback on the Source Optical Port” procedure on page 1-48
.
Create the Facility Loopback on the Source Optical Port
Step 1 Connect an optical test set to the port you are testing.
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5
Use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port. Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, double-click the card to open the card view.
Click the Maintenance > Loopback > Port tabs.
Choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
1-48
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.1 Perform a Facility Loopback on a Source-Node Optical Port
Step 6
Step 7
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (OCN)” condition on page 2-167 or the
(G1000)” condition on page 2-166
to appear during loopback setup. The condition clears when you remove the loopback.
Step 8 Complete the
“Test and Clear the Facility Loopback Circuit” procedure on page 1-49 .
Test and Clear the Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback: a.
Click the Maintenance > Loopback > Port tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the OC-N Card” procedure on page 1-49
.
Test the OC-N Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback: a.
b.
c.
Click the Maintenance > Loopback > Port tabs.
Choose None from the Loopback Type column for the port being tested.
d.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-49
Chapter 1 General Troubleshooting
1.4.2 Perform a Terminal Loopback on a Source-Node Optical Port
Step 6 e.
Click Yes in the confirmation dialog box.
1.4.2 Perform a Terminal Loopback on a Source-Node Optical Port
The terminal loopback test is performed on the source-node optical port. For the circuit in this example, it is the source OC-N port in the source node. You first create a bidirectional circuit that starts on the node destination optical port and loops back on the node source optical port. You then proceed with the terminal loopback test. Completing a successful terminal loopback to a node source port verifies that the circuit is good to the source port.
shows an example of a terminal loopback on a source
OC-N port.
Figure 1-22 Terminal Loopback on a Source-Node OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set
OC-N cards in terminal loopback state display an icon in CTC, shown in
Figure 1-23 Terminal Loopback Indicator
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Complete the “Create the Terminal Loopback on a Source-Node Optical Port” procedure on page 1-50 .
Create the Terminal Loopback on a Source-Node Optical Port
Step 1 Connect an optical test set to the port you are testing:
1-50
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.2 Perform a Terminal Loopback on a Source-Node Optical Port
Step 2
Step 3
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
a.
b.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
c.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
d.
e.
h.
i.
f.
g.
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
OCN1toOCN2.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
Click Next .
k.
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Note It is normal for the
“LPBKTERMINAL (OCN)” condition on page 2-171 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 4 Create the terminal loopback on the destination port being tested: a.
In node view, double-click the card that requires the loopback, such as the destination OC-N card in the source node.
b.
c.
Click the Maintenance > Loopback > Port tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
d.
e.
f.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-51
Chapter 1 General Troubleshooting
1.4.2 Perform a Terminal Loopback on a Source-Node Optical Port
Step 5
Complete the “Test and Clear the Terminal Loopback Circuit” procedure on page 1-52
.
Test and Clear the Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5 a.
b.
c.
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback state on the port:
Double-click the card in the source node with the terminal loopback.
Click the Maintenance > Loopback > Port tabs.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
c.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
Click the Circuits tab.
b.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Optical Card” procedure on page 1-52 .
Test the Optical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port before testing the next segment of the network circuit path: a.
Double-click the card in the source node with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback > Port
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( the port being tested.
IS ; tabs.
OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for
1-52
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.3 Perform an XC Loopback on the Source Optical Port
Step 6
Step 7 e.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit before testing the next segment of the network circuit path: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.4.3 Perform an XC Loopback on the Source Optical Port” procedure on page 1-53 .
1.4.3 Perform an XC Loopback on the Source Optical Port
Note This procedure is only performed on OC-N cards and tests the cross-connect circuit connection.
Note You can perform an XC loopback on either the circuit source working or the protect port of a 1+1 protection group.
Note XC loopbacks do not require on-site personnel.
The XC loopback test occurs on the cross-connect card in a network circuit. Completing a successful XC loopback from an OC-N card through the cross-connect card eliminates the cross-connect card as the
source of trouble for a faulty circuit. Figure 1-24
shows an example of an XC loopback path on a source
OC-N port.
Figure 1-24
Test Set
XC Loopback on a Source OC-N Port
OC-Nx XC OC-Ny
Complete the
“Create the XC Loopback on the Source-Node Optical Port” procedure on page 1-53
.
Create the XC Loopback on the Source-Node Optical Port
Step 1 Connect an optical test set to the port you are testing:
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-53
Chapter 1 General Troubleshooting
1.4.3 Perform an XC Loopback on the Source Optical Port
Step 2
Step 3
Step 4
Step 5
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
a.
b.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to put the circuit being tested out of service: a.
b.
c.
In node view, click the Circuits tab.
Click the circuit and then click Edit .
In the Edit Circuit dialog box, click the State tab.
d.
e.
Choose OOS,MT from the Target Circuit Admin State drop-down list.
Click Apply .
Click Yes in the confirmation dialog box.
f.
Use CTC to set up the XC loopback on the circuit being tested: a.
In node view, double-click the OC-N card to open the card view.
b.
Click the Maintenance > Loopback > SONET STS tabs.
c.
d.
e.
Click the check box in the
Click Apply .
Click Yes
XC Loopback
in the confirmation dialog box.
column for the port being tested.
Complete the “Test and Clear the XC Loopback Circuit” procedure on page 1-54
.
Test and Clear the XC Loopback Circuit
Note This procedure is performed only on OC-N cards.
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
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.
If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the
XC loopback: a.
In card view, click the Maintenance > Loopback > SONET STS tabs.
b.
c.
d.
Uncheck the check box in the XC Loopback column for the circuit being tested.
Click Apply .
Click Yes in the confirmation dialog box.
1-54
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.3 Perform an XC Loopback on the Source Optical Port
Step 4 Complete the
“Test the Standby Cross-Connect Card” procedure on page 1-55
.
Test the Standby Cross-Connect Card
Note This procedure is performed only on cross-connect cards.
Step 1
Step 2
Perform a reset on the standby cross-connect card: a.
b.
c.
d.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
Position the cursor over the standby cross-connect card.
Right-click and choose RESET CARD .
Click Yes in the confirmation dialog box.
Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:
Caution Cross-connect side switches, with the exception of side switches using XC-VXC-10G cards, are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms. XC-VXC-10G side switches are errorless. b.
c.
d.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.
In the node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 3
Step 4
Resend test traffic on the loopback circuit.
The test traffic now travels through the alternate cross-connect card.
If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem. Clear the XC loopback circuit: a.
Click the Circuits tab.
b.
c.
d.
Choose the XC loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-55
Chapter 1 General Troubleshooting
1.4.3 Perform an XC Loopback on the Source Optical Port
Step 5 e.
Confirm that the XC loopback circuit is deleted from the Circuits tab list. If the test set indicates a good circuit, the problem might be a defective cross-connect card.
To confirm a defective original cross-connect card, complete the
“Retest the Original Cross-Connect
.
Retest the Original Cross-Connect Card
Note This procedure is performed only on OC-N and cross-connect cards.
Step 1 Initiate an external switching command (side switch) on the cross-connect cards.
a.
Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green. b.
c.
d.
In node view, select the Maintenance > Cross-Connect > Cards tabs.
In the Cross-Connect Cards area, click Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its
ACT/SBY LED turns amber.
Step 2
Step 3
Step 4
Step 5
Step 6
Resend test traffic on the loopback circuit.
If the test set indicates a faulty circuit, the problem is probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447 and proceed to
Step 4 . If the circuit is not shown to be faulty and the card is not shown to be defective, you
are finished with testing.
Complete the
“Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266 for the
defective card.
If the test set indicates a good circuit, the cross-connect card might have had a temporary problem that was cleared by the side switch. Clear the XC loopback circuit: a.
b.
c.
d.
Click the Circuits tab.
Choose the XC loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port” procedure on page 1-57 .
1-56
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port
1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port
Performing the facility loopback test on an intermediate port isolates whether this node is causing circuit failure. In the situation shown in
Figure 1-25 , the test is being performed on an intermediate OC-N port.
Figure 1-25 Facility Loopback Path to an Intermediate-Node OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Complete the
“Create a Facility Loopback on an Intermediate-Node Optical Port” procedure on page 1-57
.
Create a Facility Loopback on an Intermediate-Node Optical Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
If you are starting the current procedure without the optical test set hooked up to the source port port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the facility loopback on the test port: a.
In node view, click the Circuits tab and click Create .
b.
c.
d.
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
e.
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
OCN1toOCN3.
Leave the Bidirectional check box checked.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-57
Chapter 1 General Troubleshooting
1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port
Step 4 f.
g.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
h.
i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
Click Next .
j.
k.
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Note It is normal for the
“LPBKFACILITY (OCN)” condition on page 2-167 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the facility loopback on the destination port being tested: a.
Go to the node view of the intermediate node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
d.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the intermediate-node card that requires the loopback.
Click the Maintenance > Loopback > Port tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
e.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
f.
g.
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the Facility Loopback Circuit” procedure on page 1-58
.
Test and Clear the Facility Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
b.
Click the Maintenance > Loopback > Port tabs.
Choose None from the Loopback Type column for the port being tested.
c.
d.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
1-58
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
Step 4
Step 5 e.
b.
c.
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“Test the Optical Card” procedure on page 1-59
.
Test the Optical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback from the port: a.
b.
c.
Click the Maintenance > Loopback > Port tabs.
Choose None from the Loopback Type column for the port being tested.
d.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
e.
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
b.
c.
Click the Circuits tab.
Choose the loopback circuit being tested.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports” procedure on page 1-59
.
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
In the next troubleshooting test, you perform a terminal loopback on the intermediate-node port to isolate whether the destination port is causing circuit trouble. In the example situation in
terminal loopback is performed on an intermediate optical port in the circuit. You first create a
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-59
Chapter 1 General Troubleshooting
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
Figure 1-26 bidirectional circuit that originates on the source-node optical port and loops back on the intermediate-node port. You then proceed with the terminal loopback test. If you successfully complete a terminal loopback on the node, this node is excluded from possible sources of circuit trouble.
Terminal Loopback Path to an Intermediate-Node OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set
OC-N cards placed in facility loopback state display an icon, shown in
Figure 1-27 Facility Loopback Indicator
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Create a Terminal Loopback on Intermediate-Node Optical Ports
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
If you just completed the
“1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical
, leave the optical test set hooked up to the source-node port.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
1-60
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
Step 4 e.
f.
c.
d.
g.
h.
i.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
OCN1toOCN4.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears on the Circuits tab list and that it is described in the Dir column as a two-way circuit.
Note It is normal for the
“LPBKTERMINAL (OCN)” condition on page 2-171 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the intermediate node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback > Port tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the Optical Terminal Loopback Circuit” procedure on page 1-61
.
Test and Clear the Optical Terminal Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port: a.
Double-click the intermediate-node card with the terminal loopback to open the card view.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-61
Chapter 1 General Troubleshooting
1.4.5 Perform a Terminal Loopback on Intermediate-Node Optical Ports
Step 4
Step 5 b.
c.
d.
Click the Maintenance > Loopback > Port tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
c.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
Click the Circuits tab.
b.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Optical Card” procedure on page 1-62 .
Test the Optical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port: a.
b.
Double-click the source-node card with the terminal loopback.
Click the Maintenance > Loopback > Port tabs.
c.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
Click the Circuits tab.
b.
c.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
1-62
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.6 Perform a Facility Loopback on a Destination-Node Optical Port
1.4.6 Perform a Facility Loopback on a Destination-Node Optical Port
You perform a facility loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in
shows a facility loopback being performed on a destination-node OC-N port.
Figure 1-28 Facility Loopback Path to a Destination-Node OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC OC-N
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Complete the
“Create the Facility Loopback on a Destination-Node Optical Port” procedure on page 1-63
.
Create the Facility Loopback on a Destination-Node Optical Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the hairpin circuit on the test port: a.
In node view, click the Circuits tab and click Create .
b.
c.
d.
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
OCN1toOCN5.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-63
Chapter 1 General Troubleshooting
1.4.6 Perform a Facility Loopback on a Destination-Node Optical Port
Step 4 e.
f.
g.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
h.
i.
Click Next .
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Finish .
Note It is normal for the
“LPBKFACILITY (OCN)” condition on page 2-167 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the facility loopback on the destination port being tested: a.
Go to the node view of the destination node: b.
c.
d.
•
•
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
In node view, double-click the card that requires the loopback.
OK .
Click the Maintenance > Loopback > Port tabs.
e.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
f.
g.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the Optical Facility Loopback Circuit” procedure on page 1-64
.
Test and Clear the Optical Facility Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
Click the Maintenance > Loopback > Port tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
1-64
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port
Step 4
Step 5 d.
Click Apply .
e.
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“Test the Optical Card” procedure on page 1-65
.
Test the Optical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback on the port: a.
Click the Maintenance > Loopback > Port tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
d.
e.
c.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
Click the Circuits tab.
b.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port” procedure on page 1-65
.
1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port
The terminal loopback at the destination-node port is the final local hardware error elimination in the circuit troubleshooting process. If this test is completed successfully, you have verified that the circuit is good up to the destination port. The example in
Figure 1-29 shows a terminal loopback on an
intermediate-node destination OC-N port.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-65
Chapter 1 General Troubleshooting
1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port
Figure 1-29 Terminal Loopback Path to a Destination-Node OC-N Port
OC-N
Source
ONS Node
XC OC-N OC-N
Intermediate
ONS Node
XC OC-N
Test Set
OC-N
Destination
ONS Node
XC OC-N
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Create the Terminal Loopback on a Destination-Node Optical Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
d.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
OCN1toOCN6.
e.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
f.
g.
h.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
1-66
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.4.7 Perform a Terminal Loopback on a Destination-Node Optical Port
Step 4 i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Finish .
Note It is normal for the
“LPBKTERMINAL (OCN)” condition on page 2-171 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback > Port tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the Optical Terminal Loopback Circuit” procedure on page 1-67
.
Test and Clear the Optical Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port: a.
Double-click the intermediate-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback > Port tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
Click the Circuits tab.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-67
Chapter 1 General Troubleshooting
1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks
Step 5
Step 6 b.
c.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
d.
The entire 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, the problem might be a faulty card.
Complete the “Test the Optical Card” procedure on page 1-68 .
Test the Optical Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good card.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port: a.
Double-click the source-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback > Port tabs.
Select None from the Loopback Type column for the port being tested.
e.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
b.
c.
Click the Circuits tab.
Choose the loopback circuit being tested.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks
Facility loopbacks, terminal loopbacks, and cross-connect loopback circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure.
1-68
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.1 Perform a Facility Loopback on a Source-Node Ethernet Port
You can use these procedures on G-Series and CE-Series Ethernet cards but not on E-Series or
ML-Series Ethernet cards. The example in this section tests a G-Series card circuit on a three-node
BLSR. Using a series of facility loopbacks and terminal loopbacks, the example scenario traces the circuit path, tests the possible failure points, and eliminates them. The logical progression contains six network test procedures:
Note The test sequence for your circuits will differ according to the type of circuit and network topology.
3.
4.
1.
2.
5.
6.
A facility loopback on the source-node Ethernet port
A terminal loopback on the source-node Ethernet port
A facility loopback on the intermediate-node Ethernet port
A terminal loopback on the intermediate-node Ethernet port
A facility loopback on the destination-node Ethernet port
A terminal loopback on the destination-node Ethernet port
Note Facility and terminal loopback tests require on-site personnel.
1.5.1 Perform a Facility Loopback on a Source-Node Ethernet Port
The facility loopback test is performed on the node source port in the network circuit. In the testing situation used in this example, the source G-Series port in the source node. Completing a successful facility loopback on this port isolates the G-Series port as a possible failure point.
shows an example of a facility loopback on a circuit source Ethernet port.
Note Facility loopbacks are not available for Release 4.1 or earlier G-Series cards.
Note Facility loopbacks require on-site personnel.
Figure 1-30 Facility Loopback on a Circuit Source Ethernet Port
Ethernet
Source
ONS Node
XC
Ethernet Ethernet
Intermediate
ONS Node
XC
Ethernet
Test Set
Ethernet
Destination
ONS Node
XC
Ethernet
Caution Performing a loopback on an in-service circuit is service-affecting.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-69
Chapter 1 General Troubleshooting
1.5.1 Perform a Facility Loopback on a Source-Node Ethernet Port
Create the Facility Loopback on the Source-Node Ethernet Port
Step 1 Connect an optical test set to the port you are testing.
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, double-click the card to open the card view.
Click the Maintenance > Loopback tabs.
Choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (G1000)” condition on page 2-166 to appear during
loopback setup. The condition clears when you remove the loopback.
Step 9
Complete the “Test and Clear the Facility Loopback Circuit” procedure on page 1-70
.
Test and Clear the Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback: a.
Click the Maintenance > Loopback tabs.
d.
e.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test the Ethernet Card” procedure on page 1-71 .
1-70
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback: a.
b.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
c.
d.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
Click Apply .
e.
Click Yes in the confirmation dialog box.
Complete the
“1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port” procedure on page 1-71
.
1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port
The terminal loopback test is performed on the node source Ethernet port. For the circuit in this example, it is the source G-Series port in the source node. You first create a bidirectional circuit that starts on the node destination G-Series port and loops back on the node source G-Series port. You then proceed with the terminal loopback test. Completing a successful terminal loopback to a node source port verifies that the circuit is good to the source port.
shows terminal loopback on a G-Series port.
Note Terminal loopbacks are not available for R4.0 and earlier G-Series cards.
Note Terminal loopbacks require on-site personnel.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-71
Chapter 1 General Troubleshooting
1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port
Figure 1-31 Terminal Loopback on a G-Series Port
4 ports
GigE
Processor Subsystem
GBIC 1
GBIC 2
GBIC 3
GBIC 4
SERDES
SERDES
SERDES
SERDES
GigE
MAC
GigE
MAC
GigE
MAC
GigE
MAC
Terminal
Loopback
FPGA
Block
Facility
Loopback
Path
Termination
Block
BTC
192
Protect
RX BPIA
Protect
TX BPIA
BACKPLANE
Main
RX BPIA
Main
TX BPIA
STS48
Caution Performing a loopback on an in-service circuit is service-affecting.
Complete the “Create the Terminal Loopback on a Source-Node Ethernet Port” procedure on page 1-72
.
Create the Terminal Loopback on a Source-Node Ethernet Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
If you just completed the
“1.5.1 Perform a Facility Loopback on a Source-Node Ethernet Port” procedure on page 1-69
, leave the optical test set hooked up to the Ethernet port in the source node.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
c.
In node view, click the
Click Next .
Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
1-72
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.2 Perform a Terminal Loopback on a Source-Node Ethernet Port
Step 4 d.
e.
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
G1K1toG1K2.
Leave the Bidirectional check box checked.
Click Next .
f.
g.
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
h.
i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
Click Next .
j.
k.
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Note It is normal for the
“LPBKTERMINAL (G1000)” condition on page 2-170
to appear during a loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the terminal loopback on the destination port being tested: a.
b.
c.
In node view, double-click the card that requires the loopback, such as the destination G-Series card in the source node.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
d.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the Ethernet Terminal Loopback Circuit” procedure on page 1-73
.
Test and Clear the Ethernet Terminal Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback state on the port: a.
Double-click the card in the source node with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-73
Chapter 1 General Troubleshooting
1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port
Step 4
Step 5 e.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
b.
c.
d.
Click the Circuits tab.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Ethernet Card” procedure on page 1-74 .
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port before testing the next segment of the network circuit path: a.
Double-click the card in the source node with the terminal loopback.
b.
c.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
d.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit before testing the next segment of the network circuit path: a.
b.
Click the Circuits tab.
Choose the loopback circuit being tested.
c.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port” procedure on page 1-74 .
1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port
Performing the facility loopback test on an intermediate port isolates whether this node is causing circuit failure. It is shown in
.
1-74
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port
Figure 1-32 Hairpin on a Source-Node Ethernet Port
CE-MR-10
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC CE-MR-10
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Complete the
“Create a Facility Loopback on an Intermediate-Node Ethernet Port” procedure on page 1-75
.
Create a Facility Loopback on an Intermediate-Node Ethernet Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the facility loopback on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
d.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
G1KtoG1K3.
e.
If you are starting the current procedure without the optical test set hooked up to the source port port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
f.
g.
h.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-75
Chapter 1 General Troubleshooting
1.5.3 Create a Facility Loopback on an Intermediate-Node Ethernet Port
Step 4 i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Finish .
Note It is normal for the
“LPBKFACILITY (G1000)” condition on page 2-166 or the
“LPBKFACILITY (OCN)” condition on page 2-167
to appear during a loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the facility loopback on the destination port being tested: a.
Go to the node view of the intermediate node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the intermediate-node card that requires the loopback.
Click the Maintenance > Loopback tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the Ethernet Facility Loopback Circuit” procedure on page 1-76
.
Test and Clear the Ethernet Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
Click the Maintenance > Loopback tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
Click the Circuits tab.
1-76
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports
Step 5 b.
c.
d.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“Test the Ethernet Card” procedure on page 1-77
.
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback from the port: a.
Click the Maintenance > Loopback tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
Click the Circuits tab.
b.
c.
Choose the loopback circuit being tested.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports” procedure on page 1-77
.
1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports
In the next troubleshooting test, you perform a terminal loopback on the intermediate-node port to isolate whether the destination port is causing circuit trouble. In the example situation in
terminal loopback is performed on an intermediate Ethernet port in the circuit. You first create a bidirectional circuit that originates on the source-node Ethernet port and loops back on the intermediate-node port. You then proceed with the terminal loopback test. If you successfully complete a terminal loopback on the node, this node is excluded from possible sources of circuit trouble.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-77
Chapter 1 General Troubleshooting
1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports
Figure 1-33 Facility Loopback on an Intermediate-Node Ethernet Port
Ethernet
Source
ONS Node
XC Ethernet
Intermediate
Ethernet
ONS Node
XC Ethernet
Test Set
Ethernet
Destination
ONS Node
XC Ethernet
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Create a Terminal Loopback on Intermediate-Node Ethernet Ports
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
d.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
G1K1toG1K4.
e.
If you just completed the
intermediate-node port.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
f.
g.
h.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-78 November 2009
Chapter 1 General Troubleshooting
1.5.4 Create a Terminal Loopback on Intermediate-Node Ethernet Ports
Step 4 i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish .
Confirm that the newly created circuit appears on the Circuits tab list and that it is described in the Dir column as a two-way circuit.
Note It is normal for the
“LPBKTERMINAL (G1000)” condition on page 2-170
to appear during a loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the intermediate node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the Ethernet Terminal Loopback Circuit” procedure on page 1-79
.
Test and Clear the Ethernet Terminal Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port: a.
Double-click the intermediate-node card with the terminal loopback to open the card view.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
e.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
Click Apply .
f.
Click Yes in the confirmation dialog box.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-79
Chapter 1 General Troubleshooting
1.5.5 Perform a Facility Loopback on a Destination-Node Ethernet Port
Step 4
Step 5
Clear the terminal loopback circuit: a.
b.
c.
d.
Click the
Choose the loopback circuit being tested.
Click
Circuits
Delete .
tab.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the “Test the Ethernet Card” procedure on page 1-80 .
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port: a.
Double-click the source-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
e.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
b.
c.
Click the Circuits tab.
Choose the loopback circuit being tested.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
1.5.5 Perform a Facility Loopback on a Destination-Node Ethernet Port
You perform a facility loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in
shows a facility loopback being performed on an
Ethernet port.
1-80
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.5 Perform a Facility Loopback on a Destination-Node Ethernet Port
Figure 1-34 Terminal Loopback on an Intermediate-Node Ethernet Port
Ethernet
Source
ONS Node
XC Ethernet
Intermediate
Ethernet
ONS Node
XC Ethernet
Test Set
Ethernet
Destination
ONS Node
XC Ethernet
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Complete the
“Create the Facility Loopback on a Destination-Node Ethernet Port” procedure on page 1-81
.
Create the Facility Loopback on a Destination-Node Ethernet Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the hairpin circuit on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
d.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
G1K1toG1K5.
e.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
f.
g.
h.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-81
Chapter 1 General Troubleshooting
1.5.5 Perform a Facility Loopback on a Destination-Node Ethernet Port
Step 4 i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Finish .
Note It is normal for the
“LPBKFACILITY (G1000)” condition on page 2-166 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the facility loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the Ethernet Facility Loopback Circuit” procedure on page 1-82
.
Test and Clear the Ethernet Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
Click the Maintenance > Loopback tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
Click the Circuits tab.
b.
Choose the loopback circuit being tested.
1-82
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port
Step 5 c.
Click Delete . d.
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“Test the Ethernet Card” procedure on page 1-83
.
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback on the port: a.
b.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
c.
Choose the appropriate state (IS; OOS,DSBLD; OOS,MT) from the Admin State column for the port being tested.
Click Apply .
d.
e.
Click Yes in the confirmation dialog box.
Clear the facility loopback circuit: a.
b.
Click the Circuits tab.
Choose the loopback circuit being tested.
c.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
Complete the
“1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port” procedure on page 1-83
.
1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port
The terminal loopback at the destination-node port is the final local hardware error elimination in the circuit troubleshooting process. If this test is completed successfully, you have verified that the circuit is good up to the destination port. The example in
Figure 1-29 shows a terminal loopback on an
intermediate-node destination Ethernet port.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-83
Chapter 1 General Troubleshooting
1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port
Figure 1-35 Facility Loopback on a Destination-Node Ethernet Port
Ethenet
Source
ONS Node
XC Ethernet
Intermediate
Ethernet
ONS Node
XC Ethernet
Test Set
Ethernet
Destination
ONS Node
XC Ethernet
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Create the Terminal Loopback on a Destination-Node Ethernet Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Use CTC to set up the terminal loopback on the test port: a.
b.
c.
In node view, click the Circuits tab and click Create .
In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.
d.
Click Next .
In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as
G1K1toG1K6.
e.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
f.
g.
h.
Leave the Bidirectional check box checked.
Click Next .
In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.
Click Next .
1-84
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.5.6 Perform a Terminal Loopback on a Destination-Node Ethernet Port
Step 4 i.
In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box.
j.
k.
Click Next .
In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Finish .
Note It is normal for the
“LPBKTERMINAL (G1000)” condition on page 2-170
to appear during a loopback setup. The condition clears when you remove the loopback.
Step 5
Step 6
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the destination node:
• Choose View > Go To Other Node from the menu bar.
b.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
c.
d.
e.
f.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the Ethernet Terminal Loopback Circuit” procedure on page 1-85
.
Test and Clear the Ethernet Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port: a.
Double-click the intermediate-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
Click the Circuits tab.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-85
Chapter 1 General Troubleshooting
1.6 Troubleshooting FC_MR Circuit Paths With Loopbacks
Step 5
Step 6 b.
c.
Choose the loopback circuit being tested.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
d.
The entire 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, the problem might be a faulty card.
Complete the “Test the Ethernet Card” procedure on page 1-86 .
Test the Ethernet Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good card.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port: a.
Double-click the source-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
e.
Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Clear the terminal loopback circuit: a.
b.
c.
Click the Circuits tab.
Choose the loopback circuit being tested.
d.
Click Delete .
Click Yes in the Delete Circuits dialog box. Do not check any check boxes.
The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
1.6 Troubleshooting FC_MR Circuit Paths With Loopbacks
Facility loopbacks, terminal loopbacks, and cross-connect loopback circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure. FC_MR loopback tests
1-86
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.1 Perform a Facility Loopback on a Source-Node FC_MR Port differ from electrical, optical, and Ethernet testing because loopback testing does not require circuit creation. FC_MR client ports are statically mapped to the trunk ports so no signal needs to traverse the cross-connect card (in a circuit) to test the loopback.
You can use these procedures on fibre channel data storage (FC_MR) cards. The example in this section tests an FC_MR circuit on a three-node BLSR. Using a series of facility loopbacks and terminal loopbacks, the example scenario traces the circuit path, tests the possible failure points, and eliminates them. The logical progression contains seven network test procedures:
Note FC_MR card client ports do not appear in the Maintenance > Loopback tabs unless they have been provisioned. Provision ports in the card view Provisioning > Pluggable Port Modules tab. For information about provisioning client ports, refer to the Cisco ONS 15454 Procedure Guide .
Note The test sequence for your circuits will differ according to the type of circuit and network topology.
3.
4.
1.
2.
A facility loopback on the source-node FC_MR port
A terminal loopback on the source-node FC_MR port
A facility loopback on the destination-node FC_MR port
A terminal loopback on the destination-node FC_MR port
Note Facility, hairpin, and terminal loopback tests require on-site personnel.
1.6.1 Perform a Facility Loopback on a Source-Node FC_MR Port
The facility loopback test is performed on the node source port in the network circuit. In the testing situation used in this example, the source muxponder or transponder port in the source node. Completing a successful facility loopback on this port isolates the FC_MR port as a possible failure point.
Figure 1-38 shows an example of a facility loopback on a circuit source FC_MR port.
Figure 1-36 Terminal Loopback on a Destination-Node Ethernet Port
Ethernet
Source
ONS Node
XC Ethernet
Intermediate
Ethernet
ONS Node
XC Ethernet Ethernet
Destination
ONS Node
XC Ethernet
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-87
Chapter 1 General Troubleshooting
1.6.1 Perform a Facility Loopback on a Source-Node FC_MR Port
Complete the
“Create the Facility Loopback on the Source-Node FC_MR Port” procedure on page 1-88
.
Create the Facility Loopback on the Source-Node FC_MR Port
Step 1 Connect an optical test set to the port you are testing.
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. The Tx and Rx terminals connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In CTC node view, double-click the card to open the card view.
Click the Maintenance > Loopback tabs.
Choose OOS,MT from the Admin State column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
Choose Facility from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
Note It is normal for the
“LPBKFACILITY (OCN)” condition on page 2-167
or the
(G1000)” condition on page 2-166 to appear during loopback setup. The condition clears when
you remove the loopback.
Step 9
Complete the “Test and Clear the FC_MR Facility Loopback Circuit” procedure on page 1-88 .
Test and Clear the FC_MR Facility Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback: a.
Click the Maintenance > Loopback tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
d.
e.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
1-88
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.2 Perform a Terminal Loopback on a Source-Node FC_MR Port
Step 4 Complete the
“Test the FC_MR Card” procedure on page 1-89 .
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback: a.
b.
c.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
d.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
e.
Click Yes in the confirmation dialog box.
Complete the
“1.6.2 Perform a Terminal Loopback on a Source-Node FC_MR Port” procedure on page 1-89
.
1.6.2 Perform a Terminal Loopback on a Source-Node FC_MR Port
The terminal loopback test is performed on the node source FC_MR muxponder or transponder port. For the circuit in this example, the test port is the source FC_MR port in the source node. Completing a successful terminal loopback to a node source port verifies that the circuit is good to the source port.
Figure 1-39 shows an example of a terminal loopback on a source FC_MR port.
Figure 1-37 Hairpin on a Destination-Node Ethernet Port
CE-MR-10
Destination
ONS Node
XC OC-N OC-N
Source
ONS Node
XC CE-MR-10
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-89
Chapter 1 General Troubleshooting
1.6.2 Perform a Terminal Loopback on a Source-Node FC_MR Port
Note Terminal loopbacks require on-site personnel.
Complete the
“Create the Terminal Loopback on a Source-Node FC_MR Port” procedure on page 1-90
.
Create the Terminal Loopback on a Source-Node FC_MR Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 a.
b.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In node view, double-click the card that requires the loopback, such as the destination OC-N card in the source node.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the FC_MR Port Terminal Loopback Circuit” procedure on page 1-90
.
Test and Clear the FC_MR Port Terminal Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback state on the port: a.
b.
Double-click the card in the source node with the terminal loopback.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-90 November 2009
Chapter 1 General Troubleshooting
1.6.3 Create a Facility Loopback on an Intermediate-Node FC_MR Port
Step 4 e.
Click Apply .
f.
Click Yes in the confirmation dialog box.
Complete the
“Test the FC_MR Card” procedure on page 1-91 .
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the defective card.
Clear the terminal loopback on the port before testing the next segment of the network circuit path: a.
b.
Double-click the card in the source node with the terminal loopback.
Click the Maintenance > Loopback tabs.
c.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“1.6.3 Create a Facility Loopback on an Intermediate-Node FC_MR Port” procedure on page 1-91
.
1.6.3 Create a Facility Loopback on an Intermediate-Node FC_MR Port
Performing the facility loopback test on an intermediate port determines whether this node is causing
circuit failure. In the example shown in Figure 1-40
, the test is being performed on an intermediate
FC_MR port.
Figure 1-38 Facility Loopback on a Circuit Source FC_MR Port
FC_MR
Source
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC FC_MR
Test Set
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-91
Chapter 1 General Troubleshooting
1.6.3 Create a Facility Loopback on an Intermediate-Node FC_MR Port
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Create a Facility Loopback on an Intermediate-Node FC_MR Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 a.
b.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
In node view, double-click the intermediate-node card that requires the loopback.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the “Test and Clear the FC_MR Port Facility Loopback Circuit” procedure on page 1-92 .
Test and Clear the FC_MR Port Facility Loopback Circuit
Step 1
Step 2
Step 3
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
b.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
1-92
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports
Step 4 c.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test the FC_MR Card” procedure on page 1-93 .
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback from the port: a.
Click the Maintenance > Loopback tabs.
b.
c.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports” procedure on page 1-93
.
1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports
In the next troubleshooting test, you perform a terminal loopback on the intermediate-node port to isolate whether the destination port is causing circuit trouble. In the example situation in
terminal loopback is performed on an intermediate FC_MR port in the circuit. If you successfully complete a terminal loopback on the node, this node is excluded from possible sources of circuit trouble.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-93
Chapter 1 General Troubleshooting
1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports
Figure 1-39 Terminal Loopback on a Source-Node FC_MR Port
Source
ONS Node
FC_MR XC OC-N OC-N
Intermediate
ONS Node
XC OC-N
Test Set
OC-N
Destination
ONS Node
XC FC_MR
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Complete the “Create a Terminal Loopback on Intermediate-Node FC_MR Ports” procedure on page 1-94 .
Create a Terminal Loopback on Intermediate-Node FC_MR Ports
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
b.
If you just completed the
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Create the terminal loopback on the destination port being tested: a.
Go to the node view of the intermediate node:
• Choose View > Go To Other Node from the menu bar.
b.
c.
d.
e.
f.
• Choose the node from the drop-down list in the Select Node dialog box and click OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
1-94
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.4 Create a Terminal Loopback on Intermediate-Node FC_MR Ports
Step 4 g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the FC_MR Terminal Loopback Circuit” procedure on page 1-95 .
Test and Clear the FC_MR Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port: a.
Double-click the intermediate-node card with the terminal loopback to open the card view.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
e.
f.
Click Yes in the confirmation dialog box.
Complete the
“Test the FC_MR Card” procedure on page 1-95 .
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the defective card.
Clear the terminal loopback on the port: a.
Double-click the source-node card with the terminal loopback.
b.
c.
d.
Click the Maintenance > Loopback tabs.
Select None from the Loopback Type column for the port being tested.
e.
f.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
Click Apply .
Click Yes in the confirmation dialog box.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-95
Chapter 1 General Troubleshooting
1.6.5 Perform a Facility Loopback on a Destination-Node FC_MR Port
Step 6
1.6.5 Perform a Facility Loopback on a Destination-Node FC_MR Port
You perform a facility loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in
shows a facility loopback being performed on an
FC_MR port.
Figure 1-40 Facility Loopback on an Intermediate-Node FC_MR Port
Source
ONS Node
FC_MR XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC FC_MR
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Facility loopbacks require on-site personnel.
Create the Facility Loopback on a Destination-Node FC_MR Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
Step 2
Step 3 a.
If you just completed the
b.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Create the facility loopback on the destination port being tested: a.
Go to the node view of the destination node:
1-96
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.5 Perform a Facility Loopback on a Destination-Node FC_MR Port
Step 4 b.
c.
d.
• 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 OK .
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
e.
Select Facility from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
f.
g.
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the FC_MR Facility Loopback Circuit” procedure on page 1-97
.
Test and Clear the FC_MR Facility Loopback Circuit
Step 1
Step 2
Step 3
Step 4
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility loopback from the port: a.
b.
c.
Click the Maintenance > Loopback tabs.
Choose None from the Loopback Type column for the port being tested.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
Click Apply .
d.
e.
Click Yes in the confirmation dialog box.
Complete the
“Test the FC_MR Card” procedure on page 1-97 .
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the suspected bad card and replace it with a known-good one.
Resend test traffic on the loopback circuit with a known-good card installed.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the faulty card.
Clear the facility loopback on the port: a.
Click the Maintenance > Loopback tabs.
b.
Choose None from the Loopback Type column for the port being tested.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-97
Chapter 1 General Troubleshooting
1.6.6 Perform a Terminal Loopback on a Destination-Node FC_MR Port
Step 6 c.
Choose the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) from the Admin State column for the port being tested.
d.
e.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“1.6.6 Perform a Terminal Loopback on a Destination-Node FC_MR Port” procedure on page 1-98 .
1.6.6 Perform a Terminal Loopback on a Destination-Node FC_MR Port
The terminal loopback at the destination-node port is the final local hardware error elimination in the circuit troubleshooting process. If this test is completed successfully, you have verified that the circuit
is good up to the destination port. The example in Figure 1-41
shows a terminal loopback on an intermediate-node destination FC_MR port.
Figure 1-41 Terminal Loopback on an Intermediate-Node FC_MR Port
Source
ONS Node
FC_MR XC OC-N OC-N
Intermediate
ONS Node
XC OC-N OC-N
Destination
ONS Node
XC FC_MR
Test Set
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Terminal loopbacks require on-site personnel.
Create the Terminal Loopback on a Destination-Node FC_MR Port
Step 1 Connect an optical test set to the port you are testing:
Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.
a.
1-98
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.6.6 Perform a Terminal Loopback on a Destination-Node FC_MR Port
Step 2
Step 3 b.
If you are starting the current procedure without the optical test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing. Both Tx and Rx connect to the same port.
Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)
Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.
Note It is normal for the
“LPBKTERMINAL (OCN)” condition on page 2-171 to appear during a
loopback setup. The condition clears when you remove the loopback.
Step 4
Step 5
Create the terminal loopback on the destination port being tested: a.
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 OK .
b.
c.
d.
In node view, double-click the card that requires the loopback.
Click the Maintenance > Loopback tabs.
Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.
e.
f.
g.
Select Terminal from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
Click Apply .
Click Yes in the confirmation dialog box.
Complete the
“Test and Clear the FC_MR Terminal Loopback Circuit” procedure on page 1-99 .
Test and Clear the FC_MR Terminal Loopback Circuit
Step 1
Step 2
Step 3
Step 4 a.
b.
c.
If the test set is not already sending traffic, send test traffic on the loopback circuit.
Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port:
Double-click the intermediate-node card with the terminal loopback.
Click the Maintenance > Loopback tabs.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
If the test set indicates a faulty circuit, the problem might be a faulty card.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-99
1.7 Using CTC Diagnostics
Step 5
Complete the “Test the FC_MR Card” procedure on page 1-100
.
Chapter 1 General Troubleshooting
Test the FC_MR Card
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the suspected bad card
and replace it with a known-good card.
Resend test traffic on the loopback circuit with a known-good card.
If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support at 1 800 553-2447.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the defective card.
Clear the terminal loopback on the port: a.
b.
c.
Double-click the source-node card with the terminal loopback.
Click the Maintenance > Loopback tabs.
d.
Select None from the Loopback Type column for the port being tested.
Select the appropriate state ( IS ; OOS,DSBLD ; OOS,MT ; IS,AINS ) in the Admin State column for the port being tested.
e.
f.
Click Apply .
Click Yes in the confirmation dialog box.
The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
1.7 Using CTC Diagnostics
CTC provides diagnostics for the following functions:
• Verifying proper card ASICS function
•
•
Verifying standby card operation
Verifying proper card LED operation
•
•
Diagnostic circuit creation
Customer problem notifications detected via alarms
• Provision of a downloadable, machine-readable diagnostic information file to be used by Cisco
Technical Support.
Some of these functions, such as ASIC verification and standby card operation, are invisibly monitored in background functions. Change or problem notifications are provided in the Alarms and Conditions window. Other diagnostic functions—verifying card LED function, creating bidirectional diagnostic circuits, and also downloading diagnostic files for technical support—are available to the user in the node view Maintenance > Diagnostic tabs. The user-operated diagnostic features are described in the following paragraphs.
1-100
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.7.1 Card LED Lamp Tests
1.7.1 Card LED Lamp Tests
A card LED lamp test determines whether card-level indication LEDs are operational. This diagnostic test is run as part of the initial ONS 15454 turn-up, during maintenance routines, or any time you question whether an LED is in working order. Maintenance or higher-level users can complete the following tasks to verify LED operation.
Verify General Card LED Operation
Step 1 In node view, click the Maintenance > Diagnostic tabs (
Figure 1-42 CTC Node View Diagnostic Window
Step 2
Step 3
Step 4
Click Lamp Test .
Watch to make sure all the port LEDs illuminate simultaneously for several seconds, with the following durations:
•
•
For tri-color LEDs: three 5-second cycles
For dual-color LEDs: one 5-second cycle and one 10-second cycle
• For the AIC or AIC-I: one 15-second cycle
Click OK in the Lamp Test Run dialog box.
With the exceptions previously described, if an OC-N or DS-N LED does not light up, the LED is faulty.
Return the defective card to Cisco through the RMA process. Contact the Cisco Technical Assistance
Center (TAC) at 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-101
Chapter 1 General Troubleshooting
1.7.1 Card LED Lamp Tests
Verify G-Series Ethernet or FC_MR Card Port-Level LED Operation
Note G-Series and FC_MR card-level LEDs illuminate during a lamp test, but the port-level LEDs do not.
Step 1
Step 2
Step 3
Complete the “Verify General Card LED Operation” procedure on page 1-101 to verify that card-level
LEDs are operational.
Use the following list of guidelines to physically test whether the G-Series Ethernet port LEDs are operating correctly. If the LED appears as described when the listed state is occurring for the port, the
LED is considered to be functioning correctly.
• Clear port LED: Should only occur if there is a loss of receive link (such as a disconnected link or unplugged Gigabit Interface Converter, [GBIC]). An LOS alarm could be present on the port.
•
•
Amber port LED: Should only occur if a port is disabled but the link is connected, or if the port is enabled and the link is connected but a transport failure is present. A TPTFAIL alarm can be present on the port.
Green port LED: Should occur if the port is enabled and has no errors against it or traffic in it. Can also occur if the port is enabled, has no errors, and is running traffic proportionate to the blink rate.
No traffic-affecting port alarms should be present.
If you are unable to determine the port state, contact Cisco Technical Support at 1 800 553-2447.
Verify E-Series and ML-Series Ethernet Card Port-Level LED Operation
Note E-Series and ML-Series card-level LEDs illuminate during a lamp test, but the port-level LEDs do not.
Note For information about the ML-Series card, refer to the Ethernet Card Software Feature and Configuration
Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Step 1
Step 2
Step 3
Complete the “Verify General Card LED Operation” procedure on page 1-101 to verify that card-level
LEDs are operational.
Use the following list of guidelines to physically test whether the single E-Series or ML-Series Ethernet port LED is operating correctly. If the LED appears as described when the listed state is occurring for the port, the LED is considered to be functioning correctly.
• Clear port LED: Should only occur if there is a loss of receive link (such as a disconnected link or unplugged GBIC), or if traffic is flowing in one direction (either transmit or receive). A CARLOSS alarm could be present on the port.
•
•
Amber port LED: Should only occur if the link is connected and the physical port is transmitting and receiving traffic.
Green port LED: Should occur if the link is up and no traffic is flowing on the port.
If you are unable to determine the port state, contact Cisco Technical Support at 1 800 553-2447.
1-102
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.7.2 Retrieve Diagnostics File Button
1.7.2 Retrieve Diagnostics File Button
When you click the Retrieve Diagnostics File button in the Maintenance window, CTC retrieves system data that can be off-loaded by a Maintenance or higher-level user to a local directory and sent to
Technical Support for troubleshooting purposes. The diagnostics file is in machine language and is not human-readable, but can be used by Cisco Technical Support for problem analysis. Complete the following task to off-load the diagnostics file.
Note In addition to the machine-readable diagnostics file, the ONS 15454 also stores an audit trail of all system events such as user logins, remote logins, configuration, and changes. This audit trail is considered a record-keeping feature rather than a troubleshooting feature. Information about the feature is located in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide .
Off-Load the Diagnostics File
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In the node view, click the Maintenance > Diagnostic tabs (
).
Click Retrieve Tech Support Log .
In the Saving Diagnostic File dialog box, navigate to the directory (local or network) where you want to save the file.
Enter a name in the File Name field.
You do not have to give the archive file a particular extension. It is a compressed file (gzip) that can be unzipped and read by Cisco Technical Support.
Click Save .
The Get Diagnostics status window shows a progress bar indicating the percentage of the file being saved, then shows “Get Diagnostics Complete.”
Click OK .
1.7.3 Bidirectional Diagnostic Circuit
CTC provides a diagnostic bidirectional loopback circuit feature that uses pseudo-random bit sequence
(PRBS) error detection to monitor standby path protection, BLSR, 1+1, or unprotected circuit path readiness.
The diagnostic circuit is bidirectional and uses a single VT 1.5 in an STS. The circuit can traverse multiple nodes, but it must be carried by the same STS for the entire path. The circuit originates and ultimately destinates on the same node, but can be looped (by a hairpin circuit) through other nodes.
After the circuit returns to the originating node, the signal result is detected and analyzed for errors by
PRBS.
This type of circuit is created much the same way as a normal standby protection channel access (PCA) circuit, but is designated by checking the Diagnostic check box during circuit creation. A normal circuit uses line cards as the endpoints, but if a circuit is configured as a diagnostic, the endpoints are cross-connect cards.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-103
Chapter 1 General Troubleshooting
1.7.3 Bidirectional Diagnostic Circuit
Each card type utilizes the diagnostic feature differently. Standby electrical cards run PRBS tests to ensure signal path integrity. Optical cards do not run PRBS tests, but instead run ASIC tests to test card operability. Cross-connect cards verify the standby paths.
The diagnostic circuit can be configured for an end-to-end or multiple-node path layout, traversing the transmit and receive standby paths as shown in
Figure 1-43 CTC Node View Diagnostic Window
Node C
Node B Node D
PRBS
Detector
PRBS
Generator
Node A
Node E
Node H Node F
Node G
VT PRBS signal that tests all spans on the BLSR ring.
VT PRBS signal that tests only one span on the BLSR ring.
NOTE: The end without the arrow is where the PRBS pattern is generated.
The end with the arrow is the end where the PRBS pattern is detected.
The maximum diagnostic circuit size is VT1.5, and the maximum quantity of available diagnostic circuits is one per node. (In other words, if you create a diagnostic VT within an STS, the remaining 27
VTs can still be provisioned, and they may also contain diagnostic circuits originating on other nodes.)
As with all bidirectional circuits, a diagnostic circuit can only be created if the same STS is available on each span the circuit traverses. When you use a bidirectional diagnostic that traverses one or more intermediate nodes, create or utilize an existing bidirectional circuit on each intermediate node. At the terminating node, you will need to create a hairpin loopback at the end of the PRBS source span to return the signal.
Note The diagnostic VT circuit does not raise a failure alarm if AIS-P or UNEQ-P is returned to the PRBS detector. In order to see an alarm indicating a failed diagnostic circuit, the circuit must be returned to the
PRBS detector with a different payload than the generator sources and without the AIS-P or UNEQ-P conditions.
Create a Bidirectional Diagnostic Circuit
Step 1 Log into the node where you will create the diagnostic circuit. (For login instructions, refer to the
“Connect the PC and Log into the GUI” chapter in the Cisco ONS 15454 Procedure Guide .)
1-104
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.7.3 Bidirectional Diagnostic Circuit
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
If you want to assign a name to the circuit source and destination ports before you create the circuit, refer to the task for assigning a name to a port in the “Create Circuits and VT Tunnels” chapter of the
Cisco ONS 15454 Procedure Guide. If not, continue with
.
From the View menu, choose Go to Network View .
Click the Circuits tab, then click Create .
In the Circuit Creation dialog box, complete the following fields:
• Circuit Type—Choose VT .
•
•
Number of Circuits—Enter 1 (the maximum diagnostic circuit quantity available per STS).
Auto-ranged—Uncheck the box. (This option is not applicable to diagnostic circuits.)
Click Next .
Define the circuit attributes in the Circuit Creation Dialog Box (
Figure 1-44 ) using the following
parameters:
Figure 1-44 Network View Circuit Creation Dialog Box
Step 8
•
•
•
•
•
•
Name—Assign a name to the circuit. The name can be alphanumeric and up to 48 characters,
(including spaces). Circuit names should be 44 characters or less if you want the ability to create monitor circuits. If you leave the field blank, CTC assigns a default name to the circuit.
Size—VT1.5 is the default. You cannot change it.
Bidirectional—This is the default value. Leave it checked for this circuit.
State—This option is not available when you check the Diagnostic option.
Diagnostic—Check this box to create a diagnostic circuit.
Apply to drop ports—Leave this box unchecked.
Create cross-connects only (TL1-like)—Not applicable to diagnostic circuits. •
•
•
Inter-domain (UCP) SLA—Not applicable to diagnostic circuits.
Protected Drops—Not applicable to diagnostic circuits.
Click Next .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-105
Chapter 1 General Troubleshooting
1.7.4 Data Communications Network Tool
Step 9
Step 10
Step 11
Step 12
In the Source area of the Circuit Creation pane, complete the following: a.
b.
From the Node drop-down list, choose the node.
From the Slot drop-down list, choose PRBS Generator .
c.
Click Next .
In the Destination area of the Circuit Creation pane, complete the following: a.
b.
c.
d.
From the Node drop-down list, choose the node. The only selectable item in the list is the node chosen as the source node.
From the Slot drop-down list, choose the slot where the span originates.
From the STS drop-down list, choose the STS.
From the VT drop-down list, choose the VT. e.
Click Next .
Click Finish .
In the Circuits window, verify that the new circuit(s) appear in the circuits list.
1.7.4 Data Communications Network Tool
CTC contains a data communications network (DCN) tool that assists with network troubleshooting for
Open Shortest Path First (OSPF) networks. This tool, located in network view, is shown in
It executes an internal dump command to retrieve information about all nodes accessible from the entry point.
1-106
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
Figure 1-45 DCN Tools OSPF Dump
1.8 Restoring the Database and Default Settings
The dump, which provides the same information as a dump executed by special networking commands, is available at the network view in the Maintenance > Diagnostic tabs. You can select the access point node in the Select Node drop-down list. To create the dump, click Retrieve. (To clear the dump, click
Clear.)
The contents of the dump file can be saved or printed and furnished to Cisco Technical Support for use in OSPF network support.
1.8 Restoring the Database and Default Settings
This section contains troubleshooting for node operation errors that require restoring software data or the default node setup.
1.8.1 Restore the Node Database
Symptom One or more nodes does not function properly or has incorrect data.
Possible Cause Incorrect or corrupted node database.
Recommended Action Complete the procedures in the “Maintain the Node” chapter of the
Cisco ONS 15454 Procedure Guide .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-107
Chapter 1 General Troubleshooting
1.9 PC Connectivity Troubleshooting
1.9 PC Connectivity Troubleshooting
This section contains information about system minimum requirements, supported platforms, browsers, and JREs. It also contains troubleshooting procedures for PC and network connectivity to the
ONS 15454.
1.9.1 PC System Minimum Requirements
Workstations running CTC Software Release 7.2 for the ONS products on Windows platforms must have the following minimum requirements:
•
•
•
•
•
Pentium III or higher processor
Processor speed of at least 700 MHz
256 MB or more of RAM
50 MB or more of available hard disk space
20 GB or larger hard drive
1.9.2 Sun System Minimum Requirements
Workstations running Software R7.2 for the ONS products on Sun workstations need to have the following minimum requirements:
•
•
•
UltraSPARC or faster processor
256 MB or more of RAM
50 MB or more of available hard disk space
1.9.3 Supported Platforms, Browsers, and JREs
Software R7.2 supports the following platforms:
•
•
•
•
•
•
Windows NT
Windows 98
Windows XP
Windows 2000
Solaris 8
Solaris 9
Software R7.2 supports the following browsers and JREs:
• Netscape 7 browser (PC or Solaris 8 or 9 with Java plug-in 1.4.2 or 5.0)
•
•
•
PC platforms with Java plug-in 1.4.2 or 5.0
Internet Explorer 6.0 browser (on PC platforms with Java plug-in 1.4.2 or 5.0)
Mozilla 1.7 (Solaris only)
1-108
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.9.4 Unsupported Platforms and Browsers
Note You can obtain browsers at the following URLs:
Internet Explorer: http://www.microsoft.com
Mozilla: http://www.mozilla.org/
Note JRE 1.4.2 or JRE 5.0 is required to run Software R7.2. JRE 1.4.2 is provided on the software CD.
1.9.4 Unsupported Platforms and Browsers
Software R7.2 does not support the following platforms:
•
•
Windows 95
Solaris 2.5
• Solaris 2.6
Software R7.2 does not support the following browsers and JREs:
•
•
•
Netscape 4.73 for Windows.
Netscape 4.76 on Solaris is not supported.
Netscape 7 on Solaris 8 or 9 is only supported with JRE 1.4.2 and above.
1.9.5 Unable to Verify the IP Configuration of Your PC
Symptom When connecting your PC to the ONS 15454, you are unable to successfully ping the IP address of your PC to verify the IP configuration.
Possible Cause The IP address and/or subnet mask was entered incorrectly.
Recommended Action Verify that the IP address used to ping the PC matches the IP address displayed when in the Windows IP Configuration information retrieved from the system. See the
IP Configuration of Your PC” procedure on page 1-109 .
Possible Cause The IP configuration of your PC is not properly set.
Recommended Action Verify the IP configuration of your PC. Complete the
Configuration of Your PC” procedure on page 1-109
. If this procedure is unsuccessful, contact your
Network Administrator for instructions to correct the IP configuration of your PC.
Verify the IP Configuration of Your PC
Step 1
Step 2
Step 3
Open a DOS command window by selecting Start > Run from the Start menu.
In the Open field, type command and then click OK . The DOS command window appears.
At the prompt in the DOS window, type one of the following commands:
• For Windows 98, NT, 2000, and XP, type ipconfig and press the Enter key.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-109
Chapter 1 General Troubleshooting
1.9.6 Browser Login Does Not Launch Java
The Windows IP configuration information appears, including the IP address, subnet mask, and the default gateway.
Note The winipcfg command only returns the information above if you are on a network.
Step 4
Step 5
At the prompt in the DOS window, type ping followed by the IP address shown in the Windows IP configuration information previously displayed.
Press the Enter key to execute the command.
If the DOS window returns multiple (usually four) replies, the IP configuration is working properly.
If you do not receive a reply, your IP configuration might not be properly set. Contact your Network
Administrator for instructions to correct the IP configuration of your PC.
1.9.6 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.
Possible Cause The PC operating system and browser are not properly configured.
Recommended Action Reconfigure the PC operating system java plug-in control panel and the browser settings. Complete the
“Reconfigure the PC Operating System Java Plug-in Control Panel” procedure on page 1-110 and the
“Reconfigure the Browser” procedure on page 1-111 .
Reconfigure the PC Operating System Java Plug-in Control Panel
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 1
Step 2
From the Windows start menu, click Settings > Control Panel .
If Java Plug-in does not appear, the JRE might not be installed on your PC: a.
b.
c.
d.
Run the Cisco ONS 15454 software CD.
Open the CD-drive : \ Windows\JRE folder.
Double-click the j2re-1_4_2-win icon to run the JRE installation wizard.
Follow the JRE installation wizard steps.
From the Windows start menu, click Settings > Control Panel .
In the Java Plug-in Control Panel window, double-click the Java Plug-in 1.4.2
icon.
Click the Advanced tab on the Java Plug-in Control Panel.
Navigate to C:\ProgramFiles\JavaSoft\JRE\1.4.2
.
Select JRE 1.4
.
Click Apply .
Close the Java Plug-in Control Panel window.
1-110
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.9.7 Unable to Verify the NIC Connection on Your PC
Reconfigure the Browser
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
From the Start Menu, launch your browser application.
If you are using Netscape Navigator: a.
On the Netscape Navigator menu bar, click the Edit > Preferences menus.
b.
c.
d.
e.
In the Preferences window, click the Advanced > Proxies
In the Proxies window, click the Direct connection to the Internet check box and click OK .
On the Netscape Navigator menu bar, click the
categories.
Edit > Preferences menus.
In the Preferences window, click the Advanced > Cache categories.
f.
Confirm that the Disk Cache Folder field shows one of the following paths:
• For Windows 98/ME, C:\ProgramFiles\Netscape\Communicator\cache
• For Windows NT/2000/XP, C:\ProgramFiles\Netscape\ username \Communicator\cache .
If the Disk Cache Folder field is not correct, click Choose Folder .
g.
h.
i.
c.
Navigate to the file listed in Step
OK .
Click OK on the Preferences window and exit the browser.
If you are using Internet Explorer: a.
On the Internet Explorer menu bar, click the Tools > Internet Options menus.
b.
In the Internet Options window, click the Advanced tab.
In the Settings menu, scroll down to Java (Sun) and click the Use Java 2 v1.4.2 for applet (requires restart) check box.
d.
Click OK in the Internet Options window and exit the browser.
Temporarily disable any virus-scanning software on the computer. See the
Downloading CTC JAR Files From TCC2/TCC2P Card” section on page 1-116
.
Verify that the computer does not have two network interface cards (NICs) installed. If the computer does have two NICs, remove one.
Restart the browser and log on to the ONS 15454.
1.9.7 Unable to Verify the NIC Connection on Your PC
Symptom When connecting your PC to the ONS 15454, you are unable to verify that the network interface card (NIC) connection is working properly because the link LED is not illuminated or flashing.
Possible Cause The Category-5 cable is not plugged in properly.
Recommended Action Confirm that both ends of the cable are properly inserted. If the cable is not fully inserted due to a broken locking clip, the cable should be replaced.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-111
Chapter 1 General Troubleshooting
1.9.8 Verify PC Connection to the ONS 15454 (ping)
Possible Cause The Category-5 cable is damaged.
Recommended Action Ensure that the cable is in good condition. If in doubt, use a known-good cable.
Often, cabling is damaged due to pulling or bending. (For information about installing cable, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .)
Possible Cause Incorrect type of Category-5 cable is being used.
Recommended Action If you are connecting an ONS 15454 directly to your laptop, a PC, or a router, use a straight-through Category-5 cable. When connecting the ONS 15454 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.12.2.1 Crimp Replacement LAN Cables” section on page 1-134 .
Possible Cause The NIC is improperly inserted or installed.
Recommended Action If you are using a Personal Computer Memory Card International Association
(PCMCIA)-based NIC, remove and reinsert the NIC to make sure the NIC is fully inserted. (If the
NIC is built into the laptop or PC, verify that the NIC is not faulty.)
Possible Cause The NIC is faulty.
Recommended Action Confirm that the NIC is working properly. If you have no issues connecting to the network (or any other node), then the NIC should be working correctly. If you have difficulty connecting a to the network (or any other node), then the NIC might be faulty and needs to be replaced.
1.9.8 Verify PC Connection to the ONS 15454 (ping)
Symptom The TCP/IP connection was established and then lost.
Possible Cause A lost connection between the PC and the ONS 15454.
Recommended Action Use a standard ping command to verify the TCP/IP connection between the PC and the ONS 15454 TCC2/TCC2P card. A ping command should work if the PC connects directly
to the TCC2/TCC2P card or uses a LAN to access the TCC2/TCC2P card. Complete the “Ping the
ONS 15454” procedure on page 1-112 .
Ping the ONS 15454
Step 1
Step 2
Open a the command prompt: a.
b.
If you are using a Microsoft Windows operating system, from the Start Menu choose Run , enter command in the Open field of the Run dialog box, and click OK .
If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
For both the Sun and Microsoft operating systems, at the prompt enter: ping ONS-15454-IP-address
For example: ping 198.168.10.10
1-112
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.9.9 The IP Address of the Node is Unknown
Step 3
Step 4
Step 5
Step 6
If the workstation has connectivity to the ONS 15454, the ping is successful and displays a reply from the IP address. If the workstation does not have connectivity, a “Request timed out” message appears.
If the ping is successful, it demonstrates that an active TCP/IP connection exists. Restart CTC.
If the ping is not successful, and the workstation connects to the ONS 15454 through a LAN, check that the workstation’s IP address is on the same subnet as the ONS node.
If the ping is not successful and the workstation connects directly to the ONS 15454, check that the link light on the workstation’s NIC is illuminated.
1.9.9 The IP Address of the Node is Unknown
Symptom The IP address of the node is unknown and you are unable to login.
Possible Cause The node is not set to the default IP address.
Recommended Action Leave one TCC2/TCC2P card in the shelf. Connect a PC directly to the remaining TCC2/TCC2P card and perform a hardware reset of the card. The TCC2/TCC2P card transmits the IP address after the reset to enable you to capture the IP address for login. Complete the
“Retrieve Unknown Node IP Address” procedure on page 1-113
.
Retrieve Unknown Node IP Address
Step 1
Step 2
Step 3
Step 4
Connect your PC directly to the active TCC2/TCC2P card Ethernet port on the faceplate.
Start the Sniffer application on your PC.
Perform a hardware reset by pulling and reseating the active TCC2/TCC2P card.
After the TCC2/TCC2P card completes resetting, it broadcasts its IP address. The Sniffer software on your PC will capture the IP address being broadcast.
1.10 CTC Operation Troubleshooting
This section contains troubleshooting procedures for CTC login or operation problems.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-113
Chapter 1 General Troubleshooting
1.10.1 CTC Colors Do Not Appear Correctly on a UNIX Workstation
1.10.1 CTC Colors Do Not Appear Correctly on a UNIX Workstation
Symptom When running CTC on a UNIX workstation, the colors do not appear correctly. For example, both major and minor alarms appear in the same color.
Possible Cause When running in 256-color mode on a UNIX workstation, color-intensive applications such as Netscape might use all of the colors.
Recommended Action CTC requires a full 24-color palette to run properly. When logging into CTC on a UNIX workstation, run as many colors as your adapter will support. In addition, you can use the -install or the -ncols 32 command line options to limit the number of colors that Netscape uses.
Complete the “Limit Netscape Colors” procedure on page 1-114 . If the problem persists after
limiting Netscape colors, exit any other color-intensive applications in use.
Limit Netscape Colors
Step 1
Step 2
Close the current session of Netscape.
Launch Netscape from the command line by entering: netscape -install
(installs Netscape colors for Netscape use) or netscape -ncols 32
(limits Netscape to 32 colors so that if the requested color is not available, Netscape chooses the closest color option)
1.10.2 Unable to Launch CTC Help After Removing Netscape
Symptom After removing Netscape and running CTC using Internet Explorer, you are unable to launch
CTC Help and receive an “MSIE is not the default browser” error message.
Possible Cause Loss of association between browser and Help files.
Recommended Action When the CTC software and Netscape are installed, the Help files are associated with Netscape by default. When you remove Netscape, the Help files are not automatically associated with Internet Explorer as the default browser. Reset Internet Explorer as the default browser so that CTC associates the Help files to the correct browser. Complete the
Internet Explorer as the Default Browser for CTC” procedure on page 1-114
to associate the CTC
Help files to the correct browser.
Reset Internet Explorer as the Default Browser for CTC
Step 1
Step 2
Step 3
Open the Internet Explorer browser.
From the menu bar, click Tools > Internet Options . The Internet Options window appears.
In the Internet Options window, click the Programs tab.
1-114
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.3 Unable to Change Node View to Network View
Step 4
Step 5
Step 6
Step 7
Click the Internet Explorer should check to see whether it is the default browser check box.
Click OK .
Exit any and all open and running CTC and Internet Explorer applications.
Launch Internet Explorer and open a new CTC session. You should now be able to access the CTC Help.
1.10.3 Unable to Change Node View to Network View
Symptom When activating a large, multinode BLSR from Software R3.2 to Software R3.3, some of the nodes appear grayed out. Logging into the new CTC, the user is unable to change node view to network view on any and all nodes, from any workstation. This is accompanied by an “Exception occurred during event dispatching: java.lang.OutOfMemoryError” in the java window.
Possible Cause The large, multinode BLSR requires more memory for the graphical user interface
(GUI) environment variables.
Recommended Action Reset the system or user CTC_HEAP environment variable to increase the memory limits. Complete the
“Reset the CTC_HEAP Environment Variable for Windows” procedure on page 1-115
or the
“Reset the CTC_HEAP Environment Variable for Solaris” procedure on page 1-115
to enable the CTC_HEAP variable change.
Note This problem typically affects large networks where additional memory is required to manage large numbers of nodes and circuits.
Reset the CTC_HEAP Environment Variable for Windows
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Exit any and all open and running CTC and Netscape applications.
From the Windows Desktop, right-click My Computer and choose Properties in the shortcut menu.
In the System Properties window, click the Advanced tab.
Click Environment Variables to open the Environment Variables window.
Click New under the User variables field or the System variables field.
Enter CTC_HEAP in the Variable Name field.
Enter 256 in the Variable Value field, and then click OK to create the variable.
Click OK in the Environment Variables window to accept the changes.
Click OK in the System Properties window to accept the changes.
Restart the browser and CTC software.
Reset the CTC_HEAP Environment Variable for Solaris
Step 1 From the user shell window, kill any CTC applications.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 1-115
Chapter 1 General Troubleshooting
1.10.4 Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P Card
Step 2
Step 3
Step 4
Kill any Netscape applications.
In the user shell window, set the environment variable to increase the heap size:
% setenv CTC_HEAP 256
Restart the browser and CTC software in the same user shell window.
1.10.4 Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P
Card
Symptom The browser stalls or hangs when downloading a CTC Java archive (JAR) file from the
TCC2/TCC2P card.
Possible Cause McAfee VirusScan software might be interfering with the operation. The problem occurs when the VirusScan Download Scan is enabled on McAfee VirusScan 4.5 or later.
Recommended Action
Disable the VirusScan Download Scan feature. Complete the “Disable the
VirusScan Download Scan” procedure on page 1-116 .
Disable the VirusScan Download Scan
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
From the Windows Start menu, choose Programs > Network Associates > VirusScan Console .
Double-click the VShield icon listed in the VirusScan Console dialog box.
Click Configure on the lower part of the Task Properties window.
Click the Download Scan icon on the left of the System Scan Properties dialog box.
Uncheck the Enable Internet download scanning check box.
Click Yes when the warning message appears.
Click OK in the System Scan Properties dialog box.
Click OK in the Task Properties window.
Close the McAfee VirusScan window.
1.10.5 CTC Does Not Launch
Symptom CTC does not launch; usually an error message appears before the login window appears.
Possible Cause The Netscape browser cache might point to an invalid directory.
Recommended Action Redirect the Netscape cache to a valid directory. Complete the
Netscape Cache to a Valid Directory” procedure on page 1-117 .
1-116
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.6 Slow CTC Operation or Login Problems
Redirect the Netscape Cache to a Valid Directory
Step 1
Step 2
Step 3
Step 4
Step 5
Launch Netscape.
Open the Edit menu.
Choose Preferences .
Under the Category column on the left side, expand the Advanced category and choose the Cache tab.
Change your disk cache folder to point to the cache file location.
The cache file location is usually C:\ProgramFiles\Netscape\Users\ yourname \cache. The yourname segment of the file location is often the same as the user name.
1.10.6 Slow CTC Operation or Login Problems
Symptom You experience slow CTC operation or have problems logging into CTC.
Possible Cause The CTC cache file might be corrupted or might need to be replaced.
Recommended Action Search for and delete cache files. This operation forces the ONS 15454 to download a new set of Java archive (JAR) files to your computer hard drive. Complete the
“Delete the CTC Cache File Automatically” procedure on page 1-117
or the “Delete the CTC Cache File
Manually” procedure on page 1-118
.
Delete the CTC Cache File Automatically
Caution All running sessions of CTC must be halted before deleting the CTC cache. Deleting CTC cache might cause any CTC running on this system to behave in an unexpected manner.
Step 1
Step 2
Step 3
Enter an ONS 15454 IP address into the browser URL field. The initial browser window shows a
Delete CTC Cache button.
Close all open CTC sessions and browser windows. The PC operating system does not allow you to delete files that are in use.
Click Delete CTC Cache
on the initial browser window to clear the CTC cache. Figure 1-46
shows the
Delete CTC Cache window.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-117
1.10.6 Slow CTC Operation or Login Problems
Figure 1-46 Deleting the CTC Cache
Chapter 1 General Troubleshooting
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
Step 2
Step 3
Step 4
Step 5
To delete the JAR files manually, from the Windows Start menu choose Search > For Files or Folders .
Enter ctc*.jar or cms*.jar in the Search for files or folders named field in the Search Results dialog box and click Search Now .
Click the Modified column in the Search Results dialog box to find the JAR files that match the date when you downloaded the files from the TCC2/TCC2P.
Highlight the files and press the keyboard Delete key.
Click Yes in the Confirm dialog box.
1-118
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.7 Node Icon is Gray on CTC Network View
1.10.7 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.
Possible Cause Different CTC releases do not recognize each other.
Recommended Action Correct the core version build as described in the
Releases Do Not Recognize Each Other” section on page 1-121 .
Possible Cause Username and password do not match.
Recommended Action Correct the username and password as described in the
Password Do Not Match” section on page 1-122
.
Possible Cause No IP connectivity between nodes.
Recommended Action Usually accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in the
“1.10.16 Ethernet Connections” section on page 1-124 .
Possible Cause A lost DCC connection.
Recommended Action Usually accompanied by an embedded operations channel (EOC) alarm. Clear the EOC alarm and verify the DCC connection as described in the
.
1.10.8 CTC Cannot Launch Due to Applet Security Restrictions
Symptom The error message “Unable to launch CTC due to applet security restrictions” appears after you enter the IP address in the browser window.
Possible Cause You are logging into a node running CTC Software R4.0 or earlier. Releases earlier than R4.1 require a modification to the java.policy file so that CTC JAR files can be downloaded to the computer. The modified java.policy file might not exist on the computer.
Recommended Action Install the software CD for the release of the node you are logging into. Run the CTC Setup Wizard (double-click Setup.exe
). Choose Custom installation , then choose the Java
Policy option. For additional information, refer to the CTC installation information in the “Connect the PC and Log into the GUI” chapter of the Cisco ONS 15454 Procedure Guide . If the software CD is not available, you must manually edit the java.policy file on your computer. Complete the
“Manually Edit the java.policy File” procedure on page 1-119 .
Manually Edit the java.policy File
Step 1
Step 2
Search your computer for java.policy file and open it with a text editor (Notepad or Wordpad).
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 {
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-119
Chapter 1 General Troubleshooting
1.10.9 Java Runtime Environment Incompatible
Step 3
Step 4
Step 5 permission java.security.AllPermission;
};
If these five lines are not in the file, enter them manually.
Save the file and restart Netscape.
CTC should now start correctly.
If the error message is still reported, save the java.policy file as .java.policy
. On Win98/2000/XP PCs, save the file to the C:\Windows folder. On Windows NT 4.0 or later PCs, save the file to all of the user folders on that PC, for example, C:\Winnt\profiles\joeuser.
1.10.9 Java Runtime Environment Incompatible
Symptom The CTC application does not run properly.
Possible Cause The compatible Java 2 JRE is not installed.
Recommended Action The JRE contains the Java virtual machine, runtime class libraries, and Java application launcher that are necessary to run programs written in the Java programming language.
The ONS 15454 CTC is a Java application. A Java application, unlike an applet, cannot rely completely on a web browser for installation and runtime services. When you run an application written in the Java programming language, you need the correct JRE installed. The correct JRE for each CTC software release is included on the Cisco ONS 15454 software CD. Complete the
“Launch CTC to Correct the Core Version Build” procedure on page 1-121
. If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible
with the different software releases. Table 1-3 shows JRE compatibility with ONS 15454 software
releases.
Table 1-3 JRE Compatibility
Software Release
ONS 15454 R2.2.1 and earlier
ONS 15454 R2.2.2
ONS 15454 R3.0
ONS 15454 R3.1
ONS 15454 R3.2
ONS 15454 R3.3
ONS 15454 R3.4
ONS 15454 R4.0
2
ONS 15454 R4.1
ONS 15454 R4.5
ONS 15454 R4.6
ONS 15454 R4.7
JRE 1.2.2
Compatible
Yes
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
No
JRE 1.3
Compatible
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
JRE 1.4
Compatible
No
No
No
No
No
No
No
No
No
No
Yes
Yes
JRE 1.4.2
Compatible
No
No
No
No
No
No
No
No
No
No
No
No
1
JRE 1.5
Compatible
No
No
No
No
No
No
No
No
No
No
No
No
1-120
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.10 Different CTC Releases Do Not Recognize Each Other
Table 1-3 JRE Compatibility (continued)
Software Release
ONS 15454 R5.0
ONS 15454 R6.0
ONS 15454 R7.0
ONS 15454 R7.2
JRE 1.2.2
Compatible
No
No
No
No
JRE 1.3
Compatible
Yes
No
No
No
JRE 1.4
Compatible
Yes
Yes
No
No
1.
JRE 1.4.2 is the recommended version and is provided on the software CD.
2.
R4.0 notifies you if an earlier JRE version is running on your PC or UNIX workstation.
JRE 1.4.2
Compatible
1
Yes
Yes
Yes
Yes
JRE 1.5
Compatible
No
No
Yes
Yes
Launch CTC to Correct the Core Version Build
Step 1
Step 2
Step 3
Step 4
Exit the current CTC session and completely close the browser.
Start the browser.
Enter the ONS 15454 IP address of the node that reported the alarm. This can be the original IP address you logged in with or an IP address other than the original.
Log into CTC. The browser downloads the JAR file from CTC.
1.10.10 Different CTC Releases Do Not Recognize Each Other
Symptom Different CTC releases do not recognize each other. This situation is often accompanied by the
INCOMPATIBLE-SW alarm.
Possible Cause The software loaded on the connecting workstation and the software on the
TCC2/TCC2P card are incompatible.
Recommended Action This occurs when the TCC2/TCC2P 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. Complete the “Launch
CTC to Correct the Core Version Build” procedure on page 1-121
.
Note Remember to always log into the ONS node with the latest CTC core version first. If you initially log into an ONS node running a CTC core version of 2.2 or lower and then attempt to log into another ONS node in the network running a higher CTC core version, the lower version node does not recognize the new node.
Launch CTC to Correct the Core Version Build
Step 1
Step 2
Exit the current CTC session and completely close the browser.
Start the browser.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-121
Chapter 1 General Troubleshooting
1.10.11 Username or Password Do Not Match
Step 3
Step 4
Enter the ONS 15454 IP address of the node that reported the alarm. This can be the original IP address you logged on with or an IP address other than the original.
Log into CTC. The browser downloads the JAR file from CTC.
1.10.11 Username or Password Do Not Match
Symptom A username/password mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm .
Possible Cause The username or password entered does not match the information stored in the
TCC2/TCC2P.
Recommended Action All ONS nodes must have the same username and password created to display every ONS node in the network. You can also be locked out of certain ONS nodes on a network if your username and password were not created on those specific ONS nodes. For initial login to the
ONS 15454, enter the CISCO15 user name in capital letters and click Login and use the password
“otbu+1,” which is case-sensitive. Complete the
and password are verified against the Radius server database rather than the security information in the local node database. For more information about Radius security, refer to the “Security” chapter in the Cisco ONS 15454 Reference Manual .
Verify Correct Username and Password
Step 1
Step 2
Step 3
Ensure that your keyboard Caps Lock key is not turned on and affecting the case-sensitive entry of the username and password.
Contact your system administrator to verify the username and password.
Call Cisco Technical Support at 1 800 553-2447 to have them enter your system and create a new user name and password.
1.10.12 No IP Connectivity Exists Between Nodes
Symptom No IP connectivity exists between nodes. The nodes have a gray icon. This problem is usually accompanied by alarms.
Possible Cause A lost Ethernet connection.
Recommended Action Usually is accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in the
“1.10.16 Ethernet Connections” section on page 1-124
.
1-122
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.13 DCC Connection Lost
1.10.13 DCC Connection Lost
Symptom DCC connection is lost. The node usually has alarms and the nodes in the network view have a gray icon. This symptom is usually accompanied by an EOC alarm.
Possible Cause A lost DCC connection.
Recommended Action Usually accompanied by an EOC alarm. Clear the EOC alarm and verify the
DCC connection as described in the
.
1.10.14 “Path in Use” Error When Creating a Circuit
Symptom While creating a circuit, you get a “Path in Use” error that prevents you from completing the circuit creation.
Possible Cause Another user has already selected the same source port to create another circuit.
Recommended Action 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. The other user gets the “Path in
Use” error. Cancel the circuit creation and start over, or click Back until you return to the initial circuit creation window. The source port that was previously selected no longer appears in the available list because it is now part of a provisioned circuit. Select a different available port and begin the circuit creation process again.
1.10.15 Calculate and Design IP Subnets
Symptom You cannot calculate or design IP subnets on the ONS 15454.
Possible Cause The IP capabilities of the ONS 15454 require specific calculations to properly design
IP subnets.
Recommended Action Cisco provides a free online tool to calculate and design IP subnets.
Go to http://www.cisco.com/cgi-bin/Support/IpSubnet/home.pl
.
For information about ONS 15454 IP capability, refer to the “Management Network Connectivity” chapter in the Cisco ONS 15454 Reference Manual .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-123
Chapter 1 General Troubleshooting
1.10.16 Ethernet Connections
1.10.16 Ethernet Connections
Symptom Ethernet connections appear to be broken or are not working properly.
Possible Cause Improperly seated connections.
Possible Cause Incorrect connections.
Recommended Action You can fix most connectivity problems in an Ethernet network by following a few guidelines. See
when using the steps in the
“Verify Ethernet Connections” procedure on page 1-124 .
Figure 1-47
Device "A"
192.168.1.25
255.255.255.0
VLAN #1 Member
Ethernet Connectivity Reference
Device "B"
192.168.1.75
255.255.255.0
VLAN #1 Member
Virtual
LAN # 1
ONS Node #1
Port #1 VLAN #1
Device "C"
192.168.1.50
Port #3 VLAN #1
255.255.255.0
VLAN #1 Member
ONS Node #2
Port #1 VLAN #1
Port #2 VLAN #1
Device "D"
192.168.1.100
255.255.255.0
VLAN #1 Member
Verify Ethernet Connections
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Verify that the alarm filter is turned OFF.
Check for SONET and DWDM alarms on the STS that carries the VLAN Ethernet circuit. Clear any alarms by looking them up in
Chapter 2, “Alarm Troubleshooting.”
Check for Ethernet-specific alarms. Clear any raised alarms by looking up that alarm in Chapter 2,
Verify that the ACT LED on the Ethernet card is green.
Verify that Ports 1 and 3 on ONS 15454 #1 and Ports 1 and 2 on ONS 15454 #2 have green link-integrity
LEDs illuminated.
If no green link-integrity LED is illuminated for any of these ports: a.
b.
c.
Verify physical connectivity between the ONS 15454s and the attached device.
Verify that the ports are enabled on the Ethernet cards.
Verify that you are using the proper Ethernet cable and that it is wired correctly, or replace the cable with a known-good Ethernet cable.
1-124
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.10.17 VLAN Cannot Connect to Network Device from Untag Port
Step 7
Step 8
Step 9 d.
Check the status LED on the Ethernet card faceplate to ensure the card booted up properly. This LED should be steady green. If necessary, remove and reinsert the card and allow it to reboot.
e.
It is possible that the Ethernet port is functioning properly but the link LED itself is broken.
Complete the
“Verify General Card LED Operation” procedure on page 1-101
.
Verify connectivity between device A and device C by pinging between these locally attached devices.
Complete the
“1.9.8 Verify PC Connection to the ONS 15454 (ping)” procedure on page 1-112
. If the ping is unsuccessful: a.
b.
Verify that device A and device C are on the same IP subnet.
Open the Ethernet card in CTC card view and click the Provisioning > VLAN tabs to verify that both Port 1 and Port 3 on the card are assigned to the same VLAN.
c.
If a port is not assigned to the correct VLAN, click that port column in the VLAN row and set the port to Tagged or Untag. Click Apply .
for devices B and D.
Verify that the Ethernet circuit that carries VLAN #1 is provisioned and that ONS 15454 #1 and
ONS 15454 #2 ports also use VLAN #1.
1.10.17 VLAN Cannot Connect to Network Device from Untag Port
Symptom Networks that have a VLAN with one ONS 15454 Ethernet card port set to Tagged and one
ONS 15454 Ethernet card set to Untag might have difficulty implementing Address Resolution Protocol
(ARP) for a network device attached to the Untag port ( Figure 1-48
). They might also see a higher than normal runt packets count at the network device attached to the Untag port. This symptom/limitation also exists when ports within the same card or ports within the same chassis are put on the same VLAN, with a mix of tagged and untagged.
Possible Cause The Tagged ONS 15454 adds the IEEE 802.1Q tag and the Untag ONS 15454 removes the Q-tag without replacing the bytes. The NIC of the network device categorizes the packet as a runt and drops the packet.
Possible Cause Dropped packets can also occur when ARP attempts to match the IP address of the network device attached to the Untag port with the physical MAC address required by the network access layer.
Recommended Action The solution is to set both ports in the VLAN to Tagged to stop the stripping of the 4 bytes from the data packet and prevent the NIC card in the network access device from recognizing the packet as a runt and dropping it. Network devices with IEEE 802.1Q-compliant NIC cards accept the tagged packets. Network devices with non IEEE 802.1Q compliant NIC cards still drop these tagged packets. The solution might require upgrading network devices with non-IEEE 802.1Q compliant NIC cards to IEEE 802.1Q compliant NIC cards. You can also set both ports in the VLAN to Untag, but you will lose IEEE 802.1Q compliance.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-125
Chapter 1 General Troubleshooting
1.10.17 VLAN Cannot Connect to Network Device from Untag Port
Figure 1-48 VLAN with Ethernet Ports at Tagged and Untag
Workstation #1 ONS Node with Ethernet card
VLAN port set to Tagged
ONS Node with Ethernet card
Workstation #2
VLAN port set to Untag
SONET/SDH
Ethernet
Change VLAN Port Tagged and Untag Settings
Step 1
Step 2
Open the CTC card view for the Ethernet card involved in the problem VLAN.
Click the Provisioning > Ether VLAN tabs (
Figure 1-49 Configuring VLAN Membership for Individual Ethernet Ports
Step 3
Step 4
If the port is set to Tagged , continue to look at other cards and their ports in the VLAN until you find the port that is set to Untag .
At the VLAN port set to Untag , click the port and choose Tagged .
1-126
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.11 Circuits and Timing
Step 5
Note The attached external devices must recognize IEEE 802.1Q VLANs.
After each port is in the appropriate VLAN, click Apply .
1.11 Circuits and Timing
This section provides solutions to circuit creation and reporting errors, as well as common timing reference errors and alarms.
1.11.1 OC-N Circuit Transitions to Partial State
Symptom An automatic or manual transition of a circuit from one state to another state results in the
OOS-PARTIAL status, which indicates that not all OC-N connections in the circuit are in the IS-NR service state.
Possible Cause During a manual transition, CTC cannot communicate with one of the nodes or one of the nodes is on a version of software that does not support the new state model.
Recommended Action Repeat the manual transition operation. If the partial state persists, determine which node in the circuit is not changing to the desired state. Complete the
Circuit Nodes” procedure on page 1-127
. Log into the circuit node that did not change to the desired state and determine the version of software. If the software on the node is Software R3.3 or earlier, upgrade the software. Refer to the release-specific software upgrade document for procedures.
Note If the node software cannot be upgraded to R4.0, the partial state condition can be avoided by using only the circuit state supported in the earlier software version.
Possible Cause During an automatic transition, some path-level defects and/or alarms were detected on the circuit.
Possible Cause One end of the circuit is not properly terminated.
Recommended Action Determine which node in the circuit is not changing to the desired state.
Complete the
“View the State of OC-N Circuit Nodes” procedure on page 1-127
. Log onto the circuit node that did not change to the desired state and examine the circuit for path-level defects, improper circuit termination, or alarms. See
Chapter 2, “Alarm Troubleshooting,” for procedures to
clear alarms. Refer to the “Manage Circuits” chapter in the Cisco ONS 15454 Procedure Guide for instructions to change circuit configuration settings. Resolve and clear the defects and/or alarms on the circuit node and verify that the circuit transitions to the desired state.
View the State of OC-N Circuit Nodes
Step 1 Click the Circuits tab.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-127
Chapter 1 General Troubleshooting
1.11.2 AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits
Step 2
Step 3
Step 4
From the Circuits tab list, select the circuit with the * _PARTIAL status condition.
Click Edit . The Edit Circuit window appears.
In the Edit Circuit window, click the State tab (if you are viewing a SONET circuit).
The State tab window lists the Node, End A, End B, CRS Admin State, and CRS Service State for each of the nodes in the circuit.
1.11.2 AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits
Symptom An incomplete circuit path causes an AIS.
Possible Cause The port on the reporting node is in-service but a node upstream on the circuit does not have an OC-N port in service.
Recommended Action An AIS-V indicates that an upstream failure occurred at the virtual tributary
(VT) layer. AIS-V alarms also occur on DS3XM-6 and DS3XM-12 VT circuits that are not carrying traffic and on stranded bandwidth. Complete the
“Clear AIS-V on DS3XM-6 or DS3XM-12 Unused
VT Circuits” procedure on page 1-128
.
Clear AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Determine the affected port.
Record the node ID, slot number, port number, or VT number.
Create a unidirectional VT circuit from the affected port back to itself, such as
Source node/Slot 2/Port 2/VT 13 cross connected to Source node/Slot 2/Port 2/VT 13.
Uncheck the Bidirectional check box in the circuit creation window.
Give the unidirectional VT circuit an easily recognizable name, such as delete me.
Open the DS3XM-6 card in CTC card view. Click the Maintenance > DS1 tabs.
Locate the VT that is reporting the alarm (for example, DS3 #2, DS1 #13).
From the Loopback Type list, choose Facility and click Apply .
Click Circuits .
Find the one-way circuit you created in
. Select the circuit and click Delete . Do not check any check boxes.
Click Yes in the Delete Confirmation dialog box.
Open the DS3XM-6 or DS3XM-12 card in CTC card view. Click Maintenance > DS1 tabs.
Locate the VT in Facility Loopback.
From the Loopback Type list, choose None and then click Apply .
Click the Alarms tab and verify that the AIS-V alarms have cleared.
Repeat this procedure for all the AIS-V alarms on the DS3XM-6 or DS3XM-12 cards.
1-128
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.11.3 Circuit Creation Error with VT1.5 Circuit
1.11.3 Circuit Creation Error with VT1.5 Circuit
Symptom You receive an “Error while finishing circuit creation. Unable to provision circuit. Unable to create connection object at node_name ” message when trying to create a VT1.5 circuit in CTC.
Possible Cause You might have run out of bandwidth on the VT cross-connect matrix at the
ONS 15454 indicated in the error message.
Recommended Action The matrix has a maximum capacity of 336 bidirectional VT1.5 cross-connects. Certain configurations exhaust VT capacity with less than 336 bidirectional VT1.5s in a BLSR or less than 224 bidirectional VT1.5s in a path protection or 1+1 protection group. Refer to the “Circuits and Tunnels” chapter in the Cisco ONS 15454 Reference Manual for more information.
1.11.4 Unable to Create Circuit From DS-3 Card to DS3XM-6 or DS3XM-12 Card
Symptom You cannot create a circuit from a DS-3 card to a DS3XM-6 or DS3XM-12 card.
Possible Cause A DS-3 card and a DS3XM-6 or DS3XM-12 card have different functions.
Recommended Action A DS3XM-6 card converts each of its six DS-3 interfaces into 28 DS-1s for cross-connection through the network. The DS3XM-12 converts each of its 12 interfaces into up to
48 DS-1s. Thus, you can create a circuit from a DS3XM-6 or DS3XM-12 card to a DS-1 card, but not from a DS3XM card to a DS-3 card. These differences are evident in the STS path overhead. The
DS-3 card uses asynchronous mapping for DS-3, which is indicated by the C2 byte in the STS path overhead that has a hex code of 04. A DS3XM-6 or DS3XM-12 has a VT payload with a C2 hex value of 02.
Note You can find instructions for creating circuits in the “Create Circuits and VT Tunnels” chapter of the Cisco ONS 15454 Procedure Guide .
1.11.5 DS-3 Card Does Not Report AIS-P From External Equipment
Symptom A DS3-12, DS3N-12, DS3-12E, or DS3N-12E card does not report STS AIS-P from the external equipment/line side.
Possible Cause The card is functioning as designed.
Recommended Action This card terminates the port signal at the backplane so STS AIS-P is not reported from the external equipment/line side. DS3-12, DS3N-12, DS3-12E, and DS3N-12E cards have DS3 header monitoring functionality, which allows you to view PM on the DS3 path.
Nevertheless, you cannot view AIS-P on the STS path. For more information about the PM capabilities of the DS3-12, DS3N-12, DS3-12E or DS3N-12E cards, refer to the “Performance
Monitoring” chapter in the Cisco ONS 15454 Reference Manual .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-129
Chapter 1 General Troubleshooting
1.11.6 OC-3 and DCC Limitations
1.11.6 OC-3 and DCC Limitations
Symptom Limitations to OC-3 and DCC usage.
Possible Cause OC-3 and DCC have limitations for the ONS 15454.
Recommended Action For an explanation of OC-3 and DCC limitations, refer to the “Circuits and
Tunnels” chapter in the Cisco ONS 15454 Reference Manual .
1.11.7 ONS 15454 Switches Timing Reference
Symptom Timing references switch when one or more problems occur.
Possible Cause The optical or BITS input is receiving loss of signal (LOS), loss of frame (LOF), or
AIS alarms from its timing source.
Possible Cause The optical or building integrated timing supply (BITS) input is not functioning.
Possible Cause The synchronization status messaging (SSM) message is set to Do Not Use for
Synchronization (DUS).
Possible Cause SSM indicates a Stratum 3 or lower clock quality.
Possible Cause The input frequency is off by more than 15 ppm.
Possible Cause The input clock wanders and has more than three slips in 30 seconds.
Possible Cause A bad timing reference existed for at least two minutes.
Recommended Action The ONS 15454 internal clock operates at a Stratum 3E level of accuracy. This gives the ONS 15454 a free-running synchronization accuracy of +/– 4.6 ppm and a holdover stability of less than 255 slips in the first 24 hours or 3.7 x 10
–7
/day, including temperature.
ONS 15454 free-running synchronization relies on the Stratum 3 internal clock. Over an extended time period, using a higher quality Stratum 1 or Stratum 2 timing source results in fewer timing slips than a lower quality Stratum 3 timing source.
1.11.8 Holdover Synchronization Alarm
Symptom The clock is running at a different frequency than normal and the
appears.
Possible Cause The last reference input has failed.
Recommended Action The clock is running at the frequency of the last known-good reference input.
This alarm is raised when the last reference input fails. See the “HLDOVRSYNC” alarm on page 2-121
for a detailed description.
1-130
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.11.9 Free-Running Synchronization Mode
Note The ONS 15454 supports holdover timing per Telcordia GR-436 when provisioned for external
(BITS) timing.
1.11.9 Free-Running Synchronization Mode
Symptom The clock is running at a different frequency than normal and the
appears.
Possible Cause No reliable reference input is available.
Recommended Action The clock is using the internal oscillator as its only frequency reference. This occurs when no reliable, prior timing reference is available. See the
“FRNGSYNC” condition on page 2-110
for a detailed description.
1.11.10 Daisy-Chained BITS Not Functioning
Symptom You are unable to daisy chain the BITS sources.
Possible Cause Daisy-chained BITS sources are not supported on the ONS 15454.
Recommended Action Daisy-chained BITS sources cause additional wander buildup in the network and are therefore not supported. Instead, use a timing signal generator to create multiple copies of the BITS clock and separately link them to each ONS 15454.
1.11.11 Blinking STAT LED after Installing a Card
Symptom After installing a card, the STAT LED blinks continuously for more than 60 seconds.
Possible Cause The card cannot boot because it failed the Power On Shelf Test (POST) diagnostics.
Recommended Action The blinking STAT LED indicates that POST diagnostics are being performed.
If the LED continues to blink more than 60 seconds, the card has failed the POST diagnostics test
with an “Equipment Failure” description. Check the alarm tab for this alarm to appear for the slot where the card was installed. To attempt recovery, remove and reinstall the card and observe the card boot process. If the card fails to boot, replace the card. Complete the
Card” procedure on page 2-266 .
1.12 Fiber and Cabling
This section explains problems typically caused by cabling connectivity errors. It also includes instructions for crimping Category-5 cable and lists the optical fiber connectivity levels.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-131
Chapter 1 General Troubleshooting
1.12.1 Bit Errors Appear for a Traffic Card
1.12.1 Bit Errors Appear for a Traffic Card
Symptom A traffic card has multiple bit errors.
Possible Cause Faulty cabling or low optical-line levels.
Recommended Action Bit errors on line (traffic) cards usually originate from cabling problems or low optical-line levels. The errors can be caused by synchronization problems, especially if pointer justification (PJ) errors are reported. Moving cards into different error-free slots will isolate the cause. Use a test set whenever possible because the cause of the errors could be external cabling, fiber, or external equipment connecting to the ONS 15454. Troubleshoot low optical levels using the
“1.12.2 Faulty Fiber-Optic Connections” section on page 1-132
.
1.12.2 Faulty Fiber-Optic Connections
Symptom A line card has multiple SONET/DWDM alarms and/or signal errors.
Possible Cause Faulty fiber-optic connections.
Recommended Action Faulty fiber-optic connections can be the source of SONET/DWDM alarms and signal errors. Complete the
“Verify Fiber-Optic Connections” procedure on page 1-132 .
Possible Cause Faulty Category-5 cables.
Recommended Action Faulty Category-5 cables can be the source of SONET/DWDM alarms and signal errors. Complete the
“1.12.2.1 Crimp Replacement LAN Cables” section on page 1-134
.
Possible Cause Faulty GBICs.
Recommended Action Faulty GBICs can be the source of SONET/DWDM alarms and signal errors.
See the
“1.12.2.2 Replace Faulty GBIC, SFP, or XFP Connectors” section on page 1-136
.
Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments. Statement 272
Warning Laser radiation presents an invisible hazard, so personnel should avoid exposure to the laser beam.
Personnel must be qualified in laser safety procedures and must use proper eye protection before working on this equipment. Statement 300
Verify Fiber-Optic Connections
Step 1 Ensure that a single-mode fiber connects to the ONS 15454 OC-N card.
Note SM or SM Fiber should be printed on the fiber span cable. ONS 15454 OC-N cards do not use multimode fiber.
1-132
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
Step 2
Step 3
Step 4
Ensure that the connector keys on the SC fiber connector are properly aligned and locked.
Check that the single-mode fiber power level is within the specified range: a.
Remove the Rx end of the suspect fiber.
b.
c.
d.
Connect the Rx end of the suspect fiber to a fiber-optic power meter, such as a GN Nettest LP-5000.
Determine the power level of fiber with the fiber-optic power meter.
e.
Verify that the power meter is set to the appropriate wavelength for the OC-N card being tested
(either 1310 nm or 1550 nm depending on the specific card).
Verify that the power level falls within the range specified for the card if it is an OC-N card; see the
“1.12.3 OC-N Card Transmit and Receive Levels” section on page 1-140 .
If the power level falls below the specified range for the OC-N card: a.
Clean or replace the fiber patch cords. Clean the fiber according to site practice or, if none exists, follow the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If possible, do this for the OC-N card you are working on and the far-end card.
b.
c.
Clean the optical connectors on the card. Clean the connectors according to site practice or, if none exists, follow the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure
Guide . If possible, do this for the OC-N card you are working on and the far-end card.
Ensure that the far-end transmitting card is not an ONS intermediate-range (IR) card when an ONS long-range (LR) card is appropriate.
d.
IR cards transmit a lower output power than LR cards.
Replace the far-end transmitting OC-N card to eliminate the possibility of a degrading transmitter on this OC-N card.
Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the procedures in the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254 . For more
information, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide . e.
If the power level still falls below the specified range with the replacement fibers and replacement card, check for one of these three factors that attenuate the power level and affect link loss (LL):
• Excessive fiber distance; single-mode fiber attenuates at approximately 0.5 dB/km.
•
•
Excessive number or fiber connectors; connectors take approximately 0.5 dB each.
Excessive number of fiber splices; splices take approximately 0.5 dB each.
Note These are typical attenuation values. Refer to the specific product documentation for the actual values or use an optical time domain reflectometer (OTDR) to establish precise link loss and budget requirements.
Step 5 If no power level shows on the fiber, the fiber is bad or the transmitter on the OC-N card failed.
a.
b.
Check that the Tx and Rx fibers are not reversed. LOS and EOC alarms normally accompany reversed Tx and Rx fibers. Switching reversed Tx and Rx fibers clears the alarms and restores the signal.
Clean or replace the fiber patch cords. Clean the fiber according to site practice or, if none exists, follow the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If possible, do this for the OC-N card you are working on and the far-end card.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-133
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections c.
d.
Retest the fiber power level.
If the replacement fiber still shows no power, replace the OC-N card.
Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the procedures in the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254
. For more information, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
Step 6 If the power level on the fiber is above the range specified for the card, ensure that an ONS LR card is not being used when an ONS IR card is appropriate.
LR cards transmit a higher output power than IR cards. When used with short runs of fiber, an LR transmitter is too powerful for the receiver on the receiving OC-N card.
Receiver overloads occur when maximum receiver power is exceeded.
Tip To prevent overloading the receiver, use an attenuator on the fiber between the ONS OC-N card transmitter and the receiver. Place the attenuator on the receive transmitter of the ONS OC-N 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.12.2.1 Crimp Replacement LAN Cables
You can crimp your own LAN cables for use with the ONS 15454. Use a cross-over cable when connecting an ONS 15454 to a hub, LAN modem, or switch, and use a LAN cable when connecting an
ONS 15454 to a router or workstation. Use Category-5 cable RJ-45 T-568B, Color Code (100 Mbps), and a crimping tool.
Figure 1-50 shows the wiring of an RJ-45 connector.
cable layout, and
Table 1-4 shows the cable pinouts. Figure 1-52
shows a cross-over cable layout, and
Table 1-5 shows the cross-over pinouts.
Figure 1-50 RJ-45 Pin Numbers
8 7 6 5 4 3 2 1 1 2 3 4 5 6 7 8
End view of RJ-45 plug
1-134
Cisco ONS 15454 Troubleshooting Guide, R7.2
Looking into an RJ-45 jack
November 2009
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
November 2009
Figure 1-51 LAN Cable Layout
5
6
7
8
1
2
3
4
Table 1-4
6
7
8
4
5
2
3
Pin
1
LAN Cable Pinout
Color white/orange orange white/green blue white/blue green white/brown brown
3
4
4
1
1
2
3
Pair
2
Name
Transmit Data +
Transmit Data –
Receive Data +
—
—
Receive Data –
—
—
5
6
7
8
1
2
3
4
Figure 1-52 Cross-Over Cable Layout
7
8
5
6
3
4
1
2
Table 1-5
2
3
4
5
6
Pin
1
Cross-Over Cable Pinout
Color white/orange orange white/green blue white/blue green
Pair
2
2
3
1
1
3
Name
Transmit Data +
Transmit Data –
Receive Data +
—
—
Receive Data –
7
8
5
6
3
4
1
2
6
1
4
5
2
Pin
3
6
7
8
4
5
2
3
Pin
1
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-135
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
Table 1-5
Pin
7
8
Cross-Over Cable Pinout (continued)
Color white/brown brown
Pair
4
4
Name
—
—
Pin
7
8
Note Odd-numbered pins always connect to a white wire with a colored stripe.
1.12.2.2 Replace Faulty GBIC, SFP, or XFP Connectors
GBICs and Small Form-factor Pluggables (SFP or XFP) are hot-swappable and can be installed or removed while the card or shelf assembly is powered and running.
Warning Class 1 laser product. Statement 1008
Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments. Statement 272
GBICs and SFPs/XFPs are input/output devices that plug into a Gigabit Ethernet card to link the port with the fiber-optic network. The type of GBIC or SFP determines the maximum distance that the
Ethernet traffic can travel from the card to the next network device. For a description of GBICs and SFPs and their capabilities refer to the Cisco ONS 15454 Reference Manual .
Note GBICs and SFPs must be matched on either end by type: SX to SX, LX to LX, or ZX to ZX.
Note All versions of G1K-4 cards support coarse wavelength division multiplexing (CWDM) GBICs.
GBICs are available in two different models. One GBIC model has two clips (one on each side of the
GBIC) that secure the GBIC in the slot on the E1000-2-G, G-Series, or G1K-4 card. The other model has a locking handle. Both models are shown in
.
Figure 1-53 GBICs
Receiver
Transmitter
Clip
Receiver
Transmitter
Handle
1-136
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
Note GBICs are very similar in appearance. Check the GBIC label carefully before installing it.
Remove GBIC, SFP, or XFP Connectors
Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments. Statement 272
Step 1
Step 2
Step 3
Disconnect the network fiber cable from the GBIC SC connector or XFP/SFP LC duplex connector.
Release the GBIC or SFP/XFP from the slot by simultaneously squeezing the two plastic tabs on each side.
Slide the GBIC or SFP/XFP out of the Gigabit Ethernet module slot. A flap closes over the GBIC or SFP slot to protect the connector on the Gigabit Ethernet card.
Install a GBIC or SFP/XFP Device
Warning Class 1 laser product. Statement 1008
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Note G-Series cards manufactured before August 2003 do not support DWDM GBICs. G1K-4 cards compatible with DWDM GBICs have a Common Language Equipment Identification (CLEI) code of
WM5IRWPCAA.
Note All versions of G1K-4 cards support coarse wavelength division multiplexing (CWDM) GBICs.
Note GBICs, SFPs, and XFPs are hot-swappable and can therefore be installed/removed while the card/shelf assembly is powered and running.
Step 1
Step 2
Remove the GBIC, SFP, or XFP from its protective packaging.
Check the label to verify that the GBIC, SFP, or XFP is the correct type for your network.
shows the available GBICs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-137
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
Note The GBICs are very similar in appearance. Check the GBIC label carefully before installing it.
Table 1-6 Available GBICs
GBIC
Associated
Cards
1000BaseSX E1000-2-G
G1K-4
CE-1000-4
Application
Short reach
FC_MR-4 Long reach
Fiber
Multimode fiber up to 550 m long
1000BaseLX E1000-2-G
G1K-4
CE-1000-4
1000BaseZX G1K-4
CE-1000-4
Long reach
Extra long reach
Single-mode fiber up to
5 km long
Single-mode fiber up to
70 km long
Product Number
15454E-GBIC-SX=
15454-GBIC-SX
ONS-GC-GE-SX
15454E-GBIC-LX=
15454-GBIC-LX
ONS-GC-GE-LX
15454E-GBIC-ZX=
15454-GBIC-ZX
ONS-GC-GE-ZX
Single-mode fiber, 1310 nm ONS-GX-2FC-SML=
FC_MR-4 Intermediate reach Multimode fiber, 850 nm ONS-GX-2FC-MMI=
Table 1-7 shows the available SFPs and XFPs.
Table 1-7 Available SFPs and XFPs
SFP/XFP
Associated
Cards
1000BaseSX ML1000-2
Application
Short reach
1000BaseLX
1000BaseFX ML100X-8
1000BaseLX-
10
Long reach
Short reach
Intermediate reach
Fiber
Multimode fiber up to
550 m long
Product Number
15454E-SFP-LC-SX=
Single-mode fiber up to
5 km long
1310 nm multimode fiber up to 2 km long
15454E-SFP-LC-LX=
ONS-SE-100-FX
1310 nm, single mode fiber, up to 15 km long
ONS-SE-100-LX10
1-138
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.12.2 Faulty Fiber-Optic Connections
Table 1-7
SFP/XFP
OC-48 SR
OC-48 IR1
OC-48 LR1
OC-48 LR2
OC-48 LR2
DWDM
OC-3/OC-12
IR1 dual rate
OC-12 LR1
OC-12 LR2
OC-12
CWDM
OC-3 IR1
OC-3 LR1
OC-3 LR2
OC-3 CWDM
Available SFPs and XFPs (continued)
Associated
Cards
MRC-12
Application
Short reach
MRC-12
(cont.)
Intermediate reach
Long reach
Long reach
Long reach
Intermediate reach
Long reach
Long reach
Long reach
Intermediate reach
Long reach
Long reach
Long reach
Fiber
1310-nm single-mode fiber up to 2 km long
1310-nm single-mode fiber, up to 15 km long
1310-nm single-mode fiber up to 40 km long
1550-nm single-mode fiber up to 80 km long
1530.33 to 1560.61 nm single-mode fiber up to
120 km long
1310-nm single-mode fiber up to 15 km long
1310-nm single-mode fiber up to 40 km long
1550-nm single-mode fiber up to 80 km long
1470 to 1610 nm single-mode fiber up to
80 km long
1310-nm single-mode fiber up to 15 km long
1310-nm single-mode fiber up to 40 km long
1550-nm single-mode fiber up to 80 km long
1470 to 1610 nm single-mode fiber up to
80 km long
1310-nm single-mode fiber up to 10 km long
Product Number
ONS-SI-2G-S1
ONS-SI-2G-I1
ONS-SI-2G-L1
ONS-SI-2G-L2
ONS-SC-2G-30.3 through
ONS-SC-2G-60.6
ONS-SI-622-I1
ONS-SI-622-L1
ONS-SI-622-L2
ONS-SE-622-1470 through
ONS-SE-622-1610
ONS-SI-155-I1
ONS-SI-155-L1
ONS-SI-155-L2
ONS_SE-155-1470 through
ONS-SE-155-1610
ONS-XC-10G-S1 OC-192 SR1 OC192SR1/
STM64IO
Short Reach
1
OC-192 SR1,
IR1, LR2
OC192/
STM64 Any
Reach
1
Short reach
Short reach
Intermediate reach
Long reach
1310-nm single-mode fiber up to 10 km long
1550-nm single-mode fiber up to 15 km long
1550-nm single-mode fiber up to 80 km long
ONS-XC-10G-S1
ONS-XC-10G-I2
ONS-XC-10G-L2
1.
CTC refers to this card as OC192-XFP
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-139
Chapter 1 General Troubleshooting
1.12.3 OC-N Card Transmit and Receive Levels
Step 3
Step 4
Note Before you install SFPs on the MRC-12 card, refer to the MRC-12 card information in the
Cisco ONS 15454 Reference Manual for bandwidth restrictions based on the port where you install the SFP and the cross-connect card being used.
Verify the type of GBIC, SFP, or XFP you are using:
•
•
•
If you are using a GBIC with clips, go to
.
If you are using a GBIC with a handle, go to
If you are using an SFP or XFP, go to Step 6
.
.
For GBICs with clips: a.
Grip the sides of the GBIC with your thumb and forefinger and insert the GBIC into the slot on the card.
Note GBICs are keyed to prevent incorrect installation.
Step 5
Step 6 b.
c.
Slide the GBIC through the flap that covers the opening until you hear a click. The click indicates the GBIC is locked into the slot.
When you are ready to attach the network fiber-optic cable, remove the protective plug from the
GBIC, save the plug for future use, then plug the fiber connector into the GBIC.
For GBICs with a handle: a.
Remove the protective plug from the SC-type connector.
b.
c.
d.
Grip the sides of the GBIC with your thumb and forefinger and insert the GBIC into the slot on the card.
Lock the GBIC into place by closing the handle down. The handle is in the correct closed position when it does not obstruct access to an SC-type connector.
Slide the GBIC through the cover flap until you hear a click.
The click indicates that the GBIC is locked into the slot.
e.
When you are ready to attach the network fiber-optic cable, remove the protective plug from the
GBIC, save the plug for future use, then plug the fiber connector into the GBIC.
For SFPs and XFPs: a.
b.
c.
Plug the LC duplex connector of the fiber into a Cisco-supported SFP or XFP.
If the new SFP or XFP has a latch, close the latch over the cable to secure it.
Plug the cabled SFP or XFP into the card port until it clicks.
1.12.3 OC-N Card Transmit and Receive Levels
Each OC-N card has a transmit and receive connector on its faceplate.
lists these levels.
1-140
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.12.3 OC-N Card Transmit and Receive Levels
November 2009
Table 1-8 Optical Card Transmit and Receive Levels
Card
Transmit Receive
Minimum Maximum Minimum
OC3 IR 4/STM1 SH 1310
OC3IR/STM1SH 1310-8
OC12 IR/STM4 SH 1310
OC12 LR/STM4 LH 1310
OC12 LR/STM4 LH 1550
OC12 IR/STM4 SH 1310-4
OC48 IR 1310
OC48 LR 1550
OC48 IR/STM16 SH AS 1310
OC48 LR/STM16 LH AS 1550
OC48 ELR/STM16 EH 100 GHz
OC48 ELR/STM16 EH 200 GHz
OC192 SR/STM64 IO 1310
OC192 IR/STM64 SH 1550
–15 dBm
–15 dBm
–15 dBm
–3 dBm
–3 dBm
–15 dBm
–5 dBm
–2 dBm
–8 dBm
–8 dBm
–8 dBm
+2 dBm
+2 dBm
–8 dBm
0 dBm
+3 dBm
–5 dBm 0 dBm
–2 dBm +3 dBm
–2 dBm 0 dBm
–2 dBm 0 dBm
–6 dBm –1 dBm
–1 dBm +2 dBm
–28 dBm
–28 dBm
–28 dBm
–28 dBm
–28 dBm
–30 dBm
–18 dBm
–28 dBm
–18 dBm
–28 dBm
–27 dBm at
1E-12 BER
–28 dBm
–11 dBm
–14 dBm
OC192 LR/STM64 LH 1550 +7 dBm +10 dBm –19 dBm
OC192 LR/STM64 LH ITU 15xx.xx +3 dBm +6 dBm –22 dBm
15454_MRC-12 (ONS-SI-2G-S1) –10 dBm –3 dBm
15454_MRC-12 (ONS-SI-2G-I1) –5 dBm 0 dBm
–18 dBm
–18 dBm
–27 dBm
–28 dBm
–28 dBm
15454_MRC-12 (ONS-SI-2G-L1) –2 dBm 3 dBm
15454_MRC-12 (ONS-SI-2G-L2) –2 dBm 3 dBm
15454_MRC-12 (ONS-SC-2G-30.3 through ONS-SC-2G-60.6)
0 dBm 4 dBm
15454_MRC-12 (ONS-SI-622-I1) –15 dBm –8 dBm
15454_MRC-12 (ONS-SI-622-L1) –3 dBm 2 dBm
15454_MRC-12 (ONS-SI-622-L2) –3 dBm 2 dBm
15454_MRC-12
(ONS-SE-622-1470 through
ONS-SE-622-1610)
0 dBm 5 dBm
15454_MRC-12 (ONS-SI-155-I1) –15 dBm –8 dBm
–28 dBm
–28 dBm
–28 dBm
–28 dBm
15454_MRC-12 (ONS-SI-155-L1)
15454_MRC-12 (ONS-SI-155-L2)
15454_MRC-12
(ONS_SE-155-1470 through
ONS-SE-155-1610)
OC192SR1/STM64IO Short Reach
(ONS-XC-10G-S1)
–5 dBm
–5 dBm
0 dBm
–6 dBm
0 dBm
0 dBm
5 dBm
–1 dBm
–30 dBm
–34 dBm
–34 dBm
–34 dBm
–11 dBm
–8 dBm
–10 dBm
–10 dBm
–3 dBm
–1 dBm
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-141
–8 dBm
–1 dBm
–1 dBm
–10 dBm
–9 dBm
–3 dBm
0 dBm
–9 dBm
–9 dBm
–9 dBm
–8 dBm
–8 dBm
–8 dBm
–3 dBm
Maximum
–8 dBm
–8 dBm
–8 dBm
–8 dBm
–8 dBm
–8 dBm
0 dBm
–8 dBm
0 dBm
–8 dBm
–9 dBm
Chapter 1 General Troubleshooting
1.13 Power Supply Problems
Table 1-8
Card
Optical Card Transmit and Receive Levels (continued)
OC192/STM64 Any Reach
(ONS-XC-10G-S1)
OC192/STM64 Any Reach
(ONS-XC-10G-I2)
OC192/STM64 Any Reach
(ONS-XC-10G-L2)
Transmit Receive
Minimum Maximum Minimum
–6 dBm –1 dBm –11 dBm
–1 dBm
0 dBm
2 dBm
4 dBm
–14 dBm
–24 dBm
1.13 Power Supply Problems
Maximum
–1 dBm
2 dBm
–7dBm
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.
Possible Cause Loss of power or low voltage.
Possible Cause Improperly connected power supply.
Recommended Action The ONS 15454 requires a constant source of DC power to properly function.
Input power is –48 VDC. Power requirements range from –42 VDC to –57 VDC. A newly installed
ONS 15454 that is not properly connected to its power supply does not operate. Power problems can be confined to a specific ONS 15454 or affect several pieces of equipment on the site. A loss of power or low voltage can result in a loss of traffic and causes the LCD clock on the ONS 15454 to default to January 1, 1970, 00:04:15. To reset the clock, in node view click the
Provisioning > General > General tabs and change the Date and Time fields. Complete the
“Isolate the Cause of Power Supply Problems” procedure on page 1-142
.
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Caution Operations that interrupt power supply or short the power connections to the ONS 15454 are service-affecting.
Isolate the Cause of Power Supply Problems
Step 1 If a single ONS 15454 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.
1-142
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 1 General Troubleshooting
1.13.1 Power Consumption for Node and Cards
Step 2 d.
e.
b.
c.
f.
g.
h.
Verify that the power cable is #12 or #14 AWG and in good condition.
Verify that the power cable connections are properly crimped. Stranded #12 or #14 AWG does not always crimp properly with Staycon type connectors.
Verify that 20-A fuses are used in the fuse panel.
Verify that the fuses are not blown.
Verify that a rack-ground cable attaches to the frame-ground terminal (FGND) on the right side of the ONS 15454 EIA. Connect this cable to the ground terminal according to local site practice.
Verify that the DC power source has enough capacity to carry the power load.
If the DC power source is battery-based:
•
•
•
•
Check that the output power is high enough. Power requirements range from –42 VDC to
–57 VDC.
Check the age of the batteries. Battery performance decreases with age.
Check for opens and shorts in batteries, which might affect power output.
If brownouts occur, the power load and fuses might be too high for the battery plant.
If multiple pieces of site equipment show signs of fluctuating power or power loss: a.
Check the uninterruptible power supply (UPS) or rectifiers that supply the equipment. Refer to the
UPS manufacturer’s documentation for specific instructions.
b.
c.
Check for excessive power drains caused by other equipment, such as generators.
Check for excessive power demand on backup power systems or batteries when alternate power sources are used.
1.13.1 Power Consumption for Node and Cards
Symptom You are unable to power up a node or the cards in a node.
Possible Cause Improper power supply.
Recommended Action Refer to power information in the “Hardware Specifications” appendix in the
Cisco ONS 15454 Reference Manual .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
1-143
1.13.1 Power Consumption for Node and Cards
Chapter 1 General Troubleshooting
1-144
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
C H A P T E R
2
Alarm Troubleshooting
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration.
Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables
provide lists of ONS 15454 alarms organized by severity.
provides a list of alarms organized alphabetically.
gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in
. For a comprehensive list of all conditions and instructions for using TL1 commands, refer to the Cisco ONS SONET TL1 Command Guide .
An alarm’s troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log into the Technical
Support Website at http://www.cisco.com/techsupport for more information or call the Cisco Technical
Assistance Center 1 800 553-2447.
For more information about alarm profiles, refer to the “Manage Alarms” chapter in the
Cisco ONS 15454 Procedure Guide .
2.1 Alarm Indexes by Default Severity
The following tables group alarms and conditions by their default severities in the ONS 15454 system.
These severities are the same whether they are reported in the CTC Alarms window severity (SEV) column or in TL1.
Note The CTC default alarm profile contains some alarms or conditions that are not currently implemented but are reserved for future use.
Note The CTC default alarm profile in some cases contains two severities for one alarm (for example,
MJ/MN). The ONS 15454 platform default severity comes first (in this example, MJ), but the alarm can be demoted to the second severity in the presence of a higher-ranking alarm. This is in accordance with
Telcordia GR-474.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-1
Chapter 2 Alarm Troubleshooting
2.1.1 Critical Alarms (CR)
2.1.1 Critical Alarms (CR)
Table 2-1
Table 2-1 alphabetically lists ONS 15454 Critical (CR) alarms.
ONS 15454 Critical Alarm List
AUTOLSROFF (OCN)
AWG-FAIL (OTS)
AWG-OVERTEMP (OTS)
BKUPMEMP (EQPT)
COMIOXC (EQPT)
CONTBUS-DISABLED (EQPT)
CTNEQPT-PBPROT (EQPT)
CTNEQPT-PBWORK (EQPT)
ENCAP-MISMATCH-P (STSTRM)
EQPT (AICI-AEP)
EQPT (AICI-AIE)
EQPT (EQPT)
EQPT (PPM)
EQPT-DIAG (EQPT)
EQPT-MISS (FAN)
FAN (FAN)
GAIN-HFAIL (AOTS)
GAIN-LFAIL (AOTS)
GE-OOSYNC (FC)
GE-OOSYNC (GE)
GE-OOSYNC (ISC)
GE-OOSYNC (TRUNK)
HITEMP (NE)
I-HITEMP (NE)
IMPROPRMVL (EQPT)
IMPROPRMVL (PPM)
LINK-KEEPALIVE (ML1000)
LINK-KEEPALIVE (ML100T)
LINK-KEEPALIVE (MLFX)
LOA (VCG)
LOF (DS3)
LOF (E1)
LOF (OCN)
LOF (STSTRM)
LOF (TRUNK)
LOM (STSMON)
LOM (STSTRM)
LOM (TRUNK)
LOP-P (STSMON)
LOP-P (STSTRM)
LOS (2R)
LOS (DS3)
LOS (E1)
LOS (ESCON)
LOS (ISC)
LOS (OCN)
LOS (OTS)
LOS (TRUNK)
LOS-P (OCH)
LOS-P (OMS)
LOS-P (OTS)
LOS-P (TRUNK)
MEA (AIP)
MEA (BIC)
MEA (EQPT)
MEA (FAN)
MEA (PPM)
MFGMEM (AICI-AEP)
MFGMEM (AICI-AIE)
MFGMEM (AIP)
MFGMEM (BPLANE)
MFGMEM (FAN)
MFGMEM (PPM)
OPWR-HFAIL (AOTS)
OPWR-HFAIL (OCH)
OPWR-HFAIL (OMS)
OPWR-HFAIL (OTS)
OPWR-LFAIL (AOTS)
OPWR-LFAIL (OCH)
OPWR-LFAIL (OMS)
OPWR-LFAIL (OTS)
OTUK-LOF (TRUNK)
OTUK-TIM (TRUNK)
PLM-P (STSMON)
PLM-P (STSTRM)
PORT-ADD-PWR-FAIL-HIGH (OCH)
PORT-ADD-PWR-FAIL-LOW (OCH)
PORT-FAIL (OCH)
SQM (STSTRM)
SWMTXMOD-PROT (EQPT)
SWMTXMOD-WORK (EQPT)
TIM (OCN)
TIM (TRUNK)
TIM-P (STSTRM)
TIM-S (E1)
TIM-S (OCN)
UNEQ-P (STSMON)
UNEQ-P (STSTRM)
VOA-HFAIL (AOTS)
VOA-HFAIL (OCH)
VOA-HFAIL (OMS)
VOA-HFAIL (OTS)
VOA-LFAIL (AOTS)
VOA-LFAIL (OCH)
VOA-LFAIL (OMS)
VOA-LFAIL (OTS)
2-2
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.1.2 Major Alarms (MJ)
2.1.2 Major Alarms (MJ)
Table 2-2
alphabetically lists ONS 15454 Major (MJ) alarms.
ONS 15454 Major Alarm List
APSCM (OCN)
APSCNMIS (OCN)
AUTONEG-RFI (ML1000)
BAT-FAIL (PWR )
BLSROSYNC (OCN)
GFP-EX-MISMATCH (GFP-FAC)
GFP-LFD (CE100T)
GFP-LFD (CE1000)
GFP-LFD (FCMR)
GFP-LFD (GFP-FAC)
CARLOSS (CE100T)
CARLOSS (CE1000)
CARLOSS (E1000F)
CARLOSS (E100T)
CARLOSS (EQPT)
CARLOSS (FC)
CARLOSS (G1000)
CARLOSS (GE)
CARLOSS (ISC)
CARLOSS (ML1000)
CARLOSS (ML100T)
CARLOSS (MLFX)
CARLOSS (TRUNK)
DATA-CRC (CE100T)
DATA-CRC (ML1000)
DATA-CRC (ML100T)
DATA-CRC (MLFX)
DBOSYNC (NE)
DSP-COMM-FAIL (TRUNK)
DSP-FAIL (TRUNK)
DUP-SHELF-ID (SHELF)
EHIBATVG (PWR )
ELWBATVG (PWR )
E-W-MISMATCH (OCN)
EXTRA-TRAF-PREEMPT (OCN)
FC-NO-CREDITS (FC)
FC-NO-CREDITS (FCMR)
FC-NO-CREDITS (TRUNK)
GFP-LFD (ML1000)
GFP-LFD (ML100T)
GFP-LFD (MLFX)
GFP-NO-BUFFERS (FCMR)
GFP-NO-BUFFERS (GFP-FAC)
GFP-UP-MISMATCH (CE1000)
GFP-UP-MISMATCH (CE100T)
GFP-UP-MISMATCH (FCMR)
GFP-UP-MISMATCH (GFP-FAC)
GFP-UP-MISMATCH (ML1000)
GFP-UP-MISMATCH (ML100T)
GFP-UP-MISMATCH (MLFX)
HIBATVG (PWR )
INVMACADR (AIP)
LASERBIAS-FAIL (AOTS)
LOF (DS1)
LOF (E1)
LOM (VT-TERM)
LOP-V (VT-MON)
LOP-V (VT-TERM)
LOS (DS1)
LOS (E1)
LWBATVG (PWR )
MAX-STATIONS (RPRIF)
MEA (SHELF)
MEM-GONE (EQPT)
ODUK-TIM-PM (TRUNK)
OPTNTWMIS (NE)
RING-ID-MIS (OCN)
RING-ID-MIS (OSC-RING)
RING-MISMATCH (OCN)
RPR-PEER-MISS (RPRIF)
RPR-PROT-CONFIG-MISMATCH
(RPRIF)
RPR-RI-FAIL (RPRIF)
RPR-SPAN-MISMATCH (ML1000)
RPR-SPAN-MISMATCH (ML100T)
RPR-SPAN-MISMATCH (MLFX)
SHELF-COMM-FAIL (SHELF)
SIGLOSS (ESCON)
SIGLOSS (FC)
SIGLOSS (FCMR)
SIGLOSS (GE)
SIGLOSS (ISC)
SIGLOSS (TRUNK)
SQM (VT-TERM)
SYNCLOSS (FC)
SYNCLOSS (FCMR)
SYNCLOSS (GE)
SYNCLOSS (ISC)
SYNCLOSS (TRUNK)
SYNCPRI (NE-SREF)
SYSBOOT (NE)
TIM-V (VT-TERM)
TPTFAIL (CE1000)
TPTFAIL (CE100T)
TPTFAIL (FCMR)
TPTFAIL (G1000)
TPTFAIL (ML1000)
TPTFAIL (ML100T)
TPTFAIL (MLFX)
TRMT (DS1)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-3
Chapter 2 Alarm Troubleshooting
2.1.3 Minor Alarms (MN)
Table 2-2 ONS 15454 Major Alarm List (continued)
FEC-MISM (TRUNK)
GFP-CSF (CE100T)
GFP-CSF (CE1000)
GFP-CSF (FCMR)
GFP-CSF (GFP-FAC)
GFP-CSF (ML1000)
GFP-CSF (ML100T)
GFP-CSF (MLFX)
GFP-DE-MISMATCH (FCMR)
GFP-DE-MISMATCH (GFP-FAC)
GFP-EX-MISMATCH (CE1000)
GFP-EX-MISMATCH (FCMR)
OUT-OF-SYNC (FC)
OUT-OF-SYNC (GE)
OUT-OF-SYNC (TRUNK)
PEER-NORESPONSE (EQPT)
PLM-V (VT-TERM)
PRC-DUPID (OCN)
PROV-MISMATCH (TRUNK)
PTIM (TRUNK)
RCVR-MISS (DS1)
RCVR-MISS (E1)
RESERVED-RATE-EXCEEDED-RI
NGLET0 (RPRIF)
RESERVED-RATE-EXCEEDED-RI
NGLET1 (RPRIF)
—
TRMT (E1)
TRMT-MISS (DS1)
TRMT-MISS (E1)
UNEQ-V (VT-MON)
UNEQ-V (VT-TERM)
UT-COMM-FAIL (TRUNK)
UT-FAIL (TRUNK)
WVL-MISMATCH (TRUNK)
—
—
—
2.1.3 Minor Alarms (MN)
Table 2-3 alphabetically lists ONS 15454 Minor (MN) alarms.
Table 2-3 ONS 15454 Minor Alarm List
APSB (OCN)
APSCDFLTK (OCN)
APSC-IMP (OCN)
APSCINCON (OCN)
APSIMP (OCN)
APS-INV-PRIM (OCN)
APSMM (OCN)
APS-PRIM-SEC-MISM (OCN)
AUTORESET (EQPT)
AUTOSW-UNEQ (VT-MON)
AWG-DEG (OTS)
BLSR-SW-VER-MISM (OCN)
BPV (BITS)
CASETEMP-DEG (AOTS)
COMM-FAIL (EQPT)
CONTBUS-A-18 (EQPT)
CONTBUS-B-18 (EQPT)
HI-RXPOWER (OCN)
HITEMP (EQPT)
HI-TXPOWER (2R)
HI-TXPOWER (EQPT)
HI-TXPOWER (ESCON)
HI-TXPOWER (FC)
HI-TXPOWER (GE)
HI-TXPOWER (ISC)
HI-TXPOWER (OCN)
HI-TXPOWER (PPM)
ISIS-ADJ-FAIL (OCN)
ISIS-ADJ-FAIL (TRUNK)
KBYTE-APS-CHANNEL-FAILURE
(OCN)
LASERBIAS-DEG (AOTS)
LASERBIAS-DEG (OTS)
LASEREOL (OCN)
LASERTEMP-DEG (AOTS)
LO-TXPOWER (GE)
LO-TXPOWER (ISC)
LO-TXPOWER (OCN)
LO-TXPOWER (PPM)
LO-TXPOWER (TRUNK)
MEM-LOW (EQPT)
OPWR-HDEG (AOTS)
OPWR-HDEG (OCH)
OPWR-HDEG (OMS)
OPWR-HDEG (OTS)
OPWR-LDEG (AOTS)
OPWR-LDEG (OCH)
OPWR-LDEG (OMS)
OPWR-LDEG (OTS)
OTUK-IAE (TRUNK)
PORT-ADD-PWR-DEG-HI (OCH)
PORT-ADD-PWR-DEG-LOW (OCH)
2-4
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
Table 2-3 ONS 15454 Minor Alarm List (continued)
CONTBUS-IO-A (EQPT)
CONTBUS-IO-B (EQPT)
DATAFLT (NE)
DUP-IPADDR (NE)
DUP-NODENAME (NE)
EOC (OCN)
EOC (TRUNK)
EOC-L (OCN)
EOC-L (TRUNK)
ERROR-CONFIG (EQPT)
EXCCOL (EQPT)
LMP-FAIL (CTRL)
LMP-FAIL (GE)
LMP-FAIL (OCN)
LMP-FAIL (TLINK)
LMP-SD (GE)
LMP-SD (OCN)
LMP-SF (GE)
LMP-SF (OCN)
LMP-UNALLOC (GE)
LMP-UNALLOC (OCN)
LOF (BITS)
EXT (ENVALRM)
FEPRLF (OCN)
FIBERTEMP-DEG (AOTS)
GAIN-HDEG (AOTS)
GAIN-LDEG (AOTS)
GCC-EOC (TRUNK)
HI-LASERBIAS (2R)
HI-LASERBIAS (EQPT)
HI-LASERBIAS (ESCON)
HI-LASERBIAS (FC)
HI-LASERBIAS (GE)
HI-LASERBIAS (ISC)
HI-LASERBIAS (OCN)
HI-LASERBIAS (PPM)
HI-LASERTEMP (EQPT)
HI-LASERTEMP (OCN)
HI-LASERTEMP (PPM)
HI-RXPOWER (2R)
HI-RXPOWER (ESCON)
HI-RXPOWER (FC)
HI-RXPOWER (GE)
HI-RXPOWER (ISC)
LO-LASERBIAS (EQPT)
LO-LASERBIAS (OCN)
LO-LASERBIAS (PPM)
LO-LASERTEMP (EQPT)
LO-LASERTEMP (OCN)
LO-LASERTEMP (PPM)
LO-RXPOWER (2R)
LO-RXPOWER (ESCON)
LO-RXPOWER (FC)
LO-RXPOWER (GE)
LO-RXPOWER (ISC)
LO-RXPOWER (OCN)
LOS (BITS)
LOS (FUDC)
LOS (MSUDC)
LOS-O (OCH)
LOS-O (OMS)
LOS-O (OTS)
LO-TXPOWER (2R)
LO-TXPOWER (EQPT)
LO-TXPOWER (ESCON)
LO-TXPOWER (FC)
2.1.3 Minor Alarms (MN)
PROTNA (EQPT)
PROV-MISMATCH (PPM)
PWR-FAIL-A (EQPT)
PWR-FAIL-B (EQPT)
PWR-FAIL-RET-A (EQPT)
PWR-FAIL-RET-B (EQPT)
SFTWDOWN (EQPT)
SH-INS-LOSS-VAR-DEG-HIGH (OTS)
SH-INS-LOSS-VAR-DEG-LOW (OTS)
SNTP-HOST (NE)
SPANLENGTH-OUT-OF-RANGE
(OTS)
SSM-FAIL (BITS)
SSM-FAIL (DS1)
SSM-FAIL (E1)
SSM-FAIL (OCN)
SSM-FAIL (TRUNK)
SYNCPRI (EXT-SREF)
SYNCSEC (EXT-SREF)
SYNCSEC (NE-SREF)
SYNCTHIRD (EXT-SREF)
SYNCTHIRD (NE-SREF)
TIM-MON (OCN)
TIM-MON (TRUNK)
TIM-P (STSMON)
UNREACHABLE-TARGET-POWER
(OCH)
VOA-HDEG (AOTS)
VOA-HDEG (OCH)
VOA-HDEG (OMS)
VOA-HDEG (OTS)
VOA-LDEG (AOTS)
VOA-LDEG (OCH)
VOA-LDEG (OMS)
VOA-LDEG (OTS)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-5
Chapter 2 Alarm Troubleshooting
2.1.4 NA Conditions
2.1.4 NA Conditions
Table 2-4
Table 2-4 alphabetically lists ONS 15454 Not Alarmed (NA) conditions.
ONS 15454 NA Conditions List
ALS (2R)
ALS (AOTS)
ALS (ESCON)
ALS (FC)
ALS (GE)
ALS (ISC)
ALS (OCN)
ALS (TRUNK)
FRCDSWTOSEC (NE-SREF)
FRCDSWTOTHIRD (EXT-SREF)
FRCDSWTOTHIRD (NE-SREF)
FRNGSYNC (NE-SREF)
FSTSYNC (NE-SREF)
FULLPASSTHR-BI (OCN)
HELLO (OCN)
HELLO (TRUNK)
ALS-DISABLED (EQPT)
AMPLI-INIT (AOTS)
HI-CCVOLT (BITS)
HLDOVRSYNC (NE-SREF)
ANSWTOPRI (NE-SREF) INC-ISD (DS3)
APC-CORRECTION-SKIPPED (AOTS) INHSWPR (EQPT)
APC-CORRECTION-SKIPPED (OCH) INHSWWKG (EQPT)
APC-CORRECTION-SKIPPED (OMS) INTRUSION-PSWD (NE)
APC-CORRECTION-SKIPPED (OTS) IOSCFGCOPY (EQPT)
APC-DISABLED (NE) KB-PASSTHR (OCN)
APC-END (NE)
APC-OUT-OF-RANGE (AOTS)
APC-OUT-OF-RANGE (OCH)
APC-OUT-OF-RANGE (OMS)
APC-OUT-OF-RANGE (OTS)
APS-PRIM-FAC (OCN)
AS-CMD (2R)
AS-CMD (AOTS)
AS-CMD (BPLANE)
AS-CMD (CE1000)
AS-CMD (CE100T)
AS-CMD (DS1)
AS-CMD (DS3)
AS-CMD (E1)
AS-CMD (E1)
AS-CMD (E1000F)
AS-CMD (E100T)
AS-CMD (EQPT)
LAN-POL-REV (NE)
LASER-APR (AOTS)
LCAS-CRC (STSTRM)
LCAS-CRC (VT-TERM)
LCAS-RX-FAIL (STSTRM)
LCAS-RX-FAIL (VT-TERM)
LCAS-TX-ADD (STSTRM)
LCAS-TX-ADD (VT-TERM)
LCAS-TX-DNU (STSTRM)
LCAS-TX-DNU (VT-TERM)
LKOUTPR-S (OCN)
LOCKOUT-REQ (2R)
LOCKOUT-REQ (EQPT)
LOCKOUT-REQ (ESCON)
LOCKOUT-REQ (FC)
LOCKOUT-REQ (GE)
LOCKOUT-REQ (ISC)
LOCKOUT-REQ (OCN)
SD-V (VT-TERM)
SF (DS1)
SF (DS3)
SF (E1)
SF (TRUNK)
SF-L (E1)
SF-L (OCN)
SF-L (TRUNK)
SF-P (STSMON)
SF-P (STSTRM)
SF-V (VT-MON)
SF-V (VT-TERM)
SHUTTER-OPEN (OTS)
SPAN-NOT-MEASURED (OTS)
SPAN-SW-EAST (OCN)
SPAN-SW-WEST (OCN)
SQUELCH (OCN)
SQUELCHED (2R)
SQUELCHED (ESCON)
SQUELCHED (FC)
SQUELCHED (GE)
SQUELCHED (ISC)
SQUELCHED (OCN)
SQUELCHED (TRUNK)
SSM-DUS (BITS)
SSM-DUS (DS1)
SSM-DUS (E1)
SSM-DUS (OCN)
SSM-DUS (TRUNK)
SSM-LNC (BITS)
SSM-LNC (NE-SREF)
SSM-LNC (TRUNK)
SSM-OFF (BITS)
SSM-OFF (DS1)
2-6
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.1.4 NA Conditions
Table 2-4 ONS 15454 NA Conditions List (continued)
AS-CMD (TRUNK)
AS-MT (2R)
AS-MT (AOTS)
AS-MT (CE1000)
AS-MT (CE100T)
AS-MT (DS1)
AS-MT (DS3)
AS-MT (E1)
AS-MT (E1)
AS-MT (EQPT)
AS-MT (ESCON)
AS-MT (FC)
AS-MT (FCMR)
AS-MT (G1000)
AS-MT (GE)
AS-MT (GFP-FAC)
AS-MT (ISC)
AS-MT (ML1000)
AS-MT (ML100T)
AS-CMD (ESCON)
AS-CMD (FC)
AS-CMD (FCMR)
AS-CMD (G1000)
AS-CMD (GE)
AS-CMD (GFP-FAC)
AS-CMD (ISC)
AS-CMD (ML1000)
AS-CMD (ML100T)
AS-CMD (MLFX)
AS-CMD (NE)
AS-CMD (OCH)
AS-CMD (OCN)
AS-CMD (OMS)
AS-CMD (OTS)
AS-CMD (PPM)
AS-CMD (PWR )
AS-CMD (SHELF)
LOCKOUT-REQ (STSMON)
LOCKOUT-REQ (TRUNK)
LOCKOUT-REQ (VT-MON)
LPBKCRS (STSMON)
LPBKCRS (STSTRM)
LPBKDS1FE-CMD (DS1)
LPBKDS3FEAC (DS3)
LPBKDS3FEAC-CMD (DS3)
LPBKFACILITY (CE1000)
LPBKFACILITY (CE100T)
LPBKFACILITY (DS1)
LPBKFACILITY (DS3)
LPBKFACILITY (E1)
LPBKFACILITY (E1)
LPBKFACILITY (ESCON)
LPBKFACILITY (FC)
LPBKFACILITY (FCMR)
LPBKFACILITY (G1000)
LPBKFACILITY (GE)
LPBKFACILITY (ISC)
LPBKFACILITY (OCN)
LPBKFACILITY (TRUNK)
LPBKTERMINAL (CE1000)
LPBKTERMINAL (CE100T)
LPBKTERMINAL (DS1)
LPBKTERMINAL (DS3)
LPBKTERMINAL (E1)
LPBKTERMINAL (E1)
LPBKTERMINAL (ESCON)
LPBKTERMINAL (FC)
LPBKTERMINAL (FCMR)
LPBKTERMINAL (G1000)
LPBKTERMINAL (GE)
LPBKTERMINAL (ISC)
LPBKTERMINAL (OCN)
LPBKTERMINAL (TRUNK)
MAN-REQ (EQPT)
November 2009
SSM-OFF (E1)
SSM-OFF (OCN)
SSM-OFF (TRUNK)
SSM-PRC (BITS)
SSM-PRC (NE-SREF)
SSM-PRC (TRUNK)
SSM-PRS (BITS)
SSM-PRS (DS1)
SSM-PRS (E1)
SSM-PRS (NE-SREF)
SSM-PRS (OCN)
SSM-PRS (TRUNK)
SSM-RES (BITS)
SSM-RES (DS1)
SSM-RES (E1)
SSM-RES (NE-SREF)
SSM-RES (OCN)
SSM-RES (TRUNK)
SSM-SDH-TN (OCN)
SSM-SDH-TN (TRUNK)
SSM-SETS (BITS)
SSM-SETS (NE-SREF)
SSM-SETS (TRUNK)
SSM-SMC (BITS)
SSM-SMC (DS1)
SSM-SMC (E1)
SSM-SMC (NE-SREF)
SSM-SMC (OCN)
SSM-SMC (TRUNK)
SSM-ST2 (BITS)
SSM-ST2 (DS1)
SSM-ST2 (E1)
SSM-ST2 (NE-SREF)
SSM-ST2 (OCN)
SSM-ST2 (TRUNK)
SSM-ST3 (BITS)
SSM-ST3 (DS1)
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-7
Chapter 2 Alarm Troubleshooting
2.1.4 NA Conditions
Table 2-4 ONS 15454 NA Conditions List (continued)
AS-MT (MLFX)
AS-MT (OCH)
AS-MT (OCN)
AS-MT (OMS)
AS-MT (OTS)
AS-MT (PPM)
AS-MT (SHELF)
AS-MT (TRUNK)
AS-MT-OOG (STSTRM)
AS-MT-OOG (VT-TERM)
AUD-LOG-LOSS (NE)
AUD-LOG-LOW (NE)
AUTOSW-LOP (STSMON)
AUTOSW-LOP (VT-MON)
AUTOSW-PDI (STSMON)
AUTOSW-SDBER (STSMON)
AUTOSW-SFBER (STSMON)
AUTOSW-UNEQ (STSMON)
AWG-WARM-UP (OTS)
CLDRESTART (EQPT)
CTNEQPT-MISMATCH (EQPT)
DS3-MISM (DS3)
ETH-LINKLOSS (NE)
EXERCISE-RING-FAIL (OCN)
EXERCISE-SPAN-FAIL (OCN)
FAILTOSW (2R)
FAILTOSW (EQPT)
FAILTOSW (ESCON)
FAILTOSW (FC)
FAILTOSW (GE)
FAILTOSW (ISC)
FAILTOSW (OCN)
FAILTOSW (TRUNK)
FAILTOSW-PATH (STSMON)
FAILTOSW-PATH (VT-MON)
FAILTOSWR (OCN)
FAILTOSWS (OCN)
MAN-REQ (ML1000)
MAN-REQ (ML100T)
MAN-REQ (MLFX)
MAN-REQ (STSMON)
MAN-REQ (VT-MON)
MANRESET (EQPT)
MANSWTOINT (NE-SREF)
MANSWTOPRI (EXT-SREF)
MANSWTOSEC (EXT-SREF)
MANSWTOSEC (NE-SREF)
MANSWTOTHIRD (EXT-SREF)
MANSWTOTHIRD (NE-SREF)
MANUAL-REQ-RING (OCN)
MANUAL-REQ-SPAN (2R)
MANUAL-REQ-SPAN (ESCON)
MANUAL-REQ-SPAN (FC)
MANUAL-REQ-SPAN (GE)
MANUAL-REQ-SPAN (ISC)
MANUAL-REQ-SPAN (OCN)
MANUAL-REQ-SPAN (TRUNK)
NO-CONFIG (EQPT)
OCHNC-INC (OCHNC-CONN)
OCHTERM-INC (OCH-TERM)
ODUK-SD-PM (TRUNK)
ODUK-SF-PM (TRUNK)
OOU-TPT (STSTRM)
OOU-TPT (VT-TERM)
OPEN-SLOT (EQPT)
OSRION (AOTS)
OSRION (OTS)
OTUK-SD (TRUNK)
OTUK-SF (TRUNK)
OUT-OF-SYNC (ISC)
PARAM-MISM (AOTS)
PARAM-MISM (OCH)
PARAM-MISM (OMS)
PARAM-MISM (OTS)
SSM-ST3 (E1)
SSM-ST3 (NE-SREF)
SSM-ST3 (OCN)
SSM-ST3 (TRUNK)
SSM-ST3E (BITS)
SSM-ST3E (DS1)
SSM-ST3E (E1)
SSM-ST3E (NE-SREF)
SSM-ST3E (OCN)
SSM-ST3E (TRUNK)
SSM-ST4 (BITS)
SSM-ST4 (DS1)
SSM-ST4 (E1)
SSM-ST4 (NE-SREF)
SSM-ST4 (OCN)
SSM-ST4 (TRUNK)
SSM-STU (BITS)
SSM-STU (DS1)
SSM-STU (E1)
SSM-STU (NE-SREF)
SSM-STU (OCN)
SSM-STU (TRUNK)
SSM-TNC (BITS)
SSM-TNC (NE-SREF)
SSM-TNC (TRUNK)
STS-SQUELCH-L (OCN)
SW-MISMATCH (EQPT)
SWTOPRI (EXT-SREF)
SWTOPRI (NE-SREF)
SWTOSEC (EXT-SREF)
SWTOSEC (NE-SREF)
SWTOTHIRD (EXT-SREF)
SWTOTHIRD (NE-SREF)
SYNC-FREQ (BITS)
SYNC-FREQ (DS1)
SYNC-FREQ (E1)
SYNC-FREQ (OCN)
2-8
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.1.4 NA Conditions
Table 2-4 ONS 15454 NA Conditions List (continued)
FDI (OCH)
FE-AIS (DS3)
FE-DS1-MULTLOS (DS3)
FE-DS1-NSA (DS3)
FE-DS1-SA (DS3)
FE-DS1-SNGLLOS (DS3)
FE-DS3-NSA (DS3)
FE-DS3-SA (DS3)
FE-EQPT-NSA (DS3)
FE-FRCDWKSWBK-SPAN (OCN)
FE-FRCDWKSWPR-RING (OCN)
FE-FRCDWKSWPR-SPAN (OCN)
FE-IDLE (DS3)
FE-LOCKOUTOFPR-SPAN (OCN)
FE-LOF (DS3)
FE-LOS (DS3)
FE-MANWKSWBK-SPAN (OCN)
FE-MANWKSWPR-RING (OCN)
FE-MANWKSWPR-SPAN (OCN)
FORCED-REQ (EQPT)
FORCED-REQ (ML1000)
FORCED-REQ (ML100T)
FORCED-REQ (MLFX)
FORCED-REQ (STSMON)
FORCED-REQ (VT-MON)
FORCED-REQ-RING (OCN)
FORCED-REQ-SPAN (2R)
FORCED-REQ-SPAN (ESCON)
FORCED-REQ-SPAN (FC)
FORCED-REQ-SPAN (GE)
FORCED-REQ-SPAN (ISC)
FORCED-REQ-SPAN (OCN)
FORCED-REQ-SPAN (TRUNK)
FRCDSWTOINT (NE-SREF)
FRCDSWTOPRI (EXT-SREF)
FRCDSWTOPRI (NE-SREF)
FRCDSWTOSEC (EXT-SREF)
PDI-P (STSMON)
PDI-P (STSTRM)
PMI (OMS)
PMI (OTS)
PORT-MISMATCH (FCMR)
RAI (DS1)
RAI (DS3)
RAI (E1)
RING-SW-EAST (OCN)
RING-SW-WEST (OCN)
ROLL (STSMON)
ROLL (STSTRM)
ROLL (VT-MON)
ROLL-PEND (STSMON)
ROLL-PEND (VT-MON)
RPR-PASSTHR (RPRIF)
RPR-PROT-ACTIVE (RPRIF)
RPR-SD (ML1000)
RPR-SD (ML100T)
RPR-SD (MLFX)
RPR-SF (ML1000)
RPR-SF (ML100T)
RPR-SF (MLFX)
RPRW (ML1000)
RPRW (ML100T)
RPRW (MLFX)
RUNCFG-SAVENEED (EQPT)
SD (DS1)
SD (DS3)
SD (E1)
SD (TRUNK)
SD-L (E1)
SD-L (OCN)
SD-L (TRUNK)
SD-P (STSMON)
SD-P (STSTRM)
SD-V (VT-MON)
November 2009
SYNC-FREQ (TRUNK)
TEMP-MISM (NE)
TRAIL-SIGNAL-FAIL (OCH)
TRAIL-SIGNAL-FAIL (TRUNK)
TX-RAI (DS1)
TX-RAI (DS3)
TX-RAI (E1)
UNC-WORD (TRUNK)
VCG-DEG (VCG)
VCG-DOWN (VCG)
VOLT-MISM (PWR )
VT-SQUELCH-L (OCN)
WKSWPR (2R)
WKSWPR (EQPT)
WKSWPR (ESCON)
WKSWPR (FC)
WKSWPR (GE)
WKSWPR (ISC)
—
—
—
WKSWPR (OCN)
WKSWPR (STSMON)
WKSWPR (VT-MON)
WTR (2R)
WTR (EQPT)
WTR (ESCON)
WTR (FC)
WTR (GE)
WTR (ISC)
WTR (ML1000)
WTR (ML100T)
WTR (MLFX)
WTR (OCN)
WTR (STSMON)
WTR (TRUNK)
WTR (VT-MON)
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-9
Chapter 2 Alarm Troubleshooting
2.1.5 NR Conditions
2.1.5 NR Conditions
Table 2-5
Table 2-5 alphabetically lists ONS 15454 Not Reported (NR) conditions.
ONS 15454 NR Conditions List
AIS (BITS)
AIS (DS1)
AIS (DS3)
AIS (E1)
AIS (FUDC)
AIS (MSUDC)
AIS (TRUNK)
AIS-L (E1)
AIS-L (OCN)
AIS-L (TRUNK)
AIS-P (STSMON)
AIS-P (STSTRM)
AIS-V (VT-MON)
AIS-V (VT-TERM)
AUTOSW-AIS (STSMON)
AUTOSW-AIS (VT-MON)
ERFI-P-CONN (STSMON)
ERFI-P-CONN (STSTRM)
ERFI-P-PAYLD (STSMON)
ERFI-P-PAYLD (STSTRM)
ERFI-P-SRVR (STSMON)
ERFI-P-SRVR (STSTRM)
ODUK-1-AIS-PM (TRUNK)
ODUK-2-AIS-PM (TRUNK)
ODUK-3-AIS-PM (TRUNK)
ODUK-4-AIS-PM (TRUNK)
ODUK-AIS-PM (TRUNK)
ODUK-BDI-PM (TRUNK)
ODUK-LCK-PM (TRUNK)
ODUK-OCI-PM (TRUNK)
OTUK-AIS (TRUNK)
—
OTUK-BDI (TRUNK)
RFI (TRUNK)
RFI-L (E1)
RFI-L (OCN)
RFI-L (TRUNK)
RFI-P (STSMON)
RFI-P (STSTRM)
RFI-V (VT-MON)
RFI-V (VT-TERM)
ROLL-PEND (STSTRM)
TX-AIS (DS1)
TX-AIS (DS3)
TX-AIS (E1)
TX-LOF (DS1)
TX-LOF (E1)
—
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 alphabetically lists all ONS 15454 alarms and conditions.
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List
AIS (BITS)
AIS (DS1)
AIS (DS3)
AIS (E1)
AIS (FUDC)
AIS (MSUDC)
AIS (TRUNK)
AIS-L (E1)
AIS-L (OCN)
AIS-L (TRUNK)
GFP-LFD (CE1000)
GFP-LFD (FCMR)
GFP-LFD (GFP-FAC)
GFP-LFD (ML1000)
GFP-LFD (ML100T)
GFP-LFD (MLFX)
GFP-NO-BUFFERS (FCMR)
GFP-NO-BUFFERS (GFP-FAC)
GFP-UP-MISMATCH (CE1000)
GFP-UP-MISMATCH (CE100T)
RCVR-MISS (DS1)
RCVR-MISS (E1)
RESERVED-RATE-EXCEEDED-RIN
GLET0 (RPRIF)
RESERVED-RATE-EXCEEDED-RIN
GLET1 (RPRIF)
RFI (TRUNK)
RFI-L (E1)
RFI-L (OCN)
RFI-L (TRUNK)
RFI-P (STSMON)
RFI-P (STSTRM)
2-10
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6
APC-END (NE)
ONS 15454 Alarm and Condition Alphabetical List (continued)
AIS-P (STSMON)
AIS-P (STSTRM)
AIS-V (VT-MON)
AIS-V (VT-TERM)
ALS (2R)
ALS (AOTS)
ALS (ESCON)
ALS (FC)
ALS (GE)
ALS (ISC)
ALS (OCN)
ALS (TRUNK)
ALS-DISABLED (EQPT)
AMPLI-INIT (AOTS)
ANSWTOPRI (NE-SREF)
APC-CORRECTION-SKIPPED (AOTS)
APC-CORRECTION-SKIPPED (OCH)
APC-CORRECTION-SKIPPED (OMS)
APC-CORRECTION-SKIPPED (OTS)
APC-DISABLED (NE)
APC-OUT-OF-RANGE (AOTS)
APC-OUT-OF-RANGE (OCH)
APC-OUT-OF-RANGE (OMS)
APC-OUT-OF-RANGE (OTS)
APSB (OCN)
APSCDFLTK (OCN)
APSC-IMP (OCN)
APSCINCON (OCN)
APSCM (OCN)
APSCNMIS (OCN)
APSIMP (OCN)
APS-INV-PRIM (OCN)
APSMM (OCN)
APS-PRIM-FAC (OCN)
APS-PRIM-SEC-MISM (OCN)
GFP-UP-MISMATCH (FCMR)
GFP-UP-MISMATCH (GFP-FAC)
GFP-UP-MISMATCH (ML1000)
GFP-UP-MISMATCH (ML100T)
GFP-UP-MISMATCH (MLFX)
HELLO (OCN)
HI-TXPOWER (OCN)
HI-TXPOWER (PPM)
HLDOVRSYNC (NE-SREF)
I-HITEMP (NE)
IMPROPRMVL (EQPT)
IMPROPRMVL (PPM)
INC-ISD (DS3)
INHSWPR (EQPT)
INHSWWKG (EQPT)
INTRUSION-PSWD (NE)
INVMACADR (AIP)
IOSCFGCOPY (EQPT)
ISIS-ADJ-FAIL (OCN)
ISIS-ADJ-FAIL (TRUNK)
KB-PASSTHR (OCN)
KBYTE-APS-CHANNEL-FAILURE
(OCN)
LAN-POL-REV (NE)
LASER-APR (AOTS)
LASERBIAS-DEG (AOTS)
LASERBIAS-DEG (OTS)
LASERBIAS-FAIL (AOTS)
LASEREOL (OCN)
LASERTEMP-DEG (AOTS)
LCAS-CRC (STSTRM)
LCAS-CRC (VT-TERM)
LCAS-RX-FAIL (STSTRM)
LCAS-RX-FAIL (VT-TERM)
LCAS-TX-ADD (STSTRM)
LCAS-TX-ADD (VT-TERM)
LCAS-TX-DNU (STSTRM)
RFI-V (VT-MON)
RFI-V (VT-TERM)
RING-ID-MIS (OCN)
RING-ID-MIS (OSC-RING)
RING-MISMATCH (OCN)
RING-SW-EAST (OCN)
RING-SW-WEST (OCN)
ROLL (STSMON)
ROLL (STSTRM)
ROLL (VT-MON)
ROLL-PEND (STSMON)
ROLL-PEND (STSTRM)
ROLL-PEND (VT-MON)
RPR-PASSTHR (RPRIF)
RPR-PEER-MISS (RPRIF)
RPR-PROT-ACTIVE (RPRIF)
RPR-PROT-CONFIG-MISMATCH
(RPRIF)
RPR-RI-FAIL (RPRIF)
RPR-SD (ML1000)
RPR-SD (ML100T)
RPR-SD (MLFX)
RPR-SF (ML1000)
RPR-SF (ML100T)
RPR-SF (MLFX)
RPR-SPAN-MISMATCH (ML1000)
RPR-SPAN-MISMATCH (ML100T)
RPR-SPAN-MISMATCH (MLFX)
RPRW (ML1000)
RPRW (ML100T)
RPRW (MLFX)
RUNCFG-SAVENEED (EQPT)
SD (DS1)
SD (DS3)
SD (E1)
SD (TRUNK)
SD-L (E1)
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-11
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
AS-CMD (2R)
AS-CMD (AOTS)
AS-CMD (BPLANE)
AS-CMD (CE1000)
AS-CMD (CE100T)
AS-CMD (DS1)
AS-CMD (DS3)
AS-CMD (E1)
AS-CMD (E1)
AS-CMD (E1000F)
AS-CMD (E100T)
AS-CMD (EQPT)
AS-CMD (ESCON)
AS-CMD (FC)
AS-CMD (FCMR)
AS-CMD (G1000)
AS-CMD (GE)
AS-CMD (GFP-FAC)
AS-CMD (ISC)
AS-CMD (ML1000)
AS-CMD (ML100T)
AS-CMD (MLFX)
AS-CMD (NE)
AS-CMD (OCH)
AS-CMD (OCN)
AS-CMD (OMS)
AS-CMD (OTS)
AS-CMD (PPM)
AS-CMD (PWR )
AS-CMD (SHELF)
LCAS-TX-DNU (VT-TERM)
LINK-KEEPALIVE (ML1000)
LINK-KEEPALIVE (ML100T)
LINK-KEEPALIVE (MLFX)
LKOUTPR-S (OCN)
LMP-FAIL (CTRL)
LMP-FAIL (GE)
LMP-FAIL (OCN)
LMP-FAIL (TLINK)
LMP-SD (GE)
LMP-SD (OCN)
LMP-SF (GE)
LMP-SF (OCN)
LMP-UNALLOC (GE)
LMP-UNALLOC (OCN)
LOA (VCG)
LOCKOUT-REQ (2R)
LOCKOUT-REQ (EQPT)
LOCKOUT-REQ (ESCON)
LOCKOUT-REQ (FC)
LOCKOUT-REQ (GE)
LOCKOUT-REQ (ISC)
LOCKOUT-REQ (OCN)
LOCKOUT-REQ (STSMON)
LOCKOUT-REQ (TRUNK)
LOCKOUT-REQ (VT-MON)
LOF (BITS)
LOF (DS1)
LOF (DS3)
LOF (E1)
AS-CMD (TRUNK)
AS-MT (2R)
AS-MT (AOTS)
AS-MT (CE1000)
AS-MT (CE100T)
AS-MT (DS1)
LOF (E1)
LOF (OCN)
LOF (STSTRM)
LOF (TRUNK)
LO-LASERBIAS (EQPT)
LO-LASERBIAS (OCN)
SD-L (OCN)
SD-L (TRUNK)
SD-P (STSMON)
SD-P (STSTRM)
SD-V (VT-MON)
SD-V (VT-TERM)
SF (DS1)
SF (DS3)
SF (E1)
SF (TRUNK)
SF-L (E1)
SF-L (OCN)
SF-L (TRUNK)
SF-P (STSMON)
SF-P (STSTRM)
SFTWDOWN (EQPT)
SF-V (VT-MON)
SF-V (VT-TERM)
SHELF-COMM-FAIL (SHELF)
SH-INS-LOSS-VAR-DEG-HIGH (OTS)
SH-INS-LOSS-VAR-DEG-LOW (OTS)
SHUTTER-OPEN (OTS)
SIGLOSS (ESCON)
SIGLOSS (FC)
SIGLOSS (FCMR)
SIGLOSS (GE)
SIGLOSS (ISC)
SIGLOSS (TRUNK)
SNTP-HOST (NE)
SPANLENGTH-OUT-OF-RANGE
(OTS)
SPAN-NOT-MEASURED (OTS)
SPAN-SW-EAST (OCN)
SPAN-SW-WEST (OCN)
SQM (STSTRM)
SQM (VT-TERM)
SQUELCH (OCN)
2-12
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
AS-MT (DS3)
AS-MT (E1)
AS-MT (E1)
AS-MT (EQPT)
AS-MT (ESCON)
AS-MT (FC)
AS-MT (FCMR)
AS-MT (G1000)
AS-MT (GE)
AS-MT (GFP-FAC)
AS-MT (ISC)
AS-MT (ML1000)
AS-MT (ML100T)
AS-MT (MLFX)
AS-MT (OCH)
AS-MT (OCN)
AS-MT (OMS)
AS-MT (OTS)
AS-MT (PPM)
AS-MT (SHELF)
AS-MT (TRUNK)
AS-MT-OOG (STSTRM)
AS-MT-OOG (VT-TERM)
AUD-LOG-LOSS (NE)
AUD-LOG-LOW (NE)
AUTOLSROFF (OCN)
AUTONEG-RFI (ML1000)
AUTORESET (EQPT)
AUTOSW-AIS (STSMON)
AUTOSW-AIS (VT-MON)
AUTOSW-LOP (STSMON)
AUTOSW-LOP (VT-MON)
AUTOSW-PDI (STSMON)
AUTOSW-SDBER (STSMON)
AUTOSW-SFBER (STSMON)
AUTOSW-UNEQ (STSMON)
AUTOSW-UNEQ (VT-MON)
LOS (2R)
LOS (BITS)
LOS (DS1)
LOS (DS3)
LOS (E1)
LOS (E1)
LOS (ESCON)
LOS (FUDC)
LOS (ISC)
LOS (MSUDC)
LOS (OCN)
LOS (OTS)
LOS (TRUNK)
LOS-O (OCH)
LOS-O (OMS)
LOS-O (OTS)
LOS-P (OCH)
LOS-P (OMS)
LOS-P (OTS)
LO-LASERBIAS (PPM)
LO-LASERTEMP (EQPT)
LO-LASERTEMP (OCN)
LO-LASERTEMP (PPM)
LOM (STSMON)
LOM (STSTRM)
LOM (TRUNK)
LOM (VT-TERM)
LOP-P (STSMON)
LOP-P (STSTRM)
LOP-V (VT-MON)
LOP-V (VT-TERM)
LO-RXPOWER (2R)
LO-RXPOWER (ESCON)
LO-RXPOWER (FC)
LO-RXPOWER (GE)
LO-RXPOWER (ISC)
LO-RXPOWER (OCN)
SQUELCHED (2R)
SQUELCHED (ESCON)
SQUELCHED (FC)
SQUELCHED (GE)
SQUELCHED (ISC)
SQUELCHED (OCN)
SQUELCHED (TRUNK)
SSM-DUS (BITS)
SSM-DUS (DS1)
SSM-DUS (E1)
SSM-DUS (OCN)
SSM-DUS (TRUNK)
SSM-FAIL (BITS)
SSM-FAIL (DS1)
SSM-FAIL (E1)
SSM-FAIL (OCN)
SSM-FAIL (TRUNK)
SSM-LNC (BITS)
SSM-LNC (NE-SREF)
SSM-LNC (TRUNK)
SSM-OFF (BITS)
SSM-OFF (DS1)
SSM-OFF (E1)
SSM-OFF (OCN)
SSM-OFF (TRUNK)
SSM-PRC (BITS)
SSM-PRC (NE-SREF)
SSM-PRC (TRUNK)
SSM-PRS (BITS)
SSM-PRS (DS1)
SSM-PRS (E1)
SSM-PRS (NE-SREF)
SSM-PRS (OCN)
SSM-PRS (TRUNK)
SSM-RES (BITS)
SSM-RES (DS1)
SSM-RES (E1)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-13
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
AWG-DEG (OTS)
AWG-FAIL (OTS)
AWG-OVERTEMP (OTS)
AWG-WARM-UP (OTS)
BAT-FAIL (PWR )
BKUPMEMP (EQPT)
BLSROSYNC (OCN)
BLSR-SW-VER-MISM (OCN)
BPV (BITS)
CARLOSS (CE100T)
CARLOSS (CE1000)
CARLOSS (E1000F)
CARLOSS (E100T)
CARLOSS (EQPT)
CARLOSS (FC)
CARLOSS (G1000)
CARLOSS (GE)
CARLOSS (ISC)
CARLOSS (ML1000)
CARLOSS (ML100T)
CARLOSS (MLFX)
CARLOSS (TRUNK)
CASETEMP-DEG (AOTS)
CLDRESTART (EQPT)
COMIOXC (EQPT)
COMM-FAIL (EQPT)
CONTBUS-A-18 (EQPT)
CONTBUS-B-18 (EQPT)
CONTBUS-DISABLED (EQPT)
CONTBUS-IO-A (EQPT)
CONTBUS-IO-B (EQPT)
CTNEQPT-MISMATCH (EQPT)
CTNEQPT-PBPROT (EQPT)
CTNEQPT-PBWORK (EQPT)
DATA-CRC (CE100T)
DATA-CRC (ML1000)
DATA-CRC (ML100T)
LOS-P (TRUNK)
LO-TXPOWER (2R)
LO-TXPOWER (EQPT)
LO-TXPOWER (ESCON)
LO-TXPOWER (FC)
LO-TXPOWER (GE)
LO-TXPOWER (ISC)
LO-TXPOWER (OCN)
LO-TXPOWER (PPM)
LO-TXPOWER (TRUNK)
LPBKCRS (STSMON)
LPBKCRS (STSTRM)
LPBKDS1FE-CMD (DS1)
LPBKDS3FEAC (DS3)
LPBKDS3FEAC-CMD (DS3)
LPBKFACILITY (CE1000)
LPBKFACILITY (CE100T)
LPBKFACILITY (DS1)
LPBKFACILITY (DS3)
LPBKFACILITY (E1)
LPBKFACILITY (E1)
LPBKFACILITY (ESCON)
LPBKFACILITY (FC)
LPBKFACILITY (FCMR)
LPBKFACILITY (G1000)
LPBKFACILITY (GE)
LPBKFACILITY (ISC)
LPBKFACILITY (OCN)
LPBKFACILITY (TRUNK)
LPBKTERMINAL (CE1000)
LPBKTERMINAL (CE100T)
LPBKTERMINAL (DS1)
LPBKTERMINAL (DS3)
LPBKTERMINAL (E1)
LPBKTERMINAL (E1)
LPBKTERMINAL (ESCON)
LPBKTERMINAL (FC)
SSM-RES (NE-SREF)
SSM-RES (OCN)
SSM-RES (TRUNK)
SSM-SDH-TN (OCN)
SSM-SDH-TN (TRUNK)
SSM-SETS (BITS)
SSM-SETS (NE-SREF)
SSM-SETS (TRUNK)
SSM-SMC (BITS)
SSM-SMC (DS1)
SSM-SMC (E1)
SSM-SMC (NE-SREF)
SSM-SMC (OCN)
SSM-SMC (TRUNK)
SSM-ST2 (BITS)
SSM-ST2 (DS1)
SSM-ST2 (E1)
SSM-ST2 (NE-SREF)
SSM-ST2 (OCN)
SSM-ST2 (TRUNK)
SSM-ST3 (BITS)
SSM-ST3 (DS1)
SSM-ST3 (E1)
SSM-ST3 (NE-SREF)
SSM-ST3 (OCN)
SSM-ST3 (TRUNK)
SSM-ST3E (BITS)
SSM-ST3E (DS1)
SSM-ST3E (E1)
SSM-ST3E (NE-SREF)
SSM-ST3E (OCN)
SSM-ST3E (TRUNK)
SSM-ST4 (BITS)
SSM-ST4 (DS1)
SSM-ST4 (E1)
SSM-ST4 (NE-SREF)
SSM-ST4 (OCN)
2-14
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
DATA-CRC (MLFX)
DATAFLT (NE)
DBOSYNC (NE)
DS3-MISM (DS3)
DSP-COMM-FAIL (TRUNK)
DSP-FAIL (TRUNK)
DUP-IPADDR (NE)
DUP-NODENAME (NE)
DUP-SHELF-ID (SHELF)
EHIBATVG (PWR )
ELWBATVG (PWR )
ENCAP-MISMATCH-P (STSTRM)
EOC (OCN)
EOC (TRUNK)
EOC-L (OCN)
EOC-L (TRUNK)
EQPT (AICI-AEP)
EQPT (AICI-AIE)
EQPT (EQPT)
EQPT (PPM)
EQPT-DIAG (EQPT)
EQPT-MISS (FAN)
ERFI-P-CONN (STSMON)
ERFI-P-CONN (STSTRM)
ERFI-P-PAYLD (STSMON)
ERFI-P-PAYLD (STSTRM)
ERFI-P-SRVR (STSMON)
ERFI-P-SRVR (STSTRM)
ERROR-CONFIG (EQPT)
ETH-LINKLOSS (NE)
E-W-MISMATCH (OCN)
EXCCOL (EQPT)
EXERCISE-RING-FAIL (OCN)
EXERCISE-SPAN-FAIL (OCN)
EXT (ENVALRM)
EXTRA-TRAF-PREEMPT (OCN)
FAILTOSW (2R)
LPBKTERMINAL (FCMR)
LPBKTERMINAL (G1000)
LPBKTERMINAL (GE)
LPBKTERMINAL (ISC)
LPBKTERMINAL (OCN)
LPBKTERMINAL (TRUNK)
LWBATVG (PWR )
MAN-REQ (EQPT)
MAN-REQ (ML1000)
MAN-REQ (ML100T)
MAN-REQ (MLFX)
MAN-REQ (STSMON)
MAN-REQ (VT-MON)
MANRESET (EQPT)
MANSWTOINT (NE-SREF)
MANSWTOPRI (EXT-SREF)
MANSWTOSEC (EXT-SREF)
MANSWTOSEC (NE-SREF)
MANSWTOTHIRD (EXT-SREF)
MANSWTOTHIRD (NE-SREF)
MANUAL-REQ-RING (OCN)
MANUAL-REQ-SPAN (2R)
MANUAL-REQ-SPAN (ESCON)
MANUAL-REQ-SPAN (FC)
MANUAL-REQ-SPAN (GE)
MANUAL-REQ-SPAN (ISC)
MANUAL-REQ-SPAN (OCN)
MANUAL-REQ-SPAN (TRUNK)
MAX-STATIONS (RPRIF)
MEA (AIP)
MEA (BIC)
MEA (EQPT)
MEA (FAN)
MEA (PPM)
MEA (SHELF)
MEM-GONE (EQPT)
MEM-LOW (EQPT)
SSM-ST4 (TRUNK)
SSM-STU (BITS)
SSM-STU (DS1)
SSM-STU (E1)
SSM-STU (NE-SREF)
SSM-STU (OCN)
SSM-STU (TRUNK)
SSM-TNC (BITS)
SSM-TNC (NE-SREF)
SSM-TNC (TRUNK)
STS-SQUELCH-L (OCN)
SW-MISMATCH (EQPT)
SWMTXMOD-PROT (EQPT)
SWMTXMOD-WORK (EQPT)
SWTOPRI (EXT-SREF)
SWTOPRI (NE-SREF)
SWTOSEC (EXT-SREF)
SWTOSEC (NE-SREF)
SWTOTHIRD (EXT-SREF)
SWTOTHIRD (NE-SREF)
SYNC-FREQ (BITS)
SYNC-FREQ (DS1)
SYNC-FREQ (E1)
SYNC-FREQ (OCN)
SYNC-FREQ (TRUNK)
SYNCLOSS (FC)
SYNCLOSS (FCMR)
SYNCLOSS (GE)
SYNCLOSS (ISC)
SYNCLOSS (TRUNK)
SYNCPRI (EXT-SREF)
SYNCPRI (NE-SREF)
SYNCSEC (EXT-SREF)
SYNCSEC (NE-SREF)
SYNCTHIRD (EXT-SREF)
SYNCTHIRD (NE-SREF)
SYSBOOT (NE)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-15
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
FAILTOSW (EQPT)
FAILTOSW (ESCON)
FAILTOSW (FC)
FAILTOSW (GE)
FAILTOSW (ISC)
FAILTOSW (OCN)
FAILTOSW (TRUNK)
FAILTOSW-PATH (STSMON)
FAILTOSW-PATH (VT-MON)
FAILTOSWR (OCN)
FAILTOSWS (OCN)
FAN (FAN)
FC-NO-CREDITS (FC)
FC-NO-CREDITS (FCMR)
FC-NO-CREDITS (TRUNK)
FDI (OCH)
FE-AIS (DS3)
FEC-MISM (TRUNK)
FE-DS1-MULTLOS (DS3)
FE-DS1-NSA (DS3)
FE-DS1-SA (DS3)
FE-DS1-SNGLLOS (DS3)
FE-DS3-NSA (DS3)
FE-DS3-SA (DS3)
FE-EQPT-NSA (DS3)
FE-FRCDWKSWBK-SPAN (OCN)
FE-FRCDWKSWPR-RING (OCN)
FE-FRCDWKSWPR-SPAN (OCN)
FE-IDLE (DS3)
FE-LOCKOUTOFPR-SPAN (OCN)
FE-LOF (DS3)
FE-LOS (DS3)
FE-MANWKSWBK-SPAN (OCN)
FE-MANWKSWPR-RING (OCN)
FE-MANWKSWPR-SPAN (OCN)
FEPRLF (OCN)
MFGMEM (AICI-AEP)
MFGMEM (AICI-AIE)
MFGMEM (AIP)
MFGMEM (BPLANE)
MFGMEM (FAN)
MFGMEM (PPM)
NO-CONFIG (EQPT)
OCHNC-INC (OCHNC-CONN)
OCHTERM-INC (OCH-TERM)
ODUK-1-AIS-PM (TRUNK)
ODUK-2-AIS-PM (TRUNK)
ODUK-3-AIS-PM (TRUNK)
ODUK-4-AIS-PM (TRUNK)
ODUK-AIS-PM (TRUNK)
ODUK-BDI-PM (TRUNK)
ODUK-LCK-PM (TRUNK)
ODUK-OCI-PM (TRUNK)
ODUK-SD-PM (TRUNK)
ODUK-SF-PM (TRUNK)
ODUK-TIM-PM (TRUNK)
OOU-TPT (STSTRM)
OOU-TPT (VT-TERM)
OPEN-SLOT (EQPT)
OPTNTWMIS (NE)
OPWR-HDEG (AOTS)
OPWR-HDEG (OCH)
OPWR-HDEG (OMS)
OPWR-HDEG (OTS)
OPWR-HFAIL (AOTS)
OPWR-HFAIL (OCH)
OPWR-HFAIL (OMS)
OPWR-HFAIL (OTS)
OPWR-LDEG (AOTS)
OPWR-LDEG (OCH)
OPWR-LDEG (OMS)
OPWR-LDEG (OTS)
TEMP-MISM (NE)
TIM (OCN)
TIM (TRUNK)
TIM-MON (OCN)
TIM-MON (TRUNK)
TIM-P (STSMON)
TIM-P (STSTRM)
TIM-S (E1)
TIM-S (OCN)
TIM-V (VT-TERM)
TPTFAIL (CE1000)
TPTFAIL (CE100T)
TPTFAIL (FCMR)
TPTFAIL (G1000)
TPTFAIL (ML1000)
TPTFAIL (ML100T)
TPTFAIL (MLFX)
TRAIL-SIGNAL-FAIL (OCH)
TRAIL-SIGNAL-FAIL (TRUNK)
TRMT (DS1)
TRMT (E1)
TRMT-MISS (DS1)
TRMT-MISS (E1)
TX-AIS (DS1)
TX-AIS (DS3)
TX-AIS (E1)
TX-LOF (DS1)
TX-LOF (E1)
TX-RAI (DS1)
TX-RAI (DS3)
TX-RAI (E1)
UNC-WORD (TRUNK)
UNEQ-P (STSMON)
UNEQ-P (STSTRM)
UNEQ-V (VT-MON)
UNEQ-V (VT-TERM)
2-16
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.2 Alarms and Conditions Listed By Alphabetical Entry
FORCED-REQ (EQPT)
FORCED-REQ (ML1000)
FORCED-REQ (ML100T)
FORCED-REQ (MLFX)
FORCED-REQ (STSMON)
FORCED-REQ (VT-MON)
FORCED-REQ-RING (OCN)
FORCED-REQ-SPAN (2R)
FORCED-REQ-SPAN (ESCON)
FORCED-REQ-SPAN (FC)
FORCED-REQ-SPAN (GE)
FORCED-REQ-SPAN (ISC)
FORCED-REQ-SPAN (OCN)
FORCED-REQ-SPAN (TRUNK)
FRCDSWTOINT (NE-SREF)
FRCDSWTOPRI (EXT-SREF)
FRCDSWTOPRI (NE-SREF)
FRCDSWTOSEC (EXT-SREF)
FRCDSWTOSEC (NE-SREF)
FRCDSWTOTHIRD (EXT-SREF)
FRCDSWTOTHIRD (NE-SREF)
FRNGSYNC (NE-SREF)
FSTSYNC (NE-SREF)
FULLPASSTHR-BI (OCN)
GAIN-HDEG (AOTS)
GAIN-HFAIL (AOTS)
GAIN-LDEG (AOTS)
GAIN-LFAIL (AOTS)
GCC-EOC (TRUNK)
GE-OOSYNC (FC)
GE-OOSYNC (GE)
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
FIBERTEMP-DEG (AOTS)
GE-OOSYNC (ISC)
GE-OOSYNC (TRUNK)
GFP-CSF (CE100T)
GFP-CSF (CE1000)
OPWR-LFAIL (AOTS)
OPWR-LFAIL (OCH)
OPWR-LFAIL (OMS)
OPWR-LFAIL (OTS)
OSRION (AOTS)
OSRION (OTS)
OTUK-AIS (TRUNK)
OTUK-BDI (TRUNK)
OTUK-IAE (TRUNK)
OTUK-LOF (TRUNK)
OTUK-SD (TRUNK)
OTUK-SF (TRUNK)
OTUK-TIM (TRUNK)
OUT-OF-SYNC (FC)
OUT-OF-SYNC (GE)
OUT-OF-SYNC (ISC)
OUT-OF-SYNC (TRUNK)
PARAM-MISM (AOTS)
PARAM-MISM (OCH)
PARAM-MISM (OMS)
PARAM-MISM (OTS)
PDI-P (STSMON)
PDI-P (STSTRM)
PEER-NORESPONSE (EQPT)
PLM-P (STSMON)
PLM-P (STSTRM)
PLM-V (VT-TERM)
PMI (OMS)
PMI (OTS)
PORT-ADD-PWR-DEG-HI (OCH)
UNREACHABLE-TARGET-POWER
(OCH)
UT-COMM-FAIL (TRUNK)
UT-FAIL (TRUNK)
VCG-DEG (VCG)
VCG-DOWN (VCG)
VOA-HDEG (AOTS)
VOA-HDEG (OCH)
VOA-HDEG (OMS)
VOA-HDEG (OTS)
VOA-HFAIL (AOTS)
VOA-HFAIL (OCH)
VOA-HFAIL (OMS)
VOA-HFAIL (OTS)
VOA-LDEG (AOTS)
VOA-LDEG (OCH)
VOA-LDEG (OMS)
VOA-LDEG (OTS)
VOA-LFAIL (AOTS)
VOA-LFAIL (OCH)
VOA-LFAIL (OMS)
VOA-LFAIL (OTS)
VOLT-MISM (PWR )
VT-SQUELCH-L (OCN)
WKSWPR (2R)
WKSWPR (EQPT)
WKSWPR (ESCON)
WKSWPR (FC)
WKSWPR (GE)
WKSWPR (ISC)
WKSWPR (OCN)
PORT-ADD-PWR-DEG-LOW (OCH) WKSWPR (STSMON)
PORT-ADD-PWR-FAIL-HIGH
(OCH)
WKSWPR (VT-MON)
PORT-ADD-PWR-FAIL-LOW (OCH) WTR (2R)
PORT-FAIL (OCH) WTR (EQPT)
PORT-MISMATCH (FCMR)
PRC-DUPID (OCN)
WTR (ESCON)
WTR (FC)
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-17
Chapter 2 Alarm Troubleshooting
2.3 Alarm Logical Objects
Table 2-6 ONS 15454 Alarm and Condition Alphabetical List (continued)
GFP-CSF (FCMR)
GFP-CSF (GFP-FAC)
GFP-CSF (ML1000)
GFP-CSF (ML100T)
GFP-CSF (MLFX)
GFP-DE-MISMATCH (FCMR)
GFP-DE-MISMATCH (GFP-FAC)
GFP-EX-MISMATCH (CE1000)
GFP-EX-MISMATCH (FCMR)
GFP-EX-MISMATCH (GFP-FAC)
GFP-LFD (CE100T)
PROTNA (EQPT)
PROV-MISMATCH (PPM)
PROV-MISMATCH (TRUNK)
PTIM (TRUNK)
PWR-FAIL-A (EQPT)
PWR-FAIL-B (EQPT)
PWR-FAIL-RET-A (EQPT)
PWR-FAIL-RET-B (EQPT)
RAI (DS1)
RAI (DS3)
RAI (E1)
WTR (GE)
WTR (ISC)
WTR (ML1000)
WTR (ML100T)
WTR (MLFX)
WTR (OCN)
WTR (STSMON)
WTR (TRUNK)
WTR (VT-MON)
WVL-MISMATCH (TRUNK)
—
2.3 Alarm Logical Objects
The CTC alarm profile list organizes all alarms and conditions according to the logical objects they are raised against. These logical objects represent physical objects such as cards, logical objects such as circuits, or transport and signal monitoring entities such as the SONET or ITU-T G.709 optical overhead bits. One alarm can appear in multiple entries. It can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (OC-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both OCN: LOS and OTN: LOS appear in the list
(as well as the other objects).
Alarm profile list objects are defined in
Note Alarm logical object names can appear as abbreviated versions of standard terms used in the system and the documentation. For example, the “OCN” logical object refers to the OC-N signal. Logical object names or industry-standard terms are used within the entries as appropriate.
Table 2-7
Logical Object
2R
AICI-AEP
AICI-AIE
AOTS
BIC
BITS
BPLANE
Alarm Logical Object Type Definitions
Definition
Reshape and retransmit (used for transponder [TXP] cards).
Alarm Interface Controller–International/alarm expansion panel. A combination term that refers to this platform’s AIC-I card.
Alarm Interface Controller-International/Alarm Interface Extension. A combination term that refers to this platform's AIC-I card.
Amplified optical transport section. For information about AOTS alarms, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM
Troubleshooting Guide .
Backplane interface connector.
Building integrated timing supply incoming references (BITS-1, BITS-2).
The backplane.
2-18
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.3 Alarm Logical Objects
Table 2-7
Logical Object
CE1000
CE100T
CTRL
DS1
DS3
E1
E1000F
E100T
EC1
ENVALRM
EQPT
ESCON
EXT-SREF
FAN
FC
FCMR
FUDC
G1000
GE
GFP-FAC
ISC
ML1000
ML100T
MLFX
Alarm Logical Object Type Definitions (continued)
Definition
CE-1000-4 card.
CE-100T-8 card.
Control channel.
A DS-1 line on a DS-1 or DS-3 electrical card (DS1-14, DS3N-12E, DS3XM-6,
DS3XM-12).
A DS-3 line on a DS3-12, DS3N-12, DS3-12E, DS3XM-6, DS3XM-12,
DS3/EC1-48 card.
An E1 line on a DS1/E1-56 card.
An E1000 Ethernet card (E1000-2, E1000-2G).
An E100 Ethernet card (E100T-12, E100T-G).
Any EC-1 port (including EC1-12 card ports).
An environmental alarm port.
A card, its physical objects, and its logical objects as they are located in any of the eight noncommon card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signals (STS), and virtual tributaries (VT).
Enterprise System Connection fiber optic technology, referring to the following
TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G. For more information about ESCON alarms, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide .
BITS outgoing references (SYNC-BITS1, SYNC-BITS2).
Fan-tray assembly.
Fibre channel data transfer architecture, referring to the following muxponder
(MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G,
TXPP_MR_2.5G, TXP_MR_10E. For more information about FC alarms, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM
Troubleshooting Guide .
An FC_MR-4 Fibre Channel card.
SONET F1 byte user data channel for ONS 15454 ML-Series Ethernet cards.
A G-Series Ethernet card.
Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G,
MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E,
TXP_MR_10G.
Generic framing procedure facility port, referring to all MXP and TXP cards.
Inter-service channel, referring to TXPP_MR_2.5G or TXP_MR_2.5G cards. For more information about ISC alarms, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide .
An ML1000 Ethernet card (ML1000-2).
An ML100 Ethernet card (ML100T-12).
An ML100X-8 Ethernet card.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-19
Chapter 2 Alarm Troubleshooting
2.3 Alarm Logical Objects
Table 2-7 Alarm Logical Object Type Definitions (continued)
Logical Object
MSUDC
NE
Definition
Multiplex section user data channel.
The entire network element.
NE-SREF The timing status of the NE.
OCH The optical channel, referring to dense wavelength division multiplexing (DWDM) cards. For more information about OCH alarms, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide .
OCHNC-CONN The optical channel network connection, referring to DWDM cards. For more information about OCHNC-CONN alarms, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide .
OCN
OMS
OSC-RING
OTS
PPM
PWR
RPRIF
STSMON
An OC-N line on any OC-N card.
Optical multiplex section.
Optical service channel ring. For more information about OSC-RING alarms, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM
Troubleshooting Guide .
Optical transport section. For more information about OTS alarms, refer to the
“Alarm Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting
Guide .
Pluggable port module (PPM), referring to MXP and TXP cards. For more information about PPM alarms, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide .
Power equipment.
Interface for Resilient Packet Ring technology as defined in IEEE 802.17b. Also called RPR-IEEE.
STS alarm detection at the monitor point (upstream from the cross-connect).
STSTRM
TLINK
TRUNK
VCG
Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of STSMON, if available, should be changed to the same severity as the customized severity for a specific STS alarm.
STS alarm detection at termination (downstream from the cross-connect).
Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of STSTRM, if available, should be changed to the same severity as the customized severity for a specific STS alarm.
Traffic engineering (TE) link correlation.
The optical or DWDM card carrying the high-speed signal; referring to MXP or
TXP cards. For more information about TRUNK alarms, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide .
A virtual concatenation group of VTs.
2-20
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-7
Logical Object
VT-MON
VT-TERM
Alarm Logical Object Type Definitions (continued)
Definition
VT1 alarm detection at the monitor point (upstream from the cross-connect).
Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of VT-MON, if available, should be changed to the same severity as the customized severity for a specific VT alarm.
VT1 alarm detection at termination (downstream from the cross-connect).
Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of VT-TERM, if available, should be changed to the same severity as the customized severity for a specific VT alarm.
2.4 Alarm List by Logical Object Type
lists all ONS 15454 Release 7.2 alarms and logical objects as they are given in the system alarm profile. The list entries are organized by logical object name and then by alarm or condition name.
Where appropriate, the alarm entries also contain troubleshooting procedures.
Note In a mixed network containing different types of nodes (such as ONS 15310-CL, ONS 15454, and
ONS 15600), the initially displayed alarm list in the Provisioning > Alarm Profiles > Alarm Profile
Editor tab lists all conditions that are applicable to all nodes in the network. However, when you load the default severity profile from a node, only applicable alarms will display severity levels.
Nonapplicable alarms can display “use default” or “unset.”
Note In some cases this list does not follow alphabetical order, but it does reflect the order shown in CTC.
Table 2-8 Alarm List by Logical Object in Alarm Profile
2R: ALS (NA)
2R: AS-CMD (NA)
2R: AS-MT (NA)
2R: FAILTOSW (NA)
2R: FORCED-REQ-SPAN (NA)
2R: HI-LASERBIAS (MN)
2R: HI-RXPOWER (MN)
2R: HI-TXPOWER (MN)
2R: LO-RXPOWER (MN)
2R: LO-TXPOWER (MN)
2R: LOCKOUT-REQ (NA)
FAN: MFGMEM (CR)
FC: ALS (NA)
FC: AS-CMD (NA)
FC: AS-MT (NA)
FC: CARLOSS (MJ)
FC: FAILTOSW (NA)
FC: FC-NO-(CR)EDITS (MJ)
FC: FORCED-REQ-SPAN (NA)
FC: GE-OOSYNC (CR)
FC: HI-LASERBIAS (MN)
FC: HI-RXPOWER (MN)
OCN: LPBKTERMI(NA)L (NA)
OCN: MANUAL-REQ-RING (NA)
OCN: MANUAL-REQ-SPAN (NA)
OCN: PRC-DUPID (MJ)
OCN: RFI-L (NR)
OCN: RING-ID-MIS (MJ)
OCN: RING-MISMATCH (MJ)
OCN: RING-SW-EAST (NA)
OCN: RING-SW-WEST (NA)
OCN: SPAN-SW-EAST (NA)
OCN: SPAN-SW-WEST (NA)
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-21
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
2R: LOS (CR)
2R: MANUAL-REQ-SPAN (NA)
2R: SQUELCHED (NA)
2R: WKSWPR (NA)
2R: WTR (NA)
AICI-AEP: EQPT (CR)
AICI-AEP: MFGMEM (CR)
AICI-AIE: EQPT (CR)
AICI-AIE: MFGMEM (CR)
AIP: INVMACADR (MJ)
FC: LPBKFACILITY (NA)
FC: LPBKTERMI(NA)L (NA)
FC: MANUAL-REQ-SPAN (NA)
FC: OUT-OF-SYNC (MJ)
FC: SIGLOSS (MJ)
FC: SQUELCHED (NA)
FC: SYNCLOSS (MJ)
FC: WKSWPR (NA)
FC: WTR (NA)
FCMR: AS-CMD (NA)
AIP: MEA (CR)
AIP: MFGMEM (CR)
AOTS: ALS (NA)
AOTS: AMPLI-INIT (NA)
FCMR: AS-MT (NA)
FCMR: FC-NO-(CR)EDITS (MJ)
FCMR: GFP-CSF (MJ)
FCMR: GFP-DE-MISMATCH (MJ)
AOTS:
APC-CORRECTION-SKIPPED (NA)
FCMR: GFP-EX-MISMATCH (MJ)
AOTS: APC-OUT-OF-RANGE (NA) FCMR: GFP-LFD (MJ)
AOTS: AS-CMD (NA)
AOTS: AS-MT (NA)
AOTS: CASETEMP-DEG (MN)
AOTS: FIBERTEMP-DEG (MN)
AOTS: GAIN-HDEG (MN)
AOTS: GAIN-HFAIL (CR)
AOTS: GAIN-LDEG (MN)
FCMR: GFP-NO-BUFFERS (MJ)
FCMR: GFP-UP-MISMATCH (MJ)
FCMR: LPBKFACILITY (NA)
FCMR: LPBKTERMI(NA)L (NA)
FCMR: PORT-MISMATCH (NA)
FCMR: SIGLOSS (MJ)
FCMR: SYNCLOSS (MJ)
AOTS: GAIN-LFAIL (CR)
AOTS: LASER-APR (NA)
AOTS: LASERBIAS-DEG (MN)
AOTS: LASERBIAS-FAIL (MJ)
AOTS: LASERTEMP-DEG (MN)
AOTS: OPWR-HDEG (MN)
AOTS: OPWR-HFAIL (CR)
AOTS: OPWR-LDEG (MN)
AOTS: OPWR-LFAIL (CR)
AOTS: OSRION (NA)
AOTS: PARAM-MISM (NA)
AOTS: VOA-HDEG (MN)
AOTS: VOA-HFAIL (CR)
FCMR: TPTFAIL (MJ)
FUDC: AIS (NR)
FUDC: LOS (MN)
G1000: AS-CMD (NA)
G1000: AS-MT (NA)
G1000: CARLOSS (MJ)
G1000: LPBKFACILITY (NA)
G1000: LPBKTERMI(NA)L (NA)
G1000: TPTFAIL (MJ)
GE: ALS (NA)
GE: AS-CMD (NA)
GE: AS-MT (NA)
GE: CARLOSS (MJ)
OCN: SQUELCH (NA)
OCN: SQUELCHED (NA)
OCN: SSM-DUS (NA)
OCN: SSM-FAIL (MN)
OCN: SSM-OFF (NA)
OCN: SSM-PRS (NA)
OCN: SSM-RES (NA)
OCN: SSM-SDH-TN (NA)
OCN: SSM-SMC (NA)
OCN: SSM-ST2 (NA)
OCN: SSM-ST3 (NA)
OCN: SSM-ST3E (NA)
OCN: SSM-ST4 (NA)
OCN: SSM-STU (NA)
OCN: STS-SQUELCH-L (NA)
OCN: SYNC-FREQ (NA)
OCN: TIM (CR)
OCN: TIM-MON (MN)
OCN: TIM-S (CR)
OCN: VT-SQUELCH-L (NA)
OCN: WKSWPR (NA)
OCN: WTR (NA)
OMS: APC-CORRECTION-SKIPPED
(NA)
OMS: APC-OUT-OF-RANGE (NA)
OMS: AS-CMD (NA)
OMS: AS-MT (NA)
OMS: LOS-O (MN)
OMS: LOS-P (CR)
OMS: OPWR-HDEG (MN)
OMS: OPWR-HFAIL (CR)
OMS: OPWR-LDEG (MN)
OMS: OPWR-LFAIL (CR)
OMS: PARAM-MISM (NA)
OMS: PMI (NA)
OMS: VOA-HDEG (MN)
OMS: VOA-HFAIL (CR)
2-22
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
AOTS: VOA-LDEG (MN)
AOTS: VOA-LFAIL (CR)
BIC: MEA (CR)
BITS: AIS (NR)
BITS: BPV (MN)
BITS: HI-CCVOLT (NA)
BITS: LOF (MN)
BITS: LOS (MN)
BITS: SSM-DUS (NA)
BITS: SSM-FAIL (MN)
BITS: SSM-LNC (NA)
BITS: SSM-OFF (NA)
BITS: SSM-PRC (NA)
BITS: SSM-PRS (NA)
GE: FAILTOSW (NA)
GE: FORCED-REQ-SPAN (NA)
GE: GE-OOSYNC (CR)
GE: HI-LASERBIAS (MN)
GE: HI-RXPOWER (MN)
GE: HI-TXPOWER (MN)
GE: LMP-FAIL (MN)
GE: LMP-SD (MN)
GE: LMP-SF (MN)
GE: LMP-U(NA)LLOC (MN)
GE: LO-RXPOWER (MN)
GE: LO-TXPOWER (MN)
GE: LOCKOUT-REQ (NA)
GE: LPBKFACILITY (NA)
OMS: VOA-LDEG (MN)
OMS: VOA-LFAIL (CR)
OSC-RING: RING-ID-MIS (MJ)
OTS: APC-CORRECTION-SKIPPED
(NA)
OTS: APC-OUT-OF-RANGE (NA)
OTS: AS-CMD (NA)
OTS: AS-MT (NA)
OTS: AWG-DEG (MN)
OTS: AWG-FAIL (CR)
OTS: AWG-OVERTEMP (CR)
OTS: AWG-WARM-UP (NA)
OTS: LASERBIAS-DEG (MN)
OTS: LOS (CR)
OTS: LOS-O (MN)
BITS: SSM-RES (NA)
BITS: SSM-SETS (NA)
BITS: SSM-SMC (NA)
BITS: SSM-ST2 (NA)
BITS: SSM-ST3 (NA)
BITS: SSM-ST3E (NA)
BITS: SSM-ST4 (NA)
BITS: SSM-STU (NA)
BITS: SSM-TNC (NA)
BITS: SYNC-FREQ (NA)
GE: LPBKTERMI(NA)L (NA)
GE: MANUAL-REQ-SPAN (NA)
GE: OUT-OF-SYNC (MJ)
GE: SIGLOSS (MJ)
GE: SQUELCHED (NA)
GE: SYNCLOSS (MJ)
GE: WKSWPR (NA)
GE: WTR (NA)
GFP-FAC: AS-CMD (NA)
GFP-FAC: AS-MT (NA)
OTS: LOS-P (CR)
OTS: OPWR-HDEG (MN)
OTS: OPWR-HFAIL (CR)
OTS: OPWR-LDEG (MN)
OTS: OPWR-LFAIL (CR)
OTS: OSRION (NA)
OTS: PARAM-MISM (NA)
OTS: PMI (NA)
OTS: SH-INS-LOSS-VAR-DEG-HIGH
(MN)
OTS: SH-INS-LOSS-VAR-DEG-LOW
(MN)
BPLANE: AS-CMD (NA)
BPLANE: MFGMEM (CR)
CE1000: AS-CMD (NA)
GFP-FAC: GFP-CSF (MJ)
GFP-FAC: GFP-DE-MISMATCH (MJ)
OTS: SHUTTER-OPEN (NA)
OTS: SPAN-NOT-MEASURED (NA)
GFP-FAC: GFP-EX-MISMATCH (MJ) OTS: SPANLENGTH-OUT-OF-RANGE
(MN)
GFP-FAC: GFP-LFD (MJ) OTS: VOA-HDEG (MN) CE1000: AS-MT (NA)
CE1000: CARLOSS (MJ)
CE1000: GFP-CSF (MJ)
GFP-FAC: GFP-NO-BUFFERS (MJ) OTS: VOA-HFAIL (CR)
GFP-FAC: GFP-UP-MISMATCH (MJ) OTS: VOA-LDEG (MN)
CE1000: GFP-EX-MISMATCH (MJ) ISC: ALS (NA)
CE1000: GFP-LFD (MJ) ISC: AS-CMD (NA)
CE1000: GFP-UP-MISMATCH (MJ) ISC: AS-MT (NA)
CE1000: LPBKFACILITY (NA) ISC: CARLOSS (MJ)
OTS: VOA-LFAIL (CR)
PPM: AS-CMD (NA)
PPM: AS-MT (NA)
PPM: EQPT (CR)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-23
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
CE1000: LPBKTERMI(NA)L (NA) ISC: FAILTOSW (NA)
CE1000: TPTFAIL (MJ) ISC: FORCED-REQ-SPAN (NA)
CE100T: AS-CMD (NA)
CE100T: AS-MT (NA)
CE100T: CARLOSS (MJ)
CE100T: DATA-(CR)C (MJ)
CE100T: GFP-CSF (MJ)
CE100T: GFP-LFD (MJ)
CE100T: GFP-UP-MISMATCH (MJ) ISC: LOCKOUT-REQ (NA)
CE100T: LPBKFACILITY (NA) ISC: LOS (CR)
CE100T: LPBKTERMI(NA)L (NA) ISC: LPBKFACILITY (NA)
CE100T: TPTFAIL (MJ) ISC: LPBKTERMI(NA)L (NA)
CTRL: LMP-FAIL (MN)
DS1: AIS (NR)
DS1: AS-CMD (NA)
DS1: AS-MT (NA)
DS1: LOF (MJ)
DS1: LOS (MJ)
DS1: LPBKDS1FE-CMD (NA)
DS1: LPBKFACILITY (NA)
DS1: LPBKTERMI(NA)L (NA)
DS1: RAI (NA)
DS1: RCVR-MISS (MJ)
DS1: SD (NA)
DS1: SF (NA)
DS1: SSM-DUS (NA)
DS1: SSM-FAIL (MN)
DS1: SSM-OFF (NA)
DS1: SSM-PRS (NA)
DS1: SSM-RES (NA)
DS1: SSM-SMC (NA)
DS1: SSM-ST2 (NA)
DS1: SSM-ST3 (NA)
ISC: GE-OOSYNC (CR)
ISC: HI-LASERBIAS (MN)
ISC: HI-RXPOWER (MN)
ISC: HI-TXPOWER (MN)
ISC: LO-RXPOWER (MN)
ISC: LO-TXPOWER (MN)
ISC: MANUAL-REQ-SPAN (NA)
ISC: OUT-OF-SYNC (NA)
ISC: SIGLOSS (MJ)
ISC: SQUELCHED (NA)
ISC: SYNCLOSS (MJ)
ISC: WKSWPR (NA)
ISC: WTR (NA)
ML1000: AS-CMD (NA)
ML1000: AS-MT (NA)
ML1000: AUTONEG-RFI (MJ)
ML1000: CARLOSS (MJ)
ML1000: DATA-(CR)C (MJ)
PPM: HI-LASERBIAS (MN)
PPM: HI-LASERTEMP (MN)
PPM: HI-TXPOWER (MN)
PPM: IMPROPRMVL (CR)
PPM: LO-LASERBIAS (MN)
PPM: LO-LASERTEMP (MN)
PPM: LO-TXPOWER (MN)
PPM: MEA (CR)
PPM: MFGMEM (CR)
PPM: PROV-MISMATCH (MN)
PWR: AS-CMD (NA)
PWR: BAT-FAIL (MJ)
PWR: EHIBATVG (MJ)
PWR: ELWBATVG (MJ)
PWR: HIBATVG (MJ)
PWR: LWBATVG (MJ)
PWR: VOLT-MISM (NA)
RPRIF: MAX-STATIONS (MJ)
RPRIF:
RESERVED-RATE-EXCEEDED-RING
LET0 (MJ)
RPRIF:
RESERVED-RATE-EXCEEDED-RING
LET1 (MJ)
RPRIF: RPR-PASSTHR (NA)
RPRIF: RPR-PEER-MISS (MJ)
RPRIF: RPR-PROT-ACTIVE (NA)
RPRIF:
RPR-PROT-CONFIG-MISMATCH (MJ)
ML1000: FORCED-REQ (NA)
ML1000: GFP-CSF (MJ)
ML1000: GFP-LFD (MJ)
ML1000: GFP-UP-MISMATCH (MJ)
ML1000: LINK-KEEPALIVE (CR)
ML1000: MAN-REQ (NA)
RPRIF: RPR-RI-FAIL (MJ)
SHELF: AS-CMD (NA)
SHELF: AS-MT (NA)
SHELF: DUP-SHELF-ID (MJ)
SHELF: MEA (MJ)
SHELF: SHELF-COMM-FAIL (MJ)
ML1000: RPR-SD (NA)
ML1000: RPR-SF (NA)
STSMON: AIS-P (NR)
STSMON: AUTOSW-AIS (NR)
ML1000: RPR-SPAN-MISMATCH (MJ) STSMON: AUTOSW-LOP (NA)
2-24
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
DS1: SSM-ST3E (NA)
DS1: SSM-ST4 (NA)
DS1: SSM-STU (NA)
DS1: SYNC-FREQ (NA)
DS1: TRMT (MJ)
DS1: TRMT-MISS (MJ)
DS1: TX-AIS (NR)
DS1: TX-LOF (NR)
DS1: TX-RAI (NA)
DS3: AIS (NR)
DS3: AS-CMD (NA)
DS3: AS-MT (NA)
DS3: DS3-MISM (NA)
DS3: FE-AIS (NA)
DS3: FE-DS1-MULTLOS (NA)
DS3: FE-DS1-NSA (NA)
DS3: FE-DS1-SA (NA)
DS3: FE-DS1-SNGLLOS (NA)
DS3: FE-DS3-NSA (NA)
DS3: FE-DS3-SA (NA)
DS3: FE-EQPT-NSA (NA)
DS3: FE-IDLE (NA)
DS3: FE-LOF (NA)
DS3: FE-LOS (NA)
DS3: INC-ISD (NA)
DS3: LOF (CR)
DS3: LOS (CR)
DS3: LPBKDS3FEAC (NA)
DS3: LPBKDS3FEAC-CMD (NA)
DS3: LPBKFACILITY (NA)
DS3: LPBKTERMI(NA)L (NA)
DS3: RAI (NA)
DS3: SD (NA)
DS3: SF (NA)
DS3: TX-AIS (NR)
DS3: TX-RAI (NA)
E1000F: AS-CMD (NA)
ML1000: RPRW (NA)
ML1000: TPTFAIL (MJ)
ML1000: WTR (NA)
ML100T: AS-CMD (NA)
ML100T: AS-MT (NA)
ML100T: CARLOSS (MJ)
ML100T: DATA-(CR)C (MJ)
ML100T: FORCED-REQ (NA)
ML100T: GFP-CSF (MJ)
ML100T: GFP-LFD (MJ)
STSMON: AUTOSW-PDI (NA)
STSMON: AUTOSW-SDBER (NA)
STSMON: AUTOSW-SFBER (NA)
STSMON: AUTOSW-UNEQ (NA)
STSMON: ERFI-P-CONN (NR)
STSMON: ERFI-P-PAYLD (NR)
STSMON: ERFI-P-SRVR (NR)
STSMON: FAILTOSW-PATH (NA)
STSMON: FORCED-REQ (NA)
STSMON: LOCKOUT-REQ (NA)
ML100T: GFP-UP-MISMATCH (MJ)
ML100T: LINK-KEEPALIVE (CR)
ML100T: MAN-REQ (NA)
ML100T: RPR-SD (NA)
STSMON: LOM (CR)
STSMON: LOP-P (CR)
STSMON: LPBK(CR)S (NA)
STSMON: MAN-REQ (NA)
ML100T: RPR-SF (NA) STSMON: PDI-P (NA)
ML100T: RPR-SPAN-MISMATCH (MJ) STSMON: PLM-P (CR)
ML100T: RPRW (NA)
ML100T: TPTFAIL (MJ)
STSMON: RFI-P (NR)
STSMON: ROLL (NA)
ML100T: WTR (NA)
MLFX: AS-CMD (NA)
MLFX: AS-MT (NA)
MLFX: CARLOSS (MJ)
MLFX: DATA-(CR)C (MJ)
MLFX: FORCED-REQ (NA)
MLFX: GFP-CSF (MJ)
MLFX: GFP-LFD (MJ)
STSMON: ROLL-PEND (NA)
STSMON: SD-P (NA)
STSMON: SF-P (NA)
STSMON: TIM-P (MN)
STSMON: UNEQ-P (CR)
STSMON: WKSWPR (NA)
STSMON: WTR (NA)
STSTRM: AIS-P (NR)
MLFX: GFP-UP-MISMATCH (MJ)
MLFX: LINK-KEEPALIVE (CR)
MLFX: MAN-REQ (NA)
MLFX: RPR-SD (NA)
STSTRM: AS-MT-OOG (NA)
STSTRM: ENCAP-MISMATCH-P (CR)
STSTRM: ERFI-P-CONN (NR)
STSTRM: ERFI-P-PAYLD (NR)
MLFX: RPR-SF (NA) STSTRM: ERFI-P-SRVR (NR)
MLFX: RPR-SPAN-MISMATCH (MJ) STSTRM: LCAS-(CR)C (NA)
MLFX: RPRW (NA)
MLFX: TPTFAIL (MJ)
STSTRM: LCAS-RX-FAIL (NA)
STSTRM: LCAS-TX-ADD (NA)
MLFX: WTR (NA)
MSUDC: AIS (NR)
MSUDC: LOS (MN)
STSTRM: LCAS-TX-DNU (NA)
STSTRM: LOF (CR)
STSTRM: LOM (CR)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-25
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
E1000F: CARLOSS (MJ)
E100T: AS-CMD (NA)
E100T: CARLOSS (MJ)
E1: AIS (NR)
E1: AS-CMD (NA)
E1: AS-MT (NA)
E1: LOF (MJ)
E1: LOS (MJ)
E1: LPBKFACILITY (NA)
E1: LPBKTERMI(NA)L (NA)
E1: RAI (NA)
E1: RCVR-MISS (MJ)
E1: SD (NA)
E1: SF (NA)
E1: SSM-DUS (NA)
E1: SSM-FAIL (MN)
E1: SSM-OFF (NA)
E1: SSM-PRS (NA)
E1: SSM-RES (NA)
E1: SSM-SMC (NA)
E1: SSM-ST2 (NA)
E1: SSM-ST3 (NA)
E1: SSM-ST3E (NA)
E1: SSM-ST4 (NA)
E1: SSM-STU (NA)
E1: SYNC-FREQ (NA)
E1: TRMT (MJ)
E1: TRMT-MISS (MJ)
E1: TX-AIS (NR)
E1: TX-LOF (NR)
E1: TX-RAI (NA)
EC1: AIS-L (NR)
EC1: AS-CMD (NA)
EC1: AS-MT (NA)
EC1: LOF (CR)
EC1: LOS (CR)
EC1: LPBKFACILITY (NA)
NE-SREF: FRCDSWTOINT (NA)
NE-SREF: FRCDSWTOPRI (NA)
NE-SREF: FRCDSWTOSEC (NA)
NE-SREF: FRCDSWTOTHIRD (NA)
NE-SREF: FRNGSYNC (NA)
NE-SREF: FSTSYNC (NA)
NE-SREF: HLDOVRSYNC (NA)
NE-SREF: MANSWTOINT (NA)
NE-SREF: MANSWTOPRI (NA)
NE-SREF: MANSWTOSEC (NA)
NE-SREF: MANSWTOTHIRD (NA)
NE-SREF: SSM-LNC (NA)
NE-SREF: SSM-PRC (NA)
NE-SREF: SSM-PRS (NA)
NE-SREF: SSM-RES (NA)
NE-SREF: SSM-SETS (NA)
NE-SREF: SSM-SMC (NA)
NE-SREF: SSM-ST2 (NA)
NE-SREF: SSM-ST3 (NA)
NE-SREF: SSM-ST3E (NA)
NE-SREF: SSM-ST4 (NA)
NE-SREF: SSM-STU (NA)
NE-SREF: SSM-TNC (NA)
NE-SREF: SWTOPRI (NA)
NE-SREF: SWTOSEC (NA)
NE-SREF: SWTOTHIRD (NA)
NE-SREF: SYNCPRI (MJ)
NE-SREF: SYNCSEC (MN)
NE-SREF: SYNCTHIRD (MN)
NE: APC-DISABLED (NA)
NE: APC-END (NA)
NE: AS-CMD (NA)
NE: AUD-LOG-LOSS (NA)
NE: AUD-LOG-LOW (NA)
NE: DATAFLT (MN)
NE: DBOSYNC (MJ)
NE: DUP-IPADDR (MN)
STSTRM: LOP-P (CR)
STSTRM: LPBK(CR)S (NA)
STSTRM: OOU-TPT (NA)
STSTRM: PDI-P (NA)
STSTRM: PLM-P (CR)
STSTRM: RFI-P (NR)
STSTRM: ROLL (NA)
STSTRM: ROLL-PEND (NR)
STSTRM: SD-P (NA)
STSTRM: SF-P (NA)
STSTRM: SQM (CR)
STSTRM: TIM-P (CR)
STSTRM: UNEQ-P (CR)
TLINK: LMP-FAIL (MN)
TRUNK: AIS (NR)
TRUNK: AIS-L (NR)
TRUNK: ALS (NA)
TRUNK: AS-CMD (NA)
TRUNK: AS-MT (NA)
TRUNK: CARLOSS (MJ)
TRUNK: DSP-COMM-FAIL (MJ)
TRUNK: DSP-FAIL (MJ)
TRUNK: EOC (MN)
TRUNK: EOC-L (MN)
TRUNK: FAILTOSW (NA)
TRUNK: FC-NO-(CR)EDITS (MJ)
TRUNK: FEC-MISM (MJ)
TRUNK: FORCED-REQ-SPAN (NA)
TRUNK: GCC-EOC (MN)
TRUNK: GE-OOSYNC (CR)
TRUNK: HELLO (NA)
TRUNK: ISIS-ADJ-FAIL (MN)
TRUNK: LO-TXPOWER (MN)
TRUNK: LOCKOUT-REQ (NA)
TRUNK: LOF (CR)
TRUNK: LOM (CR)
TRUNK: LOS (CR)
2-26
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
EC1: LPBKTERMI(NA)L (NA)
EC1: RFI-L (NR)
EC1: SD-L (NA)
EC1: SF-L (NA)
EC1: TIM-S (CR)
ENVALRM: EXT (MN)
EQPT: ALS-DISABLED (NA)
EQPT: AS-CMD (NA)
EQPT: AS-MT (NA)
EQPT: AUTORESET (MN)
EQPT: BKUPMEMP (CR)
EQPT: CARLOSS (MJ)
EQPT: CLDRESTART (NA)
EQPT: COMIOXC (CR)
EQPT: COMM-FAIL (MN)
EQPT: CONTBUS-A-18 (MN)
OCH: APC-OUT-OF-RANGE (NA)
OCH: AS-CMD (NA)
OCH: AS-MT (NA)
OCH: FDI (NA)
EQPT: CONTBUS-B-18 (MN) OCH: LOS-O (MN)
EQPT: CONTBUS-DISABLED (CR) OCH: LOS-P (CR)
EQPT: CONTBUS-IO-A (MN)
EQPT: CONTBUS-IO-B (MN)
OCH: OPWR-HDEG (MN)
OCH: OPWR-HFAIL (CR)
EQPT: CTNEQPT-MISMATCH (NA) OCH: OPWR-LDEG (MN)
EQPT: CTNEQPT-PBPROT (CR) OCH: OPWR-LFAIL (CR)
EQPT: CTNEQPT-PBWORK (CR)
EQPT: EQPT (CR)
EQPT: EQPT-DIAG (CR)
NE: DUP-NODE(NA)ME (MN)
NE: ETH-LINKLOSS (NA)
NE: HITEMP (CR)
NE: I-HITEMP (CR)
NE: INTRUSION-PSWD (NA)
NE: LAN-POL-REV (NA)
NE: OPTNTWMIS (MJ)
NE: SNTP-HOST (MN)
NE: SYSBOOT (MJ)
NE: TEMP-MISM (NA)
OCH-TERM: OCHTERM-INC (NA)
OCH: APC-CORRECTION-SKIPPED
(NA)
EQPT: ERROR-CONFIG (MN)
EQPT: EXCCOL (MN)
EQPT: FAILTOSW (NA)
EQPT: FORCED-REQ (NA)
EQPT: HI-LASERBIAS (MN)
EQPT: HI-LASERTEMP (MN)
EQPT: HI-TXPOWER (MN)
EQPT: HITEMP (MN)
TRUNK: LOS-P (CR)
TRUNK: LPBKFACILITY (NA)
TRUNK: LPBKTERMI(NA)L (NA)
TRUNK: MANUAL-REQ-SPAN (NA)
TRUNK: ODUK-1-AIS-PM (NR)
TRUNK: ODUK-2-AIS-PM (NR)
TRUNK: ODUK-3-AIS-PM (NR)
TRUNK: ODUK-4-AIS-PM (NR)
TRUNK: ODUK-AIS-PM (NR)
TRUNK: ODUK-BDI-PM (NR)
TRUNK: ODUK-LCK-PM (NR)
TRUNK: ODUK-OCI-PM (NR)
TRUNK: ODUK-SD-PM (NA)
TRUNK: ODUK-SF-PM (NA)
TRUNK: ODUK-TIM-PM (MJ)
TRUNK: OTUK-AIS (NR)
TRUNK: OTUK-BDI (NR)
TRUNK: OTUK-IAE (MN)
TRUNK: OTUK-LOF (CR)
TRUNK: OTUK-SD (NA)
TRUNK: OTUK-SF (NA)
TRUNK: OTUK-TIM (CR)
OCH: PARAM-MISM (NA) TRUNK: OUT-OF-SYNC (MJ)
OCH: PORT-ADD-PWR-DEG-HI (MN) TRUNK: PROV-MISMATCH (MJ)
OCH: PORT-ADD-PWR-DEG-LOW
(MN)
OCH: PORT-ADD-PWR-FAIL-HIGH
(CR)
TRUNK: PTIM (MJ)
TRUNK: RFI (NR)
OCH: PORT-ADD-PWR-FAIL-LOW
(CR)
OCH: PORT-FAIL (CR)
TRUNK: RFI-L (NR)
TRUNK: SD (NA)
TRUNK: SD-L (NA)
TRUNK: SF (NA)
OCH: TRAIL-SIG(NA)L-FAIL (NA)
OCH:
U(NR)EACHABLE-TARGET-POWER
(MN)
OCH: VOA-HDEG (MN)
OCH: VOA-HFAIL (CR)
OCH: VOA-LDEG (MN)
TRUNK: SF-L (NA)
TRUNK: SIGLOSS (MJ)
TRUNK: SQUELCHED (NA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-27
Chapter 2 Alarm Troubleshooting
2.4 Alarm List by Logical Object Type
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
EQPT: IMPROPRMVL (CR)
EQPT: INHSWPR (NA)
EQPT: INHSWWKG (NA)
EQPT: IOSCFGCOPY (NA)
EQPT: LO-LASERBIAS (MN)
EQPT: LO-LASERTEMP (MN)
EQPT: LO-TXPOWER (MN)
EQPT: LOCKOUT-REQ (NA)
EQPT: MAN-REQ (NA)
EQPT: MA(NR)ESET (NA)
OCH: VOA-LFAIL (CR)
OCHNC-CONN: OCHNC-INC (NA)
OCN: AIS-L (NR)
OCN: ALS (NA)
OCN: APS-INV-PRIM (MN)
OCN: APS-PRIM-FAC (NA)
OCN: APS-PRIM-SEC-MISM (MN)
OCN: APSB (MN)
OCN: APSC-IMP (MN)
OCN: APSCDFLTK (MN)
EQPT: MEA (CR)
EQPT: MEM-GONE (MJ)
EQPT: MEM-LOW (MN)
EQPT: NO-CONFIG (NA)
OCN: APSCINCON (MN)
OCN: APSCM (MJ)
OCN: APSCNMIS (MJ)
OCN: APSIMP (MN)
EQPT: OPEN-SLOT (NA) OCN: APSMM (MN)
EQPT: PEER-NORESPONSE (MJ) OCN: AS-CMD (NA)
EQPT: PROT(NA) (MN)
EQPT: PWR-FAIL-A (MN)
OCN: AS-MT (NA)
OCN: AUTOLSROFF (CR)
TRUNK: SSM-DUS (NA)
TRUNK: SSM-FAIL (MN)
TRUNK: SSM-LNC (NA)
TRUNK: SSM-OFF (NA)
TRUNK: SSM-PRC (NA)
TRUNK: SSM-PRS (NA)
TRUNK: SSM-RES (NA)
TRUNK: SSM-SDH-TN (NA)
TRUNK: SSM-SETS (NA)
TRUNK: SSM-SMC (NA)
TRUNK: SSM-ST2 (NA)
TRUNK: SSM-ST3 (NA)
TRUNK: SSM-ST3E (NA)
TRUNK: SSM-ST4 (NA)
TRUNK: SSM-STU (NA)
TRUNK: SSM-TNC (NA)
TRUNK: SYNC-FREQ (NA)
TRUNK: SYNCLOSS (MJ)
EQPT: PWR-FAIL-B (MN)
EQPT: PWR-FAIL-RET-A (MN)
OCN: BLSR-SW-VER-MISM (MN)
OCN: BLSROSYNC (MJ)
EQPT: PWR-FAIL-RET-B (MN) OCN: E-W-MISMATCH (MJ)
EQPT: RUNCFG-SAVENEED (NA) OCN: EOC (MN)
TRUNK: TIM (CR)
TRUNK: TIM-MON (MN)
TRUNK: TRAIL-SIG(NA)L-FAIL (NA)
TRUNK: UNC-WORD (NA)
EQPT: SFTWDOWN (MN)
EQPT: SW-MISMATCH (NA)
OCN: EOC-L (MN)
OCN: EXERCISE-RING-FAIL (NA)
TRUNK: UT-COMM-FAIL (MJ)
TRUNK: UT-FAIL (MJ)
EQPT: SWMTXMOD-PROT (CR) OCN: EXERCISE-SPAN-FAIL (NA) TRUNK: WTR (NA)
EQPT: SWMTXMOD-WORK (CR) OCN: EXTRA-TRAF-PREEMPT (MJ) TRUNK: WVL-MISMATCH (MJ)
EQPT: WKSWPR (NA)
EQPT: WTR (NA)
ESCON: ALS (NA)
ESCON: AS-CMD (NA)
OCN: FAILTOSW (NA)
OCN: FAILTOSWR (NA)
VCG: LOA (CR)
VCG: VCG-DEG (NA)
OCN: FAILTOSWS (NA) VCG: VCG-DOWN (NA)
OCN: FE-FRCDWKSWBK-SPAN (NA) VT-MON: AIS-V (NR)
ESCON: AS-MT (NA)
ESCON: FAILTOSW (NA)
OCN: FE-FRCDWKSWPR-RING (NA)
OCN: FE-FRCDWKSWPR-SPAN (NA)
VT-MON: AUTOSW-AIS (NR)
VT-MON: AUTOSW-LOP (NA)
ESCON: FORCED-REQ-SPAN (NA) OCN: FE-LOCKOUTOFPR-SPAN (NA) VT-MON: AUTOSW-UNEQ (MN)
ESCON: HI-LASERBIAS (MN) OCN: FE-MANWKSWBK-SPAN (NA) VT-MON: FAILTOSW-PATH (NA)
ESCON: HI-RXPOWER (MN)
ESCON: HI-TXPOWER (MN)
ESCON: LO-RXPOWER (MN)
OCN: FE-MANWKSWPR-RING (NA) VT-MON: FORCED-REQ (NA)
OCN: FE-MANWKSWPR-SPAN (NA) VT-MON: LOCKOUT-REQ (NA)
OCN: FEPRLF (MN) VT-MON: LOP-V (MJ)
2-28
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.5 Trouble Notifications
Table 2-8 Alarm List by Logical Object in Alarm Profile (continued)
ESCON: LO-TXPOWER (MN)
ESCON: LOCKOUT-REQ (NA)
ESCON: LOS (CR)
ESCON: LPBKFACILITY (NA)
OCN: FORCED-REQ-RING (NA)
OCN: FORCED-REQ-SPAN (NA)
OCN: FULLPASSTHR-BI (NA)
OCN: HELLO (NA)
ESCON: LPBKTERMI(NA)L (NA) OCN: HI-LASERBIAS (MN)
ESCON: MANUAL-REQ-SPAN
(NA)
OCN: HI-LASERTEMP (MN)
ESCON: SIGLOSS (MJ)
ESCON: SQUELCHED (NA)
OCN: HI-RXPOWER (MN)
OCN: HI-TXPOWER (MN)
ESCON: WKSWPR (NA)
ESCON: WTR (NA)
OCN: ISIS-ADJ-FAIL (MN)
OCN: KB-PASSTHR (NA)
EXT-SREF: FRCDSWTOPRI (NA) OCN:
KBYTE-APS-CHANNEL-FAILURE
(MN)
EXT-SREF: FRCDSWTOSEC (NA) OCN: LASEREOL (MN)
EXT-SREF: FRCDSWTOTHIRD
(NA)
EXT-SREF: MANSWTOPRI (NA)
OCN: LKOUTPR-S (NA)
OCN: LMP-FAIL (MN)
EXT-SREF: MANSWTOSEC (NA) OCN: LMP-SD (MN)
EXT-SREF: MANSWTOTHIRD
(NA)
OCN: LMP-SF (MN)
EXT-SREF: SWTOPRI (NA)
EXT-SREF: SWTOSEC (NA)
OCN: LMP-U(NA)LLOC (MN)
OCN: LO-LASERBIAS (MN)
EXT-SREF: SWTOTHIRD (NA)
EXT-SREF: SYNCPRI (MN)
EXT-SREF: SYNCSEC (MN)
EXT-SREF: SYNCTHIRD (MN)
OCN: LO-LASERTEMP (MN)
OCN: LO-RXPOWER (MN)
OCN: LO-TXPOWER (MN)
OCN: LOCKOUT-REQ (NA)
FAN: EQPT-MISS (CR)
FAN: FAN (CR)
FAN: MEA (CR)
OCN: LOF (CR)
OCN: LOS (CR)
OCN: LPBKFACILITY (NA)
VT-MON: MAN-REQ (NA)
VT-MON: RFI-V (NR)
VT-MON: ROLL (NA)
VT-MON: ROLL-PEND (NA)
VT-MON: SD-V (NA)
VT-MON: SF-V (NA)
VT-MON: UNEQ-V (MJ)
VT-MON: WKSWPR (NA)
VT-MON: WTR (NA)
VT-TERM: AIS-V (NR)
VT-TERM: AS-MT-OOG (NA)
VT-TERM: LCAS-(CR)C (NA)
VT-TERM: LCAS-RX-FAIL (NA)
VT-TERM: LCAS-TX-ADD (NA)
VT-TERM: LCAS-TX-DNU (NA)
VT-TERM: LOM (MJ)
VT-TERM: LOP-V (MJ)
VT-TERM: OOU-TPT (NA)
VT-TERM: PLM-V (MJ)
VT-TERM: RFI-V (NR)
VT-TERM: SD-V (NA)
VT-TERM: SF-V (NA)
VT-TERM: SQM (MJ)
VT-TERM: TIM-V (MJ)
VT-TERM: UNEQ-V (MJ)
2.5 Trouble Notifications
The ONS 15454 system reports trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253-CORE, and graphical user interface (GUI) state indicators.These notifications are described in the following paragraphs.
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and status or descriptive notifications (if configured to do so) as conditions in the CTC Alarms window. Alarms typically signify a problem that the user needs to remedy, such as a loss of signal. Conditions do not necessarily require troubleshooting.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-29
Chapter 2 Alarm Troubleshooting
2.5.1 Alarm Characteristics
2.5.1 Alarm Characteristics
The ONS 15454 uses standard alarm entities to identify what is causing trouble. All alarms stem from hardware, software, environment, or operator-originated problems whether or not they affect service.
Current alarms for the network, CTC session, node, or card are listed in the Alarms tab. (In addition, cleared alarms are also found in the History tab.)
2.5.2 Condition Characteristics
Conditions include any problem detected on an ONS 15454 shelf. They can include standing or transient notifications. A snapshot of all current raised, standing conditions on the network, node, or card can be retrieved in the CTC Conditions window or using TL1's set of RTRV-COND commands. (In addition, some but not all cleared conditions are also found in the History tab.)
For a comprehensive list of all conditions, refer to the Cisco ONS SONET TL1 Command Guide . For
more information about transient conditions, see Chapter 3, “Transient Conditions.”
Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity and alarms and events appear on the Conditions tab. You can change this behavior for the
LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the
NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT value to TRUE on the NE Defaults tab.
For more information about changing NE defaults, refer to the “Maintain the Node” chapter in the
Cisco ONS 15454 Procedure Guide .
2.5.3 Severities
The ONS 15454 uses Telcordia-devised standard severities for alarms and conditions: Critical (CR),
Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are described below:
•
•
A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs immediate correction. Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a
Critical (CR), Service-Affecting (SA) alarm.
A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, loss of traffic on more than five DS-1 circuits is Critical (CR), but loss of traffic on one to four DS-1 circuits is Major (MJ).
•
•
•
Minor (MN) alarms generally are those that do not affect service. For example, the automatic protection switching (APS) byte failure (APSB) alarm indicates that line terminating equipment
(LTE) detects a byte failure on the signal that could prevent traffic from properly executing a traffic switch.
Not Alarmed (NA) conditions are information indicators, such as for free-run synchronization state
(FRNGSYNC) or a forced-switch to primary (FRCSWTOPRI) timing event. They could or could not require troubleshooting, as indicated in the entries.
Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or
MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be expected in the presence of primary alarms.
2-30
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.5.4 Alarm Hierarchy
Severities can be customized for an entire network or for single nodes, from the network level down to the port level by changing or downloading customized alarm profiles. These custom severities are subject to the standard severity-demoting rules given in Telcordia GR-474-CORE and shown in the
“2.5.4 Alarm Hierarchy” section on page 2-31
. Procedures for customizing alarm severities are located in the “Manage Alarms” chapter in the Cisco ONS 15454 Procedure Guide .
2.5.4 Alarm Hierarchy
All alarm, condition, and unreported event severities listed in this manual are default profile settings.
However in situations when traffic is not lost, such as when the alarm occurs on protected ports or circuits, alarms having Critical (CR) or Major (MJ) default severities can be demoted to lower severities such as Minor (MN) or Non-Service-Affecting (NSA) as defined in Telcordia GR-474-CORE.
A path alarm can be demoted if a higher-ranking alarm is raised for the same object. For example, If a path trace identifier mismatch (TIM-P) is raised on a circuit path and then a loss of pointer on the path
(LOP-P) is raised on the path, the LOP-P alarm stands and the TIM-P closes. The path alarm hierarchy used in the ONS 15454 system is shown in
.
Table 2-9
Priority
Highest
—
—
Lowest
Path Alarm Hierarchy
Condition Type
AIS-P
LOP-P
UNEQ-P
TIM-P
Facility (port) alarms also follow a hierarchy, which means that lower-ranking alarms are closed by
higher-ranking alarms. The facility alarm hierarchy used in the ONS 15454 is shown in Table 2-10 .
Table 2-10 Facility Alarm Hierarchy
—
—
—
—
—
—
—
—
—
—
Priority
Highest
—
Condition Type
LOS
LOF
AIS-L
SF-L
SD-L
RFI-L
TIM-S
AIS-P
LOP-P
SF-P
SD-P
UNEQ-P
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-31
Chapter 2 Alarm Troubleshooting
2.5.4 Alarm Hierarchy
Table 2-10
Priority
—
Lowest
Facility Alarm Hierarchy
Condition Type
TIM-P
PLM-P
Near-end failures and far-end failures follow different hierarchies. Near-end failures stand according to whether they are for the entire signal (LOS, LOF), facility (AIS-L), path (AIS-P, etc.) or VT (AIS-V,
etc.). The full hierarchy for near-end failures is shown in Table 2-11 . This table is taken from
Telcordia GR-253-CORE.
Table 2-11 Near-End Alarm Hierarchy
—
—
—
—
Priority
Highest
—
—
—
—
—
—
—
Lowest
Condition Type
LOS
LOF
AIS-L
AIS-P
1
LOP-P
2
UNEQ-P
TIM-P
PLM-P
AIS-V
LOP-V
UNEQ-V
PLM-V
DS-N AIS (if reported for outgoing DS-N signals)
1.
Although it is not defined as a defect or failure, all-ones STS pointer relay is also higher priority than LOP-P. Similarly, all-ones VT pointer relay is higher priority than LOP-V.
2.
LOP-P is also higher priority than the far-end failure RFI-P, which does not affect the detection of any near-end failures. Similarly, LOP-V is higher priority than
RFI-V.
The far-end failure alarm hierarchy is shown in
, as given in Telcordia GR-253-CORE.
Table 2-12 Far-End Alarm Hierarchy
Priority
Highest
—
Lowest
Condition Type
RFI-L
RFI-P
RFI-V
2-32
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.5.5 Service Effect
2.5.5 Service Effect
Service-Affecting (SA) alarms—those that interrupt service—could be Critical (CR), Major (MJ), or
Minor (MN) severity alarms. Service-Affecting (SA) alarms indicate service is affected.
Non-Service-Affecting (NSA) alarms always have a Minor (MN) default severity.
2.5.6 States
The Alarms or History tab State (ST) column indicate the disposition of the alarm or condition as follows:
•
•
•
A raised (R) event is one that is active.
A cleared (C) event is one that is no longer active.
A transient (T) event is one that is automatically raised and cleared in CTC during system changes such as user login, logout, loss of connection to node view, etc. Transient events do not require user action. These are listed in
Chapter 3, “Transient Conditions.”
2.6 Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS 15454. Personnel should not perform any procedures in this chapter unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances users should pay close attention to the following caution.
Caution Hazardous voltage or energy could be present on the backplane when the system is operating. Use caution when removing or installing cards.
Some troubleshooting procedures require installation or removal of OC-192 cards; in these instances users should pay close attention to the following warnings.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Warning Class 1 laser product. Statement 1008
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-33
Chapter 2 Alarm Troubleshooting
2.7 Alarm Procedures
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206
Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment.
This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207
2.7 Alarm Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.
Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner of the GUI is not indented. If it is, click it to turn it off. When you are done checking for alarms, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the “Manage Alarms” chapter in the Cisco ONS 15454 Procedure Guide .
Note When checking alarms, ensure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, refer to the “Manage Alarms” chapter in the Cisco ONS 15454
Procedure Guide.
2.7.1 AIS
Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity and alarms and events appear on the Conditions tab. You can change this behavior for the
LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the
NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT value to TRUE on the NE Defaults tab.
For more information about changing NE defaults, refer to the “Maintain the Node” chapter in the
Cisco ONS 15454 Procedure Guide .
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, DS3, E1, FUDC, MSUDC
DWDM Logical Object: TRUNK
The Alarm Indication Signal (AIS) condition indicates that this node is detecting an alarm indication signal in the incoming signal SONET overhead.
2-34
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.2 AIS-L
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Note ONS 15454 DS-3 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A
DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback.
Clear the AIS Condition
Step 1
Step 2
Step 3
Determine whether there are alarms on the upstream nodes and equipment, especially the
“LOS (OCN)” alarm on page 2-158
, or if there are out-of-service (OOS,MT or OOS,DSBLD) ports.
Clear the upstream alarms using the applicable procedures in this chapter.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.2 AIS-L
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: EC1, OCN
DWDM Logical Object: TRUNK
The AIS Line condition indicates that this node is detecting line-level AIS in the incoming signal. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
This condition can also be raised in conjunction with the
“TIM-S” alarm, page 2-239 if AIS-L is enabled.
Note ONS 15454 DS-3 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A
DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback.
Clear the AIS-L Condition
Step 1
Step 2
Complete the
“Clear the AIS Condition” procedure on page 2-35 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-35
Chapter 2 Alarm Troubleshooting
2.7.3 AIS-P
2.7.3 AIS-P
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
The AIS Path condition means that this node is detecting AIS in the incoming path. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
Clear the AIS-P Condition
Step 1
Step 2
Complete the “Clear the AIS Condition” procedure on page 2-35
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.4 AIS-V
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: VT-MON, VT-TERM
The AIS VT condition means that this node is detecting AIS in the incoming VT-level path.
See the
“1.11.2 AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits” section on page 1-128 for
more information.
Clear the AIS-V Condition
Step 1
Step 2
Complete the “Clear the AIS Condition” procedure on page 2-35
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.5 ALS
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.6 AMPLI-INIT
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-36
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.7 APC-CORRECTION-SKIPPED
2.7.7 APC-CORRECTION-SKIPPED
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.8 APC-DISABLED
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.9 APC-END
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.10 APC-OUT-OF-RANGE
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.11 APSB
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The APS Channel Byte Failure alarm occurs when LTE detects protection switching byte failure or an invalid switching code in the incoming APS signal. Some older SONET not manufactured by Cisco send invalid APS codes if they are configured in a 1+1 protection group with newer SONET nodes, such as the ONS 15454. These invalid codes cause an APSB alarm on an ONS 15454.
Step 1
Step 2
Step 3
Use an optical test set to examine the incoming SONET overhead to confirm inconsistent or invalid
K bytes. For specific procedures to use the test set equipment, consult the manufacturer. If corrupted
K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15454.
If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you could need to replace the upstream cards for protection switching to operate properly. Complete the
Replace a Traffic Card” procedure on page 2-266 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.12 APSCDFLTK
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-37
Chapter 2 Alarm Troubleshooting
2.7.13 APSC-IMP
SONET Logical Object: OCN
The APS Default K Byte Received alarm occurs during bidirectional line switched ring (BLSR) provisioning or when a BLSR is not properly configured, for example, when a four-node BLSR has one node configured as a path protection. When this misconfiguration occurs, a node in a path protection or
1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for
BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the
“BLSROSYNC” alarm on page 2-55 .
Clear the APSCDFLTK Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Complete the
“Identify a BLSR Ring Name or Node ID Number” procedure on page 2-253
to verify that each node has a unique node ID number.
Repeat
Step 1 for all nodes in the ring.
If two nodes have the same node ID number, complete the
“Change a BLSR Node ID Number” procedure on page 2-254
to change one node ID number so that each node ID is unique.
If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the
“E-W-MISMATCH” alarm on page 2-87
.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide provides procedures for fibering BLSRs.
If the alarm does not clear and the network is a four-fiber BLSR, ensure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if a working fiber is incorrectly attached to a protect fiber.
If the alarm does not clear, complete the
“Verify Node Visibility for Other Nodes” procedure on page 2-254
.
If nodes are not visible, complete the
“Verify or Create Node Section DCC Terminations” procedure on page 2-268
to ensure that section data communications channel (SDCC) terminations exist on each node.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.13 APSC-IMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
An Improper SONET APS Code alarm indicates three consecutive, identical frames containing:
•
•
•
•
Unused code in bits 6 through 8 of byte K2.
Codes that are irrelevant to the specific protection switching operation being requested.
Requests that are irrelevant to the ring state of the ring (such as a span protection switch request in a two-fiber ring NE).
ET code in K2 bits 6 through 8 received on the incoming span, but not sourced from the outgoing span.
2-38
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.13 APSC-IMP
Note This alarm can occur on a VT tunnel when it does not have VT circuits provisioned on it. It can also occur when the exercise command or a lockout is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.
Note The APSC-IMP alarm may be raised on a BLSR or MS-SPRing when a drop connection is part of a cross-connect loopback.
Note The APSC-IMP alarm may be momentarily raised on BLSR spans during PCA circuit creation or deletion across multiple nodes using CTC.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.
For specific procedures to use the test set equipment, consult the manufacturer.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
If the K byte is invalid, the problem lies with upstream equipment and not with the reporting ONS 15454.
Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.
If the K byte is valid, verify that each node has a ring name that matches the other node ring names.
Complete the
“Identify a BLSR Ring Name or Node ID Number” procedure on page 2-253 .
for all nodes in the ring.
If a node has a ring name that does not match the other nodes, make that node’s ring name identical to the other nodes. Complete the
“Change a BLSR Ring Name” procedure on page 2-253
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-39
Chapter 2 Alarm Troubleshooting
2.7.14 APSCINCON
2.7.14 APSCINCON
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
An APS Inconsistent alarm means that an inconsistent APS byte is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the
SONET signal from a working to a protect path when necessary. An inconsistent APS code occurs when three consecutive frames contain nonidentical APS bytes, which in turn give the receiving equipment conflicting commands about switching.
Clear the APSCINCON Alarm
Step 1
Step 2
Look for other alarms, especially the
“LOS (OCN)” alarm on page 2-158 , the
“LOF (OCN)” alarm on page 2-145
, or the
. Clearing these alarms clears the APSCINCON alarm.
If an APSINCON alarm occurs with no other alarms, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.15 APSCM
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
The APS Channel Mismatch alarm occurs when the ONS 15454 expects a working channel but receives a protect channel. In many cases, the working and protect 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. The APSCM alarm occurs only on the ONS 15454 when bidirectional protection is used on OC-N cards in a 1+1 protection group configuration. The APSCM alarm does not occur in an optimized 1+1 protection configuration.
Warning On the ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
2-40
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.16 APSCNMIS
Clear the APSCM Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Verify that the working-card channel fibers are physically connected directly to the adjoining node’s working-card channel fibers.
If the fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node’s protection-card channel fibers.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.16 APSCNMIS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
The APS Node ID Mismatch alarm occurs when the source node ID contained in the incoming APS channel K2 byte is not present in the ring map. The APSCNMIS alarm could occur and clear when a
BLSR is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains, the alarm clears when a K byte with a valid source node ID is received.
Clear the APSCNMIS Alarm
Step 1
Step 2
Step 3
Step 4
Complete the “Identify a BLSR Ring Name or Node ID Number” procedure on page 2-253 to verify that
each node has a unique node ID number.
If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.
Click Close in the Ring Map dialog box.
If two nodes have the same node ID number, complete the
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.
Note Applying and removing a lockout on a span causes the ONS node to generate a new K byte. The
APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.
Step 5 If the alarm does not clear, use the
“Initiate a Lockout on a BLSR Protect Span” procedure on page 2-261
to lock out the span.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-41
Chapter 2 Alarm Troubleshooting
2.7.17 APSIMP
Step 6
Step 7
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 to clear the
lockout.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.17 APSIMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The APS Invalid Code alarm occurs if a 1+1 protection group is not properly configured at both nodes to send or receive the correct APS byte. A node that is either configured for no protection or is configured for path protection or BLSR protection does not send the right K2 APS byte anticipated by a system configured for 1+1 protection. The 1+1 protect port monitors the incoming K2 APS byte and raises this alarm if it does not receive the byte.
The alarm is superseded by an APSCM or APSMM alarm, but not by an AIS condition. It clears when the port receives a valid code for 10 ms.
Clear the APSIMP Alarm
Step 1
Step 2
Step 3
Step 4
Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group. For procedures, refer to the “Turn Up Node” chapter in the
Cisco ONS 15454 Procedure Guide .
If the other end of the group is properly configured or the alarm does not clear after you have provisioned the group correctly, verify that the working ports and protect ports are cabled correctly.
Ensure that both protect ports are configured for SONET.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.18 APS-INV-PRIM
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: OCN
The Optimized 1+1 APS Primary Facility condition occurs on OC-N cards in an optimized 1+1 protection system if the incoming primary section header does not indicate whether it is primary or secondary.
Note APS-INV-PRIM is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.
2-42
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.19 APSMM
2.7.19 APSMM
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
An APS Mode Mismatch failure alarm occurs on OC-N cards when there is a mismatch of the protection switching schemes at the two ends of the span, such as being bidirectional at one end and unidirectional at the other. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional. APSMM can also occur if third-party equipment is provisioned as 1:N and the ONS 15454 is provisioned as 1+1.
If one end is provisioned for 1+1 protection switching and the other is provisioned for path protection switching, an APSMM alarm occurs in the ONS 15454 that is provisioned for 1+1 protection switching.
Clear the APSMM Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
For the reporting ONS 15454, display node view and verify the protection scheme provisioning: a.
b.
Click the Provisioning > Protection tabs.
Click the 1+1 protection group configured for the OC-N cards.
The chosen protection group is the protection group optically connected (with data communications channel, or DCC, connectivity) to the far end.
Click Edit .
c.
d.
Record whether the Bidirectional Switching check box is checked.
Click OK in the Edit Protection Group dialog box.
Log into the far-end node and verify that the OC-N 1+1 protection group is provisioned.
Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in
. If not, change it to match.
Click Apply .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.20 APS-PRIM-FAC
Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
SONET Logical Object: OCN
The Optimized 1+1 APS Invalid Primary Section condition occurs on OC-N cards in an optimized 1+1 protection system if there is an APS status switch between the primary and secondary facilities to identify which port is primary.
Note APS-PRIM-FAC is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-43
Chapter 2 Alarm Troubleshooting
2.7.21 APS-PRIM-SEC-MISM
Clear the APS-PRIM-FAC Condition
Step 1
Step 2
This condition clears when the card receives a valid primary section indication (1 or 2).
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.21 APS-PRIM-SEC-MISM
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: OCN
The Optimized 1+1 APS Primary Section Mismatch condition occurs on OC-N cards in an optimized
1+1 protection system if there is a mismatch between the primary section of the local node facility and the primary section of the remote-node facility.
Clear the APS-PRIM-SEC-MISM Alarm
Step 1
Step 2
Ensure that the local node and remote-node ports are correctly provisioned the same way. For more information about optimized 1+1 configurations, refer to the “Turn Up Node” chapter in the
Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.22 AS-CMD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BPLANE, CE1000, CE100T, DS1, DS3, E1, E1000F, E100T, EC1, EQPT,
FCMR, G1000, GFP-FAC, ML1000, ML100T, MLFX, NE, OCN, PWR
DWDM Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCH, OMS, OTS, PPM, SHELF,
TRUNK
The Alarms Suppressed by User Command condition applies to the network element (NE object), backplane, a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects. For example, suppressing alarms on a card also suppresses alarms on its ports.
Note For more information about suppressing alarms, refer to the “Manage Alarms” chapter in the
Cisco ONS 15454 Procedure Guide .
Clear the AS-CMD Condition
Step 1 For all nodes, in node view, click the Conditions tab.
2-44
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.23 AS-MT
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Click Retrieve . If you have already retrieved conditions, look under the Object column and Eqpt Type column and note what entity the condition is reported against, such as a port, slot, or shelf.
•
•
If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with
If the condition is reported against the backplane, go to
.
• If the condition is reported against the NE object, go to
Determine whether alarms are suppressed for a port and if so, raise the suppressed alarms: a.
b.
Double-click the card to open the card view.
Click the Provisioning > Alarm Profiles > Alarm Behavior tabs and complete one of the following substeps:
•
•
If the Suppress Alarms column check box is checked for a port row, deselect it and click Apply .
If the Suppress Alarms column check box is not checked for a port row, from the View menu choose Go to Previous View .
If the AS-CMD condition is reported for a card and not an individual port, in node view click the
Provisioning > Alarm Profiles > Alarm Behavior tabs.
Locate the row number for the reported card slot.
Click the Suppress Alarms column check box to deselect the option for the card row.
If the condition is reported for the backplane, the alarms are suppressed for cards such as the ONS 15454
AIP that are not in the optical or electrical slots. To clear the alarm, complete the following steps: a.
b.
In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.
In the backplane row, uncheck the Suppress Alarms column check box.
c.
Click Apply .
If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm, complete the following steps: a.
b.
In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs if you have not already done so.
Click the Suppress Alarms check box located at the bottom of the window to deselect the option.
c.
Click Apply .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.23 AS-MT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: CE1000, CE100T, DS1, DS3, E1, EC1, EQPT, FCMR, G1000, GFP-FAC,
ML1000, ML100T, MLFX, OCN
DWDM Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCH, OMS, OTS, PPM, SHELF,
TRUNK
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-45
Chapter 2 Alarm Troubleshooting
2.7.24 AS-MT-OOG
The Alarms Suppressed for Maintenance Command condition applies to OC-N and electrical cards and occurs when a port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations.
Clear the AS-MT Condition
Step 1
Step 2
Complete the “Clear an OC-N Card Facility or Terminal Loopback Circuit” procedure on page 2-268 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.24 AS-MT-OOG
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
The Alarms Suppressed on an Out-Of-Group VCAT Member condition is raised on an STS or VT member of a VCAT group whenever the member is in the IDLE (AS-MT-OOG) admin state. This condition can be raised when a member is initially added to a group. In the IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.
The AS-MT-OOG condition clears when an STS or VT member transitions to a different state from IDLE
(AS-MT-OOG) or when the member is removed completely from the VCAT group. The condition does not require troubleshooting unless it does not clear.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.25 AUD-LOG-LOSS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The Audit Trail Log Loss condition occurs when the log is 100 percent full and the oldest entries are being replaced while new entries are generated. The log capacity is 640 entries. The log must be off-loaded using the following procedure to make room for more entries.
Clear the AUD-LOG-LOSS Condition
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, click the Maintenance > Audit tabs.
Click Retrieve .
Click Archive .
In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.
Enter a name in the File Name field.
2-46
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.26 AUD-LOG-LOW
Step 6
Step 7
You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.
Click Save .
The 640 entries are saved in this file. New entries continue with the next number in the sequence, rather than starting over.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.26 AUD-LOG-LOW
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The Audit Trail Log Low condition occurs when the audit trail log is 80 percent full.
Note AUD-LOG-LOW is an informational condition and does not require troubleshooting.
2.7.27 AUTOLSROFF
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: OCN
The Auto Laser Shutdown alarm occurs when the OC-192 card temperature exceeds 194 degrees F
(90 degrees C). The internal equipment automatically shuts down the OC-192 laser when the card temperature rises to prevent the card from self-destructing.
Warning On the ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the AUTOLSROFF Alarm
Step 1 View the temperature displayed on the ONS 15454 LCD front panel (
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-47
Chapter 2 Alarm Troubleshooting
2.7.28 AUTONEG-RFI
Figure 2-1
Slot
Shelf LCD Panel
Status Port
8/18/03
04.06-002L-10
24˚C
FAN FAIL CRIT MAJ MIN
Step 2
Step 3
Step 4
If the temperature of the shelf exceeds 194 degrees F (90 degrees C), the alarm should clear if you solve the ONS 15454 temperature problem. Complete the
“Clear the HITEMP Alarm” procedure on page 2-120
.
If the temperature of the shelf is under 194 degrees F (90 degrees C), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the OC-192 card.
If card replacement does not clear the alarm, call Cisco TAC 1 800 553-2447 to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.
2.7.28 AUTONEG-RFI
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: ML1000
The autonegotiation remote fault indication (RFI) indicates that an ML1000 Gigabit Ethernet port cannot detect its far-end link partner. This is typically caused by a far-end port shutdown or a unidirectional fiber cut. The partner node is likely raising a CARLOSS alarm.
AUTONEG-RFI may also be caused by misconfigured autonegotiation parameters. This causes more of a soft failure as opposed to the
“CARLOSS (ML1000, ML100T, MLFX)” alarm, page 2-63
, which is typically caused by a failure like a loss of light or optical fiber. The alarm clears the partner node is detected.
Note The far end of an Ethernet link is usually a switch or router that does not use an ONS management system.
Clear the AUTONEG-RFI Alarm
Step 1
Step 2
Check for a
“CARLOSS (EQPT)” alarm on page 2-58
procedure in this chapter.
If the alarm does not clear or if there is no far-end CARLOSS, check the near-end Gigabit Ethernet port autonegotiation settings: a.
Double-click the ML1000 card to display the card view.
b.
c.
Click the upper IOS tab, then click Open IOS Connection .
In Privileged Executive mode, enter the following command: router# show interface gigabitethernet 0
2-48
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.29 AUTORESET
Step 3
Step 4
Step 5 d.
View the command output and record the autonegotiation setting, such as the following example:
Full-duplex, 1000Mb/s, Gbic not connected, Auto-negotiation output flow-control is off, input flow-control is on
View the autonegotiation configuration for the partner node. If it is ONS equipment, follow the previous step for this node. If the node is different vendor client equipment, follow that equipment documentation to obtain the information.
If the alarm does not clear, check for any fiber breaks such as on the transmit cable from the partner node to the near-end node.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.29 AUTORESET
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Automatic System Reset alarm occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.
AUTORESET typically clears after a card reboots (up to ten minutes). If the alarm does not clear, complete the following procedure.
Clear the AUTORESET Alarm
Step 1
Step 2
Step 3
Determine whether there are additional alarms that could have triggered an automatic reset. If there are, troubleshoot these alarms using the applicable section of this chapter.
If the card automatically resets more than once a month with no apparent cause, complete the
Replace a Traffic Card” procedure on page 2-266 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.30 AUTOSW-AIS
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, VT-MON
The Automatic unidirectional path protection Switch Caused by an AIS condition indicates that automatic path protection switching occurred because of an AIS condition. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.
Note This condition is only reported if the path protection is set up for revertive switching.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-49
Chapter 2 Alarm Troubleshooting
2.7.31 AUTOSW-LOP (STSMON)
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS Condition
Step 1
Step 2
Complete the “Clear the AIS Condition” procedure on page 2-35
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.31 AUTOSW-LOP (STSMON)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: STSMON
The Automatic path protection Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the
. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-LOP (STSMON) Condition
Step 1
Step 2
Complete the “Clear the LOP-P Alarm” procedure on page 2-149 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.32 AUTOSW-LOP (VT-MON)
Default Severity: Not Alarmed (NA), Service-Affecting (SA)
SONET Logical Object: VT-MON
The AUTOSW-LOP alarm for the VT monitor (VT-MON) indicates that automatic path protection switching occurred because of the
. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note This condition is only reported if the path protection is set up for revertive switching.
2-50
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.33 AUTOSW-PDI
Clear the AUTOSW-LOP (VT-MON) Condition
Step 1
Step 2
Complete the
“Clear the LOP-V Alarm” procedure on page 2-150
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.33 AUTOSW-PDI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: STSMON
The Automatic path protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a
. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-PDI Condition
Step 1
Step 2
Complete the
“Clear the PDI-P Condition” procedure on page 2-187
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.34 AUTOSW-SDBER
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON
The Automatic path protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a
“SD-P” condition on page 2-214 caused automatic path protection switching to occur. If
the path protection is configured for revertive switching, the path protection reverts to the working path when the SD-P is resolved.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-SDBER Condition
Step 1 Complete the
“Clear the SD-P Condition” procedure on page 2-214 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-51
Chapter 2 Alarm Troubleshooting
2.7.35 AUTOSW-SFBER
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.35 AUTOSW-SFBER
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON
The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a
“SF-P” condition on page 2-217 caused automatic path protection switching to occur. If the path
protection is configured for revertive switching, the path protection reverts to the working path when the
SF-P is resolved.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-SFBER Condition
Step 1
Step 2
Complete the “Clear the SF-P Condition” procedure on page 2-217 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.36 AUTOSW-UNEQ (STSMON)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: STSMON
The Automatic path protection Switch Caused by Unequipped condition indicates that an
, caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-UNEQ (STSMON) Condition
Step 1
Step 2
Complete the “Clear the UNEQ-P Alarm” procedure on page 2-245 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-52
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.37 AUTOSW-UNEQ (VT-MON)
2.7.37 AUTOSW-UNEQ (VT-MON)
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: VT-MON
AUTOSW-UNEQ (VT-MON) indicates that the
caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note This condition is only reported if the path protection is set up for revertive switching.
Clear the AUTOSW-UNEQ (VT-MON) Condition
Step 1
Step 2
Complete the
“Clear the UNEQ-V Alarm” alarm on page 2-247 procedure.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.
2.7.38 AWG-DEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.39 AWG-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.40 AWG-OVERTEMP
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.41 AWG-WARM-UP
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.42 BAT-FAIL
Default Severity: Major (MJ), Service-Affecting (SA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-53
Chapter 2 Alarm Troubleshooting
2.7.43 BKUPMEMP
SONET Logical Object: PWR
The Battery Fail alarm occurs when one of the two power supplies (A or B) is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so onsite information about the conditions is necessary for troubleshooting.
Clear the BAT-FAIL Alarm
Step 1
Step 2
Step 3
At the site, determine which battery is not present or operational.
Remove the power cable from the faulty supply. For procedures, refer to the “Install the Shelf and
Backplane Cable” chapter in the Cisco ONS 15454 Procedure Guide . Reverse the power cable installation procedure.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.43 BKUPMEMP
•
•
•
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P flash memory. The alarm occurs when the TCC2/TCC2P is in use and has one of four problems:
Flash manager fails to format a flash partition.
Flash manager fails to write a file to a flash partition.
•
Problem at the driver level.
Code volume fails cyclic redundancy checking (CRC, a method to verify for errors in data transmitted to the TCC2/TCC2P).
The BKUPMEMP alarm can also cause the
. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Caution A software update on a standby TCC2/TCC2P can take up to 30 minutes.
Clear the BKUPMEMP Alarm
Step 1
Step 2
Step 3
Verify that both TCC2/TCC2Ps are powered and enabled by confirming lighted ACT/SBY LEDs on the
TCC2/TCC2Ps.
Determine whether the active or standbyTCC2/TCC2P has the alarm.
If both TCC2/TCC2Ps are powered and enabled, reset the TCC2/TCC2P where the alarm is raised. If the card is the active TCC2/TCC2P, complete the
“Reset an Active TCC2/TCC2P Card and Activate the
Standby Card” procedure on page 2-263
. If the card is the standby TCC2/TCC2P: a.
Right-click the standby TCC2/TCC2P in CTC.
2-54
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.44 BLSROSYNC
Step 4 b.
c.
d.
Choose Reset Card from the shortcut menu.
Click Yes in the Are You Sure dialog box. The card resets, the FAIL LED blinks on the physical card.
Wait ten minutes to verify that the card you reset completely reboots.
If the TCC2/TCC2P you reset does not reboot successfully, or the alarm has not cleared, call Cisco TAC
1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265 . If the Cisco TAC
technician tells you to remove the card and reinstall a new one, follow the
Card” procedure on page 2-266 .
2.7.44 BLSROSYNC
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
The BLSR Out Of Synchronization alarm occurs is raised temporarily during a span upgrade, downgrade, or two-fiber to four-fiber mode upgrade and clears when the procedure is complete for all nodes on the ring. If the alarm does not clear, ensure that all maintenance procedures have completed for all nodes on the ring. If the alarm still does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.45 BLSR-SW-VER-MISM
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
The BLSR Software Version Mismatch alarm is raised by the TCC2/TCC2P when it checks all software versions for all nodes in a ring and discovers a mismatch in versions.
Clear the BLSR-SW-VER-MISM Alarm
Step 1
Step 2
Clear the alarm by loading the correct software version on the TCC2/TCC2P with the incorrect load. To download software, refer to the release-specific software download document.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.46 BPV
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: BITS
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-55
Chapter 2 Alarm Troubleshooting
2.7.47 CARLOSS (CE1000, CE100T)
The 64K Clock Bipolar Density Violation alarm is raised on the TCC2P card if there is a frequency variation in the 8K BITS clock.
The TCC2P card contains an 8K clock and a 64K clock. Each has some bipolar variation, which is normal. This alarm is raised on the 8K clock if that variation discontinues. The BPV alarm is demoted by an LOF or LOS against the BITS clock.
Note This alarm is not raised on the TCC2 card.
Clear the BPV Alarm
Step 1
Step 2
Reestablishing a normal BITS input signal clears the alarm. Clear any alarms on the incoming signal or against the BITS timing sources.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.47 CARLOSS (CE1000, CE100T)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE1000, CE100T
The Carrier Loss alarm is raised on CE-Series cards in Mapper mode when the port is In-Service (IS) state and if there is no carrier signal. Circuit need not be present to raise the alarm. In releases prior to 6.01 the
Carrier Loss alarm is raised on CE-100T-8 cards in Mapper mode when there is a circuit failure due to link integrity. It does not get raised when a user simply puts the port in the In-Service and Normal (IS-NR) service state.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the CARLOSS (CE100T) Alarm
Step 1
Step 2
Complete the “Clear the CARLOSS (G1000) Alarm” procedure on page 2-61 . However, rather than
checking for a TPTFAIL (G1000) at the end of the procedure, check for a
CE1000)” alarm on page 2-240 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2-56
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.48 CARLOSS (E1000F, E100T)
2.7.48 CARLOSS (E1000F, E100T)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: E1000F, E100T
A Carrier Loss alarm on the LAN E-Series Ethernet card is the data equivalent of the
“LOS (OCN)” alarm on page 2-158
. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of the CARLOSS alarm are a disconnected cable, an Ethernet Gigabit Interface
Converter (GBIC) fiber connected to an optical card rather than an Ethernet device, or an improperly installed Ethernet card. Ethernet card ports must be enabled for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
The CARLOSS alarm also occurs after a node database is restored. After restoration, the alarm clears in approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP).
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the CARLOSS (E1000F, E100T) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If no misconnection to an OC-N card exists, verify that the transmitting device is operational. If not, troubleshoot the device.
If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port. For specific procedures to use the test set equipment, consult the manufacturer.
If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the “Install Cards and
Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If a valid Ethernet signal is present, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266 for the Ethernet card.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the Ethernet card.
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.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-57
Chapter 2 Alarm Troubleshooting
2.7.49 CARLOSS (EQPT)
Step 9
An Ethernet manual cross-connect is used when another vendor’s equipment sits between ONS 15454 nodes, and the open systems interconnect/target identifier address resolution protocol
(OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, complete the following steps. The reappearing alarm could be a result of mismatched STS circuit sizes in the set up of the manual cross-connect. If the Ethernet circuit is not part of a manual cross-connect, the following steps do not apply. a.
Right-click anywhere in the row of the CARLOSS alarm.
b.
c.
d.
Click Select Affected Circuits in the shortcut menu that appears.
Record the information in the type and size columns of the highlighted circuit.
From the examination of the layout of your network, determine which ONS 15454 and card and card are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:
• Log into the ONS 15454 at the other end of the Ethernet manual cross-connect.
e.
•
•
Double-click the Ethernet card that is part of the Ethernet manual cross-connect.
Click the Circuits tab.
• Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The Ethernet manual cross-connect circuit connects the Ethernet card to an OC-N card at the same node.
Use the information you recorded to determine whether the two Ethernet circuits on each side of the
Ethernet manual cross-connect have the same circuit size.
If one of the circuit sizes is incorrect, complete the
“Delete a Circuit” procedure on page 2-268 and
reconfigure the circuit with the correct circuit size. For more information, refer to the “Create
Circuits and VT Tunnels” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.49 CARLOSS (EQPT)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: EQPT
A Carrier Loss on the LAN Equipment alarm generally occurs on OC-N cards when the ONS 15454 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 TCC2/TCC2P or the LAN backplane pin connection.
This CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the node.
On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G or MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 monitoring is turned off.
A TXP_MR_2.5G card can raise a CARLOSS alarm when the payload is incorrectly configured for the
10 Gigabit Ethernet or 1 Gigabit Ethernet payload data types.
2-58
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.49 CARLOSS (EQPT)
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual . For more information about MRC-12 and OC192-XFP/STM64-XFP cards, refer to the “Optical Cards” chapter in the
Cisco ONS 15454 Reference Manual . For more information about Ethernet cards, refer to the “Ethernet
Cards” chapter in the Cisco ONS 15454 Reference Manual .
Clear the CARLOSS (EQPT) Alarm
Step 1
Step 2
Step 3
Step 4
If the reporting card is an MXP or TXP card in an ONS 15454 node, verify the data rate configured on the pluggable port module (PPM): a.
b.
c.
Double-click the reporting MXP or TXP card.
Click the Provisioning > Pluggable Port Modules tabs.
d.
View the Pluggable Port Modules area port listing in the Actual Equipment Type column and compare this with the contents of the Selected PPM area Rate column for the MXP or TXP multirate port.
If the rate does not match the actual equipment, you must delete and recreate the selected PPM.
Select the PPM, click Delete , then click Create and choose the correct rate for the port rate.
If the reporting card is an OC-N card, verify connectivity by pinging the ONS 15454 that is reporting the alarm by completing the
“1.9.8 Verify PC Connection to the ONS 15454 (ping)” procedure on page 1-112
.
If the ping is successful, it demonstrates that an active TCP/IP connection exists. Restart CTC: a.
b.
Exit from CTC.
Reopen the browser.
c.
Log into CTC.
Using optical test equipment, verify that proper receive levels are achieved. (For instructions to use optical test equipment, refer to the manufacturer documentation.)
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-59
Chapter 2 Alarm Troubleshooting
2.7.50 CARLOSS (FC)
Step 6
Step 7
Step 8
Step 9
If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
If you are unable to establish connectivity, replace the fiber cable with a new known-good cable. To do this, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure
Guide .
If you are unable to establish connectivity, perform standard network or LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node and CTC. To verify cable continuity, follow site practices.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.50 CARLOSS (FC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.51 CARLOSS (G1000)
A Carrier Loss alarm on the LAN G-Series Ethernet card is the data equivalent of the
CARLOSS on the G1000-4 card is caused by one of two situations:
•
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: G1000
•
The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. The CARLOSS can be caused by an improperly connected Ethernet cable or a problem with the signal between the Ethernet device and the G1000-4 port.
If a problem exists in the end-to-end path (including possibly the far-end G1000-4 card), it causes the reporting card to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting
G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, other alarms such as the
“TPTFAIL (G1000)” alarm on page 2-241 or OC-N alarms or conditions on the end-to-end path
normally accompany the CARLOSS (G1000) alarm.
Refer to the Cisco ONS 15454 Reference Manual for a description of the G1000-4 card’s end-to-end
Ethernet link integrity capability. Also see the
“TRMT” alarm on page 2-243 for more information about
alarms that occur when a point-to-point circuit exists between two cards.
Ethernet card ports must be enabled for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
2-60
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.51 CARLOSS (G1000)
Clear the CARLOSS (G1000) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
If the fiber cable is correctly connected and attached, verify that the cable connects the card to another
Ethernet device and is not misconnected to an OC-N card.
If no misconnection to the OC-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.
Verify that optical receive levels are within the normal range. The correct specifications are listed in the
“1.12.3 OC-N Card Transmit and Receive Levels” section on page 1-140 .
If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port. For specific procedures to use the test set equipment, consult the manufacturer.
If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the “Install Cards and
Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, and link autonegotiation is enabled on the port but the autonegotiation process fails, the card turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, determine whether there are conditions that could cause autonegotiation to fail: a.
b.
Confirm that the attached Ethernet device has autonegotiation enabled and is configured for compatibility with the asymmetric flow control on the card.
Confirm that the attached Ethernet device configuration allows reception of flow control frames.
If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. (The autonegotiation process restarts.)
If the alarm does not clear and the
“TPTFAIL (G1000)” alarm on page 2-241 is also reported, complete
the
“Clear the TPTFAIL (G1000) Alarm” procedure on page 2-241 . If the TPTFAIL alarm is not raised,
continue to the next step.
Note When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition could be the G1000-4 card's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 10
Step 11
If the TPTFAIL alarm was not raised, determine whether a terminal (inward) loopback has been provisioned on the port: a.
b.
In node view, click the card to go to card view.
Click the Maintenance > Loopback tabs .
c.
If the service state is listed as OOS-MA,LPBK&MT, a loopback is provisioned. Go to
.
If a loopback was provisioned, complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-61
Chapter 2 Alarm Troubleshooting
2.7.52 CARLOSS (GE)
Step 12
On the G1000-4, provisioning a terminal (inward) loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.
If the does not have a loopback condition, continue to
If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm could be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps if the Ethernet circuit is part of a manual cross-connect:
Note An ONS 15454 Ethernet manual cross-connect is used when another vendor’s equipment sits between ONS nodes, and the OSI/TARP-based equipment does not allow tunneling of the
ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
Step 13
Step 14
Step 15 c.
d.
a.
b.
e.
f.
Right-click anywhere in the row of the CARLOSS alarm.
Right-click or left-click Select Affected Circuits in the shortcut menu that appears.
Record the information in the type and size columns of the highlighted circuit.
Examine the layout of your network and determine which ONS 15454 and card are hosting the
Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:
•
•
Log into the node at the other end of the Ethernet manual cross-connect.
Double-click the Ethernet card that is part of the Ethernet manual cross-connect.
Click the Circuits tab.
•
• Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit connects the Ethernet card to an OC-N card at the same node.
Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
If one of the circuit sizes is incorrect, complete the
“Delete a Circuit” procedure on page 2-268 and
reconfigure the circuit with the correct circuit size. Refer to the “Create Circuits and VT Tunnels” chapter in the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.
.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the Ethernet card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.52 CARLOSS (GE)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-62
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.53 CARLOSS (ISC)
2.7.53 CARLOSS (ISC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.54 CARLOSS (ML1000, ML100T, MLFX)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: ML1000, ML100T, MLFX
A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the
A CARLOSS alarm occurs when the Ethernet port has been configured from the Cisco IOS command line interface (CLI) as a no-shutdown port and one of the following problems also occurs:
• The cable is not properly connected to the near or far port.
•
•
Autonegotiation is failing (which raises the
“AUTONEG-RFI” alarm, page 2-48
).
The speed (10/100 ports only) is set incorrectly.
Note For information about provisioning ML-Series Ethernet cards from the Cisco IOS interface, refer to the
Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the CARLOSS (ML1000, ML100T, MLFX) Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Verify that the LAN cable is properly connected and attached to the correct port on the ML-Series card and on the peer Ethernet port. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, verify that autonegotiation is set properly on the ML-Series card port and the peer Ethernet port.
If the alarm does not clear, verify that the speed is set properly on the ML-Series card port and the peer
Ethernet port if you are using 10/100 ports.
If the alarm does not clear, the Ethernet signal is not valid, but the transmitting device is operational, replace the LAN cable connecting the transmitting device to the Ethernet port.
If the alarm does not clear, disable and reenable the Ethernet port by performing a “shutdown” and then a “no shutdown” on the Cisco IOS CLI as in the following example: router(config)# shut router(config)# no shut
This action restarts autonegotiation.
If the alarm does not clear, complete the
“Create the Facility Loopback on the Source DS-1, DS-3,
DS3N-12, DS3i-N-12, or EC1 Port” procedure on page 1-10 and test the loopback.
If the problem persists with the loopback installed, complete the “Remove and Reinsert (Reseat) Any
Card” procedure on page 2-266 .
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-63
Chapter 2 Alarm Troubleshooting
2.7.55 CARLOSS (TRUNK)
Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.55 CARLOSS (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.56 CASETEMP-DEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.57 CLDRESTART
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 power is initialized.
Clear the CLDRESTART Condition
Step 1
Step 2
Step 3
Step 4
Complete the “Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
.
If the condition fails to clear after the card reboots, complete the
“Remove and Reinsert (Reseat) Any
.
If the condition does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.58 COMIOXC
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Input/Output Slot To Cross-Connect Communication Failure alarm is caused by the XC10G or
XC-VXC-10G cross-connect card when there is a communication failure for a traffic slot.
2-64
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.59 COMM-FAIL
Clear the COMIOXC Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 on the card in which the alarm is
reported. For the LED behavior, see the
“2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the CTC reset does not clear the alarm, move traffic off the reporting cross-connect card. Complete the
“Side Switch the Active and Standby Cross-Connect Cards” procedure on page 2-264 .
Complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266 on the card in which
the alarm is reported.
If the alarm does not clear, complete the
“Physically Replace an In-Service Cross-Connect Card” procedure on page 2-266
for the reporting cross-connect card or complete the
Traffic Card” procedure on page 2-266
on the card in which the alarm is reported.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.59 COMM-FAIL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2/TCC2P and the traffic card. The failure could indicate a broken card interface.
Clear the COMM-FAIL Alarm
Step 1
Step 2
Step 3
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for the reporting card.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.60 CONTBUS-A-18
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2/TCC2P slot to
TCC2/TCC2P slot occurs when the main processor on the TCC2/TCC2P in the first slot (TCC A) loses communication with the coprocessor on the same card. This applies to the TCC2/TCC2P in Slot 7.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-65
Chapter 2 Alarm Troubleshooting
2.7.61 CONTBUS-B-18
Clear the CONTBUS-A-18 Alarm
Step 1
Step 2
Step 3
Step 4
Complete the
“Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
to make the TCC2/TCC2P in Slot 11 active.
Wait approximately 10 minutes for the TCC2/TCC2P in Slot 7 to reset as the standby TCC2/TCC2P.
Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Position the cursor over the TCC2/TCC2P in Slot 11 and complete the
Card and Activate the Standby Card” procedure on page 2-263 to return the card to the active state.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
(1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the
TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263 . If the Cisco TAC
technician tells you to remove the card and reinstall a new one, follow the
.
2.7.61 CONTBUS-B-18
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2/TCC2P slot to
TCC2/TCC2P slot occurs when the main processor on the TCC2/TCC2P in the second slot (TCC B) loses communication with the coprocessor on the same card. This applies to the Slot 11 TCC2/TCC2P.
Clear the CONTBUS-B-18 Alarm
Step 1
Step 2
Step 3
Step 4
Complete the “Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
to make the Slot 7 TCC2/TCC2P active.
Wait approximately 10 minutes for the Slot 11 TCC2/TCC2P to reset as the standby TCC2/TCC2P.
Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Position the cursor over the Slot 7 TCC2/TCC2P and complete the
“Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
to return the Slot 11 TCC2/TCC2P to the active state.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
(1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the
.
2.7.62 CONTBUS-DISABLED
Default Severity: Critical (CR), Service-Affecting (SA)
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-66 November 2009
Chapter 2 Alarm Troubleshooting
2.7.63 CONTBUS-IO-A
SONET Logical Object: EQPT
The CONTBUS-DISABLED alarm is a function of the enhanced cell bus verification feature. This alarm occurs when a defective card is installed in the shelf assembly or when a card already installed in the shelf assembly becomes defective (that is, the card fails the enhanced cell bus verification test). The alarm persists as long as the defective card remains in the chassis. When the card is removed,
CONTBUS-DISABLED will remain raised for a one-minute wait time. This wait time is designed as a guard period so that the system can distinguish this outage from a briefer card reset communication outage.
If no card is reinserted into the original slot during the wait time, the alarm clears. After this time, a different, nondefective card (not the original card) should be inserted.
When CONTBUS-DISABLED is raised, no message-oriented communication is allowed to or from this slot to the TCC2/TCC2P (thus avoiding node communication failure).
Caution CONTBUS-DISABLED clears only when the faulty card is removed for one minute. If any card at all is reinserted before the one-minute guard period expires, the alarm does not clear.
CONTBUS-DISABLED overrides
, during the one-minute wait period, but afterward IMPROPRMVL can be raised because it is no longer suppressed. IMPROPRMVL is raised after CONTBUS-DISABLED clears if the card is in the node database. If CONTBUS-DISABLED has cleared but IMPROPRMVL is still active, inserting a card will clear the IMPROPRMVL alarm.
Clear the CONTBUS-DISABLED Alarm
Step 1
Step 2
If the IMPROPRMVL alarm is raised, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
. (For general information about card installation, refer to the “Install Cards and Fiber-Optic
Cable” chapter in the Cisco ONS 15454 Procedure Guide .)
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.63 CONTBUS-IO-A
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A TCCA to Shelf A Slot Communication Failure alarm occurs when the active Slot 7 TCC2/TCC2P
(TCC 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 15454 switches to the protect
TCC2/TCC2P. In the case of a TCC2/TCC2P protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P to the reporting card. The physical path of communication includes the TCC2/TCC2P, the other card, and the backplane.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-67
Chapter 2 Alarm Troubleshooting
2.7.64 CONTBUS-IO-B
Clear the CONTBUS-IO-A Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Ensure that the reporting card is physically present in the shelf. Record the card type. Click the
Inventory tab and view the Eqpt Type column to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the
“MEA (EQPT)” alarm on page 2-177
for the reporting card.
If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P, perform a CTC reset of the object card. Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 . For the
LED behavior, see the
“2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
If the alarm object is the standby Slot 11 TCC2/TCC2P, complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for it. The procedure is similar.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.)
If CONTBUS-IO-A is raised on several cards at the same time, complete the
TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263 .
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the
.
2.7.64 CONTBUS-IO-B
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A TCC B to Shelf Communication Failure alarm occurs when the active Slot 11 TCC2/TCC2P (TCC B) 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-B alarm could appear briefly when the ONS 15454 switches to the protect
TCC2/TCC2P. In the case of a TCC2/TCC2P protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P to the reporting card. The physical path of communication includes the TCC2/TCC2P, the other card, and the backplane.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the
Inventory tab and view the Eqpt Type column to reveal the provisioned type.
2-68
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.65 CTNEQPT-MISMATCH
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
If the actual card type and the provisioned card type do not match, see the
“MEA (EQPT)” alarm on page 2-177
for the reporting card.
If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P, perform a CTC reset of the object card. Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
. For the
LED behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
for it. The procedure is similar.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.)
If CONTBUS-IO-B is raised on several cards at the same time, complete the “Reset an Active
TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the CTC reset does not clear the alarm, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the reporting card.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265 . If the Cisco TAC
technician tells you to remove the card and reinstall a new one, follow the
Card” procedure on page 2-266 .
2.7.65 CTNEQPT-MISMATCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Connection Equipment Mismatch condition is raised when there is a mismatch between the cross-connect card preprovisioned in the slot and the card actually installed in the shelf. For example, one type of cross-connect card could be preprovisioned in Slot 10, but another could be physically installed. It can also be caused by a card that is mismatched with the card. For example,
CTNEQPT-MISMATCH is raised when an XCVT card is replaced with a XC10G card.
Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation could briefly occur during the upgrade process.
The cross-connect card you are replacing should not be the active card. (It can be in SBY state or otherwise not in use.)
Note During an upgrade, this condition occurs and is raised as its default severity, Not Alarmed (NA).
However, after the upgrade has occurred, if you wish to change the condition’s severity so that it is
Not Reported (NR), you can do this by modifying the alarm profile used at the node. For more information about modifying alarm severities, refer to the “Manage Alarms” chapter in the
Cisco ONS 15454 Procedure Guide .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-69
Chapter 2 Alarm Troubleshooting
2.7.66 CTNEQPT-PBPROT
Clear the CTNEQPT-MISMATCH Condition
Step 1
Step 2
Step 3
Determine what kind of card is preprovisioned in the slot: a.
b.
In node view, click the Inventory tab.
View the information for the slot in the Eqpt Type and Actual Eqpt Type columns.
The Eqpt Type column contains the equipment that is provisioned in the slot. The Actual Eqpt Type contains the equipment that is physically present in the slot. For example, Slot 8 could be provisioned for an XCVT card, which is shown in the Eqpt Type column, but an XC10G XC10G card could be physically present in the slot. The XC10G would be shown in the Actual Eqpt Type column.
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 for the mismatched card.
If the condition does not clear, log onto http://www.cisco.com/techsupport for more information or call
Cisco TAC 1 800 553-2447.
2.7.66 CTNEQPT-PBPROT
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the protect ONS 15454 Slot 10 XC10G card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane.
The problem exists in the cross-connect card and the reporting traffic card, or the TCC2/TCC2P and the backplane.
Note This alarm automatically raises and clears when the Slot 8 XC10G card is reseated.
Caution A software update on a standby TCC2/TCC2P can take up to 30 minutes.
Clear the CTNEQPT-PBPROT Alarm
Step 1 If all traffic cards show CTNEQPT-PBPROT alarm, complete the following steps: a.
Complete the “Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
for the standby TCC2/TCC2P. b.
for the standby TCC2/TCC2P.
Caution Do not physically reseat an active TCC2/TCC2P. Doing so disrupts traffic.
2-70
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.67 CTNEQPT-PBWORK
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
. For the LED behavior, see the “2.8.2 Typical Traffic
Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the cross-connect reset is not complete and error-free or if the TCC2/TCC2P reboots automatically, call Cisco TAC 1 800 553-2447.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the standby OC-192 card.
Determine whether the card is an active card or standby card in a protection group. Click the node view
Maintenance > Protection tabs, then click the protection group. The cards and their status are displayed in the list.
Switch Command” procedure on page 2-257
. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
on the reporting card. For the LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the reporting card.
Complete the
“Initiate a 1:1 Card Switch Command” procedure on page 2-257 to switch traffic back.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting traffic card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.67 CTNEQPT-PBWORK
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the ONS 15454 Slot 8 XC10G card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane.
The problem exists in the cross-connect card and the reporting traffic card, or the TCC2/TCC2P and the backplane.
Note This alarm automatically raises and clears when the ONS 15454 Slot 10 XC10G card is reseated.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-71
Chapter 2 Alarm Troubleshooting
2.7.67 CTNEQPT-PBWORK
Clear the CTNEQPT-PBWORK Alarm
Step 1 If all traffic cards show CTNEQPT-PBWORK alarm, complete the following steps: a.
b.
Complete the “Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
for the active TCC2/TCC2P and then complete the
“Remove and Reinsert (Reseat) the
Standby TCC2/TCC2P Card” procedure on page 2-265
.
for the TCC2/TCC2P.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Caution Do not physically reseat an active TCC2/TCC2P; it disrupts traffic.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
If all cards do not show the alarm, complete the
“Side Switch the Active and Standby Cross-Connect
Cards” procedure on page 2-264
for the active XC10G card.
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
for the reporting card. For the LED behavior, see the
“2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the standby cross-connect card.
If the alarm does not clear and the reporting traffic card is the active card in the protection group,
complete the “Initiate a 1:1 Card Switch Command” procedure on page 2-257
. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
for the reporting card. For the LED behavior, see the
“2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If you switched traffic, complete the “Initiate a 1:1 Card Switch Command” procedure on page 2-257
to revert the traffic.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the OC-192 card.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting traffic card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2-72
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.68 DATA-CRC
2.7.68 DATA-CRC
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE100T, ML100T, ML1000, MLFX
The data cyclic redundancy check (CRC) Bad Packet Count Exceeds Threshold alarm indicates that
Cisco proprietary ring-wrapping (RPR) has been triggered for an ML-Series card in high-level data link
(HDLC) mode, but no SONET or data-level alarm is raised along with
RPRW, page 209 , to indicate the
failure.
In a typical scenario that triggers Cisco proprietary RPR protection, the errored node raises RPRW, and
SONET or data errors such as
TPTFAIL (ML100T, ML1000, MLFX), page 242 . If, however, a
packet-over-SONET (POS) port is placed in down administrative state, the card will raise an RPRW without raising any SONET B3 bit alarms or data alarms. The DATA-CRC alarm accompanies this instance of RPRW to indicate the signal interruption.
Clear the DATA-CRC Alarm
Step 1
Step 2
Step 3
Determine whether the
, is raised on the ring. If so, clear it using the appropriate trouble-clearing procedure in this chapter.
If the DATA-CRC alarm does not clear, check whether the alarmed card POS port is in the Down administrative state: a.
Double-click the ML-Series card to display the card view.
b.
c.
Click the Provisioning > POS Ports tabs.
View the port’s setting in the Admin State column. If it is Down, verify that both POS ports are properly configured. Refer to the Ethernet Card Software Feature and Configuration Guide for the
Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 for configuration information.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.69 DATAFLT
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The Software Data Integrity Fault alarm occurs when the TCC2/TCC2P exceeds its flash memory capacity.
Caution When the system reboots, the last configuration entered is not saved.
Clear the DATAFLT Alarm
Step 1 Complete the
“Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-73
Chapter 2 Alarm Troubleshooting
2.7.70 DBOSYNC
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.70 DBOSYNC
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: NE
The Standby Database Out Of Synchronization alarm occurs when the standby TCC2/TCC2P database does not synchronize with the active database on the active TCC2/TCC2P.
Caution If you reset the active TCC2/TCC2P while this alarm is raised, you lose current provisioning.
Clear the DBOSYNC Alarm
Step 1
Step 2
Step 3
Save a backup copy of the active TCC2/TCC2P database. Refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide for procedures.
Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm: a.
In node view, click the Provisioning > General > General tabs.
b.
In the Description field, make a small change such as adding a period to the existing entry.
The change causes a database write but does not affect the node state. The write could take up to a minute.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.71 DISCONNECTED
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm clears when CTC reconnects to the node.
Clear the DISCONNECTED Alarm
Step 1
Step 2
Restart CTC.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).
2-74
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.72 DS3-MISM
2.7.72 DS3-MISM
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on a signal transiting the ONS 15454 DS3XM-6, DS3XM-12, or DS3/EC1-48 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type for a DS3XM-6 card is set to C Bit and the incoming signal frame format is detected as M13, then the
ONS 15454 reports a DS3-MISM condition.
Clear the DS3-MISM Condition
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Display the CTC card view for the reporting DS3XM-6, DS3XM-12, or DS3/EC1-48 card.
Click the Provisioning > Line tabs.
For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal (C Bit or M13).
If the Line Type field does not match the expected incoming signal, select the correct Line Type in the drop-down list.
Click Apply .
If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 matches the expected incoming signal. For specific procedures to use the test set equipment, consult the manufacturer.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.73 DSP-COMM-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.74 DSP-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.75 DUP-IPADDR
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: NE
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-75
Chapter 2 Alarm Troubleshooting
2.7.76 DUP-NODENAME
The Duplicate IP Address alarm indicates that the alarmed node IP address is already in use within the same DCC area. When this happens, CTC no longer reliably connects to either node. Depending on how the packets are routed, CTC could connect to either node (having the same IP address). If CTC has connected to both nodes before they shared the same address, it has two distinct NodeModel instances
(keyed by the node ID portion of the MAC address).
Clear the DUP-IPADDR Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Isolate the alarmed node from the other node having the same address: a.
b.
Connect to the alarmed node using the Craft port on the TCC2/TCC2P card.
Begin a CTC session.
c.
In the login dialog window, uncheck the Network Discovery check box.
In node view, click the Provisioning > Network > General tabs.
In the IP Address field, change the IP address to a unique number.
Click Apply .
Restart any CTC sessions that are logged into either of the duplicate IP addresses. (For procedures to log in or log out, refer to the “Connect the PC and Log Into the GUI” chapter in the Cisco ONS 15454
Procedure Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.76 DUP-NODENAME
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The Duplicate Node Name alarm indicates that the alarmed node alphanumeric name is already being used within the same DCC area.
Clear the DUP-NODENAME Alarm
Step 1
Step 2
Step 3
Step 4
In node view, click the Provisioning > General > General tabs.
In the Node Name/TID field, enter a unique name for the node.
Click Apply .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-76
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.77 DUP-SHELF-ID
2.7.77 DUP-SHELF-ID
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.78 EHIBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: PWR
The Extreme High Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage exceeds the extreme high power threshold. This threshold, with a default value of –56.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for
120 seconds.
Clear the EHIBATVG Alarm
Step 1
Step 2
The problem is external to the ONS 15454. Troubleshoot the power source supplying the battery leads.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.79 ELWBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: PWR
The Extreme Low Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage falls below the extreme low power threshold. This threshold, with a default value of –40.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains over the threshold for
120 seconds.
Clear the ELWBATVG Alarm
Step 1
Step 2
The problem is external to the ONS 15454. Troubleshoot the power source supplying the battery leads.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.80 ENCAP-MISMATCH-P
Default Severity: Critical (CR), Service-Affecting (SA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-77
Chapter 2 Alarm Troubleshooting
2.7.80 ENCAP-MISMATCH-P
SONET Logical Object: STSTRM
The Encapsulation C2 Byte Mismatch Path alarm applies to ML-Series Ethernet cards. It occurs when the first three following conditions are met and one of the last two is false:
• The received C2 byte is not 0x00 (unequipped).
•
•
•
•
The received C2 byte is not a PDI value.
The received C2 does not match the expected C2.
The expected C2 byte is not 0x01 (equipped unspecified).
The received C2 byte is not 0x01 (equipped unspecified).
(This is in contrast to the
, which must meet all five criteria.) For an
ENCAP-MISMATCH-P to be raised, there is a mismatch between the received and expected C2 byte, with either the expected byte or received byte value being 0x01.
For example, an ENCAP-MISMATCH-P alarm is raised if a circuit created between two ML-Series cards has generic framing procedure (GFP) framing provisioned on one end and HDLC framing with
LEX encapsulation provisioned on the other. The GFP framing card transmits and expects a C2 byte of
0x1B, while the HDLC framing card transmits and expects a C2 byte of 0x01.
A mismatch between the transmit and receive cards on any of the following parameters can cause the alarm:
• Mode (HDLC, GFP-F)
•
•
Encapsulation (LEX, HDLC, PPP)
CRC size (16 or 32)
• Scrambling state (on or off)
This alarm is demoted by a
“PLM-P” condition on page 2-189 or a
“PLM-V” condition on page 2-190 .
Note By default, an ENCAP-MISMATCH-P alarm causes an ML-Series card data link to go down. This behavior can be modified using the command line interface (CLI) command in interface configuration mode: no pos trigger defect encap .
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Clear the ENCAP-MISMATCH-P Alarm
Step 1
Step 2
Ensure that the correct framing mode is in use on the receive card: a.
In node view, double-click the receive ML-Series card to open the card view.
b.
c.
Click the Provisioning > Card tabs.
In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply .
Ensure that the correct framing mode is in use on the transmit card, and that it is identical to the receiving card: a.
In node view, double-click the transmit ML-Series card to open the card view.
2-78
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.81 EOC
Step 3
Step 4 b.
•
Click the Provisioning > Card tabs.
c.
In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply .
If the alarm does not clear, use the CLI to ensure that the remaining settings are correctly configured on the ML-Series card:
• Encapsulation
CRC size
• Scrambling state
To open the interface, click the IOS tab and click Open IOS Command Line Interface (CLI) . Refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454
SDH, and Cisco ONS 15327 entries on all three of these topics to obtain the full configuration command sequences.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.81 EOC
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: TRUNK
The SONET DCC Termination Failure alarm occurs when the ONS 15454 loses its DCC. Although this alarm is primarily SONET, it can apply to DWDM. For example, the OSCM card can raise this alarm on its OC-3 section overhead.
The SDCC consists of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS 15454 uses the DCC on the SONET section layer to communicate network management information.
Warning On the ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-79
Chapter 2 Alarm Troubleshooting
2.7.81 EOC
Note If a circuit shows a partial state when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the EOC Alarm
Step 1 If the
“LOS (DS1)” alarm on page 2-152
is also reported, complete the “Clear the LOS (OCN) Alarm” procedure on page 2-159 .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
Step 6
If the
.
If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry SDCC traffic. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If the physical connections are correct and configured to carry DCC traffic, ensure that both ends of the fiber span have in-service (IS-NR) ports. Verify that the ACT/SBY LED on each card is green.
When the LEDs on the cards are correctly illuminated, complete the
“Verify or Create Node Section
DCC Terminations” procedure on page 2-268
to verify that the DCC is provisioned for the ports at both ends of the fiber span.
Repeat
If DCC is provisioned for the ends of the span, verify that the port is active and in service: a.
Confirm that the card shows a green LED in CTC or on the physical card.
b.
c.
d.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine whether the port is in service, double-click the card in CTC to open the card view.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS .
e.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and click IS in the drop-down list. Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
Step 7 For all nodes, if the card is in service, use an optical test set to determine whether signal failures are present on fiber terminations. For specific procedures to use the test set equipment, consult the manufacturer.
2-80
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.82 EOC-L
Caution Using an optical test set can disrupt service on the OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for commonly used switching procedures.
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. See the
“1.12.3 OC-N Card Transmit and Receive Levels” section on page 1-140
for non-DWDM card levels and refer to the Cisco ONS 15454 DWDM Reference Manual for
DWDM card levels.
If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If fiber connectors are properly fastened and terminated, complete the “Reset an Active TCC2/TCC2P
Card and Activate the Standby Card” procedure on page 2-263
.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Resetting the active TCC2/TCC2P switches control to the standby TCC2/TCC2P. If the alarm clears when the ONS 15454 node switches to the standby TCC2/TCC2P, the user can assume that the previously active card is the cause of the alarm.
If the TCC2/TCC2P reset does not clear the alarm, delete the problematic SDCC termination: a.
From the View menu in card view, choose Go to Previous View if you have not already done so.
b.
c.
d.
e.
Click the
Highlight the problematic DCC termination.
Click
Provisioning > Comm Channels > SDCC
Delete .
Click Yes in the Confirmation Dialog box.
tabs.
Recreate the SDCC termination. Refer to the “Turn Up Network” chapter in the Cisco ONS 15454
Procedure Guide for procedures.
Verify that both ends of the DCC have been recreated at the optical ports.
If the alarm has not cleared, call Cisco TAC 1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
“Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the
“Physically Replace a Traffic Card” procedure on page 2-266
.
2.7.82 EOC-L
Default Severity: Minor (MN), Non-Service-Affecting (NSA) for OCN
SONET Logical Object: OCN
DWDM Logical Object: TRUNK
The Line DCC (LDCC) Termination Failure alarm occurs when the ONS 15454 loses its line data communications channel (LDCC) termination. In DWDM configurations, for example, the OSCM card can raise this alarm on its OC-3 line overhead.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-81
Chapter 2 Alarm Troubleshooting
2.7.83 EQPT
The LDCC consists of nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS 15454 uses the LDCCs on the SONET line layer to communicate network management information.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note
If a circuit shows a partial status when the “EOC” alarm, page 2-79
, or EOC-L is raised, it occurs when the logical circuit is in place. The circuit is able to carry traffic when the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the EOC-L Alarm
Step 1
Step 2
Complete the “Clear the EOC Alarm” procedure on page 2-80
.
If the alarm has not cleared, call Cisco TAC 1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
the
“Physically Replace a Traffic Card” procedure on page 2-266 .
2.7.83 EQPT
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: AICI-AEP, AICI-AIE, EQPT
DWDM Logical Object: PPM
An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card. If the
This alarm is also invoked if a diagnostic circuit detects a card application-specific integrated circuit
(ASIC) failure. In this case, if the card is part of a protection group, an APS switch occurs. If the card is the protect card, switching is inhibited and a
“PROTNA” alarm on page 2-192 is raised. The standby path
generates a path-type alarm.
2-82
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.84 EQPT-DIAG
Clear the EQPT Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If traffic is active on the alarmed port, you could need to switch traffic away from it. See the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254
for commonly used traffic-switching procedures.
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for the reporting card. For LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the
LED status. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the CTC reset does not clear the alarm, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the reporting card.
If the physical reseat of the card fails to clear the alarm, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.84 EQPT-DIAG
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
An Equipment-Diagnostic Failure alarm indicates that a software or hardware failure has occurred on the reporting card. This alarm can be raised against a traffic card or a cross-connect card.
Clear the EQPT-DIAG Alarm
Step 1
Step 2
Step 3
Step 4
If traffic is active on the alarmed card, you could need to switch traffic away from it. Refer to the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254 for procedures.
Complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266 for the alarmed card
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
if it is raised against a traffic card, or complete the
“Physically Replace an In-Service Cross-Connect
Card” procedure on page 2-266 if the alarm is raised against the cross-connect card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.85 EQPT-MISS
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: FAN
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-83
Chapter 2 Alarm Troubleshooting
2.7.86 ERFI-P-CONN
The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or not fully inserted. It could also indicate that the ribbon cable connecting the AIP to the system board is bad.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Clear the EQPT-MISS Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
If the alarm is reported against the fan, verify that the fan-tray assembly is present.
If the fan-tray assembly is present, complete the
“Replace the Fan-Tray Assembly” procedure on page 2-273
.
If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the “Install the Fan-Tray
Assembly,” procedure in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, replace the ribbon cable from the AIP to the system board with a known-good ribbon cable.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.86 ERFI-P-CONN
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
The Three-Bit (Enhanced) Remote Failure Indication (ERFI) Path Connectivity condition is triggered on
DS-1, DS-3, or VT circuits when the
“UNEQ-P” alarm on page 2-245 and the
are raised on the transmission signal.
Clear the ERFI-P-CONN Condition
Step 1
Step 2
Complete the “Clear the UNEQ-P Alarm” procedure on page 2-245 . This should clear the ERFI
condition.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.87 ERFI-P-PAYLD
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
2-84
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.88 ERFI-P-SRVR
The Three-Bit ERFI Path Payload condition is triggered on DS-1, DS-3, or VT circuits when the
“PLM-P” alarm on page 2-189 is raised on the transmission signal.
Clear the ERFI-P-PAYLD Condition
Step 1
Step 2
Complete the
“Clear the PLM-P Alarm” procedure on page 2-189
. This should clear the ERFI condition.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.88 ERFI-P-SRVR
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
The Three-Bit ERFI Path Server condition is triggered on DS-1, DS-3, or VT circuits when the
“AIS-P” condition on page 2-36
or the
is raised on the transmission signal.
Clear the ERFI-P-SRVR Condition
Step 1
Step 2
Complete the
“Clear the LOP-P Alarm” procedure on page 2-149
. This should clear the ERFI condition.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.89 ERROR-CONFIG
The Error in Startup Configuration alarm applies to the ML-Series Ethernet cards. These cards process startup configuration files line by line. If one or more lines cannot be executed, the error causes the
ERROR-CONFIG alarm. ERROR-CONFIG is not caused by hardware failure.
The typical reasons for an errored startup file are:
•
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
•
•
The user stored the configuration for one type of ML-Series card in the database and then installed another type in its slot.
The configuration file contained a syntax error on one of the lines.
A user stored the configuration for the ML-Series card and then changed the card mode from
RPR-IEEE mode to another mode, or vice versa.
Note For information about provisioning the ML-Series Ethernet cards from the Cisco IOS interface, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454
SDH, and Cisco ONS 15327.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-85
Chapter 2 Alarm Troubleshooting
2.7.90 ETH-LINKLOSS
Clear the ERROR-CONFIG Alarm
Step 1
Step 2
Step 3
Step 4
If you have a different type of ML-Series card specified in the startup configuration file than what you have installed, create the correct startup configuration.
Follow the card provisioning instructions in the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Upload the configuration file to the TCC2/TCC2P: a.
b.
In node view, right-click the ML-Series card graphic.
Choose IOS Startup Config from the shortcut menu.
c.
Click Local > TCC and navigate to the file location in the Open dialog box.
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 .
If the alarm does not clear or if your configuration file was correct according to the installed card, start a Cisco IOS CLI for the card: a.
Right click the ML-Series card graphic in node view.
b.
Choose Open IOS Connection from the shortcut menu.
Note Open IOS Connection is not available unless the ML-Series card is physically installed in the shelf.
Step 5
Step 6
Follow the card provisioning instructions in the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 to correct the errored configuration file line.
Execute the CLI command: router(config)# copy run start
The command copies the new card configuration into the database and clears the alarm.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.90 ETH-LINKLOSS
The Rear Panel Ethernet Link Removed condition, if enabled in the network defaults, is raised under the following conditions:
• The node.network.general.AlarmMissingBackplaneLAN field in NE default is enabled.
•
•
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The node is configured as a gateway network element (GNE).
The backplane LAN cable is removed.
2-86
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.91 E-W-MISMATCH
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the ETH-LINKLOSS Condition
Step 1
Step 2
To clear this condition, reconnect the backplane LAN cable. Refer to the “Install the Shelf and Backplane
Cable” chapter in the Cisco ONS 15454 Procedure Guide for procedures to install this cable.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.91 E-W-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
A Procedural Error Misconnect East/West Direction alarm occurs during BLSR setup, or when nodes in a ring have slots misconnected. An east slot can be misconnected to another east slot, or a west slot can be misconnected to another west slot. In most cases, the user did not connect the fibers correctly or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but could change the traditional east-west node connection pattern of the ring.
Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its east-west slots configured correctly. If the alarm appears during the initial setup, the alarm clears itself shortly after the ring setup is complete.
Note The lower-numbered slot at a node is traditionally labeled the west slot and the higher numbered slot is labeled the east slot. For example, Slot 6 is west and Slot 12 is east.
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.
Clear the E-W-MISMATCH Alarm with a Physical Switch
Step 1
Step 2
Diagram the ring setup, including nodes and spans, on a piece of paper or white board.
In node view, click View > Go to Network View .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-87
Chapter 2 Alarm Troubleshooting
2.7.91 E-W-MISMATCH
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Click the circuit and click Edit . The network map detailed view window appears. This window contains the node name, slot, and port for each end of each span.
Label each of the nodes on the diagram with the same name that appears on the network map.
Label the span ends on the diagram with the same information. For example, with
Node 1/Slot 12/Port 1—Node 2/Slot 6/Port 1 (2F BLSR OC48, ring name=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/Port 1.
Repeat Steps
for each span on your diagram.
Label the highest slot at each node east and the lowest slot at each node west.
Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span. Refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure
Guide for more information about cabling the system.
If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
Clear the E-W-MISMATCH Alarm in CTC
Step 1
Step 2
Step 3
Step 4
Step 5
Log into the misconnected node. A misconnected node has both ring fibers connecting it to its neighbor nodes misconnected.
Click the Maintenance > BLSR tabs.
From the row of information for the fiber span, complete the
“Identify a BLSR Ring Name or Node ID
Number” procedure on page 2-253 to identify the node ID, ring name, and the slot and port in the
East Line column and West Line column. Record the above information.
Click View > Go to Network View .
Delete and recreate the BLSR: a.
Click the Provisioning > BLSR tabs.
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-88 November 2009
Chapter 2 Alarm Troubleshooting
2.7.92 EXCCOL
Step 6
Step 7
Step 8
Step 9
Step 10 b.
c.
Click the row from
to select it and click Delete .
Click Create .
Fill in the ring name and node ID from the information collected in
d.
e.
Click Finish .
Display node view and click the Maintenance > BLSR tabs.
Change the West Line field to the slot you recorded for the East Line in
Change the East Line field to the slot you recorded for the West Line in
Click OK .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.92 EXCCOL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Excess Collisions on the LAN alarm indicates that too many collisions are occurring between data packets on the network management LAN, and communications between the ONS 15454 and CTC could be affected. The network management LAN is the data network connecting the workstation running the
CTC software to the TCC2/TCC2P. The problem causing the alarm is external to the ONS 15454.
Troubleshoot the network management LAN connected to the TCC2/TCC2P for excess collisions. You might need to contact the system administrator of the network management LAN to accomplish the following steps.
Clear the EXCCOL Alarm
Step 1
Step 2
Step 3
Verify that the network device port connected to the TCC2/TCC2P has a flow rate set to 10 Mb, half-duplex.
If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the
TCC2/TCC2P and the network management LAN.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.93 EXERCISE-RING-FAIL
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Exercise Ring command issues ring protection switching of the requested channel without completing the actual bridge and switch. The EXERCISE-RING-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-89
Chapter 2 Alarm Troubleshooting
2.7.94 EXERCISE-SPAN-FAIL
Note If the exercise command gets rejected due to the existence of a higher-priority condition in the ring,
EXERCISE-RING-FAIL is Not Reported (NR).
Clear the EXERCISE-RING-FAIL Condition
Step 1
Step 2
Step 3
Look for and clear, if present, the
“LOF (OCN)” alarm on page 2-145 , the
“LOS (OCN)” alarm on page 2-158
, or a BLSR alarm.
Complete the “Initiate an Exercise Ring Switch on a BLSR” procedure on page 2-261 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.94 EXERCISE-SPAN-FAIL
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Exercise Span command issues span switching of the requested channel without completing the actual bridge and switch. The EXERCISE-SPAN-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.
Note If the exercise command gets rejected due to the existence of a higher-priority condition in the span or ring, EXERCISE-SPAN-FAIL is Not Reported (NR).
Clear the EXERCISE-SPAN-FAIL Condition
Step 1
Step 2
Step 3
Look for and clear, if present, the
“LOF (OCN)” alarm on page 2-145 , the
“LOS (OCN)” alarm on page 2-158
, or a BLSR alarm.
Complete the “Initiate an Exercise Ring Switch on a BLSR” procedure on page 2-261 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.95 EXT
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: ENVALRM
A Failure Detected External to the NE alarm occurs because an environmental alarm is present. For example, a door could be open or flooding could have occurred.
2-90
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.96 EXTRA-TRAF-PREEMPT
Clear the EXT Alarm
Step 1
Step 2
Step 3
Step 4
In node view double-click the AIC-I card to open the card view.
Double-click the Maintenance > External Alarms tab.
Follow your standard operating procedure to remedy environmental conditions that cause alarms. The alarm clears when the situation is remedied.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.96 EXTRA-TRAF-PREEMPT
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
An Extra Traffic Preempted alarm occurs on OC-N cards in two-fiber and four-fiber BLSRs when low-priority traffic directed to the protect system has been preempted by a working system protection switch.
Clear the EXTRA-TRAF-PREEMPT Alarm
Step 1
Step 2
Step 3
Step 4
Verify that the protection switch has occurred by checking the Conditions tab.
If a ring switch has occurred, clear the ring switch on the working system by following the appropriate
the Cisco ONS 15454 Procedure Guide .
If the alarm occurred on a four-fiber BLSR and the span switch occurred on this OC-N, clear the span switch on the working system.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.97 FAILTOSW
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
The Failure to Switch to Protection Facility condition occurs when a working or protect electrical or optical facility switches to its companion port by using a MANUAL command. For example, if you attempt to manually switch traffic from an unused protect port to an in-service working port, the switch will fail (because traffic is already present on the working port) and you will see the FAILTOSW condition.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-91
Chapter 2 Alarm Troubleshooting
2.7.98 FAILTOSW-PATH
Clear the FAILTOSW Condition
Step 1 Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the card and clears the FAILTOSW.
Note A higher-priority alarm is an alarm raised on the working DS-N card using the 1:N card protection group. The working DS-N card is reporting an alarm but not reporting a FAILTOSW condition.
Step 2
Step 3
If the condition does not clear, replace the working electrical or optical card that is reporting the higher-priority alarm by following the
“Physically Replace a Traffic Card” procedure on page 2-266
.
This card is the working electrical or optical card using the protect card and not reporting FAILTOSW.
Replacing the working electrical or optical card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.98 FAILTOSW-PATH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, VT-MON
The Fail to Switch to Protection Path condition occurs when the working circuit does not switch to the protection circuit on a path protection. Common causes of the FAILTOSW-PATH alarm include a missing or defective protect port, a lockout set on one of the path protection nodes, or path-level alarms that would cause a path protection switch to fail including the
“AIS-P” condition on page 2-36 , the
“LOP-P” alarm, page 2-149 , the
“SD-P” condition on page 2-214 , the
“SF-P” condition on page 2-217 ,
and the
The “LOF (OCN)” alarm, page 2-145
, the
“LOS (OCN)” alarm on page 2-158 , the
“SD-L” condition on page 2-213
, or the
“SF-L” condition on page 2-217 can also occur on the failed path.
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
Step 1 Look up and clear the higher-priority alarm. Clearing this alarm frees the standby card and clears the
FAILTOSW-PATH condition. If the
“AIS-P” condition on page 2-36 , the
, the
, the “SF-P” condition on page 2-217 , the
“SD-P” condition on page 2-214
, the
“LOF (OCN)” alarm, page 2-145 , the
“LOS (OCN)” alarm on page 2-158 , the
“SD-L” condition on page 2-213 , or the
“SF-L” condition on page 2-217
are also occurring on the reporting port, complete the applicable alarm clearing procedure.
Note A higher-priority alarm is an alarm raised on the working electrical card using the 1:N card protection group. The working DS-N card is reporting an alarm but not reporting a FAILTOSW condition.
2-92
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.99 FAILTOSWR
Step 2
Step 3
If the condition does not clear, replace the active OC-N card that is reporting the higher-priority alarm.
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266 . 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 condition.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.99 FAILTOSWR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems.
FAILTOSWR clears in any of the following situations:
• A physical card pull of the active TCC2/TCC2P (done under Cisco TAC supervision).
•
•
•
A node power cycle.
A higher-priority event such as an external switch command.
•
The next ring switch succeeds.
The cause of the APS switch (such as the
“SD (DS1, DS3)” condition on page 2-210
(DS1, DS3)” condition on page 2-215 ) clears.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the FAILTOSWR Condition in a BLSR Configuration
Step 1 Perform the Exercise Ring command on the reporting card: a.
b.
c.
Click the
Click the row of the affected ring under the West Switch column.
Select
Maintenance > BLSR
Exercise Ring tabs.
in the drop-down list.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-93
Chapter 2 Alarm Troubleshooting
2.7.99 FAILTOSWR
Step 2
Step 3
Step 4
Step 5
Step 6
If the condition does not clear, from the view menu, choose Go to Network View .
Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.
If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node.
Click the Maintenance > BLSR tabs.
Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards and ports are active and in service: a.
b.
c.
Verify the LED status: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Double-click the card in CTC to open the card view.
d.
e.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS . Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
Step 7
Step 8
If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards. To verify fiber continuity, follow site practices.
If fiber continuity to the ports is good, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
Caution Using an optical test set disrupts service on the OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for commonly used switching procedures.
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within
lists these specifications.
Repeat Steps
for any other ports on the card.
If the optical power level for all OC-N cards is within specifications, complete the
“Physically Replace a Traffic Card” procedure on page 2-266 for the protect standby OC-N card.
If the condition does not clear after you replace the BLSR cards on the node one by one, repeat
through
12 for each of the nodes in the ring.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-94
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.100 FAILTOSWS
2.7.100 FAILTOSWS
The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber
BLSR, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS condition does not appear. If the ring switch does not occur, the FAILTOSWS condition appears. FAILTOSWS clears when one of the following situations occurs:
• A physical card pull of the active TCC2/TCC2P done under Cisco TAC supervision.
•
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
•
•
•
A node power cycle.
A higher-priority event such as an external switch command occurs.
The next span switch succeeds.
The cause of the APS switch (such as the
“SD (DS1, DS3)” condition on page 2-210
(DS1, DS3)” condition on page 2-215 ) clears.
Clear the FAILTOSWS Condition
Step 2
Step 3
Step 4
Step 5
Step 6
Step 1 Perform the Exercise Span command on the reporting card: a.
b.
c.
d.
Click the Maintenance > BLSR tabs.
Determine whether the card you would like to exercise is the west card or the east card.
Click the row of the affected span under the East Switch or West Switch column.
Select Exercise Span in the drop-down list.
If the condition does not clear, from the view menu, choose Go to Network View .
Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.
If clearing other alarms does not clear the FAILTOSWS condition, log into the near-end node.
Click the Maintenance > BLSR tabs.
Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards are active and in service: a.
Verify the LED status: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
b.
c.
To determine whether the OC-N port is in service, double-click the card in CTC to open the card view.
Click the Provisioning > Line tabs.
d.
e.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS . Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-95
Chapter 2 Alarm Troubleshooting
2.7.101 FAN
Step 7
Step 8
If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards. To verify fiber continuity, follow site practices.
If fiber continuity to the ports is good, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
Caution Using an optical test set disrupts service on the OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for commonly used switching procedures.
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within
lists these specifications.
Repeat Steps
for any other ports on the card.
If the optical power level for all OC-N cards is within specifications, complete the
“Physically Replace a Traffic Card” procedure on page 2-266 for the protect standby OC-N card.
If the condition does not clear after you replace the BLSR cards on the node one by one, follow
through
12 for each of the nodes in the ring.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.101 FAN
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: FAN
The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15454 can rise above its normal operating range.
The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the shelf. However, even with five working fans, the fan-tray assembly could need replacement because a sixth working fan is required for extra protection against overheating.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Clear the FAN Alarm
Step 1
Step 2
Determine whether the air filter needs replacement. Complete the
“Inspect, Clean, and Replace the
Reusable Air Filter” procedure on page 2-271
.
If the filter is clean, complete the
“Remove and Reinsert a Fan-Tray Assembly” procedure on page 2-272
.
2-96
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.102 FC-NO-CREDITS
Step 3
Step 4
If the replacement fan-tray assembly does not operate correctly, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a
Service-Affecting (SA) problem 1 800 553-2447.
2.7.102 FC-NO-CREDITS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: FCMR
DWDM Logical Objects: FC, TRUNK
The Fibre Channel Distance Extension Credit Starvation alarm occurs on storage access networking
(SAN) Fibre Channel/Fiber Connectivity (FICON) FC_MR-4 cards when the congestion prevents the generic framing procedure (GFP) transmitter from sending frames to the FC_MR-4 card port. For example, the alarm can be raised when an operator configures a card to autodetect framing credits but the card is not connected to an interoperable FC-SW-standards-based Fibre Channel/FICON port.
FC-NO-CREDITS is raised only if transmission is completely prevented. (If traffic is slowed but still passing, this alarm is not raised.) The alarm is raised in conjunction with the GFP-NO-BUFFERS alarm.
For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a
GFP-NO-BUFFERS alarm could be raised at the upstream remote FC_MR-4 data port.
Clear the FC-NO-CREDITS Alarm
Step 1
Step 2 h.
i.
j.
b.
c.
d.
If the port is connected to a Fibre Channel/FICON switch, make sure it is configured for interoperation mode using the manufacturer’s instructions.
If the port is not connected to a switch, turn off Autodetect Credits: a.
Double-click the FC_MR-4 card.
e.
Click Provisioning > Port > General.
Under Admin State, click the cell and choose OOS,MT .
Click Apply .
Click the Provisioning > Port > Distance Extension tabs.
f.
g.
Uncheck the Autodetect Credits column check box.
Click Apply .
Click Provisioning > Port > General.
Under Admin State, click the cell and choose IS .
Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
Step 3 Program the Credits Available value based on the buffers available on the connected equipment:
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-97
Chapter 2 Alarm Troubleshooting
2.7.103 FDI
Step 4
Note The NumCredits must be provisioned to a value smaller than or equal to the receive buffers or credits available on the connected equipment.
a.
b.
c.
d.
Double-click the FC_MR-4 card.
Click the
Click
Provisioning > Port > Distance Extension
Enter a new value in the Credits Available column.
Apply .
tabs.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.103 FDI
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.104 FE-AIS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far-End AIS condition occurs when an AIS has occurred at the far-end node. FE-AIS usually occurs
in conjunction with a downstream LOS alarm (see the “LOS (OCN)” alarm on page 2-158
).
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the FE-AIS Condition
Step 1
Step 2
Complete the “Clear the AIS Condition” procedure on page 2-35
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.105 FEC-MISM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-98
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.106 FE-DS1-MULTLOS
2.7.106 FE-DS1-MULTLOS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far-End Multiple DS-1 LOS Detected condition occurs when multiple DS-1 signals are lost on a far-end DS-1 card.
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 alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-DS1-MULTLOS Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an ONS 15454 FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.107 FE-DS1-NSA
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End DS-1 Equipment Failure Non-Service-Affecting (NSA) condition occurs when a far-end
DS-1 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.
Clear the FE-DS1-NSA Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an alarm from a card in an ONS 15454 Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-99
Chapter 2 Alarm Troubleshooting
2.7.108 FE-DS1-SA
2.7.108 FE-DS1-SA
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End DS-1 Equipment Failure Service Affecting condition occurs when there is a far-end equipment failure on a DS-1 card that affects service because traffic is unable to switch to the protect port.
Clear the FE-DS1-SA Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in
Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.109 FE-DS1-SNGLLOS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far-End Single DS-1 LOS condition occurs when a single DS-1 signal is lost on far-end DS-1 equipment (within a DS3). Signal loss also causes the
“LOS (OCN)” alarm on page 2-158 .
Clear the FE-DS1-SNGLLOS Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.110 FE-DS3-NSA
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
2-100
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.111 FE-DS3-SA
SONET Logical Object: DS3
The Far End DS-3 Equipment Failure Non-Service-Affecting (NSA) condition occurs when a far-end
ONS 15454 DS-3 equipment failure occurs in C-bit framing mode, but does not affect service because the port is protected and traffic is able to switch to the protect port.
Clear the FE-DS3-NSA Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in
Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.111 FE-DS3-SA
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End DS-3 Equipment Failure Service Affecting condition occurs when there is a far-end equipment failure on an ONS 15454 DS-3 card in C-bit framing mode that affects service because traffic is unable to switch to the protect port.
Clear the FE-DS3-SA Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in
Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.112 FE-EQPT-NSA
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-101
Chapter 2 Alarm Troubleshooting
2.7.113 FE-FRCDWKSWBK-SPAN
The Far End Common Equipment Failure condition occurs when a Non-Service-Affecting (NSA) equipment failure is detected on far-end DS-3 equipment.
Clear the FE-EQPT-NSA Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.113 FE-FRCDWKSWBK-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Forced Switch Back to Working—Span condition is raised on a far-end 1+1 working port when it is Force switched to the working port.
Note WKSWBK-type conditions apply only to revertive circuits.
Clear the FE-FRCDWKSWBK-SPAN Condition
Step 1
Step 2
Complete the
“Clear a 1+1 Force or Manual Switch Command” procedure on page 2-256
for the far-end port.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.114 FE-FRCDWKSWPR-RING
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a BLSR is forced from working to protect using the Force Ring command. This condition is only visible on the network view Conditions tab.
2-102
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.115 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-RING Condition
Step 1
Step 2
Step 3
Step 4
Step 5
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm.
If the FE-FRCDWKSWPR-RING condition does not clear, complete the
Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.115 FE-FRCDWKSWPR-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber BLSR is forced from working to protect using the Force Span command.
This condition is only visible on the network view Conditions tab. The port where the Force Switch occurred is indicated by an “F” on the network view detailed circuit map. This condition is accompanied by WKSWPR.
Clear the FE-FRCDWKSWPR-SPAN Condition
Step 1
Step 2
Step 3
Step 4
Step 5
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm.
If the FE-FRCDWKSWPR-SPAN condition does not clear, complete the
Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.116 FE-IDLE
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal in C-bit framing mode.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-103
Chapter 2 Alarm Troubleshooting
2.7.117 FE-LOCKOUTOFPR-SPAN
Clear the FE-IDLE Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot the FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm by clearing the protection switch. See the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for commonly used traffic-switching procedures.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.117 FE-LOCKOUTOFPR-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far-End Lock Out of Protection Span condition occurs when a BSLR span is locked out of the protection system from a far-end node using the Lockout Protect Span command. This condition is only seen on the network view Conditions tab and is accompanied by LKOUTPR-S. The port where the lockout originated is marked by an “L” on the network view detailed circuit map.
Clear the FE-LOCKOUTOFPR-SPAN Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Ensure there is no lockout set. Complete the
“Clear a BLSR External Switching Command” procedure on page 2-262
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.118 FE-LOF
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End LOF condition occurs when a far-end node reports the
“LOF (DS3)” alarm on page 2-143
in C-bit framing mode.
2-104
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.119 FE-LOS
Clear the FE-LOF Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Complete the
“Clear the LOF (DS1) Alarm” procedure on page 2-142 . It also applies to FE-LOF.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.119 FE-LOS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The Far End LOS condition occurs in C-bit framing mode when a far-end node reports the
“LOS (DS3)” alarm on page 2-153
.
Clear the FE-LOS Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot the FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Complete the
“Clear the LOS (DS1) Alarm” procedure on page 2-152 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.120 FE-MANWKSWBK-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Manual Switch Back to Working—Span condition occurs when a far-end span with a
Manual switch reverts to working.
Note WKSWBK-type conditions such as FE-MANWKSWBK-SPAN apply only to nonrevertive circuits.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-105
Chapter 2 Alarm Troubleshooting
2.7.121 FE-MANWKSWPR-RING
Clear the FE-MANWKSWBK-SPAN Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot the FE condition, determine which node and card link directly to the card reporting the
FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.121 FE-MANWKSWPR-RING
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Ring Manual Switch of Working Facility to Protect condition occurs when a BLSR working ring is switched from working to protect at a far-end node using the Manual Ring command.
Clear the FE-MANWKSWPR-RING Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.122 FE-MANWKSWPR-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far-End Span Manual Switch Working Facility to Protect condition occurs when a four-fiber BLSR span is switched from working to protect at the far-end node using the Manual Span command. This condition is only visible on the network view Conditions tab and is accompanied by WKSWPR. The port where the Manual Switch occurred is indicated by an “M” on the network view detailed circuit map.
2-106
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.123 FEPRLF
Clear the FE-MANWKSWPR-SPAN Condition
Step 1
Step 2
Step 3
Step 4
To troubleshoot an FE condition, determine which node and card link directly to the card reporting the
FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Complete the
“Clear a BLSR External Switching Command” alarm on page 2-262
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.123 FEPRLF
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Far End Protection Line Failure alarm occurs when an APS channel
“SF-L” condition on page 2-217
occurs on the protect card coming into the node.
Note The FEPRLF alarm occurs when bidirectional protection is used on optical cards in a 1+1 protection group configuration or four-fiber BLSR configuration.
Clear the FEPRLF Alarm on a Four-Fiber BLSR
Step 1
Step 2
Step 3
Step 4
To troubleshoot the FE alarm, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Log into the node that links directly to the card reporting the FE condition.
Clear the main alarm. Refer to the appropriate alarm section in this chapter in this chapter for procedures.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.124 FIBERTEMP-DEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.125 FORCED-REQ
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, ML1000, ML100T, MLFX, STSMON, VT-MON
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-107
Chapter 2 Alarm Troubleshooting
2.7.126 FORCED-REQ-RING
The Force Switch Request on Facility or Port condition occurs when you enter the Force command on a port to force traffic from a working port to a protect port or protection span (or from a protect port to a working port or span). You do not need to clear the condition if you want the Force switch to remain.
FORCED-REQ is raised for an IEEE 802.17b-based RPR span if the force was requested in the
Cisco IOS CLI using the “rpr-ieee protection request force-switch {east | west}” command. It clears from the IEEE 802.17b-based RPR span when you remove the switch in the CLI. For the
IEEE 802.17b-based RPR interface, FORCED-REQ is suppressed by
. It also suppresses the following alarms:
•
•
•
•
Clear the FORCED-REQ Condition
Step 1
Step 2
Step 3
If the condition is raised on a SONET entity, complete the
“Clear a 1+1 Force or Manual Switch
Command” procedure on page 2-256
.
If the condition is raised on an IEEE-802.17b-based RPR span, enter the following command in the CLI in RPR-IEEE interface configuration mode: router(config-if)#no rpr-ieee protection request force-switch {east | west}
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.126 FORCED-REQ-RING
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Force Switch Request Ring condition applies to optical trunk cards when the Force Ring command is applied to BLSRs to move traffic from working to protect. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by
WKSWPR, page 250 . The port where
the FORCE RING command originated is marked with an “F” on the network view detailed circuit map.
Clear the FORCED-REQ-RING Condition
Step 1
Step 2
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-108
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.127 FORCED-REQ-SPAN
2.7.127 FORCED-REQ-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
The Force Switch Request Span condition can apply to optical trunk cards in two-fiber or four-fiber
BLSRs when the Force Span command is applied to a BLSR SPAN to force traffic from working to protect or from protect to working. This condition appears on the network view Alarms, Conditions, and
History tabs. The port where the FORCE SPAN command was applied is marked with an “F” on the network view detailed circuit map.
FORCED-REQ can be raised in 1+1 facility protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by “FORCED
TO WORKING”), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.
Clear the FORCED-REQ-SPAN Condition
Step 1
Step 2
Complete the
“Clear a BLSR External Switching Command” procedure on page 2-262
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.128 FRCDSWTOINT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
The Force Switch to Internal Timing condition occurs when the user issues a FORCE command to switch to an internal timing source.
Note FRCDSWTOINT is an informational condition and does not require troubleshooting.
2.7.129 FRCDSWTOPRI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Force Switch to Primary Timing Source condition occurs when the user issues a FORCE command to switch to the primary timing source.
Note FRCDSWTOPRI is an informational condition and does not require troubleshooting.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-109
Chapter 2 Alarm Troubleshooting
2.7.130 FRCDSWTOSEC
2.7.130 FRCDSWTOSEC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Force Switch to Second Timing Source condition occurs when the user issues a FORCE command to switch to the second timing source.
Note FRCDSWTOSEC is an informational condition and does not require troubleshooting.
2.7.131 FRCDSWTOTHIRD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Force Switch to Third Timing Source condition occurs when the user issues a Force command to switch to a third timing source.
Note FRCDSWTOTHIRD is an informational condition and does not require troubleshooting.
2.7.132 FRNGSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
The Free Running Synchronization Mode condition occurs when the reporting ONS 15454 is in free-run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the node has lost its designated building integrated timing supply (BITS) timing source. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15454 node relying on an internal clock.
Note If the ONS 15454 is configured to operate from its internal clock, disregard the FRNGSYNC condition.
Clear the FRNGSYNC Condition
Step 1
Step 2
Step 3
If the ONS 15454 is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the “Timing” chapter in the Cisco ONS 15454 Reference Manual for more information.
If the BITS source is valid, clear alarms related to the failures of the primary and secondary reference sources, such as the
and the
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-110
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.133 FSTSYNC
2.7.133 FSTSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
A Fast Start Synchronization Mode condition occurs when the node is choosing a new timing reference.
The previous timing reference has failed.
The FSTSYNC alarm disappears after approximately 30 seconds. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call
Cisco TAC 1 800 553-2447.
Note FSTSYNC is an informational condition. It does not require troubleshooting.
2.7.134 FULLPASSTHR-BI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are active and carrying traffic and there is a change in the receive K byte from No Request.
Clear the FULLPASSTHR-BI Condition
Step 1
Step 2
Complete the
“Clear a BLSR External Switching Command” procedure on page 2-262
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.135 GAIN-HDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.136 GAIN-HFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.137 GAIN-LDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-111
Chapter 2 Alarm Troubleshooting
2.7.138 GAIN-LFAIL
2.7.138 GAIN-LFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.139 GCC-EOC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.140 GE-OOSYNC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.141 GFP-CSF
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on
FC_MR-4, ML100T, ML1000, ML100X-8, MXP_MR_25G, and MXPP_MR_25G GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a CARLOSS,
LOS, or SYNCLOSS alarm caused by an event such as a pulled receive cable is affecting a remote data port's transmission capability. This alarm can be demoted when a facility loopback is placed on the
FC_MR-4 port.
Note For more information about provisioning MXP or TXP cards, refer to the Cisco ONS 15454 DWDM
Reference Manual . For more information about Ethernet cards, refer to the Ethernet Card Software
Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and
Cisco ONS 15327 .
Clear the GFP-CSF Alarm
Step 1
Step 2
Clear the Service-Affecting (SA) alarm at the remote data port.
If the GFP-CSF alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.142 GFP-DE-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
2-112
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.143 GFP-EX-MISMATCH
SONET Logical Objects: FCMR, GFP-FAC
The GFP Fibre Channel Distance Extension Mismatch alarm indicates that a port configured for
Distance Extension is connected to a port that is not operating in Cisco's proprietary Distance Extension mode. It is raised on Fibre Channel and FICON card GFP ports supporting distance extension. The alarm occurs when distance extension is enabled on one side of the transport but not on the other. To clear, distance extension must be enabled on both ports connected by a circuit.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the GFP-DE-MISMATCH Alarm
Step 1 Ensure that the distance extension protocol is configured correctly on both sides: a.
Double-click the card to open the card view.
b.
i.
j.
g.
h.
e.
f.
c.
d.
Click the Provisioning > Port > General
Under Admin State, click the cell and choose OOS,MT .
Click
Click the Provisioning > Port > Distance Extension tabs.
Check the check box in the
Click Apply .
Click the
Click
Apply
Apply .
.
Enable Distance Extension
Provisioning > Port > General
tabs.
tabs.
Under Admin State, click the cell and choose IS .
column.
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 2 If the GFP-DE-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.143 GFP-EX-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE1000, FCMR, GFP-FAC
The GFP Extension Header Mismatch alarm is raised on Fibre Channel/FICON cards when it receives frames with an extension header that is not null. The alarm occurs when a provisioning error causes all
GFP frames to be dropped for 2.5 seconds.
Ensure that both end ports are sending a null extension header for a GFP frame. The FC_MR-4 card always sends a null extension header, so if the equipment is connected to other vendors’ equipment, those need to be provisioned appropriately.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-113
Chapter 2 Alarm Troubleshooting
2.7.144 GFP-LFD
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the GFP-EX-MISMATCH Alarm
Step 1
Step 2
Ensure that the vendor equipment is provisioned to send a null extension header in order to interoperate with the FC_MR-4 card. (The FC_MR-4 card always sends a null extension header.)
If the GFP-EX-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.144 GFP-LFD
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP Loss of Frame Delineation alarm applies to Fibre Channel, FICON GFP, and Ethernet ports.
This alarm occurs if there is a faulty SONET connection, if SONET path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. This loss causes traffic stoppage.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the GFP-LFD Alarm
Step 1
Step 2
Look for and clear any associated SONET path errors such as LOS or AIS-L originating at the transmit node.
If the GFP-LFD alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.145 GFP-NO-BUFFERS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: FCMR, GFP-FAC
The GFP Fibre Channel Distance Extension Buffer Starvation alarm is raised on Fibre Channel/FICON card ports supporting GFP and the distance extension protocol when the GFP transmitter cannot send
GFP frames due to lack of remote GFP receiver buffers. This occurs when the remote GFP-T receiver experiences congestion and is unable to send frames over the Fibre Channel/FICON link.
2-114
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.146 GFP-UP-MISMATCH
This alarm could be raised in conjunction with the
“FC-NO-CREDITS” alarm, page 2-97
. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm could be raised at the upstream remote FC_MR-4 data port.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the GFP-NO-BUFFERS Alarm
Step 1
Step 2
Complete the
“Clear the FC-NO-CREDITS Alarm” procedure on page 2-97
.
If the GFP-CSF alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a
Service-Affecting (SA) problem.
2.7.146 GFP-UP-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type. For example, the local port media type could be set to Fibre Channel—1 Gbps
ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL or FICON—2 Gbps ISL.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the GFP-UP-MISMATCH Alarm
Step 1
Step 2
Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps: a.
b.
c.
Double-click the card to open the card view.
Click the Provisioning > Port > Distance Extension tabs.
Check the check box in the Enable Distance Extension column.
d.
Click Apply .
Ensure that both ports are set for the correct media type. For each port, complete the following steps: a.
Double-click the card to open the card view (if you are not already in card view).
b.
Click the Provisioning > Port > General tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-115
Chapter 2 Alarm Troubleshooting
2.7.147 HELLO
Step 3 c.
Choose the correct media type ( Fibre Channel - 1Gbps ISL , Fibre Channel - 2 Gbps ISL ,
FICON - 1 Gbps ISL , or FICON - 2 Gbps ISL ) from the drop-down list.
d.
Click Apply .
If the GFP-UP-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a
Service-Affecting (SA) problem.
2.7.147 HELLO
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Open Shortest Path First (OSPF) Hello alarm is raised when the two end nodes cannot bring an
OSPF neighbor up to the full state. Typically, this problem is caused by an area ID mismatch, and/or an
OSPF HELLO packet loss over the DCC.
Clear the HELLO Alarm
Step 1
Step 2
Ensure that the area ID is correct on the missing neighbor: a.
In node view, click the Provisioning > Network > OSPF tabs.
b.
c.
Ensure that the IP address in the Area ID column matches the other nodes.
If the address does not match, click the incorrect cell and correct it.
d.
Click Apply .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.148 HIBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: PWR
The High Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage exceeds the high power threshold. This threshold, with a default value of –52 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for
120 seconds. (For information about changing this threshold, refer to the “Turn Up Node” chapter in the
Cisco ONS 15454 Procedure Guide .
Clear the HIBATVG Alarm
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying the battery leads.
2-116
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.149 HI-CCVOLT
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.149 HI-CCVOLT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: BITS
The 64K Composite Clock High NE Voltage alarm occurs when the 64K signal peak voltage exceeds
1.1 VDC.
Clear the HI-CCVOLT Condition
Step 1
Step 2
Step 3
Lower the source voltage to the clock.
If the condition does not clear, add more cable length or add a 5 dBm attenuator to the cable.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.150 HI-LASERBIAS
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM
The Equipment High Transmit Laser Bias Current alarm is raised against TXP_MR_10G,
TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, and OC192-XFP card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.
Laser bias typically starts at about 30 percent of the manufacturer maximum laser bias specification and increases as the laser ages. If the HI-LASERBIAS alarm threshold is set at 100 percent of the maximum, the laser usability has ended. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the HI-LASERBIAS Alarm
Step 1
Complete the “Clear the LASEREOL Alarm” procedure on page 2-132
, which can include replacing the card. Replacement is not urgent and can be scheduled during a maintenance window.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-117
Chapter 2 Alarm Troubleshooting
2.7.151 HI-LASERTEMP
Caution Removing an active card can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254
for commonly used traffic-switching procedures.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.151 HI-LASERTEMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Object: PPM
The Equipment High Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards.
HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength.
When the TXP or MXP card raises this alarm, the laser is automatically shut off. The
“LOS (OCN)” alarm on page 2-158
is raised at the far-end node and the
“DUP-IPADDR” alarm on page 2-75
is raised at the near end.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the HI-LASERTEMP Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, double-click the TXP or MXP card to open the card view.
Click the Performance > Optics PM > Current Values tabs.
Verify the card laser temperature levels. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 for the MXP or TXP card.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting MXP or TXP card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.152 HI-RXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
2-118
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.152 HI-RXPOWER
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC
The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, or
OC192-XFP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.
Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .
Note When you upgrade a node to Software Release 6.0 or later, this enables received optical power PMs for the OC3-8, OC192-SR, OC192-IR, OC192-ITU, OC-192-XFP, MRC-12, and MRC25G-4 cards. The newly enabled HI-RXPOWER and LO-RXPOWER alarms require that you initialize a site-accepted optical power (OPR0) nominal value after the upgrade. (To do this, refer to the procedure in the “Turn
Up a Node” chapter in the Cisco ONS 15454 Procedure Guide .) When you apply the value change, CTC uses the new OPR0 value to calculate PM percentage values. If you do not change the nominal value, the
HI-RXPOWER or LO-RXPOWER may be raised in response to the unmodified setting.
Clear the HI-RXPOWER Alarm
Step 1
Step 2
Find out whether gain (the amplification power) of any amplifiers has been changed. This change also causes channel power to need adjustment.
Find out whether channels have been dropped from the fiber. Increasing or decreasing channels can affect power. If channels have been dropped, the power levels of all channels have to be adjusted.
Note If the card is part of an amplified DWDM system, dropping channels on the fiber affects the transmission power of each channel more than it would in an unamplified system.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
At the transmit end of the errored circuit, decrease the transmit power level within safe limits.
If neither of these problems cause the HI-RXPOWER alarm, there is a slight possibility that another wavelength is drifting on top of the alarmed signal. In this case, the receiver gets signals from two transmitters at the same time and data alarms would be present. If wavelengths are drifting, the data is garbled and receive power increases by about +3 dBm.
If the alarm does not clear, add fiber attenuators to the receive ports. Start with low-resistance attenuators and use stronger ones as needed, depending on factors such as the transmission distance, according to standard practice.
If the alarm does not clear and no faults are present on the other port(s) of the transmit or receive card, use a known-good loopback cable to complete the
“1.6.1 Perform a Facility Loopback on a
Source-Node FC_MR Port” procedure on page 1-87 and test the loopback.
the card at the next available maintenance window.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-119
Chapter 2 Alarm Troubleshooting
2.7.153 HITEMP
2.7.153 HITEMP
Default Severity: Critical (CR), Service-Affecting (SA) for NE; Default Severity: Minor (MN),
Non-Service-Affecting (NSA) for EQPT
SONET Logical Objects: EQPT, NE
The High Temperature alarm occurs when the temperature of the ONS 15454 is above 122 degrees F
(50 degrees C).
Clear the HITEMP Alarm
Step 1 View the temperature displayed on the ONS 15454 LCD front panel (
Figure 2-2 Shelf LCD Panel
Slot Status Port
8/18/03
04.06-002L-10
24˚C
FAN FAIL CRIT MAJ MIN
Step 2
Step 3
Step 4
Step 5
Step 6
Verify that the environmental temperature of the room is not abnormally high.
If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454 shelf.
If airflow is not blocked, physically ensure that blank faceplates fill the ONS 15454 shelf empty slots.
Blank faceplates help airflow.
If faceplates fill the empty slots, determine whether the air filter needs replacement. Refer to the
“Inspect, Clean, and Replace the Reusable Air Filter” procedure on page 2-271 .
If the fan does not run or the alarm persists, complete the
“Replace the Fan-Tray Assembly” procedure on page 2-273
.
Note The fan should run immediately when correctly inserted.
Step 7 If the replacement fan-tray assembly does not operate correctly, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a
Service-Affecting (SA) problem 1 800 553-2447 if it applies to the NE, or a
Non-Service-Affecting (NSA) problem if it applies to equipment.
2.7.154 HI-TXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM
2-120
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.155 HLDOVRSYNC
The Equipment High Transmit Power alarm is an indicator on the TXP_MR_E, TXP_MR_10G,
TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the HI-TXPOWER Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, double-click the card view for the TXP_MR_10E, TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card.
Click the Provisioning > Optics Thresholds > Current Values tabs.
Decrease (change toward the negative direction) the OPT-HIGH column value by 0.5 dBm.
If the card transmit power setting cannot be lowered without disrupting the signal, complete the
“Physically Replace a Traffic Card” section on page 2-266
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.155 HLDOVRSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15454 relying on an internal clock.
Clear the HLDOVRSYNC Condition
Step 1 Clear additional alarms that relate to timing, such as:
•
•
•
•
•
•
•
2.7.187 LOF (BITS), page 2-141
2.7.204 LOS (BITS), page 2-151
2.7.252 MANSWTOINT, page 2-173
2.7.253 MANSWTOPRI, page 2-173
2.7.254 MANSWTOSEC, page 2-173
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-121
Chapter 2 Alarm Troubleshooting
2.7.156 I-HITEMP
Step 2
Step 3
•
•
2.7.255 MANSWTOTHIRD, page 2-174
•
•
•
•
•
•
Reestablish a primary and secondary timing source according to local site practice. If none exists, refer to the “Change Node Settings” chapter in the Cisco ONS 15454 Procedure Guide.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.156 I-HITEMP
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: NE
The Industrial High Temperature alarm occurs when the temperature of the ONS 15454 is above 149
degrees F (65 degrees C) or below –40 degrees F (–40 degrees C). This alarm is similar to the HITEMP
alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.
Clear the I-HITEMP Alarm
Step 1
Step 2
Complete the “Clear the HITEMP Alarm” procedure on page 2-120
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.
2.7.157 INCOMPATIBLE-SEND-PDIP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
The Incompatible Software alarm is raised when the PDIP provisioning on CTC differs from the provisioning on the host node.
Clear the INCOMPATIBLE-SEND-PDIP Alarm
Step 1 Reconfigure the send-PDI-P-alarm capability in CTC to align with the host node settings.
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-122 November 2009
Chapter 2 Alarm Troubleshooting
2.7.158 INCOMPATIBLE-SW
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).
2.7.158 INCOMPATIBLE-SW
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
The Incompatible Software alarm is raised when CTC cannot connect to the NE due to incompatible versions of software between CTC and the NE. The alarm is cleared by restarting CTC in order to redownload the CTC jar files from the NE.
Clear the INCOMPATIBLE-SW Alarm
Step 1
Step 2
Restart the CTC application.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).
2.7.159 IMPROPRMVL
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
DWDM Logical Object: PPM
The Improper Removal equipment alarm occurs when a card is physically removed from its slot before it is deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm; it only needs to be recognized by CTC. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node. It can also occur if the card is inserted into a slot but is not fully plugged into the backplane. For PPMs, the alarm occurs if you provision a PPM but no physical module is inserted on the port.
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. When you delete the card, CTC loses connection with the node view and go to network view.
Note CTC gives the user approximately 15 seconds to physically remove the card before CTC begins a card reboot.
Note It can take up to 30 minutes for software to be updated on a standby TCC2/TCC2P.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-123
Chapter 2 Alarm Troubleshooting
2.7.159 IMPROPRMVL
Clear the IMPROPRMVL Alarm
Step 1
Step 2
In node view, right-click the card reporting the IMPROPRMVL.
Choose Delete from the shortcut menu.
Note CTC does not allow you to delete the reporting card if the card is in service, does have circuits mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.
Step 3 If any ports on the card are in service, place them out of service (OOS,MT):
Caution Before placing a port out of service (OOS,MT or OOS,DSBLD), ensure that no live traffic is present.
Step 4 a.
b.
In node view, double-click the reporting card to open the card view.
Click the Provisioning > Line tab.
Click the Admin State column of any in-service (IS) ports.
c.
d.
Choose OOS,MT to take the ports out of service.
If a circuit has been mapped to the card, complete the
“Delete a Circuit” procedure on page 2-268 .
Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.
Step 5
Step 6
Step 7
Step 8
If the card is paired in a protection scheme, delete the protection group: a.
Click View > Go to Previous View to return to node view.
b.
c.
If you are already in node view, click the Provisioning > Protection
Click the protection group of the reporting card.
tabs.
d.
Click Delete .
If the card is provisioned for DCC, delete the DCC provisioning: a.
b.
Click the ONS 15454 Provisioning > Comm Channels > SDCC
Click the slots and ports listed in DCC terminations.
tabs. c.
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.
b.
c.
Click the Provisioning > Timing > General tabs.
Under NE Reference, click the drop-down arrow for Ref-1 .
d.
Change Ref-1 from the listed OC-N card to Internal Clock .
Click Apply .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2-124
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.160 INC-ISD
2.7.160 INC-ISD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
The DS-3 Idle condition indicates that the DS-3 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has an OOS-MA,MT service state. It is resolved when the OOS-MA,MT state ends.
Note INC-ISD is a condition and not an alarm. It is for information only and does not require troubleshooting.
2.7.161 INHSWPR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Inhibit Switch To Protect Request on Equipment condition occurs on traffic cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.
Clear the INHSWPR Condition
Step 1
Step 2
Step 3
If the condition is raised against a 1+1 port, complete the
“Initiate a 1+1 Manual Switch Command” section on page 2-255
.
If the condition is raised against a 1:1 card, complete the
“Initiate a 1:1 Card Switch Command” procedure on page 2-257
to switch it back.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.162 INHSWWKG
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Inhibit Switch To Working Request on Equipment condition occurs on traffic cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the protect system. If the card is part of a 1:N protection scheme, traffic can be switched between protect cards when the switch to working is disabled.
Clear the INHSWWKG Condition
Step 1 If the condition is raised against a 1+1 port, complete the
“Initiate a 1+1 Manual Switch Command” section on page 2-255
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-125
Chapter 2 Alarm Troubleshooting
2.7.163 INTRUSION-PSWD
Step 2
Step 3
If it is raised against a 1:1 card, complete the
“Initiate a 1:1 Card Switch Command” procedure on page 2-257
to switch traffic back.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.163 INTRUSION-PSWD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The Security Intrusion Incorrect Password condition occurs after a user attempts a provisionable (by
Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not in login sessions for lower-level users. The
INTRUSION-PSWD condition is automatically cleared when a provisionable lockout timeout expires, or it can be manually cleared in CTC by the Superuser if the lockout is permanent.
Clear the INTRUSION-PSWD Condition
Step 1
Step 2
Step 3
Click the Provisioning > Security > Users tabs.
Click Clear Security Intrusion Alarm .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.164 INVMACADR
Default Severity: Major (MJ), Non-Service Affecting (NSA)
SONET Logical Object: AIP
The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15454 MAC address is invalid. Each ONS 15454 has a unique, permanently assigned MAC address. The address resides on an
AIP EEPROM. The TCC2/TCC2P reads the address value from the AIP chip during boot-up and keeps this value in its synchronous dynamic RAM (SDRAM).
Under normal circumstances, the read-only MAC address can be viewed in the Provisioning/Network tab in CTC.
The ONS 15454 uses both IP and MAC addresses for circuit routing. When an INVMACADR alarm exists on a node, you see a PARTIAL circuit in the CTC circuit status column. The circuit works and is able to carry traffic, but CTC cannot logically display the circuit end-to-end information.
An invalid MAC address can be caused when:
• There is a read error from the AIP during bootup; in this case, the reading TCC2/TCC2P uses the default MAC address (00-10-cf-ff-ff-ff).
2-126
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.164 INVMACADR
•
•
•
There is a read error occurring on one of the redundant TCC2/TCC2Ps that read the address from the AIP; these cards read the address independently and could therefore each read different address values.
An AIP component failure causes a read error.
The ribbon cable connecting the AIP card to the backplane is bad.
Clear the INVMACADR Alarm
Step 1
Step 2
Step 3
Check for any outstanding alarms that were raised against the active and standby TCC2/TCC2P and resolve them.
If the alarm does not clear, determine whether the LCD display on the fan tray (
) is blank or if the text is garbled. If so, proceed to
. If not, continue with Step 3
.
At the earliest maintenance window, reset the standby TCC2/TCC2P:
Note The reset requires approximately five minutes. Do not perform any other step until the reset is complete.
Step 4
Step 5
Step 6 d.
e.
a.
b.
c.
Log into a node on the network. If you are already logged in, continue with Step
Identify the active TCC2/TCC2P.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Right-click the standby TCC2/TCC2P in CTC.
Choose Reset Card from the shortcut menu.
Click Yes in the Are You Sure dialog box.
The card resets, the FAIL LED blinks on the physical card, and connection to the node is lost. CTC switches to network view.
f.
g.
Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Double-click the node and ensure that the reset TCC2/TCC2P is still in standby mode and that the other TCC2/TCC2P is active.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Ensure that no new alarms associated with this reset appear in the CTC Alarms window.
h.
If the standby TCC2/TCC2P fails to boot into standby mode and reloads continuously, the AIP is probably defective. In this case, the standby TCC2/TCC2P is unsuccessfully attempting to read the
EEPROM located on the AIP. The TCC2/TCC2P reloads until it reads the EEPROM. Proceed to
If the standby TCC2/TCC2P rebooted successfully into standby mode, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265 .
Resetting the active TCC2/TCC2P causes the standby TCC2/TCC2P to become active. The standby
TCC2/TCC2P keeps a copy of the chassis MAC address. If its stored MAC address is valid, the alarm should clear.
After the reset, note whether or not the INVMACADR alarm has cleared or is still present.
Complete the
“Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
again to place the standby TCC2/TCC2P back into active mode.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-127
Chapter 2 Alarm Troubleshooting
2.7.165 IOSCFGCOPY
Step 7
After the reset, note whether or not the INVMACADR alarm has cleared or is still present. If the
INVMACADR alarm remains standing through both TCC2/TCC2P resets, this indicates that the AIP is probably defective. Proceed to
If the INVMACADR was raised during one TCC2/TCC2P reset and cleared during the other, the
TCC2/TCC2P that was active while the alarm was raised needs to be replaced. Continue with
If the faulty TCC2/TCC2P is currently in standby mode, complete the “Physically Replace a Traffic
for this card. If the faulty TCC2/TCC2P is currently active, during the next available maintenance window complete the
“Reset an Active TCC2/TCC2P Card and Activate the
Standby Card” procedure on page 2-263
and then complete the
“Physically Replace a Traffic Card” procedure on page 2-266 .
Note If the replacement TCC2/TCC2P is loaded with a different software version from the current
TCC2/TCC2P, the card bootup could take up to 30 minutes. During this time, the card LEDs flicker between Fail and Act/Sby as the active TCC2/TCC2P version software is copied to the new standby card.
Step 8
Step 9
Step 10
Step 11
Open a case with Cisco TAC (1 800 553-2447) for assistance with determining the node’s previous MAC address.
Replace the ribbon cable between the system board and the AIP with a known-good cable.
If the alarm persists, complete the
“Replace the Alarm Interface Panel” procedure on page 2-274
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.165 IOSCFGCOPY
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The IOS Configuration Copy in Progress condition occurs on ML-Series Ethernet cards when a
Cisco IOS startup configuration file is being uploaded or downloaded to or from an ML-Series card.
(This condition is very similar to the
“SFTWDOWN” condition on page 2-218
but it applies to
ML-Series Ethernet cards rather than to the TCC2/TCC2P.)
The condition clears after the copy operation is complete. (If it does not complete correctly, the
“NO-CONFIG” condition on page 2-181 could be raised.)
Note IOSCFGCOPY is an informational condition.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
2.7.166 ISIS-ADJ-FAIL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-128 November 2009
Chapter 2 Alarm Troubleshooting
2.7.166 ISIS-ADJ-FAIL
SONET Logical Object: OCN
The Open System Interconnection (OSI) Intermediate System to Intermediate-System (IS-IS) Adjacency
Failure alarm is raised by an intermediate system (node routing IS Level 1 or Level 1 and 2) when no IS or end system (ES) adjacency is established on a point-to-point subnet. The Intermediate-System
Adjacency Failure alarm is not supported by ES. It is also not raised by IS for disabled routers.
The alarm is typically caused by a misconfigured router manual area adjacency (MAA) address. For more information about IS-IS OSI routing and MAA configuration, refer to the “Management Network
Connectivity” chapter in the Cisco ONS 15454 Reference Manual . For more information about configuring OSI, refer to the “Turn Up Node” chapter in the Cisco ONS 15454 Procedure Guide .
Clear the ISIS-ADJ-FAIL Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Ensure that both ends of the communication channel are using the correct Layer 2 protocol and settings
(LAPD or PPP). To do this, complete the following steps: a.
b.
c.
At the local node, in node view, click the
Click the row of the circuit. Click Edit .
Provisioning > Comm Channels > SDCC tabs.
d.
In the Edit SDCC termination dialog box, view and record the following selections: Layer 2 protocol
(LAPD or PPP); Mode radio button selection (AITS or UITS); Role radio button selection (Network or User); MTU value; T200 value, and T203 selections.
Click Cancel .
e.
Login to the remote node and follow the same steps, also recording the same information for this node.
If both nodes do not use the same Layer 2 settings, you will have to delete the incorrect termination and recreate it. To delete it, click the termination and click Delete . To recreate it, refer to the “Turn Up Node” chapter in the Cisco ONS 15454 Procedure Guide for the procedure.
If the nodes use PPP Layer 2, complete the “Clear the EOC Alarm” procedure on page 2-80
. If the alarm does not clear, go to
If both nodes use the LAPD Layer 2 protocol but have different Mode settings, change the incorrect node’s entry by clicking the correct setting radio button in the Edit SDCC termination dialog box and clicking OK.
If the Layer 2 protocol and Mode settings are correct, ensure that one node is using the Network role and the other has the User role. If not (that is, if both have the same mode settings), correct the incorrect one by clicking the correct radio button in the Edit SDCC termination dialog box and clicking OK .
If the Layer 2, Mode, and Role settings are correct, compare the MTU settings for each node. If one is incorrect, choose the correct value in the Edit SDCC dialog box and click OK .
If all of the preceding settings are correct, ensure that OSI routers are enabled for the communications channels at both ends: a.
Click Provisioning > OSI > Routers > Setup tabs.
b.
c.
View the router entry under the Status column. If the status is Enabled, check the other end.
If the Status is Disabled, click the router entry and click Edit .
d.
Check the Enabled check box and click OK .
If the routers on both ends are enabled and the alarm still has not cleared, ensure that both ends of the communications channel have a common MAA: a.
Click the Provisioning > OSI > Routers > Setup tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-129
Chapter 2 Alarm Troubleshooting
2.7.167 KB-PASSTHR b.
Record the primary MAA and secondary MAAs, if configured.
Tip
Step 9
You can record long strings of information such as the MAA address by using the CTC export and print functions. Export it by choosing File > Export > html. Print it by choosing File > Print.
c.
d.
Log into the other node and record the primary MAA and secondary MAAs, if configured.
Compare this information. There should be at least one common primary or secondary MAA in order to establish an adjacency.
e.
If there is no common MAA, one must be added to establish an adjacency. Refer to the “Turn Up
Node” chapter in the Cisco ONS 15454 Procedure Guide for procedures.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.167 KB-PASSTHR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The K Bytes Pass Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are not active and the node is in K Byte pass-through state. It also occurs when a
BLSR ring is being exercised using the Exercise Ring command.
Clear the KB-PASSTHR Condition
Step 1
Step 2
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.168 KBYTE-APS-CHANNEL-FAILURE
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: OCN
The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For example, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.
This alarm is also raised during checksum failure if the K1 and K2 bytes are overwritten by test equipment. It is not raised in bidirectional full pass-through or K-byte pass-through states. The alarm is overridden by the
, the
“LOF (OCN)” alarm, page 2-145 , the
or the
2-130
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.169 LAN-POL-REV
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
Step 1
Step 2
Step 3
Step 4
The alarm is most frequently raised due to mismatched span provisioning. In this case, reprovision one side of the span with the same parameters. To do this, refer to the “Turn Up Network” chapter in the
Cisco ONS 15454 Procedure Guide.
If the error is not caused by misprovisioning, it is due to checksum errors within an OC-N, cross-connect, or TCC2/TCC2P. In this case, complete the
“Side Switch the Active and Standby Cross-Connect Cards” procedure on page 2-264
to allow CTC to resolve the issue.
If third-party equipment is involved, ensure that it is configured for the same APS channel as the
Cisco ONS equipment.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.169 LAN-POL-REV
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
The LAN Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised during a software upgrade when the card detects that a connected Ethernet cable has reversed receive wire pairs. The card automatically compensates for this reversal, but LAN-POL-REV stays active.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the LAN-POL-REV Condition
Step 1
Step 2
Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.170 LASER-APR
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-131
Chapter 2 Alarm Troubleshooting
2.7.171 LASERBIAS-DEG
2.7.171 LASERBIAS-DEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.172 LASERBIAS-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.173 LASEREOL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Laser Approaching End of Life alarm applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G,
TXP_MR_10E, and MXP_2.5G_10G cards. It is typically accompanied by the
“HI-LASERBIAS” alarm on page 2-117
. It is an indicator that the laser in the card must be replaced. How soon the replacement must happen depends upon the HI-LASERBIAS alarm’s threshold. If the threshold is set under 100 percent, the laser replacement can usually be done during a maintenance window. But if the
HI-LASERBIAS threshold is set at 100 percent and is accompanied by data errors, LASEREOL indicates the card must be replaced sooner.
Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .For more information about MXP and TXP cards, refer to the Cisco ONS 15454 DWDM
Troubleshooting Guide .
Clear the LASEREOL Alarm
Step 1
Step 2
Complete the “Physically Replace a Traffic Card” procedure on page 2-266 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.174 LASERTEMP-DEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.175 LCAS-CRC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
2-132
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.176 LCAS-RX-FAIL
The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against
ML-Series Ethernet cards and CE-series cards. It occurs when there is an equipment, path, or provisioning error on the virtual concatenation group (VCG) that causes consecutive 2.5 second CRC failures in the LCAS control word.
Transmission errors would be reflected in CV-P, ES-P, or SES-P performance monitoring statistics. If these errors do not exist, an equipment failure is indicated.
If LCAS is not supported on the peer node, the condition does not clear.
LCAS-CRC can also occur if the VCG source node is not LCAS-enabled, but the receiving node does have the capability enabled. Both source and destination nodes must have LCAS enabled. Otherwise, the
LCAS-CRC condition persists on the VCG.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Clear the LCAS-CRC Condition
Step 1
Step 2
Step 3
Step 4
Step 5
Look for and clear any associated equipment failures, such as the EQPT alarm, on the receive node or transmit node.
Look for and clear any bit error rate alarms at the transmit node.
If no equipment or SONET path errors exist, ensure that the remote node has LCAS enabled on the circuit: a.
In node view, click the Circuits tab.
b.
c.
Choose the VCAT circuit and click Edit .
In the Edit Circuit window, click the General tab. d.
Verify that the Mode column says LCAS .
If the column does not say LCAS, complete the
“Delete a Circuit” procedure on page 2-268 and recreate
it in LCAS mode using the instructions in the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.176 LCAS-RX-FAIL
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
The LCAS VCG Member Receive-Side-In Fail condition is raised against FC_MR-4 cards, CE-series cards, and ML-Series Ethernet cards with LCAS-enabled VCG.
LCAS VCGs treat failures unidirectionally, meaning that failures of the transmit or receive points occur independently of each other. The LCAS-RX-FAIL condition can occur on the receive side of an LCAS
VCG member for the following reasons:
• SONET path failure (a unidirectional failure as seen by the receive side)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-133
Chapter 2 Alarm Troubleshooting
2.7.177 LCAS-TX-ADD
• VCAT member is set out of group at the transmit side, but is set in group at the receive side
• VCAT member does not exist at the transmit side but does exist and is in group at the receive side
The condition can be raised during provisioning operations on LCAS VCGs but should clear when the provisioning is completed.
Software-enabled LCAS VCGs treat failure bidirectionally, meaning that both directions of a VCG member are considered failed if either transmit or receive fails. The LCAS-RX-FAIL condition is raised on these VCG members when a member receive side fails due to a SONET path failure.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Note ML-Series cards are LCAS-enabled. ML-Series and FC_MR-4 cards are SW-LCAS enabled.
Clear the LCAS-RX-FAIL Condition
Step 1
Step 2
Check for and clear any line or path alarms (typically ending in “-L” or “-P”).
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.177 LCAS-TX-ADD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-Series Ethernet and CE-series cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed. The remote likely reports a path condition such as the
“AIS-P” condition on page 2-36 or the
Note LCAS-TX-ADD is an informational condition and does not require troubleshooting.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
2.7.178 LCAS-TX-DNU
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
2-134
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.179 LINK-KEEPALIVE
The LCAS VCG Member Transmit-Side-In Do Not Use condition is raised on FC_MR-4 cards,
CE-series and ML-Series Ethernet cards when the transmit side of an LCAS VCG member is in the do-not use state. For a unidirectional failure, this condition is only raised at the source node. The
LCAS-TX-DNU condition is raised when the cable is unplugged.
The node reporting this condition likely reports an
“RFI-P” alarm, page 2-199 , and the remote node
likely reports a path alarm such as the
or the
.
Note LCAS-TX-DNU is an informational condition and does not require troubleshooting.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
2.7.179 LINK-KEEPALIVE
Default Severity: Critical (CR), Non-Service-Affecting (NSA)
SONET Logical Objects: ML1000, ML100T, MLFX, OCN
The LINK-KEEPALIVE alarm indicates that a span is not receiving a defined number of keep-alive messages on the ML card’s IEEE 802.17b-based interface or Cisco proprietary RPR interface within allotted keep-alive timeout period. Although this alarm defaults to a Critical (CR) severity, it can be downgraded if the span is protected.
A LINK-KEEPALIVE alarm causes an
, to also be raised. LINK-KEEPALIVE is suppressed by
. This alarm clears when a defined number of consecutive keep-alive messages is received on the interface.
Note In the Cisco IOS CLI “show ons alarms” command display, this alarm is called KEEP-ALIVE-FAIL.
Note The GFP-UP-MISMATCH, GFP-CSF, GFP-LFD, and TPTFAIL alarms suppress the
LINK-KEEPALIVE alarm even though the LINK-KEEPALIVE alarm has higher severity than the other alarms. The GFP alarms are promoted because the LINK-KEEPALIVE alarm information is contained within a GFP frame. The TPTFAIL alarm is promoted because it is a layer 1 alarm while
LINK-KEEPALIVE is a layer 2 alarm.
Clear the LINK-KEEPALIVE Alarm
Step 1
Step 2
Step 3
Verify that no SONET or GFP circuit alarms that could impact Ethernet data traffic are present. If any are present, clear them using the relevant procedures in this chapter.
Verify that the
is not present. If it is present, complete the trouble-clearing procedure.
Verify that the keep-alive timer on this IEEE RPR 802.17b-based station has the same value as its neighboring RPR-IEEE stations.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-135
Chapter 2 Alarm Troubleshooting
2.7.180 LKOUTPR-S
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.180 LKOUTPR-S
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Lockout of Protection Span condition occurs when span traffic is locked out of a protect span using the Lockout of Protect command. This condition is visible on the network view Alarms, Conditions, and
History tabs after the lockout has occurred and accompanies the
circuit map.
Clear the LKOUTPR-S Condition
Step 1
Step 2
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.181 LMP-FAIL
Default Severity:Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: CLIENT, CTRL, TLINK
The Link Management Protocol Fail alarm is raised by the TCC2/TCC2P card when an LMP control channel fails or when there is a traffic engineering (TE) link correlation error. When the alarm is raised against a control channel, it uses a control channel (CTRLx) AID. When the alarm is raised against a TE link, a TE link AID (TLINKx) is used.
The alarm clears when the control channel or TE link is restored.
Note LMP-FAIL occurs independently of the condition hierarchy between
, or
Note When the LMP-FAIL alarm is reported against a control channel (CTRLx) AID, it only refers to control channel failure. It does not directly indicate data link or traffic engineering link status.
Note When the LMP-FAIL alarm is reported against a TE link AID (TLINKx), it refers only to TE link status, not to control channel or data link status.
2-136
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.182 LMP-SD
Clear the LMP-FAIL Alarm
Step 1
Step 2
Step 3
Step 4
Verify the AID (CTRLx or TLINKx) of the alarm.
If the alarm is against the control channel AID, this is caused by mismatched control channel parameters between the near-end ONS 15454 and the far-end node (which may be another vendor’s equipment).
Complete the following steps: a.
Determine whether both near-end and far-end sides of the control channel are in the IS administrative state:
•
•
Click the Provisioning > Comm Channels > LMP > Control Channel tabs and view the
Admin State column content for the channel.
If the status does not say IS, change it and click Apply .
b.
c.
d.
Verify that the far-end node is using the near-end node’s IP address as its remote node IP address, and that the far end is also using the LMP node ID as its remote node ID. Update the far end’s values if they are incorrect.
If instead the alarm is raised against the TE link AID, complete the following steps: a.
Determine whether the near-end node LMP configuration contains the far-end node’s IP address as its remote node IP. Also verify that the near-end node’s LMP configuration uses the LMP node ID as its own remote node ID. If one or more of these values is incorrect, enter it correctly.
Determine whether the far-end node LMP configuration contains the near-end node's IP address as its remote node IP. Also verify that the far-end node’s LMP configuration uses the LMP node ID as its own remote node ID. If one or more of these values is incorrect, enter it correctly.
b.
Determine whether both near-end and far-end sides of the TE link are in the IS administrative state.
If either end is currently down, update its administrative state to IS:
• Click the Provisioning > Comm Channels > LMP > TE link tab.
• If the status does not say IS, change it and click Apply .
Determine whether the near-end node’s remote TE link ID matches the far-end node’s local TE link
ID. If the near-end node’s remote value is incorrect, enter it correctly.
c.
Determine whether the far-end node’s remote TE link ID corresponds to the near-end node’s local
TE link ID. If the far-end node’s remote value is incorrect, enter it correctly.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.182 LMP-SD
Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: GE
The LMP Data Link Signal Degrade condition occurs for when the TCC2/TCC2P receives an LMP link summary or channel status message that the control channel is not available from the far end, so the data link level of service is not guaranteed. The degrade range is provisionable.
LMP-SD clears when the TCC2/TCC2P receives a link summary or channel status message reporting that the data link is in the Signal Okay (OK) state.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-137
Chapter 2 Alarm Troubleshooting
2.7.183 LMP-SF
LMP-SD is part of an alarm hierarchy that includes
.
The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If
LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end
LOS-type alarms for DWDM clients. LMP-SD, however, does not suppress LOS alarms.
This condition clears when the far-end trouble has been cleared.
Clear the LMP-SD Condition
Step 1 Look for and clear any of the following alarms in
Table 2-13 and Table 2-14 occurring on the far-end
port. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide , R7.x
for DWDM trunk (
)
and client ( Table 2-14 ) alarm trouble-clearing procedures.
Table 2-13 Transponder Trunk Alarms that Cause LMP-SD
Trunk Port Alarm
SD
OTUK-SD
ODUK-SD-PM
ODUK-SD-TCM1
ODUK-SD-TCM2
LMP Failure
SD
SD
SD
SD
SD
Direction
Tx
Tx
Tx
Tx
Tx
Table 2-14 Transponder Client Alarm that Causes LMP-SD
Client Port Alarm
SD
LMP Failure
SD
Direction
Rx
Step 2 If the LMP-SD condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.183 LMP-SF
Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: GE
The LMP Data Link Signal Fail condition notifies the near-end user of a far-end problem (and thus is
NSA for the near end). The near-end’s TCC2/TCC2P receives an LMP link summary or channel status message that the data link service has failed. The signal fail threshold provisionable.
LMP-SF clears when the TCC2/TCC2P receives a link summary or channel status message reporting that the data link is in the Signal Okay (OK) state.
2-138
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.183 LMP-SF
LMP-SF is part of an alarm hierarchy that includes
.
The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If
LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end
LOS-type alarms for DWDM clients, but LMP-SD does not suppress LOS-type alarms.
This condition clears when the far-end trouble has been cleared.
Clear the LMP-SF Condition
Step 1 Look for and clear any of the following alarms in
Table 2-15 , Table 2-16 , or Table 2-17 occurring on the
far-end port. The card alarms are located in this chapter. The Cisco ONS 15454 DWDM Troubleshooting
Guide , R7.x
contains trouble-clearing procedures for DWDM trunk ( Table 2-16 ) and client ( Table 2-17
) alarms.
Table 2-15 Transponder Card Alarms that Cause LMP-SF
Card Alarm
LMP Failure
SF
SF
Direction
Tx
Tx
Table 2-16 Transponder Trunk Alarms that Cause LMP-SF
Trunk Port Alarm
LOS
OTUK-LOF
OTUK-AIS
LMP Failure
SF
SF
SF
LOM SF
OTUK-SF SF
ODUK-SF-PM
ODUK-SF-TCM1
SF
SF
ODUK-SF-TCM2 SF SF
FEC-MISM SF
Tx
Tx
Tx
Tx
Direction
Tx
Tx
Tx
Tx
Tx
Table 2-17
Client Alarm
LOS
SIGLOSS
SYNCLOSS
CARLOSS
LOF
Transponder Client Alarms that Cause LMP-SF
LMP Failure
SF
SF
SF
SF
SF
Direction
Rx
Rx
Rx
Rx
Rx
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-139
Chapter 2 Alarm Troubleshooting
2.7.184 LMP-UNALLOC
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.184 LMP-UNALLOC
Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: GE
The LMP Data Link Unallocated condition is raised when the TCC2/TCC2P receives an LMP link summary or channel status message reporting that the data link as unallocated for data traffic. The condition clears when the data link is allocated and sends an LMP link summary or channel status message to this effect. If a data link has the LMP-UNALLOC alarm raised against it, this should suppress all other alarms on the client port, since the far-end node is not using the errored port. (Consequently you do not have to clear any alarms on the far-end node’s unused port.)
LMP-UNALLOC is part of an alarm hierarchy that includes
.
The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If
LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end
LOS-type DWDM client alarms, but LMP-SD does not.
In most cases, this condition is an informational notice at the near-end node that the far-end port is not being utilized. If, however, the far-end port should be allocated for traffic, log into the Technical Support
Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.185 LOA
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: VCG
The Loss of Alignment on a VCG is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.
Clear the LOA Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
In network view, click the Circuits tab.
Click the alarmed VCG and then click Edit .
In the Edit Circuit window, view the source and destination circuit slots, ports, and STSs.
Identify whether the STS travels across different fibers. If it does, complete the
“Delete a Circuit” procedure on page 2-268 .
Recreate the circuit using the procedure in the “Create Circuits and VT Tunnels” chapter in the
Cisco ONS 15454 Procedure Guide .
2-140
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.186 LOCKOUT-REQ
Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.186 LOCKOUT-REQ
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN, STSMON, VT-MON
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an OC-N port in a 1+1 facility protection group. This can be accomplished by locking traffic onto the working port with the LOCK ON command (thus locking it off the protect port), or locking it off the protect port with the LOCK OUT command. In either case, the protect port will show
“Lockout of Protection,” and the Conditions window will show the LOCKOUT-REQ condition.
A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.
Clear the LOCKOUT-REQ Condition
Step 1
Step 2
Complete the
“Clear a Lock-On or Lockout Command” procedure on page 2-257
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.187 LOF (BITS)
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: BITS
The Loss of Frame (LOF) BITS alarm occurs when a port on theTCC2/TCC2P BITS input detects an
LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data.
Note The procedure assumes that the BITS timing reference signal is functioning properly. It also assumes the alarm is not appearing during node turn-up.
Clear the LOF (BITS) Alarm
Step 1 Verify that the line framing and line coding match between the BITS input and the TCC2/TCC2P: a.
b.
In node or card view, note the slot and port reporting the alarm.
Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-141
Chapter 2 Alarm Troubleshooting
2.7.188 LOF (DS1) c.
d.
e.
f.
g.
Click the Provisioning > Timing > BITS Facilities tabs.
Verify that the Coding setting matches the coding of the BITS timing source, either B8ZS or AMI.
If the coding does not match, click Coding and choose the appropriate coding from the drop-down list.
Verify that Framing matches the framing of the BITS timing source, either ESF or SF (D4).
If the framing does not match, click Framing and choose the appropriate framing from the drop-down list.
Note On the timing subtab, the B8ZS coding field is normally paired with ESF in the Framing field and the AMI coding field is normally paired with SF (D4) in the Framing field.
Step 2
Step 3
If the alarm does not clear when the line framing and line coding match between the BITS input and the
TCC2/TCC2P, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the
TCC2/TCC2P.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.188 LOF (DS1)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: DS1
The DS-1 LOF alarm indicates that the receiving ONS 15454 has lost frame delineation in an incoming
DS-1 data stream.
Clear the LOF (DS1) Alarm
Step 1 Verify that the line framing and line coding match between the DS1 port and the signal source: a.
b.
In CTC, note the slot and port reporting the alarm.
Find the coding and framing formats of the signal source for the card reporting the alarm. You could need to contact your network administrator for the format information.
c.
d.
e.
f.
g.
Display the card view of the reporting card.
Click the Provisioning > Line tabs.
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 list and choose the matching type.
Verify that the reporting Line Coding matches the signal source line coding (AMI and AMI or B8ZS and B8ZS). If the signal source line coding does not match the reporting port, click the Line Coding cell and choose the correct type from the drop-down list.
Click Apply .
2-142
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.189 LOF (DS3)
Note On the Line tab, the B8ZS coding field is normally paired with ESF in the Framing field.
AMI coding is normally paired with SF (D4) in the Framing field.
Note When you replace a card with the identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.189 LOF (DS3)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: DS3
The DS-3 LOF alarm indicates that the receiving ONS 15454 has lost frame delineation in the incoming
DS-3 data stream on DS3XM-6, DS3XM-12, or add DS3/EC1-48 cards. The framing of the transmitting equipment could be set to a format that differs from the receiving system. On DS3XM cards, the alarm occurs only on cards with the provisionable framing format set to C Bit or M13 and not on cards with the provisionable framing format is set to unframed.
Clear the LOF (DS3) Alarm
Step 1
Step 2
Change the line type of the non-ONS equipment attached to the reporting card to C Bit: a.
Display the card view of the reporting card.
b.
c.
d.
Click the Provisioning > Line tabs.
Verify that the line type of the reporting port matches the line type of the signal source.
If the signal source line type does not match the reporting port, click Line Type and choose C Bit from the drop-down list.
Click Apply .
e.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.190 LOF (E1)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: E1
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-143
Chapter 2 Alarm Troubleshooting
2.7.191 LOF (EC1)
The E1 LOF alarm appears on the DS1/E1-56 card when the card is placed in All E1 mode. It indicates that the receiving ONS 15454 has lost frame delineation in an incoming E1 data stream. The transmitting equipment could possibly have its framing set to a format that differs from the receiving node. For more information about the DS1/E1-56 card, refer to the “Electrical Cards” chapter in the Cisco ONS 15454
Reference Manual .
Note The DS1/E1-56 card only carries an E1 signal within an STS-3c/VT2 circuit.
Clear the LOF (E1) Alarm
Step 1 Verify that the line framing and line coding match between the DS1/E1-56 port and the signal source: a.
b.
In CTC, note the slot and port reporting the alarm.
Find the coding and framing formats of the signal source for the card reporting the alarm. You could need to contact your network administrator for this information.
c.
d.
e.
f.
g.
Double-click the DS1/E1-56 card to open the card view.
Click the Provisioning > Line tabs.
Verify that the line type of the reporting port matches the line type (E1_MF, E1_CRCMF,
AUTOFRAMED, UNFRAMED) of the signal source. If the signal source line type does not match the reporting port, click the Line Type cell to reveal a drop-down list and choose the matching type.
Verify that the reporting Line Coding matches the signal source line coding. If the signal source line coding does not match the reporting port, click the Line Coding cell and choose the correct type from the drop-down list.
Click Apply .
Note When you replace a card with the identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.191 LOF (EC1)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EC1
The EC1/EC1-12 LOF alarm occurs when a port on the reporting EC1/EC1-12 or DS3/EC1-48 card has an LOF condition. LOF indicates that the receiving ONS 15454 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.
2-144
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.192 LOF (OCN)
Clear the LOF (EC1) Alarm
Step 1 Verify cabling continuity to the port reporting the alarm. To verify cable continuity, follow site practices.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
If cabling continuity is good, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, see the loopback procedures in Chapter 1, “General Troubleshooting” to
isolate the fault causing the LOF alarm.
If the alarm does not clear, or if you need assistance conducting network troubleshooting tests, call
Cisco TAC to report a Service-Affecting (SA) problem 1 800 553-2447.
2.7.192 LOF (OCN)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: OCN
The LOF alarm occurs when a port on the reporting card has an LOF condition. It can also occur on
ONS 15454 MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G,TXP_MR_10E, or TXPP_MR_2.5G cards reporting LOF. The alarm indicates that the receiving ONS 15454 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.
When the alarm is raised on an OC-N card, it is sometimes an indication that the OC-N card expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver.
Note For information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the LOF (OCN) Alarm
Step 1 Verify cabling continuity to the port reporting the alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly. To verify cable continuity, follow site practices.
Step 2
Step 3
If cabling continuity is good, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, see the loopback procedures in Chapter 1, “General Troubleshooting” to
isolate the fault causing the LOF alarm.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-145
Chapter 2 Alarm Troubleshooting
2.7.193 LOF (STSTRM)
Step 4 If the alarm does not clear, or if you need assistance conducting network troubleshooting tests, call
Cisco TAC to report a Service-Affecting (SA) problem 1 800 553-2447.
2.7.193 LOF (STSTRM)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: STSTRM
A Loss of Frame alarm for an STS circuit termination indicates that the LOF has occurred at the
.
Clear the LOF (STSTRM) Alarm
Step 1
Step 2
Complete the “Clear the LOF (OCN) Alarm” alarm on page 2-145
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.194 LOF (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.195 LOGBUFR90
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
The Log Buffer Over 90 alarm indicates that the per-NE queue of incoming alarm, event, or update capacity of 5000 entries is over 90% full. LOGBUFR90 will clear if CTC recovers. If it does not clear, the LOGBUFROVFL alarm occurs.
Note LOGBUFR90 is an informational alarm and does not require troubleshooting.
2.7.196 LOGBUFROVFL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
2-146
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.197 LO-LASERBIAS
The Log Buffer Overflow alarm indicates that the CTC per-NE queue of incoming alarm, event, or updates, which has a capacity of 5000 entries, has overflowed. This happens only very rarely; if the alarm does occur, you must restart the CTC session. If this alarm occurs, it is likely that some updates are missing.
Clear the LOGBUFROVFL Alarm
Step 1
Step 2
Restart the CTC session.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).
2.7.197 LO-LASERBIAS
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Object: PPM
The Equipment Low Transmit Laser Bias Current alarm is raised against the TXP and MXP card laser performance. The alarm indicates that the card laser has reached the minimum laser bias tolerance.
If the LO-LASERBIAS alarm threshold is set at 0 percent (the default), the laser's usability has ended.
If the threshold is set at 5 percent to10 percent, the card is still usable for several weeks or months before you need to replace it.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the LO-LASERBIAS Alarm
Step 1
Step 2
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.198 LO-LASERTEMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Object: PPM
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-147
Chapter 2 Alarm Troubleshooting
2.7.199 LOM
The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards.
LO-LASERTEMP occurs when the internally measured transceiver temperature falls below the card setting by35.6 degrees F or 2 degrees C. A laser temperature change affects the transmitted wavelength.
(Two degrees Celsius is equivalent to about 200 picometers in the wavelength.)
When the TXP or MXP card raises this alarm, the laser is automatically shut off. The
“LOS (OCN)” alarm on page 2-158
is raised at the far-end node and the
“DUP-IPADDR” alarm on page 2-75
is raised at the near end. To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM > Current Values tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the LO-LASERTEMP Alarm
Step 1
Step 2
Step 3
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 for the reporting MXP or TXP
card.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting MXP or TXP card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.199 LOM
Default Severity: Critical (CR), Service-Affecting (SA) for STSMON, STSTRM, TRUNK;
Major (MJ) for VT-TERM
SONET Logical Objects: STSMON, STSTRM, VT-TERM
DWDM Logical Object: TRUNK
The Optical Transport Unit (OTU) Loss of Multiframe is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.)
The alarm applies to OCN ports when the Multi Frame Alignment Signal (MFAS) overhead field is errored for more than five frames and persists for more than 3 milliseconds.
Note Optical cards do not recognize the LOM. The system redirects the LOM alarm to the incoming side so that any optical card can display this alarm as a TERM alarm.
Clear the LOM Alarm
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2-148
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.200 LOP-P
2.7.200 LOP-P
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: STSMON, STSTRM
A Loss of Pointer Path alarm indicates that the SONET path pointer in the overhead has been lost. LOP occurs when valid H1/H2 pointer bytes are missing from the overhead. Receiving equipment monitors the H1/H2 pointer bytes to locate the SONET payload. An LOP-P alarm occurs when eight, nine, or ten consecutive frames do not have valid pointer values. The alarm clears when three consecutive valid pointers are received.
The LOP-P alarm can occur when the received payload does not match the provisioned payload. The alarm is caused by a circuit type mismatch on the concatenation facility. For example, if an STS-1 is sent across a circuit provisioned for STS-3c, an LOP-P alarm occurs.
For the FC_MR-4 card, an LOP-P is raised if a port is configured for a SONET signal but receives an
SONET signal instead. (This information is contained in the H1 byte bits 5 and 6.)
Clear the LOP-P Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, click the Circuits tab and view the alarmed circuit.
Verify the circuit size listed in the Size column. If the size is different from what is expected, such as an
STS3c instead of an STS1, this causes the alarm.
If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm. For specific procedures to use the test set equipment, consult the manufacturer. Ensure that the test set monitoring is set up for the same size as the circuit provisioning.
Refer to the manufacturer’s instructions for test-set use.
If the error is not due to an incorrectly configured test set, the error is in the provisioned CTC circuit size. Complete the
“Delete a Circuit” procedure on page 2-268 .
Recreate the circuit for the correct size. For procedures, refer to the “Create Circuits and VT Tunnels” chapter in the Cisco ONS 15454 Procedure Guide.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.201 LOP-V
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: VT-MON, VT-TERM
The LOP VT alarm indicates a loss of pointer at the VT level.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-149
Chapter 2 Alarm Troubleshooting
2.7.202 LO-RXPOWER
The LOP-V alarm can occur when the received payload does not match the provisioned payload. LOP-V is caused by a circuit size mismatch on the concatenation facility.
Clear the LOP-V Alarm
Step 1
Complete the “Clear the LOP-P Alarm” procedure on page 2-149 .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.202 LO-RXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC
The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, MRC-12, MRC-4, and OC192-XFP card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls below the threshold value, which is user-provisionable.
Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .
Note When you upgrade a node to Software Release 6.0 or later, this enables received optical power PMs for the OC3-8, OC192-SR, OC192-IR, OC192-ITU, OC-192-XFP, MRC-12, and MRC25G-4 cards. The newly enabled HI-RXPOWER and LO-RXPOWER alarms require that you initialize a site-accepted optical power (OPR0) nominal value after the upgrade. (To do this, refer to the procedure in the “Turn
Up a Node” chapter in the Cisco ONS 15454 Procedure Guide .) When you apply the value change, CTC uses the new OPR0 value to calculate PM percentage values. If you do not change the nominal value, the
HI-RXPOWER or LO-RXPOWER may be raised in response to the unmodified setting.
Clear the LO-RXPOWER Alarm
Step 1
Step 2
At the transmit end of the errored circuit, increase the transmit power level within safe limits.
Find out whether new channels have been added to the fiber. Up to 32 channels can be transmitted on the same fiber, but the number of channels affects power. If channels have been added, power levels of all channels need to be adjusted.
2-150
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.203 LOS (2R)
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Note If the card is part of an amplified DWDM system, adding channels on the fiber affects the transmission power of each channel more than it would in an unamplified system.
Find out whether gain (the amplification power) of any amplifiers has been changed. Changing amplification also causes channel power to need adjustment.
If the alarm does not clear, remove any receive fiber attenuators or replace them with lower-resistance attenuators.
If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility (line) loopback on a known-good port. The error reading you get is not as precise, but you generally know whether the fiber is faulty. For specific procedures to use the test set equipment, consult the manufacturer.
If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, do a facility loopback on the transmit and receive ports with known-good loopback cable. Complete the
“1.4.1 Perform a Facility Loopback on a Source-Node Optical Port” procedure on page 1-48
or the
“1.4.4 Perform a Facility Loopback on an Intermediate-Node Optical Port” procedure on page 1-57 to
test the loopback.
the card at the next available maintenance window.
If no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.203 LOS (2R)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.204 LOS (BITS)
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: BITS
The LOS (BITS) alarm indicates that the TCC2/TCC2P has an LOS from the BITS timing source. The
LOS (BITS) means the BITS clock or the connection to it failed.
Clear the LOS (BITS) Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-151
Chapter 2 Alarm Troubleshooting
2.7.205 LOS (DS1)
Step 1
Step 2
Step 3
Verify the wiring connection from the BITS clock pin fields on the ONS 15454 backplane to the timing source.
If wiring is good, verify that the BITS clock is operating properly.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.205 LOS (DS1)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: DS1
A LOS (DS1) alarm for a DS-1 port occurs when the port on the card is in service but no signal is being received. A cabling issue or a configuration issue could cause this alarm. If an upstream equipment failure causes a transmission failure, the LOS (DS1) will likely be demoted by a card-level alarm (to the
DS1/E1-56).
Clear the LOS (DS1) Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Step 4
Step 5
Verify that the fiber cable is properly connected and attached from the correct transmitting port to the correct receiving port. For more information about fiber connections and terminations, refer to the
“Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Clean the cable ends using site practices or, if none exists, complete the procedure in the “Maintain the
Node” chapter of the Cisco ONS 15454 Procedure Guide .
If the alarm is raised on a DS1/E1-56 card, verify that the card is placed in the correct service mode by completing the following steps: a.
b.
Double-click the card to open the card view.
Click the Provisioning > Card tabs.
c.
Verify that the Operating Mode column says All DS1 for your errored circuit.
For any other DS-1 or DS-3 card, consult site records to determine whether the port raising the alarm has been assigned.
If the port is not currently assigned, place the port out of service using the following steps: a.
Double-click the card to open the card view.
b.
c.
For a DS-1 card, click the Maintenance > Loopback tabs. For a DS-1 line on a DS3XM-6 or
DS3XM-12 card, click the Maintenance > DS1 tabs.
Under Admin State, click OOS,DSBLD .
d.
Click Apply .
2-152
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.206 LOS (DS3)
Step 6 For any card, if the port is assigned, verify that the correct one is in service: a.
To confirm this physically, confirm that the LED is correctly illuminated on the physical card.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
b.
To determine this virtually, double-click the card in CTC to open the card view and complete the following substeps:
• Click the Provisioning > Line tabs.
•
•
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS . Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. For specific procedures to use the test set equipment, consult the manufacturer.
Ensure that the transmit and receive outputs from the DSx patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If there is a valid signal but the alarm does not clear, replace the electrical connector on the ONS 15454.
If a valid electrical signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the “Install Cards and
Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Repeat Steps
to
for any other port on the card that reports the LOS.
If the alarm does not clear, check for any card-level alarm that could affect this port.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.206 LOS (DS3)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: DS3
The LOS (DS3) for a DS-3 port occurs when the port on a DS3XM-6, DS3XM-12, or DS3/EC1-48 card is in service but no signal is being received. The alarm is caused by incorrect or dirty cabling, a fiber break, or upstream equipment failure.
Note If a circuit shows a partial status when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-153
Chapter 2 Alarm Troubleshooting
2.7.206 LOS (DS3)
Clear the LOS (DS3) Alarm
Step 1
Step 2
Check for any upstream failures in the transmitting equipment.
Verify that the cable is properly connected from the transmitting port and attached to the correct receiving port at the node with the LOS. For more information about fiber connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 3
Step 4
Step 5
Step 6
Clean the cable ends using site practices or, if none exists, complete the procedure in the “Maintain the
Node” chapter in the Cisco ONS 15454 Procedure Guide .
Consult site records to determine whether the port raising the alarm has been assigned.
If the port is not currently assigned, place the port out of service using the following steps: a.
b.
c.
d.
Double-click the card to open the card view.
Click the Maintenance > DS3 tabs.
Under Admin State, click
Click Apply .
OOS,DSBLD .
If the port is assigned, verify that the correct one is in service: a.
To confirm this physically, confirm that the LED is correctly illuminated on the physical card.
b.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine this virtually, double-click the card in CTC to open the card view and complete the following substeps:
•
•
•
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS . Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 7
Step 8
Step 9
Step 10
Step 11
Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. (For specific procedures to use the test set equipment, consult the manufacturer.)
Ensure that the transmit and receive outputs from the DSx patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If there is a valid signal but the alarm does not clear, replace the electrical connector on the ONS 15454.
If the test set shows signal errors but the cabling is correctly installed and the transmitting device is operational, the existing cabling could still be faulty. Use the test set to locate the bad cable and replace it. To do this, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454
Procedure Guide .
Repeat Steps
1 to 10 for any other port on the card that reports the LOS.
2-154
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.207 LOS (E1)
Step 12
Step 13
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.207 LOS (E1)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: E1
An LOS (E1) alarm for a DS1/E1-56 card port occurs when the card is placed in All E1 mode and is in service, but the alarmed port is not receiving a signal due to a physical or provisioning problem. The physical causes for the alarm could be incorrectly connected or faulty cabling. The software causes could be improperly configured card or circuit size.
For more information about the DS1/E1-56 card, refer to the “Electrical Cards” chapter in the
Cisco ONS 15454 Reference Manual .
Clear the LOS (E1) Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Verify that the cable is properly connected and attached to the correct port. For more information about connecting cable, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454
Procedure Guide . Also refer to site records for your specific cabling scheme.
Ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Clean the cable using your site practices. If none exists, complete the procedure in the “Maintain the
Node” chapter in the Cisco ONS 15454 Procedure Guide .
Confirm that the card is properly provisioned to carry the E1 payload: a.
Double-click the card to open the card view.
b.
c.
Click the Provisioning > Card tabs.
Under the Operating Mode column, you should see “All E1.” If you see “All DS1,” click the drop-down to change it and click Apply .
Use a test set to confirm that a valid E1 signal exists on the line. Test the line as close to the receiving card as possible. (For specific procedures to use the test set equipment, consult the manufacturer.) If the test set shows errors, the cabling could still be faulty despite being correctly installed. Use the tester to isolate the bad section of cable and replace it. Refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide for procedures.
Repeat Steps
to
5 for any other port on the card that reports the LOS (E1).
If the alarm does not clear, look for any card-level alarm that could cause this alarm.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-155
Chapter 2 Alarm Troubleshooting
2.7.208 LOS (EC1)
Step 8
Step 9
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.208 LOS (EC1)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EC1
LOS on an EC1/EC1-12 or DS3/EC1-48 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (EC1) most likely means that the upstream transmitter has failed.
If an EC1 LOS alarm is not accompanied by additional alarms, a cabling problem (such as an incorrect attachment, fiber cut, or other fiber error) usually causes this alarm. The condition clears when the problem is corrected, allowing two consecutive valid frames to be received.
Note If a circuit shows a partial status when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the LOS (EC1) Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3 b.
c.
d.
Check for any upstream equipment failures that could cause the LOS (EC1) in this node.
If there is no cause upstream, verify cabling continuity from the transmitting port to the receiving port reporting LOS (EC1) To verify cable continuity, follow site practices.
If the continuity is good, clean the fiber according to site practice. If none exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If the cabling is good, verify that the correct EC1-12 port is in service: a.
Confirm that the LED is correctly lit on the physical card.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine whether the port is in service, double-click the card in CTC to open the card view.
Click the Provisioning > Line tabs.
e.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS . Click Apply .
2-156
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.209 LOS (ESCON)
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
If the correct port is in service, use an optical test set to confirm that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
If the signal is valid, ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the
“Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If a valid signal exists but the alarm does not clear, replace the cable connector on the ONS 15454.
Repeat Steps
through
6 for any other port on the card that reports the LOS (EC1).
If the alarm does not clear, the cabling could still be faulty despite correct attachments. Use the test set to locate the bad cable and replace it using the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, look for any card-level alarm that could cause this port alarm.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.209 LOS (ESCON)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.210 LOS (FUDC)
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: FUDC
The LOS (FUDC) alarm is raised if there is a UDC circuit created on an AIC-I UDC port but the port is not receiving signal input. The downstream node has an AIS condition raised against the AIC-I port transmitting the UDC. FUDC refers to the 64-kb user data channel using the F1 byte.
Clear the LOS (FUDC) Alarm
Step 1
Step 2
Step 3
Verify cable continuity to the AIC-I UDC port. To verify cable continuity, follow site practices.
Verify that there is a valid input signal using a test set. For specific procedures to use the test set equipment, consult the manufacturer.
If there is a valid signal, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-157
Chapter 2 Alarm Troubleshooting
2.7.211 LOS (ISC)
Step 4
Step 5
Step 6
Step 7
If the alarm does not clear, verify that the UDC is provisioned: a.
b.
At the network view, click the Provisioning > Overhead Circuits tabs.
If no UDC circuit exists, create one. Refer to the “Create Circuits and VT Tunnels” chapter in the
Cisco ONS 15454 Procedure Guide.
c.
If a user data circuit exists (shown as User Data F1 under the Type column), check the source and destination ports. These must be located on AIC-I cards to function.
If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.
If no other alarms exist that could be the source of the LOS (FUDC), or if clearing another alarm did not clear the LOS, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.211 LOS (ISC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.212 LOS (MSUDC)
The LOS (MSUDC) alarm is not used in this platform in this release. It is reserved for future development.
2.7.213 LOS (OCN)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: OCN
An LOS alarm on an OC-N port occurs when a SONET receiver detects an all-zero pattern for
10 microseconds or longer. An LOS alarm means the upstream transmitter has failed. If an OC-N LOS alarm is not accompanied by additional alarms, a fiber break is usually the cause of the alarm. It clears when two consecutive valid frames are received.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
2-158
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.213 LOS (OCN)
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note If a circuit shows a partial status when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the LOS (OCN) Alarm
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Using site practices, verify fiber continuity to the port.
If the cabling is good, verify that the correct port is in service: a.
Confirm that the LED is correctly illuminated on the physical card.
b.
c.
d.
e.
f.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine whether the OC-N port is in service, double-click the card in CTC to open the card view.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS .
Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, verify that the power level of the optical signal is within the OC-N card receiver specifications. The
“1.12.3 OC-N Card Transmit and Receive Levels” section on page 1-140
lists these specifications for each OC-N card. For DWDM cards, refer to the Cisco ONS 15454 DWDM
Reference Manual for levels.
If the optical power level is within specifications, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
If a valid signal exists, replace the connector on the backplane.
Repeat Steps
to
6 for any other port on the card reporting the LOS (OC-N).
If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-159
Chapter 2 Alarm Troubleshooting
2.7.214 LOS (OTS)
Step 9
Step 10
If no other alarms exist that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.214 LOS (OTS)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.215 LOS (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.216 LOS-O
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.217 LOS-P (OCH)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.218 LOS-P (OMS, OTS)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.219 LOS-P (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.220 LO-TXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM
2-160
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.221 LPBKCRS
The Equipment Low Transmit Power alarm is an indicator for the TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G and OC192-XFP card transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.
Note For more information about provisioning MXP or TXP PPMs, refer to the “Provision Transponders and
Muxponders” chapter of the Cisco ONS 15454 DWDM Procedure Guide . For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the LO-TXPOWER Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Display the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, or
OC192-XFP card view.
Click the Provisioning > Optics Thresholds > Current Values tabs.
Increase the TX Power Low column value by 0.5 dBm.
If the card transmit power setting cannot be increased without affecting the signal, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
.
If no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.221 LPBKCRS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between an optical card and an OC-192 card. A cross-connect loopback test occurs below line speed and does not affect traffic.
For more information on loopbacks, see the
“1.4 Troubleshooting Optical Circuit Paths With
Loopbacks” section on page 1-47 .
Note Cross-connect loopbacks occur below line speed. They do not affect traffic.
Clear the LPBKCRS Condition
Step 1
Step 2
Step 3
To remove the loopback cross-connect condition, double-click the optical card in CTC to open the card view.
Complete the
“Clear an OC-N Card Cross-Connect (XC) Loopback Circuit” procedure on page 2-269 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-161
Chapter 2 Alarm Troubleshooting
2.7.222 LPBKDS1FEAC-CMD
2.7.222 LPBKDS1FEAC-CMD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS1
The DS-1 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-1 FEAC loopback on DS3XM-6, DS3XM-12, or DS3/EC1-48 cards. For more information about
FEAC loopbacks, see the
“1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With
FEAC Loopbacks” section on page 1-45
.
Note LPBKDS1FEAC-CMD is an informational condition and does not require troubleshooting.
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
2.7.223 LPBKDS3FEAC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: DS3
A Loopback Due to FEAC Command DS-3 condition occurs when a DS3XM-6, DS3XM-12, DS3-12E, or DS3/EC1-48 port loopback signal is received in C-bit framing mode from the far-end node because of an FEAC command. An FEAC command is often used with loopbacks. LPBKDS3FEAC is only reported by these DS cards. DS3XM-6, DS3XM-12, and DS3/EC1-48 cards generate and report FEAC alarms or conditions, but a DS3-12E card only reports FEAC alarms or conditions.
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Note LPBKDS3FEAC is an informational condition and does not require troubleshooting.
Clear the LPBKDS3FEAC Condition
Step 1
Step 2
Step 3
Step 4
In node view, double-click the DS-3 card to open the card view.
Click the Maintenance > DS3 tabs.
Click the cell for the port in the Send Code column and click No Code from the drop-down list.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.224 LPBKDS3FEAC-CMD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
2-162
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.225 LPBKFACILITY (CE1000, CE100T)
SONET Logical Object: DS3
The DS-3 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-3 FEAC loopback on DS3XM-6, DS3XM-12, or DS3/EC1-48 cards. For more information about
FEAC loopbacks, see the
“1.3 Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With
FEAC Loopbacks” section on page 1-45 .
Note LPBKDS3FEAC-CMD is an informational condition and does not require troubleshooting.
2.7.225 LPBKFACILITY (CE1000, CE100T)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: CE1000, CE100T
A Loopback Facility condition on a CE-100T-8 port occurs when a software facility (line) loopback is active for a port on the card.
Note For information about troubleshooting Ethernet circuits with loopbacks, refer to the
“1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks” section on page 1-68
.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the LPBKFACILITY (CE1000, CE100T) Condition
Step 1
Step 2
Complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.226 LPBKFACILITY (DS1, DS3)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3
A Loopback Facility condition on a DS-1 or DS-3 port occurs when a software facility (line) loopback is active for the reporting DS3XM-6 card, DS3XM-12 card, a DS1/E1-56 card operating in All DS1 mode, or a DS3/EC1-48 card.
For information about troubleshooting electrical circuits with loopbacks, refer to the
“1.2 Troubleshooting Electrical Circuit Paths With Loopbacks” section on page 1-9 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-163
Chapter 2 Alarm Troubleshooting
2.7.227 LPBKFACILITY (E1)
Note CTC permits loopbacks to be performed on an in-service (IS) circuit. Performing a loopback is
Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the
, or
.
Note
ONS 15454 DS-3 terminal (inward) loopbacks do not transmit an “AIS” alarm, page 2-34
, in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback if desired.
Clear the LPBKFACILITY (DS1, DS3) Condition
Step 1
Step 2
Complete the “Clear a DS3XM-6, DS3XM-12, or DS3E-12 Card Loopback Circuit” procedure on page 2-269
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.227 LPBKFACILITY (E1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: E1
A Loopback Facility on an E1 port condition occurs when a software facility (line) loopback is active for a DS1/E1-56 card port operating in All E1 mode.
For information about troubleshooting electrical circuits with loopbacks, refer to the
“1.2 Troubleshooting Electrical Circuit Paths With Loopbacks” section on page 1-9
.
Note CTC permits loopbacks to be performed on an in-service (IS) circuit. Performing a loopback is
Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the
LPBKFACILITY condition can be accompanied by a more serious alarms such as LOS.
Note E1 facility (line) loopbacks transmit an AIS in the direction away from the loopback, but this is provisionable.
Clear the LPBKFACILITY (E1) Condition
Step 1
Complete the “Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270 .
2-164
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.228 LPBKFACILITY (EC1)
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.228 LPBKFACILITY (EC1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EC1
A Loopback Facility condition on an EC-1 port occurs when a software facility (line) loopback is active for a port on the reporting EC1/EC1-12 or DS3/EC1-48 card.
For information about troubleshooting electrical circuits with loopbacks, refer to the
“1.2 Troubleshooting Electrical Circuit Paths With Loopbacks” section on page 1-9 .
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Clear the LPBKFACILITY (EC1) Condition
Step 1
Step 2
Complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.229 LPBKFACILITY (ESCON)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.230 LPBKFACILITY (FC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.231 LPBKFACILITY (FCMR)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: FCMR
A Loopback Facility for FCMR condition occurs when a facility loopback is provisioned on an
FC_MR-4 card.
FC_MR Circuit Paths With Loopbacks” section on page 1-86 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-165
Chapter 2 Alarm Troubleshooting
2.7.232 LPBKFACILITY (G1000)
Clear the LPBKFACILITY (FCMR) Condition
Step 1
Step 2
Complete the “Clear an MXP, TXP, or FC_MR-4 Card Loopback Circuit” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.232 LPBKFACILITY (G1000)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: G1000
A Loopback Facility condition for the G1000 object occurs when a software facility (line) loopback is active for a port on the reporting G-Series Ethernet card.
For information about troubleshooting Ethernet circuits with loopbacks, refer to the
“1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks” section on page 1-68 .
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the LPBKFACILITY (G1000) Condition
Step 1
Step 2
Complete the “Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.233 LPBKFACILITY (GE)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.234 LPBKFACILITY (ISC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-166
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.235 LPBKFACILITY (OCN)
2.7.235 LPBKFACILITY (OCN)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
A Loopback Facility condition for an OC-N port occurs when a software facility (line) loopback is active for a port on the reporting OC-N card.
For information about troubleshooting optical circuits with loopbacks, refer to the
Optical Circuit Paths With Loopbacks” section on page 1-47 .
Note OC-3 facility loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted to the loopback is provided.
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Caution Before performing a facility (line) loopback on an OC-N card, ensure that the card contains at least two
DCC paths to the node where the card is installed. A second DCC path provides a nonlooped path to log into the node after the loopback is applied, thus enabling you to remove the facility loopback. Ensuring a second DCC is not necessary if you are directly connected to the ONS 15454 containing the loopback
OC-N.
Clear the LPBKFACILITY (OCN) Condition
Step 1
Step 2
Complete the
“Clear an OC-N Card Facility or Terminal Loopback Circuit” procedure on page 2-268
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.236 LPBKFACILITY (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.237 LPBKTERMINAL (CE1000, CE100T)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: CE1000, CE100T
A Loopback Terminal condition on a CE-100T-8 port occurs when a software terminal loopback is active for a port on the card.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-167
Chapter 2 Alarm Troubleshooting
2.7.238 LPBKTERMINAL (DS1, DS3)
Note For information about troubleshooting Ethernet circuits with loopbacks, refer to the
“1.5 Troubleshooting Ethernet Circuit Paths With Loopbacks” section on page 1-68 .
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the LPBKTERMINAL (CE1000, CE100T) Condition
Step 1
Step 2
Complete the “Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.238 LPBKTERMINAL (DS1, DS3)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3
A Loopback Terminal condition for a DS-1 or DS-3 occurs when a software terminal (inward) loopback is active for a DS1 or DS3 port on the reporting DS3XM-6, DS3XM-12, or DS3/EC1-48 card. DS-1 and
DS-3 terminal loopbacks do not typically return an AIS signal, but you can provision one for the
DS3/EC1-48 card.
For information about troubleshooting electrical circuits with loopbacks, refer to the
.
Clear the LPBKTERMINAL (DS1, DS3) Condition
Step 1
Step 2
Complete the “Clear a DS3XM-6, DS3XM-12, or DS3E-12 Card Loopback Circuit” procedure on page 2-269
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.239 LPBKTERMINAL (E1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: E1
A Loopback Terminal condition for an E-1 signal on a DS1/E1-56 card occurs when the card is operating in All E1 mode and a software terminal (inward) loopback is active for a port.
2-168
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.240 LPBKTERMINAL (EC1)
For information about troubleshooting electrical circuits with loopbacks, refer to the
Clear the LPBKTERMINAL (E1) Condition
Step 1
Step 2
Complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.240 LPBKTERMINAL (EC1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EC1
A Loopback Terminal condition on an EC-1 signal occurs when a software terminal (inward) loopback is active for a port on the reporting EC1/EC1-12 or DS3/EC1-48 card.
For information about troubleshooting electrical circuits with loopbacks, refer to the
“1.2 Troubleshooting Electrical Circuit Paths With Loopbacks” section on page 1-9 .
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Clear the LPBKTERMINAL (EC1) Condition
Step 1
Step 2
Complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.241 LPBKTERMINAL (ESCON)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.242 LPBKTERMINAL (FC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-169
Chapter 2 Alarm Troubleshooting
2.7.243 LPBKTERMINAL (FCMR)
2.7.243 LPBKTERMINAL (FCMR)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: FCMR
A Loopback Terminal for FCMR condition occurs when a terminal loopback is provisioned on an
FC_MR-4 card.
For information about troubleshooting these circuits with loopbacks, refer to the
FC_MR Circuit Paths With Loopbacks” section on page 1-86
.
Clear the LPBKTERMINAL (FCMR) Condition
Step 1
Step 2
Complete the “Clear an MXP, TXP, or FC_MR-4 Card Loopback Circuit” procedure on page 2-270
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.244 LPBKTERMINAL (G1000)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: G1000
A Loopback Terminal condition for the G1000 occurs when a software terminal (inward) loopback is active for a port on the reporting G-Series Ethernet card.
When a port in terminal (inward) loopback, its outgoing signal is redirected into the receive direction on the same port, and the externally received signal is ignored. On the G1000-4 card, the outgoing signal is not transmitted; it is only redirected in the receive direction.
For more information about troubleshooting Ethernet circuits, refer to the
Ethernet Circuit Paths With Loopbacks” section on page 1-68 .
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the LPBKTERMINAL (G1000) Condition
Step 1
Step 2
Complete the “Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-170
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.245 LPBKTERMINAL (GE)
2.7.245 LPBKTERMINAL (GE)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.246 LPBKTERMINAL (ISC)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.247 LPBKTERMINAL (OCN)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
A Loopback Terminal condition for an OC-N port occurs when a software terminal (inward) loopback is active for a port on the reporting card.
Note OC-N terminal loopbacks do not typically return an AIS.
Note Performing a loopback on an in-service circuit is Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the LPBKTERMINAL condition can also be accompanied by a more serious alarm such as LOS.
For information about troubleshooting circuits, refer to the loopback procedures in
Clear the LPBKTERMINAL (OCN) Condition
Step 1
Step 2
Complete the
“Clear an OC-N Card Facility or Terminal Loopback Circuit” procedure on page 2-268
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.248 LPBKTERMINAL (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.249 LWBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-171
Chapter 2 Alarm Troubleshooting
2.7.250 MAN-REQ
SONET Logical Object: PWR
The Low Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage falls below the low power threshold. This threshold, with a default value of –44 VDC, is user-provisionable.
The alarm remains raised until the voltage remains above the threshold for 120 seconds. (For information about changing this threshold, refer to the “Turn Up Node” chapter in the Cisco ONS 15454
Procedure Guide .
Clear the LWBATVG Alarm
Step 1
Step 2
The problem is external to the ONS 15454. Troubleshoot the power source supplying the battery leads.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.250 MAN-REQ
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, ML1000, ML100T, MLFX, STSMON, VT-MON
The Manual Switch Request condition occurs on a SONET entity when a user initiates a Manual switch request on an OC-N port. Clearing the Manual switch clears the MAN-REQ condition. You do not need to clear the switch if you want the Manual switch to remain.
MAN-REQ is raised for an IEEE 802.17b-based RPR span if the manual switch was requested in the
Cisco IOS CLI with the “rpr-ieee protection request manual-switch {east | west}” command. It clears from the IEEE 802.17b-based RPR span when you remove the switch in the CLI. For the RPR-IEEE,
MAN-REQ suppresses
WTR, page 251 . This condition is suppressed by the
following alarms:
•
•
•
Clear the MAN-REQ Condition
Step 1
Step 2
Step 3
If the condition is raised against a SONET entity, complete the
Command” procedure on page 2-255
.
If the condition is raised on an IEEE 802.17b-based RPR span, enter the following CLI command in
RPR-IEEE interface configuration mode: router(config-if)#no rpr-ieee protection request manual-switch {east | west}
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-172
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.251 MANRESET
2.7.251 MANRESET
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A User-Initiated Manual Reset condition occurs when you right-click a card in CTC and choose Reset.
Resets performed during a software upgrade also prompt the condition. The MANRESET condition clears automatically when the card finishes resetting.
Note MANRESET is an informational condition and does not require troubleshooting.
2.7.252 MANSWTOINT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
The Manual Switch To Internal Clock condition occurs when the NE timing source is manually switched to an internal timing source.
Note MANSWTOINT is an informational condition and does not require troubleshooting.
2.7.253 MANSWTOPRI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary timing source.
Note MANSWTOPRI is an informational condition and does not require troubleshooting.
2.7.254 MANSWTOSEC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to a second timing source.
Note MANSWTOSEC is an informational condition and does not require troubleshooting.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-173
Chapter 2 Alarm Troubleshooting
2.7.255 MANSWTOTHIRD
2.7.255 MANSWTOTHIRD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Manual Switch To Third Reference condition occurs when the NE timing source is manually switched to a third timing source.
Note MANSWTOTHIRD is an informational condition and does not require troubleshooting.
2.7.256 MANUAL-REQ-RING
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on BLSR rings to switch from working to protect or protect to working. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the MANUAL RING command originated is marked with an “M” on the network view detailed circuit map.
Clear the MANUAL-REQ-RING Condition
Step 1
Step 2
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.257 MANUAL-REQ-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
The Manual Switch Request on Ring condition occurs on BLSRs when a user initiates a Manual Span command to move BLSR traffic from a working span to a protect span. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the MANUAL SPAN command was applied is marked with an “M” on the network view detailed circuit map.
Clear the MANUAL-REQ-SPAN Condition
Step 1
Complete the “Clear a BLSR External Switching Command” procedure on page 2-262 .
2-174
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.258 MAX-STATIONS
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.258 MAX-STATIONS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The Maximum IEEE 802.17b-based RPR Station Number Exceeded alarm can be raised by all ML card stations on a ring when the maximum quantity of stations, 255, is exceeded. This excess causes the
IEEE 802.17b-based RPR scheme—and traffic—to break down.
IEEE 802.17b-based RPR messaging uses time-to-live (TTL), an 8-bit value. The maximum value these
8 bits (one byte) can have is 255. As a message travels (or hops) from station to station, the TTL is decremented by each station. Thus one station cannot communicate with another station more than 255 hops away.
If you are creating a large ring (more than 127 nodes), the MAX-STATIONS alarm might be raised until the ring is closed and stable.
MAX-STATIONS does not suppress any other alarms. However, this alarm is suppressed by
.
Clear the MAX-STATIONS Alarm
Step 1
Step 2
Remove the extra stations from the ring to clear this alarm in all other stations and to restore traffic in the ring. For procedures to add or remove IEEE 802.17b-based RPR stations, refer to the Ethernet Card
Software Feature and Configuration Guide for the Cisco ONS 15454 SDH, ONS 15454, and ONS 15327,
Release 7.x .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.259 MEA (AIP)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: AIP
If the Mismatch of Equipment Attributes (MEA) alarm is reported against the AIP, the fuse in the AIP board blew or is missing. The MEA alarm also occurs when an old AIP board with a 2-A fuse is installed in a newer ANSI 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD).
Clear the MEA (AIP) Alarm
Step 1 Complete the
“Replace the Alarm Interface Panel” procedure on page 2-274
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-175
Chapter 2 Alarm Troubleshooting
2.7.260 MEA (BIC)
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.260 MEA (BIC)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: BIC
The Missing Equipment Attributes alarm for the backplane interface connector (BIC) indicates a compatibility issue in using high-density DS-3 cards with universal backplane interface connectors
(UBIC) and an older shelf backplane. The backplane on the high-density shelf assembly, 15454-SA-HD, is compatible with the UBIC with horizontal connectors (UBIC-H) and UBIC with vertical connectors
(UBIC-V) that the high-density EC-1, DS-1, and DS-3 electrical connections require. The MEA alarm is raised if you attempt to install a high-density card in Slot 4, 5, 6, 12, 13, or 14 in a shelf assembly with an older, incompatible backplane. The card is not usable in this case. It is also raised if you attempt to use an older BIC (also known as electrical interface assemblies [EIAs]) with the newer shelf assembly.
Clear the MEA (BIC) Alarm
Step 1 Click the Provisioning > Inventory tabs to determine your backplane model. If the backplane is not a
the BICs that are compatible with various backplanes.
Table 2-18 BIC Compatibility Matrix
BIC Type
BICs that work with the newer and older backplanes
New HD BICs that work only with the new backplanes
Part No.
MANUF_EQPT_ID_BIC_A_SMB_HD_BP
MANUF_EQPT_ID_BIC_B_SMB_HD_BP
MANUF_EQPT_ID_BIC_A_BNC_24_HD_BP
MANUF_EQPT_ID_BIC_A_BNC_48_HD_BP
MANUF_EQPT_ID_BIC_B_SMB
MANUF_EQPT_ID_BIC_B_SMB_ALT
MANUF_EQPT_ID_BIC_B_BNC_24
MANUF_EQPT_ID_BIC_B_BNC_48
MANUF_EQPT_ID_BIC_A_UNIV_VERT
MANUF_EQPT_ID_BIC_B_UNIV_VERT
MANUF_EQPT_ID_BIC_A_UNIV_HORIZ
MANUF_EQPT_ID_BIC_B_UNIV_HORIZ
MANUF_EQPT_ID_BIC_A_MINI_BNC_HD_BP
MANUF_EQPT_ID_BIC_B_MINI_BNC_HD_BP
2-176
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.261 MEA (EQPT)
Table 2-18 BIC Compatibility Matrix (continued)
BIC Type
High-density BICs that work only with
15454-SA-HD
Part No.
MANUF_EQPT_ID_BIC_A_SMB
MANUF_EQPT_ID_BIC_A_SMB_ALT
MANUF_EQPT_ID_BIC_A_BNC_24
MANUF_EQPT_ID_BIC_A_BNC_48
Step 2 If you determine that your BIC type and backplane are compatible despite the MEA alarm, or if the alarm does not clear after you resolve the incompatibilities, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.261 MEA (EQPT)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The MEA alarm for equipment is reported against a card slot when the physical card inserted into a slot does not match the card type that is provisioned for that slot in CTC. The alarm also occurs when certain cards introduced in Release 3.1 or later are inserted into an older shelf assembly or when older Ethernet cards (E1000-2 and E100T-12) are used in a newer 10-Gbps-compatible shelf assembly.
Removing the incompatible cards clears the alarm.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Note If an OC3-8 card is installed in Slot 5 to 6 and Slot 12 to 13, it does not appear in CTC and raises an
MEA.
Clear the MEA (EQPT) Alarm
Step 1
Step 2
Physically verify the type of card that is installed in the slot reporting the MEA alarm. In node view, click the Inventory tab and compare it to the actual installed card.
Determine whether the ONS 15454 shelf assembly is a newer 10-Gbps-compatible shelf assembly
(15454-SA-ANSI or 15454-SA-HD) or an earlier shelf assembly. Under the HW Part # column, if the part number is 800-19857-XX or 800-19856-XX, then you have a 15454-SA-ANSI shelf. If the part number is 800-24848-XX, then you have a 15454-SA-HD shelf. If the number is not one of those listed above, then you are using an earlier shelf assembly.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-177
Chapter 2 Alarm Troubleshooting
2.7.261 MEA (EQPT)
Step 3
Note On the 15454-SA-HD (P/N: 800-24848), 15454-SA-NEBS3E, 15454-SA-NEBS3, and
15454-SA-R1 (P/N: 800-07149) shelves, the AIP cover is clear plastic. On the 15454-SA-ANSI shelf (P/N: 800-19857), the AIP cover is metal.
Verify the type of card that sits in the slot reported in the object column of the MEA row on the Alarms window by reading the name at the top of the card faceplate.
• If you have a newer 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD) and the card reporting the alarm is not an E1000-2 or E100T-12, proceed to
.
• If you have a newer 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD) and the card reporting the alarm is an E1000-2 or E100T-12, then that version of the Ethernet card is incompatible and must be removed. Proceed to
Note The E1000-2-G and E100T-G cards are compatible with the newer ANSI
10-Gbps-compatible shelf assembly and are the functional equivalent of the older, noncompatible E1000-2 and E100T-12 cards. E1000-2-G and E100T-G cards can be used as replacements for E1000-2 and E100T-12 cards in a 10-Gbps-compatible shelf assembly.
Step 4
Step 5
• If you have an older shelf assembly and the card reporting the alarm is not a card introduced in
Release 3.1 or later, which includes the OC-192, E1000-2-G, E100T-G, or OC-48 any slot (AS),
.
• If you have an older shelf assembly and the card reporting the alarm is a card introduced in Release
3.1 or later, which includes the OC-192, E1000-2-G, E100T-G, or OC-48 any slot (AS), the reporting card is incompatible with the shelf assembly and must be removed Proceed to
.
If you prefer the card type depicted by CTC, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If you prefer the card that physically occupies the slot but the card is not in service, does not have circuits mapped to it, and is not part of a protection group, place 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.
Note If the card is in service, does have circuits mapped to it, is paired in a working protection scheme, has DCC communications turned on, or is used as a timing reference, CTC does not allow you to delete the card.
Step 6 If any ports on the card are in service, place them out of service (OOS,MT):
Caution Before placing ports out of service, ensure that live traffic is not present.
Step 7 c.
d.
a.
b.
Double-click the reporting card to open the card view.
Click the Provisioning tab.
Click the admin state of any in-service ports.
Choose OOS,MT to take the ports out of service.
If a circuit has been mapped to the card, complete the
“Delete a Circuit” procedure on page 2-268 .
2-178
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.262 MEA (FAN)
Caution Before deleting the circuit, ensure that live traffic is not present.
Step 8
Step 9
Step 10
Step 11
If the card is paired in a protection scheme, delete the protection group: a.
b.
Click the Provisioning > Protection tabs.
Choose the protection group of the reporting card.
c.
Click Delete .
Right-click the card reporting the alarm.
Choose Delete .
The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.262 MEA (FAN)
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: FAN
The MEA alarm is reported against the fan-tray assembly when a newer fan-tray assembly (15454-FTA3) with a 5-A fuse is used with an older shelf assembly or when an older fan-tray assembly with a 2-A fuse is used with a newer 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD) that contains cards introduced in Release 3.1 or later. If a 10-Gbps-compatible shelf assembly contains only cards introduced before Release 3.1, then an older fan-tray assembly (15454-FTA-2) can be used and does not report an MEA alarm.
Clear the MEA (FAN) Alarm
Step 1
Step 2
Step 3
Determine whether the shelf assembly is a newer 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD) or an earlier shelf assembly. In node view, click the Inventory tab.
Under the HW Part # column, if the part number is 800-19857-XX or 800-19856-XX, then you have a
15454-SA-ANSI shelf. If the part number is 800-24848-XX, you have a 15454-SA-HD shelf.
Under the HW Part # column, if the number is not one of those listed above, then you are using an earlier shelf assembly.
If you have a 10-Gbps-compatible shelf assembly (15454-SA-ANSI or 15454-SA-HD), the alarm indicates that an older incompatible fan-tray assembly is installed in the shelf assembly. Obtain a newer fan-tray assembly (15454-FTA3) with a 5-A fuse and complete the
“Replace the Fan-Tray Assembly” procedure on page 2-273
.
If you are using an earlier shelf assembly, the alarm indicates that you are using a newer fan-tray assembly (15454-FTA3), which is incompatible with the earlier version of the shelf assembly. Obtain an earlier version of the fan-tray assembly (15454-FTA2) and complete the
Assembly” procedure on page 2-273 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-179
Chapter 2 Alarm Troubleshooting
2.7.263 MEA (PPM)
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.263 MEA (PPM)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.264 MEM-GONE
Default Severity: Major (MJ), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC2/TCC2P. The TCC2/TCC2P cards which exceed the memory capacity reboot to avoid failure of card operations.
Note The alarm does not require user intervention. The MEM-LOW alarm always preceeds the MEM-GONE alarm.
2.7.265 MEM-LOW
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Free Memory of Card Almost Gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the TCC2/TCC2P. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the card is exceeded, CTC ceases to function.
Note The alarm does not require user intervention. If the alarm does not clear, log into the Technical Support
Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.266 MFGMEM
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: AICI-AEP, AICI-AIE, AIP, BPLANE, FAN
DWDM Logical Object: PPM
The Manufacturing Data Memory Failure alarm occurs when the EEPROM fails on a card or component, or when the TCC2/TCC2P cannot read this memory. EEPROM stores manufacturing data that a system
TCC2/TCC2P uses to determine system compatibility and shelf inventory status. Unavailability of this
2-180
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.267 NO-CONFIG information can cause less-significant problems. The AIP EEPROM also stores the system MAC address. If the MFGMEM alarm indicates EEPROM failure on these panels, IP connectivity could be disrupted and the system icon is grayed out in CTC network view.
Tip When you lose LAN connectivity with an ONS 15454 due to an MFGMEM alarm on the AIP, you can reestablish node management by disconnecting the Ethernet cable from the panel and connecting it to the active TCC2/TCC2P LAN port.
Clear the MFGMEM Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Complete the
“Reset an Active TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263
.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265 . If the Cisco TAC
technician tells you to remove the card and reinstall a new one, complete the
Traffic Card” procedure on page 2-266
.
If the MFGMEM alarm continues to report after replacing the TCC2/TCC2Ps, the problem lies with the
EEPROM.
If the MFGMEM is reported from the fan-tray assembly, obtain a fan-tray assembly and complete the
“Replace the Fan-Tray Assembly” procedure on page 2-273 .
If the MFGMEM is reported from the AIP, the backplane, or the alarm persists after the fan-tray assembly is replaced, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.267 NO-CONFIG
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The No Startup Configuration condition applies to ML-Series Ethernet cards and occurs when no startup configuration file has been downloaded to the TCC2/TCC2P, whether or not you preprovision the card slot. This alarm can be expected during provisioning. When the startup configuration file is copied to the active TCC2/TCC2P, the alarm clears.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Clear the NO-CONFIG Condition
Step 1 Create a startup configuration for the card in Cisco IOS.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-181
Chapter 2 Alarm Troubleshooting
2.7.268 NOT-AUTHENTICATED
Step 2
Step 3
Step 4
Follow the card provisioning instructions in the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Upload the configuration file to the TCC2/TCC2P: a.
In node view, right-click the ML-Series card graphic.
b.
c.
Choose IOS Startup Config from the shortcut menu.
Click Local > TCC and navigate to the file location.
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.268 NOT-AUTHENTICATED
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: SYSTEM
The NOT-AUTHENTICATED alarm is raised by CTC (not by the NE) when CTC fails to log into a node.
This alarm only appears in CTC where the login failure occurred. This alarm differs from the
“INTRUSION-PSWD” alarm on page 2-126 because INTRUSION-PSWD occurs when a user exceeds
the login failures threshold.
Note NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.
2.7.269 OCHNC-INC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.270 OCHTERM-INC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.271 ODUK-1-AIS-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-182
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.272 ODUK-2-AIS-PM
2.7.272 ODUK-2-AIS-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.273 ODUK-3-AIS-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.274 ODUK-4-AIS-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.275 ODUK-AIS-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.276 ODUK-BDI-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.277 ODUK-LCK-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.278 ODUK-OCI-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.279 ODUK-SD-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-183
Chapter 2 Alarm Troubleshooting
2.7.280 ODUK-SF-PM
2.7.280 ODUK-SF-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.281 ODUK-TIM-PM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.282 OOU-TPT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSTRM, VT-TERM
The Out of Use Transport Failure alarm is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) This condition is raised when a member circuit in a VCAT is unused, such as when it is removed by
SW-LCAS. It occurs in conjunction with the
“VCG-DEG” condition on page 2-248
.
Clear the OOT-TPT Condition
Step 1
Step 2
Complete the
“Clear the VCG-DEG Condition” procedure on page 2-248
. Clearing that condition clears this condition as well.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.283 OPEN-SLOT
Default Severity: Not Alarmed (NA)
Logical Object: EQPT
The Open Slot condition indicates that there is an open slot in the system shelf. Slot covers assist with airflow and cooling.
Clear the OPEN-SLOT Condition
Step 1
Step 2
To install a slot cover and clear this condition, refer to the procedures located in the “Install Cards and
Fiber-Optic Cable” chapter of the Cisco ONS 15454 Procedure Guide .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-184
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.284 OPTNTWMIS
2.7.284 OPTNTWMIS
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.285 OPWR-HDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.286 OPWR-HFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.287 OPWR-LDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.288 OPWR-LFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.289 OSRION
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.290 OTUK-AIS
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.291 OTUK-BDI
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-185
Chapter 2 Alarm Troubleshooting
2.7.292 OTUK-IAE
2.7.292 OTUK-IAE
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.293 OTUK-LOF
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.294 OTUK-SD
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.295 OTUK-SF
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.296 OTUK-TIM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.297 OUT-OF-SYNC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.298 PARAM-MISM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.299 PDI-P
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
2-186
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.299 PDI-P
PDI-P is a set of application-specific codes indicating a signal label mismatch failure (SLMF) in the
ONS 15454 STS path overhead. The condition indicates to downstream equipment that there is a defect in one or more of the directly mapped payloads contained in that STS synchronous payload envelope
(SPE). For example, the mismatch could occur in the overhead to the path selector in a downstream node configured as part of a path protection. The PDI-P codes appear in the STS Signal Label (C2 byte).
An SLMF often occurs when the payload (for example, ATM) does not match what the signal label is reporting. The
often accompanies a PDI-P condition. If the PDI-P is the only condition reported with the AIS, clearing PDI-P clears the AIS. PDI-P can also occur during an upgrade, but usually clears itself and is not a valid condition.
A PDI-P condition reported on an OC-N port supporting a G1000-4 card circuit could result from the end-to-end Ethernet link integrity feature of the G1000-4 card. If the link integrity is the cause of the path defect, it is typically accompanied by the
“TPTFAIL (G1000)” alarm on page 2-241 or the
“CARLOSS (G1000)” alarm on page 2-60
reported against one or both Ethernet ports terminating the circuit. If this is the case, clear the TPTFAIL and CARLOSS alarms to resolve the PDI-P condition.
A PDI-P condition reported on an OC-N port supporting an ML-Series card circuit could result from the end-to-end Ethernet link integrity feature of the ML-Series card. If the link integrity is the cause, it is
typically accompanied by the “TPTFAIL (ML100T, ML1000, MLFX)” alarm on page 2-242
reported against one or both POS ports terminating the circuit. If TPTFAIL is reported against one or both of the
POS ports, troubleshooting the accompanying alarm clears the PDI-P condition. Refer to the Ethernet
Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and
Cisco ONS 15327 for more information about ML-Series cards.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the PDI-P Condition
Step 1 Verify that all circuits terminating in the reporting card are DISCOVERED: a.
Click the Circuits tab.
b.
Verify that the Status column lists the circuit as active.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-187
Chapter 2 Alarm Troubleshooting
2.7.300 PEER-NORESPONSE
Step 2 c.
If the Status column lists the circuit as PARTIAL, wait 10 minutes for the ONS 15454 to initialize fully. If the PARTIAL status does not change after full initialization, log into the Technical Support
Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a
Service-Affecting (SA) problem 1 800 553-2447.
After determining that the circuit is DISCOVERED, ensure that the signal source to the card reporting the alarm is working.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 3 If traffic is affected, complete the
“Delete a Circuit” procedure on page 2-268 .
Caution Deleting a circuit can affect existing traffic.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Recreate the circuit with the correct circuit size. Refer to the “Create Circuits and VT Tunnels” chapter in the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.
If circuit deletion and re-creation does not clear the condition, verify that there is no problem stemming from the far-end OC-N card providing STS payload to the reporting card.
If the condition does not clear, confirm the cross-connect between the OC-N card and the reporting card.
If the condition does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure
Guide .
If the condition does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the optical/electrical cards.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.300 PEER-NORESPONSE
Default Severity: Major (MJ), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The switch agent raises a Peer Card Not Responding alarm if either traffic card in a protection group does not receive a response to the peer status request message. PEER-NORESPONSE is a software failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure between peer cards.
Clear the PEER-NORESPONSE Alarm
Step 1
Step 2
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
for the reporting card. For the LED behavior, see the
“2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252 .
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the
LED appearance: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
2-188
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.301 PLM-P
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a service-affecting (SA) problem.
2.7.301 PLM-P
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: STSMON, STSTRM
A Payload Label Mismatch Path alarm indicates that signal does not match its label. The condition is indicated by a problematic C2 byte value in the SONET path overhead. The alarm is raised if all of the following conditions are met:
• The received C2 byte is not 0x00 (unequipped).
•
•
•
•
The received C2 byte is not a PDI value.
The received C2 does not match the expected C2.
The expected C2 byte is not 0x01 (equipped, unspecified).
The received C2 byte is not 0x01 (equipped, unspecified).
For example, on nodes equipped with CTC Software R4.1 and earlier, this alarm could occur when you have a DS3XM-6 card connected to a DS-3 card instead of a DS-1 card. The DS3XM-6 card expects a
C2 label byte value of 01. A DS-1 card transmits this value, but a DS-3 card transmits a value of 04. The mismatch between the sent and expected values causes the PLM-P alarm.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 .
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the PLM-P Alarm
Step 1 Complete the
“Clear the PDI-P Condition” procedure on page 2-187
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-189
Chapter 2 Alarm Troubleshooting
2.7.302 PLM-V
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.302 PLM-V
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: VT-TERM
A Payload Label Mismatch VT Layer alarm indicates that the content of the V5 byte in the SONET overhead is inconsistent or invalid. PLM-V occurs when ONS 15454s interoperate with equipment that performs bit-synchronous mapping for DS-1 signal. The ONS 15454 uses asynchronous mapping.
Clear the PLM-V Alarm
Step 1
Step 2
Step 3
Verify that your signal source matches the signal allowed by the traffic card. For example, the traffic card does not allow VT6 or VT9 mapping.
If the signal source matches the card, verify that the SONET VT path originator is sending the correct
VT label value. You can find the SONET VT path originator using circuit provisioning steps.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.303 PMI
For more information about the PMI condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide.
2.7.304 PORT-ADD-PWR-DEG-HIGH
For more information about the PORT-ADD-PWR-DEG-HIGH alarm, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
2.7.305 PORT-ADD-PWR-DEG-LOW
For more information about the PORT-ADD-PWR-DEG-LOW alarm, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
2-190
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.306 PORT-ADD-PWR-FAIL-HIGH
2.7.306 PORT-ADD-PWR-FAIL-HIGH
For more information about the PORT-ADD-PWR-FAIL-HIGH alarm, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
2.7.307 PORT-ADD-PWR-FAIL-LOW
For more information about the PORT-ADD-PWR-FAIL-LOW alarm, refer to the “Alarm
Troubleshooting” chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
2.7.308 PORT-FAIL
For more information about the PORT-FAIL alarm, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide.
2.7.309 PORT-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE-MR-10, ML-MR-10, FC_MR-4
The Pluggable PORT-MISMATCH alarm applies to FC_MR-4, ML-MR-10, and CE-MR-10 Ethernet cards.
For the ML-MR-10 and CE-MR-10 cards the alarm indicates either of the following:
• The provisioned payload, speed, or duplex configured on the port does not match that of the SFP plugged into the port.
• A non-supported SFP is plugged into the port.
For the FC_MR-4 card the alarm indicates that a non-supported GBIC is plugged into the port.
Clear the PORT-MISMATCH Alarm
To clear the alarm on the CE-MR-10 card, either plug-in a supported SFP into the CE-MR-10 port or follow these steps to provision the correct payload, speed, or duplex:
1.
In node view (single-shelf mode) or shelf view (multishelf mode), double-click the CE-MR-10 card to open the card view.
2.
3.
Click the Provisioning > Ether Ports tabs.
Specify correct values in the Expected Speed and Expected Duplex fields to match the SFP configuration.
4.
Click Apply .
To clear the alarm on the FC_MR-4 card, plug-in a supported GBIC into the FC_MR-4 port and follow these steps to provision the media type:
1.
2.
In node view (single-shelf mode) or shelf view (multishelf mode), double-click the FC_MR-4 card graphic to open the card.
Click the Provisioning > Port > General tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-191
Chapter 2 Alarm Troubleshooting
2.7.310 PRC-DUPID
3.
Specify proper payload value in the Media Type field.
4.
Click Apply .
For the CE-MR-10 and FC_MR-10 card, the alarm can also be cleared using TL1 commands. For detailed instructions, refer to the Cisco ONS 15454, Cisco ONS 15600, and Cisco ONS 15310-MA
SONET TL1 Command Guide.
For the ML-MR-10 card, the alarm can be cleared through Cisco IOS commands. For detailed instructions, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide .
If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a
Service-Affecting (SA) problem.
2.7.310 PRC-DUPID
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
The Procedural Error Duplicate Node ID alarm indicates that two identical node IDs exist in the same ring. The ONS 15454 requires each node in the ring to have a unique node ID.
Clear the PRC-DUPID Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Log into a node on the ring.
.
Repeat
Step 2 for all the nodes on the ring.
If two nodes have an identical node ID number, complete the
“Change a BLSR Node ID Number” procedure on page 2-254 so that each node ID is unique.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.311 PROTNA
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Protection Unit Not Available alarm is caused by an OOS protection card when a TCC2/TCC2P or
XC10G card that has been provisioned as part of a protection group is not available. The alarm clears if the device or facility is brought back in service.
2-192
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.312 PROV-MISMATCH
Clear the PROTNA Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If the PROTNA alarm occurs and does not clear, and if it is raised against a controller or cross-connect card, ensure that there is a redundant TCC2/TCC2P installed and provisioned in the chassis.
If the alarm is raised against a line card, verify that the ports have been taken out of service (OOS,MT): a.
In CTC, double-click the reporting card to open the card view (if the card is not an XC10G card).
b.
c.
Click the Provisioning tab.
Click the admin state of any in-service (IS) ports.
d.
Choose OOS,MT to take the ports out of service.
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for the reporting card. For the LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the
LED appearance: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the reporting card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.312 PROV-MISMATCH
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.313 PTIM
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.314 PWR-FAIL-A
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONETLogical Object: EQPT
The Equipment Power Failure at Connector A alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the electrical interface assemblies (EIA),
15454_MRC-12 Multirate card, MRC-2.5G-4 Multirate card, OC192SR1/STM64IO Short Reach and
OC192/STM64 Any Reach cards (also known as OC192-XFP in CTC), OC12 IR/STM4 SH 1310-4 card,
OC3 IR/STM1 SH 1310-8 card or TCC2/TCC2P.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-193
Chapter 2 Alarm Troubleshooting
2.7.315 PWR-FAIL-B
Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment.
This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207
Clear the PWR-FAIL-A Alarm
Step 1 If a single card has reported the alarm, take the following actions depending on the reporting card:
• If the reporting card is an active traffic line port in a 1+1 protection group or part of a path protection, ensure that an APS traffic switch has occurred to move traffic to the protect port.
Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254 for
commonly used traffic-switching procedures.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
•
•
•
If the alarm is reported against an OC-N card, complete the
“Reset a Traffic Card in CTC” procedure on page 2-263
.
If the alarm is reported against a cross-connect card, complete the
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
.
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting card.
If the single card replacement does not clear the alarm, or if multiple cards report the alarm, verify the office power. Refer to the “Install the Shelf and Backplane Cable” chapter in the Cisco ONS 15454
Procedure Guide for procedures. See the
“1.13 Power Supply Problems” section on page 1-142
as necessary.
If the alarm does not clear, reseat the power cable connection to the connector.
If the alarm does not clear, physically replace the power cable connection to the connector.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.315 PWR-FAIL-B
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
2-194
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.316 PWR-FAIL-RET-A
The Equipment Power Failure at Connector B alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the electrical interface assemblies (EIA),
15454_MRC-12 Multirate card, MRC-2.5G-4 Multirate card, OC192SR1/STM64IO Short Reach and
OC192/STM64 Any Reach cards (also known as OC192-XFP in CTC), OC12 IR/STM4 SH 1310-4 card,
OC3 IR/STM1 SH 1310-8 card or TCC2/TCC2P.
Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment.
This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207
Clear the PWR-FAIL-B Alarm
Step 1
Step 2
Complete the
“Clear the PWR-FAIL-A Alarm” procedure on page 2-194 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.316 PWR-FAIL-RET-A
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Equipment Power Failure at Connector A alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the electrical interface assemblies (EIA),
15454_MRC-12 Multirate card, MRC-2.5G-4 Multirate card, OC192SR1/STM64IO Short Reach and
OC192/STM64 Any Reach cards (also known as OC192-XFP in CTC), OC12 IR/STM4 SH 1310-4 card,
OC3 IR/STM1 SH 1310-8 card or TCC2/TCC2P.
Clear the PWR-FAIL-RET-A Alarm
Step 1
Step 2
Complete the
“Clear the PWR-FAIL-A Alarm” procedure on page 2-194 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.317 PWR-FAIL-RET-B
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-195
Chapter 2 Alarm Troubleshooting
2.7.318 RAI
The Equipment Power Failure at Connector B alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the electrical interface assemblies (EIA),
15454_MRC-12 Multirate card, MRC-2.5G-4 Multirate card, OC192SR1/STM64IO Short Reach and
OC192/STM64 Any Reach cards (also known as OC192-XFP in CTC), OC12 IR/STM4 SH 1310-4 card,
OC3 IR/STM1 SH 1310-8 card or TCC2/TCC2P.
Clear the PWR-FAIL-RET-A Alarm
Step 1
Step 2
Complete the “Clear the PWR-FAIL-A Alarm” procedure on page 2-194
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.318 RAI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3, E1
The Remote Alarm Indication condition signifies an end-to-end failure. The error condition is sent from one end of the SONET path to the other. RAI on a DS3XM-6 card indicates that the far-end node is receiving a DS-3 AIS.
Clear the RAI Condition
Step 1
Step 2
Complete the “Clear the AIS Condition” procedure on page 2-35
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.319 RCVR-MISS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: DS1, E1
A Facility Termination Equipment Receiver Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance usually occurs when a receive cable is missing from a DS-1 port, or a possible mismatch of backplane equipment occurs. For example, an SMB connector or a BNC connector could be misconnected to a
DS-1 card.
Note DS-1s are four-wire circuits and need a positive (tip) and negative (ring) connection for both transmit and receive.
2-196
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.320 RESERVED-RATE-EXCEEDED-RINGLET0
Clear the RCVR-MISS Alarm
Step 1 Ensure that the device attached to the DS-1 port is operational.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
If the attachment is good, verify that the cabling is securely connected.
If the cabling is good, verify that the pinouts are correct.
If the pinouts are correct, replace the receive cable.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a service-affecting (SA) problem.
2.7.320 RESERVED-RATE-EXCEEDED-RINGLET0
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The Reserved Bandwidth Exceeds Link Rate on Ringlet Zero alarm is raised by an ML-1000 card if the sum the of reserved bandwidth configured on each station of ringlet 0 is greater then the link rate (circuit bandwidth). The alarm clears when the sum of the reserved bandwidth on each station falls below the link rate. In the case of SW-LCAS or LCAS circuits, the link rate is the working link rate, which will change when members are removed
RESERVED-RATE-EXCEEDED-RINGLET0 does not suppress any alarms, but it is suppressed by
.
Clear the RESERVED-RATE-EXCEEDED-RINGLET0 Alarm
Step 1
Step 2
Step 3
At the CLI command prompt in privileged executive mode, enter the following command: router# show rpr-ieee topology detail
This command’s output shows the configured reserved bandwidth rate from each station.
Reduce the reserved bandwidth on the alarmed station until the error clears. Enter the following CLI command in IEEE 802.17b-based RPR interface configuration mode: router (config-if)# rpr-ieee tx-traffic rate-limit reserved
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a service-affecting (SA) problem.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-197
Chapter 2 Alarm Troubleshooting
2.7.321 RESERVED-RATE-EXCEEDED-RINGLET1
2.7.321 RESERVED-RATE-EXCEEDED-RINGLET1
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The Reserved Bandwidth Exceeds Link Rate on Ringlet One alarm is raised by an ML-1000 card if the sum the of reserved bandwidth configured on each station of ringlet 1 is greater then the link rate (circuit bandwidth). The alarm clears when the sum of the reserved bandwidth on each station falls below the link rate. In the case of SW-LCAS or LCAS circuits, the link rate is the working link rate, which will change when members are removed
RESERVED-RATE-EXCEEDED-RINGLET1 does not suppress any alarms, but it is suppressed by
.
Clear the RESERVED-RATE-EXCEEDED-RINGLET1 Alarm
Step 1
Step 2
Step 3
At the CLI command prompt in privileged executive mode, enter the following command: router# show rpr-ieee topology detail
This command’s output shows the configured reserved bandwidth rate from each station.
Reduce the reserved bandwidth on the alarmed station until the error clears. Enter the following CLI command in IEEE 802.17b-based RPR interface configuration mode: router (config-if)# rpr-ieee tx-traffic rate-limit reserved
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a service-affecting (SA) problem.
2.7.322 RFI
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.323 RFI-L
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: EC1, OCN
DWDM Logical Object: TRUNK
A RFI Line condition occurs when the ONS 15454 detects an RFI in OC-N card SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-L condition in the reporting node. RFI-L indicates that the condition is occurring at the line level.
Clear the RFI-L Condition
Step 1 Log into the node at the far-end node of the reporting ONS 15454.
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-198 November 2009
Chapter 2 Alarm Troubleshooting
2.7.324 RFI-P
Step 2
Step 3
Identify and clear any alarms, particularly the “LOS (OCN)” alarm on page 2-158
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.324 RFI-P
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
The RFI Path condition occurs when the ONS 15454 detects an RFI in the an STS-1 signal 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 terminating node in that path segment.
Clear the RFI-P Condition
Step 1 Verify that the ports are enabled and in service (IS-NR) on the reporting ONS 15454: a.
Confirm that the LED is correctly illuminated on the physical card.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card. b.
c.
d.
e.
To determine whether the OC-N port is in service, double-click the card in CTC to open the card view.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS . Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 2
Step 3
Step 4
To find the path and node failure, verify the integrity of the SONET STS circuit path at each of the intermediate SONET nodes.
Clear alarms in the node with the failure, especially the “UNEQ-P” alarm on page 2-245
or the
“UNEQ-V” alarm on page 2-247 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.325 RFI-V
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: VTMON, VT-TERM
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-199
Chapter 2 Alarm Troubleshooting
2.7.326 RING-ID-MIS
An RFI VT Layer condition occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-V condition in the reporting node. RFI-V indicates that an upstream failure has occurred at the VT layer.
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 “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
If connectors are correctly connected, verify that the DS-N port is active and in service (IS-NR): a.
b.
Confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine whether the OC-N port is in service, double-click the card in CTC to open the card view.
c.
d.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS. If the Admin State column lists the port as
OOS,MT or OOS,DSBLD, click the column and choose IS . Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 4
Step 5
Step 6
Step 7
If the ports are active and in service, use an optical test set to verify that the signal source does not have errors. For specific procedures to use the test set equipment, consult the manufacturer.
If the signal is valid, log into the node at the far-end of the reporting ONS 15454.
Clear alarms in the far-end node, especially the
“UNEQ-P” alarm on page 2-245 or the
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.326 RING-ID-MIS
Default Severity: Major (MJ), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: OSC-RING
The Ring ID Mismatch condition refers to the ring ID in APC. It occurs when a ring name does not match other detectable node ring names, and can cause problems with applications that require data exchange with APC. This alarm is similar to the
“RING-MISMATCH” alarm, page 2-201 , but rather than apply to
BLSDR ring protection, RING-ID-MIS applies to DWDM node discovery within the same network.
2-200
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.327 RING-MISMATCH
Note For more information about APC, refer to the Cisco ONS 15454 DWDM Procedure Guide.
Clear the RING-ID-MIS Alarm
Step 1
Step 2
Complete the
“Clear the RING-MISMATCH Alarm” procedure on page 2-201
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.327 RING-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
A Procedural Error Mismatch Ring alarm occurs when the ring name of the ONS 15454 node that is reporting the alarm does not match the ring name of another node in the BLSR. Nodes connected in a
BLSR must have identical ring names to function. This alarm can occur during BLSR provisioning.
RING-MISMATCH is somewhat similar to RING-ID-MIS, but it applies to BLSR protection discovery instead of DWDM node discovery.
Note For more information about DWDM cards, refer to the Cisco ONS 15454 DWDM Reference Manual .
Clear the RING-MISMATCH Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
In node view, click the Provisioning > BLSR tabs.
Note the name in the Ring Name field.
Log into the next ONS 15454 node in the BLSR.
Complete the
“Identify a BLSR Ring Name or Node ID Number” procedure on page 2-253 .
If the ring name matches the ring name in the reporting node, repeat
Step 4 for the next ONS 15454 in
the BLSR.
Complete the
“Change a BLSR Ring Name” procedure on page 2-253
.
Verify that the ring map is correct.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.328 RING-SW-EAST
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-201
Chapter 2 Alarm Troubleshooting
2.7.329 RING-SW-WEST
SONET Logical Object: OCN
The Ring Switch Is Active East Side condition occurs when a ring switch occurs at the east side of a
BLSR using a Force Ring command. The condition clears when the switch is cleared. RING-SW-EAST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an “F” on the network view detailed circuit map.
Note RING-SW-EAST is an informational condition and does not require troubleshooting.
2.7.329 RING-SW-WEST
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Ring Switch Is Active West Side condition occurs when a ring switch occurs at the west side of a
BLSR using a Force Ring command. The condition clears when the switch is cleared. RING-SW-WEST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an “F” on the network view detailed circuit map.
Note RING-SW-WEST is an informational condition and does not require troubleshooting.
2.7.330 ROLL
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM, VT-MON
The ROLL condition indicates that circuits are being rolled. This is typically carried out to move traffic for a maintenance operation or to perform bandwidth grooming. The condition indicates that a good signal has been received on the roll destination leg, but the roll origination leg has not yet been dropped.
The condition clears when the roll origination leg is dropped.
Note ROLL is an informational condition and does not require troubleshooting.
2.7.331 ROLL-PEND
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM, VT-MON
ROLL-PEND indicates that a roll process has been started, but a good signal has not been received yet by the roll destination leg. This condition can be raised individually by each path in a bulk circuit roll.
The condition clears when a good signal has been received on the roll destination leg.
Note ROLL-PEND is an informational condition and does not require troubleshooting.
2-202
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.332 RPR-PASSTHR
2.7.332 RPR-PASSTHR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: RPRIF
The IEEE 802.17 b-based RPR Interface in Pass-Through Mode condition indicates that an ML card’s
IEEE 802.17 b-based RPR interface is not participating in a ring. Instead, the card is behaving like a passive device that allows the signal to transit but does not manipulate it. Pass-through mode itself is hitless.
You can manually place an ML card into (or out of) pass-through mode using the Cisco IOS CLI command SHUTDOWN (SHUT) for such reasons as adding, removing, or servicing the node. To do so is hitless.
The ML-1000 automatically enters pass-through mode if either of the following conditions is true:
• Redundant interconnect (RI) is configured and the ML card is in primary mode (that is, single traffic queue mode), standby state.
•
RI is configured and the RI interface goes down during a WTR, page 251 , while the ML card is in
secondary mode (that is, dual traffic queue mode) on a Cisco proprietary RPR ring.
Note For GFP and HDLC mode, the ML card shutdown (SHUT) command causes an
sent to the peer. But in IEEE 802.17b-based RPR mode, AIS-P is not inserted toward the peer.
The RPR-PASSTHR condition suppresses the following alarms:
•
•
•
•
•
•
•
•
•
•
RESERVED-RATE-EXCEEDED-RINGLET0, page 197
RESERVED-RATE-EXCEEDED-RINGLET1, page 198
RPR-PROT-CONFIG-MISMATCH, page 206
•
•
If RPR-PASSTHR is raised—meaning that this RPR-IEEE interface is not available—one or more of its peer nodes might raise
RPR-PEER-MISS, page 204 . RPR-PASSTHR does not suppress
.
Clear the RPR-PASSTHR Condition
Step 1 If the ML card was manually configured shut down using the CLI command SHUTDOWN (SHUT), enter the following command at the command prompt: router# no shut
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-203
Chapter 2 Alarm Troubleshooting
2.7.333 RPR-PEER-MISS
Step 2
Step 3
Step 4
Step 5
Step 6
If the card is in pass-through mode due to being in an RI primary mode standby state, either the
IEEE 802.17b-based RPR interface is down or the interconnect interface is down. You must clear the root cause of either problem to clear the pass-through. To trace the root cause problem in the RPR-IEEE interface setup, enter the following CLI command in privileged executive mode: router# show interface rpr-ieee 0
View the command output and locate the RI information line. It displays the name of the monitored interfaces as “monitoring ring interface,” or “monitoring interconnect interface.”
Locate and clear any trouble on the monitored interface. Trouble might be indicated on that interface through previous alarms that occurred before RPR-PASSTHR was raised.
If the card is in pass-through mode while in RI secondary mode when the interconnect fails, pass-through mode should clear automatically in 60 seconds.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.7.333 RPR-PEER-MISS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The IEEE 802.17-based RPR Peer Node Is Missing condition is raised by an ML card when RI is configured on the card, but this station does not detect its peer station in the topology. The condition clears when the peers detect each other.
Clear the RPR-PEER-MISS Condition
Step 1 Determine whether the peer MAC address is properly configured by completing the following steps: a.
Enter the following CLI command in privileged executive mode: router# show interface rpr-ieee 0
This command’s output will include information, similar to the following, about the RPR-IEEE interface raising the condition:
Hardware is RPR-IEEE Channelized SONET, address is 000e.8312.bcf0 (bia 000e.87312.bfc0) b.
Verify that the alarmed interface’s configured peer MAC address is the correct MAC address for the peer card. A card in primary mode need to list the peer MAC address of the card operating in secondary mode; the secondary card needs to list the peer MAC address of the primary card. Peer
MAC address information is contained in the same “show interface rpr-ieee 0” command output. In the following line example, the RPR-IEEE interface raising the alarm is primary; it is in active mode, and its configured peer, the secondary card, is MAC address 000e.8312.b870:
RI: primary,active peer mac 000e.8312.b870
Note The primary and secondary cards do not have to be neighbors on the ring.
2-204
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.334 RPR-PROT-ACTIVE
Step 2
Step 3
Step 4
Step 5
Note If RI is configured, then RI information is displayed in the “show interface rpr 0" output.
To correct the MAC address configuration, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454 SDH, ONS 15454, and ONS 15327, Release 7.x for procedures.
If the condition does not clear, enter the following command in privileged executive mode: router# show rpr-ieee protection
The command output, similar to the following lines, shows whether any protection switches are active:
West Span Failures: none
East Span Failures: none
A protection switch can cause an RPR-PEER-MISS condition. You may also see the
“RPR-PROT-ACTIVE” alarm on page 2-205
raised for a span. Clear any protection issues.
If the condition does not clear, correct any issues on the peer node that would cause it to go into pass-through mode, which can cause the peer to raise RPR-PEER-MISS.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.334 RPR-PROT-ACTIVE
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: RPRIF
The IEEE 802.17b-based RPR Protection is Active condition, raised by the ML card, indicates that ring protection is active and that steering protection as defined in IEEE 802.17b is active.
IEEE 802.17b-based RPR provides hitless protection switching for all protected traffic on a ring. Its steering protection mechanism ensures that each station receives span change information (such as fail or restoration) in time to make protection switching decisions within the 50-millisecond time frame.
The condition clears when steering protection is no longer active.For more information about steering, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454 SDH,
ONS 15454, and ONS 15327, Release 7.x .
This condition is suppressed by
.
Clear the RPR-PROT-ACTIVE Condition
Step 1
Step 2
Locate and clear any service-affecting SONET error that might have caused a protection switch, in turn triggering the RPR-PROT-ACTIVE condition. Clearing the SONET condition will clear
RPR-PROT-ACTIVE.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-205
Chapter 2 Alarm Troubleshooting
2.7.335 RPR-PROT-CONFIG-MISMATCH
2.7.335 RPR-PROT-CONFIG-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The IEEE 802.17b-based RPR Protection Configuration Mismatched alarm is raised by an ML card when it detects that its steering protection scheme is mismatched with other vendors’ equipment configured for wrapping protection. The ONS 15454 does not support IEEE 802.17b’s optional wrapping scheme.
The alarm clears when the other vendor’s equipment configuration is changed to utilize steering protection.
RPR-PROT-CONFIG-MISMATCH is suppressed by
Clear the RPR-PROT-CONFIG-MISMATCH Alarm
Step 1
Step 2
You cannot clear this alarm from the ONS 15454; rather, it is caused by incompatible vendor equipment configuration. See that equipment’s support information to correct the configuration for steering instead of wrapping. This, in turn, will cause RPR-PROT-CONFIG-MISMATCH to clear.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.
2.7.336 RPR-RI-FAIL
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: RPRIF
The IEEE 802.17b-based RPR RI Fail condition is raised by an ML card in primary or secondary mode.
If a card is in primary mode, a Gigabit Ethernet interface can cause an interconnect interface (IC) failure.
(The IC includes the Gigabit Ethernet interface and possibly a port channel interface.) In primary mode,
RPR-RI-FAIL can also be raised in response to a downed ring interface. In secondary mode, the only possible cause of this condition is IC failure.
The alarm clears when the IEEE 802.17b-based RPR interface returns to Init modes and faults, if present, are cleared. RPR-RI-FAIL is suppressed by
.
Clear the RPR-RI-FAIL Condition
Step 1
Step 2
Step 3
If the card is in primary mode, enter the following command at the CLI in privileged executive mode: router# show interface rpr-ieee 0
The RI information line displays the name of the monitored interfaces and says either “monitoring ring interface,” or “monitoring interconnect interface.”
Determine why the monitored interface is down. It can occur because the ring interface has been shut down using the “shutdown” CLI command, or because both SONET circuits are down or OOS.
2-206
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.337 RPR-SD
Step 4
Step 5
If correcting the previous problem on a primary interface does not clear the condition, or if the condition is raised on a card is secondary mode, the IC failure root cause must be corrected. This can be due to a fiber pull, having link protocol down, or shut down interfaces.
• Link state is indicated in the “show interface rpr-ieee 0” output on the following line:
RPR-IEEE0 is up, line protocol is up
• A shutdown is indicated if a node is in pass-through mode. The same command output indicates whether or not this is the case:
MAC passthrough not set
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.7.337 RPR-SD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: ML100T, ML1000, MLFX
The IEEE 802.17b-based RPR Signal Degrade condition indicates that a minor signal degradation has occurred on an IEEE- RPR ring that, if not overridden, can deactivate the link.The RPR-SD condition is
RPR-SD condition clears when the SONET signal degrade clears.
RPR-SD suppresses
It is suppressed by the following alarms:
•
•
•
Clear the RPR-SD Condition
Step 1
Step 2
Complete the
“Clear the SD-P Condition” procedure on page 2-214 to clear this secondary condition.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a
Service-Affecting (SA) problem.
2.7.338 RPR-SF
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: ML100T, ML1000, MLFX
The IEEE 802.17b-based RPR Signal Fail condition indicates a signal loss or major signal degradation that deactivates the RPR-IEEE link. The failure that raises RPR-SF can be attributable to any of the following alarms:
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-207
Chapter 2 Alarm Troubleshooting
2.7.339 RPR-SPAN-MISMATCH
•
•
•
•
•
•
•
•
•
•
•
The RPR-SF condition can also occur if a SONET circuit’s state is UNASSIGNED (not provisioned).
This condition clears when these primary cause alarms are cleared. RPR-SF is suppressed by
. RPR-SF itself suppresses the following alarms:
•
Clear the RPR-SF Condition
Step 1
Step 2
Complete the trouble-clearing procedure in this chapter for any primary cause SONET failure condition as previously listed.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a
Service-Affecting (SA) problem.
2.7.339 RPR-SPAN-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: ML100T, ML1000, MLFX
The IEEE 802.17b-based RPR-SPAN-MISMATCH alarm is caused by span misprovisioning, span forced switching, physical miscabling, or a circuit loopback.
Miscabling problems between this node’s east or west span and its neighboring span in the same direction can also cause this alarm, as will provisioning an XC loopback on a circuit that carries
RPR-IEEE traffic.
If a traffic-affecting issue such as AIS-P, page 36
;
’
, or
UNEQ-P, page 245 occurs, it in turn suppresses RPR-SPAN-MISMATCH.
Note Clearing a circuit XC loopback does not always cause the loopback to clear. If this is the case, a FORCE switch is used to clear the RPR-SPAN-MISMATCH alarm. The FORCE might cause a traffic hit.
RPR- SPAN-MISMATCH is suppressed by
2-208
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.340 RPRW
Clear the RPR-SPAN-MISMATCH Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Locate and clear any primary cause provisioning errors.
If the alarm does not clear, locate and correct any span cabling errors.
If the alarm does not clear, look for and clear XC loopbacks on the spans.
If the alarm does not clear, configure a FORCE switch on the 802.17b-based RPR span and then clear the switch. To do this, enter the following CLI command in RPR-IEEE interface provisioning mode: router(config)# rpr-ieee protection request forced-switch {east | west}
Clear the switch by entering the following command: router(config)# no rpr-ieee protection request forced-switch {east | west}
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.
2.7.340 RPRW
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: ML100T, ML1000, MLFX
The Cisco proprietary RPR Wrapped condition applies to ML-Series card and occurs when the Cisco proprietary RPR protocol initiates a ring wrap due to a fiber cut, node failure, node restoration, new node insertion, or other traffic problem. It can also be raised if the POS port has an Admin down condition.
.). The POS port can go down for one of the following reasons : Deletion of circuit on the POS port, SPR KeepAlive failure when it is configured.
When the wrap occurs, traffic is redirected to the original destination by sending it in the opposite direction around the ring after a link state change or after receiving any SONET path-level alarms.
Note
ML-Series card POS interfaces normally send the “PDI-P” alarm on page 2-186
to the far end when the
POS link goes down or when Cisco proprietary RPR wraps. ML-Series card POS interfaces do not send a PDI-P alarm to the far end when this alarm is detected, when the alarm is being sent to the far end, or when the only defects being detected are the
, the
, the VCAT “LOM” alarm on page 2-148 , or the VCAT
Note For more information about ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the RPRW Condition
Step 1 If a circuit on the POS port part of SPR interface had been deleted, recreate the circuit on the POS port for this alarm to clear ring wrapping.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-209
Chapter 2 Alarm Troubleshooting
2.7.341 RUNCFG-SAVENEED
Step 2
Step 3
Step 4
Look for and clear any service-affecting SONET path-level alarms on the affected circuit, such as the
“LOS-P (TRUNK)” alarm on page 2-160 ,
, or the
“TIM-P” alarm on page 2-238 . Clearing such an alarm can also clear RPRW.
If the condition does not clear, look for and clear any service alarms for the ML-Series card itself, such as the
“CARLOSS (CE1000, CE100T)” alarm on page 2-56
, “CARLOSS (ML1000, ML100T, MLFX)” alarm on page 2-63
, “TPTFAIL (CE100T, CE1000)” alarm on page 2-240
, or the
ML1000, MLFX)” alarm on page 2-242
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.7.341 RUNCFG-SAVENEED
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Run Configuration Save Needed condition occurs when you change the running configuration file for ML-Series cards. It is a reminder that you must save the change to the startup configuration file for it to be permanent.
The condition clears after you save the running configuration to the startup configuration, such as by entering the following command in privileged executive mode in the CLI: router# copy run start
If you do not save the change, the change is lost after the card reboots. If the command “copy run start” is executed in configuration mode and not privileged executive mode, the running configuration will be saved, but the alarm will not clear.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
2.7.342 SD (DS1, DS3)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3
A Signal Degrade (SD) condition for DS-1 or DS-3 occurs when the quality of an electrical signal on a
DS3XM-6, DS3XM-12, or DS3/EC1-48 card has exceeded the BER signal degrade threshold. Signal degrade is defined by Telcordia as a soft failure condition. SD and signal fail (SF) both monitor the incoming BER and are similar, but SD is triggered at a lower bit error rate than SF.
The BER threshold is user-provisionable and has a range for SD from 1E–9 dBm to 1E–5 dBm.
SD can be reported on electrical card ports that are In-Service and Normal (IS-NR); Out-of-Service and
Autonomous, Automatic In-Service (OOS-AU,AIS); or Out-of-Service and Management, Maintenance
(OOS-MA,MT), but not in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state. The BER count increase associated with this alarm does not take an IS-NR port out of service, but if it occurs on an AINS port, the alarm prevents the port from going into service.
2-210
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
November 2009
2.7.342 SD (DS1, DS3)
The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem such as a faulty fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice. SD can also be caused by repeated XC10G card switches that in turn can cause switching on the lines or paths.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note Some levels of BER errors (such as 1E–9 dBm) take a long period to raise or clear, about 9,000 seconds, or 150 minutes. If the SD threshold is provisioned at 1E–9 dBm rate, the SD alarm needs at least one and one-half hours to raise and then another period at least as long to clear.
Note The recommended test set for use on all SONET ONS electrical cards is the Omniber 718. For specific procedures to use the test set equipment, consult the manufacturer.
Clear the SD (DS1, DS3) Condition
Step 1 If the condition applies for a DS-3 line on a DS3XM-6, DS3XM-12, DS3E-12, or DS3/EC1-48 card, complete the
“Clear a DS3XM-6, DS3XM-12, or DS3E-12 Card Loopback Circuit” procedure on page 2-269
. If the condition applies to any other DS-N card (DS3i-N-14, DS3-12, DS3i-N-14, or
DS1/E1-56) complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Ensure that the fiber connector for the card is completely plugged in. For more information about fiber connections and card insertion, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If the BER threshold is correct and at the expected level, use an optical test set to measure the power level of the line to ensure it is within guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
If the optical power level is good, verify that optical receive levels are within the acceptable range.
If receive levels are good, clean the fibers at both ends according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
If the condition does not clear, verify that single-mode fiber is used.
If the fiber is of the correct type, verify that a single-mode laser is used at the far-end node.
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-211
Chapter 2 Alarm Troubleshooting
2.7.343 SD (E1)
Step 8
Step 9
Step 10
Step 11
Clean the fiber connectors at both ends for a signal degrade according to site practice.
Verify that a single-mode laser is used at the far end.
If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement. Refer to the
“2.9.4 Physical Card Reseating, Resetting, and Replacement” section on page 2-264
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.343 SD (E1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: E1
An SD condition for an E1 occurs on a DS1/E1-56 card in E1 only mode when the quality of an electrical signal has exceeded the BER signal degrade threshold.
SD is triggered at a lower bit error rate than SF. The SD BER threshold is user-provisionable and ranges from 1E–9 dBm to 1E–5 dBm.
SD can be reported on electrical card ports that are In-Service and Normal (IS-NR); Out-of-Service and
Autonomous, Automatic In-Service (OOS-AU,AIS); or Out-of-Service and Management, Maintenance
(OOS-MA,MT) but not in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state. The BER count increase associated with this alarm does not take an IS-NR port out of service, but if it occurs on an AINS port, the alarm prevents the port from going into service.
The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem such as a faulty fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice. SD can also be caused by repeated XC10G card switches that in turn can cause switching on the lines or paths.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Note Some levels of BER errors (such as 1E–9 dBm) take a long period to raise or clear, about 9,000 seconds, or 150 minutes. If the SD threshold is provisioned at 1E–9 dBm rate, the SD alarm needs at least one and a half hours to raise and then another period at least as long to clear.
Note The recommended test set for use on all SONET ONS electrical cards is the Omniber 718. For specific procedures to use the test set equipment, consult the manufacturer.
2-212
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.344 SD (TRUNK)
Clear the SD (E1) Condition
Step 1 Complete the
“Clear Other Electrical Card or Ethernet Card Loopbacks” procedure on page 2-270
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Ensure that the fiber connector for the card is completely plugged in. For more information about fiber connections and card insertion, refer to the “Install Cards and Fiber-Optic Cable” chapter in the
Cisco ONS 15454 Procedure Guide .
If the BER threshold is correct and at the expected level, use an optical test set to measure the power level of the line to ensure it is within guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
If the optical power level is good, verify that optical receive levels are within the acceptable range.
If receive levels are good, clean the fibers at both ends according to site practice. If no site practice exists, complete the procedure in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide .
If the condition does not clear, verify that single-mode fiber is used.
If the fiber is of the correct type, verify that a single-mode laser is used at the far-end node.
Clean the fiber connectors at both ends for a signal degrade according to site practice.
If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement. Refer to the
“2.9.4 Physical Card Reseating, Resetting, and Replacement” section on page 2-264 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.344 SD (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.345 SD-L
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EC1, OCN
An SD Line condition is similar to the
“SD (DS1, DS3)” condition on page 2-210
. It applies to the line level of the SONET signal and travels on the B2 byte of the SONET overhead.
An SD-L on an Ethernet or OC-N card does not cause a protection switch. If the alarm is reported on a card that has also undergone a protection switch, the SD BER count continues to accumulate. The condition is superseded by higher-priority alarms such as the
, the
(OCN)” alarm, page 2-145 , the
, and the
.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-213
Chapter 2 Alarm Troubleshooting
2.7.346 SD-L (TRUNK)
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the SD-L Condition
Step 1
Step 2
Complete the “Clear the SD (DS1, DS3) Condition” procedure on page 2-211
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.346 SD-L (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.347 SD-P
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
An SD Path condition is similar to the
“SD (DS1, DS3)” condition on page 2-210 , but it applies to the
path (STS) layer of the SONET overhead. A path or STS-level SD alarm travels on the B3 byte of the
SONET overhead.
For path protection protected circuits, the BER threshold is user-provisionable and has a range for SD from 1E–9 dBm to 1E–5 dBm. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E–6 dBm.
On path protection configurations, an SD-P condition causes a switch from the working card to the protect card at the path (STS) level. On BLSR, 1+1, and on unprotected circuits, an SD-P condition does not cause switching.
The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.
The SD clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.
Clear the SD-P Condition
Step 1
Step 2
Complete the “Clear the SD (DS1, DS3) Condition” procedure on page 2-211
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-214
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.348 SD-V
2.7.348 SD-V
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: VT-MON, VT-TERM
An SD-V condition is similar to the
“SD (DS1, DS3)” condition on page 2-210 , but it applies to the VT
layer of the SONET overhead.
For path protection protected circuits, the BER threshold is user-provisionable and has a range for SD from 1E–9 dBm to 1E–5 dBm. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E–6 dBm.
On path protection configurations, an SD-V condition does not cause a switch from the working card to the protect card at the path (STS) level. On BLSR, 1+1, and on unprotected circuits, an SD-V condition does not cause switching.
The BER increase that causes the alarm is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.
The SD alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.
Clear the SD-V Condition
Step 1
Step 2
Complete the
“Clear the SD (DS1, DS3) Condition” procedure on page 2-211 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.349 SF (DS1, DS3)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3
A Signal Fail (SF) condition occurs when the quality of the signal has exceeded the BER signal failure threshold. Signal failure is defined by Telcordia as a “hard failure” condition. The SD and SF conditions both monitor the incoming BER error rate and are similar conditions, but SF is triggered at a higher BER than SD.
The BER threshold is user-provisionable and has a range for SF from 1E–5 to 1E–3.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-215
Chapter 2 Alarm Troubleshooting
2.7.350 SF (E1)
Clear the SF (DS1, DS3) Condition
Step 1
Complete the “Clear the SD (DS1, DS3) Condition” procedure on page 2-211
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.350 SF (E1)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: E1
An SF condition for an E1 occurs on a DS1/lE1-56 card in E1 only mode when the quality of the signal has exceeded the BER signal failure threshold.
SF monitors the incoming BER error rate just as SD does, but SF is triggered at a higher BER than SD.
The SF BER threshold is user-provisionable and has a range for SF from 1E–5 to 1E–3.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the SF (E1) Condition
Step 1
Complete the “Clear the SD (E1) Condition” procedure on page 2-213
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-216
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.351 SF (TRUNK)
2.7.351 SF (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.352 SF-L
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EC1, OCN
An SF Line condition is similar to the
“SF (DS1, DS3)” condition on page 2-215 , but it applies to the
line layer B2 overhead byte of the SONET signal. It can trigger a protection switch.
The SF-L condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.
The condition is superseded by higher-priority alarms such as the
“LOF (EC1)” alarm, page 2-144 , the
, and the
.
Clear the SF-L Condition
Step 1
Step 2
Complete the
“Clear the SD (DS1, DS3) Condition” procedure on page 2-211 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.353 SF-L (TRUNK)
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.354 SF-P
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: STSMON, STSTRM
An SF Path condition is similar to the
“SF (DS1, DS3)” condition on page 2-215 , but it applies to the
path (STS) layer B3 byte of the SONET overhead. It can trigger a protection switch.
The SF-P condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.
Clear the SF-P Condition
Step 1 Complete the
“Clear the SD (DS1, DS3) Condition” procedure on page 2-211 .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-217
Chapter 2 Alarm Troubleshooting
2.7.355 SFTWDOWN
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.355 SFTWDOWN
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
A Software Download in Progress alarm occurs when the TCC2/TCC2P is downloading or transferring software.
If the active and standby TCC2/TCC2Ps have the same versions of software, it takes approximately three minutes for software to be updated on a standby TCC2/TCC2P.
If the active and standby TCC2/TCC2Ps have different software versions, the transfer can take up to
30 minutes. Software transfers occur when different software versions exist on the two cards. After the transfer completes, the active TCC2/TCC2P reboots and goes into standby mode after approximately three minutes.
No action is necessary. Wait for the transfer or the software download to complete. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
Note SFTWDOWN is an informational alarm.
2.7.356 SF-V
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: VT-MON, VT-TERM
An SF-V condition is similar to the
“SF (DS1, DS3)” condition on page 2-215
, but it applies to the VT layer of the SONET overhead.
Clear the SF-V Condition
Step 1
Step 2
Complete the “Clear the SD (DS1, DS3) Condition” procedure on page 2-211
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.357 SHELF-COMM-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-218
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.358 SH-INS-LOSS-VAR-DEG-HIGH
2.7.358 SH-INS-LOSS-VAR-DEG-HIGH
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.359 SH-INS-LOSS-VAR-DEG-LOW
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.360 SHUTTER-OPEN
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.361 SIGLOSS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: FCMR
DWDM Logical Objects: ESCON, FC, GE, ISC, TRUNK
The Signal Loss on Data Interface alarm is raised on FC_MR-4 card receive client ports and MXP card
FC and ISC client data ports when there is a loss of signal. (Loss of Gigabit Ethernet client signal results
in a “CARLOSS (GE)” alarm, page 2-62
, not SIGLOSS.) SIGLOSS can also be raised on the MXP trunk port.
If the
“SYNCLOSS” alarm, page 2-233 , was previously raised on the port, the SIGLOSS alarm will
demote it.
Clear the SIGLOSS Alarm
Step 1
Step 2
Step 3
Step 4
Ensure that the data port connection at the near-end card’s port of the SONET link is operational.
Verify fiber continuity to the port. To verify fiber continuity, follow site practices.
Check the physical port LED on the card. The port LED looks clear (that is, not lit green) if the link is not connected.
If the alarm does not clear, log onto http://www.cisco.com/techsupport for more information or call
Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.362 SNTP-HOST
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: NE
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-219
Chapter 2 Alarm Troubleshooting
2.7.363 SPANLENGTH-OUT-OF-RANGE
The Simple Network Timing Protocol (SNTP) Host Failure alarm indicates that an ONS 15454 serving as an IP proxy for the other ONS 15454 nodes in the ring is not forwarding SNTP information to the other nodes in the network. The forwarding failure can result from two causes: either the IP network attached to the ONS 15454 proxy node is experiencing problems, or the ONS 15454 proxy node itself is not functioning properly.
Clear the SNTP-HOST Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Ping the SNTP host from a workstation in the same subnet to ensure that communication is possible within the subnet by completing the
“1.9.8 Verify PC Connection to the ONS 15454 (ping)” procedure on page 1-112
.
If the ping fails, contact the network administrator who manages the IP network that supplies the SNTP information to the proxy and determine whether the network is experiencing problems, which could affect the SNTP server/router connecting to the proxy ONS 15454 system.
If no network problems exist, ensure that the ONS system proxy is provisioned correctly: a.
b.
c.
In node view for the ONS 15454 serving as the proxy, click the Provisioning > General tabs.
Ensure that the Use NTP/SNTP Server check box is checked.
If the Use NTP/SNTP Server check box is not checked, click it.
Ensure that the Use NTP/SNTP Server field contains a valid IP address for the server.
d.
If proxy is correctly provisioned, refer to the “Timing” chapter in the Cisco ONS 15454 Reference
Manual for more information on SNTP Host.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.363 SPANLENGTH-OUT-OF-RANGE
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.364 SPAN-SW-EAST
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Span Switch Is Active East Side condition occurs when a span switch occurs at the east side of a four-fiber BLSR span using a Force Span command. The condition clears when the switch is cleared.
SPAN-SW-EAST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Span was applied shows an “F” on the network view detailed circuit map.
Note SPAN-SW-EAST is an informational condition and does not require troubleshooting.
2-220
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.365 SPAN-SW-WEST
2.7.365 SPAN-SW-WEST
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Span Switch Is Active West Side condition occurs when a span switch occurs at the west side of a four-fiber BLSR span using a Force Span command. The condition clears when the switch is cleared.
SPAN-SW-WEST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Span was applied shows an “F” on the network view detailed circuit map.
Note SPAN-SW-WEST is an informational condition and does not require troubleshooting.
2.7.366 SQUELCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Ring Squelching Traffic condition occurs in a BLSR when a node that originates or terminates STS circuits fails or is isolated by multiple fiber cuts or maintenance Force Ring commands. The isolation or failure of the node disables circuits that originate or terminate on the failed node. SQUELCH conditions appear on one or both of the nodes on either side of the isolated or failed node. The
“AIS-P” condition on page 2-36 also appears on all nodes in the ring except the isolated node.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 .
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the SQUELCH Condition
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1 Determine the isolated node: a.
From the View menu, choose Go to Network View .
b.
The grayed out node with red spans is the isolated node.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-221
Chapter 2 Alarm Troubleshooting
2.7.367 SQUELCHED
Step 2
Step 3
Verify fiber continuity to the ports on the isolated node. To verify cable continuity, follow site practices.
If fiber continuity is good, verify that the proper ports are in service: a.
Confirm that the LED is correctly illuminated on the physical card.
b.
A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
To determine whether the OC-N port is in service, double-click the card in CTC to open the card view.
c.
d.
e.
Click the Provisioning > Line tabs.
Verify that the Admin State column lists the port as IS.
If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose
IS . Click Apply .
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 4
Step 5
Step 6
Step 7
Step 8
If the correct ports are in service, use an optical test set to verify that a valid signal exists on the line.
For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
If the signal is valid, verify that the power level of the optical signal is within the optical card receiver specifications. Refer to the Cisco ONS 15454 Reference Manual for card specifications.
If the receiver levels are good, ensure that the optical transmit and receive fibers are connected properly.
If the connectors are good, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the OC-N card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.367 SQUELCHED
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
The Client Signal Squelched condition is raised by a TXP_MR_10G, TXP_MR_10E, TXP_MR_2.5G,
TXPP_MR_2.5G, MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_2.5G, or MXPP_MR_2.5G card.
The condition can be raised in the following situations:
• An MXP or TXP client facility detects that an upstream receive facility has experienced a loss of signal (such as an Ethernet CARLOSS, DWDM SIGLOSS, or optical LOS). In response, the facility’s transmit is turned off (SQUELCHED). The upstream receive facilities are the trunk receive on the same card as the client, as well as the client receive on the card at the other end of the trunk span.
2-222
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.367 SQUELCHED
November 2009
• The client will squelch if the upstream trunk receive (on the same card) experiences a
;
, or
“LOS (TRUNK)” alarm, page 2-160
. In some transparent modes, the client is squelched if the trunk detects an
, or a “TIM” alarm, page 2-237 .
• The client will squelch if the upstream client receive (on the card at the other end of the DWDM span) experiences
;
;
;
or
“LOS (TRUNK)” alarm, page 2-160
.
In an example situation, an upstream MXP_2.5G_10G client port receive experiences a “loss of light,” and this port raises CARLOSS, SIGLOSS, or LOS (determined by the payload type) locally. The port also sends client signal fail to its downstream card. The downstream card raises a
, turns off the client transmit laser, and raises the SQUELCHED condition.
The local client raises SQUELCHED if it also raises one of the following alarms for the client, all of which are signalled by the upstream node:
•
•
•
•
•
•
2.7.145 GFP-NO-BUFFERS, page 2-114
2.7.142 GFP-DE-MISMATCH, page 2-112
2.7.143 GFP-EX-MISMATCH, page 2-113
•
•
•
2.7.271 ODUK-1-AIS-PM, page 2-182
2.7.272 ODUK-2-AIS-PM, page 2-183
2.7.273 ODUK-3-AIS-PM, page 2-183
2.7.274 ODUK-4-AIS-PM, page 2-183
On the MXP_MR_10G, the local client raises a SQUELCHED condition if the upstream client detects one of the following alarms. Note that no corresponding local alarm is raised to indicate which of these conditions is present upstream.
• LOS for the clients including the
“LOS (2R)” alarm on page 2-151 , the
“LOS (ESCON)” alarm on page 2-157
, and the
“LOS (ISC)” alarm on page 2-158
• CARLOSS for the clients including the
“CARLOSS (FC)” alarm on page 2-60 , the
(GE)” alarm on page 2-62 , and the
“CARLOSS (ISC)” alarm on page 2-63
The local client raises a SQUELCHED condition if the local trunk raises one of the following alarms:
•
•
•
•
•
2.7.215 LOS (TRUNK), page 2-160
(squelching enabled)
•
•
•
•
•
2.7.275 ODUK-AIS-PM, page 2-183
2.7.277 ODUK-LCK-PM, page 2-183
2.7.281 ODUK-TIM-PM, page 2-184
(squelching enabled)
2.7.399 TIM, page 2-237 (for the OC-N, squelching enabled)
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-223
Chapter 2 Alarm Troubleshooting
2.7.368 SQM
•
2.7.55 CARLOSS (TRUNK), page 2-64
•
2.7.429 WVL-MISMATCH, page 2-252 (client or trunk)
When troubleshooting the SQUELCHED condition locally, look for failures progressing upstream in the following order. (If you are troubleshooting this alarm remotely, reverse the order of progress.)
•
•
•
Local client alarms, as above
Local trunk alarms, as above
Remote (upstream) client receive alarms, as above
Note If you see a SQUELCHED condition on the trunk, this can only be caused by a transponder (TXP) card.
Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .
Clear the SQUELCHED Condition
Step 1
Step 2
Step 3
If the object is reported against any object besides ESCON, determine whether the remote node and local node reports and LOF or the LOS alarm (for the client trunk, as listed above). If it does, turn to the relevant section in this chapter and complete the troubleshooting procedure.
If no LOF or LOS is reported, determine whether any other listed remote node or local node conditions as listed above has occurred. If so, turn to the relevant section of this chapter and complete the troubleshooting procedure.
If none of these alarms is reported, determine whether the local port reporting the SQUELCHED condition is in loopback. (You will see LPBKFACILITY or LPBKTERMINAL condition for this particular client type in the Condition window.) If it is in loopback, complete the following steps: a.
b.
c.
Double-click the client card to open the card view.
Click the Maintenance > Loopback > Port tabs.
If the port Admin State column says OOS,MT or OOS,DSBLD, click the cell to highlight it and choose IS from the drop-down list. Changing the state to IS also clears any loopback provisioned on the port.
Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.
Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.368 SQM
Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Major (MJ),
Service-Affecting (SA) for VT-TERM
2-224
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.369 SSM-DUS
SONET Logical Objects: STSTRM, VT-TERM
The Sequence Mismatch alarm is a virtual concatenated (VCAT) member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when the expected sequence numbers of VCAT members do not match the received sequence numbers.
Clear the SQM Alarm
Step 1
Step 2
Step 3
For the errored circuit, complete the “Delete a Circuit” procedure on page 2-268
.
Recreate the circuit using the “Create Circuits and VT Tunnels” chapter of the Cisco ONS 15454
Procedure Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.369 SSM-DUS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, OCN
DWDM Logical Object: TRUNK
The Synchronization Status (SSM) Message Quality Changed to Do Not Use (DUS) condition occurs when the synchronization status message (SSM) quality level degrades to DUS or is manually changed to DUS.
The signal is often manually changed to DUS to prevent timing loops from occurring. Sending a DUS prevents the timing from being reused in a loop. The DUS signal can also be sent for line maintenance testing.
Note SSM-DUS is an informational condition and does not require troubleshooting.
2.7.370 SSM-FAIL
Single Failure Default Severity: Minor (MN), Non-Service-Affecting (NSA); Double Failure
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: BITS, DS1, E1, OCN
DWDM Logical Object: TRUNK
The SSM Failed alarm occurs when the synchronization status messaging received by the ONS 15454 fails. The problem is external to the ONS 15454. This alarm indicates that although the ONS 15454 is set up to receive SSM, the timing source is not delivering valid SSM messages.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-225
Chapter 2 Alarm Troubleshooting
2.7.371 SSM-LNC
Clear the SSM-FAIL Alarm
Step 1
Step 2
Step 3
Verify that SSM is enabled on the external timing source.
If timing is enabled, use an optical test set to determine that the external timing source is delivering SSM.
For specific procedures to use the test set equipment, consult the manufacturer.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.371 SSM-LNC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
SONET Logical Objects: BITS, NE-SREF
DWDM Logical Object: TRUNK
The SSM Local Node Clock (LNC) Traceable condition occurs on MXP trunk ports when the SSM (S1) byte of the SONET overhead multiplexing section has been changed to signify that the line or BITS timing source is the LNC.
Note SSM-LNC is an informational condition and does not require troubleshooting.
2.7.372 SSM-OFF
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, OCN
DWDM Logical Object: TRUNK
The SSM Off condition applies to references used for timing the node. It occurs when the SSM for the reference has been turned off. The node is set up to receive SSM, but the timing source is not delivering
SSM messages.
Clear the SSM-OFF Condition
Step 1
Step 2
Complete the “Clear the SSM-FAIL Alarm” procedure on page 2-226
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.373 SSM-PRC
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2-226
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.374 SSM-PRS
SONET Logical Objects: BITS, NE-SREF
DWDM Logical Object: TRUNK
The SSM Primary Reference Clock (PRC) Traceable condition occurs when the SONET transmission level for an MXP trunk port is PRC.
Note SSM-PRC is an informational condition and does not require troubleshooting.
2.7.374 SSM-PRS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
The SSM Primary Reference Source (PRS) Traceable condition occurs when the SSM transmission level is changed to Stratum 1 Traceable.
Note SSM-PRS is an informational condition and does not require troubleshooting.
2.7.375 SSM-RES
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
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 and does not require troubleshooting.
2.7.376 SSM-SDN-TN
The SSM-SDN-TN condition is not used in this platform in this release. It is reserved for development.
2.7.377 SSM-SETS
The SSM-SETS condition is not used in this platform in this release. It is reserved for development.
2.7.378 SSM-SMC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-227
Chapter 2 Alarm Troubleshooting
2.7.379 SSM-ST2
DWDM Logical Object: TRUNK
The SSM SONET Minimum Clock (SMC) Traceable condition occurs when the synchronization message quality level changes to SMC. The login node does not use the clock because the node cannot use any reference beneath its internal level, which is ST3.
Note SSM-SMC is an informational condition and does not require troubleshooting.
2.7.379 SSM-ST2
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
The SSM Stratum 2 (ST2) Traceable condition occurs when the synchronization message quality level is changed to ST2.
Note SSM-ST2 is an informational condition and does not require troubleshooting.
2.7.380 SSM-ST3
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
The SSM Stratum 3 (ST3) Traceable condition occurs when the synchronization message quality level is changed to ST3.
Note SSM-ST3 is an informational condition and does not require troubleshooting.
2.7.381 SSM-ST3E
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
The SSM Stratum 3E (ST3E) Traceable condition indicates that the synchronization message quality level is changed to ST3E from a lower level of synchronization. SSM-ST3E is a Generation 2 SSM and is used for Generation 1.
Note SSM-ST3E is an informational condition and does not require troubleshooting.
2-228
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.382 SSM-ST4
2.7.382 SSM-ST4
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
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 and does not require troubleshooting.
2.7.383 SSM-STU
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, NE-SREF, OCN
DWDM Logical Object: TRUNK
The SSM Synchronization Traceability Unknown (STU) condition occurs when the reporting node is timed to a reference that does not support SSM, but the ONS 15454 has SSM support enabled. SSM-STU can also occur if the timing source is sending out SSM messages but SSM is not enabled on the
ONS 15454.
Clear the SSM-STU Condition
Step 1
Step 2
Step 3
Step 4
In node view, click the Provisioning > Timing > BITS Facilities tabs.
Complete one of the following depending upon the status of the Sync Messaging Enabled check box:
• If the Sync. Messaging Enabled check box for the BITS source is checked, uncheck the box.
• If the Sync. Messaging Enabled check box for the BITS source is not checked, check the box.
Click Apply .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.384 SSM-TNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, NE-SREF
DWDM Logical Object: TRUNK
The SSM Transit Node Clock (TNC) Traceable condition occurs when the synchronization message quality level is changed to TNC.
Note SSM-TNC is an informational condition and does not require troubleshooting.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-229
Chapter 2 Alarm Troubleshooting
2.7.385 STS-SQUELCH-L
2.7.385 STS-SQUELCH-L
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Ring is Squelching STS traffic condition is raised on an OC-N facility. If the node failure scenario includes the source or destination node, then switching the nodes will squelch all the STSs that originate from or destinate to the failure node. The condition resolves when the node is no longer failing.
This condition has an NA severity by default. However, the condition indicates that traffic is squelched due to node failure, that is, traffic outage. Traffic outage can be caused by different problems, such as multiple LOS alarms, AIS-L, or node power outage. STS-SQUELCH-L is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what is causing the node isolation.
Note STS-SQUELCH-L is an informational condition.
2.7.386 SW-MISMATCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
The Software Mismatch condition occurs during software upgrade when there is a mismatch between software versions. The card connecting to the TCC2/TCC2P is running an older version than the
TCC2/TCC2P is.
Clear the SW-MISMATCH Condition
Step 1
Step 2
Complete the “Reset a Traffic Card in CTC” procedure on page 2-263 for the errored card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.387 SWMTXMOD-PROT
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Switching Matrix Module Failure on Protect Slot alarm is raised by the Slot 10 cross connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-PROT occurs when a logic component internal to the
Slot 10 cross connect is out of frame (OOF) with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.
The XC-VXC-10G card can raise this alarm (in Slot 10) whether it is ACT or standby (SBY). The XCVT card can raise SWMTXMOD-PROT against itself if the cross-connect card is OOF with a second logic component on the same cross connect card.
2-230
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.388 SWMTXMOD-WORK
Clear the SWMTXMOD-PROT Alarm
Step 1
Step 2
Step 3
Step 4
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for the Slot 10 card. For the LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the Slot 10 cross-connect card.
Complete the
“Side Switch the Active and Standby Cross-Connect Cards” procedure on page 2-264
.
Note After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.388 SWMTXMOD-WORK
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: EQPT
The Switching Matrix Module Failure on Working Slot alarm is raised by the Slot 8 cross connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-WORK occurs when a logic component internal to the
Slot 8 cross connect is OOF with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.
The XC-VXC-10G card can raise this alarm (in Slot 8) whether it is ACT or standby (SBY). The XCVT card can raise SWMTXMOD-WORK against itself if the cross-connect card is OOF with a second logic component on the same cross connect card.
Clear the SWMTXMOD-WORK Alarm
Step 1
Step 2
Step 3
Step 4
Complete the
“Reset a Traffic Card in CTC” procedure on page 2-263 for the Slot 8 card. For LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-252
.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green
ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the alarm does not clear, complete the
“Remove and Reinsert (Reseat) Any Card” procedure on page 2-266
for the Slot 8 cross-connect card.
Complete the
“Side Switch the Active and Standby Cross-Connect Cards” procedure on page 2-264
.
Note After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-231
Chapter 2 Alarm Troubleshooting
2.7.389 SWTOPRI
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.389 SWTOPRI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Synchronization Switch to Primary Reference condition occurs when the ONS 15454 switches to the primary timing source (reference 1). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.
Note SWTOPRI is an informational condition and does not require troubleshooting.
2.7.390 SWTOSEC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Synchronization Switch to Secondary Reference condition occurs when the ONS 15454 has switched to a secondary timing source (reference 2).
Clear the SWTOSEC Condition
Step 1
Step 2
To clear the condition, clear alarms related to failures of the primary source, such as the
“SYNCPRI” alarm on page 2-234 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.391 SWTOTHIRD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
The Synchronization Switch to Third Reference condition occurs when the ONS 15454 has switched to a third timing source (reference 3).
Clear the SWTOTHIRD Condition
Step 1 To clear the condition, clear alarms related to failures of the primary source, such as the
“SYNCPRI” alarm on page 2-234 or the
.
2-232
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.392 SYNC-FREQ
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.392 SYNC-FREQ
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: BITS, DS1, E1, OCN
DWDM Logical Object: TRUNK
The Synchronization Reference Frequency Out of Bounds condition is reported against any reference that is out of the bounds for valid references. The login node fails the reference and chooses another internal or external reference to use.
Clear the SYNC-FREQ Condition
Step 1
Step 2
Use an optical test set to verify the timing frequency of the line or BITS timing source and ensure that it falls within the proper frequency. For specific procedures to use the test set equipment, consult the manufacturer.
For BITS, the proper timing frequency range is approximately –15 PPM to 15 PPM. For optical line timing, the proper frequency range is approximately –16 PPM to 16 PPM.
If the reference source frequency is not outside of bounds, complete the
Card” procedure on page 2-266 for the TCC2/TCC2P.
Note It takes up to 30 minutes for the TCC2/TCC2P to transfer the system software to the newly installed TCC2/TCC2P. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the active TCC2/TCC2P reboots and goes into standby mode after approximately three minutes.
Step 3 If the SYNC-FREQ condition continues to report after replacing the TCC2/TCC2P, log into the
Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC
1 800 553-2447.
2.7.393 SYNCLOSS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: FCMR
DWDM Logical Objects: FC, GE, ISC, TRUNK
The Loss of Synchronization on Data Interface alarm is raised on FC_MR-4 client ports and MXP cards client or trunk ports when there is a loss of signal synchronization on the port. This alarm is demoted by the SIGLOSS alarm.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-233
Chapter 2 Alarm Troubleshooting
2.7.394 SYNCPRI
Clear the SYNCLOSS Alarm
Step 1
Step 2
Step 3
Step 4
Ensure that the data port connection at the near-end card’s port of the SONET link is operational.
Verify fiber continuity to the port. To do this follow site practices.
View the physical port LED to determine whether the alarm has cleared:
•
•
If the LED is green, the alarm has cleared.
If the port LED is clear (that is, not illuminated green), the link is not connected and the alarm has not cleared.
• If the LED is red, this indicates that the fiber is pulled.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.394 SYNCPRI
Default Severity: Minor (MN), Non-Service-Affecting (NSA) for EXT-SREF;Major (MJ),
Service-Affecting (SA) for NE-SREF
SONET Logical Objects: EXT-SREF, NE-SREF
A Loss of Timing on Primary Reference alarm occurs when the ONS 15454 loses the primary timing source (reference 1). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the
ONS 15454 should switch to its secondary timing source (reference 2). Switching to the secondary timing source also triggers the
.
Note The SYNCPRI alarm will be escalated to Major (MJ), Service-Affecting if no other valid references (SYNCSEC, SYNCTHIRD) are available. If any other reference are available then SYNCPRI gets raised as Minor (MN), non service affecting.
Clear the SYNCPRI Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, click the Provisioning > Timing > General tabs.
Verify the current configuration for REF-1 of the NE Reference.
If the primary timing reference is a BITS input, complete the
“Clear the LOS (BITS) Alarm” procedure on page 2-151
.
If the primary reference clock is an incoming port on the ONS 15454, complete the
(OCN) Alarm” procedure on page 2-159 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-234
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.395 SYNCSEC
2.7.395 SYNCSEC
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
A Loss of Timing on Secondary Reference alarm occurs when the ONS 15454 loses the secondary timing source (reference 2). If SYNCSEC occurs, the ONS 15454 should switch to a third timing source
(reference 3) to obtain valid timing for the ONS 15454. Switching to a third timing source also triggers the
“SWTOTHIRD” alarm on page 2-232 .
Note The severity of SYNCSEC alarm is dependent on the alarm profile it is associated with. If the alarm profile it is associated with is Major (MJ), then this condition is raised as MJ, service affecting, even if alternate source of references are available.
Clear the SYNCSEC Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, click the Provisioning > Timing > General tabs.
Verify the current configuration of REF-2 for the NE Reference.
.
Verify that the BITS clock is operating properly.
If the secondary timing source is an incoming port on the ONS 15454, complete the
(OCN) Alarm” procedure on page 2-159
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.396 SYNCTHIRD
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Objects: EXT-SREF, NE-SREF
A Loss of Timing on Third Reference alarm occurs when the ONS 15454 loses the third timing source
(reference 3). If SYNCTHIRD occurs and the ONS 15454 uses an internal reference for source three,
“HLDOVRSYNC” condition on page 2-121 after a SYNCTHIRD alarm
Note The severity of SYNCTHIRD alarm is dependent on the alarm profile it is assosicated with.
If the alarm profile it is associated with is Major (MJ), then this condition is raised as MJ, service affecting, even if alternate source of references are available.
Clear the SYNCTHIRD Alarm
Step 1 In node view, click the Provisioning > Timing > General tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-235
Chapter 2 Alarm Troubleshooting
2.7.397 SYSBOOT
Step 2
Step 3
Step 4
Verify that the current configuration of REF-3 for the NE Reference. For more information about references, refer to the “Timing” chapter in the Cisco ONS 15454 Reference Manual .
If the third timing source is a BITS input, complete the
“Clear the LOS (BITS) Alarm” procedure on page 2-151
.
If the third timing source is an incoming port on the ONS 15454, complete the
Alarm” procedure on page 2-159 .
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 5
Step 6
If the third timing source uses the internal ONS 15454 timing, complete the
TCC2/TCC2P Card and Activate the Standby Card” procedure on page 2-263 .
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC
1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the
Reinsert (Reseat) the Standby TCC2/TCC2P Card” procedure on page 2-265
. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the
.
2.7.397 SYSBOOT
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: NE
The System Reboot alarm indicates that new software is booting on the TCC2/TCC2P. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to
30 minutes.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
Note SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.
2.7.398 TEMP-MISM
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE
Temperature Reading Mismatch Between Control Cards is raised when the temperature readings on the two TCC2/TCC2Ps are out of range of each other by more than some predefined difference (such as 5 degrees C). A message containing power monitoring and temperature information is exchanged between the two TCC2/TCC2Ps, allowing the values to be compared. The temperature of each TCC2/TCC2P is read from a system variable.
This condition can be caused by a clogged fan filter or by fan tray stoppage.
2-236
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.399 TIM
Clear the TEMP-MISM Condition
Step 1
Step 2
Step 3
Complete the
“Inspect, Clean, and Replace the Reusable Air Filter” procedure on page 2-271
.
If the condition does not clear, complete the
“Remove and Reinsert a Fan-Tray Assembly” procedure on page 2-272
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.399 TIM
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Object: OCN
DWDM Logical Object: TRUNK
The Section TIM alarm occurs when the expected J0 section trace string does not match the received section trace string. This occurs because the data being received is not correct, and the receiving port could not be connected to the correct transmitter port.
If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed due to a fibering misconnection, a TL1 routing change, or to someone entering an incorrect value in the Current
Transmit String field.
TIM occurs on a port that has previously been operating without alarms if someone switches optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the
“LOS (OCN)” alarm on page 2-158
or the
“UNEQ-P” alarm on page 2-245 . If these alarms accompany a TIM alarm,
reattach or replace the original cables/fibers to clear the alarms. If a Transmit or Expected String was changed, restore the original string.
Clear the TIM Alarm
Step 1
Step 2
Ensure that the physical fibers are correctly configured and attached. To do this, consult site documents.
For more information about cabling the ONS 15454, refer to the “Install Cards and Fiber-Optic Cable” chapter in the Cisco ONS 15454 Procedure Guide .
If the alarm does not clear, you can compare the J0 expected and transmitted strings and, if necessary, change them: a.
b.
c.
d.
Log into the circuit source node and click the Circuits tab.
Select the circuit reporting the condition, then click Edit .
In the Edit Circuit window, check the Show Detailed Circuit Map check box and click Apply .
On the detailed circuit map, right-click the source circuit port and choose Edit J0 Path Trace (port) from the shortcut menu.
e.
f.
g.
Compare the Current Transmit String and the Current Expected String entries in the Edit J0 Path
Trace dialog box.
If the strings differ, correct the Transmit or Expected strings and click Apply .
Click Close .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-237
Chapter 2 Alarm Troubleshooting
2.7.400 TIM-MON
Step 3
Step 4
If the alarm does not clear, ensure that the signal has not been incorrectly routed. (Although the
ONS 15454 routes circuits automatically, the circuit route could have been changed using TL1.) If necessary, manually correct the routing using TL1. For instructions, refer to the Cisco ONS SONET TL1
Reference Guide and the Cisco ONS SONET TL1 Command Guide .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem if necessary.
2.7.400 TIM-MON
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: TRUNK
The TIM Section Monitor TIM alarm is similar to the
, but it applies to
TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards when they are configured in transparent mode. (In transparent termination mode, all SONET overhead bytes are passed through from client ports to the trunk ports or from trunk ports to client ports.)
Note For more information about MXP and TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .
Clear the TIM-MON Alarm
Step 1
Step 2
Complete the “Clear the TIM-P Alarm” procedure on page 2-239
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.401 TIM-P
Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Default Severity:
Minor (MN), Non-Service-Affecting (NSA) for STSMON
SONET Logical Objects: STSMON, STSTRM
The TIM Path alarm occurs when the expected path trace string does not match the received path trace string. Path Trace Mode must be set to Manual or Auto for the TIM-P alarm to occur.
In manual mode at the Path Trace window, the user types the expected string into the Current Expected
String field for the receiving port. The string must match the string typed into the Transmit String field for the sending port. If these fields do not match, the login node raises the TIM-P alarm. In Auto mode on the receiving port, the card sets the expected string to the value of the received string. If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Complete the following procedure to clear either instance.
2-238
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.402 TIM-S
Clear the TIM-P Alarm
Step 1
Step 2
Complete the
“Clear the TIM Alarm” procedure on page 2-237
. (The option will say “Edit J1 Path Trace” rather than “Edit J0 Path Trace.”)
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447. If the alarm applies to the STSTRM object, it is Service-Affecting (SA).
2.7.402 TIM-S
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: EC1, OCN
The TIM for Section Overhead alarm occurs when there is a mismatch between the expected and received J0 section overhead strings in either Manual or Auto mode.
In manual mode at the DS3/EC1-48 card Section Trace window, the user enters the expected string into the Current Expected String field for the receiving port. The string must match the string typed into the
Transmit String field for the sending port. If these fields do not match, the login node raises the TIM-S alarm.
In Auto mode on the receiving port, the card sets the expected string to the value of the received string.
If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Complete the following procedure to clear either problem.
TIM-S also occurs on a port that has previously been operating without alarms if someone switches the
can be raised downstream and the “RFI-L” alarm on page 2-198 can be raised upstream.
Note AIS-L and RFI-L are disabled or enabled in the Provisioning > EC1 > Section Trace tab Disable
AIS/RDI on TIM-S?
check box.
Clear the TIM-S Alarm
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Double-click the DS3/EC1-48 card to open the card view.
Click the Provisioning > EC1 > Section Trace tabs.
Choose the port from the Port pull-down.
In the Expected area, enter the correct string into the Current Expected String field.
Click Apply .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447. If the alarm applies to the STSTRM object, it is Service-Affecting (SA).
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-239
Chapter 2 Alarm Troubleshooting
2.7.403 TIM-V
2.7.403 TIM-V
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: VT-TERM
The VT Path TIM alarm is raised on VT terminations when the J2 path trace is enabled and is mismatched with the expected trace string.
Clear the TIM-V Alarm
Step 1
Step 2
Complete the “Clear the TIM Alarm” procedure on page 2-237
.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.404 TPTFAIL (CE100T, CE1000)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: CE100T, CE1000
The Transport (TPT) Layer Failure alarm for the CE-Series card indicates a break in the end-to-end
Ethernet link integrity feature of the card. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the TPTFAIL (CE100T, CE1000) Alarm
Step 1
Step 2
Complete the “Clear the TPTFAIL (G1000) Alarm” procedure on page 2-241 .
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.
2.7.405 TPTFAIL (FCMR)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: FCMR
The Transport Fail alarm is raised against a local Fibre Channel (FC) port on an FC_MR-4 card when
the port receives another SONET error such as AIS-P, page 36
;
;
;
(for VCAT only), or
(for VCAT only).
2-240
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.406 TPTFAIL (G1000)
This TPTFAIL can be raised against Fibre Channel cards if the remote FC card port is down from
SIGLOSS or SYNCLOSS. In that case, the remote FC card port sends a PDI-P error code in the SONET
C2 byte and signals the local FC port transmitter to turn off (thus causing the local FC port to raise the
TPTFAIL alarm). A TPTFAIL can also be raised when a far-end receive fiber is pulled. This alarm can be demoted when a facility loopback is placed on the FC_MR-4 port.
Clear the TPTFAIL (FCMR) Alarm
Step 1
Step 2
Find and clear any path alarms applying to the port. Refer to the correct section of this chapter for trouble clearing instructions. Clearing the path alarm also clears the TPTFAIL.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.406 TPTFAIL (G1000)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: G1000
The Transport Layer Failure alarm for the G-Series Ethernet card indicates a break in the end-to-end
Ethernet link integrity feature of the ONS 15454 G1000-4 cards. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.
The TPTFAIL alarm indicates a problem on either the SONET path or the remote Ethernet port that prevents the complete end-to-end Ethernet path from working. If any SONET path alarms such as the
, the
, the “PDI-P” alarm on page 2-186 , or
the “UNEQ-P” alarm on page 2-245
exist on the SONET path used by the Ethernet port, the affected port causes a TPTFAIL alarm. Also, if the far-end G1000-4 port Ethernet port is administratively disabled or it is reporting the
“CARLOSS (G1000)” alarm on page 2-60
, the C2 byte in the SONET path overhead indicates the
, which in turn causes a TPTFAIL to be reported against the near-end port.
When a TPTFAIL alarm occurs, the near-end port is automatically disabled (transmit laser turned off).
In turn, the laser shutoff can also cause the external Ethernet device attached at the near end to detect a link down and turn off its transmitter. This also causes a CARLOSS alarm to occur on the reporting port.
In all cases, the source problem is either in the SONET path being used by the G1000-4 port or the far- end G1000-4 port to which it is mapped.
An occurrence of TPTFAIL on an ONS 15454 G1000-4 port indicates either a problem with the SONET path that the port is using or with the far-end G1000-4 port that is mapped to the port.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the TPTFAIL (G1000) Alarm
Step 1 Clear any alarms being reported by the OC-N card on the G1000-4 circuit.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-241
Chapter 2 Alarm Troubleshooting
2.7.407 TPTFAIL (ML100T, ML1000, MLFX)
Step 2
Step 3
If no alarms are reported by the OC-N card, or if the
“PDI-P” condition on page 2-186 is reported, the
problem could be on the far-end G1000-4 port. Clear any alarms, such as CARLOSS, reported against the far-end port or card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.407 TPTFAIL (ML100T, ML1000, MLFX)
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: ML100T, ML1000, MLFX
The TPT Layer Failure alarm for the ML-Series Ethernet card indicates a break in the end-to-end packet-over-SONET (POS) link integrity feature of the ML-Series POS cards. TPTFAIL indicates a far-end condition or misconfiguration of the POS port.
The TPTFAIL alarm indicates a problem on the SONET path, a problem on the remote POS port, or a misconfiguration of the POS port that prevents the complete end-to-end POS path from working. If any
SONET path alarms such as the “AIS-P” condition on page 2-36 , the
, the
“PDI-P” condition on page 2-186 , or the
“UNEQ-P” alarm on page 2-245 exist on the circuit used by the
POS port, the affected port could report a TPTFAIL alarm. If the far-end ML POS port is
administratively disabled, it inserts an “AIS-P” condition on page 2-36
that is detected by the near-end port. The near-end port could report TPTFAIL in this event. If the POS port is misconfigured at the
Cisco IOS CLI level, the misconfiguration causes the port to go down and report TPTFAIL.
Note For more information about the ML-Series Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm
Step 1
Step 2
Step 3
Step 4
If there are no SONET alarms reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Ethernet Card Software Feature and Configuration Guide for the
Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 for configuration information.
If the
is the only one reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Ethernet Card Software Feature and Configuration
Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 for configuration information.
If the
“PDI-P” condition on page 2-186
is the only one reported against the POS port circuit and the circuit is terminated by a G-Series card, determine whether a
“CARLOSS (G1000)” alarm on page 2-60
is reported against the G-Series card, and if so, complete the
“Clear the CARLOSS (G1000) Alarm” procedure on page 2-61 .
If the
“AIS-P” alarm on page 2-36 , the
, or the
is present, clear those alarms using the procedures in those sections.
2-242
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.408 TRMT
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.408 TRMT
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: DS1, E1
A Missing Transmitter alarm occurs when there is a transmit failure on the ONS 15454 DS-1 card because of an internal hardware failure. The card must be replaced.
Clear the TRMT Alarm
Step 1
Step 2
Complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the reporting DS-1 card.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.409 TRMT-MISS
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: DS1, E1
A Facility Termination Equipment Transmitter Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance is detected when a transmit cable is missing on the DS-1 port or the backplane does not match the inserted card. For example, an SMB connector or a BNC connector could be connected to a DS-1 card instead of a DS-3 card.
Note DS-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.
Clear the TRMT-MISS Alarm
Step 1
Step 2
Step 3
Step 4
Verify that the device attached to the DS-1 port is operational.
If the device is operational, verify that the cabling is securely connected.
If the cabling is secure, verify that the pinouts are correct.
If the pinouts are correct, replace the transmit cable.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-243
Chapter 2 Alarm Troubleshooting
2.7.410 TX-AIS
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.410 TX-AIS
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3, E1
The (TX) Transmit Direction AIS condition is raised by the ONS 15454 backplane when it receives a far-end DS-1 LOS.
Clear the TX-AIS Condition
Step 1
Step 2
Step 3
Determine whether there are alarms on the downstream nodes and equipment, especially the
(OCN)” alarm on page 2-158 , or OOS ports.
Clear the downstream alarms using the applicable procedures in this chapter.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.411 TX-LOF
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, E1
The Transmit Direction LOF condition is transmitted by the backplane when it receives a DS-1 TX-LOF.
This alarm is raised only at the transmit (egress) side.
Clear the TX-LOF Condition
Step 1
Step 2
Complete the “Clear the LOF (DS1) Alarm” procedure on page 2-142
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.412 TX-RAI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: DS1, DS3, E1
2-244
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.413 UNC-WORD
The Transmit Direction RAI condition is transmitted by the backplane when it receives a DS-1 TX-AIS.
This alarm is raised only at the transmit side, but RAI is raised at both ends.
Note The DS1-56 card operating in retiming mode reports a Transmit Condition remote alarm indication
(TX-RAI) alarm in the alarm log. However, the physical signal that is transmitted out does not have TX-
RAI in the frame. Hence, TX-RAI is not transmitted in the DS1 signal. This causes the client equipment not to detect TX-RAI in the incoming signal.
Clear the TX-RAI Condition
Step 1
Step 2
Complete the
“Clear the TX-AIS Condition” procedure on page 2-244
.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.413 UNC-WORD
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.414 UNEQ-P
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: STSMON, STSTRM
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 could result from a PARTIAL circuit or an empty VT tunnel. UNEQ-P occurs in the node that terminates a path.
Note If a newly created circuit has no signal, a UNEQ-P alarm is reported on the OC-N cards and the
“AIS-P” condition on page 2-36
is reported on the terminating cards. These alarms clear when the circuit carries a signal.
Caution Deleting a circuit affects traffic.
Clear the UNEQ-P Alarm
Step 1
Step 2
Step 3
In node view, choose Go to Network View from the View menu .
Right-click the alarm to display the Select Affected Circuits shortcut menu.
Click Select Affected Circuits .
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 2-245
Chapter 2 Alarm Troubleshooting
2.7.414 UNEQ-P
Step 4
Step 5
Step 6
When the affected circuits appear, look in the Type column for VTT, which indicates a VT tunnel circuit.
A VT tunnel with no VTs assigned could be the cause of an UNEQ-P alarm.
If the Type column does not contain VTT, there are no VT tunnels connected with the alarm. Go to
.
If the Type column does contain VTT, attempt to delete these rows:
Note The node does not allow you to delete a valid VT tunnel or one with a valid VT circuit inside.
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12 a.
a.
Click the VT tunnel circuit row to highlight it. Complete the
“Delete a Circuit” procedure on page 2-268
.
b.
c.
If an error message dialog box appears, the VT tunnel is valid and not the cause of the alarm.
If any other rows contain VTT, repeat
.
If all nodes in the ring appear in the CTC network view, determine whether the circuits are complete:
Click the Circuits tab.
b.
Verify that PARTIAL is not listed in the Status column of any circuits.
If you find circuits listed as PARTIAL, use an optical test set to verify that these circuits are not working circuits that continue to pass traffic. For specific procedures to use the test set equipment, consult the manufacturer.
If the PARTIAL circuits are not needed or are not passing traffic, delete the PARTIAL circuits.
Complete the “Delete a Circuit” procedure on page 2-268
.
Recreate the circuit with the correct circuit size. Refer to the “Create Circuits and VT Tunnels” chapter in the Cisco ONS 15454 Procedure Guide.
Log back in and verify that all circuits terminating in the reporting card are active: a.
b.
Click the Circuits tab.
Verify that the Status column lists all circuits as active.
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 “Maintain the Node” chapter of the Cisco ONS 15454 Procedure
Guide .
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
2-246
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.415 UNEQ-V
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 13
Step 14
If the alarm does not clear, complete the
“Physically Replace a Traffic Card” procedure on page 2-266
for the OC-N and electrical cards.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.415 UNEQ-V
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: VT-MON, VT-TERM
An SLMF UNEQ VT alarm indicates that the node is receiving SONET path overhead with Bits 5, 6, and 7 of the V5 overhead byte all set to zeroes. The source of the problem is not the node raising the alarm, but the node transmitting the VT signal to it. The V in UNEQ-V indicates that the failure has occurred at the VT layer.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position
(labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 .
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of
100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057
Clear the UNEQ-V Alarm
Step 1 Complete the
“Clear the UNEQ-P Alarm” procedure on page 2-245
.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-247
Chapter 2 Alarm Troubleshooting
2.7.416 UNREACHABLE-TARGET-POWER
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.
2.7.416 UNREACHABLE-TARGET-POWER
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.417 UT-COMM-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.418 UT-FAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.419 VCG-DEG
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: VCG
The VCAT Group Degraded alarm is a VCAT group alarm. (VCATs are groups of independent circuits that are concatenated from different time slots into higher-rate signals.) The alarm occurs when one member circuit carried by the ML-Series Ethernet card is down. This alarm is accompanied by the
“OOU-TPT” alarm on page 2-184 . It only occurs when a Critical (CR) alarm, such as LOS, causes a
signal loss.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the VCG-DEG Condition
Step 1
Step 2
Look for and clear any Critical (CR) alarms that apply to the errored card, such as the
or
“LOS (OTS)” alarm, page 2-160 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2-248
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.420 VCG-DOWN
2.7.420 VCG-DOWN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: VCG
The VCAT Group Down alarm is a VCAT group alarm. (VCATs are groups of independent circuits that are concatenated from different time slots into higher-rate signals.) The alarm occurs when one or more member circuits carried by an ML-Series or CE-Series Ethernet card are down. This alarm occurs in conjunction with another Critical (CR) alarm, such as the
.
Note If LCAS (Link Capacity Adjustment Scheme) is not enabled, the VCAT group transitions to the down state with even a single member down. If SW-LCAS is enabled on the VCAT group for ML1 cards, or
HW LCAS is enabled for CE cards, the VCAT group transitions to the VCG-DOWN state only when all the members are down. The presence of at least one working member causes the VCAT group to remain in VCG-DEG (VCG degraded) state.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Clear the VCG-DOWN Condition
Step 1
Step 2
Complete the
“Clear the VCG-DEG Condition” procedure on page 2-248 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.421 VOA-HDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.422 VOA-HFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.423 VOA-LDEG
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-249
Chapter 2 Alarm Troubleshooting
2.7.424 VOA-LFAIL
2.7.424 VOA-LFAIL
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.7.425 VOLT-MISM
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: PWR
The Power Monitoring Mismatch Between Control Cards alarm is raised against the shelf when the power voltages of both TCC2/TCC2Ps are out of range of each other by more than 5 VDC.
Clear the VOLT-MISM Condition
Step 1
Step 2
Step 3
Check the incoming voltage level to the shelf using a voltmeter. Follow site practices or refer to the
“Install the Shelf and Backplane Cable” chapter in the Cisco ONS 15454 Procedure Guide for power installation procedures.
Correct any incoming voltage issues.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.426 VT-SQUELCH-L
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Ring is Squelching VT Traffic condition is raised on an OC-N facility. If the node failure scenario includes the source node, the node dropping VT will squelch VT traffic. The condition resolves when the node failure is recovered.
This condition is raised as NA severity by default. However, it indicates that traffic is squelched due to node failure, that is, traffic outage. Traffic outage can be caused by different problems, such as multiple instances of the
“LOS (OCN)” alarm, page 2-158 , the
“AIS-L” condition on page 2-35 , or node power
outage. VT-SQUELCH-L is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what causes node isolation.
Note VT-SQUELCH-L is an informational condition.
2.7.427 WKSWPR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, OCN, STSMON, VT-MON
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC
2-250
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.7.428 WTR
The Working Switched To Protection condition occurs when a line experiences the
“LOS (OCN)” alarm on page 2-158 , the
“SD (DS1, DS3)” condition on page 2-210 , or the
“SD (TRUNK)” condition on page 2-213
.
This condition is also raised when you use the FORCE SPAN, FORCE RING or MANUAL SPAN command at the network level. WKSWPR is visible on the network view Alarms, Conditions, and
History tabs.
Clear the WKSWPR Condition
Step 1
Step 2
Complete the
“Clear the LOS (OCN) Alarm” procedure on page 2-159 .
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.428 WTR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Objects: EQPT, ML1000, ML100T, MLFX, OCN, STSMON, VT-MON
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK
cannot revert to the working path. The condition clears when the timer expires and traffic switches back to the working path.
If the condition is raised on an IEEE 802.17b-based RPR span, it indicates that the wait-to-restore timer is active after a span failure has cleared.
Caution DS-1 traffic loss can occur on a DS-1 with 1:N protection if a DS-1 card is reset with the protect card in the WTR state.
Note Generally, WTR is an informational condition and does not require troubleshooting.
Clear the WTR Condition on an IEEE 802.17b-Based RPR Span
Step 1
Step 2
Determine the setting for the IEEE 802.17b-based RPR interface’s WTR timer setting. In privileged executive mode, enter the following command: router# show interface rpr protection
View the WTR timer setting.
If the timer is set to “never,” clear the WTR condition by requesting a forced switch on the span. Enter the following command at the RPR-IEEE interface configuration mode command prompt: router(config-if)#rpr-ieee protection request force-switch {east | west}
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-251
Chapter 2 Alarm Troubleshooting
2.7.429 WVL-MISMATCH
Step 3
Step 4
If you configured a FORCE on the span, clear the switch with the following command: router(config-if)#no rpr-ieee protection request force-switch {east | west}
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.429 WVL-MISMATCH
For information about this alarm or condition, refer to the “Alarm Troubleshooting” chapter in the
Cisco ONS 15454 DWDM Troubleshooting Guide . This guide discusses all DWDM alarms.
2.8 Traffic Card LED Activity
ONS 15454 traffic card LED behavior patterns are listed in the following sections. These sections give behavior for card insertion, reset, and side-switch.
2.8.1 Typical Traffic Card LED Activity After Insertion
When a card is inserted, the following LED activities occur:
1.
The red FAIL LED turns on and remains illuminated for 20 to 30 seconds.
2.
3.
4.
The red FAIL LED blinks for 35 to 45 seconds.
All LEDs blink once and turn off for 5 to 10 seconds.
The ACT or ACT/SBY LED turns on. The SF LED can persist until all card ports connect to their far-end counterparts and a signal is present.
2.8.2 Typical Traffic Card LED Activity During Reset
While a card resets, the following LED activities occur:
1.
2.
3.
The FAIL LED on the physical card blinks and turns off.
The white LED with the letters “LDG” appears on the reset card in CTC.
The green ACT LED appears in CTC.
2.8.3 Typical Card LED State After Successful Reset
When a card successfully resets, the following LED states are present:
•
•
If you are looking at the physical ONS 15454, the ACT/SBY LED is illuminated.
If you are looking at node view of the ONS 15454, the current standby card has an amber LED depiction with the initials “SBY,” and this has replaced the white “LDG” depiction on the card in
CTC.
2-252
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.8.4 Typical Cross-Connect LED Activity During Side Switch
• If you are looking at node view of the ONS 15454, the current active card has a green LED depiction with the initials “ACT,” and this has replaced the white “LDG” depiction on the card in CTC.
2.8.4 Typical Cross-Connect LED Activity During Side Switch
When a XC10G card is switched in CTC from active (ACT) to standby (SBY) or from SBY to ACT, the following LED activities occur:
1.
The FAIL LED on the physical card blinks and turns off.
2.
3.
The standby card yellow SBY LED becomes a green ACT LED, indicating it is now active.
The active card green ACT LED becomes a yellow SBY LED, indicating it is now standby.
2.9 Frequently Used Alarm Troubleshooting Procedures
This section gives common procedures that are frequently used when troubleshooting alarms. Most of these procedures are summarized versions of fuller procedures existing elsewhere in the ONS 15454 documentation. They are included in this chapter for the user’s convenience. For further information, please refer to the Cisco ONS 15454 Procedure Guide .
2.9.1 Node and Ring Identification, Change, Visibility, and Termination
The following procedures relate how to identify or change BLSR names and node IDs, and how to verify visibility from other nodes.
Identify a BLSR Ring Name or Node ID Number
Step 1
Step 2
Step 3
Step 4
Log into a node on the network.
In node view, choose Go to Network View from the View menu .
Click the Provisioning > BLSR tabs.
From the Ring Name column, record the ring name, or in the Nodes column, record the Node IDs in the
BLSR. The Node IDs are the numbers in parentheses next to the node name.
Change a BLSR Ring Name
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Log into a node on the network.
In node view, choose Go to Network View from the View menu .
Click the Provisioning > BLSR tabs.
Highlight the ring and click Edit .
In the BLSR window, enter the new name in the Ring Name field.
Click Apply .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-253
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Step 7 Click Yes in the Changing Ring Name dialog box.
Change a BLSR Node ID Number
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
In node view, choose Go to Network View from the View menu .
Click the Provisioning > BLSR tabs.
Highlight the ring and click Edit .
In the BLSR window, right-click the node on the ring map.
Select Set Node ID from the shortcut menu.
In the Edit Node ID dialog box, enter the new ID. The Node ID is the number in parentheses after the
Node Name.
Click OK .
Verify Node Visibility for Other Nodes
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Log into a node on the network.
In node view, click the Provisioning > BLSR tabs.
Highlight a BLSR.
Click Ring Map .
In the BLSR Ring Map window, verify that each node in the ring appears on the ring map with a node
ID and IP address.
Click Close .
2.9.2 Protection Switching, Lock Initiation, and Clearing
The following sections give instructions for port, ring, and span switching and switch-clearing commands, as well as lock-ons and lockouts.
Initiate a 1+1 Force Switch Command
This procedure switches 1+1 protection group traffic from one port in the group to the other using a
Force switch.
Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.
2-254
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Caution Traffic is not protected during a Force protection switch.
Note A Force command switches traffic on a working path even if the path has signal degrade (SD) or signal fail (SF) conditions. A Force switch does not switch traffic on a protect path. A Force switch preempts a Manual switch.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, click the Maintenance > Protection tabs.
In the Protection Groups area, select the protection group with the port you want to switch.
In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the
Protect/Standby port, click this port.
In the Switch Commands area, click Force .
Click Yes in the Confirm Force Operation dialog box.
If the switch is successful, the group says “Force to working” in the Selected Groups area.
Initiate a 1+1 Manual Switch Command
This procedure switches 1+1 protection group traffic from one port in the group to the other using a
Manual switch.
Note A Manual command switches traffic if the path has an error rate less than the signal degrade. A Manual switch is preempted by a Force switch.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, click the Maintenance > Protection tabs.
In the Protection Groups area, select the protection group with the port you want to switch.
In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the protect/standby port, click this port.
In the Switch Commands area, click Manual .
Click Yes in the Confirm Force Operation dialog box.
If the switch is successful, the group now says “Manual to working” in the Selected Groups area.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-255
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Clear a 1+1 Force or Manual Switch Command
Note If the 1+1 protection group is configured as revertive, clearing a Force switch to protect (or working) moves traffic back to the working port. In revertive operation, the traffic always switches back to working. There is no revert to the protect. If ports are not configured as revertive, clearing a Force switch to protect does not move traffic back.
Note If the Force Switch was user-initiated, the reversion occurs immediately when the clear command is issued. The five-minute WTR period is not needed in this case. If the Force was system-initiated, allow the five-minute waiting period (during WTR) before the reversion occurs.
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, click the Maintenance > Protection tabs.
In the Protection Groups area, choose the protection group containing the port you want to clear.
In the Selected Group area, choose the port you want to clear.
In the Switching Commands area, click Clear .
Click Yes in the Confirmation Dialog box.
The Force switch is cleared. Traffic immediately reverts to the working port if the group was configured for revertive switching.
Initiate a Lock-On Command
Note For 1:1 and 1:N electrical protection groups, working or protect cards can be placed in the Lock On state.
For a 1+1 optical protection group, only the working port can be placed in the Lock On state.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In node view, click the Maintenance > Protection tabs.
In the Protection Groups list, click the protection group where you want to apply a lock-on.
If you determine that the protect card is in standby mode and you want to apply the lock-on to the protect card, make the protect card active if necessary: a.
b.
In the Selected Group list, click the protect card.
In the Switch Commands area, click Force .
In the Selected Group list, click the active card where you want to lock traffic.
In the Inhibit Switching area, click Lock On .
Click Yes in the confirmation dialog box.
2-256
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Initiate a Card or Port Lockout Command
Note For 1:1 or 1:N electrical protection groups, working or protect cards can be placed in the Lock Out state.
For a 1+1 optical protection group, only the protect port can be placed in the Lock Out state.
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, click the Maintenance > Protection tabs.
In the Protection Groups list, click the protection group that contains the card you want to lockout.
In the Selected Group list, click the card where you want to lock out traffic.
In the Inhibit Switching area, click Lock Out .
Click Yes in the confirmation dialog box.
The lockout has been applied and traffic is switched to the opposite card.
Clear a Lock-On or Lockout Command
Step 1
Step 2
Step 3
Step 4
Step 5
In node view, click the Maintenance > Protection tabs.
In the Protection Groups list, click the protection group that contains the card you want to clear.
In the Selected Group list, click the card you want to clear.
In the Inhibit Switching area, click Unlock .
Click Yes in the confirmation dialog box.
The lock-on or lockout is cleared.
Initiate a 1:1 Card Switch Command
Note The Switch command only works on the Active card, whether it is working or protect. It does not work on the Standby card.
Step 1
Step 2
Step 3
Step 4
In node view, click the Maintenance > Protection tabs.
Click the protection group that contains the card you want to switch.
Under Selected Group, click the active card.
Next to Switch Commands, click Switch .
The working slot sould change to Working/Active and the protect slot should change to Protect/Standby.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-257
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Initiate a Force Switch for All Circuits on a Path Protection Span
This procedure forces all circuits in a from the working span to the protect. It is used to remove traffic from a card that originates or terminates path protection circuits.
Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.
Caution Traffic is not protected during a Force protection switch.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 1
Step 2
Step 3
Log into a node on the network.
In node view, choose Go to Network View from the View menu .
Right-click a network span and choose Circuits .
The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
Click the Perform Path Protection span switching field.
Choose Force Switch Away from the drop-down list.
Click Apply .
In the Confirm Path Protection Switch dialog box, click Yes .
In the Protection Switch Result dialog box, click OK .
In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.
Initiate a Manual Switch for All Circuits on a Path Protection Span
This procedure manually switches all circuits in a path protection from the working span to the protect.
It is used to remove traffic from a card that originates or terminates path protection circuits.
Caution The Manual command does not override normal protective switching mechanisms.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 1
Step 2
Log into a node on the network.
Right-click a network span and choose Circuits .
The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
Click the Perform Path Protection span switching field.
Choose Manual from the drop-down list.
Click Apply .
In the Confirm Path Protection Switch dialog box, click Yes .
In the Protection Switch Result dialog box, click OK .
2-258
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
In the Circuits on Span dialog box, the switch state for all circuits is Manual. Unprotected circuits do not switch.
Initiate a Lockout for All Circuits on a Protect Path Protection Span
This procedure prevents all circuits in a path protection working span from switching to the protect span.
It is used to keep traffic off cards that originate or terminate path protection circuits.
Caution The Lock Out of Protect command overrides normal protective switching mechanisms.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 1
Step 2
Log into a node on the network. If you are already logged in, continue with
.
Right-click a network span and choose Circuits .
The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
Click the Perform Path Protection span switching field.
Choose Lock Out of Protect from the drop-down list.
Click Apply .
In the Confirm Path Protection Switch dialog box, click Yes .
In the Protection Switch Result dialog box, click OK .
In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.
Clear an External Switching Command on a Path Protection Span
Note If the ports terminating a span are configured as revertive, clearing a Force or Manual switch to protect moves traffic back to the working port. If ports are not configured as nonrevertive, clearing a Force switch to protect does not move traffic back.
Step 1
Step 2
Step 3
Log into a node on the network. If you are already logged in, continue with
.
Right-click a network span and choose Circuits .
The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
Initiate a Force switch for all circuits on the span: a.
d.
e.
b.
c.
Click the Perform Path Protection span switching field.
Choose Clear from the drop-down list.
Click Apply .
In the Confirm Path Protection Switch dialog box, click Yes .
In the Protection Switch Result dialog box, click OK .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-259
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
In the Circuits on Span dialog box, the switch state for all circuits is Clear. Unprotected circuits do not switch.
Initiate a Force Ring Switch on a BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network. If you are already logged in, continue with
From the View menu choose Go to Network View .
In network view, click the Provisioning > BLSR tabs.
Click the row of the BLSR you are switching, then click Edit .
Right-click a BLSR node west port and choose Set West Protection Operation .
In the Set West Protection Operation dialog box, choose Force Ring from the drop-down list.
Click OK .
Click Yes in the two Confirm BLSR Operation dialog boxes that appear.
Initiate a Force Span Switch on a Four-Fiber BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
From the View menu choose Go to Network View .
In network view, click the Provisioning > BLSR tabs.
Click the row of the BLSR you are switching, then click Edit .
Right-click a BLSR node west port and choose Set West Protection Operation .
In the Set West Protection Operation dialog box, choose Force Span from the drop-down list.
Click OK .
Click Yes in the two Confirm BLSR Operation dialog boxes that appear.
Initiate a Manual Span Switch on a BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
From the View menu, choose Go to Network View .
Click the Provisioning > BLSR tabs.
Choose the BLSR and click Edit .
Right-click the BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose
Manual Span from the drop-down list.
Click OK .
2-260
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.2 Protection Switching, Lock Initiation, and Clearing
Step 7 Click Yes in the two Confirm BLSR Operation dialog boxes.
Initiate a Manual Ring Switch on a BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
From the View menu, choose Go to Network View .
Click the Provisioning > BLSR tabs.
Choose the BLSR and click Edit .
Right-click the BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose
Manual Ring from the drop-down list.
Click OK .
Click Yes in the two Confirm BLSR Operation dialog boxes.
Initiate a Lockout on a BLSR Protect Span
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
From the View menu choose Go to Network View .
Click the Provisioning > BLSR tabs.
Choose the BLSR and click Edit .
Right-click the BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose
Lockout Protect Span from the drop-down list.
Click OK .
Click Yes in the two Confirm BLSR Operation dialog boxes.
Initiate an Exercise Ring Switch on a BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Log into a node on the network.
Click View > Go to Network View .
Click the Provisioning > BLSR tabs.
Click the row of the BLSR you are exercising, then click Edit .
Right-click the west port of a node and choose Set West Protection Operation .
In the Set West Protection Operation dialog box, choose Exercise Ring from the drop-down list.
Click OK .
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-261
Chapter 2 Alarm Troubleshooting
2.9.3 CTC Card Resetting and Switching
Step 8 Click Yes in the Confirm BLSR Operation dialog box.
Initiate an Exercise Ring Switch on a Four Fiber BLSR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
From the View menu, choose Go to Network View .
Click the Provisioning > BLSR tabs.
Click the row of the BLSR you are exercising, then click Edit .
Right-click the west port of a node and choose Set West Protection Operation .
In the Set West Protection Operation dialog box, choose Exercise Span from the drop-down list.
Click OK .
Click Yes in the Confirm BLSR Operation dialog box.
Clear a BLSR External Switching Command
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
From the View menu, choose Go to Network View .
Click the Provisioning > BLSR tabs.
Click the BLSR you want to clear.
Right-click the west port of the BLSR node where you invoked the switch and choose Set West
Protection Operation .
In the Set West Protection Operation dialog box, choose Clear from the drop-down list.
Click OK .
Click Yes in the Confirm BLSR Operation dialog box.
2.9.3 CTC Card Resetting and Switching
This section gives instructions for resetting traffic cards, TCC2/TCC2Ps, and cross-connect cards.
Caution For TXP and MXP cards placed in a Y-cable protection group, do not perform a software reset on both cards simultaneously. Doing so will cause a traffic hit of more than one minute. For more information about Y-cable protection groups, refer to the Cisco ONS 15454 DWDM Procedure Guide .
Caution Resetting the active card in a Y-cable group will cause a traffic outage if the standby card is down for any reason.
2-262
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.3 CTC Card Resetting and Switching
Note When an AIC-I card is rest in CTC, any subsequent user client operations (such as CTC or TL1 activity) is paused for approximately 5-10 seconds. The reset does not cause any conditions to be raised.
Note For more information about MXP and TXP cards, refer to the Cisco ONS 15454 DWDM Reference
Manual .
Reset a Traffic Card in CTC
Step 1
Step 2
Step 3
Step 4
Log into a node on the network. If you are already logged in, continue with
.
In node view, position the cursor over the optical or electrical traffic card slot reporting the alarm.
Right-click the card. Choose Reset Card from the shortcut menu.
Click Yes in the Resetting Card dialog box.
Reset an Active TCC2/TCC2P Card and Activate the Standby Card
Caution Resetting an active TCC2/TCC2P can be service-affecting.
Note Before you reset the TCC2/TCC2P, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Log into a node on the network. If you are already logged in, continue with
.
Identify the active TCC2/TCC2P:
If you are looking at the physical ONS 15454 shelf, the ACT/SBY LED of the active card is green. The
ACT/STBLY LED of the standby card is amber.
Right-click the active TCC2/TCC2P in CTC.
Choose Reset Card from the shortcut menu.
Click Yes in the Confirmation Dialog box.
The card resets, the FAIL LED blinks on the physical card, and connection to the node is lost. CTC switches to network view.
Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the
“2.8.3 Typical Card LED State After Successful Reset” section on page 2-252 .
Double-click the node and ensure that the reset TCC2/TCC2P is in standby mode and that the other
TCC2/TCC2P is active. Verify the following:
• If you are looking at the physical ONS 15454 shelf, the ACT/SBY LED of the active card is green.
The ACT/STBLY LED of the standby card is amber.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-263
Chapter 2 Alarm Troubleshooting
2.9.4 Physical Card Reseating, Resetting, and Replacement
• No new alarms appear in the Alarms window in CTC.
Side Switch the Active and Standby Cross-Connect Cards
Caution The cross-connect card side switch is usually service-affecting.
Step 1
Step 2
Step 3
Log into a node on the network. For instructions regarding how to log into a node, refer Cisco ONS 15454
Procedure Guide, Release 8.0
. If you are already logged in, continue with Step 2
.
Display node view.
Determine the active or standby XC10G card.
The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.
Note You can also position the cursor over the card graphic to display a popup identifying the card as active or standby.
Step 4
Step 5
Step 6
In node view, click the Maintenance > Cross-Connect > Cards tabs.
Click Switch .
Click Yes in the Confirm Switch dialog box. See the
“2.8.4 Typical Cross-Connect LED Activity During
Side Switch” section on page 2-253
for LED information.
Note During a maintenance side switch or soft reset of an active XC10G card, the 1+1 protection group might display a protection switch. To disallow the protection switch from being displayed, the protection group should be locked at the node where XC switch or soft reset of an active XC switch is in progress.
Caution Active cross connect (XC10G/XCVT) cards should not be physically removed.
The following rules must be followed for removing an Active Cross Connect Card (XC10G/XCVT):
If the active cross connect has to be removed, perform an XCVT/XC10G side switch to change the status of the card from active to standby and then remove the cross connect card once it goes back to standby.
OR
Perform a lockout on all circuits that originate from the node whose active cross connect card has to be removed (performing a lockout on all spans will also accomplish the same goal).
2.9.4 Physical Card Reseating, Resetting, and Replacement
This section gives instructions for physically reseating and replacing TCC2/TCC2P, cross-connect, and traffic cards.
2-264
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.4 Physical Card Reseating, Resetting, and Replacement
Caution Do not physically replace a card without first making provisions to switch or move traffic to a different card or circuit. General procedures for this are located in the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
. In-depth traffic switching procedures and information can be found in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide.
Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Caution Do not perform this action without the supervision and direction of Cisco TAC 1 800 553-2447.
Caution The TCC2/TCC2P reseat could be service-affecting. Refer to the
“2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for traffic-switching procedures.
Note Before you reset the TCC2/TCC2P, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.
Note When a standby TCC2/TCC2P card is removed and reinserted (reseated), all three fan lights could momentarily turn on, indicating that the fans have also reset.
Step 1
Step 2
Step 3
Step 4
Log into a node on the network.
Ensure that the TCC2/TCC2P you want to reseat is in standby mode. A standby card has an amber
ACT/SBY (Active/Standby) LED illuminated.
When the TCC2/TCC2P is in standby mode, unlatch both the top and bottom ejectors on the
TCC2/TCC2P.
Physically pull the card at least partly out of the slot until the lighted LEDs turn off.
Wait 30 seconds. Reinsert the card and close the ejectors.
Note The TCC2/TCC2P requires several minutes to reboot and display the amber standby LED after rebooting. Refer to the Cisco ONS 15454 Reference Manual for more information about LED behavior during a card reboot.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-265
Chapter 2 Alarm Troubleshooting
2.9.4 Physical Card Reseating, Resetting, and Replacement
Remove and Reinsert (Reseat) Any Card
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Step 4
Open the card ejectors.
Slide the card halfway out of the slot along the guide rails.
Slide the card all the way back into the slot along the guide rails.
Close the ejectors.
Physically Replace a Traffic Card
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. refer to the procedures in the
“2.9.2 Protection Switching, Lock Initiation, and Clearing” section on page 2-254
. For more information, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide .
When you replace a card with the identical type of card, you do not need to make any changes to the database.
Step 1
Step 2
Step 3
Step 4
Step 5
Open the card ejectors.
Slide the card out of the slot.
Open the ejectors on the replacement card.
Slide the replacement card into the slot along the guide rails.
Close the ejectors.
Physically Replace an In-Service Cross-Connect Card
Caution
The cross-connect reseat could be service-affecting. Refer to the “2.9.2 Protection Switching, Lock
Initiation, and Clearing” section on page 2-254
for traffic-switching procedures prior to completing this procedure.
2-266
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.5 Generic Signal and Circuit Procedures
Note This procedure is placed in the chapter as a quick guide for the user’s convenience. A more detailed procedure is located in the “Maintain the Node” chapter of the Cisco ONS 15454 Procedure Guide .
When you replace a card with the identical type of card, you do not need to make any changes to the database.
Step 1 Determine the active cross-connect card (XCVT/XC10G/XC-VXC-10G). The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.
Note You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.
Step 2 Switch the active cross-connect card to standby: a.
b.
c.
In the node view, click the Maintenance > Cross-Connect tabs.
Under Cross Connect Cards, choose Switch .
Click Yes in the Confirm Switch dialog box.
Note After the active cross-connect card becomes standby, the original standby slot becomes active.
This causes the ACT/SBY LED to become green on the former standby card.
Step 3 Physically remove the new standby cross-connect card from the ONS 15454.
Note An improper removal (IMPROPRMVL) alarm is raised when a card reseat is performed, unless the card is first deleted in Cisco Transport Controller (CTC). The alarm clears after the card is replaced.
Step 4 Insert the replacement cross-connect card into the empty slot.
The replacement card boots up and becomes ready for service after approximately one minute.
2.9.5 Generic Signal and Circuit Procedures
This section gives instructions for verify BER thresholds, deleting circuits, provisioning SDCC terminations, and clearing loopbacks.
Verify the Signal BER Threshold Level
Step 1
Step 2
Step 3
Log into a node on the network.
In node view, double-click the card reporting the alarm to open the card view.
Click the Provisioning > Line tabs.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-267
Chapter 2 Alarm Troubleshooting
2.9.5 Generic Signal and Circuit Procedures
Step 4
Step 5
Step 6
Step 7
Under the SD BER (or SF BER ) column in the Provisioning window, verify that the cell entry is consistent with the originally provisioned threshold. The default setting is 1E-7.
If the entry is consistent with the original provisioning, go back to your original procedure.
If the entry is not consistent with what the system was originally provisioned for, click the cell to reveal the range of choices and click the original entry.
Click Apply .
Delete a Circuit
Step 1
Step 2
Step 3
Step 4
Log into a node on the network.
In node view, click the Circuits tab.
Click the circuit row to highlight it and click Delete .
Click Yes in the Delete Circuits dialog box.
Verify or Create Node Section DCC Terminations
Note Portions of this procedure are different for ONS 15454 DWDM nodes.
Step 1
Step 2
Step 3
Step 4
Log into a node on the network.
In node view, click the Provisioning > Comm Channels > SDCC tab.
View the Port column entries to see where terminations are present for a node. If terminations are missing, proceed to
If necessary, create a DCC termination: a.
Click Create .
b.
c.
d.
e.
In the Create SDCC Terminations dialog box, click the ports where you want to create the DCC termination. To select more than one port, press the Shift key.
In the port state area, click the Set to IS radio button.
Verify that the Disable OSPF on Link check box is unchecked.
Click OK .
Clear an OC-N Card Facility or Terminal Loopback Circuit
Step 1
Step 2
Step 3
Log into a node on the network.
Double-click the reporting card in CTC to open the card view.
Click the Maintenance > Loopback > Port tabs.
2-268
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.5 Generic Signal and Circuit Procedures
Step 4
Step 5
Step 6
Step 7
Step 8
In the Loopback Type column, determine whether any port row shows a state other than None.
If a row contains another state besides None, click in the column cell to display the drop-down list and select None.
In the Admin State column, determine whether any port row shows a state other than IS .
If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS .
Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
Clear an OC-N Card Cross-Connect (XC) Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Log into a node on the network.
Double-click the reporting card in CTC to open the card view.
Click the Maintenance > Loopback > SONET STS tabs.
Uncheck the XC Loopback check box.
Click Apply .
Clear a DS3XM-6, DS3XM-12, or DS3E-12 Card Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
Double-click the reporting card in CTC to open the card view.
Click the Maintenance > DS3 tabs or the Maintenance > DS1 tabs.
In the Loopback Type column, determine whether any port row shows a state other than None.
If a row contains another state besides None, click in the column cell to display the drop-down list and select None.
In the Admin State column, determine whether any port row shows a state other than IS .
If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS .
Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-269
Chapter 2 Alarm Troubleshooting
2.9.5 Generic Signal and Circuit Procedures
Clear Other Electrical Card or Ethernet Card Loopbacks
Note This procedure does not apply to DS3XM-6 or DS3XM-12 cards.
Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and
Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 .
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Log into a node on the network.
Double-click the reporting card in CTC to open the card view.
Click the Maintenance > Loopback tabs.
In the Loopback Type column, determine whether any port row shows a state other than None.
If a row contains another state besides None, click in the column cell to display the drop-down list and select None .
In the Admin State column, determine whether any port row shows a state other than IS .
If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS .
Click Apply .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
Clear an MXP, TXP, or FC_MR-4 Card Loopback Circuit
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Log into a node on the network.
Double-click the reporting card in CTC to open the card view.
Click the Maintenance > Loopback tabs.
In the Loopback Type column, determine whether any port row shows a state other than None.
If a row contains another state besides None, click in the column cell to display the drop-down list and select None.
In the Admin State column, determine whether any port row shows an admin state other than IS, for example, OOS,MT .
If a row shows an admin state other than IS, click in the column cell to display the drop-down list and select IS .
Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.
2-270
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.6 Air Filter and Fan Procedures
Step 8 Click Apply .
2.9.6 Air Filter and Fan Procedures
This section gives instructions for cleaning or replacing the air filter and reseating or replacing the fan tray assembly.
Inspect, Clean, and Replace the Reusable Air Filter
To complete this task, you need a vacuum cleaner or detergent and water faucet, a spare filter, and a pinned hex key.
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206
Although the filter works if it is installed with either side facing up, Cisco recommends that you install it with the metal bracing facing up to preserve the surface of the filter.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 1
Step 2
Step 3
Step 4
Step 5
Verify that you are replacing a reusable air filter. The reusable filter is made of a gray, open-cell, polyurethane foam that is specially coated to provide fire and fungi resistance. NEBS 3E and later versions of the ONS 15454 use a reusable air filter.
If the air filter is installed in the external filter brackets, slide the filter out of the brackets while being careful not to dislodge any dust that could have collected on the filter. If the filter is installed beneath the fan tray and not in the external filter brackets, open and remove the front door assembly by completing the following steps: a.
Open the front door of the shelf assembly by completing the following substeps.(If it is already open or if the shelf assembly does not have a front door, continue with
b.
•
•
Open the front door lock.
Press the door button to release the latch.
• Swing the door open.
Remove the front door by completing the following substeps (optional):
•
•
Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.
Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.
• Secure the dangling end of the ground strap to the door or chassis with tape.
Push the outer side of the handles on the fan-tray assembly to expose the handles.
Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.
When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-271
Chapter 2 Alarm Troubleshooting
2.9.6 Air Filter and Fan Procedures
Step 6
Step 7
Step 8
Gently remove the air filter from the shelf assembly. Be careful not to dislodge any dust that could have collected on the filter.
Visually inspect the air filter material for dirt and dust.
If the reusable air filter has a concentration of dirt and dust, either vacuum or wash the air filter. Prior to washing the air filter, replace the dirty air filter with a clean air filter and also reinsert the fan-tray assembly. Wash the dirty air filter under a faucet with a light detergent.
Spare ONS 15454 filters should be kept in stock for this purpose.
Note Cleaning should take place outside the operating environment to avoid releasing dirt and dust near the equipment.
Step 9 If you washed the filter, allow it to completely air dry for at least eight hours.
Caution Do not put a damp filter back in the ONS 15454.
Step 10
Step 11
If the air filter should be installed in the external filter brackets, slide the air filter all the way to the back of the brackets to complete the procedure.
If the filter should be installed beneath the fan-tray assembly, remove the fan-tray assembly and slide the air filter into the recessed compartment at the bottom of the shelf assembly. Put the front edge of the air filter flush against the front edge of the recessed compartment. Push the fan tray back into the shelf assembly.
Caution If the fan tray does not slide all the way to the back of the shelf assembly, pull the fan tray out and readjust the position of the reusable filter until the fan tray fits correctly.
Note On a powered-up ONS 15454, the fans start immediately after the fan-tray assembly is correctly inserted.
Step 12
Step 13
Step 14
To verify that the tray is plugged into the backplane, ensure that the LCD on the front of the fan-tray assembly is activated and displays node information.
Rotate the retractable handles back into their compartments.
Replace the door and reattach the ground strap.
Remove and Reinsert a Fan-Tray Assembly
Step 1
Step 2
Step 3
Use the retractable handles embedded in the front of the fan-tray assembly to pull it forward several inches.
Push the fan-tray assembly firmly back into the ONS 15454.
Close the retractable handles.
2-272
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.6 Air Filter and Fan Procedures
Replace the Fan-Tray Assembly
Caution The 15454-FTA3 fan-tray assembly can only be installed in ONS 15454 R3.1 and later shelf assemblies
(15454-SA-ANSI, P/N: 800-19857; 15454-SA-HD, P/N: 800-24848). It includes a pin that does not allow it to be installed in ONS 15454 shelf assemblies released before ONS 15454 R3.1
(15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1, P/N: 800-07149). Equipment damage can result from attempting to install the 15454-FTA3 in a incompatible shelf assembly.
Caution Do not force a fan-tray assembly into place. Doing so can damage the connectors on the fan tray and/or the connectors on the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
To replace the fan-tray assembly, it is not necessary to move any of the cable management facilities.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Open the front door of the shelf assembly by completing the following steps. If the shelf assembly does not have a front door, continue with
a.
Open the front door lock.
b.
c.
c.
Press the door button to release the latch.
Swing the door open.
Remove the front door (optional): a.
Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.
b.
Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.
Secure the dangling end of the ground strap to the door or chassis with tape.
Push the outer side of the handles on the fan-tray assembly to expose the handles.
Fold out the retractable handles at the outside edges of the fan tray.
Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.
When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.
If you are replacing the fan-tray air filter and it is installed beneath the fan-tray assembly, slide the existing air filter out of the shelf assembly and replace it before replacing the fan-tray assembly.
If you are replacing the fan-tray air filter and it is installed in the external bottom bracket, you can slide the existing air filter out of the bracket and replace it at anytime. For more information on the fan-tray air filter, see the
“Inspect, Clean, and Replace the Reusable Air Filter” section on page 2-271 .
Slide the new fan tray into the shelf assembly until the electrical plug at the rear of the tray plugs into the corresponding receptacle on the backplane.
To verify that the tray has plugged into the backplane, check that the LCD on the front of the fan tray is activated.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-273
Chapter 2 Alarm Troubleshooting
2.9.7 Interface Procedures
Step 10 If you replace the door, be sure to reattach the ground strap.
2.9.7 Interface Procedures
This section includes instructions for replacing an EIA and an AIP.
Replace the Electrical Interface Assembly
Note You need a #2 Phillips screwdriver. If you use high-density BNC EIAs, you also need a BNC insertion and removal tool.
Step 1
Step 2
Step 3
Step 4
To remove the lower backplane cover, loosen the five screws that secure it to the ONS 15454 and pull it away from the shelf assembly.
Loosen the nine perimeter screws that hold the backplane sheet metal cover or EIA in place. Do not remove the interior screws.
If you are removing an AMP Champ EIA, remove the fastening plate before proceeding. To remove the fastening plate, loosen the two thumbscrews.
If a backplane cover is attached to the ONS 15454, lift the panel by the bottom to remove it from the shelf assembly and store the panel for later use.
If an EIA is attached to the ONS 15454, lift the EIA handles and gently pull it away from the backplane.
Note Attach backplane sheet metal covers whenever EIAs are not installed.
Step 5
Step 6
Step 7
Step 8
Step 9
Line up the connectors on the new EIA with the mating connectors on the backplane.
Gently push the EIA until both sets of connectors fit together snugly.
Replace the nine perimeter screws that you removed while removing the backplane cover.
If you are installing an AMP Champ EIA, attach the fastening plate with the two thumbscrews.
Reattach the lower backplane cover.
Replace the Alarm Interface Panel
Caution Do not use a 2A AIP with a 5A fan-tray assembly; doing so causes a blown fuse on the AIP.
Caution If any nodes in an Ethernet circuit are not using Software R4.0 or later, there is a risk of Ethernet traffic disruptions. Contact Cisco TAC at 1 800 553-2447 when prompted to do so in the procedure.
2-274
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.7 Interface Procedures
Note Perform this procedure during a maintenance window. Resetting the active TCC2/TCC2P can cause a service disruption of less then 50 ms to OC-N or DS-N traffic. Resetting the active TCC2/TCC2P can cause a service disruption of 3 to 5 minutes on all Ethernet traffic due to spanning tree reconvergence if any nodes in the Ethernet circuit are not using Software R4.0 or later.
Caution Do not perform this procedure on a node with live traffic. Hot-swapping the AIP can affect traffic and result in a loss of data. For assistance with AIP replacement contact Cisco TAC 1 800 553-2447.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454.
Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
This procedure replaces an existing AIP with a new AIP on an in-service node without affecting traffic.
Ethernet circuits that traverse nodes with a software release prior to R4.0 is affected.
You need a #2 Phillips screwdriver.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Ensure that all nodes in the affected network are running the same software version before replacing the
AIP and repairing circuits: a.
b.
In network view, click the Maintenance > Software tabs. The working software version for each node is listed in the Working Version column.
If you need to upgrade the software on a node, refer to the release-specific software upgrade document for procedures. No hardware should be changed or circuit repair performed until after the software upgrade is complete. If you do not need to upgrade software or have completed the software
.
Record the MAC address of the old AIP: a.
b.
Log into the node where you are replacing the AIP. For login procedures, refer to the “Connect the
PC and Log into the GUI” chapter in the Cisco ONS 15454 Procedure Guide .
In node view, click the Provisioning > Network > General tabs.
Record the MAC address.
c.
Call Cisco TAC 1 800 553-2447 for assistance in replacing the AIP and maintaining the original MAC address.
Unscrew the five screws that hold the lower backplane cover in place.
Grip the lower backplane cover and gently pull it away from the backplane.
Unscrew the two screws that hold the AIP cover in place.
Grip the cover and gently pull away from the backplane.
Step 8
Step 9
Note On the 15454-SA-HD (P/N: 800-24848), 15454-SA-NEBS3E, 15454-SA-NEBS3, and
15454-SA-R1 (P/N: 800-07149) shelves the AIP cover is clear plastic. On the 15454-SA-ANSI shelf (P/N: 800-19857), the AIP cover is metal.
Grip the AIP and gently pull it away from the backplane.
Disconnect the fan-tray assembly power cable from the AIP.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-275
Chapter 2 Alarm Troubleshooting
2.9.7 Interface Procedures
Step 10 Set the old AIP aside for return to Cisco.
Caution The type of shelf the AIP resides in determines the version of AIP that should replace the failed AIP. The
15454-SA-ANSI shelf (P/N: 800-19857) and 15454-SA-HD (P/N: 800-24848) currently use the 5A AIP,
(P/N: 73-7665-01). The 15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1 (P/N: 800-07149) shelves and earlier use the 2A AIP (P/N: 73-5262-01).
Caution Do not put a 2A AIP (P/N: 73-5262-01) into a 15454-SA-ANSI (P/N: 800-19857) or 15454-SA-HD
(P/N: 800-24848) shelf; doing so causes a blown fuse on the AIP.
Step 11
Step 12
Step 13
Step 14
Step 15
Attach the fan-tray assembly power cable to the new AIP.
Place the new AIP on the backplane by plugging the panel into the backplane using the DIN connector.
Replace the AIP cover over the AIP and secure the cover with the two screws.
Replace the lower backplane cover and secure the cover with the five screws.
In node view, click the Provisioning > Network tabs.
Caution Cisco recommends TCC2/TCC2P resets be performed in a maintenance window to avoid any potential service disruptions.
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Reset the standby TCC2/TCC2P: a.
b.
Right-click the standby TCC2/TCC2P and choose Reset Card .
Click Yes in the Resetting Card dialog box. As the card resets, a loading (Ldg) indication appears on the card in CTC.The reset takes approximately five minutes. Do not perform any other steps until the reset is complete.
Reset the active TCC2/TCC2P: a.
Right click the active TCC2/TCC2P and choose Reset Card .
b.
Click Yes in the Resetting Card dialog box. As the card resets, a Ldg indication appears on the card in CTC. The reset takes approximately five minutes and CTC loses its connection with the node.
From the File drop-down list, choose Exit to exit the CTC session.
Log back into the node. At the Login dialog box, choose (None) from the Additional Nodes drop-down list.
Record the new MAC address: a.
b.
In node view, click the Provisioning > Network > General tabs.
Record the MAC address.
In node view, click the Circuits tab. Note that all circuits listed are PARTIAL.
In node view, choose Repair Circuits from the Tools drop-down list. The Circuit Repair dialog box appears.
Read the instructions in the Circuit Repair dialog box. If all the steps in the dialog box have been completed, click Next . Ensure that you have the old and new MAC addresses.
The Node MAC Addresses dialog box appears. Complete the following steps: a.
From the Node drop-down list, choose the name of the node where you replaced the AIP.
2-276
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 2 Alarm Troubleshooting
2.9.7 Interface Procedures
Step 25
Step 26
Step 27 b.
In the Old MAC Address field, enter the old MAC address that was recorded in
c.
Click Next .
The Repair Circuits dialog box appears. Read the information in the dialog box and click Finish .
The CTC session freezes until all circuits are repaired. Circuit repair can take up to five minutes or more depending on the number of circuits provisioned on it.
When the circuit repair is complete, the Circuits Repaired dialog box appears.
Click OK .
In the node view of the new node, click the Circuits tab. Note that all circuits listed are DISCOVERED.
If all circuits listed do not have a DISCOVERED status, call the Cisco TAC 1 800 553-2447 to open a
Return Material Authorization (RMA).
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
2-277
2.9.7 Interface Procedures
Chapter 2 Alarm Troubleshooting
2-278
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
C H A P T E R
3
Transient Conditions
This chapter gives a description, entity, SNMP number, and trap for each commonly encountered
Cisco ONS 15454 transient condition.
3.1 Transients Indexed By Alphabetical Entry
alphabetically lists all ONS 15454 transient conditions and their entity, SNMP number, and
SNMP trap.
Note The CTC default alarm profile might contain conditions that are not currently implemented but are reserved for future use.
Table 3-1 ONS 15454 Transient Condition Alphabetical Index
Transient Condition
Entity
NE
3.3.2 ADMIN-DISABLE-CLR, page 3-4
NE
NE
3.3.4 ADMIN-LOCKOUT-CLR, page 3-4
NE
NE
NE
3.3.7 ADMIN-SUSPEND-CLR, page 3-5
NE
3.3.8 AUD-ARCHIVE-FAIL, page 3-5
EQPT
NE
3.3.11 DBBACKUP-FAIL, page 3-5
3.3.12 DBRESTORE-FAIL, page 3-5
OCN
EQPT
EQPT
NE
SNMP Number SNMP Trap
5270 disableInactiveUser
5280
5040
5050
5020 disableInactiveClear adminLockoutOfUser adminLockoutClear adminLogoutOfUser
5340
5350
6350
5690 suspendUser suspendUserClear archiveOfAuditLogFailed automaticWdmAnsFinish ed
2100
3724
3726
5230 blsrMultiNodeTableUpdat eCompleted databaseBackupFailed databaseRestoreFailed firewallHasBeenDisabled
Cisco ONS 15454 Troubleshooting Guide, R7.2
3-1 November 2009
Chapter 3 Transient Conditions
3.1 Transients Indexed By Alphabetical Entry
Table 3-1
Transient Condition
3.3.14 FRCDWKSWBK-NO-TRFSW, page 3-6
ONS 15454 Transient Condition Alphabetical Index (continued)
Entity
OCN
3.3.15 FRCDWKSWPR-NO-TRFSW, page 3-6
3.3.17 INTRUSION-PSWD, page 3-6
3.3.18 IOSCFG-COPY-FAIL, page 3-6
3.3.19 LOGIN-FAILURE-LOCKOUT, page 3-6
3.3.20 LOGIN-FAILURE-ONALRDY, page 3-7
3.3.21 LOGIN-FAILURE-PSWD, page
3.3.22 LOGIN-FAILURE-USERID, page
3.3.23 LOGOUT-IDLE-USER, page 3-7
3.3.24 MANWKSWBK-NO-TRFSW, page
3.3.25 MANWKSWPR-NO-TRFSW, page
3.3.28 PSWD-CHG-REQUIRED, page 3-8
3.3.31 SESSION-TIME-LIMIT, page 3-8
3.3.32 SFTWDOWN-FAIL, page 3-8
OCn
NE
NE
—
NE
NE
NE
NE
—
OCN
OCN
—
EQPT
NE
—
—
NE
EQPT
NE
NE
NE
EQPT,
OCN
6270
3480
5030
5100
5120
2640
SNMP Number SNMP Trap
5560 forcedSwitchBackToWor kingResultedInNoTraffic
Switch
5550 forcedSwitchToProtectRe sultedInNoTrafficSwitch securityIntrusionDetUser 5250
5240
3660
5080 securityIntrusionDetPwd iosConfigCopyFailed
5090 securityInvalidLoginLock edOutSeeAuditLog securityInvalidLoginAlre adyLoggedOnSeeAuditLo g
5070
3722
5110
5540 securityInvalidLoginPass wordSeeAuditLog securityInvalidLoginUser nameSeeAuditLog automaticLogoutOfIdleU ser manualSwitchBackToWor kingResultedInNoTraffic
Switch
5530
2120
2130
6280
2720
2710 manualSwitchToProtectR esultedInNoTrafficSwitch performanceMonitorThre sholdCrossingAlert protectionSwitch userPasswordChangeReq uired rmonThresholdCrossingA larm rmonHistoriesAndAlarms
ResetReboot sessionTimeLimitExpired softwareDownloadFailed userLockedOut loginOfUser logoutOfUser switchedBackToWorking
3-2
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 3 Transient Conditions
3.2 Trouble Notifications
Table 3-1 ONS 15454 Transient Condition Alphabetical Index (continued)
Transient Condition
Entity
2R,
TRUNK,
EQPT,
ESCON,
FC, GE,
ISC, OCN,
STSMON,
VT-MON
NE
—
SNMP Number SNMP Trap
2650 switchedToProtection
2660
3420 warmRestart spanIsInWaitToRestoreSt ate
3.2 Trouble Notifications
The ONS 15454 system reports trouble by using standard condition characteristics that follow the rules in Telcordia GR-253 and graphical user interface (GUI) state indicators.
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and reports status or descriptive notifications (if configured to do so) as conditions in the CTC Alarms window. Alarms typically signify a problem that you need to remedy, such as a loss of signal. Conditions do not necessarily require troubleshooting.
3.2.1 Condition Characteristics
Conditions include any problem detected on an ONS 15454 shelf. They can include standing or transient notifications. You can retrieve a snapshot of all currently raised conditions on the network, node, or card in the CTC Conditions window or by using the RTRV-COND commands in TL1.
Note Some cleared conditions are found on the History tab.
For a comprehensive list of conditions, refer to the Cisco ONS SONET TL1 Command Guide .
3.2.2 Condition States
The History tab state (ST) column indicates the disposition of the condition, as follows:
•
•
•
A raised (R) event is active.
A cleared (C) event is no longer active.
A transient (T) event is automatically raised and cleared in CTC during system changes such as user login, log out, and loss of connection to node view. Transient events do not require user action.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
3-3
Chapter 3 Transient Conditions
3.3 Transient Conditions
3.3 Transient Conditions
This section lists in alphabetical order all the transient conditions encountered in Software Release 7.2.
The description, entity, SNMP number, and SNMP trap accompany each condition.
3.3.1 ADMIN-DISABLE
The Disable Inactive User (ADMIN-DISABLE) condition occurs when the administrator disables the user or the account is inactive for a specified period.
This transient condition does not result in a standing condition.
3.3.2 ADMIN-DISABLE-CLR
The Disable Inactive Clear (ADMIN-DISABLE-CLR) condition occurs when the administrator clears the disable flag on the user account.
This transient condition does not result in a standing condition.
3.3.3 ADMIN-LOCKOUT
The Admin Lockout of User (ADMIN-LOCKOUT) condition occurs when the administrator locks a user account.
This transient condition does not result in a standing condition.
3.3.4 ADMIN-LOCKOUT-CLR
The Admin Lockout Clear (ADMIN-LOCKOUT-CLR) condition occurs when the administrator unlocks a user account or the lockout time expires.
This transient condition does not result in a standing condition.
3.3.5 ADMIN-LOGOUT
The Admin Logout of User (ADMIN-LOGOUT) condition occurs when the administrator logs off a user session.
This transient condition does not result in a standing condition.
3.3.6 ADMIN-SUSPEND
The Suspend User (ADMIN-SUSPEND) condition occurs when the password for a user account expires.
This transient condition does not result in a standing condition.
3-4
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 3 Transient Conditions
3.3.7 ADMIN-SUSPEND-CLR
3.3.7 ADMIN-SUSPEND-CLR
The Suspend User Clear (ADMIN-SUSPEND-CLR) condition occurs when the user or administrator changes the password.
This transient condition does not result in a standing condition.
3.3.8 AUD-ARCHIVE-FAIL
The Archive of Audit Log Failed (AUD-ARCHIVE-FAIL) condition occurs when the software cannot archive the audit log. The condition normally occurs when the user refers to an FTP server that does not exist, or uses an invalid login when trying to archive. The user must log in again with correct user name, password, and FTP server details.
This transient condition does not result in a standing condition.
3.3.9 AUTOWDMANS
The Automatic WDM ANS Finish (AUTOWDMANS) condition indicates that an automatic node setup command has been initiated. It normally occurs when you replace DWDM cards; the condition is an indication that the system has regulated the card.
This transient condition does not result in a standing condition.
3.3.10 BLSR-RESYNC
The BLSR Multinode Table Update Completed (BLSR-RESYNC) condition might occur when you create or delete circuits on a bidirectional line switched ring (BLSR), change a ring topology (for example, add or delete a BLSR node), or change the BLSR circuit state and ring ID.
This transient condition does not result in a standing condition.
3.3.11 DBBACKUP-FAIL
The Database Backup Failed (DBBACKUP-FAIL) condition occurs when the system fails to back up the database when the backup command is initiated.
This condition can occur when the server is not able to handle the backup operation due to network or server issues. Repeat the same operation again and check to see if it is successful. If the backup fails, it could be due to a network issue or software program failure.
3.3.12 DBRESTORE-FAIL
The Database Restore Failed (DBRESTORE-FAIL) condition occurs when the system fails to restore the backed up database when the restore command is initiated.
This condition can be due to server issues, network issues, or human error (pointing to a file that does not exist, wrong file name, etc.). Retrying the database restore with the correct file will usually succeed.
If the network issue persists, you must contact network lab support. If the condition is caused by a network element (NE) failure, contact TAC for assistance. .
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 3-5
Chapter 3 Transient Conditions
3.3.13 FIREWALL-DIS
3.3.13 FIREWALL-DIS
The Firewall Has Been Disabled (FIREWALL-DIS) condition occurs when you provision the firewall to
Disabled.
This transient condition does not result in a standing condition.
3.3.14 FRCDWKSWBK-NO-TRFSW
The Forced Switch Back to Working Resulted in No Traffic Switch (FRCDWKSWBK-NO-TRFSW) condition occurs when you perform a Force Switch to the working port/card and the working port/card is already active.
This transient condition might result in a Force Switch (Ring or Span) standing condition for a BLSR.
3.3.15 FRCDWKSWPR-NO-TRFSW
The Forced Switch to Protection Resulted in No Traffic Switch (FRCDWKSWPR-NO-TRFSW) condition occurs when you perform a Force Switch to the protect port/card, and the protect port/card is already active.
This transient condition does not result in a standing condition.
3.3.16 INTRUSION
The Invalid Login Username (INTRUSION) condition occurs when you attempt to login with an invalid user ID.
This transient condition does not result in a standing condition.
3.3.17 INTRUSION-PSWD
The Security Intrusion Attempt Detected (INTRUSION -PSWD) condition occurs when you attempt to login with an invalid password.
This transient condition does not result in a standing condition.
3.3.18 IOSCFG-COPY-FAIL
The IOS Config Copy Failed (IOSCFG-COPY-FAIL) condition occurs on ML-Series Ethernet cards when the software fails to upload or download the Cisco IOS startup configuration file to or from an
ML-Series card. This condition is similar to the
“SFTWDOWN-FAIL” condition on page 3-8
, but the
IOSCFG-COPY-FAIL condition applies to ML-Series Ethernet cards rather than the TCC2/TCC2P card.
3.3.19 LOGIN-FAILURE-LOCKOUT
The Invalid Login–Locked Out (LOGIN-FAILURE-LOCKOUT) condition occurs when you attempt to log into a locked account.
Cisco ONS 15454 Troubleshooting Guide, R7.2
3-6 November 2009
Chapter 3 Transient Conditions
3.3.20 LOGIN-FAILURE-ONALRDY
This transient condition does not result in a standing condition.
3.3.20 LOGIN-FAILURE-ONALRDY
The Security: Invalid Login–Already Logged On (LOGIN-FAILURE-ONALRDY) condition occurs when you attempt to login to a node where the user already has an existing session and a
Single-User-Per-Node (SUPN) policy exists.
This transient condition does not result in a standing condition.
3.3.21 LOGIN-FAILURE-PSWD
The Invalid Login–Password (LOGIN-FAILURE-PSWD) condition occurs when you attempt to login with an invalid password.
This transient condition does not result in a standing condition.
3.3.22 LOGIN-FAILURE-USERID
The Invalid Login–Username (LOGIN-FAILURE-USERID) condition occurs when a user login (CTC,
CTM, or TL1) fails because the login username is not present on the node database. You must log in again with an existing user ID.
This transient condition is equivalent to a security warning. You must check the security log (audit log) for other security-related actions that have occurred.
3.3.23 LOGOUT-IDLE-USER
The Automatic Logout of Idle User (LOGOUT-IDLE-USER) condition occurs when a user session is idle for too long (the idle timeout expires) and the session terminates as a result. You must log in again to restart your session.
3.3.24 MANWKSWBK-NO-TRFSW
The Manual Switch Back To Working Resulted in No Traffic Switch (MANWKSWBK-NO-TRFSW) condition occurs when you perform a Manual switch to the working port/card and the working port/ card is already active.
This transient condition does not result in a standing condition.
3.3.25 MANWKSWPR-NO-TRFSW
The Manual Switch to Protect Resulted in No Traffic Switch (MANWKSWPR-NO-TRFSW) condition occurs when you perform a Manual switch to the protect port/card and the protect port/card is already active.
This transient condition results in a BLSR Manual Switch (Span or Ring) standing condition.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
3-7
Chapter 3 Transient Conditions
3.3.26 PM-TCA
3.3.26 PM-TCA
The Performance Monitor Threshold Crossing Alert (PM-TCA) condition occurs when network collisions cross the rising threshold for the first time.
3.3.27 PS
The Protection Switch (PS) condition occurs when the traffic switches from a working/active card to a protect/standby card.
3.3.28 PSWD-CHG-REQUIRED
The User Password Change Required (PSWD-CHG-REQUIRED) condition occurs when you are denied login for a shell function such as telnet or FTP because you did not change the login password. You can change the password through CTC or TL1.
3.3.29 RMON-ALARM
The RMON Threshold Crossing Alarm (RMON-ALARM) condition occurs when the remote monitoring variable crosses the threshold.
3.3.30 RMON-RESET
The RMON Histories and Alarms Reset Reboot (RMON-RESET) condition occurs when the time-of-day settings on the TCC2/TCC2P card are increased or decreased by more than five seconds.
This invalidates all the history data and remote monitoring (RMON) must restart. It can also occur when you reset a card.
3.3.31 SESSION-TIME-LIMIT
The Session Time Limit Expired (SESSION-TIME-LIMIT) condition occurs when a login session exceeds the time limit and you are logged out of the session. You must login again.
3.3.32 SFTWDOWN-FAIL
The Software Download Failed (SFTDOWN-FAIL) condition occurs when the system fails to download the required software.
An incorrect input that points to the wrong place or file, network issues, or a bad (corrupt) package can cause this failure. Retrying the operation with the correct name/location will usually succeed. If network issues persist, you must contact the network lab support.
3-8
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 3 Transient Conditions
3.3.33 USER-LOCKOUT
3.3.33 USER-LOCKOUT
The User Locked Out (USER-LOCKOUT) condition occurs when the system locks an account because of a failed login attempt. To proceed, the administrator must unlock the account or the lockout time must expire.
3.3.34 USER-LOGIN
The Login of User (USER-LOGIN) occurs when you begin a new session by verifying your User ID and password.
This transient condition does not result in a standing condition.
3.3.35 USER-LOGOUT
The Logout of User (USER-LOGOUT) condition occurs when you stop a login session by logging out of your account.
This transient condition does not result in a standing condition.
3.3.36 WKSWBK
The Switched Back to Working (WKSWBK) condition occurs when traffic switches back to the working port/card in a non-revertive protection group.
This transient condition does not result in a standing condition.
3.3.37 WKSWPR
The Switched to Protection (WKSWPR) condition occurs when traffic switches to the protect port/card in a non-revertive protection group. This transient condition does not result in a standing condition. The
(WKSWPR) is raised as a standing condition in a revertive protection group.
The Switched to Protection (WKSWPR) condition also occurs after the protection switch in a 1+1 non-revertive protection group as a transient condition. When the protection group is changed to revertive, the (WKSWPR) is not raised as a standing condition or as a new transient condition. However, after a protection switch in a 1:1 protection group, the user will not be allowed to configure the protection group from non-revertive to revertive.
3.3.38 WRMRESTART
The Warm Restart (WRMRESTART) condition occurs when the node restarts while it is powered up. A restart can be caused by provisioning, such as database-restore and IP changes, or software defects. A
WRMRESTART is normally accompanied by MANRESET or AUTORESET to indicate whether the reset was initiated manually (MAN) or automatically (AUTO).
This is the first condition that appears after a TCC2/TCC2P card is powered up. The condition changes to COLD-START if the TCC2/TCC2P card is restarted from a physical reseat or a power loss.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
3-9
Chapter 3 Transient Conditions
3.3.39 WTR-SPAN
3.3.39 WTR-SPAN
The Span is in Wait To Restore State (WTR-SPAN) condition occurs when a BLSR switches to another span due to a Signal Failure-Span command or a fiber is pulled from a four-fiber BLSR configuration.
The condition is raised until the WaitToRestore (WTR) period expires.
This transient condition clears when the BLSR returns to a normal condition or the IDLE state.
3-10
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
November 2009
C H A P T E R
4
Error Messages
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration.
Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This chapter lists the Cisco ONS 15454, 15454 SDH, 15600, 15327, 15310-CL, and 15310-MA error messages. The error dialog box in
Figure 4-1 consists of three parts: the error title, error ID, and error
message. The table lists two types of messages: error messages (EIDnnnn ) and warning messages
(WIDnnnn ). Error messages are alerts that an unexpected or undesirable operation has occurred which either indicates the risk of loss of traffic or an inability to properly manage devices in the network.
Warnings are alerts that the requested operation could lead to an error. Warnings are sometimes used to convey important information.
Figure 4-1 Error Dialog Box
Error Title
Error ID
Error Message
gives a list of all error or warning message numbers, the messages, and a brief description of each message.
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-1
Chapter 4 Error Messages
Table 4-1 Error Messages
Error Warning
ID
EID-0
EID-1
Error Warning Message
Invalid error ID.
EID-1000
EID-1001
Description
The error ID is invalid.
Null pointer encountered in {0}.
Cisco Transport Controller (CTC) encountered a null pointer in the area described by the specified item.
Refer to the error message text.
The host name of the network element cannot be resolved to an address.
Unable to launch CTC due to applet security restrictions. Please review the installation instructions to make sure that the CTC launcher is given the permissions it needs. Note that you must exit and restart your browser in order for the new permissions to take effect.
Refer to the error message text.
EID-1002
EID-1003
EID-1004
The host name (e.g., for the network element) was successfully resolved to its address, but no route can be found through the network to reach the address.
An error was encountered while attempting to launch CTC.
{0}
Problem Deleting CTC Cache: {0} {1}
The node is not reachable from CTC client station.
Unexpected exception or error while launching CTC from the applet.
Unable to delete the CTC cached JARs, because another application may have the
JAR files running; for example, another instance of CTC.
EID-1005
EID-1006
EID-1007
EID-1018
EID-1019
EID-1020
EID-1021
EID-1022
An error occurred while writing to the {0} file.
The URL used to download {0} is malformed.
An I/O error occurred while trying to download {0}.
CTC encountered an error while writing to log files, preference files, etc.
The URL used to download the specified
JAR file is incorrect.
An input or output exception was encountered when CTC tried to download the specified JAR file.
The password is invalid. Password must contain at least 1 alphabetic, 1 numeric, and 1 special character (+, # or %).
Password shall not contain the associated user-ID.
Could not create {0}.
Please enter another filename.
Fatal exception occurred, exiting CTC.
Unable to switch to the Network view.
CTC could not create the file due to an invalid filename.
CTC was unable to switch from the node or card view to the network view and is now shutting down.
Unable to navigate to {0}.
CTC was uanble to display the requested view (node or network).
Refer to the error message text.
A session cannot be opened right now with this slot. Most likely someone else (using a different CTC) already has a session opened with this slot.
Please try again later.
Ensure that the shell access in CTC
(Provisioning>Security>Access) is set to non-secure mode.
4-2
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-1023
Error Warning Message
This session has been terminated.
Terminations are caused when the session has timed out, the card resets, there is already a session with the slot, or password configuration is required.
EID-1025 Unable to create Help Broker.
Description
Refer to the error message text.
EID-1026
EID-1027
EID-1028
Error found in the Help Set file.
Unable to locate help content for Help ID: "{0}".
Error saving table. {0}
CTC was unable to create the help broker for the online help.
CTC encountered an error in the online help file.
CTC was unable to locate the content for the help ID.
There was an error while saving the specified table.
EID-1031
EID-1032
EID-1035
WID-1036
EID-1037
EID-1038
EID-1039
WID-1040
WID-1041
EID-2001
EID-2002
CTC cannot locate the online user manual files. The files may have been moved, deleted, or not installed. To install online user manuals, run the CTC installation wizard on the software or documentation CD.
Refer to the error message text.
CTC cannot locate Acrobat Reader. If Acrobat Reader is not installed, you can install the Reader using the CTC installation wizard provided on the software or documentation CD.
Refer to the error message text.
CTC experienced an I/O error while working with the log files.
Usually this means that the computer has run out of disk space.
This problem may or may not cause CTC to stop responding.
Ending this CTC session is recommended, but not required.
WARNING: Deleting the CTC cache may cause any CTC running on this system to behave in an unexpected manner.
Could not open {0}. Please enter another filename.
Refer to the error message text.
Refer to the warning message text.
Invalid file name. CTC is unable to open the specified file. Ensure that the file exists and the filename was typed correctly.
The file {0} does not exist.
The version of the browser applet does not match the version required by the network element. Please close and restart your browser in order to launch the Cisco Transport Controller.
WARNING: Running the CTC with a JRE version other than the recommended JRE version might cause the CTC to behave in an unexpected manner.
An error occured while closing the {0} connection.
The specified file does not exist.
Refer to error message.
Refer to warning message.
No rolls selected. {0}
CTC encountered an error while closing the specified connection.
No rolls were selected for the bridge and roll.
The Roll must be completed or cancelled before it can be deleted.
You cannot delete the roll unless it has been completed or cancelled.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-3
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2003
EID-2004
EID-2005
EID-2006
EID-2007
EID-2008
EID-2009
EID-2010
EID-2011
EID-2012
EID-2013
EID-2014
EID-2015
EID-2016
EID-2017
EID-2018
EID-2019
EID-2020
EID-2021
EID-2022
EID-2023
EID-2024
Error Warning Message
Error deleting roll.
No IOS slot selected.
CTC cannot find the online help files for {0}. The files may have been moved, deleted, or not installed. To install online help, run the setup program on the software or documentation
CDs.
Error editing circuit(s). {0} {1}.
Unable to save preferences.
Unable to store circuit preferences: {0}
Description
There was an error when CTC tried to delete the roll.
You did not select a Cisco IOS slot.
CTC cannot find the online help files for the specified window. The files might have been moved, deleted, or not installed. To install online help, run the setup program on the software CD.
An error occurred when CTC tried to open the circuit for editing.
CTC cannot save the preferences.
CTC cannot find the file needed to save the circuit preferences.
Refer to the error message text.
Unable to download package:
{0}
Delete destination failed.
Circuit destroy failed.
Reverse circuit destroy failed.
Circuit creation error. Circuit creation cannot proceed due to changes in the network which affected the circuit(s) being created. The dialog will close. Please try again.
No circuit(s) selected. {0}
CTC could not delete the destination.
CTC could not destroy the circuit.
CTC could not reverse the circuit destroy.
Refer to the error message text.
Unable to delete circuit {0}as it has one or more rolls.
Unable to delete circuit.
Error mapping circuit. {0}
Circuit roll failure. The circuit has to be in the DISCOVERED state in order to perform a roll.
You must select a circuit to complete this function.
You must delete the rolls in the circuit before deleting the circuit itself.
CTC could not delete the tunnel as there are circuits that use the tunnel.
There was an error mapping the circuit.
There was a failure in circuit roll. Change the circuit state to DISCOVERED and proceed.
Refer to the error message text.
Circuit roll failure. Bridge and roll is not supported on a
DWDM circuit.
Circuit roll failure. The two circuits must have the same direction.
Refer to the error message text.
Circuit roll failure. The two circuits must have the same size.
Refer to the error message text.
Circuit roll failure. A maximum of two circuits can be selected for a bridge and roll operation.
Unable to create new user account.
Refer to the error message text.
Refer to the error message text.
Node selection error.
There was an error during node selection.
4-4
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2025
EID-2026
EID-2027
EID-2028
EID-2029
EID-2030
EID-2031
EID-2032
EID-2033
EID-2034
EID-2035
EID-2036
EID-2037
EID-2038
EID-2040
EID-2041
EID-2042
Error Warning Message
This feature cannot be used. Verify that each of the endpoints of this circuit are running software that supports this feature.
Unable to apply {0} request. {1}
Description
Refer to the error or warning message text.
For example, this error is generated from the node view Provisioning> WDM-ANS> tabs to indicate that the selected ring type is not supported by the endpoints of the circuit. Another example is the
Provisioning> VLAN tabs in card view
(Ethernet card only), where it indicates that the back-end spanning tree protocol (STP) disabling is not supported.
Error occurred while attempting to switch a path protection circuit away from a span.
CTC could not delete the circuit drop.
Error deleting circuit drop.
Error removing circuit node.
The requested operation is not supported.
Provisioning error.
Error adding node.
Unable to rename circuit. {0}
An error occurred during validation. {0}
CTC could not remove the circuit node.
The task you are trying to complete is not supported by CTC.
There was an error during provisioning.
There was an error while adding a node.
CTC could not rename the circuit.
There was an internal error while validating the user changes after the Apply button was pressed. This error can occur in the Edit
Circuit dialog box or in the BLSR table in the shelf view (rare condition).
Refer to the error message text.
Unable to add network circuits:
{0}
The source and destination nodes are not connected.
Cannot delete this {0}.
LAN Access has been disabled on this node and this {0} is needed to access the node.
Application error. Cannot find attribute for {0}.
Refer to the error message text.
You cannot delete the DCC/GCC link as it is needed to access the node.
Invalid protection operation.
Please select a node first.
No paths are available on this link. Please make another selection.
This span is not selectable. Only the green spans with an arrow may be selected.
CTC cannot find an attribute for the specified item.
The protection operation you tried to execute is invalid.
You must select a node before performing the task.
You must select a link that has paths available.
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-5
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2043
Error Warning Message
This node is not selectable. Only the source node and nodes attached to included spans (blue) are selectable. Selecting a selectable node will enable its available outgoing spans.
EID-2044
EID-2045
EID-2047
EID-2048
EID-2050
EID-2051
EID-2052
EID-2054
This link may not be included in the required list. Constraints only apply to the primary path. Each node may have a maximum of one incoming signal and one outgoing link.
This link may not be included in the required list. Only one outgoing link may be included for each node.
Error validating slot number. Please enter a valid value for the slot number.
Error validating port number. Please enter a valid value for the port number.
New circuit destroy failed.
Circuit cannot be downgraded. {0}
Error during circuit processing.
Endpoint selection error.
Description
Refer to the error message text.
You must select only one link going in and out of a node. Selecting more than one link is contradictory to the path selection algorithm.
Refer to the error message text.
There was an error due to an invalid slot number.
There was an error due to an invalid port number.
CTC could not destroy the new circuit.
The specified circuit cannot be downgraded.
There was an error during the circuit processing.
There was an error during the endpoint selection.
EID-2055
EID-2056
No endpoints are available for this selection. Please make another selection.
Communication error. {0}
This error occurs in the circuit creation dialog only during a race condition that has incorrectly allowed entities without endpoints to be displayed in the combination boxes.
An internal error occurred in Network
Alarm tab while synchronizing alarms with the nodes.
EID-2059
EID-2060
EID-2061
EID-2062
EID-2063
EID-2064
EID-2065
Node deletion Error. {0}
No PCA circuits found.
Error provisioning VLAN.
Cannot delete VLAN. No VLAN(s) are selected. Please select a VLAN.
Cannot delete default VLAN.
Error deleting VLANs.
{0}
Cannot import profile. Profile "{0}" exists in the editor and the maximum number of copies (ten) exists in the editor. Aborting the import. The profile has already been loaded eleven times.
There was an error during the node deletion.
CTC could not find any protection channel access (PCA) circuits for this task.
There was an error defining the VLAN.
Refer to the error message text.
The selected VLAN is the default VLAN and cannot be deleted.
There was an error deleting the specified
VLAN.
Cannot import the profile because the profile has reached the maximum number of copies in the editor.
4-6
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2066
EID-2067
EID-2068
EID-2069
EID-2070
EID-2071
EID-2072
EID-2073
EID-2074
EID-2075
EID-2077
EID-2078
EID-2079
EID-2080
EID-2081
EID-2082
EID-2083
EID-2085
EID-2086
EID-2087
EID-2088
EID-2089
Error Warning Message
Unable to store profile. Error writing to {0}.
File write error. {0}
Unable to load alarm profile from node.
File not found or I/O exception.
(No such file or directory)
Failure deleting profile. {0}
Only one column may be highlighted.
Only one profile may be highlighted.
This column is permanent and may not be removed.
Select one or more profiles.
This column is permanent and may not be reset.
This column is permanent and may not be renamed.
At least two columns must be highlighted.
Cannot load alarmables into table. There are no reachable nodes from which the list of alarmables may be loaded. Please wait until such a node is reachable and try again.
Node {0} has no profiles.
You cannot select more than one column during clone action.
You cannot select more than one profile.
You cannot delete a permanent column.
You have not selected any profile or column. Reset operation is done by right-clicking the selected column.
A permanent column is non resettable.
You cannot rename a permanent column.
You connot compare two profiles unless you select two columns.
Refer to the error message text.
Error removing profile {0} from node {1}.
Cannot find profile {0} on node {1}.
Error adding profile {0} to node {1}.
The specified node does not have any profiles.
There was an error while removing the specified profile from the specified node.
CTC cannot find the specified profile from the specified node.
There was an error adding the specified profile to the specified node.
Invalid profile selection. No profiles were selected.
Invalid node selection. No nodes were selected.
No profiles were selected. Please select at least one profile.
Invalid profile name.
Too many copies of {0} exist. Please choose another name.
Description
CTC encountered an error while trying to store the profile.
CTC encountered an error while writing the specified file.
CTC encountered an error trying to load the alarm profile from the node.
Either the specified file was not found, or there was an input/output exception.
There was a failure in deleting the specified profile.
You tried to select an invalid profile. Select another profile.
You tried to select an invalid node. Select another node.
Refer to the error message text.
The profile name cannot be empty.
Select a unique name.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-7
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2090
EID-2091
EID-2092
EID-2093
EID-2094
EID-2095
EID-2096
EID-2097
EID-2099
EID-2100
EID-2101
EID-2102
EID-2103
EID-2104
EID-2106
EID-2107
EID-2108
EID-2109
EID-2110
EID-2111
EID-2113
EID-2114
EID-2115
Error Warning Message
No nodes selected. Please select the node(s) on which to store the profile(s).
Unable to switch to node {0}.
General exception error.
Not enough characters in name. {0}
Password and confirmed password fields do not match.
Description
You must select one or more nodes on which you can store the profile.
CTC is unable to switch to the specified node.
CTC encountered a general exception error while trying to complete the task.
The name must have a minimum of six characters.
You must make sure the two fields have the same password.
The password you entered is not allowed.
Illegal password.
{0}
The user must have a security level.
No user name specified.
Ring switching error.
Please select at least one profile to delete.
Protection switching error.
You must have an assigned security level to perform this task.
You did not specify a user name.
There was an error during the ring switch.
You have not selected the profile to delete.
There was an error during the protection switching.
The forced switch could not be removed for some circuits. You must switch these circuits manually.
The forced switch could not be removed for some circuits. You must switch these circuits manually.
There was an error during the span upgrade.
Error upgrading span.
Unable to switch circuits back as one or both nodes are not reachable.
The node name cannot be empty.
Error adding {0}, unknown host.
This error occurs during the path protection span upgrade procedure.
You must supply a name for the node.
{0} is already in the network.
The node is already in the current login group.
There was an error adding the specified item.
The specified item exists in the network.
Please enter a number between 0 and {0}.
The node you are trying to add is already present in the current login group.
You must enter a number in the range between 0 and the specified value.
This node ID is already in use. Please choose another.
Cannot set extension byte for ring.
{0}
Card communication failure. Error applying operation.
Error applying operation.
{0}
Select a node ID that is not in use.
CTC cannot set the BLSR/MS-SPRing extension byte.
This error can occur during an attempt to apply a BLSR protection operation to a line.
There was an error in applying the specified operation.
4-8
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2116
Error Warning Message
Invalid extension byte setting for ring.
{0}
EID-2118
EID-2119
EID-2120
EID-2121
Cannot delete ring. There is a protection operation set. All protection operations must be clear for ring to be deleted.
Cannot delete {0} because a protection switch is in effect.
Please clear any protection operations, make sure that the reversion time is not "never" and allow any protection switches to clear before trying again.
The following nodes could not be unprovisioned
{0}
Therefore you will need to delete this {1} again later.
Cannot upgrade ring.
{0}
EID-2122
Description
The extension byte set for the specified ring is invalid.
Clear all the protection operations for the ring before deleting it.
Clear all protection operations or switches before deleting the ring.
The specified nodes could not be unprovisioned. Try deleting this BLSR or
MS-SPRing later.
CTC cannot upgrade the specified ring.
EID-2123
EID-2124
EID-2125
EID-2126
EID-2127
Inadequate ring speed for upgrade. Only {0} (or higher) {1} can be upgraded to 4-fiber.
Verify that the following nodes have at least two in-service ports with the same speed as the 2-fiber {0}. The ports cannot serve as a timing reference, and they cannot have DCC terminations or overhead circuits. {1}
You have selected an incorrect ring speed for upgrade. Only rings within the specified parameters can be upgraded to 4-fiber
BLSR.
Nonupgradable nodes. Verify that the specified nodes have at least two IS-NR ports with the same speed as the 2-fiber
BLSR.
The specified ports cannot serve as a timing reference, and they cannot have data communications channel (DCC) terminations or overhead circuits.
Refer to the error message text.
You cannot add this span because it is connected to a node that already has the east and west ports defined.
You cannot add this span as it would cause a single card to host both the east span and the west span. A card cannot protect itself.
Refer to the error message text.
OSPF area error.
There is an Open Shortest Path First (OSPF) area error.
{0}
You cannot add this span. It would cause the following circuit(s) to occupy different {0} regions on different spans:
{1}
A circuit cannot occupy different STS regions on different spans. You may add a different span or delete the specified circuit.
EID-2128
EID-2129
Either select a different span or delete the above circuit(s).
Illegal state error.
This port is already assigned. The east and west ports must be different.
An internal error occurred while trying to remove a span from a BLSR.
This alarm occurs in the network-level
BLSR creation dialog box.
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-9
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2130
Error Warning Message
The ring ID value, {0}, is not valid. Please enter a valid number between 0 and 9999.
Description
Enter a ring ID value between 0 and 9999.
EID-2131
EID-2135
EID-2137
EID-2138
EID-2139
EID-2143
EID-2144
EID-2145
EID-2146
EID-2147
EID-2148
WID-2149
WID-2150
WID-2152
WID-2153
WID-2154
WID-2155
WID-2156
WID-2157
EID-2158
Cannot set reversion to INCONSISTENT.
Unable to store overhead circuit preferences:
{0}
Circuit merge error. {0} There was an error while merging the circuits.
Refer to the error message text.
Cannot delete all destinations. Please try again.
Error updating destinations.
No online help version selected. Cannot delete the online help book.
Error deleting online help book(s).
{0}
There was an error in updating the circuit destinations.
Select the version of online help, and proceed.
You cannot delete the specified online help.
Unable to locate a node with an IOS card.
Security violation. You may only logout your own account.
Security violation. You may only change your own account.
You must select another reversion type.
Input/Output error. Unable to store overhead circuit preferences.
Refer to error message.
You cannot logout of an account other than your own.
You cannot change an account other than your own.
Security violation. You may not delete the account under which you are currently logged in.
There is nothing exportable on this view.
Node {0} is not initialized. Please wait and try again.
You cannot delete the account you are currently loggd in.
Refer to the error message text.
Spanning tree protection is being disabled for this circuit.
Adding this drop makes the circuit a PCA circuit.
Wait till the specified node is initialized and try again.
Refer to the warning message text.
Refer to the warning message text.
Disallow creating monitor circuits on a port grouping circuit.
Refer to the warning message text.
Only partial switch count support on some nodes.
{0}
The specified nodes do not support switch counts completely.
Refer to the warning message text.
Manual roll mode is recommended for dual rolls. For auto dual rolls, please verify that roll to facilities are in service and error free.
Cannot complete roll(s).
{0}
CTC could not complete the roll because the roll is destroyed, in an incomplete state, in a TL1_roll state, is cancelled, or is not ready to complete.
Invalid roll mode.
{0}
There are two roll modes: auto and manual.
For a one-way circuit source roll, the roll mode must be auto and for a one- way circuit destination roll, the roll mode must be manual.
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-10 November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2159
EID-2160
EID-2161
Error Warning Message
Roll not ready for completion.
{0}
Roll not connected.
{0}
Sibling roll not complete.
{0}
EID-2162
EID-2163
EID-2164
WID-2165
WID-2166
WID-2167
WID-2168
WID-2169
WID-2170
WID-2171
WID-2172
EID-2173
EID-2174
Description
The roll is not ready for completion.
Refer to error messge text.
One of the rolls is not completed for the dual roll. If it is auto roll, it will be completed when a valid signal is detected.
If it is a manual roll, you must complete the roll from CTC if Bridge and Roll is operated from CTC, or from TL1 if Bridge and Roll is operated from TL1.
Refer to the error message text.
Error during roll acknowledgement.
{0}
Cannot cancel roll.
{0}
Roll error.
{0}
The MAC address of node {0} has been changed. All circuits originating from or dropping at this node will need to be repaired.
CTC cannot cancel the roll.
CTC encountered a roll error.
Port unavailable. The desired CTC CORBA (IIOP) listener port, {0}, is already in use or you do not have permission to listen on it. Please select an alternate port.
Invalid number entered. Please check it and try again.
Repair the circuits that originate from or drop at the specified node, with the new
MAC address.
Initialize the node and proceed.
Unable to insert node into the domain as the node is not initialized.
Insufficient security privilege to perform this action.
Warnings loading{0}. {1}
The profile list on node {0} is full. Please delete one or more profiles if you wish to add profile.
{1}
You have been logged out. Click OK to exit CTC.
The CTC CORBA (IIOP) listener port setting of {0} will be applied on the next CTC restart.
You do not have the previlege to perform this action.
CTC encountered warnings while loading the alarm profile import file.
One or more of the profiles selected do not exist on one or more of the nodes selected.
The profile selected does not exist on the node. Select another profile.
The number of profile that can exist on a node has reached the limit. To add a profile, delete any of the existing profiles.
Refer to the warning message text.
The Internet Inter-ORB Protocol (IIOP) listener port setting for the CTC Common
Object Request Broker Architecture
(CORBA) will be applied on the next CTC restart.
Select an alternate port, as the current port is either in use or you do not have enough permission on it.
You entered an invalid firewall port number.
Try again.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-11
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
WID-2175
WID-2176
Error Warning Message
Extension byte mismatch.
{0}
Not all spans have the same OSPF Area ID. This will cause problems with protection switching. To determine the OSPF
Area for a given span, click on the span and the OSPF Area will be displayed in the pane to the left of the network map.
Description
There is a mismatch with the extension byte.
Refer to the warning message text.
WID-2178
WID-2179
EID-2180
EID-2181
Only one edit pane can be opened at a time. The existing pane will be displayed.
Refer to the warning message text.
There is no update as the circuit has been deleted.
CTC initialization failed in step {0}.
This link may not be included as it originates from the destination.
Refer to the warning message text.
CTC initialization has failed in the specified step.
You must not include this link as it originates from destination of a circuit. It is against the path selection algorithm.
EID-2182
EID-2183
EID-2184
EID-2185
EID-2186
EID-2187
EID-2188
EID-2189
EID-2190
EID-2191
EID-2192
EID-2193
EID-2194
The value of {0} is invalid.
Circuit roll failure. Current version of CTC does not support bridge and roll on a VCAT circuit.
Cannot enable the STP on some ports because they have been assigned an incompatible list of VLANs. You can view the
VLAN/Spanning Tree table or reassign ethernet ports VLANs.
The value of the specified item is invalid.
Refer to the error message text.
Refer to the error message text.
Cannot assign the VLANs on some ports because they are incompatible with the Spanning Tree Protocol. You can view the VLAN/Spanning Tree table or reassign VLANs.
Software download failed on node {0}.
TL1 keyword "all" can not be used as the ring name. Please provide another name.
Adding this span will cause the ring to contain more nodes than allowed.
Refer to the error message text.
The maximum length for the ring name that can be used is {0}.
Please try again.
The nodes in this ring do not support alphanumeric IDs. Please use a ring ID between {0} and {1}.
The software could not be downloaded onto the specified node.
You must shorten the length of the ring name.
The ring ID should not contain alphanumeric characters, and must be in the specified range.
Refer to the error message text.
You have reached the maximum number of nodes allowed.
Ring name must not be empty.
Cannot find a valid route for the circuit creation request.
You must supply a ring name.
CTC could not complete the circuit creation request either beacuse there are no physical links, or the bandwidth of the available links are already reserved.
Cannot find a valid route for the circuit drop creation request.
Refer to the error message text.
Cannot find a valid route for the roll creation request.
Refer to the error message text.
4-12
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2195
Error Warning Message
The circuit VLAN list cannot be mapped to one spanning tree.
You can view the VLAN/Spanning Tree table or reassign
VLANs.
Description
Refer to the error message text.
EID-2196
EID-2197
Unable to relaunch the CTC. {0}
CORBA failure. Unable to proceed.
There is an error relaunching CTC.
There was a CORBA failure, and the task cannot proceed. Verify the Java version.
EID-2198
EID-2199
EID-2200
EID-2202
EID-2203
EID-2204
EID-2205
EID-2206
Unable to switch to the {0} view.
CTC is unable to switch to the specified view.
The login failed on the specified tasks.
Login failed on {0} {1}
CTC has detected a jar file deletion. The jar file was used to manage one or more nodes. This CTC session will not be able to manage those nodes and they will appear gray on the network map. It is recommended that you exit this CTC session and start a new one.
Intra-node circuit must have two sources to be Dual Ring
Interconnect.
Refer to the error message text.
Intranode circuit must have two sources to be a dual ring interconnect (DRI).
No member selected.
Number of circuits must be a positive integer
Circuit Type must be selected.
Unable to autoselect profile! Please select profile(s) to store and try again.
You must select a member.
The number of circuits cannot be zero or negative.
You must select a circuit type.
Refer to the error message text.
EID-2207
EID-2208
EID-2209
EID-2210
EID-2211
EID-2212
You cannot add this span. Either the ring name is too big (i.e., ring name length is greater than {0}) or the endpoints do not support alphanumeric IDs.
This is an invalid or unsupported JRE.
Reduce the length of the ring name, or remove the alphanumberic characters from the end points.
The version of Java Runtime Environment
(JRE) is either invalid or unsupported.
The user name must be at least {0} characters long.
No package name selected.
No node selected for upgrade.
Protected Line is not provisionable.
The user name must be at least of the specified character length.
You must select a package name.
You must select a node for the upgrade.
The protected line cannot be provisioned.
Choose another line.
WID-2213
EID-2214
EID-2215
EID-2216
EID-2217
The current type or state of some drops does not allow the new circuit state of {0} to be applied to them indirectly.
The circuit state, specified by {0} cannot be applied to the selected drops.
The node is disconnected. Please wait till the node reconnects. Refer to the error message text.
Error while leaving {0} page.
Error while entering {0} page.
There was an error while leaving the specified page.
There was an error while entering the specified page.
Some conditions could not be retrieved from the network view Refer to the error message text.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-13
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2218
EID-2219
EID-2220
EID-2221
EID-2222
EID-2223
EID-2224
EID-2225
EID-2226
EID-2320
EID-2321
Error Warning Message
Bandwidth must be between {0} and {1} percent.
Protection operation failed, XC loopback is applied on cross-connection.
Description
The bandwidth must be within the specified parameters.
As the protection operation failed, a cross-connect (XC) loopback will be applied on cross-connection.
The tunnel status is PARTIAL. CTC will not be able to change it. Please try again later
Refer to the error message text.
Cannot find a valid route for the unprotected to {0} upgrade request.
One or more of the following nodes are currently part of a
4-fiber {0}. Only a single 4-fiber {0} is supported per node.
{1}
Refer to the error message text.
Only one circuit can be upgraded at a time.
Refer to the error message text.
This link may not be included as it terminates on the source.
Refer to the error message text.
No valid signal while trying to complete the roll. (0)
The nodes, specified by {1}, are already part of a 4-fiber BLSR/MS-SPRing type
(specified by {0}).
Roll can be completed only when a valid signal is detected. If not, the roll completion may result in an error.
Refer to the error message text.
Circuit roll failure.
{0}
This VCAT circuit does not support deletion of its member circuits.
Error deleting member circuits.
{0}
You can not delete a circuit that is a member of VCAT circuit.
Refer to the error message text.
WID-2322
EID-2323
EID-2324
EID-2325
WID-2326
WID-2327
Not all cross-connects from selected circuits could be merged into the current circuit. They may appear as partial circuits.
Circuit roll failure.
Bridge and roll is not supported on a monitor circuit.
Circuit upgrade error.
{0}
Refer to the warning message text.
A monitor circuit does not support Bridge and Roll.
Refer to the error message text.
You have failed {0} times to unlock this session. CTC will exit after you click OK or close this dialog box.
The maximum amount of attempts to unlock this session has been reached.
Refer to the warning message text.
Currently, CTC does not support bridge and roll on circuits that are entirely created by TL1. To continue with bridge and roll in
CTC, selected circuits must be upgraded.
OK to upgrade selected circuits and continue bridge and roll operation?
Currently, CTC does not support bridge and roll on circuits that are partially created by TL1. To continue with bridge and roll in CTC, selected circuits must be upgraded.
OK to upgrade selected circuits and continue bridge and roll operation?
Refer to the warning message text.
4-14
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-2328
EID-2329
EID-2330
EID-2331
EID-2332
EID-3001
EID-3002
EID-3003
EID-3004
EID-3005
EID-3006
EID-3007
EID-3008
EID-3009
EID-3010
EID-3016
EID-3017
EID-3018
EID-3019
EID-3020
EID-3021
Error Warning Message
Circuit reconfigure error.
{0}
{0} of {1} circuits could not be successfully created.
Circuit verification: selected {0} invalid!
Description
The attempt to reconfigure the specified circuit has failed.
A few circuits could not be created.
The selected item, specified by {0}, is invalid as per the details, specified in {1}.
{1}
Deleting {0} may be service affecting.
Hold-off timer validation error in row [0].
{1} hold-off timer for {2} must be between {3}-10,000 ms, in steps of 100 ms.
An Ethernet RMON threshold with the same parameters already exists. Please change one or more of the parameters and try again.
Error retrieving defaults from the node: {0}
Cannot load file {0}.
Cannot load properties from the node
Cannot save NE Update values to file {0}
Deleting the item can affect the service of
CTC.
Refer to the error message text.
Change a few parameters in an Ethernet remote monitoring (RMON) threshold and try again.
There was an error while retrieving the defaults from the specified node.
CTC cannot load the specified file.
Refer to the error message text.
CTC cannot save the network element (NE) update values to the specified file.
Refer to the error message text.
Cannot load NE Update properties from the node
Provisioning Error for {0}
Not a valid Card
There was a provisioning error for the specified item.
You cannot perform DWDM automatic node setup (ANS) from the Card view.
Please navigate to the Node view and try again.
No {0} selected Select the specified item, for example,
VLAN, port, slot, etc.
Refer to the error message text.
Unable to create bidirectional optical link
Invalid subnet address.
Subnet address already exists.
Standby TSC not ready.
Refer to the error message text.
Refer to the error message text.
The standby Timing and Shelf Control card
(TSC) not ready.
Enter the complete internal subnet address.
Incomplete internal subnet address.
TSC One and TSC Two subnet addresses cannot be the same.
A node’s internal subnet must be different from one another as each TSC is on separate ethernet buses, isolated by broadcast domains.
An error was encountered while retrieving the diagnostics:
{0}
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-15
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
EID-3022
EID-3023
EID-3024
Requested action not allowed.
Unable to retrieve low order cross connect mode.
Unable to switch {0} cross connect mode.
Please verify that the type and/or number of circuits provisioned does not exceed the criterion for switching modes.
EID-3025
EID-3026
Error while retrieving thresholds.
Cannot modify send DoNotUse.
Description
The requested action is not allowed.
Refer to the error message text.
CTC cannot switch the cross-connect mode for the specified item, as the type or the number of circuits does not match with the criterion for switching modes.
There was an error retrieving the thresholds.
You cannot modify the Send DoNotUse field.
EID-3027
EID-3028
EID-3029
EID-3031
EID-3032
EID-3033
EID-3035
EID-3036
EID-3039
EID-3040
EID-3041
EID-3042
EID-3046
EID-3047
EID-3048
EID-3049
EID-3050
Cannot modify SyncMsg.
Cannot change port type.
Unable to switch to the byte because an overhead change is present on this byte of the port.
Error hard-resetting card.
You cannot modify the SyncMsg field.
You cannot change the port type.
Refer to the error message text.
There was an error while resetting card hardware.
Error resetting card.
The lamp test is not supported on this shelf.
There was an error while resetting the card.
Refer to the error message text.
The cross connect diagnostics cannot be performed Refer to the error message text.
The cross connect diagnostics test is not supported on this shelf. The cross-connect diagnostics test is not supported on this shelf.
Card change error.
Invalid card type.
Error applying changes.
There was an error while changing the card.
The selected card type is invalid.
CTC is unable to create a protection group.
Check if the protect port supports circuits, a timing reference, SONET SDCC, orderwire, or a test access point.
Refer to the error message text.
The flow control low value must be less than the flow control high value for all ports in the card.
The flow control water mark value must be between {0} and
{1}, inclusive.
The file named {0} could not be read. Please check the name and try again.
There is no IOS startup config file available to download.
The flow control watermark value must be between the two specified values.
Refer to the error message text.
There is an update in progress so the download cannot be done at this time.
An exception was caught trying to save the file to your local file system.
CTC could not find the configuration file for IOS startup.
Refer to the error message text.
Check whether the file already exists and cannot be over written, or there isa space constraint in the file system.
4-16
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3051
EID-3052
EID-3053
EID-3054
EID-3055
EID-3056
EID-3057
EID-3058
EID-3059
EID-3060
Error Warning Message
The maximum size for a config file in bytes is: {0}
Description
The size of the configuration file should not exceed the specified number of bytes.
Refer to the error message text.
There was an error saving the config file to the TCC.
The value of {0} must be between {1} and {2}
Cannot remove provisioned input/output ports or another user is updating the card, please try later.
Cannot create soak maintance pane.
Cannot save defaults to file {0}
The value of the item must be between the specified values.
Another user may be updating the card. You can try again later.
Refer to the error message text.
Cannot load default properties from the node.
File {0} does not exist.
Error encountered while refreshing.
CTC cannot save the defaults to the specified file.
Refer to the error message text.
Refer to the error message text.
There was an error while refreshing.
The ALS Recovery Pulse Interval must be between {0} seconds and {1} seconds.
The automatic laser shutdown (ALS)
Recovery Interval must be between the specified range of seconds.
EID-3061
EID-3062
EID-3064
EID-3065
EID-3066
EID-3067
EID-3068
EID-3069
EID-3070
EID-3071
EID-3072
EID-3073
The ALS Recovery Pulse Duration must be between {0} seconds and {1} seconds.
Error encountered while setting values.
Not a G1000 Card.
The automatic laser shutdown (ALS)
Recovery Duration must be between the specified range of seconds.
Refer to the error message text.
This card is not a G1000-4 card.
An error was encountered while attempting to create RMON threshold:
{0}
You must wait some time before you try again.
Minimum sample period must be greater than or equal to 10.
Refer to the error message text.
Rising Threshold: Invalid Entry, valid range is from 1 to {0} This is an invalid rising threshold entry. The valid range is from 1 to the specified value.
Falling Threshold: Invalid Entry, valid range is from 1 to {0} This is an invalid falling threshold entry.
The valid range is from 1 to the specified value.
Refer to the error message text.
Rising threshold must be greater than or equal to falling threshold.
Error in data for ports {0} Exactly one VLAN must be marked untagged for each port. These changes will not be applied.
Get Learned Address
Clear Learned Address
Clear Selected Rows
CTC encountered data error for the specified ports. Only one VLAN should be marked untagged for each port.
Unable to retrieve the learned MAC address from the NE.
Failure attempting to clear the learned MAC address from a specific card or Ether group.
Failure attempting to clear the learned MAC address from a specific card or Ether group.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-17
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3074
EID-3075
EID-3076
EID-3077
EID-3078
EID-3079
EID-3080
EID-3081
EID-3082
EID-3084
Error Warning Message
Clear By {0}
At least one row in param column needs to be selected.
CTC lost its connection with this node. The NE Setup Wizard will exit.
No optical link selected.
Unable to create optical link.
Cannot apply defaults to node: {0}
Cannot go to the target tab {0}
Port type cannot be changed.
Cannot modify the {0} extension byte.
Description
Error encountered trying to clear the learned MAC address from either a VLAN or a port.
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
CTC cannot apply the defaults to the specified node.
CTC cannot go to the specified target tab.
Refer to the error message text.
You cannot modify the specified extension byte.
Error encountered while trying to retrieve laser parameters for
{0}
No OSC Terminations selected
There is no card, or there was an internal communications error when attempting to get the laser parameters for the card.
Select an OSC termination and proceed.
EID-3085
EID-3086
EID-3087
EID-3088
EID-3089
EID-3090
EID-3091
EID-3092
EID-3093
EID-3094
EID-3095
WID-3096
EID-3097
One or more Osc terminations could not be created.
OSC termination could not be edited.
No {0} card to switch.
Cannot use/change {0} state when {1} is failed or missing.
Cannot perform operation as {0} is
{1}LOCKED_ON/LOCKED_OUT.
Cannot perform the operation as protect is active.
Cannot perform operation.
Refer to the error message text.
Invalid service state. The requested action cannot be applied.
Select another service state and proceed.
Cannot perform the operation as duplex pair is {0}locked.
Cannot perform the operation as no XC redundancy is available.
Deletion failed since the circuit is in use
Internal communication error encountered while trying to retrieve laser parameters. This can happen when equipment is not present or when equipment is resetting. Check the equipment state and try to refresh the values again.
The ring termination is in use.
Refer to the error message text.
Refer to the error message text.
No card of the specified type to switch.
Cannot use or change the specified state when the card is failed or missing.
Refer to the error message text.
You cannot perform the requested operation on the cross connect card without having a backup cross connect card.
Refer to the error message text.
Refer to the warning message text.
EID-3098 No ring terminations selected.
The ring termination you are trying to access is in use. Try after sometime.
Select one of the ring terminations.
4-18
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
EID-3099
EID-3100
Sorry, entered key does not match existing authentication key.
Error encountered during authentication.
Description
Check the authentication key and reenter.
There was an error in authentication. Verify that the key does not exceed the character limit .
EID-3101
EID-3102
EID-3103
EID-3104
DCC Metric is not in the range 1 - 65535.
Invalid DCC Metric
Invalid IP Address: {0}
Router priority is not in the range of 0 - 255
The DCC metric should be in the range of 1 to 65535.
There was an invalid DCC metric.
The IP address is invalid.
EID-3105
EID-3106
EID-3107
EID-3109
Invalid Router Priority
Hello Interval is not in the range of 1 - 65535
Invalid Hello Interval
Invalid Dead Interval value. Valid range is 1 - 2147483647
The router priority should be in the range of
0 to 255.
The router priority is invalid.
The hello interval should be in the range of
1 to 65535.
The hello interval is invalid.
EID-3110
EID-3111
EID-3112
EID-3113
Dead Interval must be larger than Hello Interval
LAN transit delay is not in the range of 1 - 3600 seconds
Invalid Transmit Delay
Retransmit Interval is not in the range 1 - 3600 seconds
The dead interval value must be between 1 and 2147483647.
Refer to the error message text.
The LAN transit delay should be in the range of 1 to 3600 seconds.
The transmit delay is invalid.
EID-3114
EID-3115
EID-3116
EID-3117
Invalid Retransit Interval
LAN Metric is not in the range 1 - 65535.
The retransmit interval should be in the range of 1 to 3600 seconds.
The retransmit interval is invalid.
The LAN metric should be in the range of 1 to 65535.
The LAN metric is invalid.
Refer to the error message text.
EID-3118
EID-3119
Invalid LAN Metric
If OSPF is active on LAN, no DCC Area Ids may be 0.0.0.0.
Please change all DCC Area Ids to non-0.0.0.0 values before enabling OSPF on the LAN.
If OSPF is active on LAN, LAN Area ID may not be the same as DCC Area Id.
Validation Error
EID-3120
EID-3121
No object of type {0} selected to delete.
Error Deleting {0}
LAN must be part of a different OSPF area other than the DCC network.
CTC was unable to validate the values entered by the user. This error message is common to several different provisioning tabs within CTC (examples include the
SNMP provisioning tab, the General>
Network provisioning tab, the Security >
Configuration provisioning tab, etc.).
Choose an object of the specified type to delete.
There is an error deleting the item.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-19
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3122
EID-3123
EID-3124
EID-3125
EID-3126
EID-3127
EID-3128
EID-3129
EID-3130
Error Warning Message
No object of type {0} selected to edit.
Error Editing {0}
{0} termination is in use.
Delete the associated OSPF Range Table Entry and try again
No {0} Terminations selected.
{0} termination could not be edited.
Description
Choose an object of the specified type to edit.
There was an error editing the item.
Refer to the error message text.
Unable to provision orderwire because E2 byte is in use by {0}. Refer to the error message text.
The authentication key may only be {0} characters maximum The authentication key cannot exceed the specified number of characters.
The authentication keys do not match!
Error creating OSPF area virtual link.
No specified terminations are selected.
CTC could not edit the specified termination.
Refer to the error message text.
CTC encountered an error while creating the area virtual link.
EID-3131
EID-3132
EID-3133
EID-3134
EID-3135
EID-3136
EID-3137
EID-3138
EID-3139
EID-3140
EID-3141
EID-3142
EID-3143
EID-3144
Error creating OSPF virtual link.
Error setting OSPF area range: {0}, {1}, false.
CTC encountered an error creating the virtual link.
CTC encountered an error while setting the area range for the specified values.
Max number of OSPF area ranges exceeded.
Invalid Area ID. Use DCC OSPF Area ID, LAN Port Area ID, or 0.0.0.0.
OSPF area ranges exceeded the maximum number.
Refer to the error message text.
Invalid Mask
Invalid Range Address
Your request has been rejected because the timing source information was updated while your changes were still pending. Please retry.
Invalid clock source for switching.
Refer to the error message text.
The range address is invalid. Try again.
Refer to the error message text.
Cannot switch to a reference of inferior quality.
Higher priority switch already active.
Attempt to access a bad reference.
No Switch Active.
Error creating static route entry.
Max number of static routes exceeded.
You have selected an invalid clock source.
Choose another clock.
Refer to the error message text.
You cannot switch the timing source manually when a higher priority switch is already active.
Refer to the error message text.
None of the switches are active.
CTC encountered an error while a creating static route entry.
The number of static routes has exceeded its limit.
4-20
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3145
EID-3146
EID-3147
EID-3148
EID-3149
EID-3150
EID-3151
EID-3152
EID-3153
EID-3154
EID-3155
EID-3156
EID-3157
EID-3158
EID-3159
EID-3160
EID-3161
EID-3162
EID-3163
EID-3164
EID-3165
1
Error Warning Message
RIP Metric is not in the range 1-15.
Invalid RIP Metric
Error creating summary address.
No Layer 2 domain has been provisioned.
Description
The Routing Information Protocol (RIP) metric should be in the range of 1 to 15.
Refer to the error message text.
There was an error while creating the summary address.
You must provision any one of the layer 2 domain.
Refer to the error message text.
Unable to retrieve MAC addresses.
The target file {0} is not a normal file.
The target file {0} is not writeable.
Error creating Protection Group
The specified target file is not a normal file.
The target file is not writeable. Specify another file.
CTC encountered an error creating
Protection Group.
Refer to the error message text.
Cannot delete card, it is in use.
Cannot {0} card, provisioning error.
Error Building Menu
Error on building menu (cards not found for {0} group)
Unable to set selected model: unexpected model class {0}
CTC cannot perform the task on the card.
CTC encountered an error building the menu.
CTC encountered an error while building the menu, as cards could not be found for the specified group).
CTC encountered an unexpected model class while trying to complete the task.
Refer to the error message text.
Unable to switch, a similar or higher priority condition exists on peer or far-end card.
Error applying operation.
{0} error encountered.
Ring Upgrade Error
CTC encountered an error while applying this operation.
CTC encountered the specified error.
An error was encountered while attempting to upgrade the BLSR. Refer to the details portion of the error dialog box for more information.
This protection operation cannot be set because the protection operation on the other side has been changed but not yet applied.
Cannot validate data for row {0}
Refer to the error message text.
CTC cannot validate the data for the specified row.
New Node ID ({0}) for Ring ID {1} duplicates ID of node {2} The new specified node ID for the specified ring ID is the same as another node ID.
The Ring ID provided is already in use. Ring IDs must be unique
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-21
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3166
EID-3167
EID-3168
EID-3169
EID-3170
EID-3171
EID-3172
EID-3173
EID-3174
EID-3175
EID-3176
EID-3177
EID-3178
EID-3179
EID-3180
EID-3181
EID-3182
EID-3183
EID-3184
EID-3185
EID-3186
EID-3187
EID-3214
Error Warning Message
Error refreshing {0} table
Slot already in use
Provisioning Error
Error Adding Card
Cannot delete card, {0}
Error creating Trap Destination
No RMON Thresholds selected
The contact “{0}” exceeds the limit of {1} characters.
The location “{0}” exceeds the limit of {1} characters.
The operator identifier “{0}” exceeds the limit of {1} characters.
The operator specific information “{0}” exceeds the limit of
{1} characters.
The node name cannot be empty.
The name “{0}” exceeds the limit of {1} characters.
Protect card is in use.
1+1 Protection Group does not exist.
Y Cable Protection Group does not exist.
The Topology Element is in use and cannot be deleted as requested
Error Deleting Protection Group
No {0} selected.
Description
CTC encountered an error while refreshing the specified table.
Refer to the error message text.
An error was encountered while attempting the specified provisioning operation. Refer to the details portion of the error dialog box for more information.
CTC encountered an error while adding the card.
Refer to the error message text.
CTC encountered an error creating the trap destination.
Select an RMON threshold.
The specified contact exceeds the specified character limit.
The specified location exceeds the specified character limit.
The specified operator identifier exceeds the specified character limit.
The specified operator specific information exceeds the specified character limit.
The specified name is empty.
The specified name exceeds the specified character limit.
Refer to the error message text.
Create a 1+1 protection group.
Refer to the error message text.
You cannot delete the topology element which is in use.
CTC encountered an error while deleting the protection group.
You must select an item before completing this task.
Refer to the error message text.
There is a protection switch operation on this ring. Therefore, it cannot be deleted at this time.
Busy: {0} is {1} and cannot be deleted as requested.
Error deleting trap destination.
Could not get number of HOs for line.
The request cannot be completed.
CTC encountered an error deleting the trap destination.
The number of High Orders (STS/STM) for the line is not available.
4-22
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3215
EID-3216
EID-3217
EID-3218
EID-3219
EID-3220
EID-3222
EID-3225
EID-3226
EID-3227
EID-3228
EID-3229
EID-3230
EID-3231
WID-3232
EID-3233
EID-3234
EID-3235
EID-3236
EID-3237
Error Warning Message
Error in refreshing.
Invalid proxy port.
Could not refresh stats.
Unable to launch automatic node setup.
Unable to refresh automatic node setup information.
Description
Used frequently in pane classes to indicate a general error condition when trying to refresh from the model.
Refer to the error message text.
CTC could not refresh statistics values.
Refer to the error message text.
Failure trying to retrieve automatic node setup information.
Error refreshing row {0}
Could not clear stats.
Error while refreshing pane.
Error refreshing the specified row.
Refer to the error message text.
Used frequently in pane classes to indicate a general error condition when trying to refresh from the model.
Refer to the error message text.
{0} termination(s) could not be deleted. {1}
Unable to record a baseline, performance metrics will remain unchanged.
CTC failed to set the baseline values while provisioning NE. Previous values remain unchanged.
Refer to the error message text.
{0} termination(s) could not be created.
{1}
RIP is active on the LAN. Please disable RIP before enabling
OSPF.
OSPF is active on the LAN. Please disable OSPF before enabling RIP.
Error in Set OPR
Database Backup failed. {0}
Turn off the Routing Information Protocol
(RIP) on the LAN, before enabling OSPF.
Turn off the OSPF on the LAN before enabling RIP.
An error was encountered while attempting to provision the optical power received
(OPR).
Edit the port state while provisioning the port.
Cannot transition port state indirectly because the port is still providing services: if the port state should be changed, edit it directly via port provisioning.
Current loopback provisioning does not allow this state transition.
Current synchronization provisioning does not allow this state transition
Refer to the error message text.
You cannot transition the port state to the target date while in the current synchonization state.
Refer to the error message text.
Cannot perform requested state transition on this software version.
Database Restore failed. {0} CTC failed to restore the specified database.
CTC failed to backup the specified database.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-23
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3238
EID-3239
EID-3240
EID-3241
EID-3242
WID-3243
EID-3244
WID-3245
EID-3246
EID-3247
EID-3248
EID-3249
EID-3250
EID-3251
EID-3252
EID-3253
EID-3254
EID-3255
Error Warning Message
Send PDIP setting on {0} is inconsistent with that of control node {1}
The overhead termination is invalid
The maximum number of overhead terminations has been exceeded.
The {0} termination port is in use.
An {1} exists on the selected ports.
Therefore, you must create the {0}s one by one.
Description
The send payload defect indicator path
(PDI-P) setting on the specified item should be consistent with that of the specified control node.
Refer to the error message text.
Overhead terminations have exceeded the limit.
The specified termination port is in use.
Select another port.
The specified DCC already exists on the selected port. You can create a DCC of another type.
The port you have chosen as an {0} endpoint already supports an {1}. The port cannot support both DCCs. After the {0} is created, verify that no EOC alarms are present and then delete the {1} to complete the downgrade.
An {0} exists on the selected ports.
Therefore, you must create the {1}s one by one.
The same port can not be used by multiple
DCCs.
The port you have chosen as an {1} endpoint already supports an {0}. The port cannot support both DCCs. After the {1} is created, verify that no EOC alarms are present and then delete the {0} to complete the upgrade.
Wizard unable to validate data: {0}
Ordering error. The absolute value should be {0}
Wrong parameter is changed: {0}
The specified DCC already exists on the selected port. You can create a DCC of another type.
The port selected as a DCC endpoint already supports another DCC. Refer to the warning message text.
CTC encountered an error.
The absolute value entered was wrong.
CTC changed the incorrect parameter.
Invalid voltage increment value.
Invalid power monitor range.
Unable to complete requested action. {0}
No download has been initiated from this CTC session.
Reboot operation failed. {0}
Validation Error. {0}
Refer to the error message text.
Refer to the error message text.
CTC could not complete the specified action.
Refer to the error message text.
Refer to the error message text.
The Cisco Transport Controller (CTC) was unable to validate the values entered by the user, specified by {0}. This error message is common to several different provisioning tabs within the CTC.
Cannot change timing configuration, manual/force operation is performed.
Refer to the error message text.
4-24
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
WID-3256
EID-3257
Could not assign timing reference(s) because - at least one timing reference has already been used and/or - a timing reference has been attempted to be used twice.
Please verify the settings.
Duplicate DCC number detected: {0}.
EID-3258
EID-3259
EID-3260
EID-3261
EID-3262
WID-3263
EID-3264
Description
Refer to the warning message text.
CTC detected more than one occurene of the a DCC number. Remove one of them.
Refer to the error message text.
There was a software error attempting to download the file.
Please try again later.
Create FC-MR Threshold
An error was encountered while provisioning the internal subnet:
{0}
The port rate provisioning cannot be changed while circuits exist on this port.
You must create a Fibre Channel Multirate
(FC_MR) card threshold.
The specified internal subnet could not be provisoned.
Refer to the error message text.
The port provisioning cannot be changed when the port status is not OOS.
You must provision the ports only when the port is Out of Service.
You are using Java version {0}. CTC should run with Java version {1}. It can be obtained from the installation CD or http://java.sun.com/j2se/
CTC is being launched with the wrong version of the JRE {0}. This version of CTC requires a particular version of the JRE {1}.
The CTC and browser must be closed and restarted to allow the correct Java version to be loaded.
The port provisioning cannot be changed while the port is {0}. You must modify the port provisioning only when the port is out of service.
EID-3265
EID-3266
WID-3267
WID-3268
WID-3269
WID-3270
WID-3271
WID-3272
WID-3273
WID-3274
Error modifying Protection Group
Conditions could not be retrieved from the shelf or card view.
Cannot edit XTC protection group.
Invalid entry. {0}
Protection Group could not be modified.
Refer to the error message text.
Refer to the warning message text.
The specified entry is invalid.
{0} was successfully initiated for {1} but its completion status was not able to be obtained from the node. {0} may or may not have succeeded. When the node is accessible, check its software version.
Refer to the error message text.
The file {0} does not exist.
The value entered must be greater than {0}.
The specified file does not exist.
The value entered must be greater than the specified value.
An entry is required to complete this task.
Entry required
{0} already exists in the list.
A software upgrade is in progress. Network configuration changes that results a node reboot can not take place during software upgrade. Please try again after software upgrade is done.
The specified item already exists in the list.
Refer to the warning message text.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-25
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
WID-3275
Error Warning Message
WID-3276
WID-3277
Make sure the Remote Interface ID and the Local Interface ID on the two sides are matched. (Local Interface ID on this node should equal Remote Interface ID on the neighbor node and vice-versa.)
Both {0} and {1} exist on the same selected port.
{2}
The description cannot contain more than {0} characters. Your input will be truncated.
Description
Refer to the warning message text.
The specified port has both SDCC and
LDCC.
The input exceeds the character limit. The value will be truncated to the maximum chacter limit.
WID-3279
WID-3280
Card deleted, returning to shelf view.
ALS will not engage until both the protected trunk ports detect
LOS.
CTC returns to node view.
Refer to the warning message text.
WID-3282
WID-3283
WID-3284
WID-3285
Performing a software upgrade while TSC 5 is active could result in a service disruption. It is recommended that you make
TSC 10 the active TSC by performing a soft reset of TSC 5. The following 15600s are currently unsafe to upgrade...
Refer to the warning message text.
Before activating a new version, make sure you have a database backup from the current version.
Reverting to an older version.
Refer to the warning message text.
Applying FORCE or LOCKOUT operations may result in traffic loss.
CTC is being reverted to an older version of application.
Refer to the warning message text.
WID-3286
WID-3287
WID-3288
EID-3290
EID-3291
EID-3292
EID-3293
The ring status is INCOMPLETE. CTC cannot determine if there are existing protection operations or switches in other parts of the ring. Applying a protection operation at this time could cause a traffic outage. Please confirm that no other protection operations or switches exist before continuing.
There is a protection operation or protection switch present on the ring. Applying this protection operation now will probably cause a traffic outage.
Refer to the warning message text.
Refer to the warning message text.
This ring status is INCOMPLETE. CTC will not be able to apply this change to all of the nodes in the {0}.
Unable to delete specified provisionable patchcord(s).
Cannot change revertive behavior due to an active protection switch.
Error resetting shelf.
No such provisionable patchcord.
Change the ring status to apply the change to all nodes in the ring type.
Refer to the error message text.
Protection switch should not be active to change the revertive behaviour.
CTC encountered an error while resetting the node.
You are attempting to delete a provisionable patchcord that does not exist. This happens when multiple instances of CTC are running and attempting to delete the same provisionable patchcord concurrently.
4-26
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
EID-3294
EID-3295
EID-3296
No RMON thresholds available for selected port.
This card does not support RMON thresholds.
Buffer-to-buffer credit is only supported for Fibre Channel (FC) and FICON.
Description
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
EID-3298
EID-3300
EID-3301
EID-3302
EID-3303
EID-3304
EID-3305
EID-3306
EID-3307
EID-3308
EID-3309
ALS Auto Restart is not supported by this interface.
Can not have duplicate OSPF area IDs.
LAN metric may not be zero.
Standby {0} not ready.
DCC Area ID and {0} conflict.
{1}
DCC number is out of range.
Can not have OSPF turned on on the LAN interface and the back bone area set on a DCC interface.
Ethernet circuits must be bidirectional.
Error while creating connection object at {0}.
DWDM Link can be used only for optical channel circuits.
OCH-NC circuit: link excluded - wrong direction.
Refer to the error message text.
OSPF area IDs should be unique.
Refer to the error message text.
Standby controller card is not ready.
DCC Area ID and ring type, specified by
{0}, conflict each other due to the details specified by {1}.
Enter a DCC number that is within the range
You cannot have the default OSPF area on a
DCC while OSPF is enabled on the LAN.
Refer to the error message text.
CTC encountered an error at the specified connection while creating the connection.
Refer to the error message text.
The optical channel (circuit) does not allow the specified link to be included because it is in the wrong optical direction.
Refer to the error message text.
EID-3310
EID-3311
EID-3312
DWDM Link does not have wavelength available.
Laser already on.
Unable to change the power setpoint {0} {1}
EID-3313
EID-3314
EID-3315
EID-3316
Unable to modify offset. Amplifier port is in service state.
Requested action not allowed. Invalid state value.
Unable to perform operation.
Wrong node side.
Refer to the error message text.
CTC cannot change change the power setpoint. The new setpoint would either make the thresholds inconsistent or set the fail threshold outside the range.
Refer to the error message text.
Refer to the error message text.
CTC is unable to perform operation.
This task was applied to the wrong node side.
EID-3317 Name too long.
EID-3318
EID-3319
EID-3320
EID-3321
EID-3322
Illegal name.
Wrong line selection.
Unable to delete optical link.
This feature is unsupported by this version of software.
Equipment is not plugged-in.
Reduce the number of charcters in the name.
The name you entered is illegal.
Select another line
CTC cannot delete the optical link.
Refer to the error message text.
Plug-in the equipment and proceed.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-27
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3323
EID-3324
EID-3325
EID-3326
EID-3327
EID-3328
EID-3330
EID-3331
EID-3334
EID-3335
Error Warning Message
APC system is busy.
No path to regulate.
Requested action not allowed.
Wrong input value.
Error in getting thresholds.
Description
Automatic Power Control (APC) system is busy.
There is no circuit path to regulate.
Generic DWDM provisioning failure message.
The input value is incorrect.
There was an error retrieving the thresholds.
This message is displayed only for the
OSCM/OSC-CSM line thresholds.
Error applying changes to row {0}.Value out of range.
There was an error applying the changes to the specified row. The value is out of range.
Refer to the error message text.
Unable to switch to the byte because an overhead channel is present on this byte of the port.
Error applying changes to row.
Cannot change timing parameters on protect port.
Refer to the error message text.
You cannot change timing parameters on protect port.
The type of this port cannot be changed: SDH validation check failed. Check if this port is part of a circuit, protection group,
SONET DCC, orderwire, or UNI-C interface.
Error on reading a control mode value.
Refer to the error message text.
The Control Mode must be retrieved.
EID-3336
EID-3337
EID-3338
EID-3339
EID-3340
EID-3341
EID-3342
EID-3343
EID-3344
EID-3345
EID-3346
Error on setting a set point gain value.
Error on reading a set-point gain value.
Error on setting a tilt calibration value.
Error on setting expected wavelength.
Error on reading expected wavelength.
Error on reading actual wavelength.
Error on reading actual band.
Error on reading expected band.
Error on setting expected band.
Error retrieving defaults from the node: {0}.
The Gain Set Point must be set.
The Gain Set Point must be retrieved.
The tilt calibration must be set.
The expected wavelength must be set.
The expected wavelength must be retrieved.
The actual wavelength must be retrieved.
The actual band must be retrieved.
The expected band must be retrieved.
The expected band must be set.
There was an error retrieving defaults from the specified node.
EID-3347
EID-3348
EID-3349
EID-3350
EID-3351
EID-3352
Cannot load file {0}.
Cannot load properties from the node.
Cannot save NE Update values to file.
Cannot load NE Update properties from the node:
File {0} does not exist.
Error on setting value at {0}.
CTC cannot load the specified file.
Refer to the error message text.
Check your file system for space constraint or any other problem.
Refer to the error message text.
The specified file does not exist.
There was an error while setting the value at the specified location.
4-28
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3353
EID-3354
EID-3355
EID-3357
EID-3358
EID-3359
EID-3361
EID-3362
EID-3363
EID-3364
EID-3365
EID-3366
EID-3370
EID-3371
EID-3372
EID-3375
EID-3376
EID-3377
EID-3378
EID-3379
EID-3380
EID-3381
EID-3382
Error Warning Message
There is no such interface available.
Specified endpoint is in use.
Specified endpoint is incompatible.
Unable to calculate connections.
Optical link model does not exist for specified interface.
Description
The interface specified is not present in
CTC.
Select another endpoint that is not in use.
Refer to the error message text.
Refer to the error message text.
Create an optical linkmodel for the interface, and proceed.
Unable to set optical parameters for the node.
Ring termination is in use. Error deleting ring termination
Error deleting ring termination.
No ring terminations selected.
Error creating ring ID.
OSC termination is in use.
Unable to delete OSC termination.
Refer to the error message text.
You cannot delete a ring in use.
There was an error while deleting ring termination.
You must select a ring termination.
There was an error while creating the ring
ID.
Select another optical service channel
(OSC) which is not in use.
There was an error deleting the OSC termination.
You must select an optical link.
No optical link has been selected
Error while calculating automatic optical link list.
Attempt to access an OCHNC connection that has been destroyed.
Expected span loss must be set.
Unable to retrieve measured span loss.
Wrong interface used.
Duplicate origination patchcord identifier.
Refer to the error message text.
CTC destroyed an external attempt to access an optical channel network connection.
Refer to the error message text.
Refer to the error message text.
The interface used for the card is wrong.
The provisionable patchcord identifier to the patchcord you are attempting to provision is already in use by another patchcord on the origination node.
Duplicate termination patchcord identifier.
Unable to locate host.
Maximum Frame size must be between {0} and {1} and may be increased in increments of {2}.
Number of credits must be between {0} and {1}.
The provisionable patchcord identifier to the patchcord you are attempting to provision is already in use by another patchcord on the remote node.
Refer to the error message text.
The frame size must be in the specified range. This can incremented by the specified value.
The number of credits must be between the specified values.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-29
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3383
WID-3384
EID-3385
EID-3386
EID-3387
Error Warning Message
GFP Buffers Available must be between {0} and {1} and may be increased in increments of {2}.
Description
The GFP buffers must be in the specified range. This can incremented by the specified value.
You are about to force the use of Secure Mode for this chassis.
You will not be able to undo this operation. OK to continue?
Refer to the warning message text.
{0}. Delete circuits, then try again.
Unable to provision transponder mode:
{0}
You must change port{0} to an out-of-service state before changing card parameters. Click Reset to revert the changes.
Refer to the error message text.
The specified transponder mode canot be provisioned.
All the card ports should be changed to out-of-service before changing the parameters.
EID-3388
EID-3389
EID-3390
EID-3391
WID-3392
WID-3393
EID-3394
EID-3395
EID-3396
EID-3397
EID-3398
EID-3399
EID-3400
EID-3401
Unable to change the card mode because the card has circuits.
Refer to the error message text.
Error encountered while changing the card mode.
Refer to the error message text.
Port is in use.
Unable to change the port rate because the port has been deleted.
Refer to the error message text.
You cannot change the port rate of a card that has been deleted.
Refer to the warning message text.
Could not assign timing reference(s) because - with external timing, only a single protected, or two unprotected timing references per BITS Out may be selected. Please use the
“Reset” button and verify the settings.
Could not assign timing reference(s) because - with line or mixed timing, only a single unprotected timing reference per
BITS Out may be selected. Please use the “Reset” button and verify the settings.
Refer to the warning message text.
Error refreshing Power Monitoring values.
Invalid Configuration: {0}
Invalid Configuration: The standby controller card is not a
TCC2P card.
Wrong version for file {0}.
Cannot delete PPM.
Cannot delete PPM. It has port(s) in use.
Refer to the error message text.
CTC encountered an error in IP address, net mask length, or default router, or a restricted IIOP port was selected.
The standby controller card should be a
TCC2P card.
The specified file is of wrong version.
Refer to the error message text.
Remove the ports coonected to the
Pluggable Port Module before it can be deleted.
Unable to switch, force to Primary Facility not allowed.
{0} cannot be provisioned for the port while {1} is enabled.
Refer to the error message text.
The relationship between parameters {0} and {1} are such that enabling either one, prevents the provisioning of the other.
4-30
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-3402
Error Warning Message
Unable to complete the switch request.
The {0} card is either not present or is not responding. Try again after ensuring that the {0} card is present and is not resetting.
EID-3403 Admin state transition has not been attempted on the monitored port.
Description
Refer to the error message text.
Refer to the error message text.
EID-3404 The far end IP address could not be set on the {0} termination.
The IP address cannot be: loopback (127.0.0.0/8) class D (224.0.0.0/4)
Refer to the error message text.
class E (240.0.0.0/4) broadcast (255.255.255.255/32)
EID-4000
EID-4001
WID-4002
EID-4003
EID-4004
EID-4005
EID-4006
EID-4007
WID-4008
EID-4009
EID-4010 internal {1}
The {0} ring name cannot be changed now. A {0} switch is active.
You cannot change the ring name because a switch of the same ring type is active.
The {0} ring ID cannot be changed now. A {0} switch is active. You cannot change the ring ID because a switch of the same ring type is active.
CAUTION: Reverting to an earlier software release may result in TRAFFIC LOSS and loss of connectivity to the node. It may require onsite provisioning to recover.
If the node was running {0} before, reverting will restore the
{0} provisioning, losing any later provisioning. If the node was running some other version, reverting will LOSE ALL
PROVISIONING.
{1}
{2}
The IOS console is disabled for the card in slot {0}.
Refer to the warning message text.
The card may not be an IOS-based card or it may be rebooting.
Error cancelling software upgrade.
{0} encountered while performing DB backup.
The file {0} does not exist or cannot be read.
The size of {0} is zero.
CTC encountered an error while cancelling the software upgrade.
CTC encountered the specified error during database backup.
Refer to error message.
The size of the file that is being backed up or restored is zero.
A software upgrade is in progress.
{0} can not proceed during a software upgrade.
Please try again after the software upgrade has completed.
{0} encountered while restoring database.
The operation was terminated due to the following error:
{0}
The specified action cannot be performed during a software upgrade. You must try after the upgrade process is completed.
CTC encountered the specified error while restoring the database.
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-31
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
EID-4011 Provisioning
{0}
EID-5000
EID-5001
EID-5002
EID-5003
Cannot find a valid route for tunnel change request.
Tunnel could not be changed.
Tunnel could not be restored and must be recreated manually.
Circuit roll failure.
Description
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
EID-5004
WID-5005
WID-5006
WID-5007
WID-5008
WID-5009
EID-5010
EID-5011
WID-5012
EID-5013
EID-5014
WID-5015
EID-5016
EID-5017
{0}
There is already one 4F {0} provisioned on the set of nodes involved in {1}. The maximum number of 4F {0} rings has been reached for that node.
There is already one 4F BLSR provisioned on the set of nodes involved in the ring. The maximum number of 4F BLSR rings has been reached for that node.
Refer to the warning message text.
A non-zero hold-off time can violate switching time standards, and should only be used for a circuit with multiple path selectors.
Warning: Different secondary {0} node should only be used for
DRI or Open-ended path protected circuits.
You should use different secondary end point only for DRI or open-ended path protected circuits.
If you change the scope of this view, the contents of this profile editor will be lost.
Refer to the warning message text.
Please make sure all the protection groups are in proper state after the cancellation.
Circuit {0} not upgradable. No {1} capable {2}s are available at node {3}.
Domain name already exists.
Domain name may not exceed {0} characters.
Refer to the warning message text.
No VT capable STSs are available at the node.
Refer to the error message text.
You may have reached the maximum number of charcters.
Refer to the warning message text.
Software load on {0} does not support the addition of a node to a 1+1protection group.
{0} doesn’t support Bridge and Roll Feature. Please select a different port.
An automatic network layout is already in progress, please wait for it to complete for running it again.
{0} cannot be applied to {1}.
The specified port does not support Bridge and Roll.
You must for the automatic network layout to complete before running it again.
You cannot apply the admin state operation, specified by {0}, to port count, specified by
{1}.
An error was encountered while attempting to provision the
{0}. {1}
Unable to rollback provisioning, the {0} may be left in an
INCOMPLETE state and should be manually removed.
CTC encountered an error while provisioning the card.
You may have to remove the BLSR manually as it was left incomplete.
4-32
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-5018
EID-5019
WID-5020
EID-5021
WID-5022
EID-5023
Error Warning Message
{0} is {1} node and cannot be added to {2} network.
No nodes are selected. Please choose a node.
Warning: Ethergroup circuits are stateless (i.e., always in service).
Current state selection of {0} will be ignored.
Unable to communicate with node.
Operation failed.
Description
You cannot add the node {0} of type {1} to the host node of type {2}. This prevents you from hosting both SONET and SDH nodes in the same session.
Manual mode for this equipment does not support an expected string consisting of all null characters. Please change the expected string or the path trace mode.
The path trace mode does not support strings that consist of null characters. You must either change the expected string or the path trace mode.
Refer to the warning message text.
Unable to transition port state indirectly because the port aggregates low order circuits: if the port state should be changed, edit it directly via port provisioning
Refer to the error message text.
Refer to the warning message text.
CTC encountered a network communication error. Connectivity between
CTC and the NE was disrupted, either transiently or permanently.
EID-5024
WID-5025
EID-5026
Overhead circuit will not be upgraded.
The path targeted for this switch request is already active. The switch request can be applied, but traffic will not switch at this time.
A 15600 cannot serve as the primary or secondary node in a 4
Fiber {0} circuit. Please change your ring and/or node selections so that a 15600 is not chosen as the primary or secondary node in this 4 Fiber {1} circuit.
Refer to the error message text.
Refer to the warning message text.
Refer to the error message text.
WID-5027
WID-5028
EID-5029
EID-5030
WID-5031
EID-5032
The {0} Edit Window for {1} has been closed due to significant provisioning changes. These changes may only be transitory, so you may re-open the {0} Edit Window to view the updated state.
Warning: This operation should only be used to clean up rolls that are stuck. It may also affect completeness of the circuit.
Continue with deletion?
Re-open the BLSR/MS-SPRing edit window to view the updated state of the ring.
Refer to the warning message text.
A software downgrade cannot be performed to the selected version while an SSXC card is inserted in this shelf. Please follow the steps to replace the SSXC with a CXC card before continuing the software downgrade.
Refer to the error message text.
A software downgrade cannot be performed at the present time. Try the software downgrade later.
Refer to the warning message text.
Cancelling a software upgrade during standby TSC clock acquisition may result in a traffic outage.
Error accepting load. Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-33
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-5033
EID-5034
EID-5035
EID-5036
EID-5037
Error Warning Message
Unable to load profile.
Error decoding characters.
Unable to load profile.
File format error.
Unable to load profile.
File read error.
The GNE Host Name {0} is invalid.
Provisionable patchcords cannot be created between transponder trunk ports and mux/demux ports on the same node.
Description
CTC detected an error while decoding characters and could not load the profile.
CTC detected an error and could not load the profile.
CTC could not read the file and is therefore unable to load the profile.
The specified host name is invalid. CTC could not resolve the host name to any valid
IP address
You must create provisionable patchcords between transponder trunk ports and mux/demux ports that are on different nodes.
patchcords ports and mux/demux ports must use the same wavelength:
{0} is not equal to {1}. patchcords ports and mux/demux ports must use the same wavelength:
{0} is not equal to {1}.
Please provision the {2} wavelength on {3}.
EID-5040
EID-5041
Provisionable patchcords between OC3/OC12 ports and mux/demux ports are not supported.
Provisionable patchcords between non-colored OCn trunk ports and mux/demux ports are not supported.
EID-5042
Wavelengths used by provisionable patchcords for transponser trunk ports and mux/demux ports must be the same.
Transmitter and receiver port wavelengths are not equal. Provision the receiver and transmitter wavelengths on transmitter and receiver ports respectively.
Refer to the error message text.
Refer to the error message text.
WID-5043
EID-5044
EID-5045
WID-5046
Provisionable patchcords created between OCn trunk ports and mux/demux ports must use the same wavelength:
{0} is not equal to {1}.
Warning: line card is only provisioned: wavelength compatibility check is skipped.
Virtual link can be used only for OCH trail circuits.
Virtual link does not have wavelength available.
Wavelengths used by provisionable patchcords for OC-N trunk ports and mux/demux ports must be the same.
Refer to the warning message text.
Refer to the error message text.
Set wavelengths for the virtual link and proceed.
Refer to the warning message text.
EID-5047
Warning: if you select "Use OCHNC Direction" your circuit will be limited to nodes prior to release 07.00.
Provisionable patchcords between OC3/OC12 ports are not supported.
Refer to the error message text.
EID-5048
EID-5049
EID-5050
Provisionable patchcords between non-colored OCn trunk ports are not supported.
Provisionable patchcords between non-colored OCn trunk ports and mux/demux ports are not supported.
Cannot find Element Model:
{0}
Refer to the error message text.
Refer to the error message text.
The specified Element Model cannot be located.
4-34
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
WID-5051 Unable to transition port state indirectly because the port aggregates OCH CC circuits: if the port state should be changed, edit it directly via port provisioning
EID-5052
EID-5053
The operation is not valid for the connection type
The operation cannot be performed because the connection is under test access
EID-5054
EID-5055
EID-5056
EID-5057
EID-5058
EID-5059
EID-5060
EID-5061
EID-6000
EID-6001
EID-6002
EID-6003
EID-6004
EID-6005
Description
Refer to the warning message text.
You may have selected the incorrect switch.
Refer to the error message text.
TL1 Tunnel Open Failed: {0}
Some patchcords were not deleted. Patchcords cannot be deleted if they are incomplete or support any circuits, or if the nodes supporting them are not connected.
Refer to the error message text.
Refer to the error message text.
This PPC cannot be deleted because one or more circuits are provisioned over it.
Remove the circuits provisioned over the provisionable patchcord before trying to delete it.
Refer to the error message text.
Adding last node not completed yet.
Please wait before trying to add new node.
OCHNC Upgrade is applicable only to bidirectional circuits.
Refer to the error message text.
OCHNC upgrade failed.
One or more communication failures occurred during the operation.
OCHNC upgrade partially failed.
One or more communication failures occurred during the operation.
Create the OCH CC manually.
CTC encountered a complete failure while upgrading optical channel network connection.
CTC encountered a partial failure while upgrading an optical channel network connection.
Overhead circuit source and destination must reside on the same shelf.
Refer to the error message text.
Platform does not support power monitoring thresholds
One of the XC cards has failures or is missing.
Refer to the error message text.
Check whether all the cross-connect cards are installed and working.
Unlock the cross-connect card.
Enter a new ID for the ring.
One of the XC cards is locked.
Unable to create OSC termination.
Ring ID already assigned.
Unable to perform a system reset while a BLSR ring is provisioned on the node.
Could not assign timing references:
- Only two DS1 or BITS interfaces can be specified.
- DS1 interfaces cannot be retimed and used as a reference
- BITS-2 is not supported on this platform.
Remove the BLSR from the node and continue with the reset procedure.
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-35
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6006
EID-6008
Error Warning Message
Could not assign timing references:
- NE reference can only be used if timing mode is LINE.
- A BITS reference can only be used if timing mode is not
LINE.
- A line reference can only be used if timing mode is not
EXTERNAL.
Description
Refer to the error message text.
SF BER and SD BER are not provisionable on the protect line of a protection group.
Refer to the error message text.
WID-6009
WID-6010
WID-6011
EID-6012
EID-6013
If Autoadjust GFP Buffers is disabled, GFP Buffers Available must be set to an appropriate value based on the distance between the circuit end points.
Refer to the warning message text.
If Auto Detection of credits is disabled, Credits Available must be set to a value less than or equal to the number of receive credits on the connected FC end point.
Refer to the warning message text.
Idle filtering should be turned off only when required to operate with non-Cisco Fibre Channel/FICON-over-SONET equipment.
Refer to the warning message text.
Could not change the retiming configuration. There are circuits on this port.
NTP/SNTP server could not be changed.
{1}
You cannot change the timing configuration on this port unless the circuits on this port are deleted.
Refer to the error message text.
EID-6014
EID-6015
EID-6016
EID-6017
EID-6018
EID-6019
EID-6020
EID-6021
EID-6022
EID-6023
Operation failed. The reference state is OOS.
Distance Extension cannot be disabled if the port media type is
FICON 1Gbps ISL or FICON 2Gbps ISL.
Change the Out-of-service state to Active.
Refer to the error message text.
Card mode cannot be changed to Fibre Channel Line Rate if the port media type is FICON 1Gbps ISL or FICON 2Gbps ISL.
The destination of a {0} route cannot be a node IP address.
Refer to the error message text.
A node IP address cannot be the destination for a static route.
Refer to the error message text.
The destination of a {0} route cannot be the same as the subnet used by the node.
The destination of a static route cannot be 255.255.255.255
The network address such as
255.255.255.255 is not valid. Enter a valid address.
Refer to the error message text.
The destination of a static route cannot be the loopback network
(127.0.0.0/8)
The subnet mask length for a non-default route must be between 8 and 32.
Length of subnet mask must be within the specified range.
Refer to the error message text.
The subnet mask length for a default route must be 0.
The destination of a {0} route cannot be an internal network{1}.
The destination of a static route must not be an internal network.
4-36
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6024
Error Warning Message
The destination of a {0} route cannot be a class D (224.0.0.0/4) or class E (240.0.0.0/4) address.
Description
The destination of a static route must not be a class D or class E address.
EID-6025
EID-6026
The destination of a {0} route cannot be a class A broadcast address (x.255.255.255/8)
The destination of a static route must not be a class A broadcast address. It should be
(xxx.0.0.0).
The destination of a static route must not be a class B broadcast address.
EID-6027
EID-6028
EID-6029
EID-6030
EID-6031
The destination of a {0} route cannot be a class B broadcast address (x.x.255.255/16)
The destination of a {0} route cannot be a class C broadcast address (x.x.x.255/24)
The destination of a {0} route cannot be the subnet broadcast address associated with a node IP address.
The next hop of a static route cannot be the same as the destination of the route or an internal network{0}.
The next hop of a static default route must be the provisioned default router.
No more static routes can be created.
The destination of a static route must not be a class C broadcast address.
The destination of a static route must not be a subnet broadcast address of a node IP.
Static route must have the default route as the next hop, and not destination of the route or internal network.
The default route is selected for networks that do not have a specific route.
EID-6032
EID-6033
This static route already exists.
Previous operation is still in progress.
You have reached the maximum number of static routes.
Refer to the error message text.
Another operation is in progress. You must try after sometime.
Refer to the error message text.
EID-6035
EID-6036
EID-6037
Parent entity does not exist.
Parent PPM entity does not exist.
Equipment type is not supported.
EID-6038
EID-6039
EID-6040
EID-6041
EID-6042
Invalid PPM port.
Card is part of a regeneration group.
Out of memory.
Port is already present.
Port is used as timing source.
Create a parent entity for the PPM.
CTC does not support this equipment.
Refer to the error message text.
Select another card.
Refer to the error message text.
Refer to the error message text.
Choose another port because the selected port is being used as a timing source.
Refer to the error message text.
EID-6043
EID-6044
EID-6045
DCC or GCC is present.
Card or port is part of protection group.
Port has overhead circuit(s).
Refer to the error message text.
Refer to the error message text.
EID-6046
EID-6047
EID-6048
G.709 configuration is not compatible with data rate.
Port cannot be deleted because its service state is
OOS-MA,LPBK&MT.
{0} is {1}.
Refer to the error message text.
To delete the port, you must change the port state to OOS-DSBLD.
The trunk port is in the wrong state to carry out the action.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-37
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6049
EID-6050
WID-6051
EID-6052
EID-6053
EID-6054
EID-6055
EID-6056
WID-6057
EID-6058
EID-6059
EID-6060
EID-6061
EID-6062
EID-6063
EID-6064
EID-6065
EID-6066
EID-6067
EID-6068
EID-6069
EID-6070
EID-6071
EID-6072
WID-6073
Error Warning Message
Mode {0} is not supported.
Description
CTC does not support the mode of operation requested on the card.
Refer to the error message text.
Some {0} terminations were not {1}d.
{2}
All {0} terminations were {1}d successfully.
{2}
The authentication key can not be blank.
No more SNMP trap destinations can be created.
Refer to the warning message text.
{0} is not a valid IP address for an SNMP trap destination.
The IP address is already in use.
Invalid SNMP trap destination. {0}
Changing the card mode will result in an automatic reset.
Max number of IP Over CLNS tunnels exceeded.
The specified IP Over CLNS tunnel already exists!
Cannot {0} IP Over CLNS tunnel entry:
{1}.
Error deleting IP Over CLNS tunnel entry.
Enter an authentication key.
You have reached the maximum number of
SNMP trap destinations.
The IP address specified is not a valid receiver of SNMP traps.
Refer to the error message text.
The specified SNMP trap destination is invalid. Choose another destination.
Refer to the warning message text.
Refer to the error message text.
Specify another IP Over CLNS tunnel.
Refer to the error message text.
Selected IP Over CLNS tunnel does not exist.
Selected router does not exist.
MAA address list is full.
Selected area address is duplicated.
CTC encountered an error while deleting the IP Over CLNS tunnel entry.
Create a IP Over CLNS tunnel.
Create a router.
Refer to the error message text.
Enter another area address.
Primary area address can not be removed.
Selected area address does not exist.
Refer to the error message text.
Choose another area address.
The IP Over CLNS NSEL may not be modified while there are
IP Over CLNS Tunnel Routes provisioned.
The node is currently in ES mode. Only router #1 may be provisioned.
You cannot change the NSEL address if tunnels are provisioned.
An End System needs only one provisioned router.
No router selected.
Cannot flush TARP data cache.
Select a router.
You cannot flush the cache in the Tunnel identifier Address Resolution Protocol
(TARP) state.
You cannot add the specified cache entry.
Cannot add TARP data cache entry:
{0}
TARP request has been initiated.
Try refreshing TARP data cache later.
Refer to the warning message text.
4-38
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID Error Warning Message
EID-6074
EID-6075
EID-6076
EID-6077
EID-6078
EID-6079
WID-6080
EID-6081
EID-6082
EID-6083
EID-6084
WID-6085
EID-6086
EID-6087
EID-6088
End System mode only supports one subnet.
Trying to remove MAT entry that does not exit.
Cannot {0} TARP manual adjacency entry:
{1}
Area address shall be 1 to 13 bytes long.
TDC entry with TID {0} does not exist in the table.
Description
Refer to the error message text.
CTC is removing the MAT entry.
CTC cannot add the specified adjacency entry for reasons unknown.
The area address should not be more than 13 characters.
The specified Tunnel Identifier does not exist.
Unable to remove TDC entry with TID {0}.
Please verify that TARP is enabled.
Router #{0} does not have an area address in common with router #1. Switching from IS L1/L2 to IS L1 in this case will partition your network.
The limit of 10 RADIUS server entries has been reached.
You must enable TARP inorder to remove the TDC entry.
Refer to the warning message text.
{0} cannot be empty.
CTC does not allow more than 10 RADIUS servers.
The Shared Secrets field should not be empty.
Refer to the error message text.
The entry you selected for editing has been altered by other.
Changes cannot be committed.
The RADIUS server entry already exists.
Disabling shell access will prevent Cisco TAC from connecting to the vxWork shell to assist users.
Cannot change card. Card resources are in use.
Specify another RADIUS server entry.
Refer to the warning message text.
The card you are trying to remove is being used. Cannot change the card.
Refer to the error message text.
Cannot change card. The new card type is invalid or incompatible.
This line cannot be put into loopback while it is in use as a timing source
Refer to the error message text.
EID-6089
EID-6090
EID-6091
EID-6092
EID-6093
EID-6094
EID-6095
EID-6096
Interface not found. {0}
Interface type not valid for operation. {0}
The current state of the interface prohibits this operation. {0} The port is in an invalid state to set a loopback.
Operation prohibited for this interface. {0} CTC does not allow this operation for the specified interface.
Max number of Tarp Data Cache entries exceeded.
CTC cannot find the specified interface.
Choose another interface.
Max number of Manual Adjacency Table entries exceeded.
Invalid Ais/Squelch mode.
Default IP Over CLNS tunnel route is only allowed on a node without a default static route and a default router of 0.0.0.0
You have exceeded the number of characters permitted.
Refer to the error message text.
Refer to the error message text.
Refer to the error message text.
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
4-39
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6097
EID-6098
EID-6099
WID-6100
EID-6101
WID-6102
EID-6103
EID-6104
EID-6105
Error Warning Message
The authorization key does not comply with IOS password restrictions.
{0}
Description
Specify another authorization key.
Default static route is not allowed when default IP Over CLNS tunnel exists
You cannot create a subnet on a disabled router.
Refer to the error message text.
Create the subnet on an active router.
Refer to the warning message text.
Disabling a router that has a provisioned subnet is not recommended.
The MAT entry already exists.
The new card has less bandwidth than the current card. Circuits using VT15 and higher will be deleted.
Refer to the error message text.
Refer to the warning message text.
The TDC entry already exists.
APC ABORTED.
The 'Change Card' command is valid for MRC cards only when port 1 is the sole provisioned port.
Specify another entry for TARP Data
Cache.
Automatic Power Control is aborted.
Refer to the error message text.
EID-6106
EID-6107
EID-6108
EID-6109
EID-6110
EID-6111
EID-6112
To delete all RADIUS server entries, RADIUS authentication must be disabled.
The node failed to restart the TELNET service on the selected port. Try using another unreserved port that is not being used within the following ranges:
23, 1001-9999 (with the exception of 1080, 2001-2017, 2361,
3081-3083, 4001-4017, 4022, 4081, 4083, 5000, 5001, 7200,
9100, 9300, 9401).
Disable Radius authentication and proceed.
Refer to the error message text.
That port is already in use.
Error: A section trace is active on the trunk port. The action cannot be completed.
Max number of TARP requests reached.
Restart a TELNET session.
Actions such as putting the port in an incomplete state are not permitted while a section trace is active.
You have exceeded the maximum number of TARP requests.
Refer to the error message text.
The card in {0} cannot be removed because it is the protected card.
Error adding shelf, {0} The shelf ID specified is invalid or already exists, the equipment does not support multishelf, the specified shelf position is out of range, or the specified shelf position is already in use.
4-40
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6113
EID-6114
EID-6115
Error Warning Message
Cannot delete shelf, {0}
Description
One or more of the equipment modules
(provisioned virtual links, provisioned server trails, provisioned protection groups, or provisioned DCCs) in the shelf is currently in use. Delete cards from all the slots and try again.
Refer to the error message text.
The maximum number of supported shelves have already been provisioned.
There are bad or duplicate shelf positions.
Valid rack numbers are {0} to {1}.
Valid rack positions are {2} to {3}.
Refer to the error message text.
EID-6116
EID-6117
WID-6118
EID-6119
EID-6120
WID-6121
EID-6122
EID-6123
EID-6124
EID-6125
EID-6126
EID-6127
EID-6128
Attempt to access an OchTrail connection that has been destroyed.
Attempt to access an OchTrail adit that has been destroyed.
Software has prevented an attempt to access an OCH trail .
The resource cannot be accessed because it is released or fully utilized.
Refer to the warning message text.
The following slots are provisioned but do not have cards installed:
{0}
CTC will assume they are ITU-T interfaces.
Unable to rearrange the shelves.
{0}
This equipment does not support multishelf.
This internal patchcord can not be provisioned because the end points have no compatible wavelengths
Unable to start the wizard.
{0}
One of the following conditions is present: duplicate shelf positions, invalid shelf positions, or concurrent movement (two
CTC sessions are attempting to rearrange the shelves at the same time.)
Refer to the error message text.
The end points of an internal patchcord should have compatible wavelengths.
CTC was unable to initiate the wizard due to the specified reason.
A communication failure occurred.
OSI request can not be completed successfully.
Invalid ALS recovery pulse interval.
Invalid ALS recovery pulse duration.
Refer to the error message text.
Refer to the error message text.
The current setting does not support the specified ALS mode.
Refer to the error message text.
All enabled routers are required to have the same area.
Refer to the error message text.
EID-6129
EID-6135
A software download is in progress. Configuration changes that results a card reboot can not take place during software download. Please try again after software download is done.
The payload configuration and card mode are incompatible.
DCC is present.
Refer to the error message text.
Refer to the error message text.
A data communication channel (DCC) already exists.
EID-6136 Unable to provision: {0} CTC was not able to provision the specified port or card.
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009 4-41
Chapter 4 Error Messages
Table 4-1 Error Messages (continued)
Error Warning
ID
EID-6137
EID-6138
EID-6139
EID-6140
EID-6143
EID-6144
Error Warning Message
Cannot disable multishelf.
Description
Multishelf is not supported on equipment, is already disabled, or modules on the shelf are currently in use.
Invalid LAN configuration.
Invalid card(s) present.
Please remove all non-MSTP cards and try again.
Verify the LAN configuration.
Non-DWDM cards cannot be added to an a
DWDM node. Remove the cards.
Refer to the error message text.
The shelf identifier for a subtended shelf cannot be provisioned via CTC. It must be changed using the LCD.
DHCP server could not be changed.
The port provisioning cannot be changed when the port media is Undefined.
Refer to the error message text.
If the port is not pre-provisioned with the type of media that is going to be inserted, you cannot access any of the existing values for the port.
1.
EID-3159 can appear if you attempt to perform another switching operation within a certain time interval. This interval is an algorithm of three seconds per working card in the protection group. The maximum interval is 10 seconds.
4-42
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
Numerics
1+1 protection
see external switching commands
see external switching commands
APS channel byte failure
APS invalid code condition
disable switching
far-end forced switch back to working condition
optimized 1+1 APS primary facility condition
A
ADMIN-DISABLE
ADMIN-DISABLE-CLR
ADMIN-LOCKOUT
ADMIN-LOCKOUT-CLR
ADMIN-LOGOUT
ADMIN-SUSPEND
ADMIN-SUSPEND-CLR
AICI-AEP logical object
AICI-AIE logical object
AIP
MAC address location
MEA
replace
air filter, replace
AIS
AIS
AIS-P
AIS-V
November 2009
I N D E X
AUTOSW-AIS
FE-AIS
ODUK-1-AIS-PM
ODUK-2-AIS-PM
ODUK-3-AIS-PM
ODUK-4-AIS-PM
ODUK-AIS-PM
OTUK-AIS
TX-AIS
alarm logical objects alarm index
definition list
alarms
alarms in this index appear individually by name
alphabetical list
characteristics
frequently used troubleshooting procedures
list of critical alarms
list of minor alarms
TL1
alarm troubleshooting
alphabetical alarm list
ALS
AMI coding
AMPLI-INIT
AOTS logical object
APC-CORRECTION-SKIPPED
APC-DISABLED
APC-OUT-OF-RANGE
APSB
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-1
Index
APSC-IMP
APSCINCON
APSCM
APSIMP
APSMM
APS-PRIM-FAC
APS-PRIM-SEC-MISM
ARP
AS-CMD
AS-MT
AS-MT-OOG
asynchronous mapping
AUD-ARCHIVE FAIL
AUD-LOG-LOW
AUTOLSROFF
automatic protection switching byte failure
channel failure on protect card 2-107
invalid k bytes
mode mismatch failure
path protection alarms
ring switch failure
span switch failure
automatic reset
AUTONEG-RFI
AUTORESET
AUTOSW-AIS
AUTOSW-LOP (STSMON)
AUTOSW-LOP (VT-MON)
AUTOSW-PDI
AUTOSW-SDBER
AUTOSW-SFBER
AUTOSW-UNEQ (STSMON)
AUTOSW-UNEQ (VTMON)
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-2
AWG-DEG
AWG-FAIL
AWG-OVERTEMP
AWG-WARM-UP
B
B8ZS
BAT-FAIL
BER threshold range
verify threshold level
BIC logical object
BER
BITS daisy-chained
errors
holdover timing
loss of frame
loss of signal
BITS logical object
BKUPMEMP
BLSR change node ID number
change ring name
far-end protection line failure
improper configuration (alarms)
ring switch failure
squelch alarm
verify node visibility
BLSR-RESYNC
BLSR-SW-VER-MISM
BNC connector
BPLANE logical object
November 2009
browser applet security restrictions
does launch Java
limit Netscape colors
reconfigure
stalls during download
unsupported
C card reset
LED activity
procedure
cards replace
CARLOSS cause of TPTFAIL
CE1000
CE100T
E1000
E100T
EQPT
FC
G1000
GE
ISC
ML100T, ML1000, MLFX
November 2009
Index
TRUNK
CARLOSS
CASETEMP-DEG
CBIT framing
CE100T
CE-Series Ethernet cards
CE-Series Ethernet cards carrier loss
compatible GBICs
loopbacks
terminal loopback condition
transport layer failure alarm 2-240
circuits
hairpin circuits
loopbacks
AIS-V alarm on DS3XM-6 or DS3XM-12 card
bidirectional diagnostic circuits
circuit state transition error
delete
generic procedures
identify circuit state
troubleshoot electrical circuits
troubleshoot Ethernet circuits 1-68
troubleshoot FC_MR-4 circuits
troubleshoot optical circuits
VT1.5 circuit creation error
CLDRESTART
COMIOXC
conditions
conditions are indexed individually by name
characteristics
list of not-alarmed conditions
list of not-reported conditions
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-3
Index
CONTBUS-B-18
CONTBUS-DISABLED
CONTBUS-IO-A
critical alarms definition
cross-connect cards
LED activity during side switch
main payload bus failure
reset (side switch)
test during a cross-connect loopback
test during a hairpin circuit
cross-connect loopback description
clear an OC-N card loopback circuit
perform on a destination-node OC-N carrying an
perform on a source-node STS carrying an electrical
perform on a source OC-N port
C-Series Ethernet cards facility loopback behavior
CTC terminal loopback behavior
applet security restrictions
cannot change node view to network view
cannot launch
colors appear incorrectly on UNIX workstation
correct the core version build
delete cache files
gray node icon
log-in errors 1-110, 1-116, 1-119, 1-122
loss of TCP/IP connection
release interoperability problems 1-121
slow operation or login problems
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-4 username and password mismatch
verifying PC connection
CTC_HEAP variable
CTNEQPT-PBPROT
CTNEQPT-PBWORK
cyclic redundancy checking (CRC)
D database
out of synchronization
restore
verify version
see DCN tool
DATAFLT
DBBACKUP-FAIL
DBOSYNC
DBRESTORE-FAIL
DCC channel loss
connection loss
create or verify DCC terminations
delete a DCC termination
limitations with OC-3
default K alarm
diagnostic tests bidirectional diagnostic circuit
lamp test
overview
retrieve
DISCONNECTED
DS1 logical object
DS3 logical object
DS3XM-12 card
November 2009
AIS-V alarm and unused VT circuits
clear a loopback circuit
create a facility loopback
create a terminal loopback
facility loopback behavior
FEAC loopbacks
incomplete circuit from DS-3 card
terminal loopback behavior
test and clear a facility loopback circuit
test and clear a terminal loopback circuit
DS3XM-6 card
AIS-V alarm and unused VT circuits
clear a loopback circuit
create a facility loopback
create a terminal loopback
facility loopback behavior
FEAC loopbacks
incomplete circuit from DS-3 card
terminal loopback behavior
test and clear a facility loopback circuit
test and clear a terminal loopback circuit
DS-N cards
see also DS3XM-12 card see also DS3XM-6 card see also electrical cards
DSP-COMM-FAIL
DSP-FAIL
DUP-IPADDR
DUP-NODENAME
DUP-SHELF-ID
DWDM cards
GBIC compatibility
OCHNC-CONN alarm object
E
E1000 logical object
November 2009
Index
E-Series Ethernet cards
E100T
E-Series Ethernet cards
E1 logical object
east ⁄
EC-1 card loopback facility alarm
LOS
electrical cards
EC1 logical object
EHIBATVG
EIAs
test during a facility loopback
electrical cable
CAT-5 problems
test during a facility loopback
electrical cards clear loopbacks
create a facility loopback
create a hairpin circuit
create a terminal loopback
DS-3 idle condition
facility loopback behavior
facility loopback example
frame format mismatch
idle DS-3 signal
initiate a protection switch
LOF
loopback facility alarm
loopback signal received
loss of signal
reset
terminal loopback behavior
test and clear a facility loopback circuit
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-5
Index test and clear a terminal loopback circuit
test and delete a hairpin circuit 1-16, 1-34
test during a facility loopback
test during a terminal loopback
ENCAP-MISMATCH-P
ENVALRM logical object
EOC
EOC
EOC-L
GCC-EOC
EQPT
EQPT
EQPT-DIAG
EQPT-MISS
MEA
equipment failure far-end DS-1 failure
far-end DS-3 failure
hardware failure on reporting card
missing fan-tray assembly
software or hardware failure on reporting card
ERFI-P-CONN
ERFI-P-SRVR
error messages
ESCON logical object
E-Series Ethernet cards carrier loss
compatible GBICs
verify LED operation
Ethernet
CE-Series Ethernet cards
E-Series Ethernet cards
G-Series Ethernet cards
ML-Series Ethernet cards
cable with reversed receive pairs 2-131
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-6 configure VLANs
Tag/Untag port connectivity 1-125
troubleshoot Ethernet circuit paths
verify connections
ETH-LINKLOSS
E-W-MISMATCH
EXCCOL
excess collisions
EXERCISE conditions
EXERCISE-SPAN-FAIL
external switching commands
BLSR Force Ring condition
BLSR Force Span condition 2-103, 2-109
BLSR Lockout Protect Span condition 2-104
BLSR Manual ring condition
clear a 1+1 Force or Manual switch
clear a BLSR switching command
clear a lock-on or lockout
clear a path span switch
initiate a 1+1 Manual switch 2-255
initiate a 1+1 Protection switch 2-254
initiate a 1:1 card switch command
initiate a BLSR exercise ring switch
initiate a BLSR Force ring switch
initiate a BLSR Force span switch
initiate a BLSR lockout
initiate a BLSR Manual ring switch
initiate a BLSR Manual span switch
initiate a lockout
initiate a path protection Force switch
initiate a path protection lockout 2-259
initiate a path protection Manual switch
path protection Manual Ring condition
side switch a cross-connect card
EXTRA-TRAF-PREEMPT
November 2009
Index
F facility alarms, hierarchy
facility loopback definition
card view indicator
clear an OC-N loopback circuit
create on an intermediate-node Ethernet port 1-74
perform on a destination-node electrical port
perform on a destination-node Ethernet port
perform on a destination-node FC_MR-4 card
perform on a destination-node OC-N port
perform on an intermediate-node Ethernet port
perform on an intermediate node FC_MR-4 card
perform on an intermediate node OC-N port
perform on a source-node Ethernet port
perform on a source-node OC-N port
perform on source-node FC_MR-4 cards
test a source electrical port
FAILTOSW
FAILTOSWR
FAN logical object
fan-tray assembly
MEA
missing unit alarm
replace
far-end alarms, hierarchy
FC_MR-4 card clear loopbacks
facility loopback behavior
facility loopback condition
FC-NO-CREDITS alarm
November 2009
GFP-EX-MISMATCH
GFP-UP-MISMATCH
LED test
terminal loopback condition
transport fail alarm
troubleshoot circuits with loopbacks
FCMR
FC_MR-4 card
FDI
FEAC alarms
inhibit loopbacks
send code
FEC-MISM
FE-DS1-MULTLOS
FE-DS1-NSA
FE-DS1-SA
FE-DS1-SNGLLOS
FE-DS3-NSA
FE-DS3-SA
FE-EQPT-NSA
FE-FRCDWKSWBK-SPAN
FE-FRCDWKSWPR-SPAN
FE-IDLE
FE-LOCKOUTOFPR-SPAN
FE-LOF
FE-LOS
FE-MANWKSWBK-SPAN
FE-MANWKSWPR-RING
FE-MANWKSWPR-SPAN
FEPRLF
fiber
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-7
Index faulty connections
verify connections
FIBERTEMP-DEG
see FC_MR-4 card
FC_MR-4 card firewall, invalid port number
FIREWALL-DIS
FORCED-REQ
FORCED-REQ-RING
FORCED-REQ-SPAN
external switching commands
FRCDSWTOINT
FRCDSWTOPRI
FRCDSWTOTHIRD
FRCDWKSWBK-NO-TRFSW
FRCDWKSWPR-NO-TRFSW
free run synchronization
FSTSYNC
FUDC logical object
G
G1000
G-Series Ethernet cards
GAIN-HDEG
GAIN-HFAIL
GAIN-LDEG
GAIN-LFAIL
GBICs compatibility
install
remove
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-8
GCC-EOC
GE-OOSYNC
GFP
FC_MR-4 congestion
GFP-DE-MISMATCH alarm
GFP-EX-MISMATCH alarm
GFP-FAC logical object
GFP-LFD alarm
GFP-UP-MISMATCH alarm
G-Series Ethernet cards carrier loss
clear loopbacks
compatible GBICs
facility loopback behavior
facility loopback condition
LED activity
LED test
terminal loopback behavior
terminal loopback condition
terminal loopback PM behavior 1-7
transport layer failure alarm
troubleshoot Ethernet circuit paths
H hairpin circuit definition
perform on a destination-node electrical port
perform on source-node electrical port 1-15
HELLO
HIBATVG
HI-CCVOLT
HI-LASERTEMP
November 2009
HITEMP
HI-TXPOWER
HLDOVRSYNC
I
I-HITEMP
improper card removal
IMPROPRMVL
INC-ISD
INCOMPATIBLE-SW
INHSWPR
INHSWWKG
Internet Explorer, reset as default browser
interoperability problems
INTRUSION
INTRUSION-PSWD
INVMACADR
IOSCFGCOPY
IOSCFG-COPY-FAIL
IP connectivity
IP address unknown
no connectivity exists between nodes
retrieve IP address
verify
IP subnets
ISC logical object
ISIS-ADJ-FAIL
J
Java
JRE browser does not launch
Java plug-in control panel, reconfigure
JRE
November 2009
Index
compatibility by software release 1-120
incompatibility
launch failure
K
KB-PASSTHR
KBTYE-APS-CHANNEL-FAILURE
k bytes
APS default K byte received
APS node ID mismatch
K bytes pass through
test signal
L lamp test
LAN (CAT-5) cable
faulty
LASERBIAS-DEG
LASERBIAS-FAIL
LASEREOL
LASERTEMP-DEG
LCAS
LCAS-CRC
LCAS-RX-FAIL
LCAS-TX-ADD
LCAS-TX-DNU
LED blinking STAT LED
cross-connect card side switch
lamp test
traffic card after reset
traffic card during reset
traffic card insertion
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-9
Index
line framing
LKOUTPR-S
LMP
LMP-SD
LMP-SF
LMP-UNALLOC
LMP-FAIL
LMP-SD
LMP-SF
LMP-UNALLOC
LOA
lock initiation
external switching commands
LOCKOUT-REQ
see external switching commands
LOF
BITS
DS1
DS3
E1
EC1
FE-LOF
OTUK-LOF
STSTRM
TRUNK
TX-LOF
LOGBUFR90
logical objects alarm index
definition list
log-in errors applet security restrictions
browser login does not launch Java
browser stallls when downloading .jar file
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-10 no DCC connection
no IP connectivity
slow CTC operation
username/password mismatch 1-122
LOGIN-FAILURE-LOCKOUT
LOGIN-FAILURE-ONALRDY
LOGIN-FAILURE-PSWD
LOGOUT-IDLE-USER
LO-LASERBIAS
LOM
loopback
see also cross-connect loopbacks
LOP
AUTOSW-LOP
LOP-V
LO-RXPOWER
LOS
BITS
DS1
DS3
E1
EC1
ESCON
FE-LOS
FUDC
ISC
LOS-O
LOS-P (OCH)
LOS-P (OMS)
MSUDC
OCN
November 2009
OTS
TRUNK
LOF
LOP
LOS
LO-TXPOWER
LPBKDS3FEAC
LPBKFACILITY change alarm suppression defaults
CE1000
CE100T
DS1
DS3
E1
EC1
ESCON
FC
G1000
GE
ISC
OCN
TRUNK
LPBKTERMINAL change alarm suppression defaults
CE1000
CE100T
DS1
DS3
E1
EC1
ESCON
FC
G1000
GE
November 2009
Index
ISC
OCN
TRUNK
LWBATVG
M
MAC address
CTC location
invalid
mismatch
major alarms definition
list of alarms
MAN-REQ
MANRESET
MANSWTOPRI
MANSWTOSEC
MANSWTOTHIRD
MANUAL-REQ-RING
MANUAL-REQ-SPAN
MANWKSWBK-NO-TRFSW
MANWKSWPR-NO-TRFSW
MAX-STATIONS
MEA
AIP
BIC
EQPT
FAN
PPM
MEM-GONE
MEM-LOW
MFGMEM
minor alarms
list of alarms
ML1000
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-11
Index
ML-Series Ethernet cards
ML100T
ML-Series Ethernet cards
MLFX
ML-Series Ethernet cards
ML-Series Ethernet cards
LCAS
C2 byte mismatched path
carrier loss
compatible SFPs
error in startup configuration
IOS configuration copy in progress condition
transport layer failure alarm 2-242
verify LED operation
MSUDC logical object
N near-end alarms, hierarchy
NE logical object
Netscape Navigator clear cache
limit colors
unable to launch CTC help after removing
network testing
hairpin circuits
loopbacks
NIC card
NO-CONFIG
node ID, identify
not alarmed alarms definition
NOT-AUTHENTICATED
not reported alarms
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-12 definition
O
OCHNC-CONN logical object
OCHTERM-INC
OC-N cards bit errors
circuit state transition error
clear a cross-connect loopback circuit
clear a facility or terminal loopback circuit 2-268
create a cross-connect loopback
facility loopback behavior
hairpin circuits
LED activity
lockout request condition
loopback caveat
OC-3 and DCC limitations
reset
terminal loopback alarm
terminal loopback behavior
terminal loopback condition
test and clear a cross-connect loopback circuit
transmit and receive levels
ODUK-1-AIS-PM
ODUK-2-AIS-PM
ODUK-3-AIS-PM
ODUK-4-AIS-PM
ODUK-AIS-PM
ODUK-LCK-PM
ODUK-SF-PM
ODUK-TIM-PM
OMS logical object
November 2009
OOU-TPT
OPEN-SLOT
optical transmit and receive levels
OPWR-HDEG
OPWR-HFAIL
OPWR-LDEG
OSC-RING logical object
OSPF
DCN tool
disable OSPF
HELLO alarm
OSRION
OTUK-AIS
OTUK-IAE
OTUK-LOF
OTUK-SF
OTUK-TIM
OUT-OF-SYNC
P
PARAM-MISM
password
⁄ username mismatch
path alarms, hierarchy
Path Protection failed switch path
PDI alarm
SD alarm
path protection
AIS alarm
initiate a Force switch 2-258 initiate a Manual switch 2-258
November 2009
Index
PDI
AUTOSW-PDI
PDI-P
PEER-NORESPONSE
ping
PLM
PLM-P
PLM-V
PMI
PORT-ADD-PWR-DEG-HI
PORT-ADD-PWR-DEG-LOW
PORT-ADD-PWR-FAIL-LOW
PORT-FAIL
PORT-MISMATCH
power battery failure
extreme high voltage
extreme low voltage
high receive power
high voltage battery
improper power supply
low receive power
low transmit power
measure power levels
power failure at connector
power monitoring mismatch 2-250
power supply problems
PPM
PPM logical object
PRC-DUPID
PROTNA
PROV-MISMATCH
PS
PSWD-CHG-REQUIRED
PTIM
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-13
Index
PWR-FAIL-A
PWR-FAIL-B
PWR-FAIL-RET-A
PWR-FAIL-RET-B
PWR logical object
R
RAI
RCVR-MISS
receive levels
RESERVED-RATE-EXCEEDED-RINGLET0
RESERVED-RATE-EXCEEDED-RINGLET1
RFI
ERFI-P-CONN
ERFI-P-SRVR
RFI-L
RFI-P
RFI-V
RING-MISMATCH
RING-SW-EAST
RMON-ALARM
RMON-RESET
ROLL
ROLL-PEND
RPRIF logical object
RPR-PEER-MISS
RPR-PROT-ACTIVE
RPR-PROT-CONFIG-MISMATCH 2-206
RPR-RI-FAIL
RPR-SD
RPR-SF
RPR-SPAN-MISMATCH
RPRW
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-14
RX levels
RX packet
S safety summary
see FC_MR-4 card
SD
DS1
DS3
E1
OTUK-SD
RPR-SD
SD-L
SD-L (trunk)
SD-P
SD-V
service-affecting alarms, definition 2-33
SESSION-TIME-LIMIT
severities
SF
AUTOSW-SFBER
DS1
DS3
E1
ODUK-SF-PM
OTUK-SF
RPR-SF
SF-L (trunk)
SF-P
SF-V
SFPs compatibility
install
November 2009
replace
SFTWDOWN
SHELF-COMM-FAIL
SH-INS-LOSS-VAR-DEG-HIGH
SH-INS-LOSS-VAR-DEG-LOW
SHUTTER-OPEN
external switching commands
SIGLOSS
SF
SMB connector
SNTP-HOST
SPAN-SW-WEST
SQM
SQUELCH
SSM do not use for synchronization
failure
quality level degrade
SSM-DUS
SSM-FAIL
SSM-LNC
SSM-OFF
SSM-PRC
SSM-PRS
SSM-RES
SSM-SDN-TN
SSM-SETS
SSM-SMC
SSM-ST2
SSM-ST3
SSM-ST4
SSM-STU
SSM-TNC
synchronization traceability alarm
November 2009
Index
storage access networking card see
FC_MR-4 card
STSMON
AUTOSW-UNEQ
STS-SQUELCH-L
STSTRM logical object
switching
automatic protection switching
external switching commands
SW-MISMATCH
SWMTXMOD-PROT
SWTOPRI
SWTOSEC
SWTOTHIRD
SYNC-FREQ
synchronization status messaging
see SSM
SYNCLOSS
SYNCSEC
T
TCC2 card communication failure (TCC2 to TCC2)
flash memory exceeded
jar file dowload problem
reseat (remove and reinsert)
reset
TCC2P card
communication failure (TCC2P to TCC2P) 2-65, 2-66
flash memory exceeded
jar file download problem
reseat (remove and reinsert)
reset
TCP/IP
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-15
Index
Telcordia signal degrade definition
signal failure definition
temperature fan-tray assembly alarm
high-temperature alarm
industrial high-temperature alarm 2-122
OC-192 alarm
TEMP-MISM
terminal loopback definition
clear an OC-N loopback circuit
electrical card example
perform on a destination electrical port
perform on a destination-node Ethernet port 1-83
perform on a destination-node FC_MR-4 card
perform on a destination-node OC-N port
perform on an intermediate-node Ethernet port
perform on an intermediate-node FC_MR-4 card
perform on an intermediate OC-N port
perform on a source-node electrical port
perform on a source node Ethernet port
perform on a source-node FC_MR-4 card 1-89
TIM perform on a source-node OC-N port
ODUK-TIM-PM
OTUK-TIM
PTIM
TIM-MON
TIM-P
TIM-S
TIM-V
timing alarms
64 clock bipolor density
SSM force switch to internal timing
force switch to primary timing
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-16
force switch to secondary timing 2-110
force switch to tertiary timing
free running synchronization
loss of frame on BITS
loss of primary reference
loss of service on BITS
loss of tertiary reference
synchronization
timing reference failure
timing reference automatic switch to secondary source
(condition)
automatic switch to third timing source
(condition)
change
manual switch to internal source (condition)
manual switch to primary source (condition)
manual switch to second source (condition)
manual switch to third source (condition) 2-174
switch error
TLINK logical object
TPTFAIL
CE1000
CE100T
FCMR
G1000
ML100T, ML1000, MLFX
TPTFAIL (ML1000)
TPTFAIL (MLFX)
transient conditions
transients are indexed individually by name
alphabetical list
characteristics
transmission failure
transmit levels
TRMT
TRMT-MISS
troubleshooting
see also alarm troubleshooting
November 2009
Index
alarm characteristics
conditions
frequently used procedures
service effect
severities
trouble notifications
TRUNK logical object
TX-AIS
Tx levels
TX-LOF
Tx packet
TX-RAI
U
UNEQ
AUTOSW-UNEQ (STSMON)
AUTOSW-UNEQ (VTMON)
UNEQ-V
UNIX incorrect colors
reset the CTC_HEAP environmental variable
UNREACHABLE-TARGET-POWER
USER-LOCKOUT
USER-LOGOUT
username/password mismatch
UT-COMM-FAIL
UT-FAIL
V
VCG-DEG
VCG-DOWN
VCG logical object
VirusScan, disable
VLAN cannot connect to network device
change tagged and untag settings
VOA
VOA-HDEG
VOA-HFAIL
VOA-LDEG
VOA-LFAIL
see power
VOLT-MISM
VT1.5 circuit creation error
VT-MON logical object
VT-TERM logical object
W
west or east misconnection alarm
WKSWBK
WKSWPR
workstation requirements
WRMRESTART
WTR
WTR-SPAN
X
XFPs compatibility
install
remove
November 2009
Cisco ONS 15454 Troubleshooting Guide, R7.2
IN-17
Index
IN-18
Cisco ONS 15454 Troubleshooting Guide, R7.2
November 2009
İndir
Herkese açık bağlantı güncellendi
Sohbetinize giden herkese açık bağlantı güncellendi. You may view and manage your chat links after registration here.
Belge herkese açık bağlantısı
Reklam