J-42
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
AppendixJ Troubleshooting
J.10.4 Equipment Management Problems
Step 3 If the rtm link up message for the node is found and the log indicates that notification to ooemc has been
sent, then collect the log files and report the problem.
Step 4 If the rtm link up message cannot be found, then search for link down message. Grep
RTM_LINK_DOWN from the emd log files. If the rtm link down message is found, then the node is not
reachable by the nts process. Check with the network administrator and see J.10.13.1 NTS, page J-127
if RTM_LINK_UP and RTM_LINK_DOWN messages are not found.
Defect information—Collect the following information for further analysis:
•Ooemc and nts log files from the /opt/svplus/log directory.
Possible alternative workaround—None.
J.10.4.4 Node Mode Remains in 2
After EMD receives the rtm link up message and the node active message has been sent to ooemc, ooemc
will change the node mode from 1 to 2 and trigger the node resync process. The node resync time varies
depending on the switch configuration and network activities. If the node mode stays in mode 2 for
longer than the normal time for node resynchronization, there can be a problem with the node resync
process.
Step 1 The debugging process for this problem is mainly focused on log file inspection. Make sure that log level
of all related CTM processes is set at the right level. See J.10.4.2 Network Setup and Configuration
Required for OOEMC Sync-Up Process, page J-41 for more information.
Step 2 Go to the /opt/svplus/tmp directory to check for configuration upload files.
Step 3 Determine which files have been uploaded for a node. For example, issue the following command on a
node with node_id=9:
ls -ltr *.9
If files have been uploaded for this node, then the node resync process is ongoing. Make sure that the
time stamps for these files refer to the current time.
Note Refer to step 6 for a list of configuration upload files.
Step 4 If there are no files uploaded for a node, it is possible that the trap IP address on the switch does not
match the IP address used for node discovery. It is also possible that an SNMP request failure occurred.
To check the IP addresses, perform the following:
a. Use the CLI command dbnds to display the IP address used for node discovery.
b. Use the CLI command dsptrapip to display the trap IP address.
c. If there is a mismatch, use the CLI command cnftrapip to reconfigure the trap IP address. Use the
IP address used by CTM for node discovery. See J.10.4.2 Network Setup and Configuration
Required for OOEMC Sync-Up Process, page J-41 for more information.
Step 5 If the trap IP address is not the issue, check whether there is an SNMP request failure. Normally, after
the node resync process is triggered, ooemc will send SNMP requests to the switch to start the
configuration upload file creation process. If the request fails, then ooemc will continue resending the
SNMP requests until it exceeds the maximum number of retries and declares node resync failure with
node mode equal to 5.