Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Releases 9.1 and 9.2
Chapter 1, General Troubleshooting
Downloads: This chapterpdf (PDF - 1.71MB) The complete bookPDF (PDF - 8.15MB) | Feedback

General Troubleshooting

Table Of Contents

General Troubleshooting

1.1  Network Troubleshooting Tests

1.1.1  Facility Loopback

1.1.2  Terminal Loopback

1.1.3  Hairpin Circuit

1.1.4  Cross-Connect Loopback

1.2  Identify Points of Failure on an Electrical Circuit Path

1.2.1  Perform a Facility Loopback on a Source-Node Port

Create the Facility Loopback on the Source-Node Port

Test the Facility Loopback

Test the Electrical Cabling

1.2.2  Perform a Hairpin on a Source-Node Port

Create the Hairpin on the Source-Node Port

Test the Hairpin Circuit

1.2.3  Perform a Terminal Loopback on a Destination-Node Port

Create the Terminal Loopback on a Destination-Node Port

Test the Terminal Loopback Circuit on the Destination-Node Port

1.2.4  Perform a Network Interface Unit Loopback on a Destination-Node Port

DS1 Inhibit FEAC Backplane Loopback

Create the NIU Loopback on a Destination-Node DS1 Port

Test and Clear the DS1 NIU Loopback Circuit

1.2.5  Perform a Hairpin Test on a Destination-Node Port

Create the Hairpin Loopback Circuit on the Destination-Node Port

Test the Hairpin Circuit

1.2.6  Perform a Facility Loopback on a Destination Port

Create a Facility Loopback Circuit on a Destination Port

Test the Facility Loopback Circuit

Test the Electrical Cabling

1.3  Identify Points of Failure on an OC-N Circuit Path

1.3.1  Perform a Facility Loopback on a Source-Node OC-N Port

Create the Facility Loopback on the Source OC-N Port

Test the Facility Loopback Circuit

1.3.2  Perform a Cross-Connect Loopback on the Source OC-N Port

Create the Cross-Connect Loopback on the Source OC-N Port

Test the Cross-Connect Loopback Circuit

1.3.3  Perform a Terminal Loopback on a Source-Node OC-N Port

Create the Terminal Loopback on a Source Node OC-N Port

Test the Terminal Loopback Circuit

1.3.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port

Create the Facility Loopback on an Intermediate-Node OC-N Port

Test the Facility Loopback Circuit

1.3.5  Perform a Terminal Loopback on an Intermediate-Node OC-N Port

Create the Terminal Loopback on an Intermediate-Node OC-N Port

Test the Terminal Loopback Circuit

1.3.6  Perform a Facility Loopback on a Destination-Node OC-N Port

Create the Facility Loopback on a Destination-Node OC-N Port

Test the Facility Loopback Circuit

1.3.7  Perform a Terminal Loopback on a Destination-Node OC-N Port

Create the Terminal Loopback on a Destination-Node OC-N Port

Test the Terminal Loopback Circuit

1.4  Troubleshooting Wideband Electrical Card (WBE-28 and WBE-84 Cards) FEAC on DS3 Ports

1.4.1  FEAC Send Code

1.4.2  WBE-28/WBE-84 Inhibit FEAC Loopback

1.4.3  FEAC Alarms

1.5  Troubleshooting WBE-28 and WBE-84 Cards with Far End Loopcodes on DS1 Ports

1.5.1  FEAC Send Code

1.5.2  WBE-28/WBE-84 Inhibit FEAC Loopback

1.6  Troubleshooting Ethernet Circuit Paths With Loopbacks

1.6.1  Perform a Facility Loopback on a Source-Node Ethernet Port

Create the Facility Loopback on the Source-Node Ethernet Port

Test and Clear the Facility Loopback Circuit

Test the Ethernet Card

1.6.2  Perform a Terminal Loopback on a Source-Node Ethernet Port

Create the Terminal Loopback on a Source-Node Ethernet Port

Test and Clear the Ethernet Terminal Loopback Circuit

Test the Ethernet Card

1.6.3  Perform a Hairpin Test on a Source-Node Ethernet Port

Create the Hairpin Circuit on the Source-Node Ethernet Port

Test and Delete the Ethernet Port Hairpin Circuit

Test the Standby Cross-Connect Card

Retest the Original Cross-Connect Card

1.6.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port

Create a Facility Loopback on an Intermediate-Node OC-N Port

Test and Clear the OC-N Facility Loopback Circuit

Test the OC-N (Controller) Card

1.6.5  Perform a Terminal Loopback on Intermediate-Node OC-N Ports

Create a Terminal Loopback on Intermediate-Node OC-N Ports

Test and Clear the OC-N Terminal Loopback Circuit

Test the OC-N Card

1.6.6  Perform a Facility Loopback on a Destination-Node Ethernet Port

Create the Facility Loopback on a Destination-Node Ethernet Port

Test and Clear the Ethernet Facility Loopback Circuit

Test the Ethernet Card

1.6.7  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.8  Perform a Hairpin Test on a Destination-Node Ethernet Port

Create the Hairpin Circuit on the Destination-Node Port

Test and Delete the Ethernet Hairpin Circuit

Test the Standby Cross-Connect Card

Retest the Original Cross-Connect Card

1.7  Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel

1.7.1  Set Up the Equipment for Testing

1.7.2  Perform Manual Mode Tests

1.7.3  Perform Automatic Mode Tests

1.7.4  Retrieving Test Results from Automatic Tests

1.7.5  Perform Loop Tests

1.8  Restore the Database and Default Settings

1.8.1  Restore the Node Database

1.9  PC Connectivity Troubleshooting

1.9.1  Unable to Verify the IP Configuration of Your Microsoft Windows PC

Verify the IP Configuration of Your Microsoft Windows PC

1.9.2  Browser Login Does Not Launch Java

Reconfigure the Microsoft Windows PC Operating System Java Plug-in Control Panel

Reconfigure the Browser

1.9.3  Unable to Verify the NIC Connection on Your Microsoft Windows PC

1.9.4  Verify Microsoft Windows PC Connection to the Node (Ping)

Ping the ONS 15310-CL or ONS 15310-MA

1.10  CTC Operation Troubleshooting

1.10.1  Unable to Launch CTC Help After Removing Netscape

Set Internet Explorer as the Default Browser for CTC

1.10.2  Unable to Change Node View to Network View

Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Microsoft Windows

Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Solaris

1.10.3  Browser Stalls When Downloading CTC JAR Files from port

Disable the VirusScan Download Scan

1.10.4  CTC Does Not Launch

Redirect the Netscape Cache to a Valid Directory

1.10.5  Sluggish CTC Operation or Login Problems

Delete the CTC Cache File Automatically

Delete the CTC Cache File Manually

1.10.6  Node Icon is Gray on CTC Network View

1.10.7  Java Runtime Environment Incompatible

Launch CTC to Correct the Core Version Build

1.10.8  Different CTC Releases Do Not Recognize Each Other

Launch CTC to Correct the Core Version Build

1.10.9  Username or Password Does Not Match the Port Information

Verify Correct Username and Password

1.10.10  Superuser Password Needs to Be Reset

1.10.11  No IP Connectivity Exists Between Nodes

1.10.12  DCC Connection Lost

1.10.13  "Path in Use" Error When Creating a Circuit

Cancel the Circuit Creation and Start Over

1.10.14  Calculate and Design IP Subnets

1.11  Circuits and Timing

1.11.1  Circuit Transitions to Partial Status

View the State of Circuit Nodes

1.11.2  Circuits Remain in PARTIAL Status

1.11.3  AIS-V on Unused 15310-CL-CTX Card VT Circuits

Clear AIS-V on Unused Controller Card VT Circuits

1.11.4  Circuit Creation Error with VT1.5 Circuit

1.11.5  OC-3 and DCC Limitations

1.11.6  ONS 15310-CL or ONS 15310-MA Switches Timing Reference

1.11.7  Holdover Synchronization Alarm

1.11.8  Free-Running Synchronization Mode

1.11.9  Daisy-Chained BITS Not Functioning

1.11.10  Blinking STAT LED after Installing a Card

1.12  Fiber and Cabling

1.12.1  Bit Errors Appear for a Traffic Card

1.12.2  Faulty Fiber-Optic Connections

Verify Fiber-Optic Connections

1.13  Power and LED Tests

1.13.1  Power Supply Problems

1.13.2  Power Consumption for Node and Cards

1.13.3  Lamp Tests for Card LEDs

Verify Card LED Operation

1.13.4  Retrieve Tech Support Logs Button

Off-Load the Diagnostics File


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 15310-CL or Cisco ONS 15310-MA. To troubleshoot specific alarms, see Chapter 2 "Alarm Troubleshooting."

This chapter includes the following sections on network problems:

Network Troubleshooting Tests—Describes loopbacks and hairpin circuits, which you can use to test circuit paths through the network or logically isolate faults.


Note For network acceptance tests, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


Identify Points of Failure on an Electrical Circuit Path—Explains how to perform loopback and hairpin tests, which you can use to test ONS 15310-CL DS-N circuit paths through the network or logically isolate faults.

Identify Points of Failure on an OC-N Circuit Path—Explains how to perform loopback and hairpin tests on OC-N paths, which you can use to test ONS 15310-CL or ONS 15310-MA OC-N circuit paths through the network or logically isolate faults.

Troubleshooting Wideband Electrical Card (WBE-28 and WBE-84 Cards) FEAC on DS3 Ports

Troubleshooting WBE-28 and WBE-84 Cards with Far End Loopcodes on DS1 Ports

Troubleshooting Ethernet Circuit Paths With Loopbacks—Explains how to perform loopback tests for CE100T-8 ports (and intermediate node OC-N ports the Ethernet circuit is mapped through). Follow these instructions to test an Ethernet circuit through the network or logically isolate faults.

Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel—Explains how to use the ONS 15310-MA DSX Wiring Verification Kit to test the DS-1 and DS-3 wiring between an ONS 15310-MA shelf and the digital signal cross-connect (DSX) wiring panel.

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

Restore the Database and Default Settings—Explains how to restore software data and restore the node to the default setup.

PC Connectivity Troubleshooting—Provides troubleshooting procedures for Microsoft Microsoft Windows PC and network connectivity to the ONS 15310-CL or ONS 15310-MA.

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 and LED Tests—Provides troubleshooting procedures for power problems and lists LED behavior.

1.1  Network Troubleshooting Tests

Use loopbacks and hairpins to test newly created circuits before running live traffic or to logically locate the source of a network failure. Both the ONS 15310-CL and ONS 15310-MA allow electrical, optical, and Ethernet loopbacks:

For the ONS 15310-CL, the 15310-CL-CTX controller card contains DS-1, DS-3, EC-1, and OC-3 or OC-12 optical ports which can be loopbacked. The CE-100T-8 Ethernet cards can be loopbacked, but the ML-100T-8 Ethernet card cannot support this function.

For the ONS 15310-MA, the CTX2500 card controller card contains OC-N ports that can support optical loopbacks. The DS1-28/DS3-EC1-3 card and DS1-84/DS3-EC1-3 card support electrical loopbacks. The CE-100T-8 Ethernet card supports loopbacks, but the ML-100T-8 card does not.

1.1.1  Facility Loopback

A facility loopback tests a card's line interface unit (LIU) and related cabling. After applying a facility loopback on a port, use an optical or electrical test set, as appropriate, to run traffic over the loopback. A successful facility loopback isolates the card LIU or the cabling plant as the potential cause of a network problem.


Caution Before performing a facility loopback on any port, make sure there are 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, thus enabling you to remove the facility loopback. Ensuring a second DCC is not necessary if you are directly connected to the node containing the loopback port.


Caution A facility loopback applies to an entire facility and not to an individual circuit. Exercise caution when using loopbacks on an OC-N port carrying live traffic because this traffic can be interrupted.


Note In CTC, the facility loopback is sometimes called a "facility (line)" loopback to indicate the direction that the loopback signal travels, that is, toward the span.


1.1.2  Terminal Loopback

A terminal loopback tests a circuit path as it passes through the cross-connect pathways of the node and loops back from the port where the loopback originates. A terminal loopback on an OC-N port turns the signal around before it reaches the LIU and sends it back through the card. This test verifies that the card's cross-connect circuit paths are valid.

For example, if you place a terminal loopback on a ONS 15310-CL optical port, the test-set traffic enters on the 15310-CL-CTX DS-3 port and travels toward the OC-N port. The terminal loopback placed on this OC-N port turns the signal around before it reaches the LIU, sending it back through the card to the electrical port. This test verifies that the optical cross-connect paths are valid (but it does not test the LIU for the OC-N port).


Note In CTC, the terminal loopback is sometimes called a "terminal (inward)" loopback, indicating the direction that the loopback signal travels—that is, back toward the port where it originated.



Note Due to hardware limitations on a terminal loopback, you cannot send an AIS downstream on a Cisco ONS 15310-CL CTX card.


1.1.3  Hairpin Circuit

A hairpin circuit brings traffic in and out on an electrical port instead of sending the traffic onto the OC-N line. A hairpin loops back only one specific synchronous transport signal (STS) or virtual tributary (VT) circuit. This kind of circuit test can be run on a node running live traffic because it does not affect the rest of the facility's traffic.

1.1.4  Cross-Connect Loopback

A cross-connect loopback tests a circuit path as it passes through the cross-connect portion of the 15310-CL-CTX or CTX2500 card and loops back to the port being tested. Testing and verifying circuit integrity often involves taking down the whole line; however, a cross-connect loopback allows you to create a loopback on any embedded channel at supported payloads at the STS-1 granularity and higher. For example, you can loop back a single STS-1 on an optical facility without interrupting the other STS circuits.

You can create a cross-connect loopback on working or protect OC-3 optical ports unless the protect port is used in a 1+1 protection group and is in working mode.


Note If a terminal or facility loopback exists on an optical port, you cannot use the cross-connect loopback.


1.2  Identify Points of Failure on an Electrical Circuit Path

Facility loopbacks, hairpin circuits, and terminal loopbacks 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 tests in this section can be used to test DS-1, DS-3, or EC-1 circuits on a path protection configuration. Using a series of facility loopbacks, hairpin circuits, and terminal loopbacks, the path of the circuit is traced and the possible points of failure are tested and eliminated. A logical progression of network test procedures applies to this scenario:

1. Facility loopback on the source-node port

2. Hairpin on the source-node port

3. Terminal loopback to the destination-node port

4. Hairpin on the destination-node port

5. Facility loopback to the destination-node port


Note The test sequence for your circuits differs according to the type of circuit and network topology.



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



Note These procedures are performed when power connections to the nodes or sites are within necessary specifications. If the network tests do not isolate the problems, troubleshoot outward for power failure.


1.2.1  Perform a Facility Loopback on a Source-Node Port

The facility loopback test is performed on the node source port in the network circuit. Completing a successful facility loopback on this port isolates the cabling and port as possible failure points.


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


Note Loopbacks operate only on ports in the Out-of-Service, Maintenance (OOS,MT) administrative state and Out-of-Service and Management, Maintenance (OOS-MA,MT) service state. Brief instructions are given in each procedure for changing the port's state. For more information about port state, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


Create the Facility Loopback on the Source-Node Port


Step 1 Connect an electrical test set to the DS-1, DS-3, or EC-1 port you are testing. For the ONS 15310-CL, this port is located on the 15310-CL-CTX. For the ONS 15310-MA, this port is located on the DS1-28/DS3-EC1-3 or DS1-84/DS3-EC1-3.

Use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the port.

Step 2 Adjust the test set accordingly.

Step 3 Use CTC to create the facility loopback on the port being tested:

a. In node view, double-click the card where you are performing the loopback, then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

b. Choose OOS,MT from the Admin State column for the port being tested.

c. Choose Facility from the Loopback Type column for the port being tested.

d. Click Apply.

e. Click Yes in the confirmation dialog box.


Note It is normal for a facility loopback LPBKFACILITY (DS1, DS3) or LPBKFACILITY (EC1) condition to appear during loopback setup. The condition clears when you remove the loopback.


Step 4 Continue with the "Test the Facility Loopback" procedure.


Test the Facility Loopback


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

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

Step 3 If the test set indicates a good circuit, complete the following steps:

a. Double-click the electrical card, then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

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

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

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card, faulty port, or faulty cabling from the electrical port. Continue with the "Test the Electrical Cabling" procedure.


Test the Electrical Cabling


Step 1 Replace the suspect cabling (the cables from the test set to the electrical port) with a cable known to be good.

If a cable known to be good is not available, test the suspect cable with a test set. Remove the suspect cable from the electrical port and connect the cable to the Tx and Rx terminals of the test set. Run traffic to determine whether the cable is good or suspect.

Step 2 Resend test-set traffic on the loopback circuit with a good cable installed.

Step 3 If the test set indicates a good circuit, the problem is probably the defective cable. Replace the defective cable, then clear the loopback:

a. Double-click the card, then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

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

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

d. Click Apply.

e. Click Yes in the confirmation dialog box.

Step 4 If the test set indicates a faulty circuit, the problem might be a faulty port. Continue with the "1.2.2  Perform a Hairpin on a Source-Node Port" procedure.


1.2.2  Perform a Hairpin on a Source-Node Port

The hairpin test is performed on the first port in the network circuit. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through this port isolates the possibility that the source port is the cause of the faulty circuit.

Create the Hairpin on the Source-Node Port


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

If you just completed the "1.2.1  Perform a Facility Loopback on a Source-Node Port" procedure, leave the electrical test set connected to the electrical port.

If you are starting the current procedure without the electrical test set connected to the electrical port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the electrical connectors for the port you are testing.

Step 2 Adjust the test set accordingly.

Step 3 Use CTC to set up the hairpin on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as Hairpin1.

c. Set the circuit Type and Size to the normal preferences, such as STS and STS1.

d. Uncheck the Bidirectional check box and click Next.

e. In the Circuit Source dialog box, select the same Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, use the same Node, Slot, Port, and Type used for the Circuit Source dialog box and click Finish.

Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a one-way circuit.

Step 5 Continue with the "Test the Hairpin Circuit" procedure.


Test the Hairpin Circuit


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

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

Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin loopback circuit. 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.

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

Step 4 If the test set indicates a faulty circuit, there might be a problem with the port. Continue with the "1.2.3  Perform a Terminal Loopback on a Destination-Node Port" procedure.


1.2.3  Perform a Terminal Loopback on a Destination-Node Port

The terminal loopback test is performed on the node destination port in the circuit. First, create a bidirectional circuit that originates on the source node electrical port (such as DS-1, DS-3, or EC-1) and terminates on the destination-node electrical port. Then continue with the terminal loopback test. Completing a successful terminal loopback to a destination-node port verifies that the circuit is good up to the destination port.


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

Create the Terminal Loopback on a Destination-Node Port


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

a. If you just completed the "1.2.2  Perform a Hairpin on a Source-Node Port" procedure, leave the electrical test set connected to the electrical port in the source node.

b. If you are starting the current procedure without the electrical test set connected to the port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the connectors for the electrical port you are testing.

Step 2 Adjust the test set accordingly.

Step 3 Use CTC to set up the terminal loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as DSNtoDSN.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Leave the Bidirectional check box checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the electrical port in the destination node) and click Finish.

Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note Loopbacks operate only on ports in the OOS,MT administrative state.



Note It is normal for a LPBKTERMINAL (DS1, DS3) or LPBKTERMINAL (EC1) condition 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:

From the View menu, choose Go To Other Node.

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

b. In node view, double-click the destination node (ONS 15310-CL or ONS 15310-MA).

c. Double-click the correct card, then click the appropriate following tabs:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

d. Select OOS,MT from the Admin State column.

e. Select Terminal from the Loopback Type column.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Continue with the "Test the Terminal Loopback Circuit on the Destination-Node Port" procedure.


Test the Terminal Loopback Circuit on the Destination-Node Port


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

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

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

a. Double-click the 15310-CL-CTX or CTX2500 card in the destination node with the terminal loopback.

b. Double-click the appropriate card containing the electrical circuit you are testing, and click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

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

d. Select the appropriate state (IS,AINS,AINS OOS,DSBLD or 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.

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty port. Continue with the "1.2.5  Perform a Hairpin Test on a Destination-Node Port" procedure.


1.2.4  Perform a Network Interface Unit Loopback on a Destination-Node Port

The network interface unit (NIU) loopback test is performed on the node destination port in the circuit. First, create a bidirectional circuit that originates on the source node electrical port (DS-1) and terminates on the destination-node electrical port. Then continue with the NIU loopback test. Completing a successful NIU loopback to a destination-node port verifies that the circuit is good up to the destination port.


Note NIU loopback is applicable for ESF frame format only.



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

DS1 Inhibit FEAC Backplane Loopback

DS1 ports initiate loopbacks when they receive FEAC loop codes. If the Inhibit FE Backplane Lbk check box is checked for a DS1 port, that port ignores any FEAC loop codes it receives and will not loop back (return them).

Create the NIU Loopback on a Destination-Node DS1 Port


Step 1 Connect a test set to the near end DS1 port.


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.

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

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 VT, 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 C1C1toC1C6.

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 DS1 where the test set is connected as shown in Figure 1-2.

h. Click Next.

i. In the Circuit Creation destination dialog box, select the Node, card Slot, Port, and DS1 connected to CPE as shown in Figure 1-2.

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.

Step 5 Create NIU Loopback on the destination port being tested:

a. Go to the card view of the destination node:

b. Click the Maintenance > DS1 > Loopback tabs.

c. Uncheck the Inhibit FE Backplane Lbk checkbox for port being tested.


Note The Inhibit FE Backplane Lbk checkbox is always checked by default.


Figure 1-1 Accessing FEAC Functions on the DS1 ports of WBE-28/WBE-84 Cards

d. Click Apply.

Step 6 Send activate loop codes from the test set.

The destination port senses the loop codes form the test set and creates NIU terminal loopback on that port.


Note It is normal for a LPBKTERMINAL (DS1, DS3) condition to appear during a loopback setup. The condition clears when you remove the loopback.


Figure 1-2 Diagram of FEAC Circuit

Step 7 Complete the "Test and Clear the DS1 NIU Loopback Circuit" procedure.


Test and Clear the DS1 NIU Loopback Circuit


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

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

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Clear the NIU loopback through the test set or through CTC:

Step 4 Clear NIU loopback from the test set by sending the deactivate loop codes.

Clear NIU loopback through CTC:

a. Double-click the destination node DS1 card with the NIU loopback.

b. Click the Maintenance > DS1 > Loopback tabs:

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 5 Clear the NIU loopback circuit:

a. Click the Circuits tab.

b. Choose the NIU loopback circuit being tested.

c. Click Delete.


Note If you delete the NIU loopback circuit without clearing the NIU loopback (Step 4), you have to manually clear the NIU loopback through the test set or CTC.


d. Click Yes in the Delete Circuits dialog box.

The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.


Note If the destination port needs to be reused for other purposes, enable the Inhibit FE Backplane Lbk checkbox.

a. Go to the card view of the destination node:

b. Click the Maintenance > DS1 > Loopback tabs.

c. Enable the Inhibit FE Backplane Lbk checkbox for port being tested.

d. Click Apply.



1.2.5  Perform a Hairpin Test on a Destination-Node Port

The hairpin test is performed on the port in the destination node. To perform this test, you must also create a bidirectional circuit in the transmit direction from the destination ONS 15310-CL or ONS 15310-MA to the source node. Creating the bidirectional circuit and completing a successful hairpin eliminates the possibility that the source port, destination port, or fiber span is responsible for the faulty circuit.

Create the Hairpin Loopback Circuit on the Destination-Node Port


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

Use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the electrical cabling panel for the port you are testing.

Step 2 Adjust the test set accordingly.

Step 3 Use CTC to set up the source loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as Hairpin1.

c. Set the circuit Type and Size to the normal preferences, such as STS and STS1.

d. Leave the Bidirectional check box checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the port in the destination node) and click Finish.

Step 4 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.

Step 5 Use CTC to set up the destination hairpin circuit on the port being tested.


Note The destination loopback circuit on a port is a one-way test.


For example, in a typical east-to-west slot configuration, a DS-3 port on the source node is one end of the fiber span, and a DS-3 port on the destination node is the other end.

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as Hairpin1.

c. Set the Circuit Type and Size to the normal preferences, such as STS and STS1.

d. Uncheck the Bidirectional check box and click Next.

e. In the Circuit Source dialog box, select the same Node, Slot, Port, and Type where the previous circuit is connected and click Next.

f. In the Circuit Destination dialog box, use the same Node, Slot, Port, and Type used for the Circuit Source dialog box and click Finish.

Step 6 Confirm that the newly created circuit appears on the Circuits tab list as a one-way circuit.

Step 7 Verify that the circuits connect to the correct slots. For example, verify that source node OC-N port (east slot) is connected to the destination node (west slot). If two east slots or two west slots are connected, the circuit does not work. Except for the distinct slots, all other circuit information, such as ports, should be identical.

Step 8 Continue with the "Test the Hairpin Circuit" procedure.


Test the Hairpin Circuit


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

Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information indicated by the test set.

Step 3 If the test set indicates a good circuit, no further testing is necessary; 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.

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

f. Continue with the "1.2.6  Perform a Facility Loopback on a Destination Port" procedure.


1.2.6  Perform a Facility Loopback on a Destination Port

The final facility loopback test is performed on the last port in the circuit— in this case the port in the destination node. Completing a successful facility loopback on this port isolates the possibility that the destination-node cabling, card, or LIU is responsible for a faulty circuit.


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


Note Loopbacks operate only on ports in the OOS,MT administrative state.


Create a Facility Loopback Circuit on a Destination Port


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

a. If you just completed the "1.2.5  Perform a Hairpin Test on a Destination-Node Port" procedure, leave the electrical test set connected to the electrical port in the destination node.

b. If you are starting the current procedure without the electrical test set connected to the electrical port, use appropriate cabling to attach the Tx and Rx terminals of the electrical test set to the electrical interface panel.

c. Adjust the test set accordingly.

Step 2 Use CTC to create the facility loopback on the port being tested:

a. In node view, double-click the card where you are performing the loopback, then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

b. Select Facility from the Loopback Type column for the port being tested. If you are creating a loopback on a multiport card, select the row appropriate for the desired port.

c. Click Apply.

d. Click Yes in the confirmation dialog box.


Note It is normal for a LPBKFACILITY (DS1, DS3) or LPBKFACILITY (EC1) condition to appear during loopback setup. The condition clears when you remove the loopback.


Step 3 Continue with the "Test the Facility Loopback Circuit" procedure.


Test the Facility Loopback Circuit


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

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

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

a. Clear the facility loopback:

b. Double-click the card, then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

The entire electrical circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.

Step 4 If the test set indicates a faulty circuit, the problem might be a faulty card or faulty cabling. Continue with the "Test the Electrical Cabling" procedure.


Test the Electrical Cabling


Step 1 Replace the suspect cabling (the cables from the test set to the DS-1, DS-3, or EC-1 port) with a cable known to be good.

If a cable known to be good is not available, test the suspect cable with a test set. Remove the suspect cable from the electrical port and connect the cable to the Tx and Rx terminals of the test set. Run traffic to determine whether the cable is good or suspect.

Step 2 Resend test traffic on the loopback circuit with a good cable installed.

Step 3 If the test set indicates a good circuit, the problem is probably the defective cable. Replace the defective cable.

Step 4 Clear the facility loopback:

a. Double-click the card and then click the appropriate tab:

Maintenance > DS1 > Loopback

Maintenance > DS3 > Loopback

Maintenance > EC1 > Loopback

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

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

d. Click Apply.

e. Click Yes in the confirmation dialog box.

The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.


1.3  Identify Points of Failure on an OC-N Circuit Path

Using facility loopbacks, terminal loopbacks, and cross-connect loopback circuits, you can test OC-N facilities or STSs on the ONS 15310-CL or ONS 15310-MA to logically isolate faults. For this purpose, you perform a loopback test at each point along the circuit path to systematically isolate a point of failure.

The example in this section tests an OC-N circuit on a three-node path protection configuration. Using a series of facility loopbacks and terminal loopbacks, the path of the circuit is traced and the possible points of failure are tested and eliminated. A logical progression of seven network test procedures applies to this sample scenario:

1. Facility loopback on the source-node OC-N port

2. Cross-connect loopback on the source-node OC-N port

3. Terminal loopback on the source-node OC-N port

4. Facility loopback on the intermediate-node OC-N port

5. Terminal loopback on the intermediate-node OC-N port

6. Facility loopback on the destination-node OC-N port

7. Terminal loopback on the destination-node OC-N port


Note The test sequence for your circuits differs according to the type of circuit and network topology.



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


1.3.1  Perform a Facility Loopback on a Source-Node OC-N Port

The facility loopback test is performed on the node source port in the network circuit, in this example, the source 15310-CL-CTX or CTX2500 card OC-N port in the source node. Completing a successful facility loopback on this port isolates the OC-N port as a possible failure point. Performing a loopback on an in-service circuit is service-affecting.

Create the Facility Loopback on the Source OC-N Port


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

Use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

Step 2 Use CTC to create the facility loopback circuit on the port being tested:

a. In node view, double-click the controller card (15310-CL-CTX or CTX2500) to display the card view.

b. Click the Maintenance > Optical > Loopback > Port tabs.

c. Choose OOS,MT from the Admin State column for the port being tested.

d. Choose Facility from the Loopback Type column for the port being tested.

e. Click Apply.

f. Click Yes in the confirmation dialog box.


Note It is normal for a LPBKFACILITY (OCN) condition to appear during loopback setup. The condition clears when you remove the loopback.


Step 3 Continue with the "Test the Facility Loopback Circuit" procedure.


Test the Facility Loopback Circuit


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

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

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

g. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

j. Click Apply.

k. Click Yes in the confirmation dialog box.

l. Continue with the "1.3.2  Perform a Cross-Connect Loopback on the Source OC-N Port" procedure.


1.3.2  Perform a Cross-Connect Loopback on the Source OC-N Port

The cross-connect loopback test occurs on the cross-connect portion of the controller card (15310-CL-CTX or CTX2500 card) in a network circuit. Completing a successful cross-connect loopback through the card isolates the possibility that the cross-connect is the cause of the faulty circuit.

Create the Cross-Connect Loopback on the Source OC-N Port


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

a. If you just completed the "1.3.1  Perform a Facility Loopback on a Source-Node OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 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 3 Use CTC to set up the cross-connect loopback on the circuit being tested:

a. In node view, double-click the 15310-CL-CTX or CTX2500 to open the card view.

b. For the OC-N port, click the Maintenance > Optical > Loopback > SONET STS tabs.

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 4 Continue with the "Test the Cross-Connect Loopback Circuit" procedure.


Test the Cross-Connect Loopback Circuit


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

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

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

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

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 If the test set indicates a faulty circuit, there might be a problem with the cross-connect portion of the 15310-CL-CTX or CTX2500 card. Complete the "1.3.3  Perform a Terminal Loopback on a Source-Node OC-N Port" procedure.


1.3.3  Perform a Terminal Loopback on a Source-Node OC-N Port

The terminal loopback test is performed on the node destination port in the circuit, in this example, the destination OC-N port in the source node. First, create a bidirectional circuit that starts on the node source OC-N port and loops back on the node destination OC-N port. Then continue with the terminal loopback test. Completing a successful terminal loopback to a node destination OC-N port verifies that the circuit is good up to the destination OC-N. Performing a loopback on an in-service circuit is service-affecting.

Create the Terminal Loopback on a Source Node OC-N Port


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

a. If you just completed the "1.3.2  Perform a Cross-Connect Loopback on the Source OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 Use CTC to set up the terminal loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as OCN1toOCN2.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Verify that Bidirectional is checked.

e. Click Next.

f. In the Circuit Source dialog box, fill in the same Node, Slot, Port, and Type where the test set is connected and click Next.

g. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the source node) and click Finish.

Step 3 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note It is normal for a LPBKTERMINAL (OCN) condition to appear during a loopback setup. The condition clears when you remove the loopback.


Step 4 Create the terminal loopback on the destination port being tested:

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

b. Click the Maintenance > Optical > Loopback > Port tabs.

c. Select OOS,MT from the Admin State column.

d. Select Terminal from the Loopback Type column.

e. Click Apply.

f. Click Yes in the confirmation dialog box.

Step 5 Continue with the "Test the Terminal Loopback Circuit" procedure.


Test the Terminal Loopback Circuit


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

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

If the test set indicates a good circuit, no further testing is necessary on the loopback circuit:

Step 3 Clear the terminal loopback:

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

b. Click the Maintenance > Optical > Loopback > Port tabs.

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

d. Select the appropriate state (IS,AINS; OOS,DSBLD; or 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.

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty port. Continue with the "1.3.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port" procedure.


1.3.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port

The facility loopback test is performed on the node source port in the network circuit, in this example, the source OC-N port in the intermediate node. Completing a successful facility loopback on this port isolates the OC-N port as a possible failure point.


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

Create the Facility Loopback on an Intermediate-Node OC-N Port


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

a. If you just completed the "1.3.3  Perform a Terminal Loopback on a Source-Node OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 Use CTC to set up the facility loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as OCN1toOCN3.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Verify that Bidirectional is checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the intermediate node) and 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 a LPBKFACILITY (OCN) condition to appear during a loopback setup. The condition clears when you remove the loopback.


Step 4 Create the facility loopback on the destination port being tested:

a. Go to the node view of the intermediate node:

From the View menu, choose Go To Other Node.

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

b. In node view, double-click the controller card (15310-CL-CTX or CTX2500) in the intermediate node.

c. Click the Maintenance > Optical > Loopback > Port tabs.

d. Select OOS,MT from the Admin State column.

e. Select Facility from the Loopback Type column.

f. Click Apply.

g. Click Yes in the confirmation dialog box.


Note It is normal for a LPBKFACILITY (OCN) condition to appear during loopback setup. The condition clears when you remove the loopback.


Step 5 Continue with the "Test the Facility Loopback Circuit" procedure.


Test the Facility Loopback Circuit


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

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

If the test set indicates a good circuit, no further testing is necessary with the facility loopback:

Step 3 Clear the facility loopback:

a. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

d. Click Apply.

e. Click Yes in the confirmation dialog box.

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

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty OC-N port. Continue with the "1.3.5  Perform a Terminal Loopback on an Intermediate-Node OC-N Port" procedure.


1.3.5  Perform a Terminal Loopback on an Intermediate-Node OC-N Port

The terminal loopback test is performed on the node destination port in the circuit, in this example, the destination OC-N port in the intermediate node. First, create a bidirectional circuit that starts on the node source OC-N port and loops back on the node destination OC-N port. Then continue with the terminal loopback test. Completing a successful terminal loopback to a node destination OC-N port verifies that the circuit is good up to the destination OC-N port.


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

Create the Terminal Loopback on an Intermediate-Node OC-N Port


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

a. If you just completed the "1.3.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 Use CTC to set up the terminal loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as OCN1toOCN4.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Leave the Bidirectional check box checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the intermediate node) and 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 a LPBKTERMINAL (OCN) condition 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 intermediate node:

From the View menu, choose Go To Other Node.

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

b. In node view, double-click the controller card (15310-CL-CTX or CTX2500) with the OC-N port requiring a loopback.

c. Click the Maintenance > Optical > Loopback > Port tabs.

d. Select OOS,MT from the Admin State column.

e. Select Terminal from the Loopback Type column.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 5 Continue with the "Test the Terminal Loopback Circuit" procedure.


Test the Terminal Loopback Circuit


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

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

If the test set indicates a good circuit, no further testing is necessary on the loopback circuit.

Step 3 Clear the terminal loopback:

a. Double-click the card with the loopback.

b. Click the Maintenance > Optical > Loopback > Port tabs.

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

d. Select the appropriate state (IS,AINS; OOS,DSBLD; or 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.

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty controller card (15310-CL-CTX or CTX2500). Continue with the "1.3.6  Perform a Facility Loopback on a Destination-Node OC-N Port" procedure.


1.3.6  Perform a Facility Loopback on a Destination-Node OC-N Port

The final facility loopback test is performed on the source OC-N port in the destination node. Completing a successful facility loopback on this port isolates the OC-N port as a possible failure point.


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

Create the Facility Loopback on a Destination-Node OC-N Port


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

a. If you just completed the "1.3.5  Perform a Terminal Loopback on an Intermediate-Node OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 Use CTC to set up the facility loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as OCN1toOCN5.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Leave the Bidirectional check box checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the destination node) and click Finish.

Step 3 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note It is normal for a LPBKFACILITY (OCN) condition to appear during a loopback setup. The condition clears when you remove the loopback.


Step 4 Create the facility loopback on the destination port being tested:

a. Go to the node view of the destination node:

From the View menu, choose Go To Other Node.

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

b. In node view, double-click the 15310-CL-CTX or CTX2500 card with the OC-N port that requires the loopback.

c. Click the Maintenance > Optical > Loopback > Port tabs.

d. Select OOS,MT from the Admin State column.

e. Select Terminal from the Loopback Type column.

f. Click Apply.

g. Click Yes in the confirmation dialog box.


Note It is normal for a LPBKFACILITY (OCN) condition to appear during loopback setup. The condition clears when you remove the loopback.


Step 5 Continue with the "Test the Facility Loopback Circuit" procedure.


Test the Facility Loopback Circuit


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

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

If the test set indicates a good circuit, no further testing is necessary with the facility loopback:

Step 3 Clear the facility loopback:

a. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

d. Click Apply.

e. Click Yes in the confirmation dialog box.

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

Step 5 If the test set indicates a faulty circuit, the problem might be a faulty OC-N port. Continue with the "1.3.7  Perform a Terminal Loopback on a Destination-Node OC-N Port" procedure.


1.3.7  Perform a Terminal Loopback on a Destination-Node OC-N Port

The terminal loopback test is performed on the destination OC-N port in the destination node. First, create a bidirectional circuit that starts on the node source OC-N port and loops back on the node destination OC-N port. Then continue with the terminal loopback test. Completing a successful terminal loopback to a node destination OC-N port verifies that the circuit is good up to the destination OC-N.


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

Create the Terminal Loopback on a Destination-Node OC-N Port


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

a. If you just completed the "1.3.6  Perform a Facility Loopback on a Destination-Node OC-N Port" procedure, leave the optical test set connected to the OC-N port in the source node.

b. If you are starting the current procedure without the optical test set connected to the OC-N port, use appropriate cabling to attach the Tx and Rx terminals of the optical test set to the port you are testing.

c. Adjust the test set accordingly.

Step 2 Use CTC to set up the terminal loopback circuit on the port being tested:

a. Click the Circuits tab and click Create.

b. Give the circuit an easily identifiable name, such as OCN1toOCN6.

c. Set circuit Type and Size to the normal preferences, such as STS and STS1.

d. Leave the Bidirectional check box checked and click Next.

e. In the Circuit Source dialog box, fill in the source Node, Slot, Port, and Type where the test set is connected and click Next.

f. In the Circuit Destination dialog box, fill in the destination Node, Slot, Port, and Type (the OC-N port in the destination node) and click Finish.

Step 3 Confirm that the newly created circuit appears on the Circuits tab list as a two-way circuit.


Note It is normal for a LPBKTERMINAL (OCN) condition 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:

From the View menu, choose Go To Other Node.

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

b. In node view, double-click the controller card (15310-CL-CTX or CTX2500) with the OC-N port that requires the loopback, such as the 15310-CL-CTX in the destination-node ONS 15310-CL.

c. Click the Maintenance > Optical > Loopback > Port tabs.

d. Select OOS,MT from the Admin State column.

e. Select Terminal from the Loopback Type column.

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 5 Continue with the "Test the Terminal Loopback Circuit" procedure.


Test the Terminal Loopback Circuit


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

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

Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit:

a. Clear the terminal loopback:

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

Click the Maintenance > Optical > Loopback > Port tabs.

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

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

Click Apply.

Click Yes in the confirmation dialog box.

b. Clear the terminal loopback circuit:

Click the Circuits tab.

Choose the loopback circuit being tested.

Click Delete.

Click Yes in the Delete Circuits dialog box.

If no fault is found, the entire OC-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.


1.4  Troubleshooting Wideband Electrical Card (WBE-28 and WBE-84 Cards) FEAC on DS3 Ports

WBE-28/WBE-84 cards support far-end alarm and control (FEAC) functions on DS3 ports. Click the WBE-28/WBE-84 Maintenance > DS3 tabs at the card view to reveal the two additional function columns. Figure 1-1 shows the DS3 subtab and the additional Send Code and Inhibit FE Lbk function columns.

Figure 1-3 Accessing FEAC Functions on the DS3 ports of WBE-28/WBE-84 Cards

The "far end" in FEAC refers to the equipment connected to the WBE card and not to the far end of a circuit. In Figure 1-2, if a WBE-28/WBE-84 DS3 (near-end) port is configured to send a line loop code, the code will be sent to the connected test set, not the WBE-28/WBE-84 DS3 (far-end) port. FEAC functions will be available only when the DS3 port is configured in CBIT Framing.

Figure 1-4 Diagram of FEAC Circuit

1.4.1  FEAC Send Code

The Send Code column on the WBE-28/WBE-84 cards Maintenance tab only applies to OOS-MA,MT ports configured for CBIT framing. The column lets a user select No Code (the default) or line loop code. Selecting line loop code inserts a line loop activate FEAC in the CBIT overhead transmitting to the connected facility. This code initiates a loopback from the facility to the ONS 15310-MA. Selecting No Code sends a line-loop-deactivate FEAC code to the connected equipment, which will remove the loopback.

1.4.2  WBE-28/WBE-84 Inhibit FEAC Loopback

WBE-28/WBE-84 DS3 ports initiate loopbacks when they receive FEAC line loop codes. If the Inhibit FE Lbk check box is checked for a DS3 port, that port ignores any FEAC line loop codes it receives and will not loop back (return them). If you inhibit a DS3 port's far end loopback response, this DS3 port is not restricted from terminal or facility loopbacks.

1.4.3  FEAC Alarms

When an ONS 15310MA - WBE-28/WBE-84 DS3 port receives an activation code for a FEAC loopback, it raises the "LPBKDS3FEAC" condition on page 2-107. 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 "LPBKDS3FEAC-CMD" condition on page 2-108 for the near-end port.

1.5  Troubleshooting WBE-28 and WBE-84 Cards with Far End Loopcodes on DS1 Ports

WBE Cards support Far End Loopcodes when the DS1 port is operating in ESF Framing mode. Click the WBE-28/WBE-84 Maintenance->DS1 tab to reveal additional columns, namely, "Inhibit FE Lbk" and "Send Code". Here we are using the term FE Loopcodes instead of FEAC in DS1, since DS1 supports only Far End Loopcodes, but NOT Alarms.

Figure 1-5 Accessing Far End troubleshooting Functions on the WBE Cards


Note The term "Far End" refers to the equipment connected to the WBE card and not to the far end of a circuit.


1.5.1  FEAC Send Code

The Send Code column on the WBE-28/WBE-84 card Maintenance tab only applies to OOS-MA,MT ports configured for ESF framing. The column lets a user select No Code (the default) or line loop code. Selecting line loop code inserts a line loop activate Far End Loopcode in the ESF overhead transmitting to the connected facility. This code initiates a loopback from the facility to the ONS 15454. Selecting No Code sends a line-loop-deactivate Far End Loopcode to the connected equipment, which will remove the loopback.

1.5.2  WBE-28/WBE-84 Inhibit FEAC Loopback

WBE-28/WBE-84 DS1 ports initiate loopbacks when they receive Far End line loop codes. If the Inhibit FE Lbk check box is checked for a DS1 port, that port ignores any Far End line loop codes it receives and will not loop back. If you inhibit a DS1 port's far end loopback response, this DS1 port is not restricted from terminal or facility loopbacks.

1.6  Troubleshooting Ethernet Circuit Paths With Loopbacks

Facility loopbacks, terminal loopbacks, and cross-connect loopback circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a loopback test at each point along the circuit path systematically isolates possible points of failure.

When performing this testing on networks that contain intermediate nodes, you will test the OC-N connection at intermediate nodes rather than CE100T-8 card connections. (The CE100T-8 is a mapper card and is only capable of supporting point-to-point circuits.)

You can use these procedures on CE100T-8 cards but not on ML-100T-8 Ethernet cards. Using a series of facility loopbacks and terminal loopbacks, the example scenario traces the circuit path, tests the possible failure points, and eliminates them. The logical progression contains six network test procedures:


Note The test sequence for your circuits will differ according to the type of circuit and network topology.


1. A facility loopback on the source-node Ethernet port

2. A terminal loopback on the source-node Ethernet port

3. A facility loopback on the intermediate-node OC-N port

4. A terminal loopback on the intermediate-node OC-N port

5. A facility loopback on the destination-node Ethernet port

6. A terminal loopback on the destination-node Ethernet port


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


1.6.1  Perform a Facility Loopback on a Source-Node Ethernet Port

The facility loopback test is performed on the node source port in the network circuit. Completing a successful facility loopback on this port isolates the port as a possible failure point.


Note Facility loopbacks require on-site personnel.



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

Complete the "Create the Facility Loopback on the Source-Node Ethernet Port" procedure.

Create the Facility Loopback on the Source-Node Ethernet Port


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


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


Use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. The Tx and Rx terminals connect to the same port.

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

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

Step 4 Click the Maintenance > Loopback tabs.

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 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 "LPKTERMINAL (CE100T, CEMR)" condition on page 2-110 to appear during loopback setup. The condition clears when you remove the loopback.


Step 9 Complete the "Test and Clear the Facility Loopback Circuit" procedure.


Test and Clear the Facility Loopback Circuit


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

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

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

a. Double-click the CE100T-8 card, then click the Maintenance > Loopback tabs.

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

c. 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 Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure for the faulty card.

Step 5 Clear the facility loopback:

a. Double-click the CE100T-8 card, then click the Maintenance > Loopback tabs.

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

c. 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 "1.6.2  Perform a Terminal Loopback on a Source-Node Ethernet Port" procedure.


1.6.2  Perform a Terminal Loopback on a Source-Node Ethernet Port

The terminal loopback test is performed on the node source Ethernet port. To do this, you create a bidirectional circuit that starts on the node destination CE100T-8 port and loops back on node source CE100T-8 port. You then proceed with the terminal loopback test. Completing a successful terminal loopback to a node source port verifies that the circuit is good to the source port.


Note Terminal loopbacks require on-site personnel.



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

Complete the "Create the Terminal Loopback on a Source-Node Ethernet Port" procedure.

Create the Terminal Loopback on a Source-Node Ethernet Port


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


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


a. If you just completed the "1.6.1  Perform a Facility Loopback on a Source-Node Ethernet Port" procedure, leave the test set hooked up to the Ethernet port in the source node.

b. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.

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

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

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 "LPKTERMINAL (CE100T, CEMR)" condition on page 2-110 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. In node view, double-click the card that requires the loopback, such as the destination G-Series card in the source node.

b. Click the Maintenance > Loopback tabs.

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 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 CE100T-8 card in the source node with the terminal loopback.

b. Click the Maintenance > Loopback tabs.

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

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 Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure 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 CE100T-8 card with the terminal loopback in the source node.

b. Click the Maintenance > Loopback tabs.

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

d. 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 "1.6.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port" procedure.


1.6.3  Perform a Hairpin Test on a Source-Node Ethernet Port

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

Figure 1-6 Hairpin Loopback on a Source-Node Ethernet Port


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



Note Hairpin loopbacks require on-site personnel.


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

Create the Hairpin Circuit on the Source-Node Ethernet Port


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

a. If you just completed the "1.6.2  Perform a Terminal Loopback on a Source-Node Ethernet Port" procedure, leave the Ethernet test set hooked up to the Ethernet port in the source node.

b. If you are starting the current procedure without the Ethernet test set hooked up to the Ethernet port, use appropriate cabling to connect the Ethernet test set to the port you are testing.

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

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

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

b. 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 3 Confirm that the newly created circuit appears on the Circuits tab and that the Dir column describes it as a one-way circuit.

Step 4 Complete the "Test and Delete the Ethernet Port Hairpin Circuit" procedure.


Test and Delete the Ethernet 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 Cross-Connect Card" procedure.


Test the Standby Cross-Connect Card


Note Two cross-connect cards (active and standby) must be in use on a node to use this procedure.



Step 1 Perform a reset on the Active cross-connect card to make the Standby card Active:

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.


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.

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

Step 3 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 4 To confirm a defective original cross-connect card, complete the "Retest the Original Cross-Connect Card" procedure.


Retest the Original Cross-Connect Card


Step 1 Initiate an external switching command (side switch) on the cross-connect cards:

a. Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.

b. In node view, select the Maintenance > Cross-Connect > Cards tabs.

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 at (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 "2.10.3  Physical Card Reseating and Replacement" procedure 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 "1.6.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port" procedure.


1.6.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port

Performing the facility loopback test on an intermediate node OC-N port (which carries the Ethernet circuit) isolates whether this node is causing circuit failure. Complete the "Create a Facility Loopback on an Intermediate-Node OC-N Port" procedure.


Note The CE100T-8 Ethernet card only supports point-to-point configurations and is not directly implicated in the intermediate node testing.


Create a Facility Loopback on an Intermediate-Node OC-N Port


Step 1 Connect a test set to the OC-N port you are testing. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


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

Step 3 Use CTC to set up the facility loopback on the OC-N port:

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

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

c. Click Next.

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

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.

Step 5 Create the facility loopback on the destination port being tested:

a. Go to the node view of the intermediate node:

Choose View > Go To Other Node from the menu bar.

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 15310-CL-CTX or CTX2500 card card where you will perform the loopback.

c. Click the Maintenance > Optical > Loopback > Port tabs.

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


Note It is normal for the "LPBKFACILITY (OCN)" condition on page 2-110. The condition clears when you remove the loopback.


Step 6 Complete the "Test and Clear the OC-N Facility Loopback Circuit" procedure.


Test and Clear the OC-N Facility Loopback Circuit


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

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

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

a. Double-click the 15310-CL-CTX or CTX2500 card card and click the Maintenance > Optical > Loopback > Port tabs.

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

c. Choose the appropriate state (IS; 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 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 OC-N (Controller) Card" procedure.


Test the OC-N (Controller) Card


Step 1 Complete the "Physically Replace a Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure for the faulty card.

Step 5 Clear the facility loopback from the port:

a. Double-click the card and click the Maintenance > Optical > Loopback > Port tabs.

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

c. Choose the appropriate state (IS; 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 "1.6.5  Perform a Terminal Loopback on Intermediate-Node OC-N Ports" procedure.


1.6.5  Perform a Terminal Loopback on Intermediate-Node OC-N 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. To do this, you 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.


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


Note Terminal loopbacks require on-site personnel.


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

Create a Terminal Loopback on Intermediate-Node OC-N Ports


Step 1 Connect a test set to the 15310-CL-CTX or CTX2500 card port you are testing:


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


a. If you just completed the "1.6.4  Perform a Facility Loopback on an Intermediate-Node OC-N Port" procedure for the Ethernet circuit, leave the test set hooked up to the intermediate-node port.

b. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.

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

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

e. Leave the Bidirectional check box checked.

f. Click Next.

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

h. Click Next.

i. 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-112 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 15310-CL-CTX or CTX2500 card that requires the loopback.

c. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

f. Click Apply.

g. Click Yes in the confirmation dialog box.

Step 6 Complete the "Test and Clear the OC-N Terminal Loopback Circuit" procedure.


Test and Clear the OC-N 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 15310-CL-CTX or CTX2500 card with the terminal loopback to display the card view.

b. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

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 OC-N Card" procedure.


Test the OC-N Card


Step 1 Complete the "Physically Replace a Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure for the defective card.

Step 5 Clear the terminal loopback on the port:

a. Double-click the source-node 15310-CL-CTX or CTX2500 card with the terminal loopback.

b. Click the Maintenance > Optical > Loopback > Port tabs.

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

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 "1.6.6  Perform a Facility Loopback on a Destination-Node Ethernet Port" procedure.


1.6.6  Perform a Facility Loopback on a Destination-Node Ethernet Port

You perform a facility loopback test at the destination port to determine whether this local port is the source of circuit trouble.


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


Note Facility loopbacks require on-site personnel.


Complete the "Create the Facility Loopback on a Destination-Node Ethernet Port" procedure.

Create the Facility Loopback on a Destination-Node Ethernet Port


Step 1 Connect a test set to the CE100T-8 card that you are testing:


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


a. If you just completed the "Perform a Terminal Loopback on Intermediate-Node OC-N Ports" section, leave the test set hooked up to the source-node port.

b. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.

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

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

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 LPKTERMINAL (CE100T, CEMR) to appear during a loopback setup. The condition clears when you remove the loopback.


Step 5 Create the facility loopback on the destination port being tested:

a. Go to the node view of the destination node:

Choose View > Go To Other Node from the menu bar.

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

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

c. Click the Maintenance > Loopback tabs.

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 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 Loopback Circuit" procedure.


Test and Clear the Ethernet 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. Clear the facility loopback from the port:

a. Double-click the CE100T-8 card and click the Maintenance > Loopback tabs.

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 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 Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure for the faulty card.

Step 5 Clear the facility loopback on the port:

a. Double-click the CE100T-8 card and click the Maintenance > Loopback tabs.

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 "1.6.7  Perform a Terminal Loopback on a Destination-Node Ethernet Port" procedure.


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

The terminal loopback at the destination-node port is the final local hardware error elimination in the circuit troubleshooting process. If this test is completed successfully, you have verified that the circuit is good up to the destination port.


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


Note Terminal loopbacks require on-site personnel.


Complete the "Create the Terminal Loopback on a Destination-Node Ethernet Port" procedure.

Create the Terminal Loopback on a Destination-Node Ethernet Port


Step 1 Connect a test set to the CE100T-8 port that you are testing:


Note For specific procedures to connect, set up, and use the test set equipment, consult the manufacturer.


a. If you just completed the "1.6.6  Perform a Facility Loopback on a Destination-Node Ethernet Port" procedure, leave the test set hooked up to the source port.

b. If you are starting the current procedure without the test set hooked up to the source port, use appropriate cabling to attach the Tx and Rx terminals of the test set to the port you are testing. Both Tx and Rx connect to the same port.

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

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

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 "LPKTERMINAL (CE100T, CEMR)" condition on page 2-110 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 CE100T-8 card that requires the loopback.

c. Click the Maintenance > Loopback tabs.

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

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

f. Click Apply.

g. Click Yes in the confirmation dialog box.

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 CE100T-8 card with the terminal loopback.

b. Click the Maintenance > Loopback tabs.

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

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 Card" procedure 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. Refer to the procedures in the "Protection Switching, Lock Initiation, and Clearing" section. For more information, refer to the "Maintain the Node" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.

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 Card" procedure for the defective card.

Step 5 Clear the terminal loopback on the port:

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

b. Click the Maintenance > Loopback tabs.

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

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

e. Click Apply.

f. Click Yes in the confirmation dialog box.

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.8  Perform a Hairpin Test on a Destination-Node Ethernet Port

The hairpin test is performed on the cross-connect card in the network circuit. A hairpin circuit uses the same port as source as well as destination. Completing a successful hairpin through the card isolates the possibility that the cross-connect card is the cause of the faulty circuit. Figure 1-7 shows an example of a hairpin loopback on a destination-node port.

Figure 1-7 Hairpin on a Destination-Node Ethernet Port


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



Note Hairpin loopbacks require on-site personnel.


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

Create the Hairpin Circuit on the Destination-Node Port


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

a. If you just completed the "1.6.7  Perform a Terminal Loopback on a Destination-Node Ethernet Port" procedure, leave the Ethernet test set hooked up to the Ethernet port in the destination node.

b. If you are starting the current procedure without the Ethernet test set hooked up to the Ethernet port, use appropriate cabling to connect the Ethernet test set to the port you are testing.

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 Ethernet Hairpin Circuit" procedure.


Test and Delete the Ethernet 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 Cross-Connect Card" procedure.


Test the Standby Cross-Connect Card


Note Two cross-connect cards (active and standby) must be in use on a node to use this procedure.



Step 1 Perform a reset on the Active cross-connect card to make the Standby card Active:

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.


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.

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

Step 3 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 4 To confirm a defective original cross-connect card, complete the "Retest the Original Cross-Connect Card" procedure.


Retest the Original Cross-Connect Card


Step 1 Initiate an external switching command (side switch) on the cross-connect cards:

a. Determine the standby cross-connect card. On both the physical node and the CTC node view window, the standby cross-connect ACT/SBY LED is amber and the active card ACT/SBY LED is green.

b. In node view, select the Maintenance > Cross-Connect > Cards tabs.

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 return materials authorization (RMA) process. Contact Cisco Technical Support at (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 "2.10.3  Physical Card Reseating and Replacement" procedure 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.

The entire circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.


1.7  Verify Wiring from the ONS 15310-MA Shelf and DSX Wiring Panel

This procedure verifies the DS-1 and DS-3 wiring between the backplane of an ONS 15310-MA shelf and the digital signal cross-connect (DSX) wiring panel. The procedure is normally used in new installations before the cards have been installed and while the shelf is still powered down.


Note Before performing this procedure, the TST-DSX card must be installed in the Cisco ONS 15310-MA shelf. Refer to the "Install the Cisco ONS 15310-MA" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for instructions.



Caution There must be no DS-1 or DS-3 traffic in the side of the shelf being tested. The TST-DSX card disrupts service if it is plugged into the companion slot of a shelf side where a DS-1 or DS-3 port is already carrying traffic on that same side.

1.7.1  Set Up the Equipment for Testing


Step 1 Install the TST-DSX card in the ONS 15310-MA shelf and prepare the handheld receiver as described in the "Install the Cisco ONS 15310-MA" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


Note The TST-DSX card may be installed only in Slots 1 or 2 of the "A" side of the shelf or Slots 5 or 6 of the "B" side.



Note The TST-DSX card receives power either from the shelf or from the supplied AC-to-DC converter.



Note The TST-DSX card sends signals to the handheld receiver over the DS-1 and DS-3 cable bundles on both the IN and OUT ports as labeled on the DSX wiring panel. The handheld receiver is designed to function as a single-location testing device at the DSX panel for all IN and OUT DS-1 and DS-3 ports.


Figure 1-8 shows the test setup.

Figure 1-8 TST-DSX and Remote Receiver Faceplates

Figure 1-9 shows how to use the handheld receiver to perform various tests.

Figure 1-9 Handheld Receiver Usage Flowchart

Step 2 Connect a patch cord between the DS1 Port or DS3 Port connector on the handheld receiver and the desired port of the DSX panel.

The following patch cords are available

DS-3 patch cords

75-ohm male BNC connector to male WECo 440A male connector

75-ohm male BNC connector to WECo 358 male connector

75-ohm male BNC connector to 75-ohm male BNC connector

75-ohm male BNC connector to LCP connector

DS1 patch cords

100-ohm male Bantam connector to 100-ohm male Bantam connector

100-ohm male Bantam connector to 100-ohm 310 connector

Step 3 Complete the "1.7.2  Perform Manual Mode Tests" procedure or the "1.7.3  Perform Automatic Mode Tests" procedure, as needed.


1.7.2  Perform Manual Mode Tests

The manual mode test allows you to plug the patch cord from the appropriate connector on the handheld receiver (DS1 Port or DS3 Port) into a connector on the DSX panel. The handheld receiver then displays the result of the test. The manual mode is useful for debugging a small number of wiring connections.

1.7.2.1  Set Up the Handheld Receiver for Manual Mode Testing

This section describes how to set up the 15xxx RR handheld receiver to test individual wire connections. Figure 1-9 shows how to move from one option setting to another with the handheld receiver.


Step 1 Turn the handheld receiver unit on using the OFF- ON switch on the left side of the unit and observe the display.

Step 2 After the display has stopped changing, you will see that it is in manual mode with the settings last used, either DS-1 or DS-3.

Step 3 To change to a different cable type (DS-1 or DS-3), press the MENU key once.

Step 4 While the MENU screen is being displayed, press the DISPLAY key to change the setting and the ENTER key to store the setting.

Step 5 Complete the "1.7.2.2  Perform Manual Tests" procedure, as needed.


1.7.2.2  Perform Manual Tests


Step 1 At the DSX wiring panel, insert a appropriate patch cord into the handheld receiver.

Step 2 Insert the other end of the patch cord into a port on the DSX panel. The handheld receiver's screen continuously shows the test result of any detected signal.

Step 3 Review the "View and Troubleshoot Manual Test Results" section.


1.7.2.3  View and Troubleshoot Manual Test Results

The handheld receiver screen displays the test result for one DSX port and its DSX wiring, as shown in Table 1-1. Each port is uniquely identified and reported. If a test signal generated from the TST-DSX card is properly detected, the handheld receiver decodes the signal and the screen displays the port type and number and gives an OK indication. Detected errors also appear on the handheld receiver screen. Test results are not stored in the handheld receiver memory during Manual mode.

Much like a voltmeter, the handheld receiver displays what it sees. The handheld receiver reports a "good" port signal whenever it detects a properly encoded signal at its input; it has no knowledge of any labels at the DSX panel. For example, if the wires of a good signal for port A:12 are wrongly cross-wired to the DSX port labeled B:84, the handheld receiver only reports what it sees: port A:12 is "good."

While the handheld receiver is in the manual mode, the EXIT TEST or ENTER/ACCEPT keys have no effect.

Table 1-1 Messages and Probable Indications 

General Indication
Definition and Probable Cause
Specific Sample Message
Definition and Probable Cause

OK

The handheld receiver detects a valid signal from the TST-DSX card, indicating the wiring is correct.

INP DS1 B:42 OK

Input B side, port 42 for DS-1 is detected and tests good.

OPEN/NC

There is no signal at the input to the handheld receiver. When the handheld receiver is first powered up and before any patch cord is inserted into the unit, the Open/NC message is given. This message also appears if a wire is broken from the shelf to the DSX or if a "split pair" error is made where, for example, a "TIP" of one port and a "RING" of another port are both wired to the same DSX port appearance. Also, if the TST- DSX is not powered or not inserted into the shelf, no signals are generated.

DS1 OPEN/NC

There is no signal at the input to the handheld receiver.

I, IN or INP

An input port. A DS I or DS-3 service signal, if present, would flow from the DSX to the shelf.

INP DS1 B:42 OK

Input B side, port 42 for DS-1 is detected and tests good.

O or OUT

An output port. A DS-1 or DS-3 service signal, if present, would flow from the shelf to the DSX.

OUT DS1 A: 5 OK

Output A side, port 5 for DS I is detected and tests good.

SHORT

The handheld receiver detects that the TIP and RING of a DS-1 are shorted together, or the DS-3 center conductor is shorted to its shield or frame ground.

DS1 SHORT

The Tip and Ring of a DS-1 port are shorted together.

UNIDENT

An unidentified signal is detected.

DS1 UNIDENTIFIED

The signal is not valid for the 15310-MA shelf.

INR or REV

For DS-1 input wires: Tip and Ring reversal.

DS1 => INP
A:11 REV

DS-1 input A side, port 11 is detected, but the tip and ring are reversed.

OUTR or REV

For DS-1 output wires: Tip and Ring reversal.

DS1 => OUT
A:10 REV

DS 1 output A side, port 10 is detected, but the tip and ring are reversed.

WE or
WIRE ERR

A wiring error is detected. WIRE ERR appears on the handheld receiver if the detected signal cannot be diagnosed. There are cases, such as when two or more wires shorted together, where WIRE ERROR is the only indication the handheld receiver can display.


1.7.3  Perform Automatic Mode Tests

This section describes how to use the 15xxx RR handheld receiver to perform a series of tests that span one or more groups of shelf wiring. With the handheld receiver you can also view and record test results. The handheld receiver guides you through the port numbers.

There are two types of automatic mode tests:

True automatic mode

Manual prompt mode

The handheld receiver ships with the true automatic mode as the default selection.

1.7.3.1  True Automatic Mode

In the true automatic mode, you are directed to go to the first port in the testing sequence. As soon as the handheld receiver detects the expected signal, the measurement is recorded in memory, the handheld receiver emits a beep, and you are directed to the next port. Testing can be done without looking at the handheld receiver display for the entire DSX panel; you simply listen for the sound of the successful beep and then plug the patch cord into each successive port. If any port fails during the test, the handheld receiver displays the error and waits for you to press the ENTER/ACCEPT key to save the result. When the error is recorded, the handheld receiver beeps and the next test port is displayed.

1.7.3.2  Manual Prompt Mode

The manual prompt mode is activated by pressing the MENU key four times and using the DISPLAY key to switch to the manual OK PROMPT mode. You are directed to go to the first port in the testing sequence. The handheld receiver displays the expected input port and the detected signal, either OK or faulty, but then waits for you to press the ENTER/ACCEPT key. After you press the key, the handheld receiver records the measurement, beeps, and then prompts for the next port to measure. You must press the ENTER /ACCEPT key for every measurement made, both for OK and for errors, up to 84 times for a full shelf side of DSl signals.

1.7.3.3  Provision the Handheld Receiver and Perform Automatic Mode Testing


Step 1 Turn on the handheld receiver and observe the display. Adjust the settings (DS l/DS3 or OK PROMPT) as needed:

a. To change from DS-1 to DS-3 or from DS-3 to DS-1, press the MENU key once, use the DISPLAY key to change the selection, and the ENTER/ACCEPT key to save the selection.

b. To change the OK PROMPT setting, press the MENU key four times, use the DISPLAY key to change the selection, and the ENTER/ACCEPT key to save the selection

Step 2 To set the audible tone ON, press the MENU key five times, use the DISPLAY key to change the selection, and the ENTER/ACCEPT key to save the selection

Step 3 Insert an appropriate patch cord into the handheld receiver.

Step 4 At this point, the handheld receiver is still in the manual mode. Press the BEGIN TEST key to enter the automatic mode.


Note Pushing the BEGIN TEST key when testing DS-1 wiring starts the automatic test mode at DS-1 port 1 and continues for all 84 ports. To start testing at the DS-1 ports of the second connector pair, ports 29 to 56, push the BEGIN TEST key a second time, and the handheld receiver skips ahead to prompt for the DS I port 29. Pushing BEGIN TEST a third time advances the handheld receiver to start testing at the last DS-1 group, DS 1 port 57.

At any time, you may press EXIT TEST, which terminates the automatic test mode, stores the results thus far, and returns the handheld receiver to the manual mode. This is a convenient feature that, along with the skip ahead feature, allows automatic testing and result storage for a portion of the shelf's connector wiring.


Step 5 Insert the other end of the patch cord into the requested port shown on the display screen.

Step 6 Wait a few seconds for the handheld receiver to detect the signal. For a good measurement in full automatic mode, the handheld receiver displays OK, beeps, and then shows the next port to test.

Step 7 If there is an error, or if the OK PROMPT mode is active, press the ENTER/ACCEPT key to store the result.

Step 8 Move the patch cord to the next port to be tested, as shown in the GOTO message on the display.

Step 9 Repeat Step 5 through Step 8 until all ports are tested.


Note Press the EXIT TEST key to abort the testing at any time. The results to that point are stored in memory, and the handheld receiver reverts to manual mode.



1.7.3.4  View Automatic Mode Test Results During the Test

During the automatic test, there are many test conditions and messages that can appear. A few examples are given in Table 1-2 for DS-1 signal ports. Similar messages appear for the DS-3 ports.

Table 1-2 Automatic Test Mode Results 

Result
Meaning

GOTO A:15 OUT

The next port to be tested is side A, port 15 OUT direction. This prompt is displayed in the upper half of the screen.

DS1 OPEN OR NC

The handheld receiver does not detect any signal. This message is displayed and alternates on the bottom half of the screen.

ENTER TO ACCEPT

The user is asked to press the ENTER/ACCEPT key to record the present test result. This message appears at the bottom half of the screen and alternates with a test result.

OUT DS I A:15 OK

Output cable side A, port 15 for DS-1 is detected correctly. This message alternates on the lower half of the display screen. In true automatic mode, this test result flashes only until the handheld receiver stores the result in memory and then the handheld receiver beeps success and shows the next port in the GOTO message at the top half of the display. In the manual prompt mode, the handheld receiver alternates this message with the ENTER/ACCEPT message until the user pushes the ENTER key.

I A: I 5=>O A: 15

Output port A:15 is detected instead of the expected input port A:15. This test result message alternates on the lower half of the screen. This "error" could occur if the user has not yet moved the test cord from the output port just tested to the next port in sequence, the input port. The printed report for this error would appear as A: 15 WE=>OUT A: 15.

1 B: 17=>O B: 8

DS-1 output side B8 is detected, but the handheld receiver was expecting input group B port 17. This test result message alternates on the lower half of the display. The printed report would record this as B: 17 WE=>OUT B: 8.

O A:18=>OR A:12

DS-1 output A port 12 is detected, but the tip and ring are reversed, and the handheld receiver was expecting output A port 18. This test result message alternates on the lower half of the display. The printed report would record this as A: 18 WE=>OUTR A: 12.

DS 1 SHORT

The message flashes on the lower half of the display to indicate that the Tip and Ring of a DS-1 port are shorted together.

DS I WIRE ERROR

This message flashes on the lower half of the display to indicate the detected signal cannot be diagnosed. There are cases, such as when two or more wires shorted together, where WIRE ERROR is the only indication the handheld receiver can display.

TEST COMPLETE

The automatic mode has finished testing all the ports in the sequence, or the user has halted the testing by pushing the EXIT TEST key.

DISPLAY TO VIEW

When the test has stopped, the user can review the results on the screen by pressing the DISPLAY key.


1.7.4  Retrieving Test Results from Automatic Tests

The results of the last two automated tests can be viewed on the handheld receiver display screen or a computer connected via the handheld receiver's EIA-232 port. Two test reports are stored in the handheld receiver's memory. When a third automatic test is started, the older of the two stored tests is erased. Only the two most recent tests are stored at any time. You may clear memory by pushing BEGIN TEST and then END TEST.

1.7.4.1  Reviewing the Results on the Handheld Receiver Screen

At the conclusion of the automatic test or if you press the EXIT TEST key, the handheld receiver enters the manual mode. Press DISPLAY to recall on the screen the last automated test results. Only "failed" ports are shown. Ports that either pass or are untested do not appear on the screen. Each time the DISPLAY key is pressed, the next test result appears.

1.7.4.2  Sending the Results to a Computer

After the automatic test is complete and the handheld receiver is again in manual mode, the handheld receiver can send the stored results to a computer. The report is in the form of a standard text file.


Step 1 Using the supplied cable with DB9 female connectors at each end, connect the handheld receiver's EIA 232 port to a computer.


Note The handheld receiver operates as a data communications equipment (DCE) device. A straight through DB9 cable is used (pin 2 to pin 2, pin 3 to pin 3, pin 5 to pin 5).


Step 2 Set up the computer's serial port for 9600 baud, 8 data bits, no parity, and one stop bit.


Note See the instructions for your computer for the appropriate software and terminal mode set up.


Step 3 Press the MENU key once. The DSX wiring selection menu appears.

Step 4 Press MENU a second time. The test report menu appears.

Step 5 Press ENTER/ACCEPT to send the test result out the EIA 232 port.

Step 6 Wait for completion, or press EXIT TEST to abort the report. At 9600 baud the report takes only a few seconds to transmit. Either the most recent or both stored reports can be sent.

The handheld receiver returns to manual mode. Each port will have a result, either "OK," an error result, or "UNTESTED." The test reports are stored in non-volatile memory and saved until overwritten by the next test activity; this allows you to power down the handheld receiver while retaining the reports for later transmission to a computer.

There are blank lines in the test report format that you can edit to enter name, time, date, shelf locations, and so on. The test report text file may be edited with any convenient software program after being sent to a computer.


1.7.5  Perform Loop Tests

The TST-DSX card has limited capability for loopback testing with a commercial DS-1 or DS-3 test set. The handheld receiver is not used in the LOOP testing mode.

The TST DSX has passive loop circuitry with no recovery and regeneration of signals. The loop path through the ONS 15310-MA shelf and the TST-DSX card has insertion loss, which reduces the voltage amplitude of a looped signal. The cable length between the DSX wiring panel and the shelf also introduces insertion loss. Depending on the total insertion loss and the receive sensitivity threshold of the test set, it may not always be possible for a given test set to recover the weakened signal at maximum cable lengths.


Step 1 At the ONS 15310-MA shelf, set the TST-DSX card front panel switch to the LOOP position.
The LOOP LED turns steady on and the ACTIVE LED blinks.

Step 2 Connect the DS-1 or DS-3 TX/OUT signal of a commercial test set to the desired input jack at the DSX panel and connect the DSX OUT jack to the commercial test set RCV/IN port.


Note For each signal port, the TST-DSX card loops the IN port to the OUT port. That is, IN port 1 is looped to OUT port 1, port 2 to port 2, and so on. Because of the insertion loss in each looped port, daisy chaining of signals is not supported.



Note The commercial test set should show error free transmission. However, the return signal level is at a reduced level.



1.8  Restore the Database and Default Settings

This section contains troubleshooting procedures for errors that require restoration of software data or the default node setup.

1.8.1  Restore the Node Database

Symptom    One or more nodes are not functioning properly or have incorrect data.

Table 1-3 describes the potential cause of the symptom and the solution.

Table 1-3 Restore the Node Database 

Possible Problem
Solution

Incorrect or corrupted node database.

Complete the applicable procedures in the "Maintain the Node" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


1.9  PC Connectivity Troubleshooting

This section contains information about system minimum requirements, supported platforms, browsers, and Java Runtime environments (JREs) for Software Release 9.1 and Release 9.2, and troubleshooting procedures for Microsoft Windows PC and network connectivity to the ONS 15310-CL or ONS 15310-MA.

Your computer must have a web browser with the correct Java Runtime Environment (JRE) installed for the software release in use. Table 1-4 lists the requirements for Windows PCs, UNIX workstations and MacOS X (Release 9.2 only).

Table 1-4 CTC Computer Requirements 

Area
Requirements
Notes

Processor (PC only)

Pentium 4 processor or equivalent

A faster CPU is recommended if your workstation runs multiple applications or if CTC manages a network with a large number of nodes and circuits.

RAM

512 MB RAM or more (1 GB RAM or more for Release 9.2)

A minimum of 1 GB is recommended if your workstation runs multiple applications or if CTC manages a network with a large number of nodes and circuits.

Hard drive

20 GB hard drive with 100MB of free space required (250 MB of free space required for Release 9.2)

CTC application files are downloaded from the TCC2/TCC2P to your computer. These files occupy around 100MB (250MB to be safer) or more space depending on the number of versions in the network.

Operating System

PC: Windows 2000, Windows XP, Windows Vista SP1, Windows Server 2003 (Windows 7, Windows Server 2008 for Release 9.2)

Workstation: Solaris version 9 or 10

Apple Mac OS X, CTC Needs to be installed using the CacheInstaller available on CCO or the Release CD (for Release 9.2).

Use the latest patch/Service Pack released by the OS vendor. Check with the vendor for the latest patch/Service Pack.

Java Runtime Environment

JRE 5.0 (JRE 1.6 for Release 9.2)

JRE 5.0 (JRE 1.6 for Release 9.2) is installed by the CTC Installation Wizard included on the Cisco ONS 15454 software CD. JRE 5.0 (JRE 1.6 for Release 9.2) provides enhancements to CTC performance, especially for large networks with numerous circuits.

Cisco recommends that you use JRE 5.0 for networks with Software R9.1 (JRE 1.6 for Release 9.2) nodes. If CTC must be launched directly from nodes running software R7.0 or R7.2, Cisco recommends JRE 1.4.2 or JRE 5.0. If CTC must be launched directly from nodes running software R5.0 or R6.0, Cisco recommends JRE 1.4.2.If CTC must be launched directly from nodes running software earlier than R5.0, Cisco recommends JRE 1.3.1_02.

Web browser

PC:Internet Explorer 6.x, 7x (8.x for Release 9.2)

UNIX Workstation: Mozilla 1.7, Netscape 4.76, Netscape 7.x

MacOS-X PC: Safari (for Release 9.2)

For the PC, use JRE 5.0 (JRE 1.6 for Release 9.2) with any supported web browser.

The supported browser can be downloaded from the Web.

Cable

User-supplied CAT-5 straight-through cable with RJ-45 connectors on each end to connect the computer to the ONS 15310-MA SDH directly or though a LAN


1.9.1  Unable to Verify the IP Configuration of Your Microsoft Windows PC

Symptom    When connecting your Microsoft Windows PC to the ONS 15310-CL or ONS 15310-MA, you are unable to successfully ping the IP address of your Microsoft Windows PC to verify the IP configuration.

Table 1-5 describes the potential causes of the symptom and the solutions.

Table 1-5 Unable to Verify the IP Configuration of Your Microsoft Windows PC 

Possible Problem
Solution

The IP address is typed incorrectly.

Verify that the IP address used to ping the Microsoft Windows PC matches the IP address displayed when the Microsoft Windows IP Configuration information is retrieved from the system.

Verify the IP configuration of your Microsoft Windows PC, see the "Verify the IP Configuration of Your Microsoft Windows PC" procedure.

If this procedure is unsuccessful, contact your network administrator for instructions to correct the IP configuration of your Microsoft Windows PC.

The IP configuration of your Microsoft Windows PC is not properly set.


Verify the IP Configuration of Your Microsoft Windows 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 (or Microsoft Windows 98, NT, 2000, and XP), type ipconfig and press the Enter key.

The Microsoft Windows IP configuration information appears, including the IP address, subnet mask, and the default gateway.

Step 4 At the prompt in the DOS window, type ping followed by the IP address shown in the Microsoft Windows IP configuration information.

Step 5 Press the Enter key to execute the command.

If the DOS window displays multiple (usually four) replies, the IP configuration is working properly.

If you do not receive a reply, your IP configuration might not be properly set. Contact your network administrator for instructions to correct the IP configuration of your Microsoft Windows PC.


1.9.2  Browser Login Does Not Launch Java

Symptom    The message "Loading Java Applet" does not appear and the JRE does not launch during the initial login.

Table 1-6 describes the potential causes of the symptom and the solutions.

Table 1-6 Browser Login Does Not Launch Java 

Possible Problem
Solution

The Microsoft Windows PC operating system and browser are not properly configured.

Reconfigure the Microsoft Windows PC operating system java plug-in control panel and the browser settings.

See the "Reconfigure the Microsoft Windows PC Operating System Java Plug-in Control Panel" procedure and the "Reconfigure the Browser" procedure.


Reconfigure the Microsoft Windows PC Operating System Java Plug-in Control Panel


Step 1 From the Microsoft Windows start menu, click Settings > Control Panel.

Step 2 If Java Plug-in Control Panel does not appear, the JRE might not be installed on your Microsoft Windows PC.

a. Run the Cisco ONS 15310-CL or ONS 15310-MA software CD.

b. Open the CD-drive:\Windows\JRE folder.

c. Double-click the j2re-5_0-win icon to run the JRE installation wizard. (respective JRE 1.6 icon for Release 9.2.)

d. Follow the JRE installation wizard steps.

Step 3 From the Microsoft Windows start menu, click Settings > Control Panel.

Step 4 In the Java Plug-in Control Panel window, double-click the Java Plug-in 5.0) icon. (respective JRE 1.6 icon for Release 9.2.)

Step 5 Click the Advanced tab on the Java Plug-in Control Panel.

Step 6 From the Java Run Time Environment menu, select JRE 5.0 in C:\ProgramFiles\JavaSoft\JRE\5.0. (respective JRE 1.6 icon for Release 9.2.)

Step 7 Click Apply.

Step 8 Close the Java Plug-in Control Panel window.


Reconfigure the Browser


Step 1 From the Microsoft Windows Start menu, launch your browser application.

Step 2 If you are using Netscape Navigator:

a. From the Netscape Navigator menu bar, click the Edit > Preferences menus.

b. In the Preferences window, click the Advanced > Proxies categories.

c. In the Proxies window, click the Direct connection to the Internet check box and click OK.

d. From 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 Microsoft Windows 98/ME, C:\ProgramFiles\Netscape\Communicator\cache

For Microsoft Windows NT/2000/XP (Windows Vista/Windows 7 for Release 9.2), C:\ProgramFiles\Netscape\username\Communicator\cache

g. If the Disk Cache Folder field is not correct, click the Choose Folder button.

h. Navigate to the file listed in Step f and click OK.

i. Click OK in 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, Solaris, or UNIX) and click the Use Java 2 v1.4.2 for applet (requires restart) check box (or the Use Java 2 v5.0 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 port" 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 into the ONS 15310-CL or ONS 15310-MA.

Step 7 After completing browser configuration, enable the virus-scanning software on the computer.


1.9.3  Unable to Verify the NIC Connection on Your Microsoft Windows PC

Symptom    When connecting your Microsoft Windows PC to the ONS 15310-CL or ONS 15310-MA, you are unable to verify that the NIC connection is working properly because the link LED is not on or flashing.

Table 1-7 describes the potential causes of the symptom and the solutions.

Table 1-7 Unable to Verify the NIC Connection on Your Microsoft Windows PC 

Possible Problem
Solution

The CAT-5 cable is not plugged in properly.

Confirm that both ends of the cable are properly inserted. If the cable is not fully inserted due to a broken locking clip, the cable should be replaced.

The CAT-5 cable is damaged.

Ensure that the cable is in good condition. If in doubt, use a cable known to be good. Often, cabling is damaged due to pulling or bending.

Incorrect type of CAT-5 cable is being used.

If you are connecting an ONS 15310-CL or ONS 15310-MA directly to your Microsoft Windows laptop/PC or a router, use a straight-through CAT-5 cable. When connecting the node to a hub or a LAN switch, use a crossover CAT-5 cable.

For details on the types of CAT-5 cables, see the "1.12.2.1  Crimp Replacement LAN Cables" procedure.

The NIC is improperly inserted or installed.

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 Microsoft Windows laptop/PC, verify that the NIC is not faulty.

The NIC is faulty.

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 to the network (or any other node), then the NIC might be faulty and needs to be replaced.


1.9.4  Verify Microsoft Windows PC Connection to the Node (Ping)

Symptom    The TCP/IP connection is established and then lost, and a DISCONNECTED alarm appears in CTC.

Table 1-8 describes the potential cause of the symptom and the solution.

Table 1-8 Verify Microsoft Windows PC Connection to ONS 15310-CL or ONS 15310-MA (Ping) 

Possible Problem
Solution

A lost connection between the Microsoft Windows PC and the ONS 15310-CL or ONS 15310-MA.

Use a standard ping command to verify the TCP/IP connection between the Microsoft Windows PC and the ONS 15310-CL or ONS 15310-MA port. A ping command works if the Microsoft Windows PC connects directly to the port or uses a LAN to access the port.

See the "Ping the ONS 15310-CL or ONS 15310-MA" procedure.


Ping the ONS 15310-CL or ONS 15310-MA


Step 1 Open the command prompt:

a. If you are using a Microsoft Windows operating system, from the Start Menu choose Run, type command prompt in the Open field of the Run dialog box, and click OK.

b. If you are using a Sun, Solaris, or UNIX operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.

Step 2 For both the Sun (Solaris, UNIX) and Microsoft operating systems, at the prompt type:

ping ONS-15310-IP-address
 
   

For example:

ping 192.1.0.2
 
   

Step 3 If the workstation has connectivity to the node, 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 node through a LAN, check that the workstation's IP address is on the same subnet as the ONS 15310-CL or ONS 15310-MA.

Step 6 If the ping is not successful and the workstation connects directly to the node, check that the link light on the workstation's NIC is illuminated.


1.10  CTC Operation Troubleshooting

This section contains troubleshooting procedures for CTC login or operation problems.

1.10.1  Unable to Launch CTC Help After Removing Netscape

Symptom    After removing Netscape and running CTC using Internet Explorer, the user is unable to launch the CTC Help and receives an "MSIE is not the default browser" error message.

Table 1-9 describes the potential cause of the symptom and the solution.

Table 1-9 Unable to Launch CTC Help After Removing Netscape 

Possible Problem
Solution

Loss of association between browser and Help files.

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.

Set Internet Explorer as the default browser so that CTC will associate the Help files to the correct browser.

See the "Set Internet Explorer as the Default Browser for CTC" procedure to associate the CTC Help files to the correct browser.


Set Internet Explorer as the Default Browser for CTC


Step 1 Open the Internet Explorer browser.

Step 2 From the menu bar, click Tools > Internet Options. The Internet Options window appears.

Step 3 In the Internet Options window, click the Programs tab.

Step 4 Click the Internet Explorer should check to see whether it is the default browser check box.

Step 5 Click OK.

Step 6 Exit any and all open and running CTC and Internet Explorer applications.

Step 7 Launch Internet Explorer and open another CTC session. You should now be able to access the CTC Help.


1.10.2  Unable to Change Node View to Network View

Symptom    Logging into CTC session, 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.

Table 1-10 describes the potential cause of the symptom and the solution.

Table 1-10 Unable to Change Node View to Network View

Possible Problem
Solution

The browser stalls when downloading files from a port because the display requires more memory for the graphical user interface (GUI) environment variables.

Reset the system or user CTC_HEAP environment variable to increase the memory limits.

See the "Set the CTC_HEAP and CTC_MAX_PERM_SIZE_HEAP Environment Variables for Microsoft 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 Microsoft 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 Microsoft 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 browser applications.

Step 2 In the user shell window, set the environment variables to increase the heap size.

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.10.3  Browser Stalls When Downloading CTC JAR Files from port

Symptom    The browser stalls or hangs when downloading a CTC Java archive (JAR) file from the port.

Table 1-11 describes the potential cause of the symptom and the solution.

Table 1-11 Browser Stalls When Downloading JAR File from Port 

Possible Problem
Solution

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.

Disable the VirusScan Download Scan feature. See the "Disable the VirusScan Download Scan" procedure.


Disable the VirusScan Download Scan


Step 1 From the Microsoft Windows Start menu, choose Programs > Network Associates > VirusScan Console.

Step 2 Double-click the VShield icon listed in the VirusScan Console dialog box.

Step 3 Click Configure on the lower part of the Task Properties window.

Step 4 Click the Download Scan icon on the left of the System Scan Properties dialog box.

Step 5 Uncheck the Enable Internet download scanning check box.

Step 6 Click Yes when the warning message appears.

Step 7 Click OK on the System Scan Properties dialog box.

Step 8 Click OK on the Task Properties window.

Step 9 Close the McAfee VirusScan window.


1.10.4  CTC Does Not Launch

Symptom    CTC does not launch; usually an error message appears before the login window appears.

Table 1-12 describes the potential cause of the symptom and the solution.

Table 1-12 CTC Does Not Launch 

Possible Problem
Solution

The Netscape browser cache might point to an invalid directory.

Redirect the Netscape cache to a valid directory. See the "Redirect the Netscape Cache to a Valid Directory" procedure.


Redirect the Netscape Cache to a Valid Directory


Step 1 Launch Netscape.

Step 2 From the Edit menu, choose Preferences.

Step 3 In the Category column on the left side, expand Advanced and select the Cache tab.

Step 4 Change your disk cache folder to point to the cache file location.

The cache file location is usually C:\ProgramFiles\Netscape\Users\yourname\cache. The yourname segment of the file location is often the same as the user name.


1.10.5  Sluggish CTC Operation or Login Problems

Symptom    You experience sluggish CTC operation or have problems logging into CTC.

Table 1-13 describes the potential cause of the symptom and the solution.

Table 1-13 Sluggish CTC Operation or Login Problems 

Possible Problem
Solution

The CTC cache file might be corrupted or might need to be replaced.

Delete the CTC cache file. This operation forces the ONS 15310-CL or ONS 15310-MA to download a new set of JAR files to your computer hard drive. See the "Delete the CTC Cache File Automatically" procedure if you want to temporarily delete the cache stored from another CTC session, or the "Delete the CTC Cache File Manually" procedure if you want to delete the Java archive (JAR) files associated with an older JRE version.

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 Microsoft 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 the CTC cache might cause any CTC sessions running on this system to behave in an unexpected manner.


Step 1 Enter an ONS 15310-CL or ONS 15310-MA IP address in 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 Microsoft Windows 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-10 shows the Delete CTC Cache window.

Figure 1-10 Deleting the CTC Cache

Delete the CTC Cache File Manually


Caution All running sessions of CTC must be halted before deleting the CTC cache. Deleting the CTC cache might cause any CTC running on this system to behave in an unexpected manner.


Step 1 To delete the JAR files manually, from the Microsoft Windows Start menu choose Search > For Files or Folders.

Step 2 Enter ctc*.jar or cms*.jar in the Search for Files or Folders Named field on the Search Results dialog box and click Search Now.

Step 3 Click the Modified column on the Search Results dialog box to find the JAR files that match the date when you downloaded the files from the port.

Step 4 Highlight the files and press the keyboard Delete key.

Step 5 Click Yes in the Confirm dialog box.


1.10.6  Node Icon is Gray on CTC Network View

Symptom    The CTC network view shows one or more node icons as gray in color and without a node name.

Table 1-14 describes the potential causes of the symptom and the solutions.

Table 1-14 Node Icon is Gray on CTC Network View 

Possible Problem
Solution

Different CTC releases are not recognizing each other. Usually accompanied by an INCOMPATIBLE-SW alarm.

Correct the core version build as described in the "Different CTC Releases Do Not Recognize Each Other" section.

A username/password mismatch. Usually accompanied by a NOT-AUTHENTICATED condition.

Correct the username and password as described in the "Username or Password Does Not Match the Port Information" section.

No IP connectivity between nodes. Usually accompanied by Ethernet-specific alarms.

Verify the Ethernet connections as described in the "Cisco Transport Controller Operation" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

A lost DCC connection. Usually accompanied by a procedural error mismatch (EOC) alarm.

Clear the EOC alarm and verify the DCC connection as described in the "EOC" alarm on page 2-54.


1.10.7  Java Runtime Environment Incompatible

Symptom    The CTC application does not run properly.

Table 1-15 describes the potential cause of the symptom and the solution.

Table 1-15 Java Runtime Environment Incompatible 

Possible Problem
Solution

The compatible Java 2 JRE is not installed.

The Java 2 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.

Note 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 software CD and on the Cisco ONS 15310-CL and ONS 15310-MA documentation CD. See the "Launch CTC to Correct the Core Version Build" procedure.

Note If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible with all of the releases that you are running. See Table 1-16.



Note CTC will notify you if an older version JRE is running on your Microsoft Windows PC or UNIX workstation.


Launch CTC to Correct the Core Version Build


Step 1 Exit the current CTC session and completely close the browser.

Step 2 Start the browser.

Step 3 Type the node IP address of the node that reported the alarm. This can be the original IP address you logged in with or an IP address other than the original.

Step 4 Log into CTC. The browser downloads the JAR file from CTC.


1.10.8  Different CTC Releases Do Not Recognize Each Other

Symptom    Different CTC releases on the same network do not recognize each other.

Table 1-16 describes the potential cause of the symptom and the solution.

Table 1-16 Different CTC Releases Do Not Recognize Each Other 

Possible Problem
Solution

The software loaded on the connecting workstation and the software on the ONS 15310-CL or ONS 15310-MA are incompatible.

This occurs when the port software is upgraded but the Microsoft Windows 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. See 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 earlier and then attempt to log into another ONS node in the network running a later CTC core version, the earlier version node does not recognize the new node.

Note This situation is often accompanied by the INCOMPATIBLE-SW alarm.


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 In the Node Name field, type the ONS 15310-CL or ONS 15310-MA 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 port.


1.10.9  Username or Password Does Not Match the Port Information

Symptom    A mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm.

Table 1-17 describes the potential causes of the symptom and the solutions.

Table 1-17 Username or Password Does Not Match the Port Information 

Possible Problem
Solution

The username or password entered does not match the information stored in the port.

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 node, enter the CISCO15 user name in capital letters and click Login and use the password "otbu+1," which is case-sensitive.

See the "Verify Correct Username and Password" procedure.

If the node has been configured for Remote Authentication Dial In User Service (RADIUS) authentication, the username and password are verified against the RADIUS server database rather than the security information in the local node database. For more information about RADIUS security, refer to the "Security" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.


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 Contact the Cisco TAC at http://www.cisco.com/tac or 1-800-553-2447 to have them enter your system and create a new user name and password.


1.10.10  Superuser Password Needs to Be Reset

Symptom    The Superuser password has been lost or compromised.

Table 1-18 describes the potential cause of the symptom and the solution.

Table 1-18 Superuser Password Needs to Be Reset

Possible Problem
Solution

A security breach or record-keeping error has occurred.

Reset the node to the default Superuser UID and password combination using the using the password recovery cable.
Refer to the document, Recovering the Cisco ONS 15310, ONS 15327, and ONS 15454 Password.


1.10.11  No IP Connectivity Exists Between Nodes

Symptom    The nodes have a gray icon that is usually accompanied by alarms.

Table 1-19 describes the potential cause of the symptom and the solution.

Table 1-19 No IP Connectivity Exists Between Nodes 

Possible Problem
Solution

Lost Ethernet connection

Usually, this condition is accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in Chapter 8, "CTC Network Connectivity," of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.


1.10.12  DCC Connection Lost

Symptom    The node is usually accompanied by alarms and the nodes in the network view have a gray icon.

Table 1-20 describes the potential cause of the symptom and the solution.

Table 1-20 DCC Connection Lost 

Possible Problem
Solution

A lost DCC connection

Usually, this condition is accompanied by an EOC alarm. Clear the EOC alarm and verify the DCC connection as described in the "EOC" alarm on page 2-54.


1.10.13  "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.

Table 1-21 describes the potential cause of the symptom and the solution.

Table 1-21 "Path in Use" Error When Creating a Circuit 

Possible Problem
Solution

Another user has already selected the same source port to create another circuit

CTC does not remove a card or port from the available list until a circuit is completely provisioned. If two users simultaneously select the same source port to create a circuit, the first user to complete circuit provisioning gets use of the port. The other user gets the "Path in Use" error.

See the "Cancel the Circuit Creation and Start Over" procedure.


Cancel the Circuit Creation and Start Over


Step 1 Cancel the circuit creation:

a. Click Cancel.

b. Click Back until you return to the initial circuit creation window.

Step 2 Check the list of available ports. The previously selected port no longer appears in the available list because it is now part of a provisioned circuit.

Step 3 Select a different available port and begin the circuit creation process.


1.10.14  Calculate and Design IP Subnets

Symptom    You cannot calculate or design IP subnets on the ONS 15310-CL or ONS 15310-MA.

Table 1-22 describes the potential cause of the symptom and the solution.

Table 1-22 Calculate and Design IP Subnets 

Possible Problem
Solution

The IP capabilities of the ONS 15310-CL and ONS 15310-MA require specific calculations to properly design IP subnets.

Cisco provides a online tool to calculate and design IP subnets. Go to http://www.cisco.com/cgi-bin/Support/IpSubnet/home.pl. For information about ONS 15310-CL or ONS 15310-MA IP capability, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.


1.11  Circuits and Timing

This section provides solutions to circuit creation and reporting errors, as well as common timing reference errors and alarms.

1.11.1  Circuit Transitions to Partial Status

Symptom    An automatic or manual transition of another state results in the OOS-PARTIAL state; at least one of the connections in the circuit is in IS-NR state and at least one other connection in the circuit is in IS,AINS, OOS,MT, or OOS_AINS state.

Table 1-23 describes the potential causes of the symptom and the solutions.

Table 1-23 Circuit in Partial Status 

Possible Problem
Solution

During a manual transition, CTC cannot communicate with one of the nodes or one of the nodes is on a version of software that does not support the new state model.

Repeat the manual transition operation. If the Partial status persists, determine which node in the circuit is not changing to the desired state. See the "View the State of Circuit Nodes" procedure.

Log onto the circuit node that did not change to the desired state and determine the version of software. Refer to the release-specific software upgrade guide for software upgrade procedures.

During an automatic transition, some path-level defects and/or alarms were detected on the circuit.

Determine which node in the circuit is not changing to the desired state. Refer to the "View the State of Circuit Nodes" procedure.

Log into 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 the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for procedures to clear alarms and change circuit configuration settings.

Resolve and clear the defects and alarms on the circuit node and verify that the circuit transitions to the desired state.

One end of the circuit is not properly terminated.


View the State of Circuit Nodes


Step 1 Click the Circuits tab.

Step 2 From the Circuits tab list, select the circuit with the OOS-PARTIAL status condition.

Step 3 Click Edit. The Edit Circuit window appears.

Step 4 In the Edit Circuit window, click the State tab.

The State tab window lists the Node, CRS End A, CRS End B, and CRS State for each of the nodes in the circuit.


1.11.2  Circuits Remain in PARTIAL Status

Symptom    Circuits remain in the PARTIAL status.

Table 1-24 describes the potential cause of the symptom and the solution.

Table 1-24 Circuits Remain in PARTIAL Status

Possible Problem
Solution

The MAC address changed.

Repair the circuits. Refer to the "Manage Circuits" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for instructions.


1.11.3  AIS-V on Unused 15310-CL-CTX Card VT Circuits

Symptom    An incomplete circuit path causes an alarm indications signal (AIS).

Table 1-25 describes the potential cause of the symptom and the solution.

Table 1-25 AIS-V on Unused 15310-CL-CTX Card VT Circuits 

Possible Problem
Solution

The port on the reporting node is in-service but a node upstream on the circuit does not have an OC-N port in service.

An AIS-V indicates that an upstream failure occurred at the VT layer. AIS-V alarms also occur on VT circuits that are not carrying traffic and on stranded bandwidth.

Perform the "Clear AIS-V on Unused Controller Card VT Circuits" procedure.


Clear AIS-V on Unused Controller Card VT Circuits


Step 1 Determine the affected port.

Step 2 Record the node ID, slot number, port number, and 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 DeleteMe.

Step 6 Display the controller card (15310-CL-CTX or CTX2500) in CTC card view. Click the Maintenance > DS1 tabs.

Step 7 Locate the VT that is reporting the alarm (for example, DS3 #2, DS1 #13).

Step 8 From the Loopback Type list, choose Facility 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.

Step 11 Click Yes in the Delete Confirmation dialog box.

Step 12 In node view, double-click the controller card (15310-CL-CTX or CTX2500). The card view appears.

Step 13 Click the Maintenance > DS1 tabs.

Step 14 Locate the VT in the Facility Loopback list.

Step 15 From the Loopback Type list, choose None and then click Apply.

Step 16 Click the Alarm tab and verify that the AIS-V alarms have cleared.

Step 17 Repeat this procedure for all the AIS-V alarms on the controller.


1.11.4  Circuit Creation Error with VT1.5 Circuit

Symptom    You might receive an "Error while finishing circuit creation. Unable to provision circuit. Unable to create connection object at node-name" message when trying to create a VT1.5 circuit in CTC.

Table 1-26 describes the potential causes of the symptom and the solutions.

Table 1-26 Circuit Creation Error with VT1.5 Circuit 

Possible Problem
Solution

You might have run out of bandwidth on the VT cross-connect matrix at the node indicated in the error message.

The ONS 15310-CL matrix has a maximum capacity of 336 bidirectional VT1.5 cross-connects. The ONS 15310-MA capacity is 1,064.


1.11.5  OC-3 and DCC Limitations

Symptom    There are limitations to OC-3 and DCC usage.

Table 1-27 describes the potential cause of the symptom and the solution.

Table 1-27 OC-3 and DCC Limitations 

Possible Problem
Solution

OC-3 and DCC have limitations for the system.

For an explanation of OC-3 and DCC limitations, refer to the "DCC Tunnels" section in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


1.11.6  ONS 15310-CL or ONS 15310-MA Switches Timing Reference

Symptom    Timing references switch when one or more problems occur.

Table 1-28 describes the potential causes of the symptom and the solutions.

Table 1-28 ONS 15310-CL or ONS 15310-MA Switches Timing Reference 

Possible Problem
Solution

The optical or building integrated timing supply (BITS) input is receiving loss of signal (LOS), loss of frame (LOF), or AIS alarms from its timing source.

The node internal clock operates at a Stratum 3 level of accuracy. This gives the node 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 per day, including temperature.

Node free-running synchronization relies on the Stratum 3 internal clock.

Use a higher quality Stratum 1 or Stratum 2 timing source. This results in fewer timing slips than a lower quality Stratum 3 timing source.

The optical or BITS input is not functioning.

Synchronization status message (SSM) is set to Don't Use for Synchronization (DUS).

SSM indicates a Stratum 3 or lower clock quality.

The input frequency is off by more than 15 ppm.

The input clock wanders and has more than three slips in 30 seconds.

A bad timing reference existed for at least two minutes.


1.11.7  Holdover Synchronization Alarm

Symptom    The clock is running at a different frequency than normal and the holdover synchronization (HLDOVRSYNC) alarm appears.

Table 1-29 describes the potential cause of the symptom and the solution.

Table 1-29 Holdover Synchronization Alarm 

Possible Problem
Solution

The last reference input has failed.

The clock is running at the frequency of the last valid reference input. This alarm is raised when the last reference input fails. See the "HLDOVRSYNC" alarm on page 2-78 for a detailed description of this alarm.

Note The ONS 15310-CL and ONS 15310-MA support holdover timing per Telcordia GR-4436 when provisioned for external (BITS) timing.


1.11.8  Free-Running Synchronization Mode

Symptom    The clock is running at a different frequency than normal and the free-running synchronization(FRNGSYNC) alarm appears.

Table 1-30 describes the potential cause of the symptom and the solution.

Table 1-30 Free-Running Synchronization Mode 

Possible Problem
Solution

No reliable reference input is available.

The clock is using the internal oscillator as its only frequency reference. This occurs when no reliable, prior timing reference is available. See the "FRNGSYNC" alarm on page 2-71 for a detailed description of this alarm.


1.11.9  Daisy-Chained BITS Not Functioning

Symptom    You are unable to daisy-chain the BITS.

Table 1-31 describes the potential cause of the symptom and the solution.

Table 1-31 Daisy-Chained BITS Not Functioning 

Possible Problem
Solution

Daisy-chaining BITS is not supported on the system.

Daisy-chaining BITS causes additional wander buildup in the network and is therefore not supported. Instead, use a timing signal generator to create multiple copies of the BITS clock and separately link them to each node.


1.11.10  Blinking STAT LED after Installing a Card

Symptom    After installing a card, the STAT LED blinks continuously for more than 60 seconds.

Table 1-32 describes the potential cause of the symptom and the solution.

Table 1-32 Blinking STAT LED on Installed Card 

Possible Problem
Solution

The card cannot boot because it failed the Power On Shelf Test (POST) diagnostics.

The blinking STAT LED indicates that POST diagnostics are being performed. 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-BOOT alarm is raised against the slot number with an "Equipment Fails To Boot" description. Check the alarm tab for this alarm to appear for the slot where the card is installed.

To attempt recovery, remove and reinstall the card and observe the card boot process. If the card fails to boot, replace the card.


1.12  Fiber and Cabling

This section explains problems typically caused by cabling connectivity errors. It also includes instructions for crimping CAT-5 cable and lists the optical fiber connectivity levels.

1.12.1  Bit Errors Appear for a Traffic Card

Symptom    A traffic card has multiple bit errors.

Table 1-33 describes the potential cause of the symptom and the solution.

Table 1-33 Bit Errors Appear for a Line Card 

Possible Problem
Solution

Faulty cabling or low optical-line levels.

Troubleshoot cabling problems using the "Network Troubleshooting Tests" section. Troubleshoot low optical levels using procedures in the "Faulty Fiber-Optic Connections" section.

Note Bit errors on line (traffic) ports 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. Use a test set whenever possible because the cause of the errors could be external cabling, fiber, or external equipment connecting to the node.


1.12.2  Faulty Fiber-Optic Connections

Symptom    A line card has multiple SONET alarms and/or signal errors.

Table 1-34 describes the potential causes of the symptom and the solutions.

Table 1-34 Faulty Fiber-Optic Connections 

Possible Problem
Solution

Faulty fiber-optic connections.

Faulty fiber-optic connections can be the source of SONET alarms and signal errors. See the "Verify Fiber-Optic Connections" procedure.

Faulty CAT-5 cables.

Faulty CAT-5 cables can be the source of SONET alarms and signal errors. See the "1.12.2.1  Crimp Replacement LAN Cables" procedure.



Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056

Warning Class 1 laser product. Statement 1008

Warning Laser radiation presents an invisible hazard, so personnel should avoid exposure to the laser beam. Personnel must be qualified in laser safety procedures and must use proper eye protection before working on this equipment. Statement 300

Verify Fiber-Optic Connections


Step 1 Ensure that a single-mode fiber connects to the ONS 15310-CL or ONS 15310-MA Small form-factor Pluggable (SFP).

SM or SM Fiber should be printed on the fiber span cable. ONS 15310-CL and ONS 15310-MA ports 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 Rx end of the suspect fiber.

b. Connect the receive 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 optical port being tested (either 1310 nm or 1550 nm).

e. Verify that the power level falls within the range specified for the card; refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual for information.

Step 4 If the power level falls below the specified range:

a. Clean or replace the fiber patchcords. Clean the fiber according to site practice or, if none exists, follow the procedure in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. If possible, do this for the OC-N port you are working on and the far-end ONS 15310-CL or ONS 15310-MA.

b. Clean the optical connectors on the port. Clean the connectors according to site practice or, if none exists, follow the procedure in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. If possible, do this for the card you are working on and the far-end node.

c. 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 optical port failed. Complete the following steps:

a. Check that the Tx and Rx fibers are not reversed. LOS and EOC alarms normally accompany reversed Tx and Rx fibers. Switching reversed Tx and Rx fibers clears the alarms and restores the signal.

b. Clean or replace the fiber patchcords. Clean the fiber according to site practice or, if none exists, follow the procedure in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. If possible, do this for the card you are working on and the far-end card.

c. Retest the fiber power level.


Tip Most fiber has text printed on only one of the two fiber strands. Use this to identify which fiber is connected to Tx and which fiber is connected to Rx.



1.12.2.1  Crimp Replacement LAN Cables

You can crimp your own LAN cables for use with the system. Use #22 or #24 AWG shielded wire with RJ-45 connectors and a crimping tool.

Use a cross-over cable when connecting an ONS 15310-CL or ONS 15310-MA to a hub, LAN modem, or switch, and use a LAN cable when connecting a node to a router or workstation.

Figure 1-11 shows the layout of an RJ-45 connector.

Figure 1-11 RJ-45 Pin Numbers

Figure 1-12 shows the layout of a LAN cable.

Figure 1-12 LAN Cable Layout

Table 1-35 shows LAN cable pinouts.

Table 1-35 LAN Cable Pinout 

Pin
Color
Pair
Name
Pin

1

White/orange

2

Transmit Data +

1

2

Orange

2

Transmit Data -

2

3

White/green

3

Receive Data +

3

4

Blue

1

4

5

White/blue

1

5

6

Green

3

Receive Data -

6

7

White/brown

4

7

8

Brown

4

8


Figure 1-13 shows the layout of a cross-over cable.

Figure 1-13 Cross-Over Cable Layout

Table 1-36 shows cross-over cable pinouts.

Table 1-36 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  Power and LED Tests

This section provides symptoms and solutions for power supply problems, power consumption, and LED indicators.

1.13.1  Power Supply Problems

Symptom    Loss of power or low voltage, resulting in a loss of traffic and causing the LCD clock to reset to the default date and time.

Table 1-37 describes the potential causes of the symptom and the solutions.

Table 1-37 Power Supply Problems 

Possible Problem
Solution

Loss of power or low voltage

See Chapter 2 "Alarm Troubleshooting," for information about specific power alarms. Procedures for installing power supply and cables are located in the "Install Hardware" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Power supplies may be disconnected by reversing the appropriate procedure (for AC or DC power).

Note The ONS 15310-CL and ONS 15310-MA require a constant source of DC power to properly function. Input power is -48 VDC. Power requirements range from -42 VDC to -57 VDC.

Note A newly installed ONS 15310-CL or ONS 15310-MA that is not properly connected to its power supply does not operate. Power problems can be confined to a specific node or can affect several pieces of equipment on the site.

Note A loss of power or low voltage can result in a loss of traffic and causes the LCD clock on the node to default to January 1, 1970, 00:04:15. To reset the clock, in node view click the Provisioning > General tabs and change the Date and Time fields.

Improperly connected power supply



Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030

Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94

Caution Operations that interrupt power supply or short the power connections to the system are service-affecting.

1.13.2  Power Consumption for Node and Cards

Symptom    You are unable to power up a node or the cards in a node.

Table 1-38 describes the potential cause of the symptom and the solution.

Table 1-38 Power Consumption for Node and Cards 

Possible Problem
Solution

Improper power supply.

Refer to power information in the "Install Hardware" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


1.13.3  Lamp Tests for Card LEDs

Symptom    Optical (OC-N) ports LEDs do not light, or you are unsure whether the LEDs are working properly.

The LED lamp test determines whether card-level LEDs are operational. For optical ports, this test also causes port-level LEDs to turn on. For Ethernet cards, only card-level LEDs light. For these cards, port-level LEDs can be compared to the given guidelines to determine whether they are working correctly.

Optical port LEDs light during the lamp test. Ethernet cards only illuminate card-level LEDs during the test. Table 1-39 describes the possible problem and the solution for optical ports.

Table 1-39 Lamp Test for Optical and Electrical Card LEDs 

Possible Problem
Solution

Faulty optical port LED

A lamp test verifies that all the port LEDs work. Run this diagnostic test as part of the initial system turn-up, a periodic maintenance routine, or any time you question whether an LED is in working order.

Complete the "Verify Card LED Operation" procedure.


Verify Card LED Operation


Step 1 In CTC, click the Maintenance > Diagnostic tabs.

Step 2 Click Lamp Test.

Step 3 Watch to make sure all the port LEDs illuminate as previously noted for several seconds.

Step 4 Click OK on the Lamp Test Run dialog box.

With the exceptions previously described, if an OC-N or DS-N LED does not light up, the LED is faulty. Return the defective card to Cisco through the RMA process. Contact Cisco TAC at http://www.cisco.com/tac or 1-800-553-2447.


1.13.4  Retrieve Tech Support Logs Button

When you click the Retrieve Tech Support Logs button in the Diagnostics tab of the Maintenance window, CTC retrieves system data that a Retrieve or higher level user can off-load 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 procedure to off-load the diagnostics file.


Note In addition to the machine-readable diagnostics file, the ONS 15454 stores an audit trail of all system events such as user log-ins, remote log-ins, configuration, and changes. This audit trail is considered a record-keeping feature rather than a troubleshooting feature. Information about the feature is located in the "Maintain the Node" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.


Off-Load the Diagnostics File


Note The diagnostics operation is performed at a shelf level. Only single-node-related diagnostic information can be downloaded at a time.


The diagnostic files retrieved by CTC depends on the user privilege levels. Table 1-40 lists the user privilege levels and the diagnostic retrieval operations they can perform.

Table 1-40 Diagnostic Files Retrieved Based on User Privilege 

User Privilege Level
Diagnostic File Retrieval Operation

Retrieve

Export the unfiltered alarm table contents

Export the unfiltered conditions table contents

Export the unfiltered history table contents

Export the inventory table contents

CTC Dump Diagnostics log

Maintenance

All Retrieve level access operations

Save the node database

Provisioning

All Maintenance level access operations

Retrieve and save the node-level diagnostics report1

Export the audit table contents2

Superuser

All Provisioning level access operations

Retrieve and save the node-level diagnostics report

Export the audit table contents

1 If secure mode is not set on the node.

2 If the NODE.security.grantPermission.RetrieveAuditLog NE Default is set to "Provisioning."



Step 1 In the node view, click the Maintenance > Diagnostic tabs.

Step 2 Click Retrieve Tech Support Logs in the Controller area.

Step 3 In the Select a Filename for the Tech Support Logs Zip Archive dialog box, add the diagnostics file name in the format TechSupportLogs_<node_name>.zip by default. Substitute the last 20 alphanumeric characters of the node name for <node_name>. Navigate to the directory (local or network) where you want to save the file.

A message appears asking you if you want to overwrite any existing diagnostics file in the selected directory.

Step 4 Click Save.

CTC performs the diagnostic tasks and writes the diagnostic files in a folder named TechSupportLogs_<node_name> under the location selected in Step 3. After all the diagnostic files are written to the TechSupportLogs_<node_name> folder, CTC archives the retrieved diagnostic files as TechSupportLogs_<node_name>.zip. CTC deletes the TechSupportLogs_<node_name> folder after the archiving process is successfully completed. CTC retains this folder if the archiving process fails. The retrieved diagnostic files can be accessed in the TechSupportLogs_<node_name> folder.

A progress bar indicates the percentage of the file that is being saved. The Save Tech Support Logs Completed dialog box appears when the file is saved. CTC logs any error during the retrieval and archiving of diagnostics file to the CTC Alerts Log.

Table 1-41 lists the diagnostic files retrieved by CTC.

Table 1-41 List of Diagnostic Files 

Diagnostic File
Diagnostic File Content

AlarmTableLog.html

Alarm Table export

HistoryTableLog.html

Alarm Table export

ConditionsTableLog.html

Conditions Table export

InventoryTableLog.html

Inventory Table export

AuditTableLog.html

Audit Table export

CTCDumpDiagLog.txt

Audit Table export

NodeDiagnostics.bin

NodeDiagnostics.gz

OBFLDiagnostics.bin

OBFLDiagnostics.bin

NodeDatabaseBackup.bin

Database backup

TechSupportLogs_<node_name>.zip

Zip archive of all the diagnostics file


Step 5 Click OK.