Table Of Contents
General Troubleshooting
2.1 Network Troubleshooting Tests
2.2 Identify Points of Failure on a Circuit Path
2.2.1 Perform a Facility Loopback on a Source DS-N Card
2.2.2 Perform a Hairpin on a Source Node
2.2.3 Perform a Terminal Loopback on a Destination DS-N Card
2.2.4 Perform a Facility Loopback on a Destination DS-N Card
2.2.5 Using the DS3XM-6 Card FEAC (Loopback) Functions
2.3 CTC Operation and Connectivity
2.3.1 Operation: Unable to Change Node View to Network View
2.3.2 Operation: Browser Stalls When Downloading CTC JAR Files From TCC+
2.3.3 Operation: CTC Does Not Launch
2.3.4 Operation: Sluggish CTC Operation or Login Problems
2.3.5 Operation: Node Icon is Grey on CTC Network View
2.3.6 Operation: CTC Cannot Launch Due to Applet Security Restrictions
2.3.7 Operation: Java Runtime Environment Incompatible
2.3.8 Operation: Different CTC Releases Do Not Recognize Each Other
2.3.9 Operation: Username or Password Do Not Match
2.3.10 Operation: No IP Connectivity Exists Between Nodes
2.3.11 Operation: DCC Connection Lost
2.3.12 Operation: Browser Login Does Not Launch Java
2.3.13 Connectivity: Verify PC Connection to ONS 15454 (ping)
2.3.14 Calculate and Design IP Subnets
2.3.15 Ethernet Connections
2.3.16 VLAN Cannot Connect to Network Device from Untag Port
2.3.17 Cross-Connect Card Oscillator Fails
2.4 Circuits and Timing
2.4.1 AIS-V on DS3XM-6 Unused VT Circuits
2.4.2 Circuit Creation Error with VT1.5 Circuit
2.4.3 Unable to Create Circuit From DS-3 Card to DS3XM-6 Card
2.4.4 DS3 Card Does Not Report AIS-P From External Equipment
2.4.5 OC-3 and DCC Limitations
2.4.6 ONS 15454 Switches Timing Reference
2.4.7 Holdover Synchronization Alarm
2.4.8 Free-Running Synchronization Mode
2.4.9 Daisy-Chained BITS Not Functioning
2.5 Fiber and Cabling
2.5.1 Bit Errors Appear for a Traffic Card
2.5.2 Faulty Fiber-Optic Connections
2.5.3 Optical Card Transmit and Receive Levels
2.6 Power and LED Tests
2.6.1 Power Supply Problems
2.6.2 Power Consumption for Node and Cards
2.6.3 Lamp Test for Card LEDs
General Troubleshooting
This chapter provides procedures for troubleshooting the most common problems encountered when operating a Cisco ONS 15454. To troubleshoot specific ONS 15454 alarms, see Chapter 1, "Alarm Troubleshooting." If you cannot find what you are looking for in this chapter or Chapter 1, "Alarm Troubleshooting," contact the Cisco Technical Assistance Center (TAC) at 1-877-323-7368.
This chapter begins with 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 15454 Procedure Guide.
• Identify Points of Failure on a Circuit Path—Explains how to perform the tests described in the "Network Troubleshooting Tests" section.
• Using the DS3XM-6 Card FEAC (Loopback) Functions—Describes the Far End Alarm and Control (FEAC) features on the DS3XM-6 card.
The remaining sections describe symptoms, problems, and solutions that are categorized according to the following topics:
• CTC Operation and Connectivity—Provides troubleshooting procedures for CTC log-in or operation errors and PC and network connectivity.
• Circuits and Timing—Provides troubleshooting procedures for circuit creation, and error reporting, and timing reference errors and alarms.
• Fiber and Cabling—Provides troubleshooting procedures for fiber and cabling connectivity errors.
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 line (traffic) cards, except Ethernet cards, allow loopbacks and hairpins.
Caution On OC-N cards, a loopback applies to the entire card and not an individual circuit. Exercise caution when using loopbacks on an OC-N card carrying live traffic.
A facility loopback tests the line interface unit (LIU) of a card, the EIA (electrical interface assembly), 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, the EIA, or cabling plant as the potential cause of a network problem. Figure 2-1 shows a facility loopback on a DS-N card.
Figure 2-1 The facility loopback process on a DS-N card
Figure 2-2 shows a facility loopback on an OC-N card.
Caution Before performing a facility loopback on an OC-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 containing the loopback OC-N card.
Figure 2-2 The facility loopback process on an OC-N card
A terminal loopback tests a circuit path as it passes through the cross-connect card (XC, XCVT, or XC10G) and as it loops back from the card being tested. Figure 2-3 shows a terminal loopback on an OC-N card. The test-set traffic comes in on the DS-N card and goes through the cross-connect card to the OC-N card. The terminal loopback on the OC-N card turns the signal around before it reaches the LIU and sends it through the cross-connect card to the DS-N card. This test verifies that the cross-connect card and circuit paths are valid, but does not test the LIU on the OC-N card.
Figure 2-3 The terminal loopback process on an OC-N card
To test the LIU on an OC-N card, connect an optical test set to the OC-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 a DS-N card. The test-set traffic comes in on the OC-N card and goes through the cross-connect card to the DS-N card. The terminal loopback on the DS-N card turns the signal around before it reaches the LIU and sends it through the cross-connect card to the OC-N card. This test verifies that the cross-connect card and circuit paths are valid, but does not test the LIU on the DS-N card.
Figure 2-4 The terminal loopback process on a DS-N card
A hairpin circuit brings traffic in and out on a DS-N port rather than sending the traffic onto the OC-N card. A hairpin loops back only the specific STS or VT circuit and does not cause an entire OC-N port to loop back, thus preventing a drop of all traffic on the OC-N port. The hairpin allows you to test a circuit on nodes running live traffic.
Figure 2-5 The hairpin circuit process on an OC-N card
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 a DS-N circuit on a two-node bidirectional line switched ring (BLSR). 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 DS-N card
2. A hairpin on the source-node DS-N card
3. A terminal loopback on the destination-node DS-N card
4. A facility loopback on the destination DS-N card
Note All loopback tests require on-site personnel.
2.2.1 Perform a Facility Loopback on a Source DS-N Card
The facility loopback test is performed on the source card in the network circuit, in this example, the DS-N card in the source node. Completing a successful facility loopback on this card eliminates the cabling, the DS-N card, and the EIA as possible failure points. Figure 2-6 shows an example of a facility loopback on a source DS-N card.
Figure 2-6 A facility loopback on a circuit source DS-N card
Caution Performing a loopback on an in-service circuit is service-affecting.
2.2.1.1 Create the Facility Loopback on the Source DS-N Card
Step 1 Connect an electrical test set to the port you are testing.
Use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the EIA connectors or DSx panel for the port you are testing. The transmit (Tx) and receive (Rx) terminals connect to the same port. Adjust the test set accordingly.
Step 2 Use CTC to create the facility loopback circuit on the port being tested:
a. In node view, double-click the card where you will perform the loopback.
b. Click the Maintenance > Loopback tabs.
c. Choose Facility (Line) from the Loopback Type column for the port being tested. If this is a multiport card, select the appropriate row for the desired port.
d. Click Apply.
e. On the confirmation dialog box, click Yes.
Note It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.
Step 3 Proceed to the "Test the Facility Loopback Circuit" section.
2.2.1.2 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.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Hairpin on a Source Node" section.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty DS-N card, faulty cabling from the DS-N card to the DSx panel or the EIA, or a faulty EIA.
Step 5 Proceed to the "Test the DS-N Cabling" section.
2.2.1.3 Test the DS-N Cabling
Step 1 Replace the suspect cabling (the cables from the test set to the DSx panel or the EIA ports) with a known-good cable.
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 EIA 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.
a. Replace the defective cable.
b. Clear the loopback circuit before testing the next segment of the network circuit path.
c. Proceed to the "Perform a Hairpin on a Source Node" section.
Step 5 If the test set indicates a faulty circuit, the problem may be a faulty card or a faulty EIA.
Step 6 Proceed to the "Test the DS-N Card" section.
2.2.1.4 Test the DS-N Card
Step 1 Replace the suspect card with a known-good card. See Chapter 1, "Alarm Troubleshooting," for details.
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 the
Cisco ONS 15454 Procedure Guide 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.
a. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
b. Replace the faulty card.
c. Clear the loopback circuit before testing the next segment of the network circuit path.
d. Proceed to the "Perform a Hairpin on a Source Node" section.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty EIA.
Step 5 Proceed to the "Test the EIA" section.
2.2.1.5 Test the EIA
Step 1 Remove and reinstall the EIA to ensure a proper seating:
a. Remove the lower backplane cover. Loosen the five screws that secure it to the ONS 15454 and pull it away from the shelf assembly.
b. Loosen the nine perimeter screws that hold the EIA panel in place.
c. Lift the EIA panel by the bottom to remove it from the shelf assembly.
d. Follow the installation procedure for the appropriate EIA. See the "Replace the Electrical Interface Assembly" section on page 3-20.
Step 2 Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the reinstalled EIA.
Step 3 If the test set indicates a good circuit, the problem was probably an improperly seated EIA.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Hairpin on a Source Node" section
Step 4 If the test set indicates a faulty circuit, the problem is probably the defective EIA.
a. Return the defective EIA to Cisco through the RMA process. Call the Cisco TAC at 1-877-323-7368 to open an RMA case.
b. Replace the faulty EIA.
Step 5 Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the replacement EIA.
Step 6 If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.
Step 7 If the test set indicates a good circuit, the problem was probably the defective EIA.
a. Clear the loopback circuit before testing the next segment of the circuit path.
b. Proceed to the "Perform a Hairpin on a Source Node" section.
2.2.2 Perform a Hairpin on a Source Node
The hairpin test is performed on the cross-connect card in the network circuit. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through the card eliminates the possibility that the cross-connect card is the cause of the faulty circuit. Figure 2-7 shows an example of a hairpin loopback on a source node.
Figure 2-7 Hairpin on a source node
Note The ONS 15454 does not support simplex operation on the cross-connect card. Two cross-connect cards of the same type must be installed for each node.
2.2.2.1 Create the Hairpin on the Source Node
Step 1 Connect an electrical test set to the port you are testing.
a. If you just completed the "Perform a Facility Loopback on a Source DS-N Card" section, leave the electrical test set hooked up to the DS-N card in the source node.
b. If you are starting the current procedure without the electrical test set hooked up to the DS-N card, use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. The transmit (Tx) and receive (Rx) terminals connect to the same port.
c. Adjust the test set accordingly.
Step 2 Use CTC to set up the hairpin on the port being tested:
a. Click the Circuits tab and click the Create button.
b. Give the circuit an easily identifiable name, such as hairpin1.
c. Set the Circuit Type and Size to the normal preferences.
d. Uncheck the Bidirectional checkbox and click Next.
e. In the Circuit Source dialog box, fill in the same card and port where the facility loopback test (DS-N card in the source node) was performed and click Next.
f. In the Circuit Destination dialog box, use the same card and port used for the Circuit Source dialog box and click Finish.
Step 3 Confirm that the newly created circuit appears with a direction column indicating that this circuit is one-way.
Step 4 Proceed to the "Test the Hairpin Circuit" section
2.2.2.2 Test the 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.
a. Clear the hairpin circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination DS-N Card" section.
Step 4 If the test set indicates a faulty circuit, there may be a problem with the cross-connect card.
Step 5 Proceed to the "Test the Standby Cross-Connect Card" section.
2.2.2.3 Test the Standby Cross-Connect Card
Step 1 Perform a reset on the standby cross-connect card:
a. Determine the standby cross-connect card. On both the physical node and the CTC screen, the ACT/STBY LED of the standby cross-connect card is amber and the ACT/STBY LED of the active cross-connect card is green.
b. Position the cursor over the standby cross-connect card.
c. Right-click and choose RESET 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.
a. Determine the standby cross-connect card. The ACT/STBY LED of the standby cross-connect card is amber and the ACT/STBY LED of the active cross-connect card is green.
b. In the node view, select the Maintenance > XC Cards tabs.
c. From the Cross Connect Cards menu, choose Switch.
d. Click Yes on the Confirm Switch dialog box.
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.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination DS-N Card" section.
Step 5 If the test set indicates a good circuit, the problem may be a defective card.
Step 6 To confirm a defective original cross-connect card, proceed to the "Retest the Original Cross-Connect Card" section.
2.2.2.4 Retest the Original Cross-Connect Card
Step 1 Do a manual switch (side switch) of the cross-connect cards to make the original cross-connect card the active card.
a. Determine the standby cross-connect card. The ACT/STBY LED of the standby cross-connect card is amber and the ACT/STBY LED of the active cross-connect card is green.
b. In node view, select the Maintenance > XC Cards tabs.
c. From the Cross Connect Cards menu, choose Switch.
d. Click Yes on the Confirm Switch dialog box.
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.
a. Return the defective card to Cisco through the RMA process. Call the Cisco TAC at 1-877-323-7368 to open an RMA case
b. Replace the defective cross-connect card. See Chapter 1, "Alarm Troubleshooting" for details.
c. Clear the loopback circuit before testing the next segment of the network circuit path.
d. Proceed to the "Perform a Terminal Loopback on a Destination DS-N Card" section
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.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination DS-N Card" section.
2.2.3 Perform a Terminal Loopback on a Destination DS-N Card
This test is a terminal loopback performed on the destination line card in the circuit, in the following example the DS-N card in the destination node. First, create a bidirectional circuit that starts on the source node DS-N port and terminates on the destination node DS-N port. Then proceed with the terminal loopback test. Completing a successful terminal loopback to a destination node DS-N card verifies that the circuit is good up to the destination DS-N. Figure 2-8 shows an example of a terminal loopback on a destination DS-N card.
Figure 2-8 Terminal loopback on a destination DS-N card
Caution Performing a loopback on an in-service circuit is service-affecting.
2.2.3.1 Create the Terminal Loopback on a Destination DS-N Card
Step 1 Connect an electrical test set to the port you are testing:
a. If you just completed the "Perform a Hairpin on a Source Node" section, leave the electrical test set hooked up to the DS-N card in the source node.
b. If you are starting the current procedure without the electrical test set hooked up to the DS-N card, use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the DSx panel or the EIA connectors for the port you are testing. Both transmit (Tx) and receive (Rx) connect to the same port.
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 the Create button.
b. Give the circuit an easily identifiable name, such as "DSNtoDSN".
c. Set Circuit Type and Size to the normal preferences.
d. Leave the Bidirectional checkbox checked and click Next.
e. In the Circuit Source dialog box, fill in the same card and port where the facility loopback test (the DS-N card in the source node) was performed and click Next.
f. In the Circuit Destination dialog box, fill in the destination card and port (the DS-N card in the destination node) and click Finish.
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:
a. In node view, double-click the card that requires the loopback, such as the DS-N card in the destination node.
b. Click the Maintenance > Loopback tabs.
c. Select Terminal (Inward) from the Loopback Type column. If this is a multiport card, select the row appropriate for the desired port.
d. Click Apply.
e. On the confirmation dialog box, click Yes.
Step 5 Proceed to the "Test the Terminal Loopback Circuit on the Destination DS-N Card" section.
2.2.3.2 Test the Terminal Loopback Circuit on the Destination DS-N Card
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.
Proceed to the "Perform a Facility Loopback on a Destination DS-N Card" section.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty card.
Proceed to the "Test the Destination DS-N Card" section.
2.2.3.3 Test the Destination DS-N Card
Step 1 Replace the suspect card with a known-good card. See Chapter 1, "Alarm Troubleshooting" for details.
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 the
Cisco ONS 15454 Procedure Guide 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.
a. Return the defective card to Cisco through the RMA process. Call the Cisco TAC at 1-877-323-7368 to open an RMA case.
b. Replace the defective DS-N card.
Step 4 Proceed to the "Perform a Facility Loopback on a Destination DS-N Card" section.
2.2.4 Perform a Facility Loopback on a Destination DS-N Card
The final test is a facility loopback performed on the last card in the circuit, in this case the DS-N card in the destination node. Completing a successful facility loopback on this card eliminates the possibility that the destination node cabling, DS-N card, LIU, or EIA is responsible for a faulty circuit. Figure 2-9 shows an example of a facility loopback on a destination DS-N card.
Figure 2-9 Facility loopback on a destination DS-N card
Caution Performing a loopback on an in-service circuit is service-affecting.
2.2.4.1 Create a Facility Loopback Circuit on a Destination DS-N Card
Step 1 Connect an electrical test set to the port you are testing:
Use appropriate cabling to attach the electrical test set transmit (Tx) and receive (Rx) terminals to the EIA connectors or DSx panel for the port you are testing. Both transmit (Tx) and receive (Rx) connect to the same port. Set up your test set accordingly.
Step 2 Use CTC to create the facility loopback circuit on the port being tested:
a. In node view, double-click the card where the loopback will be performed.
b. Click the Maintenance > Loopback tabs.
c. Select Facility (Line) from the Loopback Type column for the port being tested. If this is a multiport card, select the row appropriate for the desired port.
d. Click Apply.
e. On the confirmation dialog box, click Yes.
Note It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.
Step 3 Proceed to the "Test the Facility Loopback Circuit" section.
2.2.4.2 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 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. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty DS-N card, faulty cabling from the DS-N card to the DSx panel or the EIA, or a faulty EIA.
Step 5 Proceed to the "Test the DS-N Cabling" section.
2.2.4.3 Test the DS-N Cabling
Step 1 Replace the suspect cabling (the cables from the test set to the DSx panel or the EIA ports) with a known-good cable.
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 EIA 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 set 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.
a. Replace the defective cable.
b. Clear the loopback circuit.
c. The entire DS-N 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 may be a faulty card or a faulty EIA.
Step 6 Proceed to the "Test the DS-N Card" section.
2.2.4.4 Test the DS-N Card
Step 1 Replace the suspect card 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. Consult the
Cisco ONS 15454 Procedure Guide 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.
a. Return the defective card to Cisco through the RMA process. Call the Cisco TAC at 1-877-323-7368 to open an RMA case.
b. Replace the faulty card. See Chapter 1, "Alarm Troubleshooting" for details.
c. Clear the loopback circuit.
d. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty EIA.
Step 5 Proceed to the "Test the EIA" section.
2.2.4.5 Test the EIA
Step 1 Remove and reinstall the EIA to ensure a proper seating.
a. Remove the lower backplane cover, loosen the five screws that secure it to the ONS 15454, and pull it away from the shelf assembly.
b. Loosen the nine perimeter screws that hold the EIA panel in place.
c. Lift the EIA panel by the bottom to remove it from the shelf assembly.
d. Follow the installation procedure for the appropriate EIA. See the "Replace the Electrical Interface Assembly" section on page 3-20.
Step 2 Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the reinstalled EIA.
Step 3 If the test set indicates a good circuit, the problem was probably an improperly seated EIA.
a. Clear the loopback circuit.
b. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, the problem is probably the defective EIA.
a. Return the defective EIA to Cisco through the RMA process. Call the Cisco TAC at 1-877-323-7368 to open an RMA case.
b. Replace the faulty EIA.
Step 5 Resend test traffic on the loopback circuit with known-good cabling, a known-good card, and the replacement EIA.
Step 6 If the test set indicates a faulty circuit, repeat all of the facility loopback procedures.
If the faulty circuit persists, call Cisco TAC at 1-877-323-7368 for assistance.
Step 7 If the test set indicates a good circuit, the problem was probably the defective EIA.
a. Clear the loopback circuit.
b. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
2.2.5 Using the DS3XM-6 Card FEAC (Loopback) Functions
The DS3XM-6 card supports Far End Alarm and Control (FEAC) features that are not available on basic DS-3 cards. Click the Maintenance tab at the DS3XM-6 card view to reveal the two additional DS3XM-6 columns. Figure 2-10 shows the DS3 subtab and the additional Send Code and Inhibit FE Lbk columns.
Figure 2-10 Accessing FEAC functions on the DS3XM-6 card
The far end in FEAC refers to the piece of equipment that is connected to the DS3XM-6 card and not the far end of a circuit. In Figure 2-11, if a DS3XM-6 (near-end) port is configured to send a Line Loop Code, the code will be sent to the connected test set, not the DS3XM-6 (far-end) port.
Figure 2-11 Diagram of far end action code
2.2.5.1 FEAC Send Code
The Send Code column on the maintenance tab of a DS3XM-6 port only applies to in-service 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 (Far End Alarm and Control) in the CBIT overhead transmitting to the connected facility. This code initiates a loopback from the facility to the ONS 15454. Selecting No Code sends a line-loop-deactivate FEAC code to the connected equipment, which will remove the loopback. You can also insert a FEAC for the 28 individual DS-1 circuits transmuxed into a DS-3 circuit.
2.2.5.2 FEAC Inhibit Loopback
The DS3XM-6 ports and transmuxed DS-1s initiate loopbacks when they receive FEAC Line Loop codes. If the Inhibit Loopback checkbox is checked for a DS-3 port, then that port will ignore any received FEAC Line Loop codes and will not loop back. The port can still be put into loopback manually using the Loopback Type column even if the Inhibit Loopback box is selected. Only DS-3 ports can be configured to inhibit responses to FEAC loopback commands, individual DS-1 ports cannot inhibit their responses.
2.2.5.3 FEAC Alarms
The node raises a LPBKDS3FEAC-CMD or LPBKDS1FEAC-CMD alarm for a DS-1 or DS-3 port if a FEAC loopback code is sent to the far end.
If the ONS 15454 port is in loopback from having received a loopback activate FEAC code, a LPBKDS3FEAC or LPBKDS1FEAC alarm occurs. The alarm will clear when a loopback deactivate FEAC command is received on that port.
A DS3E card will respond to, and can inhibit, received FEAC DS3 level loopback codes. A DS3E card cannot be configured to send FEAC codes.
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 BLSR 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).
2.3.1.1 Reset the CTC_HEAP Environment Variable for Windows
Step 1 Exit any and all open and running CTC and Netscape applications.
Step 2 From the Windows Desktop, right-click on My Computer and choose Properties in the pop-up menu.
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 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 OK to create the variable.
Step 8 Click OK in the Environment Variables window to accept the changes.
Step 9 Click OK in the System Properties window to accept the changes.
You may now restart the browser and CTC software.
2.3.1.2 Reset the CTC_HEAP Environment Variable for Solaris
Step 1 From the user shell window, kill any CTC applications.
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 CTC JAR Files From TCC+
Symptom: The browser stalls or hangs when downloading a CTC JAR file from the TCC+ card.
Table 2-2 describes the potential cause(s) of the symptom and the solution(s).
Table 2-2 Browser Stalls When Downloading jar File From TCC+
Possible Problem
|
Solution
|
McAfee VirusScan software may 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" section.
|
2.3.2.1 Disable the VirusScan Download Scan
Step 1 From the Windows start menu, choose Programs > Network Associates > VirusScan Console.
Step 2 Double-click the VShield icon listed in the VirusScan Console dialog box.
Step 3 Click 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).
2.3.3.1 Redirect the Netscape Cache to a Valid Directory
Step 1 Launch Netscape.
Step 2 Display the Edit menu.
Step 3 Choose Preferences.
Step 4 Under the Category column on the left-hand side, go to Advanced and choose the Cache tab.
Step 5 Change your disk cache folder to point to the cache file location.
The cache file location is usually C:\ProgramFiles\Netscape\Users\<yourname>\cache. The <yourname> segment of the file location is often the same as the user name.
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).
2.3.4.1 Delete the CTC Cache File Automatically
Step 1 Enter an ONS 15454 IP address into the browser URL field. The initial browser window shows a Delete CTC Cache button.
Step 2 Close all open CTC sessions and browser windows. The PC operating system 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-12 shows the Delete CTC Cache screen.
Note For CTC releases prior to 3.0, automatic deletion is unavailable. For CTC Cache file manual deletion, see the Delete the CTC Cache File Manually
Figure 2-12 Deleting the CTC cache
2.3.4.2 Delete the CTC Cache File Manually
Step 1 To delete the jar files manually, from the Windows Start menu choose Search > For Files or Folders.
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+. 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).
Table 2-6 CTC Cannot Launch Due to Applet Security Restrictions
Possible Problem
|
Solution
|
Did not execute the javapolicyinstall.bat file, or the java.policy file may be incomplete.
|
1. Verify that you have executed the javapolicyinstall.bat file on the ONS 15454 software CD. This file is installed when you run the CTC Setup Wizard (refer to the CTC installation information in the Cisco ONS 15454 Procedure Guide for instructions).
2. If you ran the javapolicyinstall.bat file but still receive the error message, you must manually edit the java.policy file on your computer. See the "Manually Edit the java.policy File" section.
|
2.3.6.1 Manually Edit the java.policy File
Step 1 Search your computer for this file and open it with a text editor (Notepad or Wordpad).
Step 2 Verify that the end of this file has the following lines:
// Insert this into the system-wide or a per-user java.policy file.
// DO NOT OVERWRITE THE SYSTEM-WIDE POLICY FILE--ADD THESE LINES!
grant codeBase "http://*/fs/LAUNCHER.jar" {
permission java.security.AllPermission;
};
Step 3 If these five lines are not in the file, enter them manually.
Step 4 Save the file and restart Netscape.
CTC should now start correctly.
Step 5 If the error message is still reported, save the java.policy file as .java.policy. On 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).
Table 2-7 Java Runtime Environment Incompatible
Possible Problem
|
Solution
|
Do not have the compatible JRE installed.
|
The Java 2 Runtime Environment (JRE) contains the Java virtual machine, runtime class libraries, and Java application launcher that are necessary to run programs written in the Java programming language.
The ONS 15454 CTC is a Java application. A Java application, unlike an applet, cannot rely completely on a web browser for installation and runtime services. When you run an application written in the Java programming language, you need the correct JRE installed. The correct JRE for each CTC software release is included on the Cisco ONS 15454 software CD and on the Cisco ONS 15454 documentation CD. See the "Launch CTC to Correct the Core Version Build" section.
If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible with the different software releases. Table 2-8 shows JRE compatibility with ONS 15454 software releases.
|
Table 2-8 JRE Compatibility
ONS Software Release
|
JRE 1.2.2 Compatible
|
JRE 1.3 Compatible
|
ONS 15454 Release 2.2.1 and earlier
|
Yes
|
No
|
ONS 15454 Release 2.2.2
|
Yes
|
Yes
|
ONS 15454 Release 3.0
|
Yes
|
Yes
|
ONS 15454 Release 3.1
|
Yes
|
Yes
|
ONS 15454 Release 3.2
|
Yes
|
Yes
|
ONS 15454 Release 3.3
|
Yes
|
Yes
|
2.3.7.1 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 ONS 15454 IP address of the node that reported the alarm. This can be the original IP address you logged on with or an IP address other than the original.
Step 4 Log into CTC. The browser will download the jar file from CTC.
Note After Release 2.2.2, the single CMS.jar file evolved into core and element files. Core files are common to both the ONS 15454 and ONS 15327, while the element files are unique to the particular product. For example, the ONS 15327 Release 1.0 uses a 2.3 core build and a 1.0 element build. To display the CTC Core Version number, from the CTC menu bar click Help > About CTC. This lists the Core and Element builds discovered on the network.
2.3.8 Operation: Different CTC Releases Do Not Recognize Each Other
Symptom: This situation is often accompanied by the INCOMPATIBLE-SW alarm.
Table 2-9 describes the potential cause(s) of the symptom and the solution(s).
Table 2-9 Different CTC Releases Do Not Recognize Each Other
Possible Problem
|
Solution
|
The software loaded on the connecting workstation and the software on the TCC+ card are incompatible.
|
This occurs when the TCC+ software is upgraded but the PC has not yet upgraded the compatible CTC jar file. It also occurs on login nodes with compatible software that encounter other nodes in the network that have a newer software version.
Note Remember to always log into the ONS node with the latest CTC core version first. If you initially log into an ONS node running a CTC core version of 2.2 or lower and then attempt to log into another ONS node in the network running a higher CTC core version, the lower version node will not recognize the new node.
See the "Launch CTC to Correct the Core Version Build" section.
|
2.3.8.1 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 ONS 15454 IP address of the node that reported the alarm. This can be the original IP address you logged on with or an IP address other than the original.
Step 4 Log into CTC. The browser will download the jar file from CTC.
Note After Release 2.2.2, the single CMS.jar file evolved into core and element files. Core files are common to both the ONS 15454 and ONS 15327, while the element files are unique to the particular product. For example, the ONS 15327 Release 1.0 uses a 2.3 core build and a 1.0 element build. To display the CTC Core Version number, from the CTC menu bar click Help > About CTC. This lists the Core and Element builds discovered on the network.
2.3.9 Operation: Username or Password Do Not Match
Symptom: A mismatch often occurs concurrently with a NOT-AUTHENTICATED alarm.
Table 2-10 describes the potential cause(s) of the symptom and the solution(s).
Table 2-10 Username or Password Do Not Match
Possible Problem
|
Solution
|
The username or password entered do not match the information stored in the TCC+.
|
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 logon to the ONS 15454, type the CISCO15 user name in capital letters and click Login (no password is required). If you are using a CTC software release prior to 3.0 and CISCO15 does not work, type cerent454 for the user name.
See the "Verify Correct Username and Password" section.
|
2.3.9.1 Verify Correct Username and Password
Step 1 Ensure that your keyboard Caps Lock key is not turned on and affecting the case-sensitive entry of the username and password.
Step 2 Contact your system administrator to verify the username and password.
Step 3 Call Cisco TAC at 1-877-323-7368 to have them enter your system and create a new user name and password.
2.3.10 Operation: No IP Connectivity Exists Between Nodes
Symptom: The nodes have a grey icon and is usually accompanied by alarms.
Table 2-11 describes the potential cause(s) of the symptom and the solution(s).
Table 2-11 No IP Connectivity Exists Between Nodes
Possible Problem
|
Solution
|
A lost Ethernet connection.
|
Usually is accompanied by Ethernet-specific alarms. Verify the Ethernet connections as described in the "Ethernet Connections" section.
|
2.3.11 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-12 describes the potential cause(s) of the symptom and the solution(s).
Table 2-12 DCC Connection Lost
Possible Problem
|
Solution
|
A lost DCC connection.
|
Usually accompanied by an EOC alarm. Clear the EOC alarm and verify the DCC connection as described in the "EOC" section on page 1-38.
|
2.3.12 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-13 describes the potential cause(s) of the symptom and the solution(s).
2.3.12.1 Reconfigure the PC Operating System and the Browser
Step 1 From the Windows start menu, click Settings > Control Panel.
Step 2 If Java Plug-in Control Panel does not appear, the JRE may not be installed on your PC.
a. Run the Cisco ONS 15454 software CD.
b. Open the [CD drive]:\Windows\JRE folder.
c. Double-click the j2re-1_3_1_02-win icon to run the JRE installation wizard.
d. Follow the JRE installation wizard steps.
Step 3 From the Windows start menu, click Settings > Control Panel.
Step 4 Double-click the Java Plug-in 1.3.1_02 icon.
Step 5 Click Advanced on the Java Plug-in Control Panel.
Step 6 From the Java Run Time Environment menu, select JRE 1.3 in C:\ProgramFiles\JavaSoft\JRE\1.3.1_02.
Step 7 Click Apply.
Step 8 On Netscape Navigator, click Edit > Preferences.
Step 9 Click Advanced > Proxies > Direct connection to the Internet > OK.
Step 10 Again on Netscape Navigator, click Edit > Preferences.
Step 11 Click Advanced > Cache.
Step 12 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 13 If the Disk Cache Folder field is not correct, click Choose Folder.
Step 14 Navigate to the file listed in Step 12 and click OK.
Step 15 Click OK on the Preferences window and exit the browser.
Step 16 Temporarily disable any virus-scanning software on the computer. See the "Operation: Browser Stalls When Downloading CTC JAR Files From TCC+" section.
Step 17 Verify that the computer does not have two network interface cards (NICs) installed. If the computer does have two NICs, remove one.
Step 18 Restart the browser and log into the ONS 15454.
2.3.13 Connectivity: Verify PC Connection to ONS 15454 (ping)
Symptom: The TCP/IP connection was established and then lost, and a DISCONNECTED alarm appears on CTC.
Table 2-14 describes the potential cause(s) of the symptom and the solution(s).
Table 2-14 Verify PC connection to ONS 15454 (ping)
Possible Problem
|
Solution
|
A lost connection between the PC and the ONS 1554.
|
Use a standard ping command to verify the TCP/IP connection between the PC and the ONS 15454 TCC+ card. A ping command will work if the PC connects directly to the TCC+ card or uses a LAN to access the TCC+ card.
Note Software Release 3.0 requires the TCC+ card and does not support the TCC card. Releases 2.2, 2.2.1, and 2.2.2 support the TCC and the TCC+ cards.
See the "Ping the ONS 15454" section.
|
2.3.13.1 Ping the ONS 15454
Step 1 Display the command prompt:
a. If you are using a Microsoft Windows operating system, from the Start Menu choose Run, type command prompt in the Open field of the Run dialog box, and click OK.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
Step 2 For both the Sun and Microsoft operating systems, at the prompt type:
ping [ONS 15454 IP address]
For example, ping 192.1.0.2.
Step 3 If the workstation has connectivity to the ONS 15454, the ping is successful and displays a reply from the IP address. If the workstation does not have connectivity, a "Request timed out" message 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 through a LAN, check that the workstation's IP address is on the same subnet as the ONS node.
Step 6 If the ping is not successful and the workstation connects directly to the ONS 15454, check that the link light on the workstation's NIC is illuminated.
2.3.14 Calculate and Design IP Subnets
Symptom: You cannot calculate or design IP subnets on the ONS 15454.
Table 2-15 describes the potential cause(s) of the symptom and the solution(s).
Table 2-15 Calculate and Design IP Subnets
Possible Problem
|
Solution
|
The IP capabilities of the ONS 15454 require specific calculations to properly design IP subnets.
|
Cisco provides a free online tool to calculate and design IP subnets. Go to http://www.cisco.com/techtools/ip_addr.html. For information about ONS 15454 IP capability, refer to the Cisco ONS 15454 Reference Manual.
|
2.3.15 Ethernet Connections
Symptom: Ethernet connections appear to be broken or are not working properly.
Table 2-15 describes the potential cause(s) of the symptom and the solution(s).
Table 2-16 Calculate and Design IP Subnets
Possible Problem
|
Solution
|
Improperly seated connections.
|
You can fix most connectivity problems in an Ethernet network by following a few guidelines. See Figure 2-13 when consulting the steps in the "Verify Ethernet Connections" section.
|
Incorrect connections.
|
Figure 2-13 Ethernet connectivity reference
2.3.15.1 Verify Ethernet Connections
Step 1 Check for SONET alarms on the STS-N that carries the VLAN #1 Ethernet circuit. Clear any alarms by looking them up in Chapter 1, "Alarm Troubleshooting."
Step 2 Check for Ethernet-specific alarms. Clear any raised alarms by looking up that alarm in Chapter 1, "Alarm Troubleshooting."
Step 3 Verify that the ACT LED on the Ethernet card is green.
Step 4 Verify that Ports 1 and 3 on ONS 15454 #1 and Ports 1 and 2 on ONS 15454 #2 have green link-integrity LEDs illuminated.
Step 5 If no green link-integrity LED is illuminated for any of these ports:
a. Verify physical connectivity between the ONS 15454s and the attached device.
b. Verify that the ports are enabled on the Ethernet cards.
c. Verify that you are using the proper Ethernet cable and that it is wired correctly, or replace the cable with a known-good Ethernet cable.
d. Check the status LED on the Ethernet card faceplate to ensure the card booted up properly. This LED should be steady green. If necessary, remove and reinsert the card and allow it to reboot.
e. It is possible that the Ethernet port is functioning properly but the link LED itself is broken. Run the procedure in the "Lamp Test for Card LEDs" section.
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 (ping)" section). If the ping is unsuccessful:
a. Verify that device A and device C are on the same IP subnet.
b. Display the Ethernet card in CTC card view and click the Provisioning > VLAN tabs to verify that both Port 1 and Port 3 on the card are assigned to the same VLAN.
c. If a port is not assigned to the correct VLAN, click that port column in the VLAN row and set the port to Tagged or Untag. Click Apply.
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 #1 and ONS 15454 #2 ports also use VLAN #1.
2.3.16 VLAN Cannot Connect to Network Device from Untag Port
Symptom: Networks that have a VLAN with one ONS 15454 Ethernet card port set to Tagged and one ONS 15454 Ethernet card set to Untag may have difficulty implementing Address Resolution Protocol (ARP) for a network device attached to the Untag port ( Figure 2-14). They may also see a higher than normal runt packets count at the network device attached to the Untag port.
Figure 2-14 A VLAN with Ethernet ports at Tagged and Untag
Table 2-14 describes the potential cause(s) of the symptom and the solution(s).
Table 2-17 Verify PC connection to ONS 15454 (ping)
Possible Problem
|
Solution
|
The Tagged ONS 15454 adds the 802.1Q tag and the Untag ONS 15454 removes the Q-tag without replacing the bytes. The NIC of the network device categorizes the packet as a runt and drops the packet.
|
The solution is to set both ports in the VLAN to Tagged to stop the stripping of the 4 bytes from the data packet and prevents the NIC card in the network access device from recognizing the packet as a runt and dropping it. Network devices with 802.1Q-compliant NIC cards will accept the tagged packets. Network devices with non-802.1Q compliant NIC cards will still drop these tagged packets. The solution may require upgrading network devices with non-802.1Q compliant NIC cards to 802.1Q-compliant NIC cards. You can also set both ports in the VLAN to Untag, but you will lose 802.1Q compliance.
|
Dropped packets can also occur when ARP attempts to match the IP address of the network device attached to the Untag port with the physical MAC address required by the network access layer.
|
2.3.16.1 Change VLAN Port Tag and Untagged Settings
Step 1 Display the CTC card view for the Ethernet card involved in the problem VLAN.
Step 2 Click the Provisioning > VLAN tabs ( Figure 2-15).
Figure 2-15 Configuring VLAN membership for individual Ethernet ports
Step 3 If the port is set to Tagged, continue to look at other cards and their ports in the VLAN until you find the port that is set to Untag.
Step 4 At the VLAN port set to Untag, click the port and choose Tagged.
Note The attached external devices must recognize IEEE 802.1Q VLANs.
Step 5 After each port is in the appropriate VLAN, click Apply.
2.3.17 Cross-Connect Card Oscillator Fails
Symptom: The XC, XCVT, or XC10G card can be affected by this problem. It is indicated by a CTNEQPT-PBPROT or CTNEQPT-PBWORK condition raised against all I/O cards in the node. The following conditions might also be raised on the node:
•SWMTXMOD against one or both cross-connect cards
•SD-L against near-end or far-end line cards
•AIS-L against far-end line cards
•RFI-L against near-end line cards
Table 2-18 describes the potential cause(s) of the symptom and the solution(s).
2.3.17.1 Resolve the XC Oscillator Failure When Slot 8 XC Card is Active
Step 1 If the CTNEQPT-PBPROT condition is reported against all I/O cards in the node and the Slot 8 cross-connect card is active, right-click the Slot 10 cross-connect card.
Step 2 Choose Reset Card, then click OK. (Slot 8 remains active and Slot 10 remains standby.)
Step 3 If the alarm remains, reseat the Slot 10 card.
Step 4 If CTNEQPT-PBPROT does not clear, replace the Slot 10 cross-connect card with a spare card.
Step 5 If CTNEQPT-PBPROT does not clear, replace the spare card placed in Slot 10 with the original cross-connect card.
Step 6 Right-click the Slot 8 card and choose Reset Card.
Step 7 Click OK to activate the Slot 10 card and place the Slot 8 card in standby.
Step 8 If you then see the CTNEQPT-PBWORK condition raised against all I/O cards in the node, verify that CTNEQPT-PBPROT has cleared on all I/O cards. Seeing CTNEQPT-PBWORK on the cards indicates that Slot 8 card has a bad oscillator. If this is indicated, complete the following substeps. Otherwise, go to Step 9.
a. Replace the Slot 8 cross-connect card with a spare card. (Slot 8 remains standby.)
b. Reseat the Slot 10 cross-connect card to activate the Slot 8 card and make Slot 10 standby.
c. Verify that the CTNEQPT-PBWORK condition has cleared on all I/O cards.
Step 9 If you see CTNEQPT-PBPROT reported against all I/O cards in the node, this indicates that the Slot 10 card has a bad oscillator. If so, complete the following steps:
a. Replace the Slot 10 cross-connect card with a spare card. (The Slot 8 card is now active.)
b. Reseat the Slot 8 cross-connect card to make Slot 10 active.
c. Verify that the CTNEQPT-PBPROT condition has cleared on all I/O cards.
2.3.17.2 Resolve the XC Oscillator Failure When Slot 10 XC Card is Active
Step 1 If the CTNEQPT-PBWORK condition is reported against all I/O cards in the node and the Slot 10 card is active, right-click the Slot 8 cross-connect card.
Step 2 Choose Reset Card and click OK. (Slot 10 remains active and Slot 8 remains standby.)
Step 3 If the CTNEQPT-PBWORK condition does not clear, reseat the Slot 8 cross-connect card.
Step 4 If the condition does not clear, replace the Slot 8 cross-connect card with an identical, spare card.
Step 5 If the condition does not clear, replace the spare card placed in Slot 8 with the original cross-connect card.
Step 6 Right-click the Slot 10 cross-connect card.
Step 7 Choose Reset Card and click OK. The Slot 8 cross-connect card becomes active and Slot 10 becomes standby.
Step 8 If you have switched the Slot 8 card to active and continue to see CTNEQPT-PBWORK reported against all I/O cards in the node, this indicates the Slot 8 card has a bad oscillator. If this is indicated, complete the following substeps. If not, go to Step 9.
a. Replace the Slot 8 cross-connect card with a spare card. (The Slot 10 card is made active.)
b. Reseat the Slot 10 cross-connect card to make Slot 8 active.
c. Verify that the CTNEQPT-PBWORK condition has cleared on all I/O cards.
Step 9 If you then see the CTNEQPT-PBPROT condition raised against all I/O cards, verify that CTNEQPT-PBWORK has cleared on the I/O cards. This indicates that Slot 10 has a bad oscillator. If so, complete the following substeps:
a. Replace the Slot 10 cross-connect card with a spare card. (Slot 10 remains standby.)
b. Reseat the Slot 8 cross-connect card to activate the Slot 10 card and make Slot 8 standby.
c. Verify that the CTNEQPT-PBPROT condition has cleared on all I/O cards.
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 AIS-V on DS3XM-6 Unused VT Circuits
Symptom: An incomplete circuit path causes an alarm indications signal (AIS).
Table 2-19 describes the potential cause(s) of the symptom and the solution(s).
Table 2-19 Calculate and Design IP Subnets
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 virtual tributary (VT) layer. AIS-V alarms also occur on DS3XM-6 VT circuits that are not carrying traffic and on stranded bandwidth.
Perform the "Clear AIS-V on DS3XM-6 Unused VT Circuits" section.
|
2.4.1.1 Clear AIS-V on DS3XM-6 Unused VT Circuits
Step 1 Determine the affected port.
Step 2 Record the node ID, slot number, port number, or VT number.
Step 3 Create a unidirectional VT circuit from the affected port back to itself, such as Source node/Slot 2/Port 2/VT 13 cross connected to Source node/Slot 2/Port 2/VT 13.
Step 4 Uncheck the bidirectional box in the circuit creation window.
Step 5 Give the unidirectional VT circuit an easily recognizable name, such as delete me.
Step 6 Display the DS3XM-6 card in CTC card view. Click the Maintenance > DS1 tabs.
Step 7 Locate the VT that is reporting the alarm (for example, DS3 #2, DS1 #13).
Step 8 From the Loopback Type list, choose Facility (line) and click Apply.
Step 9 Click Circuits.
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 box.
Step 12 Display the DS3XM-6 card in CTC card view. Click Maintenance > DS1.
Step 13 Locate the VT in Facility (line) Loopback.
Step 14 From the Loopback Type list, choose None and then click Apply.
Step 15 Click the Alarm tab and verify that the AIS-V alarms have cleared.
Step 16 Repeat this procedure for all the AIS-V alarms on the DS3XM-6 cards.
2.4.2 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 2-20 describes the potential cause(s) of the symptom and the solution(s).
Table 2-20 Circuit Creation Error with VT1.5 Circuit
Possible Problem
|
Solution
|
You may have run out of bandwidth on the VT cross-connect matrix at the ONS 15454 indicated in the error message.
|
The matrix has a maximum capacity of 336 bidirectional VT1.5 cross-connects. Certain configurations will exhaust VT capacity with less than 336 bidirectional VT1.5s in a BLSR or less than 224 bidirectional VT1.5s in a UPSR or 1+1 protection group. Refer to the Cisco ONS 15454 Reference Guide for more information.
|
2.4.3 Unable to Create Circuit From DS-3 Card to DS3XM-6 Card
Symptom: You cannot create a circuit from a DS-3 card to a DS3XM-6 card.
Table 2-21 describes the potential cause(s) of the symptom and the solution(s).
Table 2-21 Unable to Create Circuit from DS-3 Card to DS3XM-6 Card
Possible Problem
|
Solution
|
A DS-3 card and a DS3XM-6 card have different functions.
|
A DS3XM-6 card converts each of its six DS-3 interfaces into 28 DS-1s for cross-connection through the network. Thus you can create a circuit from a DS3XM-6 card to a DS-1 card, but not from a DS3XM-6 card to a DS-3 card. These differences are evident in the STS path overhead. The DS-3 card uses asynchronous mapping for DS-3, which is indicated by the C2 byte in the STS path overhead that has a hex code of 04. A DS3XM-6 has a VT payload with a C2 hex value of 02.
Note You can find instructions for creating circuits in the Cisco ONS 15454 Procedure Guide.
|
2.4.4 DS3 Card Does Not Report AIS-P From External Equipment
Symptom: A DS3-12/DS3N-12/DS3-12E/DS3N-12E card does not report STS AIS-P from the external equipment/line side.
Table 2-22 describes the potential cause(s) of the symptom and the solution(s).
Table 2-22 DS3 Card Does Not Report AIS-P From External Equipment
Possible Problem
|
Solution
|
The card is functioning as designed.
|
This card terminates the port signal at the backplane so STS AIS-P is not reported from the external equipment/line side.
DS3-12/DS3N-12E cards have DS3 header monitoring functionality, which allows you to view performance monitoring (PM) on the DS3 path. Nevertheless, you cannot view AIS-P on the STS path. For more information on the PM capabilities of the DS3-12E/DS3N-12E cards, refer to the Cisco ONS 15454 Procedure Guide.
|
2.4.5 OC-3 and DCC Limitations
Symptom: Limitations to OC-3 and DCC usage.
Table 2-23 describes the potential cause(s) of the symptom and the solution(s).
Table 2-23 OC-3 and DCC Limitations
Possible Problem
|
Solution
|
OC-3 and DCC have limitations for the ONS 15454.
|
For an explanation of OC-3 and DCC limitations, refer to the DCC Tunnels section of the Cisco ONS 15454 Procedure Guide.
|
2.4.6 ONS 15454 Switches Timing Reference
Symptom: Timing references switch when one or more problems occur.
Table 2-24 describes the potential cause(s) of the symptom and the solution(s).
Table 2-24 ONS 15454 Switches Timing Reference
Possible Problem
|
Solution
|
The optical or BITS input is receiving loss of signal (LOS), loss of frame (LOF), or AIS alarms from its timing source.
|
The ONS 15454 internal clock operates at a Stratum 3 level of accuracy. This gives the ONS 15454 a free-running synchronization accuracy of ± 4.6 ppm and a holdover stability of less than 255 slips in the first 24 hours or 3.7x10-7/day, including temperature.
ONS 15454 free-running synchronization relies on the Stratum 3 internal clock. Over an extended time period, using a higher quality Stratum 1 or Stratum 2 timing source results in fewer timing slips than a lower quality Stratum 3 timing source.
|
The optical or BITS input is not functioning.
|
Sync Status Messaging (SSM) message is set to Don't Use for Sync (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.
|
2.4.7 Holdover Synchronization Alarm
Symptom: The clock is running at a different frequency than normal and the HLDOVERSYNC alarm appears.
Table 2-25 describes the potential cause(s) of the symptom and the solution(s).
Table 2-25 Holdover Synchronization Alarm
Possible Problem
|
Solution
|
The last reference input has failed.
|
The clock is running at the frequency of the last known-good reference input. This alarm is raised when the last reference input fails. See the "HLDOVERSYNC" section on page 1-55 for a detailed description of this alarm.
Note The ONS 15454 supports holdover timing per Telcordia standard GR-4436 when provisioned for external (BITS) timing.
|
2.4.8 Free-Running Synchronization Mode
Symptom: The clock is running at a different frequency than normal and the FRNGSYNC alarm appears.
Table 2-26 describes the potential cause(s) of the symptom and the solution(s).
Table 2-26 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" section on page 1-54 for a detailed description of this alarm.
|
2.4.9 Daisy-Chained BITS Not Functioning
Symptom: You are unable to daisy-chain the BITS.
Table 2-27 describes the potential cause(s) of the symptom and the solution(s).
Table 2-27 Daisy-Chained BITS Not Functioning
Possible Problem
|
Solution
|
Daisy-chaining BITS is not supported on the ONS 15454.
|
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 ONS 15454.
|
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-28 describes the potential cause(s) of the symptom and the solution(s).
Table 2-28 Bit Errors Appear for a Line Card
Possible Problem
|
Solution
|
Faulty cabling or low optical-line levels.
|
Bit errors on line (traffic) cards usually originate from cabling problems or low optical-line levels. The errors can be caused by synchronization problems, especially if PJ (pointer justification) errors are reported. Moving cards into different error-free slots will isolate the cause. Use a test set whenever possible because the cause of the errors could be external cabling, fiber, or external equipment connecting to the ONS 15454. Troubleshoot cabling problems using the "Network Troubleshooting Tests" section. Troubleshoot low optical levels using the "Faulty Fiber-Optic Connections" section.
|
2.5.2 Faulty Fiber-Optic Connections
Symptom: A line card has multiple SONET alarms and/or signal errors.
Table 2-29 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.
2.5.2.1 Verify Fiber-Optic Connections
Step 1 Ensure that a single-mode fiber connects to the ONS 15454 OC-N card.
SM or SM Fiber should be printed on the fiber span cable. ONS 15454 OC-N cards do not use multimode fiber.
Step 2 Ensure that the connector keys on the SC fiber connector are properly aligned and locked.
Step 3 Check that the single-mode fiber power level is within the specified range:
a. Remove the receive (Rx) end of the suspect fiber.
b. Connect the 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 the power meter is set to the appropriate wavelength for the optical card being tested (either 1310 nm or 1550 nm depending on the specific card).
e. Verify that the power level falls within the range specified for the card; see the "Optical Card Transmit and Receive Levels" section.
Step 4 If the power level falls below the specified range:
a. Clean or replace the fiber patch cords. If possible, do this for the OC-N card you are working on and the far-end card.
b. Clean the optical connectors on the card. If possible, do this for the OC-N card you are working on and the far-end card.
c. Ensure that the far-end transmitting card is not an ONS intermediate range (IR) card when an ONS long range (LR) card is appropriate.
IR cards transmit a lower output power than LR cards.
d. Replace the far-end transmitting OC-N card to eliminate the possibility of a degrading transmitter on this OC-N card.
Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 Procedure Guide for information.
e. If the power level still falls below the specified range with the replacement fibers and replacement card, check for one of these three factors that attenuate the power level and affect link loss (LL):
–Excessive fiber distance; single-mode fiber attenuates at approximately 0.5 dB/km.
–Excessive number or fiber connectors; connectors take approximately 0.5 dB each.
–Excessive number of fiber splices; splices take approximately 0.5 dB each.
Note These are typical attenuation values. Refer to the specific product documentation for the actual values or use an optical time domain reflectometer (OTDR) to establish precise link loss and budget requirements.
Step 5 If no power level shows on the fiber, the fiber is bad or the transmitter on the optical card failed.
a. Check that the Transmit (Tx) and Receive (Rx) fibers are not reversed. LOS and EOC alarms normally accompany reversed Tx and Rx fibers. Switching reversed Tx and Rx fibers clears the alarms and restores the signal.
b. Clean or replace the fiber patch cords. If possible, do this for the OC-N card you are working on and the far-end card.
c. Retest the fiber power level.
d. If the replacement fiber still shows no power, replace the optical card.
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 OC-N card.
Receiver overloads occur when maximum receiver power is exceeded.
Tip To prevent overloading the receiver, use an attenuator on the fiber between the ONS OC-N card transmitter and the receiver. Place the attenuator on the receive transmitter of the ONS OC-N cards. Refer to the attenuator documentation for specific instructions.
Tip Most fiber has text printed on only one of the two fiber strands. Use this to identify which fiber is connected to Tx and which fiber is connected to Rx.
2.5.2.2 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 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-16 shows a GBIC.
Figure 2-16 A gigabit interface converter (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 1 Disconnect the network interface fiber-optic cable from the GBIC SC connector and replace the protective plug.
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.
Note GBICs are keyed to prevent incorrect installation.
Figure 2-17 Installing a GBIC on the E1000-2/E1000-2-G card
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.
2.5.2.3 Crimp Replacement CAT-5 Cables
You can crimp your own CAT-5 cables for use with the ONS 15454. Use a cross-over cable when connecting an ONS 15454 to a hub, LAN modem, or switch, and use a straight-through cable when connecting an ONS 15454 to a router or workstation. Use CAT 5 cable RJ-45 T-568B, Color Code (100 Mbps), and a crimping tool. Figure 2-18 shows the layout of an RJ-45 connector. Figure 2-19 shows the layout of a straight-through cable and Figure 2-20 shows the layout of a cross-over cable.
Figure 2-18 RJ-45 pin numbers
Figure 2-19 A straight-through cable layout
Table 2-30 Straight-through 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 2-20 A cross-over cable layout
Table 2-31 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.
2.5.3 Optical Card Transmit and Receive Levels
Each OC-N card has a transmit and receive connector on its faceplate.
Table 2-32 Optical Card Transmit and Receive Levels
Optical card
|
Rx
|
Tx
|
OC3 IR 4/STM1SH 1310
|
-8 to -28 dBm
|
-8 to -15 dBm
|
OC12 IR/STM4 SH 1310
|
-8 to -28 dBm
|
-8 to -15 dBm
|
OC12 LR/STM4 LH 1310
|
-8 to -28 dBm
|
+2 to -3 dBm
|
OC12 LR/STM4 LH 1550
|
-8 to -28 dBm
|
+2 to -3 dBm
|
OC12/STM4-4
|
-8 to -28 dBm
|
+2 to -3 dBm
|
OC48 IR 1310
|
0 to -18 dBm
|
0 to -5 dBm
|
OC48 LR 1550
|
-8 to -28 dBm
|
+3 to -2 dBm
|
OC48 AS LR 1550
|
-8 to -28 dBm
|
+3 to -2 dBm
|
OC48 ELR DWDM
|
-8 to -28 dBm
|
0 to -2 dBm
|
OC192 LR 1550
|
-9 to -17 dBm
|
+10 to +7 dBm
|
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-33 describes the potential cause(s) of the symptom and the solution(s).
Table 2-33 Power Supply Problems
Possible Problem
|
Solution
|
Loss of power or low voltage.
|
The ONS 15454 requires a constant source of DC power to properly function. Input power is -48 VDC. Power requirements range from -42 VDC to -57 VDC.
A newly installed ONS 15454 that is not properly connected to its power supply will not operate. Power problems can be confined to a specific ONS 15454 or affect several pieces of equipment on the site.
A loss of power or low voltage can result in a loss of traffic and causes the LCD clock on the ONS 15454 to default to January 1, 1970, 00:04:15. To reset the clock, in node view click the Provisioning > General tabs and change the Date and Time fields.
See the "Isolate the Cause of Power Supply Problems" section.
|
Improperly connected power supply.
|
Caution Operations that interrupt power supply or short the power connections to the ONS 15454 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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
2.6.1.1 Isolate the Cause of Power Supply Problems
Step 1 If a single ONS 15454 show signs of fluctuating power or power loss:
a. Verify that the -48 VDC #8 power terminals are properly connected to a fuse panel. These power terminals are located on the lower section of the backplane EIA under the clear plastic cover.
b. Verify that the power cable is #12 or #14 AWG and in good condition.
c. Verify that the power cable connections are properly crimped. Stranded #12 or #14 AWG does not always crimp properly with Staycon type connectors.
d. Verify that 20A fuses are used in the fuse panel.
e. Verify that the fuses are not blown.
f. Verify that a rack-ground cable attaches to the frame-ground terminal (FGND) on the right side of the ONS 15454 EIA. Connect this cable to the ground terminal according to local site practice.
g. Verify that the DC power source has enough capacity to carry the power load.
h. If the DC power source is battery-based:
–Check that the output power is high enough. Power requirements range from -42 VDC to -57
VDC.
–Check the age of the batteries. Battery performance decreases with age.
–Check for opens and shorts in batteries, which may affect power output.
–If brownouts occur, the power load and fuses may be too high for the battery plant.
Step 2 If multiple pieces of site equipment show signs of fluctuating power or power loss:
a. Check the uninterruptible power supply (UPS) or rectifiers that supply the equipment. Refer to the UPS manufacturer's documentation for specific instructions.
b. Check for excessive power drains caused by other equipment, such as generators.
c. Check for excessive power demand on backup power systems or batteries when alternate power sources are used.
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-34 describes the potential cause(s) of the symptom and the solution(s).
Table 2-34 Power Consumption for Node and Cards
Possible Problem
|
Solution
|
Improper power supply.
|
Refer to power information in the Cisco ONS 15454 Procedure Guide.
|
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-35 describes the potential cause(s) of the symptom and the solution(s).
Table 2-35 Lamp Test for Card LEDs
Possible Problem
|
Solution
|
Faulty LED
|
A lamp test verifies that all the card LEDs work. Run this diagnostic test as part of the initial ONS 15454 turn-up, a periodic maintenance routine, or any time you question whether an LED is in working order.
See the "Verify Card LED Operation" section.
|
2.6.3.1 Verify Card LED Operation
Step 1 Click the Maintenance > Diagnostic tabs.
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 light up, the LED is faulty. Call the Cisco TAC at 1-877-323-7368 and fill out an RMA to return the card.
