2-14
Cisco ONS 15454 SDH Troubleshooting and Maintenance Guide, R3.3
May 2002
Chapter 2 General Troubleshooting
CTC Operation and Connectivity
d. Follow the installation procedure for the appropriate 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.
a. Clear the loopback circuit.
b. The entire E3-12 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 FMEC card.
a. Return the defective card to Cisco through the RMA process. Call the 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 open an RMA case.
b. Replace the faulty 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.
a. Clear the loopback circuit.
b. The entire E3-12 circuit path has now passed its comprehensive series of loopback tests. This circuit
qualifies to carry live traffic.
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).
Comments to this Manuals