User guide

C-61
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Management - Elements
d. If the EntityName part of the XML file name is incorrect, contact Cisco MGM engineers, with the
Defect Information required (as given below).
Defect Information—Collect the following information for further analysis:
• Collect CMSCclient.log file under the D:\Documents and Settings\<username>\log folder
• Collect Java Console information.
• /opt/svplus/log/configserver.log
• "dspcd" command output from the switch for the controller card and the service module where this
error is detected.
• "dspln"/"dspport" command output, if this error seen for line/port.
Possible alternative workaround—None.
C.8.2.2 SNMP No Data Error
"SNMP NO DATA" error is seen while launching a Configuration Center GUI (either by drag and drop
method or right-lick method) for a network element.
Check if the element for which this error is noticed is active, and that the node is synced up fine (use
"selnd" command on the Cisco MGM machine. Check whether the correct community strings are being
used.If this error is noticed for a an properly synced up node, on an active element, proceed as follows:
Step 1 Use your favorite SNMP Manager tool to check if the switch is responding to SNMP queries.
The SNMP MIB objects to be queried for a particular dialog can be obtained from
.../svplus/log/configserver.log file. See the entries in this log file when this error occurs.
a. Using HP-OV SNMP operations we can perform a walk (on "system" MIB table for this example,
using public community string) as: /opt/OV/bin/snmpwalk -c public nodeName system
b. If an error is seen during the SNMP operations (from the SNMP manager tool), verify the switch to
cross-check if this information should really be present. If yes, proceed to Step 2.
Step 2 Collect the information from the .../svplus/log/configserver.log file when this error occurs.
a. From the configserver.log file identify the MIB objects that result in this error. Identify the MIB to
which these objects belong. Check if these MIB objects are supported from this release.
b. If the objects are supported, but still the SNMP agent is not responding for SNMP queries, get in
touch with Cisco MGM engineers for more information.
Defect Information—Collect the following information for further analysis:
• Collect all, complete screen snapshots for the investigative commands used for debugging this issue.
• .../svplus/log/configserver.log
• Related information on the switch.
Possible alternative workaround—None