Cisco ONS 15454 Troubleshooting Guide, Release 5.0
Chapter 1, General Troubleshooting
Downloads: This chapterpdf (PDF - 2.33MB) The complete bookPDF (PDF - 8.4MB) | Feedback

General Troubleshooting

Table Of Contents

General Troubleshooting

1.1  Troubleshooting Non-DWDM Circuit Paths with Loopbacks

1.1.1  Facility Loopbacks

1.1.2  Terminal Loopbacks

1.1.3  Hairpin Circuits

1.1.4  Cross-Connect Loopbacks

1.2  Troubleshooting Electrical Circuit Paths With Loopbacks

1.2.1  Perform a Facility (Line) Loopback on a Source Electrical Port (West to East)

Create the Facility (Line) Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port

Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit

Create the Facility (Line) Loopback on the Source DS3E or DS3XM Port

Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit

Test the Electrical Cabling

Test the Electrical Card

Test the EIA

1.2.2  Perform a Hairpin Test on a Source-Node Electrical Port (West to East)

Create the Hairpin Circuit on the Source-Node Electrical Port

Test and Delete the Electrical Port Hairpin Circuit

Test the Standby XC10G Cross-Connect Card

Retest the Original XC10G Cross-Connect Card

1.2.3  Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal

Create the XC Loopback on a Destination-Node OCN STS

Test and Clear the XC Loopback Circuit

Test the Standby XC10G Cross-Connect Card

Retest the Original XC10G Cross-Connect Card

1.2.4  Perform a Terminal (Inward) Loopback on a Destination Electrical Port Port (West to East)

Create the Terminal (Inward) Loopback on a Destination DS-3, DS3N-12, DS3i-N-12, or EC1 Port

Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal Loopback Circuit

Create the Terminal (Inward) Loopback on a Destination DS-3E or DS3XM Port

Test and Clear the DS-3E or DS3XM Destination Port Terminal Loopback Circuit

Test the Destination Electrical Card

1.2.5  Perform a Facility (Line) Loopback on a Destination-Node Electrical Port (East to West)

Create the Facility (Line) Loopback on the Destination DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port

Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit

Create the Facility (Line) Loopback on the Source DS3E or DS3XM Port

Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit

Test the Electrical Cabling

Test the Electrical Card

Test the EIA

1.2.6  Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)

Create the Hairpin Circuit on the Destination-Node Port

Test and Delete the Electrical Hairpin Circuit

Test the Standby XC10G Cross-Connect Card

Retest the Original XC10G Cross-Connect Card

1.2.7  Perform an XC Loopback on a Source-Node OC-N STS (East to West)
Carrying an Electrical Circuit

Create the XC Loopback on the Source OC-N Port Carrying an Electrical Circuit

Test and Clear the XC Loopback Circuit

Test the Standby XC10G Cross-Connect Card

Retest the Original XC10G Cross-Connect Card

1.2.8  Perform a Terminal (Inward) Loopback on a Source-Node Electrical Port (East to West)

Create the Terminal (Inward) Loopback on a Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port

Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Terminal Loopback

Create the Terminal (Inward) Loopback on a Source DS3E or DS3XM Port

Test and Clear the DS3E or DS3XM Port Terminal Loopback Circuit

Test the Source Electrical Card

1.3  Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks

1.3.1  FEAC Send Code

1.3.2  DS-3E and DS3i-N-12 Inhibit Loopback

1.3.3  DS3XM-6 and DS3XM-12 Inhibit FEAC Loopback

1.3.4  FEAC Alarms

1.4  Troubleshooting Optical Circuit Paths With Loopbacks

1.4.1  Perform a Facility (Line) Loopback on a Source-Node Optical Port

Create the Facility (Line) Loopback on the Source Optical Port

Test and Clear the Facility (Line) Loopback Circuit

Test the OC-N Card

1.4.2  Perform a Terminal (Inward) Loopback on a Source-Node Optical Port

Create the Terminal (Inward) Loopback on a Source-Node Optical Port

Test and Clear the Terminal Loopback Circuit

Test the Optical Card

1.4.3  Perform an XC Loopback on the Source Optical Port

Create the XC Loopback on the Source-Node Optical Port

Test and Clear the XC Loopback Circuit

Test the Standby XC10G Cross-Connect Card

Retest the Original XC10G Cross-Connect Card

1.4.4  Perform a Facility (Line) Loopback on an Intermediate-Node Optical Port

Create a Facility (Line) Loopback on an Intermediate-Node Optical Port

Test and Clear the Facility (Line) Loopback Circuit

Test the Optical Card

1.4.5  Perform a Terminal (Inward) Loopback on Intermediate-Node Optical Ports

Create a Terminal Loopback on Intermediate-Node Optical Ports

Test and Clear the Optical Terminal Loopback Circuit

Test the Optical Card

1.4.6  Perform a Facility (Line) Loopback on a Destination-Node Optical Port

Create the Facility (Line) Loopback on a Destination-Node Optical Port

Test and Clear the Optical Facility (Line) Loopback Circuit

Test the Optical Card

1.4.7  Perform a Terminal Loopback on a Destination-Node Optical Port

Create the Terminal Loopback on a Destination-Node Optical Port

Test and Clear the Optical Terminal Loopback Circuit

Test the Optical Card

1.5  Troubleshooting Ethernet Circuit Paths With Loopbacks

1.5.1  Perform a Facility (Line) Loopback on a Source-Node Ethernet Port

Create the Facility (Line) Loopback on the Source-Node Ethernet Port

Test and Clear the Facility (Line) Loopback Circuit

Test the Ethernet Card

1.5.2  Perform a Terminal (Inward) Loopback on a Source-Node Ethernet Port

Create the Terminal (Inward) Loopback on a Source-Node Ethernet Port

Test and Clear the Ethernet Terminal Loopback Circuit

Test the Ethernet Card

1.5.3  Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port

Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port

Test and Clear the Ethernet Facility (Line) Loopback Circuit

Test the Ethernet Card

1.5.4  Create a Terminal (Inward) Loopback on Intermediate-Node Ethernet Ports

Create a Terminal Loopback on Intermediate-Node Ethernet Ports

Test and Clear the Ethernet Terminal Loopback Circuit

Test the Ethernet Card

1.5.5  Perform a Facility (Line) Loopback on a Destination-Node Ethernet Port

Create the Facility (Line) Loopback on a Destination-Node Ethernet Port

Test and Clear the Ethernet Facility (Line) Loopback Circuit

Test the Ethernet Card

1.5.6  Perform a Terminal Loopback on a Destination-Node Ethernet Port

Create the Terminal Loopback on a Destination-Node Ethernet Port

Test and Clear the Ethernet Terminal Loopback Circuit

Test the Ethernet Card

1.6  Troubleshooting MXP, TXP, or FC_MR-4 Circuit Paths With Loopbacks

1.6.1  Perform a Facility (Line) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port

Create the Facility (Line) Loopback on the Source-Node MXP/TXP/FC_MR-4 Port

Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.6.2  Perform a Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port

Create the Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port

Test and Clear the MXP/TXP/FC_MR-4 Port Terminal Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.6.3  Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port

Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port

Test and Clear the MXP/TXP/FC_MR-4 Port Facility (Line) Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.6.4  Create a Terminal (Inward) Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports

Create a Terminal Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports

Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.6.5  Perform a Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port

Create the Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port

Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.6.6  Perform a Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port

Create the Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port

Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit

Test the MXP/TXP/FC_MR-4 Card

1.7  Troubleshooting DWDM Circuit Paths With ITU-T G.709 Monitoring

1.7.1  G.709 Monitoring in Optical Transport Networks

1.7.2  Optical Channel Layer

1.7.3  Optical Multiplex Section Layer

1.7.4  Optical Transmission Section Layer

1.7.5  Performance Monitoring Counters and Threshold Crossing Alerts

Set Node Default BBE or SES Card Thresholds

Provision Individual Card BBE or SES Thresholds in CTC

Provision Card PM Thresholds Using TL1

Provision Optical TCA Thresholds

1.7.6  Forward Error Correction

Provision Card FEC Thresholds

1.7.7  Sample Trouble Resolutions

1.8  Using CTC Diagnostics

1.8.1  Card LED Lamp Tests

Verify General Card LED Operation

Verify G-Series Ethernet or FC_MR-4 Card Port-Level LED Operation

Verify E-Series and ML-Series Ethernet Card Port-Level LED Operation

1.8.2  Retrieve Diagnostics File Button

Off-Load the Diagnostics File

1.8.3  Bidirectional Diagnostic Circuit

Create a Bidirectional Diagnostic Circuit

1.9  Restoring the Database and Default Settings

1.9.1  Restore the Node Database

Restore the Database

1.9.2  Restore the Node to Factory Configuration

Use the Reinitialization Tool to Clear the Database and Upload Software (Windows)

Use the Reinitialization Tool to Clear the Database and Upload Software (UNIX)

1.10  PC Connectivity Troubleshooting

1.10.1  PC System Minimum Requirements

1.10.2  Sun System Minimum Requirements

1.10.3  Supported Platforms, Browsers, and JREs

1.10.4  Unsupported Platforms and Browsers

1.10.5  Unable to Verify the IP Configuration of Your PC

Verify the IP Configuration of Your PC

1.10.6  Browser Login Does Not Launch Java

Reconfigure the PC Operating System Java Plug-in Control Panel

Reconfigure the Browser

1.10.7  Unable to Verify the NIC Connection on Your PC

1.10.8  Verify PC Connection to the ONS 15454 (ping)

Ping the ONS 15454

1.10.9  The IP Address of the Node is Unknown

Retrieve Unknown Node IP Address

1.11  CTC Operation Troubleshooting

1.11.1  CTC Colors Do Not Appear Correctly on a UNIX Workstation

Limit Netscape Colors

1.11.2  Unable to Launch CTC Help After Removing Netscape

Reset Internet Explorer as the Default Browser for CTC

1.11.3  Unable to Change Node View to Network View

Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Windows

Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Solaris

1.11.4  Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P

Disable the VirusScan Download Scan

1.11.5  CTC Does Not Launch

Redirect the Netscape Cache to a Valid Directory

1.11.6  Slow CTC Operation or Login Problems

Delete the CTC Cache File Automatically

Delete the CTC Cache File Manually

1.11.7  Node Icon is Gray on CTC Network View

1.11.8  CTC Cannot Launch Due to Applet Security Restrictions

Manually Edit the java.policy File

1.11.9  Java Runtime Environment Incompatible

Launch CTC to Correct the Core Version Build

1.11.10  Different CTC Releases Do Not Recognize Each Other

Launch CTC to Correct the Core Version Build

1.11.11  Username or Password Do Not Match

Verify Correct Username and Password

1.11.12  No IP Connectivity Exists Between Nodes

1.11.13  DCC Connection Lost

1.11.14  "Path in Use" Error When Creating a Circuit

1.11.15  Calculate and Design IP Subnets

1.11.16  Ethernet Connections

Verify Ethernet Connections

1.11.17  VLAN Cannot Connect to Network Device from Untag Port

Change VLAN Port Tag and Untagged Settings

1.12  Circuits and Timing

1.12.1  OC-N Circuit Transitions to Partial State

View the State of OC-N Circuit Nodes

1.12.2  AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits

Clear AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits

1.12.3  Circuit Creation Error with VT1.5 Circuit

1.12.4  Unable to Create Circuit From DS-3 Card to DS3XM-6 or DS3XM-12 Card

1.12.5  DS-3 Card Does Not Report AIS-P From External Equipment

1.12.6  OC-3 and DCC Limitations

1.12.7  ONS 15454 Switches Timing Reference

1.12.8  Holdover Synchronization Alarm

1.12.9  Free-Running Synchronization Mode

1.12.10  Daisy-Chained BITS Not Functioning

1.12.11  Blinking STAT LED after Installing a Card

1.13  Fiber and Cabling

1.13.1  Bit Errors Appear for a Traffic Card

1.13.2  Faulty Fiber-Optic Connections

Verify Fiber-Optic Connections

Remove GBIC or SFP Connectors

Installing a GBIC with Clips

Installing a GBIC with a Handle

1.13.3  OC-N Card Transmit and Receive Levels

1.14  Power Supply Problems

Isolate the Cause of Power Supply Problems

1.14.1  Power Consumption for Node and Cards


General Troubleshooting



Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. 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 Troubleshooting." If you cannot find what you are looking for, contact the Cisco Technical Assistance Center (1 800 553-2447).

This chapter includes the following sections on network problems:

Troubleshooting Non-DWDM Circuit Paths with Loopbacks—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 "NTP-G16" in the Cisco ONS 15454 DWDM Installation and Operations Guide.


Troubleshooting Electrical Circuit Paths With Loopbacks—Explains how to use loopback tests described in "Troubleshooting Non-DWDM Circuit Paths with Loopbacks" to isolate trouble on DS-1, DS-3, or EC-1 electrical circuits.

Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks—Describes how DS3XM-6 and DS3XM-12 card far-end alarm and control (FEAC) functions.

Troubleshooting Optical Circuit Paths With Loopbacks—Explains how to use loopback tests described in "Troubleshooting Non-DWDM Circuit Paths with Loopbacks" to isolate trouble on OC-N optical circuits.

Troubleshooting Ethernet Circuit Paths With Loopbacks—Explains how to use loopback tests described in "Troubleshooting Non-DWDM Circuit Paths with Loopbacks" to isolate trouble on G-Series or CE-Series Ethernet circuits.

Troubleshooting MXP, TXP, or FC_MR-4 Circuit Paths With Loopbacks—Explains how to use loopbacks tests described in "Troubleshooting Non-DWDM Circuit Paths with Loopbacks" to isolate trouble on muxponder (MXP), transponder (TXP), or Fibre Channel (FC_MR) circuits.

Troubleshooting DWDM Circuit Paths With ITU-T G.709 Monitoring—Explains how to utilize performance monitoring (PM) and threshold crossing alerts (TCA) to locate signal degrades on DWDM circuit paths.

The remaining sections describe symptoms, problems, and solutions that are categorized according to the following topics:

Using CTC Diagnostics—Explains how to perform card LED tests, download a diagnostic file for Cisco Technical Support, and create a bidirectional diagnostic VT circuit.

Restoring the Database and Default Settings—Provides procedures for restoring software data and restoring the node to the default setup.

PC Connectivity Troubleshooting—Provides troubleshooting procedures for PC and network connectivity to the ONS 15454.

CTC Operation Troubleshooting—Provides troubleshooting procedures for Cisco Transport Controller (CTC) login or operation problems.

Circuits and Timing—Provides troubleshooting procedures for circuit creation and error reporting as well as timing reference errors and alarms.

Fiber and Cabling—Provides troubleshooting procedures for fiber and cabling connectivity errors.

Power Supply Problems—Provides troubleshooting procedures for power supply problems.

1.1  Troubleshooting Non-DWDM 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, MXP, TXP 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.

To create a loopback on a port, the port must be in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state. The resulting service state is Out-of-Service and Management, Loopback and Maintenance (OOS-MA,LPBK & MT).


Caution Facility (line) 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 exist in the Chapter 2, "Alarm Troubleshooting." For more information about these operations, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Caution On all OC-N cards, a facility (line) 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.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 (line) 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. Figure 1-1 shows a facility loopback on a DS-N electrical card.

Figure 1-1 Facility (Line) Loopback Path on a Near-End DS-N Card

To test an OC-N card LIU, connect an optical test set to the OC-N port and perform a facility (line) loopback. Alternately, use a loopback or hairpin circuit on a card that is farther along the circuit path. Figure 1-2 shows a facility loopback on an OC-N card.

Figure 1-2 Facility (Line) Loopback Path on a Near-End OC-N Card

In CTC, OC-N cards with facility loopbacks show an icon (Figure 1-5). Loopback icons are not shown on other cards in this release.

Figure 1-3 OC-N Facility Loopback Indicator


Caution Before performing a facility (line) 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.

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, MXP, TXP, and FC_MR-4 facility loopbacks are terminated as shown in Table 1-1.

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
Facility Loopback Signal

DS-1

Terminated

DS-3

Terminated

DS3XM-6 or DS3XM-12

Terminated

All OC-N cards

Terminated

EC-1

Terminated

G-Series Ethernet

Terminated1

MXP, MXPP trunk ports

Bridged

MXP, MXPP client ports

Terminated

TXP, MXPP trunk ports

Bridged

TXP, MXPP client ports

Terminated

1 G-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 window would list the LPBKFACILITY condition in the for a tested port. (The Alarms window will show AS-MT, which means that alarms are suppressed on the facility during loopback.)

In addition to the Conditions window listing, the following behaviors occur:

If an electrical or optical port is in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state, it 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 would also cause an AIS signal to be injected. For more information about placing ports into alternate states for testing, refer to the Cisco ONS 15454 Procedure Guide Chapter 11, "Change Card Settings."

MXP, TXP, and 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.

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 (XC10G) 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

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

Figure 1-6 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.

Figure 1-6 Terminal Loopback Path on a DS-N Card

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, MXP, TXP, and FC_MR-4 terminal loopbacks are terminated as shown in Table 1-2. 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.

ONS 15454 card terminal loopback bridging and terminating behaviors are listed in Table 1-2.


Note In Table 1-2, no AIS signal 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-2 ONS 15454 Card Terminal Loopback Behavior

Card/Port
Terminal Loopback Signal

DS-1

Terminated

DS-3

Bridged

DS3XM-6 or DS3XM-12

Bridged

All OC-N cards

Bridged

EC-1

Bridged

G-Series Ethernet

Terminated1

MXP, MXPP trunk ports

Bridged

MXP, MXPP client ports

Terminated

TXP, MXPP trunk ports

Bridged

TXP, MXPP client ports

Terminated

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.


Bridged DS-N and OC-N terminal loopback examples are shown in Figure 1-7 and Figure 1-8.

Figure 1-7 Terminal Loopback on a DS-N Card with Bridged Signal

Figure 1-8 Terminal Loopback on an OC-N Card with Bridged Signal

G-Series Ethernet cards placed in terminal loopback have different performance monitoring behavior from other ONS 15454 cards. (For more information about performance monitoring counters, see Chapter 4, "Performance Monitoring.") 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 statistic is not based on the 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 does result 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 looped-back packets follow the G-Series card's normal receive path and register on the Rx Packet counter.

MXP and TXP card trunk and client ports have different service state behaviors and requirements from other ONS 15454 cards. The cards can simultaneously maintain different service states.

For TXP and TXPP cards with a client-side terminal loopback, the client port is in the OOS-MA,LPBK & MT service state and trunk port must be in IS-NR service state.

For MXP and MXPP cards with a client-side terminal loopback, the client port is in the OOS-MA,LPBK & MT service state and the remaining client and trunk ports can be in any service state.

In MXP or TXP trunk-side terminal loopbacks, the trunk port is in the OOS-MA,LPBK & MT service state and the client ports must be in IS-NR service state for complete loopback functionality. A terminal loopback affects all client ports because it is performed on the aggregate signal.

The loopback itself is listed in the Conditions window. For example, the window would list the LPBKTERMINAL condition or 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.)

In addition to the Conditions window listing, the following behaviors occur:

If an electrical or optical port is in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state, it injects an AIS signal upstream and downstream.

When an electrical or optical port is placed in the Out-of-Service and Management, Maintenance (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 would also cause an AIS signal to be injected. For more information about placing ports into alternate states for testing, refer to the Cisco ONS 15454 Procedure Guide Chapter 11, "Change Card Settings."

1.1.3  Hairpin Circuits

A hairpin circuit brings traffic in and out on a 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, thus preventing a drop of all traffic on the OC-N port. The hairpin allows you to test a specific STS or VT circuit on nodes running live traffic. Figure 1-9 shows the hairpin circuit path on a DS-N card.

Figure 1-9 Hairpin Circuit Path on a DS-N Card

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 loop back a single STS-1, STS-3c, STS-6c, etc. on an optical facility (line) 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 Figure 1-10.

Figure 1-10 Network Element with SONET Cross-Connect Loopback Function

When creating cross-connect loopbacks, consult the following rules:

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 (line) loopbacks, terminal (inward) 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 bidirectional line-switched ring (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. A facility (line) loopback on the source-node electrical port (DS-N or EC-N)

2. A hairpin on the source-node electrical port

3. An XC loopback on the destination-node OC-N STS (carrying the electrical circuit)

4. A terminal (inward) loopback on the destination-node electrical port

East-to-west direction (right to left):

1. A facility (line) loopback on the destination-node electrical port

2. A hairpin on the destination-node electrical port

3. An XC loopback on the source-node OC-N STS (carrying the electrical circuit)

4. A terminal (inward) loopback on the source-node electrical port


Note Facility, hairpin, and terminal loopback tests require on-site personnel.


1.2.1  Perform a Facility (Line) Loopback on a Source Electrical Port (West to East)

The facility (line) loopback test is performed on the node source electrical port in the network circuit; in this example, the DS-N port in the source node. Completing a successful facility (line) loopback on this port isolates the cabling, the electrical card, and the EIA as possible failure points. Figure 1-11 shows an example of a facility loopback on a source DS-N port.

Figure 1-11 Facility (Line) Loopback on a Circuit Source DS-N Port


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 Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Note DS-3 facility (line) loopbacks do not transmit an AIS condition in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Depending upon your card type, complete the "Create the Facility (Line) Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure or the "Create the Facility (Line) Loopback on the Source DS3E or DS3XM Port" procedure, then test and clear the loopbacks as instructed.

Create the Facility (Line) Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port


Step 1 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In node view, double-click the card to display the card view.

Step 4 Click the Maintenance > Loopback tab.

Step 5 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.

Step 6 Choose Facility (Line) 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.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (DS1, DS3)" condition on page 2-168 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" procedure.


Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Double-click the card to display the card view.

Step 4 Depending upon the card type, click the Maintenance > Loopback tab.

Step 5 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Cabling" procedure.


Create the Facility (Line) 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 this information, refer to the "Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks" section.


Step 1 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In node view, double-click the card to display the card view.

Step 4 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 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 has been placed in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.

Step 6 Choose Facility (Line) 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.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (DS1, DS3)" condition on page 2-168 to appear during loopback setup. The condition clears when you remove the loopback.


Step 9 Complete the "Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit" procedure.


Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Double-click the card to display the card view.

Step 4 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 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Cabling" procedure.


Test the Electrical Cabling


Step 1 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 Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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.

Step 2 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.

Step 3 Replace the defective cable.

Step 4 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 5 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Card" procedure.


Test the Electrical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the Return Materials Authorization (RMA) process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 6 Choose None from the Loopback Type column for the port being tested.

Step 7 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 8 Click Apply.

Step 9 Click Yes in the confirmation dialog box.

Step 10 Complete the "Test the EIA" procedure.


Test the EIA


Step 1 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. Loosen the nine perimeter screws that hold the EIA panel in place.

c. Lift the EIA panel by the bottom to remove it from the shelf assembly.

d. Follow the installation procedure for the appropriate EIA. See the Cisco ONS 15454 Procedure Guide Chapter 1, "Install the Shelf and Backplane Cable," for instructions.

Step 2 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 Step 16. If the problem persists and the EIA is not shown to be improperly seated, proceed to Step 3.

Step 3 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 4 Choose None from the Loopback Type column for the port being tested.

Step 5 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 6 Click Apply.

Step 7 Click Yes in the confirmation dialog box. Proceed to Step 16.

Step 8 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 (1 800 553-2447).

Step 9 Replace the faulty EIA by completing the "Replace the Electrical Interface Assembly" procedure on page 2-278.

Step 10 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.

Step 11 If the test set indicates a good circuit, the problem was probably the defective EIA. Clear the facility (line) loopback by clicking the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.

Step 12 Choose None from the Loopback Type column for the port being tested.

Step 13 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 14 Click Apply.

Step 15 Click Yes in the confirmation dialog box.

Step 16 Complete the "Perform a Hairpin Test on a Source-Node Electrical Port (West to East)" procedure.


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. Figure 1-12 shows an example of a hairpin loopback on a source-node port.

Figure 1-12 Hairpin on a Source-Node Port


Note The ONS 15454 does not support simplex operation on the XC10G cross-connect card. Two cross-connect cards of the same type must be installed for each node.


Complete the "Create the Hairpin Circuit on the Source-Node Electrical Port" procedure.

Create the Hairpin Circuit on the Source-Node Electrical Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform a Facility (Line) Loopback on a Source Electrical Port (West to East)" procedure, 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the hairpin circuit on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as Hairpin1.

e. Choose the Size, such as STS-1.

f. Uncheck the Bidirectional check box. Leave the default values for State, SD Threshold, and SF Threshold.

g. Click Next.

h. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. Leave Use Secondary Source unchecked.

i. Click Next.

j. In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. Leave Use Secondary Destination unchecked.

k. Click Next.

l. In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish.

Step 4 Confirm that the newly created circuit appears on the Circuits tab and that the Dir column describes it as a one-way circuit.

Step 5 Complete the "Test and Delete the Electrical Port Hairpin Circuit" procedure.


Test and Delete the Electrical Port Hairpin Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin circuit. Clear the hairpin circuit:

a. Click the Circuits tab.

b. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 4 Complete the "Test the Standby XC10G Cross-Connect Card" procedure.


Test the Standby XC10G Cross-Connect Card


Note Two XC10G 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 XC10G 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. Position the cursor over the standby cross-connect card.

c. Right-click and choose RESET CARD.

d. Click Yes in the confirmation dialog box.

Step 2 Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:


Caution Cross-connect side switches are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms.

a. Determine the standby XC10G 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. In the node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active XC10G 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 Resend test traffic on the loopback circuit.

The test traffic now travels through the alternate cross-connect card.

Step 4 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. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 5 To confirm a defective original cross-connect card, complete the "Retest the Original XC10G Cross-Connect Card" procedure.


Retest the Original XC10G Cross-Connect Card


Step 1 Initiate an external switching command (side switch) on the XC10G 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. In node view, select the Maintenance > Cross-Connect > Cards tab.

c. From the Cross-Connect Cards menu, choose Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 2 Resend test traffic on the loopback circuit.

Step 3 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 (1 800 553-2447) and proceed to Step 4. If the test does not indicate a faulty circuit, proceed to Step 5.

Step 4 Complete the "Physically Replace an In-Service Cross-Connect Card" procedure on page 2-271 for the defective card.

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 hairpin circuit:

a. Click the Circuits tab.

b. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 6 Complete the "Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal" procedure.


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 XC10G cross-connect card in a network circuit. Figure 1-13 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 You can perform an XC loopback on either the circuit source working or the protect port of a 1+1 protection group.


Figure 1-13 XC Loopback on a Destination OC-N Port

Create the XC Loopback on a Destination-Node OCN STS


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Hairpin Test on a Source-Node Electrical Port (West to East)" procedure, leave the optical test set hooked up to the destination-node port.

b. 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to put the circuit being tested out of service:

a. In node view, click the Circuits tab.

b. Click the circuit and then click Edit.

c. In the Edit Circuit dialog box, click the State tab.

d. Choose OOS,MT from the Target Circuit Admin State drop-down list.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Use CTC to set up the XC loopback on the circuit being tested:

a. In node view, double-click the OC-N card to display the card view.

b. Click the Maintenance > Loopback > SONET STS tab.

c. Click the check box in the XC Loopback column for the port being tested.

d. Check Apply.

e. Click Yes in the confirmation dialog box.

Step 5 Complete the "Test and Clear the XC Loopback Circuit" procedure.


Test and Clear the XC Loopback Circuit


Note This procedure is performed only on OC-N cards.



Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the XC loopback:

a. In card view, click the Maintenance > Loopback > SONET STS tab.

b. Uncheck the check box in the XC Loopback column for the circuit being tested.

c. Click Apply.

d. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the Standby XC10G Cross-Connect Card" procedure.


Test the Standby XC10G Cross-Connect Card


Step 1 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. Position the cursor over the standby cross-connect card.

c. Right-click and choose RESET CARD.

d. Click Yes in the confirmation dialog box.

Step 2 Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:


Caution Cross-connect side switches are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms.

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. In the node view, select the Maintenance > Cross-Connect > Card tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 3 Resend test traffic on the loopback circuit.

The test traffic now travels through the alternate cross-connect card.

Step 4 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. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the 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.

Step 5 To confirm a defective original cross-connect card, complete the "Retest the Original XC10G Cross-Connect Card" procedure.


Retest the Original XC10G Cross-Connect Card


Note This procedure is performed only on OC-N and XC10G 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. In node view, select the Maintenance > Cross-Connect > Card tabs.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 2 Resend test traffic on the loopback circuit.

Step 3 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 (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.

Step 4 Complete the "Physically Replace an In-Service Cross-Connect Card" procedure on page 2-271 for the defective cross-connect card and perform Step 5.

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. Click the Circuits tab.

b. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 6 If the tests indicate further problems, go to the "Perform a Terminal (Inward) Loopback on a Destination Electrical Port Port (West to East)" procedure.


1.2.4  Perform a Terminal (Inward) Loopback on a Destination Electrical Port Port (West to East)

The terminal (inward) loopback test is performed on the destination-node electrical port in the circuit, such as a destination-node DS-N port or EC-1 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 DS-N. Figure 1-14 shows an example of a terminal loopback on a destination DS-N port.

Figure 1-14 Terminal (Inward) Loopback to a Destination DS-N Port


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 Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Note DS-3 terminal loopbacks do not transmit an AIS condition in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Depending upon your card type, complete the "Create the Terminal (Inward) Loopback on a Destination DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure or the"Create the Terminal (Inward) Loopback on a Destination DS-3E or DS3XM Port" procedure. Then test and clear the loopback as instructed.

Create the Terminal (Inward) Loopback on a Destination DS-3, DS3N-12, DS3i-N-12, or EC1 Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal" procedure, 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In CTC node view, click the Circuits tab and click Create.

Step 4 In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

Step 5 Click Next

Step 6 In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS2.

Step 7 Leave the Bidirectional check box checked.

Step 8 Click Next.

Step 9 In the Circuit Creation source dialog box, select the Node, card Slot, Port, and STS (or VT) where the test set is connected.

Step 10 Click Next.

Step 11 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.

Step 12 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-172 to appear during a loopback setup. The condition clears when you remove the loopback.



Note DS-3 terminal loopbacks do not transmit a DS-3 AIS (see the "AIS" condition on page 2-30) in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Step 13 Create the terminal (inward) 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. In node view, double-click the card that requires the loopback, such as a DS-N card in the destination node.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 14 Complete the "Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal Loopback Circuit" procedure.


Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Destination Port Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Double-click the electrical card in the destination node with the terminal loopback.

Step 4 Click the Maintenance > Loopback tab.

Step 5 Select None from the Loopback Type column for the port being tested.

Step 6 Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Clear the terminal loopback:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 10 Complete the "Test the Destination Electrical Card" procedure.


Create the Terminal (Inward) Loopback on a Destination DS-3E or DS3XM Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform an XC Loopback on a Destination-Node OC-N STS (West to East) Carrying an Electrical Signal" procedure, 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 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.)

Step 2 In CTC node view, click the Circuits tab and click Create.

Step 3 In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

Step 4 Click Next.

Step 5 In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS3.

Step 6 Leave the Bidirectional check box checked.

Step 7 Click Next.

Step 8 In the Circuit Creation source dialog box, select the Node, card Slot, Port, and STS (or VT) where the test set is connected.

Step 9 Click Next.

Step 10 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. Click Next.

e. In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish.

Step 11 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-172 to appear during a loopback setup. The condition clears when you remove the loopback.



Note DS-3 terminal loopbacks do not transmit a DS-3 AIS (see the "AIS" condition on page 2-30) in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Step 12 Create the terminal (inward) 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. In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.

c. Click the Maintenance > DS3 tabs.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


d. 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 has been placed in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 13 Complete the "Test and Clear the DS-3E or DS3XM Destination Port Terminal Loopback Circuit" procedure.


Test and Clear the DS-3E or DS3XM Destination Port Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Double-click the electrical card in the destination node with the terminal loopback.

Step 4 Click the Maintenance > DS3 tabs.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 5 Select None from the Loopback Type column for the port being tested.

Step 6 Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Clear the terminal loopback:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 10 Complete the "Test the Destination Electrical Card" procedure.


Test the Destination Electrical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective electrical card.

Step 5 Clear the terminal (inward) loopback state on the port:

a. Double-click the electrical card in the destination node with the terminal loopback.

b. Depending upon the card type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Delete the terminal (inward) loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Facility (Line) Loopback on a Destination-Node Electrical Port (East to West)" procedure.


1.2.5  Perform a Facility (Line) Loopback on a Destination-Node Electrical Port (East to West)

The facility (line) loopback test is performed on the destination-node electrical port in the network circuit. Completing a successful facility (line) loopback on this port isolates the cabling, the electrical card, and the EIA as possible failure points. Figure 1-15 shows an example of a facility loopback on a destination DS-N port.

Figure 1-15 Facility (Line) Loopback on a Circuit Destination DS-N Port


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 "2.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information about these operations, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Note DS-3 facility (line) loopbacks do not transmit an AIS condition in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Depending upon your card type, complete the "Create the Facility (Line) Loopback on the Destination DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure or the "Create the Facility (Line) Loopback on the Source DS3E or DS3XM Port" procedure. Then test and clear the loopback as instructed.

Create the Facility (Line) Loopback on the Destination DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform a Terminal (Inward) Loopback on a Destination Electrical Port Port (West to East)" procedure, leave the electrical test set hooked up to the destination-node port.

b. 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In CTC node view, double-click the card to display the card view.

Step 4 Click the Maintenance > Loopback tab.

Step 5 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.

Step 6 Choose Facility (Line) 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.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.


Note It is normal for a "LPBKFACILITY (DS1, DS3)" condition on page 2-168 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" procedure.


Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Facility Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Double-click the card to display the card view.

Step 4 Click the Maintenance > Loopback tab.

Step 5 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Cabling" procedure.


Create the Facility (Line) 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 this information, refer to the "Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks" section.


Step 1 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.)

Step 2 In CTC node view, double-click the card to display the card view.

Step 3 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 4 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 has been placed in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.

Step 5 Choose Facility (Line) 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.

Step 6 Click Apply.

Step 7 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (DS1, DS3)" condition on page 2-168 to appear during loopback setup. The condition clears when you remove the loopback.


Step 8 Complete the "Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit" procedure.


Test and Clear the DS3E or DS3XM Port Facility Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Double-click the card to display the card view.

Step 4 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 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Cabling" procedure.


Test the Electrical Cabling


Step 1 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 Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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.

Step 2 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.

Step 3 Replace the defective cable.

Step 4 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 5 Choose None from the Loopback Type column for the port being tested.

Step 6 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test the Electrical Card" procedure.


Test the Electrical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "2.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260 for basic procedures. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 6 Choose None from the Loopback Type column for the port being tested.

Step 7 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 8 Click Apply.

Step 9 Click Yes in the confirmation dialog box.

Step 10 Complete the "Test the EIA" procedure.


Test the EIA


Step 1 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. Loosen the nine perimeter screws that hold the EIA panel in place.

c. Lift the EIA panel by the bottom to remove it from the shelf assembly.

d. Follow the installation procedure for the appropriate EIA. See the Cisco ONS 15454 Procedure Guide Chapter 1, "Install the Shelf and Backplane Cable," for instructions.

Step 2 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 Step 16. If the problem persists and the EIA is not shown to be improperly seated, proceed to Step 3.

Step 3 In card view for the electrical card, depending upon the type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 4 Choose None from the Loopback Type column for the port being tested.

Step 5 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 6 Click Apply.

Step 7 Click Yes in the confirmation dialog box.

Step 8 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 (1 800 553-2447).

Step 9 Replace the faulty EIA. Complete the "Replace the Electrical Interface Assembly" procedure on page 2-278.

Step 10 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.

Step 11 If the test set indicates a good circuit, the problem was probably the defective EIA. Clear the facility (line) loopback by clicking the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.

Step 12 Choose None from the Loopback Type column for the port being tested.

Step 13 Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

Step 14 Click Apply.

Step 15 Click Yes in the confirmation dialog box.

Step 16 Complete the "Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)" procedure.


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. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through the card isolates the possibility that the cross-connect card is the cause of the faulty circuit. Figure 1-16 shows an example of a hairpin loopback on a destination-node port.

Figure 1-16 Hairpin on a Destination-Node DS-N Port


Note The ONS 15454 does not support simplex operation on the XC10G cross-connect card. Two cross-connect cards of the same type must be installed for each node.


Complete the "Create the Hairpin Circuit on the Destination-Node Port" procedure.

Create the Hairpin Circuit on the Destination-Node Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform a Facility (Line) Loopback on a Destination-Node Electrical Port (East to West)" procedure, leave the electrical test set hooked up to the electrical port in the destination node.

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. The Tx and Rx terminals connect to the same port.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the hairpin circuit on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as Hairpin1.

e. Choose the Size, such as STS-1.

f. Uncheck the Bidirectional check box. Leave the default values for State, SD Threshold, and SF Threshold.

g. Click Next.

h. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected. Leave Use Secondary Source unchecked.

i. Click Next.

j. In the Circuit Creation destination dialog box, use the same Node, card Slot, Port, and STS (or VT) used for the source dialog box. Leave Use Secondary Destination unchecked.

k. Click Next.

l. In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish.

Step 4 Confirm that the newly created circuit appears on the Circuits tab and that the Dir column describes it as a one-way circuit.

Step 5 Complete the "Test and Delete the Electrical Hairpin Circuit" procedure.


Test and Delete the Electrical Hairpin Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin circuit. Clear the hairpin circuit:

a. Click the Circuits tab.

b. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 4 Complete the "Test the Standby XC10G Cross-Connect Card" procedure.


Test the Standby XC10G Cross-Connect Card


Note Two XC10G 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 XC10G 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. Position the cursor over the standby cross-connect card.

c. Right-click and choose RESET CARD.

d. Click Yes in the confirmation dialog box.

Step 2 Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:


Caution Cross-connect side switches are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms.

a. Determine the standby XC10G 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. In the node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active XC10G 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 Resend test traffic on the loopback circuit.

The test traffic now travels through the alternate cross-connect card.

Step 4 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. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 5 To confirm a defective original cross-connect card, complete the "Retest the Original XC10G Cross-Connect Card" procedure.


Retest the Original XC10G Cross-Connect Card


Step 1 Initiate an external switching command (side switch) on the XC10G 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. In node view, select the Maintenance > Cross-Connect > Cards tab.

c. From the Cross-Connect Cards menu, choose Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 2 Resend test traffic on the loopback circuit.

Step 3 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 (1 800 553-2447) and proceed to Step 4. If the test does not indicate a faulty circuit, proceed to Step 5.

Step 4 Complete the "Physically Replace an In-Service Cross-Connect Card" procedure on page 2-271 for the defective cross-connect card.

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 hairpin circuit:

a. Click the Circuits tab.

b. Choose the hairpin circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the hairpin circuit is deleted from the Circuits tab list.

Step 6 Complete the "Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit" procedure.


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 any problem exists on the circuit's OC-N span, isolating this span from others present on the card. It also eliminates the cross-connect card as the source of trouble for a faulty circuit. The loopback occurs on the XC10G cross-connect card in a network circuit. Figure 1-17 shows an 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 You can perform an XC loopback on either the circuit source working or the protect port of a 1+1 protection group.


Figure 1-17 XC Loopback on a Source OC-N Port

Complete the "Create the XC Loopback on the Source OC-N Port Carrying an Electrical Circuit" procedure.

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 Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Hairpin Test on a Destination-Node Electrical Port (East to West)" section, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to put the circuit being tested out of service:

a. In node view, click the Circuits tab.

b. Click the circuit and then click Edit.

c. In the Edit Circuit dialog box, click the State tab.

d. Choose OOS,MT from the Target Circuit Admin State drop-down list.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Use CTC to set up the XC loopback on the circuit being tested:

a. In node view, double-click the OC-N card to display the card view.

b. Click the Maintenance > Loopback > SONET STS tab.

c. Check the XC Loopback column check box for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 5 Complete the "Test and Clear the XC Loopback Circuit" procedure.


Test and Clear the XC Loopback Circuit


Note This procedure is performed only on OC-N cards.



Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the XC loopback:

a. In card view, click the Maintenance > Loopback > SONET STS tab.

b. Uncheck the check box in the XC Loopback column for the circuit being tested.

c. Click Apply.

d. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the Standby XC10G Cross-Connect Card" procedure.


Test the Standby XC10G Cross-Connect Card


Step 1 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. Position the cursor over the standby cross-connect card.

c. Right-click and choose RESET CARD.

d. Click Yes in the confirmation dialog box.

Step 2 Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:


Caution Cross-connect side switches are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms.

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. In the node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 3 Resend test traffic on the loopback circuit.

The test traffic now travels through the alternate cross-connect card.

Step 4 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. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the 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.

Step 5 To confirm a defective original cross-connect card, complete the "Retest the Original XC10G Cross-Connect Card" procedure.


Retest the Original XC10G Cross-Connect Card


Note This procedure is performed only on OC-N and XC10G 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. In node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 2 Resend test traffic on the loopback circuit.

Step 3 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 (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.

Step 4 Complete the "Physically Replace an In-Service Cross-Connect Card" procedure on page 2-271 for the defective cross-connect card. Perform Step 5.

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. Click the Circuits tab.

b. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. If the problem is not resolved, go to the "Perform a Terminal (Inward) Loopback on a Source-Node Electrical Port (East to West)" section.


1.2.8  Perform a Terminal (Inward) Loopback on a Source-Node Electrical Port (East to West)

The terminal (inward) loopback test is performed on the source-node electrical port in the circuit, such as a source-node DS-N port or EC-1 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 (Inward) Loopback on a Source DS-N Port


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. See the "2.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260 for basic instructions. For more information about these operations, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Note DS-3 terminal loopbacks do not transmit an AIS condition in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Depending upon your card type, complete the "Create the Terminal (Inward) Loopback on a Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure or the "Create the Terminal (Inward) Loopback on a Source DS3E or DS3XM Port" procedure. Then test and clear the loopback as instructed.

Create the Terminal (Inward) Loopback on a Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit" procedure, leave the electrical test set hooked up 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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In CTC node view, click the Circuits tab and click Create.

Step 4 In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

Step 5 Click Next.

Step 6 In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS4.

Step 7 Leave the Bidirectional check box checked.

Step 8 Click Next.

Step 9 In the Circuit Creation source dialog box, select the Node, card Slot, Port, and STS (or VT) where the test set is connected.

Step 10 Click Next.

Step 11 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.

Step 12 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-172 to appear during a loopback setup. The condition clears when you remove the loopback.



Note DS-3 terminal loopbacks do not transmit a DS-3 AIS (see the "AIS" condition on page 2-30) in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Step 13 Create the terminal (inward) 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. In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 14 Complete the "Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Terminal Loopback" procedure.


Test and Clear the DS-3, DS3N-12, DS3i-N-12, or EC1 Port Terminal Loopback


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Double-click the electrical card in the destination node with the terminal loopback.

Step 4 Click the Maintenance > Loopback tab.

Step 5 Select None from the Loopback Type column for the port being tested.

Step 6 Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Clear the terminal loopback:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 10 Complete the "Test the Source Electrical Card" procedure.


Create the Terminal (Inward) Loopback on a Source DS3E or DS3XM Port


Step 1 Connect an electrical test set to the port you are testing:

a. If you just completed the "Perform an XC Loopback on a Source-Node OC-N STS (East to West) Carrying an Electrical Circuit" procedure, leave the electrical test set hooked up 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.

c. Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 2 In CTC node view, click the Circuits tab and click Create.

Step 3 In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

Step 4 Click Next.

Step 5 In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as DS1toDS5.

Step 6 Leave the Bidirectional check box checked.

Step 7 Click Next.

Step 8 In the Circuit Creation source dialog box, select the Node, card Slot, Port, and STS (or VT) where the test set is connected.

Step 9 Click Next.

Step 10 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. Click Next.

e. In the Circuit Creation circuit routing preferences dialog box, leave all defaults. Click Finish.

Step 11 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-172 to appear during a loopback setup. The condition clears when you remove the loopback.



Note DS-3 terminal loopbacks do not transmit a DS-3 AIS (see the "AIS" condition on page 2-30) in the direction away from the loopback. Instead of a DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.


Step 12 Create the terminal (inward) 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. In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.

c. Click the Maintenance > DS3 tabs.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 13 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 has been placed in service. The loopback/send code cannot be selected for a DS-1 if the derived state is OOS,DSBLD.

d. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 14 Complete the "Test and Clear the DS3E or DS3XM Port Terminal Loopback Circuit" procedure.


Test and Clear the DS3E or DS3XM Port Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Double-click the electrical card in the destination node with the terminal loopback.

Step 4 Depending upon the card type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


Step 5 Select None from the Loopback Type column for the port being tested.

Step 6 Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Clear the terminal loopback:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 10 Complete the "Test the Source Electrical Card" procedure.


Test the Source Electrical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective electrical card.

Step 5 Clear the terminal (inward) loopback state on the port:

a. Double-click the electrical card in the destination node with the terminal loopback.

b. Depending upon the card type, click the Maintenance > Loopback tab, Maintenance > DS1 tab, or Maintenance > DS3 tab.


Note The DS-3 Admin State is the basis of the DS-1 Derived State.


c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Delete the terminal (inward) loopback circuit:

a. Click the Circuits tab.

b. 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 tab 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.

Figure 1-19 Accessing FEAC Functions on the DS3XM-6 Card

The "far end" in FEAC refers to the equipment connected to the DS3XM card and not to the far end of a circuit. In Figure 1-20, 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 Diagram of FEAC Circuit

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 (line). 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.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 (inward) or facility (line) loopbacks.

1.3.4  FEAC Alarms

When an ONS 15454 port receives an activation code for a FEAC loopback, it raises the "LPBKDS1FEAC" condition on page 2-166 or the "LPBKDS3FEAC" condition on page 2-166. 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 "LPBKDS1FEAC-CMD" condition on page 2-166 or the "LPBKDS3FEAC-CMD" condition on page 2-167 for the near-end port.

1.4  Troubleshooting Optical Circuit Paths With Loopbacks

Facility (line) loopbacks, terminal (inward) 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, go to the "Troubleshooting Ethernet Circuit Paths With Loopbacks" section. For information about troubleshooting MXP and TXP cards, go to the "Troubleshooting MXP, TXP, or FC_MR-4 Circuit Paths With Loopbacks" section.) The example in this section tests an OC-N circuit on a three-node BLSR. Using a series of facility, cross-connect, and terminal (inward) 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.


1. A facility (line) loopback on the source-node OC-N port

2. A terminal (inward) loopback on the source-node OC-N port

3. A cross-connect loopback on the source OC-N port

4. A facility (line) loopback on the intermediate-node OC-N port

5. A terminal (inward) loopback on the intermediate-node OC-N port

6. A facility (line) loopback on the destination-node OC-N port

7. A terminal (inward) loopback on the destination-node OC-N port


Note Facility and terminal loopback tests require on-site personnel.


1.4.1  Perform a Facility (Line) Loopback on a Source-Node Optical Port

The facility (line) 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 (line) loopback on this port isolates the OC-N port as a possible failure point. Figure 1-21 shows an example of a facility loopback on a circuit source OC-N port.

Figure 1-21 Facility (Line) Loopback on a Circuit Source OC-N Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on the Source Optical Port" procedure.

Create the Facility (Line) Loopback on the Source Optical Port


Step 1 Connect an optical test set to the port you are testing.


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


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.)

Step 2 In CTC node view, double-click the card to display the card view.

Step 3 Click the Maintenance > Loopback > Port tab.

Step 4 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.

Step 5 Choose Facility (Line) from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.

Step 6 Click Apply.

Step 7 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (OCN)" condition on page 2-171 or the "LPBKFACILITY (G1000)" condition on page 2-169 to appear during loopback setup. The condition clears when you remove the loopback.


Step 8 Complete the "Test and Clear the Facility (Line) Loopback Circuit" procedure.


Test and Clear the Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the OC-N Card" procedure.


Test the OC-N Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Complete the "Perform a Terminal (Inward) Loopback on a Source-Node Optical Port" procedure.


1.4.2  Perform a Terminal (Inward) Loopback on a Source-Node Optical Port

The terminal (inward) 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. Figure 1-22 shows an example of a terminal loopback on a source OC-N port.

Figure 1-22 Terminal (Inward) Loopback on a Source-Node OC-N Port

OC-N cards placed in terminal loopback state display an icon in the CTC graphical user interface (GUI), shown in Figure 1-23.

Figure 1-23 Terminal Loopback Indicator


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal (Inward) Loopback on a Source-Node Optical Port" procedure.

Create the Terminal (Inward) Loopback on a Source-Node Optical Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Source-Node Optical Port" procedure, leave the optical test set hooked up to the OC-N port in the source node.

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.)

Step 2 Use CTC to set up the terminal (inward) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as OCN1toOCN2.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 3 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-175 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 4 Create the terminal (inward) 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. Click the Maintenance > Loopback > Port tab.

c. 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 (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 5 Complete the "Test and Clear the Terminal Loopback Circuit" procedure.


Test and Clear the Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback state on the port:

a. Double-click the card in the source node with the terminal loopback.

b. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Optical Card" procedure.


Test the Optical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 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. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit before testing the next segment of the network circuit path:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform an XC Loopback on the Source Optical Port" procedure.


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 XC10G 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.


The XC loopback test occurs on the XC10G 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 XC Loopback on a Source OC-N Port

Complete the "Create the XC Loopback on the Source-Node Optical Port" procedure.

Create the XC Loopback on the Source-Node Optical Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Terminal (Inward) Loopback on a Source-Node Optical Port" procedure, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to put the circuit being tested out of service:

a. In node view, click the Circuits tab.

b. Click the circuit and then click Edit.

c. In the Edit Circuit dialog box, click the State tab.

d. Choose OOS,MT from the Target Circuit Admin State drop-down list.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Use CTC to set up the XC loopback on the circuit being tested:

a. In node view, double-click the OC-N card to display the card view.

b. Click the Maintenance > Loopback > SONET STS tab.

c. Click the check box in the XC Loopback column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 5 Complete the "Test and Clear the XC Loopback Circuit" procedure.


Test and Clear the XC Loopback Circuit


Note This procedure is performed only on OC-N cards.



Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the cross-connect. Clear the XC loopback:

a. In card view, click the Maintenance > Loopback > SONET STS tab.

b. Uncheck the check box in the XC Loopback column for the circuit being tested.

c. Click Apply.

d. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the Standby XC10G Cross-Connect Card" procedure.


Test the Standby XC10G Cross-Connect Card


Note This procedure is performed only on cross-connect cards.



Step 1 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. Position the cursor over the standby cross-connect card.

c. Right-click and choose RESET CARD.

d. Click Yes in the confirmation dialog box.

Step 2 Initiate an external switching command (side switch) on the cross-connect cards before you retest the loopback circuit:


Caution Cross-connect side switches are service-affecting. Any live traffic on any card in the node endures a hit of up to 50 ms.

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. In the node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 3 Resend test traffic on the loopback circuit.

The test traffic now travels through the alternate cross-connect card.

Step 4 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. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

e. Confirm that the 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.

Step 5 To confirm a defective original cross-connect card, complete the "Retest the Original XC10G Cross-Connect Card" procedure.


Retest the Original XC10G Cross-Connect Card


Note This procedure is performed only on OC-N and XC10G 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. In node view, select the Maintenance > Cross-Connect > Cards tab.

c. In the Cross-Connect Cards area, click Switch.

d. Click Yes in the Confirm Switch dialog box.


Note After the active cross-connect goes into standby mode, the original standby card becomes active and its ACT/SBY LED turns green. The former active card becomes standby and its ACT/SBY LED turns amber.


Step 2 Resend test traffic on the loopback circuit.

Step 3 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 (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.

Step 4 Complete the "Physically Replace an In-Service Cross-Connect Card" procedure on page 2-271 for the defective card. Perform Step 5.

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. Click the Circuits tab.

b. Choose the XC loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 6 Complete the "Perform a Facility (Line) Loopback on an Intermediate-Node Optical Port" procedure.


1.4.4  Perform a Facility (Line) Loopback on an Intermediate-Node Optical Port

Performing the facility (line) 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 (Line) Loopback Path to an Intermediate-Node OC-N Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Facility (Line) Loopback on an Intermediate-Node Optical Port" procedure.

Create a Facility (Line) Loopback on an Intermediate-Node Optical Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform an XC Loopback on the Source Optical Port" procedure, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the facility (line) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as OCN1toOCN3.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-171 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the facility (line) 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.

Choose the node from the drop-down list in the Select Node dialog box and click OK.

b. In node view, double-click the intermediate-node card that requires the loopback.

c. Click the Maintenance > Loopback > Port tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Facility (Line) Loopback Circuit" procedure.


Test and Clear the Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility (line) loopback. Clear the facility loopback from the port:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Clear the facility (line) loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Optical Card" procedure.


Test the Optical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Clear the facility loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Terminal (Inward) Loopback on Intermediate-Node Optical Ports" procedure.


1.4.5  Perform a Terminal (Inward) 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 Figure 1-26, the terminal loopback is performed on an intermediate optical port in the circuit. You first create a 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.

Figure 1-26 Terminal Loopback Path to an Intermediate-Node OC-N Port

OC-N cards placed in facility loopback state display an icon, shown in Figure 1-27.

Figure 1-27 Facility Loopback Indicator


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Terminal Loopback on Intermediate-Node Optical Ports" procedure.

Create a Terminal Loopback on Intermediate-Node Optical Ports


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on an Intermediate-Node Optical Port" section, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the terminal (inward) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as OCN1toOCN4.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-175 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 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.

Choose the node from the drop-down list in the Select Node dialog box and click OK.

b. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback > Port tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Optical Terminal Loopback Circuit" procedure.


Test and Clear the Optical Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port:

a. Double-click the intermediate-node card with the terminal loopback to display the card view.

b. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Optical Card" procedure.


Test the Optical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Facility (Line) Loopback on a Destination-Node Optical Port" procedure.


1.4.6  Perform a Facility (Line) Loopback on a Destination-Node Optical Port

You perform a facility (line) loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in Figure 1-28 shows a facility loopback being performed on a destination-node OC-N port.

Figure 1-28 Facility (Line) Loopback Path to a Destination-Node OC-N Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on a Destination-Node Optical Port" procedure.

Create the Facility (Line) Loopback on a Destination-Node Optical Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Terminal (Inward) Loopback on Intermediate-Node Optical Ports" section, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the hairpin circuit on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as OCN1toOCN5.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-171 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the facility (line) 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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback > Port tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Optical Facility (Line) Loopback Circuit" procedure.


Test and Clear the Optical Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Clear the facility (line) loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Optical Card" procedure.


Test the Optical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback on the port:

a. Click the Maintenance > Loopback > Port tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Clear the facility loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Terminal Loopback on a Destination-Node Optical Port" procedure.


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.

Figure 1-29 Terminal Loopback Path to a Destination-Node OC-N Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal Loopback on a Destination-Node Optical Port" procedure.

Create the Terminal Loopback on a Destination-Node Optical Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Destination-Node Optical Port" procedure, leave the optical test set hooked up to the source port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the terminal loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as OCN1toOCN6.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-175 to appear during a loopback setup. The condition clears when you remove the loopback.


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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback > Port tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Optical Terminal Loopback Circuit" procedure.


Test and Clear the Optical Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port:

a. Double-click the intermediate-node card with the terminal loopback.

b. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. 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.

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty card.

Step 6 Complete the "Test the Optical Card" procedure.


Test the Optical Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good 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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback > Port tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. 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 (line) loopbacks, terminal (inward) 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.

You can use these procedures on G-Series Ethernet cards (G1000-2) and CE_100T-8 cards but not on E-Series or ML-Series Ethernet cards. The example in this section tests a G1000 circuit on a three-node BLSR. Using a series of facility (line) loopbacks and terminal (inward) 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.


1. A facility (line) loopback on the source-node Ethernet port

2. A terminal (inward) loopback on the source-node Ethernet port

3. A facility (line) loopback on the intermediate-node Ethernet port

4. A terminal (inward) loopback on the intermediate-node Ethernet port

5. A facility (line) loopback on the destination-node Ethernet port

6. A terminal (inward) loopback on the destination-node Ethernet port


Note Facility and terminal loopback tests require on-site personnel.


1.5.1  Perform a Facility (Line) Loopback on a Source-Node Ethernet Port

The facility (line) loopback test is performed on the node source port in the network circuit. In the testing situation used in this example, the source G1000 port in the source node. Completing a successful facility (line) loopback on this port isolates the G1000 port as a possible failure point. Figure 1-21 shows an example of a facility loopback on a circuit source Ethernet port.


Note Facility (line) loopbacks are not available for Release 4.1 or earlier G-Series cards.


Figure 1-30 Facility (Line) Loopback on a Circuit Source Ethernet Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on the Source-Node Ethernet Port" procedure.

Create the Facility (Line) Loopback on the Source-Node Ethernet Port


Step 1 Connect an optical test set to the port you are testing.


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In CTC node view, double-click the card to display the card view.

Step 4 Click the Maintenance > Loopback tab.

Step 5 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.

Step 6 Choose Facility (Line) from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (G1000)" condition on page 2-169 to appear during loopback setup. The condition clears when you remove the loopback.


Step 9 Complete the "Test and Clear the Facility (Line) Loopback Circuit" procedure.


Test and Clear the Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Complete the "Perform a Terminal (Inward) Loopback on a Source-Node Ethernet Port" procedure.


1.5.2  Perform a Terminal (Inward) Loopback on a Source-Node Ethernet Port

The terminal (inward) loopback test is performed on the node source Ethernet port. For the circuit in this example, it is the source G1000 port in the source node. You first create a bidirectional circuit that starts on the node destination G1000 port and loops back on the node source G1000 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. Figure 1-31 shows terminal loopback on a G-Series port.


Note Terminal (inward) loopbacks are not available for R4.0 and earlier G-Series cards.


Figure 1-31 Terminal (Inward) Loopback on a G-Series Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal (Inward) Loopback on a Source-Node Ethernet Port" procedure.

Create the Terminal (Inward) Loopback on a Source-Node Ethernet Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Source-Node Ethernet Port" procedure, leave the optical test set hooked up to the Ethernet port in the source node.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the terminal (inward) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as G1K1toG1K2.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-174 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the terminal (inward) loopback on the destination port being tested:

a. In node view, double-click the card that requires the loopback, such as the destination G1000 card in the source node.

b. Click the Maintenance > Loopback tab.

c. 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 (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Ethernet Terminal Loopback Circuit" procedure.


Test and Clear the Ethernet Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 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. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 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. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit before testing the next segment of the network circuit path:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port" procedure.


1.5.3  Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port

Performing the facility (line) loopback test on an intermediate port isolates whether this node is causing circuit failure. It is shown in Figure 1-32.

Figure 1-32 Facility (Line) Loopback on an Intermediate-Node Ethernet Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port" procedure.

Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Terminal (Inward) Loopback on a Source-Node Ethernet Port" procedure, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the facility (line) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as G1KtoG1K3.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note It is normal for the "LPBKFACILITY (G1000)" condition on page 2-169, or the "LPBKFACILITY (OCN)" condition on page 2-171 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the facility (line) 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.

Choose the node from the drop-down list in the Select Node dialog box and click OK.

b. In node view, double-click the intermediate-node card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Ethernet Facility (Line) Loopback Circuit" procedure.


Test and Clear the Ethernet Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility (line) loopback. Clear the facility loopback from the port:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Clear the facility (line) loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Clear the facility loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Create a Terminal (Inward) Loopback on Intermediate-Node Ethernet Ports" procedure.


1.5.4  Create a Terminal (Inward) 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 Figure 1-33, the 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.

Figure 1-33 Terminal Loopback on an Intermediate-Node Ethernet Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Terminal Loopback on Intermediate-Node Ethernet Ports" procedure.

Create a Terminal Loopback on Intermediate-Node Ethernet Ports


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Create a Facility (Line) Loopback on an Intermediate-Node Ethernet Port" procedure for the Ethernet circuit, leave the optical test set hooked up to the intermediate-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the terminal (inward) loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as G1K1toG1K4.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-174 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 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.

Choose the node from the drop-down list in the Select Node dialog box and click OK.

b. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Ethernet Terminal Loopback Circuit" procedure.


Test and Clear the Ethernet Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 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 display the card view.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Facility (Line) Loopback on a Destination-Node Ethernet Port" procedure.


1.5.5  Perform a Facility (Line) Loopback on a Destination-Node Ethernet Port

You perform a facility (line) loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in Figure 1-34 shows a facility loopback being performed on an Ethernet port.

Figure 1-34 Facility (Line) Loopback on a Destination-Node Ethernet Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on a Destination-Node Ethernet Port" procedure.

Create the Facility (Line) Loopback on a Destination-Node Ethernet Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Create a Terminal (Inward) Loopback on Intermediate-Node Ethernet Ports" section, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the hairpin circuit on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as G1K1toG1K5.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note It is normal for the "LPBKFACILITY (G1000)" condition on page 2-169 to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the facility (line) 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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Ethernet Facility (Line) Loopback Circuit" procedure.


Test and Clear the Ethernet Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Clear the facility (line) loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 5 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback on the port:

a. Click the Maintenance > Loopback tab.

b. 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.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Clear the facility loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. Do not check any check boxes.

Step 7 Complete the "Perform a Terminal Loopback on a Destination-Node Ethernet Port" procedure.


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.

Figure 1-35 Terminal Loopback on a Destination-Node Ethernet Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal Loopback on a Destination-Node Ethernet Port" procedure.

Create the Terminal Loopback on a Destination-Node Ethernet Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Destination-Node Ethernet Port" procedure, leave the optical test set hooked up to the source port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Use CTC to set up the terminal loopback on the test port:

a. In node view, click the Circuits tab and click Create.

b. In the Circuit Creation dialog box, choose the type, such as STS, and number, such as 1.

c. Click Next.

d. In the next Circuit Creation dialog box, give the circuit an easily identifiable name such as G1K1toG1K6.

e. Leave the Bidirectional check box checked.

f. Click Next.

g. In the Circuit Creation source dialog box, select the same Node, card Slot, Port, and STS (or VT) where the test set is connected.

h. Click Next.

i. 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.

Step 4 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-174 to appear during a loopback setup. The condition clears when you remove the loopback.


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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the Ethernet Terminal Loopback Circuit" procedure.


Test and Clear the Ethernet Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 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. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. 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.

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty card.

Step 6 Complete the "Test the Ethernet Card" procedure.


Test the Ethernet Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good 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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Clear the terminal loopback circuit:

a. Click the Circuits tab.

b. Choose the loopback circuit being tested.

c. Click Delete.

d. Click Yes in the Delete Circuits dialog box. 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 MXP, TXP, or FC_MR-4 Circuit Paths With Loopbacks

Facility (line) loopbacks, terminal (inward) 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. MXP/TXP/FC_MR-4 loopback tests differ from electrical, optical, and Ethernet testing in that loopback testing does not require circuit creation. MXP, TXP, and FC_MR-4 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 transponder cards (TXP, TXPP), muxponder cards (MXP, MXPP), and fibre channel data storage (FC_MR-4) cards. The example in this section tests an MXP/TXP/FC_MR-4 circuit on a three-node BLSR. Using a series of facility (line) loopbacks and terminal (inward) 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 MXP/TXP/FC_MR-4 card client ports do not appear in the Maintenance > Loopback tab unless they have been provisioned. Do this 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.


1. A facility (line) loopback on the source-node MXP/TXP/FC_MR-4 port

2. A terminal (inward) loopback on the source-node MXP/TXP/FC_MR-4 port

3. A facility (line) loopback on the intermediate-node MXP/TXP/FC_MR-4 port

4. A terminal (inward) loopback on the intermediate-node MXP/TXP/FC_MR-4 port

5. A facility (line) loopback on the destination-node MXP/TXP/FC_MR-4 port

6. A terminal (inward) loopback on the destination-node MXP/TXP/FC_MR-4 port


Note Facility, hairpin, and terminal loopback tests require on-site personnel.


1.6.1  Perform a Facility (Line) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port

The facility (line) 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 (line) loopback on this port isolates the MXP/TXP/FC_MR-4 port as a possible failure point. Figure 1-36 shows an example of a facility loopback on a circuit source MXP/TXP/FC_MR-4 port.

Figure 1-36 Facility (Line) Loopback on a Circuit Source MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on the Source-Node MXP/TXP/FC_MR-4 Port" procedure.

Create the Facility (Line) Loopback on the Source-Node MXP/TXP/FC_MR-4 Port


Step 1 Connect an optical test set to the port you are testing.


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In CTC node view, double-click the card to display the card view.

Step 4 Click the Maintenance > Loopback tab.

Step 5 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.

Step 6 Choose Facility (Line) from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.


Note It is normal for the "LPBKFACILITY (OCN)" condition on page 2-171 or the "LPBKFACILITY (G1000)" condition on page 2-169 to appear during loopback setup. The condition clears when you remove the loopback.


Step 9 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Complete the "Perform a Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port" procedure.


1.6.2  Perform a Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port

The terminal (inward) loopback test is performed on the node source MXP/TXP/FC_MR-4 muxponder or transponder port. For the circuit in this example, it is the source MXP 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-37 shows an example of a terminal loopback on a source MXP/TXP/FC_MR-4 port.

Figure 1-37 Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port" procedure.

Create the Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port" procedure, leave the optical test set hooked up to the MXP or TXP port in the source node.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In node view, double-click the card that requires the loopback, such as the destination OC-N card in the source node.

Step 4 Click the Maintenance > Loopback tab.

Step 5 Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

Step 6 Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Port Terminal Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Port Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback state on the port:

a. Double-click the card in the source node with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 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. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Complete the "Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port" procedure.


1.6.3  Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port

Performing the facility (line) loopback test on an intermediate port isolates whether this node is causing circuit failure. In the situation shown in Figure 1-38, the test is being performed on an intermediate MXP/TXP/FC_MR-4 port.

Figure 1-38 Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port" procedure.

Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Terminal (Inward) Loopback on a Source-Node MXP/TXP/FC_MR-4 Port" procedure, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 In node view, double-click the intermediate-node card that requires the loopback.

Step 4 Click the Maintenance > Loopback tab.

Step 5 Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

Step 6 Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

Step 7 Click Apply.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Port Facility (Line) Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Port Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility (line) loopback. Clear the facility loopback from the port:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Complete the "Create a Terminal (Inward) Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports" procedure.


1.6.4  Create a Terminal (Inward) Loopback on Intermediate-Node MXP/TXP/FC_MR-4 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 Figure 1-39, the terminal loopback is performed on an intermediate MXP/TXP/FC_MR-4 port in the circuit. If you successfully complete a terminal loopback on the node, this node is excluded from possible sources of circuit trouble.

Figure 1-39 Terminal Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create a Terminal Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports" procedure.

Create a Terminal Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Create a Facility (Line) Loopback on an Intermediate-Node MXP/TXP/FC_MR-4 Port" section, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 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.

Choose the node from the drop-down list in the Select Node dialog box and click OK.

b. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port:

a. Double-click the intermediate-node card with the terminal loopback to display the card view.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 6 Complete the "Perform a Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port" procedure.


1.6.5  Perform a Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port

You perform a facility (line) loopback test at the destination port to determine whether this local port is the source of circuit trouble. The example in Figure 1-40 shows a facility loopback being performed on an MXP/TXP/FC_MR-4 port.

Figure 1-40 Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port" procedure.

Create the Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Create a Terminal (Inward) Loopback on Intermediate-Node MXP/TXP/FC_MR-4 Ports" procedure, leave the optical test set hooked up to the source-node port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 Create the facility (line) 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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Facility (Line) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Facility (Line) Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary with the facility loopback. Clear the facility (line) loopback from the port:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good one.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card installed.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the faulty card.

Step 5 Clear the facility (line) loopback on the port:

a. Click the Maintenance > Loopback tab.

b. Choose None from the Loopback Type column for the port being tested.

c. Choose the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) from the Admin State column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 6 Complete the "Perform a Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port" procedure.


1.6.6  Perform a Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 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 MXP/TXP/FC_MR-4 port.

Figure 1-41 Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port


Caution Performing a loopback on an in-service circuit is service-affecting.

Complete the "Create the Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port" procedure.

Create the Terminal Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port


Step 1 Connect an optical test set to the port you are testing:


Note Refer to the manufacturer's instructions for detailed information about connection and setup of the optical test set.


a. If you just completed the "Perform a Facility (Line) Loopback on a Destination-Node MXP/TXP/FC_MR-4 Port" procedure, leave the optical test set hooked up to the source port.

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.

Step 2 Adjust the test set accordingly. (Refer to manufacturer instructions for test-set use.)

Step 3 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-175 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. 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. In node view, double-click the card that requires the loopback.

c. Click the Maintenance > Loopback tab.

d. Select OOS,MT from the Admin State column. If this is a multiport card, select the row appropriate for the desired port.

e. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 5 Complete the "Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit" procedure.


Test and Clear the MXP/TXP/FC_MR-4 Terminal Loopback Circuit


Step 1 If the test set is not already sending traffic, send test traffic on the loopback circuit.

Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the terminal loopback from the port:

a. Double-click the intermediate-node card with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card.

Step 5 Complete the "Test the MXP/TXP/FC_MR-4 Card" procedure.


Test the MXP/TXP/FC_MR-4 Card


Step 1 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the suspected bad card and replace it with a known-good 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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

Step 2 Resend test traffic on the loopback circuit with a known-good card.

Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the RMA process. Contact Cisco Technical Support (1 800 553-2447).

Step 4 Complete the "Physically Replace a Traffic Card" procedure on page 2-271 for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node card with the terminal loopback.

b. Click the Maintenance > Loopback tab.

c. Select None from the Loopback Type column for the port being tested.

d. Select the appropriate state (IS; OOS,DSBLD; OOS,MT; IS,AINS) in the Admin State column for the port being tested.

e. Click Apply.

f. 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  Troubleshooting DWDM Circuit Paths With ITU-T G.709 Monitoring

This section provides an overview of the optical transport network (OTN) specified in ITU-T G.709 Network Node Interface for the Optical Transport Network, and provides troubleshooting procedures for DWDM circuit paths in the ITU-T G.709 OTN using performance monitoring and threshold crossing alerts (TCAs).

1.7.1  G.709 Monitoring in Optical Transport Networks

Recommendation ITU-T G.709 is part of a suite of recommendations covering the full functionality of an OTN. ITU-T G.709 takes single-wavelength SONET technology a step further by enabling transparent optical wavelength-based networks. It adds extra overhead to existing SONET, Ethernet, or asynchronous transfer mode (ATM) bit streams for performance management and improvement.

ITU-T G.709 adds the operations, administration, maintenance and provisioning (OAM&P) functionality of SONET/SDH to DWDM optical networks.

Like traditional SONET networks, ITU-T G.709 optical networks have a layered design (Figure 1-42). This structure enables localized monitoring that helps you isolate and troubleshoot network problems.

Figure 1-42 Optical Transport Network Layers

1.7.2  Optical Channel Layer

The optical channel (OCh) layer is the outermost part of the OTN and spans from client to client. The optical channel is built as follows:

1. A client signal such as SONET, Gigabit Ethernet, IP, ATM, fiber channel, or enterprise system connection (ESCON) is mapped to a client payload area and combined with an overhead to create the optical channel payload unit (OPUk).

2. A second overhead is added to the OPUk unit to create the optical channel data unit (ODUk).

3. A third overhead including forward error correction (FEC) is added to the ODUk to create the optical channel transport unit (OTUk).

4. A fourth overhead is added to the OTUk to create the entire OCh layer

1.7.3  Optical Multiplex Section Layer

The optical multiplex section (OMS) of the OTN allows carriers to identify errors occurring within DWDM network sections. The OMS layer consists of a payload and an overhead (OMS-OH). It supports the ability to monitor multiplexed sections of the network, for example the span between an optical multiplexer such as the 3 2MUX-O and a demultiplexer such as the 32 DMX-O.

1.7.4  Optical Transmission Section Layer

The optical transmission section (OTS) layer supports monitoring partial spans of a network's multiplexed sections. This layer consists of a payload and an overhead (OTS-OH). It is a transmission span between two elements in an optical network, such as between:

A multiplexer such as the 32 MUX-O and an amplifier such as the OPT-PRE

An amplifier and another amplifier, such as the OPT-BST and the OPT-PRE

An amplifier such as the OPT-BST and a demultiplexer such as the 32-DMX

1.7.5  Performance Monitoring Counters and Threshold Crossing Alerts

Performance monitoring (PM) counters and TCAs can be used for identifying trouble and troubleshooting problems in ITU-T G.709 optical transport networks. ITU-T Recommendation M.2401 recommends that the following PM parameters be monitored at the ODUk Layer:

SES (severely errored seconds)—A one-second period which contains greater than or equal to 30% errored blocks or at least one defect. SES is a subset of the errored second (ES) parameter, which is a on- second period with one or more errored blocks or at least one defect.

BBE (background block error counter)—An errored block not occurring as part of an SES. BBE is a subset of the errored block (EB) parameter, which is a block in which one or more bits are in error.

Different performance monitoring count parameters are associated with different read points in a network. Figure 1-43 illustrates the performance monitoring read points that are useful in identifying DWDM circuit points of failure. Chapter 4, "Performance Monitoring," lists all PM parameters and provides block diagrams of signal entry points, exit points and interconnections between the individual circuit cards. Consult these specifications to determine which performance monitoring parameters are associated with the system points you want to monitor or provision with CTC or TL1. The monitoring points can vary according to your configuration.

Figure 1-43 Performance Monitoring Points on ONS DWDM

TCAs are used to monitor performance through the management interface by indicating whether preset thresholds have been crossed, or whether a transmission (such as a laser transmission) is degraded. TCAs are not associated with severity levels. They are usually associated with rate, counter, and percentage parameters that are available at transponder monitoring points. Chapter 4, "Performance Monitoring," contains more information about these alerts.

Select and complete the provisioning procedure below according to your network parameters.

Complete the following procedure to provision default node ODUk BBE and SES PM thresholds for TXP cards.

Set Node Default BBE or SES Card Thresholds


Step 1 In node view, click the Provisioning > Defaults tabs (Figure 1-44).

Figure 1-44 Set Default BBE/SES Card Thresholds

Step 2 In the Defaults Selector field, select Txp_mr_2_5g > otnthresholds > Trunk > pm > 15min.


Complete the following procedure to provision BBE or SES PM thresholds in CTC for an individual TXP card.

Provision Individual Card BBE or SES Thresholds in CTC


Step 1 In node view, double-click the TXP_MR_2.5G card.
(In this example, other transponder and muxponder cards are also applicable, such as TXP_MR_10G, TXPP_MR_2.5G, and MXP_2.5G_10G.)

Step 2 Click the Provisioning > OTN > G.709 Thresholds tabs (Figure 1-45).

Figure 1-45 Provision Card BBE/SES Thresholds

Step 3 In the Directions area, click Near End.

Step 4 In the Intervals area, click 15 Min.

Step 5 In the Types area, click PM (ODUk).

Step 6 In the SES and BBE fields, enter threshold numbers, for example 500 and 10000.


Complete the following procedure if you wish to provision PM thresholds in TL1 rather than in CTC.

Provision Card PM Thresholds Using TL1


Step 1 Open a TL1 command line.

Step 2 On the TL1 command line, use the following syntax:

set-th-{och,clnt}::aid:ctag::montype,thlev,,,[tmper];

Where:

The modifier is och, as applicable to the trunk port.

Montype can be:

BBE-PM

SES-PM

LBCL-MAX

The parameter thlev is optional and indicates a threshold count value (the number of errors which must be exceeded before the threshold is crossed).

The parameter tmper is optional and is an accumulation time period for performance counters, with possible values of 1-DAY, 1-HR, 1-MIN, 15-MIN, and RAW-DATA.


Note For a list of TL1 commands, refer to the Cisco ONS 15454 SONET and SDH TL1 Quick Reference Guide, Release 4.7.



Complete the following procedure to provision TCA thresholds in CTC.

Provision Optical TCA Thresholds


Step 1 In node view, click the Provisioning > Optics Thresholds tabs (Figure 1-46).

Figure 1-46 Provision Optical TCA Thresholds

Step 2 In the Types area, click TCA.

Step 3 In the Intervals area, click 15 Min.

Step 4 In the Laser Bias High (%) field, enter the threshold value, for example, 81.0 percent.


1.7.6  Forward Error Correction

In DWDM spans, FEC reduces the quantities of retiming, reshaping, and regenerating (3R regeneration) needed to maintain signal quality. The following two PM parameters are associated with FEC:

BIEC—Bit errors corrected (BIEC) indicates the number of bit errors corrected in the DWDM trunk line during the PM time interval.

UNC-WORDS—The number of uncorrectable words detected in the DWDM trunk line during the PM time interval.

Complete the following procedure to provision BIEC and UNC-WORDS PM parameters for FEC.

Provision Card FEC Thresholds


Step 1 In node view, double-click the TXP_MR_2.5G card to open the card view.
(In this example, other transponder and muxponder cards are also applicable, such as TXP_MR_10G, TXPP_MR_2.5G, and MXP_2.5G_10G.)

Step 2 Click the Provisioning > OTN > FEC Thresholds tabs (Figure 1-47).

Figure 1-47 Provision Card FEC Thresholds

Step 3 In the Bit Errors Corrected field, enter a threshold number, for example 225837.

Step 4 In the Intervals area, click 15 Min.


1.7.7  Sample Trouble Resolutions

Some sample trouble resolutions using performance monitoring and TCAs for isolating points of degrade are provided below.

Symptom    There is a BBE TCA on a single transponder pair.

Possible Cause    The transponder input power is out of range.

Recommended Action    Check the input power on the transponder. It should be within the specified/supported range.

Possible Cause    There are dirty trunk connectors on the transponder.

Recommended Action    Check the connector on the trunk port.

Possible Cause    There is a degraded trunk patch-cord between the transponder and the DWDM port.

Recommended Action    Check the patch-cord on the transponder DWDM port.

Possible Cause    There are dirty client connectors on the channel add-drop (ADxC) transmit port or the demultiplexer (DMX) has crossed the near-end TCA.

Recommended Action    Check the connector on the OCH port of the ADxC.

Possible Cause    There are dirty client connectors on the ADxC receive port or the multiplexer (MUX) has crossed the far-end TCA point.

Recommended Action    If an optical channel bypass exists along the line, check the connectors.

Symptom    There is a BBE TCA on all transponders connected to a band add-drop card (ADxB).

Possible Cause    The transponder input power is out of range.

Recommended Action    Check the input power on the transponder. It should be within the specified/supported range.

Possible Cause    There is a dirty connector on the 4MD port.

Recommended Action    Check the connector on the drop port of the ADxB.

Possible Cause    There is a dirty connector on the ADxB drop port, and it has crossed the near-end TCA point.

Recommended Action    Check the connector on the drop port of the 4MD.

Possible Cause    There is a dirty connector on the ADxB add port and it has crossed the far-end TCA.

Recommended Action    Check the patch-cord on the 4MD or AD1Bx.

Possible Cause    There is a degraded patch-cord between the ADxB and the 4MD.

Recommended Action    If an optical band bypass exists along the line, check the band connectors.

Symptom    There is a BBE TCA on all transponders which the OCH passes through a single OTS section.

Possible Cause    This is not a transponder or channel-related issue.

Recommended Action    The problem is in the intercabinet signal path preceding the transponder. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for more information about configurations and acceptance tests for this area

Symptom    You have an LBC TCA on a single transponder.

Possible Cause    The laser of the transponder is degrading.

Recommended Action    The problem is within the laser circuitry. Check the OPT-PRE or OPT-BST optical amplifier cards. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for more information about setting up these cards.

1.8  Using CTC Diagnostics

In Release 5.0, 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 tab. The user-operated diagnostic features are described in the following paragraphs.

1.8.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 tab (Figure 1-48).

Figure 1-48 CTC Node View Diagnostic Window

Step 2 Click Lamp Test.

Step 3 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

Step 4 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 Cisco Technical Support (1 800 553-2447).


Verify G-Series Ethernet or FC_MR-4 Card Port-Level LED Operation


Note G-Series and FC_MR-4 card-level LEDs illuminate during a lamp test, but the port-level LEDs do not.



Step 1 Complete the "Verify General Card LED Operation" procedure to verify that card-level LEDs are operational.

Step 2 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.

Step 3 If you are unable to determine the port state, contact Cisco Technical Support (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 Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide.



Step 1 Complete the "Verify General Card LED Operation" procedure to verify that card-level LEDs are operational.

Step 2 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.

Step 3 If you are unable to determine the port state, contact Cisco Technical Support (1 800 553-2447).


1.8.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 Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."


Off-Load the Diagnostics File


Step 1 In the node view, click the Maintenance > Diagnostic tab (Figure 1-48).

Step 2 Click Retrieve Tech Support Log.

Step 3 In the Saving Diagnostic File dialog box, navigate to the directory (local or network) where you want to save the file.

Step 4 Enter a name in the File Name field.

You do not have to give the archive file a particular extension. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.

Step 5 Click Save.

The Get Diagnostics status window shows a progress bar indicating the percentage of the file being saved, then shows "Get Diagnostics Complete."

Step 6 Click OK.


1.8.3  Bidirectional Diagnostic Circuit

In Release 5.0, 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. Once 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.

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-49.

Figure 1-49 CTC Node View Diagnostic Window

In Release 5.0, 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 Cisco ONS 15454 Procedure Guide Chapter 3, "Connect the PC and Log into the GUI.")

Step 2 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 Cisco ONS 15454 Procedure Guide Chapter 6, "Create Circuits and VT Tunnels." If not, continue with Step 3.

Step 3 From the View menu, choose Go to Network View.

Step 4 Click the Circuits tab, then click Create.

Step 5 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.)

Step 6 Click Next.

Step 7 Define the circuit attributes in the Circuit Creation Dialog Box (Figure 1-50) using the following parameters:

Figure 1-50 Network View Circuit Creation Dialog Box

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.

Step 8 Click Next.

Step 9 In the Source area of the Circuit Creation pane, complete the following:

a. From the Node drop-down list, choose the node.

b. From the Slot drop-down list, choose PRBS Generator.

c. Click Next.

Step 10 In the Destination area of the Circuit Creation pane, complete the following:

a. From the Node drop-down list, choose the node. The only selectable item in the list is the node chosen as the source node.

b. From the Slot drop-down list, choose the slot where the span originates.

c. From the STS drop-down list, choose the STS.

d. From the VT drop-down list, choose the VT.

e. Click Next.

Step 11 Click Finish.

Step 12 In the Circuits window, verify that the new circuit(s) appear in the circuits list.

Stop. You have completed this procedure.


1.9  Restoring the Database and Default Settings

This section contains troubleshooting for node operation errors that require restoration of software data or the default node setup.

1.9.1  Restore the Node Database

Symptom    One or more nodes are not functioning properly or have incorrect data.

Possible Cause    There is an incorrect or corrupted node database.

Recommended Action    Perform a Restore the Database procedure. Refer to the "Restore the Database" procedure.

Restore the Database


Caution E1000-2 cards lose traffic for approximately 90 seconds when an ONS 15454 database is restored. Traffic is lost during the period of spanning tree reconvergence. The "CARLOSS (E100T, E1000F)" alarm on page 2-54 appears and clears during this period.


Caution If you are restoring the database on multiple nodes, wait approximately one minute after the TCC2/TCC2P reboot has completed on each node before proceeding to the next node.


Caution TCC2P cards (but not TCC2 cards) can be used in single IP address (repeater) and dual IP address (secured) mode. The secured mode has advanced features that affect database restore: A database from a secured node cannot be loaded on an unsecured repeater node. An unsecured database can be loaded onto a secured node but the database will follow the node characteristics (that is, become secured). A secured database cannot be loaded onto a TCC2P. For more information about the dual IP secured mode, refer to the Cisco ONS 15454 Reference Manual Chapter 12, "CTC Connectivity."


Note The following parameters are not backed up and restored: node name, IP address, subnet mask and gateway, and Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up database with a different node name, the circuits map to the new renamed node. Cisco recommends keeping a record of the old and new node names.



Note To avoid a node IP and secure IP ending up in the same domain after restoring a database, ensure that the node IP stored in the database differs in domain from that of the node in repeater mode. Also, after restoring a database, ensure that the node IP and secure IP differ in domain.



Step 1 In CTC, log into the node where you will restore the database:

a. On the PC connected to the ONS 15454, start Netscape or Internet Explorer.

b. In the Netscape or Internet Explorer Web address (URL) field, enter the ONS 15454 IP address.

A Java Console window displays the CTC file download status. The web browser displays information about your Java and system environments. If this is the first login from this computer, CTC caching messages appear while CTC files are downloaded to your computer. The first time you connect to an ONS 15454, this process can take several minutes. After the download, the CTC Login dialog box appears.

c. In the Login dialog box, type a user name and password (both are case sensitive) and click Login. The CTC node view window appears.

Step 2 Ensure that no ring or span (four-fiber only) switch events are present; for example, ring-switch east or west and span-switch east or west. In network view, click the Conditions tab and click Retrieve to view a list of conditions.

Step 3 If switch events need to be cleared, in node view click the Maintenance > BLSR tab and view the West Switch and East Switch columns.

a. If a switch event (not caused by a line failure) is present, choose CLEAR from the drop-down list and click Apply.

b. If a switch event caused by the Wait to Restore (WTR) condition is present, choose LOCKOUT SPAN from the drop-down list and click Apply. When the LOCKOUT SPAN is applied, choose CLEAR from the drop-down list and click Apply.

Step 4 In node view, click the Maintenance > Database tab.

Step 5 Click Restore.

Step 6 Locate the database file stored on the workstation hard drive or on network storage.


Note To clear all existing provisioning, locate and upload the database found on the latest ONS 15454 software CD.


Step 7 Click the database file to highlight it.

Step 8 Click Open. The DB Restore dialog box appears. Opening a restore file from another node or from an earlier backup might affect traffic on the login node.

Step 9 Click Yes.

The Restore Database dialog box monitors the file transfer.

Step 10 Wait for the file to complete the transfer to the TCC2/TCC2P.

Step 11 Click OK when the "Lost connection to node, changing to Network View" dialog box appears. Wait for the node to reconnect.

Step 12 If you cleared a switch in Step 3, reapply the switch as needed.


1.9.2  Restore the Node to Factory Configuration

Symptom    A node has both TCC2/TCC2P cards in standby state, and you are unable reset the TCC2/TCC2P cards to make the node functional.

Possible Cause    Both TCC2/TCC2P cards are failing in the node.

Possible Cause    You are replacing both TCC2/TCC2P cards at the same time.

Recommended Action    Restore the node to factory configuration. Refer to the "Use the Reinitialization Tool to Clear the Database and Upload Software (Windows)" procedure or the "Use the Reinitialization Tool to Clear the Database and Upload Software (UNIX)" procedure as required.


Caution Cisco strongly recommends that you keep different node databases in separate folders. This is because the reinitialization tool chooses the first product-specific software package in the specified directory if you use the Search Path field instead of the Package and Database fields. You might accidentally copy an incorrect database if multiple databases are kept in the specified directory.


Caution Restoring a node to the factory configuration deletes all cross-connects on the node.


Caution If you are restoring the database on multiple nodes, wait until the TCC2/TCC2P cards have rebooted on each node before proceeding to the next node.


Caution Restoring a node to factory configuration on a Windows or UNIX workstation should only be carried out on a standby TCC2/TCC2P card.


Caution Cisco recommends that you take care to save the node database to a safe location if you will not be restoring the node using the database provided on the software CD.


Note The following parameters are not backed up and restored when you delete the database and restore the factory settings: node name, IP address, subnet mask and gateway, and IIOP port. If you change the node name and then restore a backed up database with a different node name, the circuits map to the new renamed node. Cisco recommends keeping a record of the old and new node names.



Note If the software package files and database backup files are located in different directories, complete the Package and Database fields (Figure 1-51).



Note If you need to install or replace one or more TCC2/TCC2P cards, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," for installation instructions.


Use the Reinitialization Tool to Clear the Database and Upload Software (Windows)


Caution Restoring a node to the factory configuration deletes all cross-connects on the node.


Caution Restoring a node to factory configuration on a Windows workstation should only be carried out on a standby TCC2/TCC2P card.


Note The TCC2/TCC2P cards reboot several times during this procedure. Wait until they are completely rebooted before continuing.



Step 1 Insert the system software CD containing the reinitialization tool, software, and defaults database into the computer CD-ROM drive. If the CTC Installation Wizard appears, click Cancel.

Step 2 To find the recovery tool file, go to Start > Run > Browse and select the CD drive.

Step 3 On the CD drive, go to the CISCO15454 folder and choose All Files from the Files of Type drop-down list.

Step 4 Select the RE-INIT.jar file and click Open to open the reinitialization tool (Figure 1-51).

Figure 1-51 Reinitialization Tool in Windows

Step 5 If the node you are reinitializing is an end network element (ENE) in a proxy server network, enter the IP address of the gateway network element (GNE) in the GNE IP field. If not, leave it blank.

Step 6 Enter the node name or IP address of the node you are reinitializing in the Node IP field (Figure 1-51).

Step 7 If the User ID field does not contain your user ID, enter the ID. Enter your password in the Password field.

Step 8 Verify that the Re-Init Database, Upload Package, and Confirm check boxes are checked. If one is not checked, check the check box.

Step 9 If you are uploading the same version of software that is already active (for example, you are trying to upload version 5.0 when version 5.0 is already active), check the Force Upload check box. This option forces the NE to have the same software version on the working and protect flash memory.


Note The Force Upload box is only applicable when the Upload Package check box is checked.


Step 10 In the Search Path field, verify that the path to the CISCO15454 folder on the CD drive is listed.


Caution Before you perform the next step, be sure you are uploading the correct database. You cannot reverse the upload process after you click Yes.

Step 11 Click Go. A confirmation dialog box appears.

Step 12 Click Yes.

Step 13 The status bar at the bottom of the screen displays Complete when the node has activated the software and uploaded the database.


Note The Complete message only indicates that the TCC2/TCC2P successfully uploaded the database, not that the database restore was successful. The TCC2/TCC2P then tries to restore the database after it reboots.


Step 14 If you are logged into CTC, close the browser window and disconnect the straight-through LAN cable from the RJ-45 (LAN) port on the TCC2/TCC2P card or on the hub or switch to which the ONS 15454 is physically connected. Reconnect your straight-through LAN cable to the LAN port and log back into CTC.

Step 15 Manually set the node name and network configuration to site-specific values. See the Cisco ONS 15454 Procedure Guide Chapter 10, "Change Node Settings," for information about setting the node name, IP address, mask and gateway, and IIOP port.


Use the Reinitialization Tool to Clear the Database and Upload Software (UNIX)


Caution Restoring a node to the factory configuration deletes all cross-connects on the node.


Caution Restoring a node to factory configuration on a UNIX workstation should only be carried out on a standby TCC2/TCC2P card.


Note The TCC2/TCC2P cards reboot several times during this procedure. Wait until they are completely rebooted before continuing.



Note Java Runtime Environment (JRE) 1.4.2 must also be installed on the computer you use to perform this procedure.



Step 1 Insert the system software CD containing the reinitialization tool, software, and defaults database into the computer CD-ROM drive. If the CTC Installation Wizard appears, click Cancel.

Step 2 To find the recovery tool file, go to the CISCO15454 directory on the CD (usually /cdrom/cdrom0/CISCO15454).

Step 3 If you are using a file explorer, double-click the RE-INIT.jar file to open the reinitialization tool (Figure 1-52). If you are working with a command line interface, run java -jar RE-INIT.jar.

Figure 1-52 Reinitialization Tool in UNIX

Step 4 If the node you are reinitializing is an ENE in a proxy server network, enter the IP address of the GNE in the GNE IP field. If not, leave it blank.

Step 5 Enter the node name or IP address of the node you are reinitializing in the Node IP field (Figure 1-52).

Step 6 If the User ID field does not contain your user ID, enter the ID. Enter your password in the Password field.

Step 7 Verify that the Re-Init Database, Upload Package, and Confirm check boxes are checked. If one is not checked, check the check box.

Step 8 If you are uploading the same version of software that is already active (for example, you are trying to upload version 5.0 when version 5.0 is already active), check the Force Upload check box. This option forces the NE to have the same software version on the working and protect flash memory.

Step 9 In the Search Path field, verify that the path to the CISCO15454 folder on the CD-ROM drive is listed.


Caution Before you perform the next step, be sure you are uploading the correct database. You cannot reverse the upload process after you click Yes.

Step 10 Click Go. A confirmation dialog box appears.

Step 11 Click Yes.

Step 12 The status bar at the bottom of the screen displays Complete when the node has activated the software and uploaded the database.


Note The Complete message only indicates that the TCC2/TCC2P successfully uploaded the database; not that the database restore was successful. The TCC2/TCC2P then tries to restore the database after it reboots.


Step 13 If you are logged into CTC, close the browser window and disconnect the straight-through LAN cable from the RJ-45 (LAN) port on the TCC2/TCC2P card or on the hub or switch where the ONS 15454 is physically connected. Reconnect your straight-through LAN cable to the LAN port and log back into CTC.

Step 14 Set the node name and network configuration to site-specific values. Refer to the Cisco ONS 15454 Procedure Guide Chapter 10, "Change Node Settings" for information about provisioning the node name, IP address, subnet mask and gateway, and IIOP port.


1.10  PC Connectivity Troubleshooting

This section contains information about system minimum requirements, supported platforms, browsers, and JREs for R5.0, and troubleshooting procedures for PC and network connectivity to the ONS 15454.

1.10.1  PC System Minimum Requirements

Workstations running CTC R5.0 for the ONS products on Windows platforms need to have the following minimum requirements:

Pentium III or higher processor

Processor speed of at least 700 MHz

256 Mb or more of RAM

50 Mb or more of available hard disk space

20 GB or larger hard drive

1.10.2  Sun System Minimum Requirements

Workstations running CTC R5.0 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.10.3  Supported Platforms, Browsers, and JREs

Software R5.0 CTC supports the following platforms:

Windows NT

Windows 98

Windows XP

Windows 2000

Solaris 8

Solaris 9

Software R5.0 CTC supports the following browsers and JREs:

Netscape 7 (on Solaris 8 or 9 with Java plug-in 1.4.2)

PC platforms with Java plug-in 1.4.2

Internet Explorer 6.0 (on PC platforms with Java plug-in 1.4.2)


Note You can obtain browsers at the following URLs:
Netscape:
http://channels.netscape.com/ns/browsers/default.jsp
Internet Explorer: http://www.microsoft.com



Note The required JRE version is JRE 1.4.2.



Note JRE 1.4.2 for Windows and Solaris is available on R5.0 product CDs.


1.10.4  Unsupported Platforms and Browsers

Software R5.0 does not support the following platforms:

Windows 95

Solaris 2.5

Solaris 2.6

Software R5.0 does not support the following browsers and JREs:

Netscape 4.73 for Windows.

Netscape 4.76 on Solaris is not supported.

JRE 1.4.2 is not supported except with Netscape 7 on Solaris 8 or 9.

1.10.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 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 "Verify the IP Configuration of Your PC" procedure.

Possible Cause    The IP configuration of your PC is not properly set.

Recommended Action    Verify the IP configuration of your PC. Complete the "Verify the IP Configuration of Your PC" procedure. 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 Open a DOS command window by selecting Start > Run from the Start menu.

Step 2 In the Open field, type command and then click OK. The DOS command window appears.

Step 3 At the prompt in the DOS window, type one of the following commands:

For Windows 98, NT, and 2000, type ipconfig and press the Enter key.

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 At the prompt in the DOS window, type ping followed by the IP address shown in the Windows IP configuration information previously displayed.

Step 5 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.10.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 and the "Reconfigure the Browser" procedure.

Reconfigure the PC Operating System Java Plug-in Control Panel


Step 1 From the Windows start menu, click Settings > Control Panel.

Step 2 If Java Plug-in does not appear, the JRE might not be installed on your PC:

a. Run the Cisco ONS 15454 software CD.

b. Open the CD-drive:\Windows\JRE folder.

c. Double-click the j2re-1_4_2-win icon to run the JRE installation wizard.

d. Follow the JRE installation wizard steps.

Step 3 From the Windows start menu, click Settings > Control Panel.

Step 4 In the Java Plug-in Control Panel window, double-click the Java Plug-in 1.4.2 icon.

Step 5 Click the Advanced tab on the Java Plug-in Control Panel.

Step 6 Navigate to C:\ProgramFiles\JavaSoft\JRE\1.4.2.

Step 7 Select JRE 1.4.

Step 8 Click Apply.

Step 9 Close the Java Plug-in Control Panel window.


Reconfigure the Browser


Step 1 From the Start Menu, launch your browser application.

Step 2 If you are using Netscape Navigator:

a. On the Netscape Navigator menu bar, click the Edit > Preferences menus.

b. In the Preferences window, click the Advanced > Proxies categories.

c. In the Proxies window, click the Direct connection to the Internet check box and click OK.

d. On the Netscape Navigator menu bar, click the Edit > Preferences menus.

e. 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, C:\ProgramFiles\Netscape\username\Communicator\cache.

g. If the Disk Cache Folder field is not correct, click Choose Folder.

h. Navigate to the file listed in Step f, and click OK.

i. Click OK on the Preferences window and exit the browser.

Step 3 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.

c. 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.

Step 4 Temporarily disable any virus-scanning software on the computer. See the "Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P" section.

Step 5 Verify that the computer does not have two network interface cards (NICs) installed. If the computer does have two NICs, remove one.

Step 6 Restart the browser and log on to the ONS 15454.


1.10.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.

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 Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable.")

Possible Cause    Incorrect type of Category-5 cable is being used.

Recommended Action    If 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 "Crimp Replacement LAN Cables" section.

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.10.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.

Ping the ONS 15454


Step 1 Display the command prompt:

a. 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.

b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.

Step 2 For both the Sun and Microsoft operating systems, at the prompt enter:

ping ONS-15454-IP-address

For example:

ping 198.168.10.10

Step 3 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.

Step 4 If the ping is successful, an active TCP/IP connection exists. Restart CTC.

Step 5 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.

Step 6 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.10.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.

Retrieve Unknown Node IP Address


Step 1 Connect your PC directly to the active TCC2/TCC2P card Ethernet port on the faceplate.

Step 2 Start the Sniffer application on your PC.

Step 3 Perform a hardware reset by pulling and reseating the active TCC2/TCC2P card.

Step 4 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.11  CTC Operation Troubleshooting

This section contains troubleshooting procedures for CTC login or operation problems.

1.11.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. If the problem persists after limiting Netscape colors, exit any other color-intensive applications in use.

Limit Netscape Colors


Step 1 Close the current session of Netscape.

Step 2 Launch Netscape from the command line by typing:

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.11.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 "Reset Internet Explorer as the Default Browser for CTC" procedure to associate the CTC Help files to the correct browser.

Reset Internet Explorer as the Default Browser for CTC


Step 1 Open the Internet Explorer browser.

Step 2 From the menu bar, click Tools > Internet Options. The Internet Options window appears.

Step 3 In the Internet Options window, click the Programs tab.

Step 4 Click the Internet Explorer should check to see whether it is the default browser check box.

Step 5 Click OK.

Step 6 Exit any and all open and running CTC and Internet Explorer applications.

Step 7 Launch Internet Explorer and open a new CTC session. You should now be able to access the CTC Help.


1.11.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 "Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Windows" procedure or the "Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Solaris" procedure 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.


Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Windows


Note Before proceeding with the following steps, ensure that your system has a minimum of 1 GB of RAM. If your system does not have a minimum of 1 GB of RAM, contact the Cisco Technical Assistance Center (TAC).



Step 1 Close all open CTC sessions and browser windows.

Step 2 From the Windows Start menu, choose Control Panel > System.

Step 3 In the System Properties window, click the Advanced tab.

Step 4 Click the Environment Variables button to open the Environment Variables window.

Step 5 Click the New button under the System variables field.

Step 6 Type CTC_HEAP in the Variable Name field.

Step 7 Type 512 in the Variable Value field, and then click the OK button to create the variable.

Step 8 Again, click the New button under the System variables field.

Step 9 Type CTC_MAX_PERM_SIZE_HEAP in the Variable Name field.

Step 10 Type 128 in the Variable Value field, and then click the OK button to create the variable.

Step 11 Click the OK button in the Environment Variables window to accept the changes.

Step 12 Click the OK button in the System Properties window to accept the changes.


Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Solaris


Step 1 From the user shell window, kill any CTC sessions and broswer applications.

Step 2 In the user shell window, set the environment variables to increase the heap size.

Example

The following example shows how to set the environment variables in the C shell:

% setenv CTC_HEAP 512
% setenv CTC_MAX_PERM_SIZE_HEAP 128


1.11.4  Browser Stalls When Downloading CTC JAR Files From TCC2/TCC2P

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.

Disable the VirusScan Download Scan


Step 1 From the Windows Start menu, choose Programs > Network Associates > VirusScan Console.

Step 2 Double-click the VShield icon listed in the VirusScan Console dialog box.

Step 3 Click Configure on the lower part of the Task Properties window.

Step 4 Click the Download Scan icon on the left of the System Scan Properties dialog box.

Step 5 Uncheck the Enable Internet download scanning check box.

Step 6 Click Yes when the warning message appears.

Step 7 Click OK in the System Scan Properties dialog box.

Step 8 Click OK in the Task Properties window.

Step 9 Close the McAfee VirusScan window.


1.11.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 "Redirect the Netscape Cache to a Valid Directory" procedure.

Redirect the Netscape Cache to a Valid Directory


Step 1 Launch Netscape.

Step 2 open the Edit menu.

Step 3 Choose Preferences.

Step 4 Under the Category column on the left side, expand the Advanced category and choose the Cache tab.

Step 5 Change your disk cache folder to point to the cache file location.

The cache file location is usually C:\ProgramFiles\Netscape\Users\yourname\cache. The yourname segment of the file location is often the same as the user name.


1.11.6  Slow CTC Operation or Login Problems

Symptom    You experience slow CTC operation or have problems logging into CTC.

Table 1-3 describes the potential cause of the symptom and the solution.

Table 1-3 Slow CTC Operation or Login Problems 

Possible Problem
Solution

The CTC cache file might be corrupted or might need to be replaced.

Search for and delete cache files. This operation forces the Cisco 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 or the "Delete the CTC Cache File Manually" procedure.

Insufficient heap memory allocation.

Increase the heap size if you are using CTC to manage more than 50 nodes concurrently. See the "Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Windows" procedure or the "Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Solaris" procedure.

Note To avoid network performance issues, Cisco recommends managing a maximum of 50 nodes concurrently with CTC. To manage more than 50 nodes, Cisco recommends using Cisco Transport Manager (CTM). Cisco does not recommend running multiple CTC sessions when managing two or more large networks.


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 Enter an ONS 15454 IP address into the browser URL field. The initial browser window shows a Delete CTC Cache button.

Step 2 Close all open CTC sessions and browser windows. The PC operating system does not allow you to delete files that are in use.

Step 3 Click Delete CTC Cache on the initial browser window to clear the CTC cache. Figure 1-53 shows the Delete CTC Cache window.

Figure 1-53 Deleting the CTC Cache


Delete the CTC Cache File Manually


Caution All running sessions of CTC must be halted before deleting the CTC cache. Deleting the CTC cache might cause any CTC running on this system to behave in an unexpected manner.


Step 1 To delete the JAR files manually, from the Windows Start menu choose Search > For Files or Folders.

Step 2 Enter ctc*.jar or cms*.jar in the Search for files or folders named field in the Search Results dialog box and click Search Now.

Step 3 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.

Step 4 Highlight the files and press the keyboard Delete key.

Step 5 Click Yes in the Confirm dialog box.


1.11.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 "Different CTC Releases Do Not Recognize Each Other" section.

Possible Cause    Username and password do not match.

Recommended Action    Correct the username and password as described in the "Username or Password Do Not Match" section.

Possible Cause    No IP connectivity between nodes.

Recommended Action    Usually accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in the "Ethernet Connections" section.

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 "EOC" alarm.

1.11.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 Cisco ONS 15454 Procedure Guide Chapter 3, "Connect the PC and Log into the GUI." 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.

Manually Edit the java.policy File


Step 1 Search your computer for java.policy file and open it with a text editor (Notepad or Wordpad).

Step 2 Verify that the end of this file has the following lines:

		// Insert this into the system-wide or a per-user java.policy file.
	// DO NOT OVERWRITE THE SYSTEM-WIDE POLICY FILE--ADD THESE LINES!

	grant codeBase "http://*/fs/LAUNCHER.jar {
permission java.security.AllPermission;
	};

Step 3 If these five lines are not in the file, enter them manually.

Step 4 Save the file and restart Netscape.

CTC should now start correctly.

Step 5 If the error message is still reported, save the java.policy file as .java.policy. On Win98/2000 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.11.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 and on the Cisco ONS 15454 documentation CD. Complete the "Launch CTC to Correct the Core Version Build" procedure. 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-4 shows JRE compatibility with ONS 15454 software releases.

Table 1-4 JRE Compatibility 

Software Release
JRE 1.2.2 Compatible
JRE 1.3 Compatible
JRE 1.4 Compatible

ONS 15454 R2.2.1 and earlier

Yes

No

No

ONS 15454 R2.2.2

Yes

Yes

No

ONS 15454 R3.0

Yes

Yes

No

ONS 15454 R3.1

Yes

Yes

No

ONS 15454 R3.2

Yes

Yes

No

ONS 15454 R3.3

Yes

Yes

No

ONS 15454 R3.4

No

Yes

No

ONS 15454

Note R4.0 Software R4.0 notifies you if an earlier JRE version is running on your PC or UNIX workstation.

No

Yes

No

ONS 15454 R4.1

No

Yes

No

ONS 15454 R4.5

No

Yes

No

ONS 15454 R4.6

No

Yes

Yes

ONS 15454 R4.7

No

No

Yes

ONS 15454 R5.0

No

No

Yes


Launch CTC to Correct the Core Version Build


Step 1 Exit the current CTC session and completely close the browser.

Step 2 Start the browser.

Step 3 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.

Step 4 Log into CTC. The browser downloads the JAR file from CTC.


Note After R2.2.2, the single CMS.jar file evolved into core and element files. Core files are common to the ONS 15454, ONS 15454 SDH, and ONS 15327, while the element files are unique to the particular product. For example, the ONS 15327 R1.0 uses a 2.3 core build and a 1.0 element build. To display the CTC Core Version number, from the CTC menu bar click Help > About CTC. This lists the core and element builds discovered on the network.



1.11.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.


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 Exit the current CTC session and completely close the browser.

Step 2 Start the browser.

Step 3 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.

Step 4 Log into CTC. The browser downloads the JAR file from CTC.


Note After R2.2.2, the single CMS.jar file evolved into core and element files. Core files are common to the ONS 15454, ONS 15454 SDH, and ONS 15327, while the element files are unique to the particular product. For example, the ONS 15327 R1.0 uses a 2.3 core build and a 1.0 element build. To display the CTC Core Version number, from the CTC menu bar click Help > About CTC. This lists the core and element builds discovered on the network.



1.11.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 username in capital letters and type otbu+1 in lower-case letters. Click Login. (In Release 5.0, a password is required.) If you are using a CTC Software R2.2.2 or earlier and CISCO15 does not work, enter cerent454 for the user name. Complete the "Verify Correct Username and Password" procedure.

Verify Correct Username and Password


Step 1 Ensure that your keyboard Caps Lock key is not turned on and affecting the case-sensitive entry of the username and password.

Step 2 Contact your system administrator to verify the username and password.

Step 3 Call Cisco Technical Support (1 800 553-2447) to have them enter your system and create a new user name and password.


1.11.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 "Ethernet Connections" section.

1.11.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 "EOC" alarm.

1.11.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.11.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/techtools/ip_addr.html. For information about ONS 15454 IP capability, refer to the Cisco ONS 15454 Reference Manual Chapter 12, "IP Networking."

1.11.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 Figure 1-54 when using the steps in the "Verify Ethernet Connections" procedure.

Figure 1-54 Ethernet Connectivity Reference

Verify Ethernet Connections


Step 1 Verify that the alarm filter is turned OFF.

Step 2 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."

Step 3 Check for Ethernet-specific alarms. Clear any raised alarms by looking up that alarm in Chapter 2, "Alarm Troubleshooting."

Step 4 Verify that the ACT LED on the Ethernet card is green.

Step 5 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.

Step 6 If no green link-integrity LED is illuminated for any of these ports:

a. Verify physical connectivity between the ONS 15454s and the attached device.

b. Verify that the ports are enabled on the Ethernet cards.

c. 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.

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.

Step 7 Verify connectivity between device A and device C by pinging between these locally attached devices. Complete the "Verify PC Connection to the ONS 15454 (ping)" procedure. If the ping is unsuccessful:

a. Verify that device A and device C are on the same IP subnet.

b. Open the Ethernet card in CTC card view and click the Provisioning > VLAN tab 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.

Step 8 Repeat Step 7 for devices B and D.

Step 9 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.11.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-55). 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.

Figure 1-55 VLAN with Ethernet Ports at Tagged and Untag

Change VLAN Port Tag and Untagged Settings


Step 1 Display the CTC card view for the Ethernet card involved in the problem VLAN.

Step 2 Click the Provisioning > Ether VLAN tab (Figure 1-56).

Figure 1-56 Configuring VLAN Membership for Individual Ethernet Ports

Step 3 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.

Step 4 At the VLAN port set to Untag, click the port and choose Tagged.


Note The attached external devices must recognize IEEE 802.1Q VLANs.


Step 5 After each port is in the appropriate VLAN, click Apply.


1.12  Circuits and Timing

This section provides solutions to circuit creation and reporting errors, as well as common timing reference errors and alarms.

1.12.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 "View the State of OC-N Circuit Nodes" procedure. 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 Cisco ONS 15454 Software Upgrade Guide for software upgrade 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. 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. Refer to Chapter 2, "Alarm Troubleshooting," for procedures to clear alarms. Refer to the Cisco ONS 15454 Procedure Guide Chapter 9, "Manage Circuits," 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.

Step 2 From the Circuits tab list, select the circuit with the *_PARTIAL status condition.

Step 3 Click Edit. The Edit Circuit window appears.

Step 4 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.12.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 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.

Clear AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits


Step 1 Determine the affected port.

Step 2 Record the node ID, slot number, port number, or VT number.

Step 3 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.

Step 4 Uncheck the Bidirectional check box in the circuit creation window.

Step 5 Give the unidirectional VT circuit an easily recognizable name, such as delete me.

Step 6 Display the DS3XM-6 card in CTC card view. Click the Maintenance > DS1 tab.

Step 7 Locate the VT that is reporting the alarm (for example, DS3 #2, DS1 #13).

Step 8 From the Loopback Type list, choose Facility (Line) and click Apply.

Step 9 Click Circuits.

Step 10 Find the one-way circuit you created in Step 3. Select the circuit and click Delete. Do not check any check boxes.

Step 11 Click Yes in the Delete Confirmation dialog box.

Step 12 Display the DS3XM-6 or DS3XM-12 card in CTC card view. Click Maintenance > DS1.

Step 13 Locate the VT in Facility (line) Loopback.

Step 14 From the Loopback Type list, choose None and then click Apply.

Step 15 Click the Alarms tab and verify that the AIS-V alarms have cleared.

Step 16 Repeat this procedure for all the AIS-V alarms on the DS3XM-6 or DS3XM-12 cards.


1.12.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 Cisco ONS 15454 Reference Manual for more information.

1.12.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 Cisco ONS 15454 Procedure Guide Chapter 6, "Create Circuits and VT Tunnels."


1.12.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, go to Chapter 4, "Performance Monitoring."

1.12.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 DCC Tunnels section of the Cisco ONS 15454 Procedure Guide Chapter 5, "Turn Up Network."

1.12.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.12.8  Holdover Synchronization Alarm

Symptom    The clock is running at a different frequency than normal and the "HLDOVRSYNC" alarm 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-125 for a detailed description.


Note The ONS 15454 supports holdover timing per Telcordia GR-436 when provisioned for external (BITS) timing.


1.12.9  Free-Running Synchronization Mode

Symptom    The clock is running at a different frequency than normal and the "FRNGSYNC" alarm 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-112 for a detailed description.

1.12.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.12.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 and has failed to boot. If the card has truly failed, an "EQPT" alarm is raised against the slot number 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 "Physically Replace a Traffic Card" procedure on page 2-271.


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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

1.13  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.

1.13.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 "Faulty Fiber-Optic Connections" section.

1.13.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.

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 "Crimp Replacement LAN Cables" section.

Possible Cause    Faulty GBICs.

Recommended Action    Faulty GBICs can be the source of SONET/DWDM alarms and signal errors. See the "Replace Faulty GBIC or SFP Connectors" section.


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.


Step 2 Ensure that the connector keys on the SC fiber connector are properly aligned and locked.

Step 3 Check that the single-mode fiber power level is within the specified range:

a. Remove the receive (Rx) end of the suspect fiber.

b. Connect the Rx end of the suspect fiber to a fiber-optic power meter, such as a GN Nettest LP-5000.

c. Determine the power level of fiber with the fiber-optic power meter.

d. Verify that the power meter is set to the appropriate wavelength for the OC-N card being tested (either 1310 nm or 1550 nm depending on the specific card).

e. Verify that the power level falls within the range specified for the card if it is an OC-N card; see the "OC-N Card Transmit and Receive Levels" section.

Step 4 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 Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node." If possible, do this for the OC-N card you are working on and the far-end card.

b. Clean the optical connectors on the card. Clean the connectors according to site practice or, if none exists, follow the procedure in the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node." If possible, do this for the OC-N card you are working on and the far-end card.

c. Ensure that the far-end transmitting card is not an ONS intermediate-range (IR) card when an ONS long-range (LR) card is appropriate.

IR cards transmit a lower output power than LR cards.

d. 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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

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. Check that the Tx and Rx fibers are not reversed. LOS and EOC alarms normally accompany reversed Tx and Rx fibers. Switching reversed Tx and Rx fibers clears the alarms and restores the signal.

b. Clean or replace the fiber patch cords. Clean the fiber according to site practice or, if none exists, follow the procedure in the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node." If possible, do this for the OC-N card you are working on and the far-end card.

c. Retest the fiber power level.

d. 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.11.2  Protection Switching, Lock Initiation, and Clearing" section on page 2-260. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 15, "Maintain the Node."

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.13.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-57 shows the wiring of an RJ-45 connector. Figure 1-58 shows a LAN cable layout, and Table 1-5 shows the cable pinouts. Figure 1-59 shows a cross-over cable layout, and Table 1-6 shows the cross-over pinouts.

Figure 1-57 RJ-45 Pin Numbers

Figure 1-58 LAN Cable Layout

Table 1-5 LAN Cable Pinout 

Pin
Color
Pair
Name
Pin

1

white/orange

2

Transmit Data +

1

2

orange

2

Transmit Data -

2

3

white/green

3

Receive Data +

3

4

blue

1

4

5

white/blue

1

5

6

green

3

Receive Data -

6

7

white/brown

4

7

8

brown

4

8


Figure 1-59 Cross-Over Cable Layout

Table 1-6 Cross-Over Cable Pinout 

Pin
Color
Pair
Name
Pin

1

white/orange

2

Transmit Data +

3

2

orange

2

Transmit Data -

6

3

white/green

3

Receive Data +

1

4

blue

1

4

5

white/blue

1

5

6

green

3

Receive Data -

2

7

white/brown

4

7

8

brown

4

8



Note Odd-numbered pins always connect to a white wire with a colored stripe.


1.13.2.2  Replace Faulty GBIC or SFP Connectors

GBICs and Small Form-factor Pluggables (SFP) 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 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 "Ethernet Cards" chapter in 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 DWDM and coarse wavelength division multiplexing (CWDM) GBICs do not function with Software R5.0.


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-60.

Figure 1-60 GBICs

For a list of available GBICs and SFPs for Ethernet cards and SAN (FC_MR-4) cards, refer to the Cisco ONS 15454 Reference Manual Chapter 5, "Ethernet Cards." For a list of available SFPs for TXP and MXP cards, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.


Note GBICs are very similar in appearance. Check the GBIC label carefully before installing it.


Remove GBIC or SFP Connectors


Step 1 Disconnect the network fiber cable from the GBIC SC connector or SFP LC duplex connector.


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 2 Release the GBIC or SFP from the slot by simultaneously squeezing the two plastic tab on each side.

Step 3 Slide the GBIC or SFP 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.


Installing a GBIC with Clips


Step 1 Remove the GBIC from its protective packaging.

Step 2 Check the label to verify that the GBIC is the correct type (SX, LX, or ZX) for your network.

Step 3 Verify that you are installing compatible GBICs; for example, SX to SX, LX to LX, or ZX to ZX.

Step 4 Grip the sides of the GBIC with your thumb and forefinger and insert the GBIC into the slot on the E1000-2, E1000-2-G, or G-Series card (Figure 1-61).


Note GBICs are keyed to prevent incorrect installation.


Figure 1-61 GBIC Installation (with Clips)

Step 5 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.

Step 6 When you are ready to attach the network fiber-optic cable, remove the protective plug from the GBIC and save the plug for future use.

Step 7 Return to your originating procedure (NTP).


Installing a GBIC with a Handle


Step 1 Remove the GBIC from its protective packaging.

Step 2 Check the label to verify that the GBIC is the correct type (SX, LX, or ZX) for your network.

Step 3 Verify that you are installing compatible GBICs; for example, SX to SX, LX to LX, or ZX to ZX.

Step 4 Remove the protective plug from the SC-type connector.

Step 5 Grip the sides of the GBIC with your thumb and forefinger and insert the GBIC into the slot on the E1000-2, E1000-2-G, G1K-4, or G-Series card.


Note GBICs are keyed to prevent incorrect installation.


Step 6 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 SC-type connector.

Step 7 Return to your originating procedure (NTP).


1.13.3  OC-N Card Transmit and Receive Levels

Each OC-N card has a transmit and receive connector on its faceplate. Table 1-7 lists these levels.

Table 1-7 OC-N Card Transmit and Receive Levels 

OC-N Card
Receive
Transmit

OC3 IR4/STM1SH 1310

-28 to -8 dBm

-15 to -8 dBm

OC3 IR/STM 1SH 1310-8

-30 to -8 dBm

-15 to -8 dBm

OC12 IR/STM4 SH 1310

-28 to -8 dBm

-15 to -8 dBm

OC12 LR/STM4 LH 1310

-28 to -8 dBm

-3 to +2 dBm

OC12 LR/STM4 LH 1550

-28 to -8 dBm

-3 to +2 dBm

OC12 IR/STM4 SH 1310-4

-28 to -8 dBm

-3 to +2 dBm

OC48 IR/STM16 SH AS 1310

-18 to 0 dBm

-5 to 0 dBm

OC48 LR/STM16 LH AS 1550

-28 to -8 dBm

-2 to +3 dBm

OC48 ELR/STM16 EH 100GHz

-28 to -8 dBm

-2 to 0 dBm

OC192 SR/STM64 IO 1310

-11 to -1 dBm

-6 to -1 dBm

OC192 IR STM64 SH 1550

-14 to -1 dBm

-1 to +2 dBm

OC192 LR/STM64 LH 1550

-21 to -9 dBm

+7 to +10 dBm

OC192 LR/STM64 LH ITU 15xx.xx

-22 to -9 dBm

+3 to +6 dBm

TXP-MR-10G

Trunk side:
Client side:

-26 to -8 dBm
-14 to -1 dBm

-16 to +3 dBm
-6 to -1 dBm

MXP-2.5G-10G

Trunk side:
Client side:

-26 to -8 dBm
depends on SFP

-16 to +3 dBm
depends on SFP


1.14  Power Supply Problems

Symptom    Loss of power or low voltage, resulting in a loss of traffic and causing the LCD clock to reset to the default date and time.

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 tab and change the Date and Time fields. Complete the "Isolate the Cause of Power Supply Problems" procedure.


Warning When working with live power, always use proper tools and eye protection.



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.

b. Verify that the power cable is #12 or #14 AWG and in good condition.

c. Verify that the power cable connections are properly crimped. Stranded #12 or #14 AWG does not always crimp properly with Staycon type connectors.

d. Verify that 20-A fuses are used in the fuse panel.

e. Verify that the fuses are not blown.

f. 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.

g. Verify that the DC power source has enough capacity to carry the power load.

h. 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.

Step 2 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. Check for excessive power drains caused by other equipment, such as generators.

c. Check for excessive power demand on backup power systems or batteries when alternate power sources are used.


1.14.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 Cisco ONS 15454 Reference Manual Appendix A, "Hardware Specifications."