Appendix J Troubleshooting
J.2.10
Step 6 Verify that the NE is reachable during the duration that PM data is collected. If the NE is not reachable, there is an entry in the Audit Log table (Administration > Audit Log).
J.2.10 CTC-Based NE Is Not Discovered
Step 1 Verify that the NE is up and running.
Step 2 Verify that the NE IP address and default route are configured correctly.
Step 3 To verify that the NE is running the correct version of system software, open a CTC session to the NE and check the NE software version.
Step 4 Verify that the NE that acts as the gateway NE (GNE) (through which this node is discovered) is added to CTM and is available.
Step 5 Open CTC from the GNE and see if CTC can discover the NE.
J.2.11 CTC-Based NE Is Not Reachable
Step 1 Verify that the NE is up and running.
Step 2 Verify that the NE IP address and default route are correctly configured.
Step 3 Wait for five poll cycles while CTM reestablishes connectivity with the NE.
Step 4 To test IP connectivity to the NE from the CTM server, enter the following command from the Solaris workstation running CTM:
ping <NE_IP_address>
Step 5 To verify that the NE is running the version of system software supported by CTM, open a CTC session to the NE and check the NE software version.
Step 6 Verify that the username and password that CTM uses to reach the NE exist on the NE.
J.2.12 ONS 15501, ONS 15540, or ONS 15530 Is Not Reachable
Step 1 Enter the following command on the server to verify IP connectivity between the server and the NE:
ping <NE_IP_address>
Step 2 If the NE is reachable through IP, verify that the correct read community string is configured on the server.
•On the server, choose Administration > ONS 155XX > ONS 155XX SNMP Settings Table to view the community strings set in CTM.
•On the NE, enter the following command to view the read community string set on the NE:
show run begin SNMP
Cisco Transport Manager Release 6.0 User Guide
|
| ||
|
|