Table of Contents

General Troubleshooting

This chapter provides procedures for troubleshooting the most common problems encountered when operating a Cisco ONS 15454 SDH. To troubleshoot specific ONS 15454 SDH alarms, see "Alarm Index." If you cannot find what you are looking for in this chapter or "Alarm Index," contact the Cisco Technical Assistance Center (TAC) at 1-800-553-2447 or login to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to obtain more information.

This chapter begins with the following sections on network problems:

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

2.1 Network Troubleshooting Tests

Use loopbacks and hairpins to test newly created circuits before running live traffic or to logically locate the source of a network failure. All ONS 15454 SDH line (traffic) cards, except Ethernet cards, allow loopbacks and hairpins.

Caution   On multiport STM-N cards, a loopback applies to the entire card and not an individual circuit. Exercise caution when using loopbacks on an STM-N card carrying live traffic.

A facility loopback tests the line interface unit (LIU) of a card, the FMEC, and related cabling. After applying a facility loopback on a card, use a test set to run traffic over the loopback. A successful facility loopback eliminates the LIU, FMEC, or cabling as the potential cause of a network problem. Figure 2-1 shows a facility loopback on a E3-12 card.

Figure 2-2 shows a facility loopback on a STM-N card.

Caution   Before performing a facility loopback on an STM-N card, make sure the card contains at least two SDCC paths to the node where the card is installed. A second SDCC path provides a non-looped path to log into the node after the loopback is applied, thus enabling you to remove the facility loopback. Ensuring a second SDCC is not necessary if you are directly connected to the ONS 15454 SDH containing the loopback OC-N.

A terminal loopback tests a circuit path as it passes through the cross-connect card (XC10G) and as it loops back from the card being tested. Figure 2-3 shows a terminal loopback on an STM-N card. The test-set traffic comes in on the E3-12 card and goes through the cross-connect card to the STM-N card. The terminal loopback on the STM-N card turns the signal around before it reaches the LIU and sends it through the cross-connect card to the E3-12 card. This test verifies that the cross-connect card and circuit paths are valid, but does not test the LIU on the STM-N card.

To test the LIU on an STM-N card, connect an optical test set to the STM-N card ports and perform a facility loopback or use a loopback or hairpin on a card that is farther along the circuit path. Figure 2-4 shows a terminal loopback on an E3-12 card. The test-set traffic comes in on the STM-N card and goes through the cross-connect card to the E3-12 card. The terminal loopback on the E3-12 card turns the signal around before it reaches the LIU and sends it through the cross-connect card to the STM-N card. This test verifies that the cross-connect card and circuit paths are valid, but does not test the LIU on the E3-12 card.

A hairpin circuit brings traffic in and out on an E3-12 port rather than sending the traffic onto the STM-N card. A hairpin loops back only the specific E3 circuit and does not cause an entire STM-N port to loop back, thus preventing a drop of all traffic on the STM-N port. The hairpin allows you to test a circuit on nodes running live traffic.

2.2 Identify Points of Failure on a Circuit Path

Facility loopbacks, terminal loopbacks, and hairpin circuits are often used together to test the circuit path through the network or to logically isolate a fault. Performing a network test at each point along the circuit path systematically eliminates possible points of failure. The example in this section tests an E3-12 circuit on a two-node MS-SPRing. Using a series of facility loopbacks, terminal loopbacks, and hairpins, the path of the circuit is traced and the possible points of failure eliminated.

A logical progression of four network test procedures apply to this scenario:

---

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 E3-12 card

2. A hairpin on the source-node E3-12 card

3. A terminal loopback to the destination-node E3-12 card

4. A facility loopback to the destination E3-12 card

---

Note    All loopback tests require on-site personnel.

---

2.2.1 Perform a Facility Loopback on a Source E3-12 Card

The facility loopback test is performed on the source card in the network circuit, in this example, the source traffic card in the source node. Completing a successful facility loopback on this card eliminates the cabling, the E3-12 card, and the FMEC as possible failure points. Figure 2-6 shows an example of a facility loopback.

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

Procedure: Create the Facility Loopback on the Source E3-12 Card

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

---

Note    It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.

---

Proceed to the "Test the Facility Loopback Circuit" section.

Procedure: Test the Facility 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:

Step 4   If the test set indicates a faulty circuit, the problem may be a faulty E3-12 card, faulty cabling from the E3-12 card to the DSx panel or the FMEC, or a faulty FMEC.

Proceed to the "Test the E3-12 Cabling" section.

Procedure: Test the E3-12 Cabling

Step 2   If a known-good cable is not available, test the suspect cable with a test set. Remove the suspect cable from the DSx panel or the FMEC and connect the cable to the transmit (Tx) and receive (Rx) terminals of the test set. Run traffic to determine whether the cable is good or suspect.

Step 3   Resend test traffic on the loopback circuit with a known-good cable installed.

Step 4   If the test set indicates a good circuit, the problem was probably the defective cable.

Step 5   If the test set indicates a faulty circuit, the problem may be a faulty card or a faulty FMEC.

Proceed to the "Test the E3-12 Card" section.

Procedure: Test the E3-12 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. Consult "Maintenance," for information.

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.

Step 4   If the test set indicates a faulty circuit, the problem may be a faulty FMEC.

Proceed to the "Test the FMEC Card" section.

Procedure: Test the FMEC 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. Consult "Maintenance," for information.

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

Step 3   If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.

Step 4   If the test set indicates a good circuit, the problem was probably the defective FMEC card.

Proceed to the "Perform a Hairpin on a Source Node" section.

2.2.2 Perform a Hairpin on a Source Node

The hairpin circuit test is performed on the cross-connect card in the network circuit. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through the card eliminates the possibility that the cross-connect card is the cause of the faulty circuit. Figure 2-7 shows an example of a hairpin.

Note   The ONS 15454 SDH does not support simplex operation on the cross-connect card. Each ONS 15454 SDH requires Two XC10G cards.

Procedure: Create the Hairpin on the Source Node

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

Step 3   Confirm that the newly created circuit appears with a direction column indicating that this circuit is one-way.

Proceed to the "Test the Hairpin Circuit" section.

Procedure: Test the Hairpin 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.

Step 4   If the test set indicates a faulty circuit, there may be a problem with the cross-connect card.

Proceed to the "Test the Alternate Cross-Connect Card" section.

Procedure: Test the Alternate Cross-Connect Card

Step 2   Do a manual switch (side switch) of the cross-connect cards before retesting the loopback circuit:

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

---

Note    After the active cross-connect goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.

---

Step 3   Resend test traffic on the loopback circuit.

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

Step 4   If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem.

Step 5   If the test set indicates a good circuit, the problem may be a defective card.

To confirm a defective original cross-connect card, proceed to the "Retest the Original Cross-Connect Card" section.

Procedure: Retest the Original Cross-Connect Card

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.

Step 4   If the test set indicates a good circuit, the cross-connect card may have had a temporary problem that was cleared by the side switch.

2.2.3 Perform a Terminal Loopback on a Destination E3-12 Card

This test is a terminal loopback performed on the fourth traffic card in the circuit, in the following example the E3-12 card in the destination node is the test card. First, create a bidirectional circuit that starts on the source node E3-12 port and terminates on the destination node E3-12 port. Then, proceed with the terminal loopback test. Completing a successful terminal loopback to a destination node E3-12 card verifies that the circuit is good up to the destination E3-12. Figure 2-8 shows an example of a terminal loopback on a destination E3-12 card.

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

Procedure: Create the Terminal Loopback on a Destination E3-12 Card

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

Step 3   Confirm that the newly created circuit appears on a Circuits screen row with a direction column that shows a two-way circuit.

---

Note    It is normal for an alarm to appear during a loopback setup. The alarm clears when you remove the loopback.

---

Step 4   Create the loopback circuit on the destination card and port being tested:

Proceed to the "Test the Terminal Loopback Circuit on the Destination E3-12 Card" section.

Procedure: Test the Terminal Loopback Circuit on the Destination E3-12 Card

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.

Step 4   If the test set indicates a faulty circuit, the problem may be a faulty card.

Proceed to the "Test the Destination E3-12 Card" section.

Procedure: Test the Destination E3-12 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. Consult "Maintenance," for information.

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.

Proceed to the "Perform a Facility Loopback on a Destination E3-12 Card" section.

2.2.4 Perform a Facility Loopback on a Destination E3-12 Card

The final test is a facility loopback performed on the destination traffic card in the circuit, in this case the E3-12 card in the destination node. Completing a successful facility loopback on this card eliminates the possibility that the destination node cabling, E3-12 card, LIU, or FMEC card is responsible for a faulty circuit. Figure 2-9 shows an example of a facility loopback on a destination E3-12 card.

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

Procedure: Create a Facility Loopback Circuit on a Destination E3-12 Card

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

---

Note    It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.

---

Proceed to the "Test the Facility Loopback Circuit" section.

Procedure: Test the Facility 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.

Step 4   If the test set indicates a faulty circuit, the problem may be a faulty E3-12 card, faulty cabling from the E3-12 card to the DSx panel or the FMEC card, or a faulty FMEC card.

Proceed to the "Test the E3-12 Cabling" section.

Procedure: Test the E3-12 Cabling

Step 2   If a known-good cable is not available, test the suspect cable with a test set. Remove the suspect cable from the DSx panel or the FMEC card and connect the cable to the transmit (Tx) and receive (Rx) terminals of the test set. Run traffic to determine whether the cable is good or suspect.

Step 3   Resend test traffic on the loopback circuit with a known-good cable installed.

Step 4   If the test set indicates a good circuit, the problem was probably the defective cable.

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. Consult "Maintenance," for information.

Step 5   If the test set indicates a faulty circuit, the problem may be a faulty card or a faulty FMEC card.

Proceed to the "Test the E3-12 Card" section.

Procedure: Test the E3-12 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. Consult "Maintenance," for information.

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.

Step 4   If the test set indicates a faulty circuit, the problem may be a faulty FMEC card.

Proceed to the "Test the FMEC Card" section.

Procedure: Test the FMEC card

Step 2   Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the reinstalled FMEC card.

Step 3   If the test set indicates a good circuit, the problem was probably an improperly seated FMEC card.

Step 4   If the test set indicates a faulty circuit, the problem is probably the defective FMEC card.

Step 5   Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the replacement FMEC card.

Step 6   If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.

If faulty circuit still persists, contact Cisco TAC at 1-800-553-2447 for assistance.

Step 7   If the test set indicates a good circuit, the problem was probably the defective FMEC card.

2.3 CTC Operation and Connectivity

This section contains troubleshooting procedures for CTC login or operation errors and PC and network connectivity.

2.3.1 Operation: Unable to Change Node View to Network View

Symptom: When activating a large, multi node MS-SPRing from Software Release 3.2 to Software Release 3.3, some of the nodes appear grayed out. Logging into the new CTC, the user is unable to change node view to network view on any and all nodes, from any workstation. This is accompanied by an "Exception occurred during event dispatching: java.lang.OutOfMemoryError" in the java window.

Table 2-1 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Reset the CTC_HEAP Environment Variable for Windows

Step 2   From the Windows Desktop, right-click on My Computer and select Properties in the pop-up menu.

Step 3   In the System Properties window, click on the Advanced tab.

Step 4   Click the Environment Variables button to open the Environment Variables window.

Step 5   Click the New button under the User variables field or the System variables field.

Step 6   Type CTC_HEAP in the Variable Name field.

Step 7   Type 256 in the Variable Value field, and then click the OK button to create the variable.

Step 8   Click the OK button in the Environment Variables window to accept the changes.

Step 9   Click the OK button in the System Properties window to accept the changes.

You may now restart the browser and CTC software.

Procedure: Reset the CTC_HEAP Environment Variable for Solaris

Step 2   Kill any Netscape applications.

Step 3   In the user shell window, set the environment variable to increase the heap size: % setenv CTC_HEAP 256
You may now restart the browser and CTC software in the same user shell window.

2.3.2 Operation: Browser Stalls When Downloading jar File From TCC-I

Symptom: The browser stalls or hangs when downloading a jar file from the TCC-I card.

Table 2-2 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Disable the VirusScan Download Scan

Step 2   Double-click the VShield icon listed in the VirusScan Console dialog box.

Step 3   Click the Configure button 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 checkbox.

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.

2.3.3 Operation: CTC Does Not Launch

Symptom: CTC does not launch, usually an error message appears before the login screen displays.

Table 2-3 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Redirect the Netscape Cache to a Valid Directory

Step 2   Display the Edit menu.

Step 3   Choose Preferences.

Step 4   Under the Category column on the left-hand side, go to Advanced and select the Cache tab.

Step 5   Change your disk cache folder to point to the cache file location.

The cache file location is usually C:\ProgramFiles\Netscape\Users\<yourname>\cache. The <yourname> segment of the file location is often the same as the user name.

2.3.4 Operation: Sluggish CTC Operation or Login Problems

Symptom: You experience sluggish CTC operation or have problems logging into CTC.

Table 2-4 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Delete the CTC Cache File Automatically

Step 2   Close all open CTC sessions and browser windows. The PC operating system will not allow you to delete files that are in use.

Step 3   Click the Delete CTC Cache button on the initial browser window to clear the CTC cache. Figure 2-10 shows the Delete CTC Cache screen.

Procedure: Delete the CTC Cache File Manually

Step 2   Enter *.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 TCC-I. These files may include CTC*.jar, CMS*.jar, and jar_cache*.tmp.

Step 4   Highlight the files and press the keyboard Delete key.

Step 5   Click Yes at the Confirm dialog box.

2.3.5 Operation: Node Icon is Grey on CTC Network View

Symptom   The CTC network view shows one or more node icons as grey in color and without a node name.

Table 2-5 describes the potential cause(s) of the symptom and the solution(s).

2.3.6 Operation: CTC Cannot Launch Due to Applet Security Restrictions

Symptom   The error message "Unable to launch CTC due to applet security restrictions" appears after you enter the IP address in the browser window.

Table 2-6 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Manually Edit the java.policy File

Step 2   Verify that the end of this file has the following lines:

Step 3   If these five lines are not in the file, enter them manually.

Step 4   Save the file and restart Netscape.

CTC should now start correctly.

Step 5   If the error message is still reported, save the java.policy file as .java.policy.

On Win95/98/2000 PCs, save the file to the C:\Windows folder. On WinNT4.0 PCs, save the file to all of the user folders on that PC, for example, C:\Winnt\profiles\joeuser.

2.3.7 Operation: Java Runtime Environment Incompatible

Symptom   The CTC application will not run properly.

Table 2-7 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Launch CTC to Correct the Core Version Build

Step 2   Start the browser.

Step 3   Type the ONS 15454 SDH 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 will download the jar file from CTC.

2.3.8 Operation: Username or Password Does Not Match

Symptom   A mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm.

Table 2-8 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Verify Correct Username and Password

Step 2   Contact your system administrator to verify the username and password.

Step 3   Call Cisco TAC at 1-800-553-2447 or login to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to obtain more information to have them enter your system and create a new user name and password.

2.3.9 Operation: No IP Connectivity Exists Between Nodes

Symptom   The nodes have a grey icon and is usually accompanied by alarms.

Table 2-9 describes the potential cause(s) of the symptom and the solution(s).

2.3.10 Operation: DCC Connection Lost

Symptom   The node is usually accompanied by alarms and the nodes in the network view have a grey icon. This symptom is usually accompanied by an EOC alarm.

Table 2-10 describes the potential cause(s) of the symptom and the solution(s).

2.3.11 Operation: 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 2-11 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Reconfigure the PC Operating System and the Browser

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

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

Step 4   From the Java Run Time Environment menu, select JRE 1.3.1 in C:\ProgramFiles\JavaSoft\JRE\1.3.1

Step 5   Click Apply.

Step 6   On Netscape Navigator, click Edit > Preferences.

Step 7   Click Advanced > Proxies > Direct connection to the Internet > OK.

Step 8   Again on Netscape Navigator, click Edit > Preferences.

Step 9   Click Advanced > Cache.

Step 10   Confirm that the Disk Cache Folder field shows C:\ProgramFiles\Netscape\Communicator\cache for Windows 95/98/ME

or C:\ProgramFiles\Netscape\<username>\Communicator\cache for Windows NT/2000.

Step 11   If the Disk Cache Folder field is not correct, click Choose Folder.

Step 12   Navigate to the file listed in Step 10 and click OK.

Step 13   Click OK on the Preferences window and exit the browser.

Step 14   Temporarily disable any virus-scanning software on the computer. See the "Operation: Browser Stalls When Downloading jar File From TCC-I" section.

Step 15   Verify that the computer does not have two network interface cards (NICs) installed. If the computer does have two NICs, remove one.

Step 16   Restart the browser and log into the ONS 15454 SDH.

2.3.12 Connectivity: Verify PC Connection to ONS 15454 SDH (ping)

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

Table 2-12 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Ping the ONS 15454 SDH

Step 2   For both the Sun and Microsoft operating systems, at the prompt type:

Step 3   If the workstation has connectivity to the ONS 15454 SDH, the ping is successful and displays a reply from the IP address. If the workstation does not have connectivity, a "Request timed out" message displays.

Step 4   If the ping is successful, an active TCP/IP connection exists. Restart CTC.

Step 5   If the ping is not successful, and the workstation connects to the ONS 15454 SDH through a LAN, check that the workstation's IP address is on the same subnet as the ONS node.

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

2.3.13 Calculate and Design IP Subnets

Symptom   You cannot properly calculate or design IP subnets on the ONS 15454 SDH.

Table 2-13 describes the potential cause(s) of the symptom and the solution(s).

2.3.14 Ethernet Connections

Symptom   Ethernet connections appear to be broken or are not working properly.

Table 2-14 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Verify Ethernet Connections

Step 2   Check for Ethernet-specific alarms. Clear any raised alarms by looking up that alarm in "Alarm Index."

Step 3   Verify that the ACT LED on the Ethernet card is green.

Step 4   Verify that Ports 1 and 3 on ONS 15454 SDH #1 and Ports 1 and 2 on ONS 15454 SDH #2 have green link-integrity LEDs illuminated.

Step 5   If no green link-integrity LED is illuminated for any of these ports:

Step 6   Verify connectivity between device A and device C by pinging between these locally attached devices (see the "Connectivity: Verify PC Connection to ONS 15454 SDH (ping)" section). If the ping is unsuccessful:

Step 7   Repeat Step 6 for devices B and D.

Step 8   Verify that the Ethernet circuit that carries VLAN #1 is provisioned and that ONS 15454 SDH #1 and ONS 15454 SDH #2 ports also use VLAN #1.

2.3.15 VLAN Cannot Connect to Network Device from Untag Port

Symptom   Networks that have a VLAN with one ONS 15454 SDH Ethernet card port set to Tagged and one ONS 15454 SDH Ethernet card set to Untag may have difficulty implementing Address Resolution Protocol (ARP) for a network device attached to the Untag port (Figure 2-12). They may also see a higher than normal runt packets count at the network device attached to the Untag port.

Table 2-15 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Change VLAN Port Tag and Untagged Settings

Step 2   Click the Provisioning > VLAN tabs (Figure 2-13).

Step 3   If the port is set to Tagged, continue to look at other cards and their ports in the VLAN until you find the port that is set to Untag.

Step 4   At the VLAN port set to Untag, click the port and choose Tagged.

---

Note    The attached external devices must recognize IEEE 802.1Q VLANs.

---

Step 5   After each port is in the appropriate VLAN, click Apply.

2.4 Circuits and Timing

This section provides solutions to circuit creation and reporting errors, as well as common timing reference errors and alarms.

2.4.1 TU-AIS on Unused VC Circuits

Symptom   An incomplete circuit path causes a tributary unit alarm indications signal (TU-AIS).

Table 2-16 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Clear TU-AIS on Unused VC Circuits

Step 2   Record the node ID, slot number, port number, or VC number.

Step 3   Create a unidirectional VC circuit from the affected port back to itself, such as Source node/Slot 2/Port 2/VC11 cross connected to Source node/Slot 2/Port 2/VC11.

Step 4   Uncheck the bidirectional box in the circuit creation window.

Step 5   Give the unidirectional VC circuit an easily recognizable name, such as delete me.

Step 6   Display the DS3IN card in CTC card view. Click the Maintenance > DS1 tabs.

Step 7   Locate the VC that is reporting the alarm (for example, DS3 #2, DS1 #13).

Step 8   From the Loopback Type list, choose Facility (line) and click Apply.

Step 9   Click Circuits.

Step 10   Find the one-way circuit you created in Step 2. Select the circuit and click Delete.

Step 11   Click Yes in the Delete Confirmation box.

Step 12   Display the DS3IN card in CTC card view. Click Maintenance > DS1.

Step 13   Locate the VC in Facility (line) Loopback.

Step 14   From the Loopback Type list, choose None and then click Apply.

Step 15   Click the Alarm tab and verify that the TU-AIS alarms have cleared.

Step 16   Repeat this procedure for all the TU-AIS alarms on the DS3IN cards.

2.4.2 Circuit Creation Error with VC 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 VC circuit in CTC.

Table 2-17 describes the potential cause(s) of the symptom and the solution(s).

2.4.3 ONS 15454 SDH Switches Timing Reference

Symptom   Timing references switch when one or more problems occur.

Table 2-18 describes the potential cause(s) of the symptom and the solution(s).

2.4.4 Holdover Synchronization Alarm

Symptom   The clock is running at a different frequency than normal and the HLDOVERSYNC alarm appears.

Table 2-19 describes the potential cause(s) of the symptom and the solution(s).

2.4.5 Free-Running Synchronization Mode

Symptom   The clock is running at a different frequency than normal and the FRNGSYNC alarm appears.

Table 2-20 describes the potential cause(s) of the symptom and the solution(s).

2.4.6 Daisy-Chained SETS Not Functioning

Symptom   You are unable to daisy-chain the SETS.

Table 2-21 outlines the problem that might cause this symptom and describes solutions to the problem.

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

2.5.1 Bit Errors Appear for a Traffic Card

Symptom   A traffic card has multiple Bit errors.

Table 2-22 describes the potential cause(s) of the symptom and the solution(s).

2.5.2 Faulty Fiber-Optic Connections

Symptom   A line card has multiple SONET alarms and/or signal errors.

Table 2-23 describes the potential cause(s) of the symptom and the solution(s).

Warning Follow all directions and warning labels when working with optical fibers. To prevent eye damage, never look directly into a fiber or connector. Class IIIb laser. Danger, laser radiation when open. The OC-192 laser is off when the safety key is off (labeled 0). The laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. Avoid direct exposure to the beam. Invisible radiation is emitted from the aperture at the end of the fiber optic cable when connected, but not terminated.

Procedure: Verify Fiber-Optic Connections

SM or SM fiber should be printed on the fiber span cable. ONS 15454 SDH STM-N cards do not use multimode fiber.

Step 2   Ensure that the connector keys on the SC fiber connector are properly aligned and locked.

Step 3   Check that the single-mode fiber power level is within the specified range:

Step 4   If the power level falls below the specified range:

IR cards transmit a lower output power than LR cards.

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. Consult "Maintenance," for information.

---

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

Step 6   If the power level on the fiber is above the range specified for the card, ensure that an ONS long-range (LR) card is not being used when an ONS intermediate-range (IR) card is appropriate.

LR cards transmit a higher output power than IR cards. When used with short runs of fiber, an LR transmitter will be too powerful for the receiver on the receiving STM-N card.

Receiver overloads occur when maximum receiver power is exceeded.

Tip To prevent overloading the receiver, use an attenuator on the fiber between the ONS STM-N card transmitter and the receiver. Place the attenuator on the receive transmitter of the ONS STM-N cards. Refer to the attenuator documentation for specific instructions.

Tip Most fiber has text printed on only one of the two fiber strands. Use this to identify which fiber is connected to Tx and which fiber is connected to Rx.

Procedure: Replace Faulty Gigabit Interface Converters

Gigabit interface converters (GBICs) are hot-swappable input/output devices that plug into a Gigabit Ethernet port to link the port with the fiber-optic network. Cisco provides two GBIC models: one for short-reach applications, 15454-GBIC-SX, and one for long-reach applications, 15454-GBIC-LX. The short-reach, or "SX" model, connects to multimode fiber and has a maximum cabling distance of 1804 feet. The long-reach, or "LX" model, requires single-mode fiber and has a maximum cabling distance of 10000.5 metres (32,810 feet).

GBICs can be installed or removed while the card and shelf assembly are powered and running. GBIC transmit failure is characterized by a steadily blinking Fail LED on the Gigabit Ethernet (E1000-2/E1000-2-G) card. Figure 2-14 shows a GBIC.

Warning Class 1 laser product

Warning Invisible laser radiation may be emitted from the aperture ports of single-mode fiber optic modules when a cable is not connected. Avoid exposure and do not stare into open apertures.

Step 2   Release the GBIC from the card interface by simultaneously squeezing the two plastic tabs, one on each side of the GBIC.

Step 3   Slide the GBIC out of the Gigabit Ethernet front-panel slot.

---

Note    A flap closes over the GBIC slot to protect the connector on the Gigabit Ethernet (E1000-2/E1000-2-G) card.

---

Step 4   Remove the new GBIC from its protective packaging.

Step 5   Check the part number to verify that the GBIC is the correct type for your network.

Caution   Check the label on the GBIC carefully. The two GBIC models look similar.

Step 6   Grip the sides of the GBIC with your thumb and forefinger and insert the GBIC into the slot on the front panel of the Gigabit Ethernet (E1000-2/E1000-2-G) card (see Figure 2-15).

---

Note    GBICs are keyed to prevent incorrect installation.

---

Step 7   Slide the GBIC through the front flap until you hear a click.

The click indicates that the GBIC is locked into the slot.

Step 8   When you are ready to attach the network interface fiber-optic cable, remove the protective plug from the GBIC and save the plug for future use.

Procedure: Crimp Replacement CAT-5 Cables

You can crimp your own CAT-5 cables for use with the ONS 15454 SDH. Use a cross-over cable when connecting an ONS 15454 SDH to a hub, LAN modem, or switch, and use a straight-through cable when connecting an ONS 15454 SDH to a router or workstation. Use CAT 5 cable RJ-45 T-568B, Color Code (100 Mbps), and a crimping tool.

Note   Odd-numbered pins always connect to a white wire with a colored stripe.

2.5.3 Optical Card Transmit and Receive Levels

Each STM-N card has a transmit and receive connector on its faceplate.

2.6 Power and LED Tests

This section provides the "Power Supply Problems" section, the "Power Consumption for Node and Cards" section, and the "Lamp Test for Card LEDs" section.

2.6.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 2-27 describes the potential cause(s) of the symptom and the solution(s).

Caution   Operations that interrupt power supply or short the power connections to the ONS 15454 SDH are service-affecting.

Warning When working with live power, always use proper tools and eye protection.

Warning Always use the supplied electrostatic discharge (ESD) wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Isolate the Cause of Power Supply Problems

Step 2   If multiple pieces of site equipment show signs of fluctuating power or power loss:

2.6.2 Power Consumption for Node and Cards

Symptom   You are unable to power up a node or the cards in a node.

Table 2-28 describes the potential cause(s) of the symptom and the solution(s).

2.6.3 Lamp Test for Card LEDs

Symptom   Card LED will not light or you are unsure if LEDs are working properly.

Table 2-29 describes the potential cause(s) of the symptom and the solution(s).

Procedure: Verify Card LED Operation

Step 2   Click Lamp Test.

Step 3   Watch to make sure all the LEDs on the cards illuminate for several seconds.

Step 4   Click OK on the Lamp Test Run dialog box.

If an LED does not illuminate, the LED is faulty. Call the Cisco TAC at 1-800-553-2447 and fill out an RMA to return the card.