Appendix J Troubleshooting
J.9 XR 12000 Problems
J.9 XR 12000 Problems
This section describes troubleshooting procedures for problems related to the XR 12000.
J.9.1 Reporting XR 12000 Issues
When reporting an XR 12000 problem, include detailed steps to reproduce the problem and the software version(s) of the NE(s) to which the problem applies. Also, enter the following router CLI commands on the XR 12000 and collect the data:
show version show platform show inventory
show ipv4 interface brief show
show log events buffer
Turn on trace level debugging in the Control Panel for the service in question, wait until the problem occurs, and collect the GSRIOXNEService logs from /opt/CiscoTransportManagerServer/log.
J.9.2 CTM Cannot Discover an XR 12000 Node
Complete the following steps if CTM cannot discover an XR 12000 node:
Step 1 Verify that the NE is configured with “hfrems” as the username and “hfrems” as the password with
Step 2 Check whether the XML CORBA agent service is running. To configure the XML CORBA agent, enter:
Router(config)# xml agent corba [ssl]
Router(config)# commit
Note ssl is optional and enables SSL CORBA services.
If SSL CORBA services are activated, enter the following commands to check whether HTTP over SSL is running:
Router(config)# http server ssl
Router(config)# commit
Step 3 The CORBA agent on the router accepts connections only when using the hostname. Check to see if the
device IP address has an entry in DNS. If DNS is not used, add an entry in the /etc/hosts file.
Step 4 Verify that CTM supports the software version that is running on the router. The CTM release notes list the
Step 5 When an NE is added to CTM, the NE type is retrieved to verify whether the NE is an XR 12000. If the device is not of NE type XR 12000, the NE is moved to an LOC state in CTM and an NE type mismatch alarm is raised.
Cisco Transport Manager Release 6.0 User Guide
| ||
|
