user manual

J-34
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10 Problems with MGX Voice Gateway Devices
On UNIX, enter the <CTM_home>/bin/ctmcdebug-start command to start the client and repeat the
same operation. This generates the error and exception messages on the terminal. Capture the terminal
messages for debugging.
J.10 Problems with MGX Voice Gateway Devices
This section describes troubleshooting procedures for problems related to the MGX Voice Gateway
devices.
J.10.1 Discovery Mechanism
CTM manages the Private Network-Network Interface (PNNI). The ILMITopoc process uses SNMP
protocol to discover the physical PNNI network. All the discovered nodes are displayed in the MGX NE
GUIs (Configuration Center, Diagnostics Center, Statistics Report, and Chassis View). CTM is notified
of all subsequent changes in the network through traps for MGX nodes.
Once the ILMITopoc process discovers all the nodes, it sends all the nodes to the topod process. Topod
then sends these nodes and trunks to other processes in CTM such as ooemc, NMServer, nts, and so on.
J.10.2 Discovery Issues at Startup
This section includes the following information:
• J.10.2.1 No Nodes Are Discovered, page J-34
• J.10.2.2 Node Name Is Incorrect in the Database, page J-35
• J.10.2.3 Node IP Is Incorrect in the Database, page J-36
• J.10.2.4 Node Alarm Is Shown Incorrectly in the Database, page J-36
• J.10.2.5 Reachable Node Is Shown as Unreachable, page J-37
• J.10.2.6 CTM State Is Incorrect, page J-37
J.10.2.1 No Nodes Are Discovered
If no nodes are in the CTM database, complete the following steps:
Step 1 Verify that the nodes are IP-reachable. Complete the following substeps:
a. Enter the following CLI commands to retrieve the primary IP address of the node:
dspndparms
dspipif
b. Enter the following command to check whether CTM has IP connectivity to the node:
ping <node_IP_address>
Step 2 If CTM has IP connectivity to the nodes, verify that the community strings of the gateway nodes are
correct. Complete the following substeps:
a. Enter the following command on the switch CLI of the node that cannot be discovered:
dspsnmp