User guide

C-64
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Management - Elements
c. For a line, the window title will have <NodeName>.<SlotNumber>.<LineNumber>
d. For a port, the window title will have <NodeName>.<SlotNumber>.<PortNumber> and so on.
Step 2 With the information obtained from Step1, Check if that object is appearing in the tree view.
a. If it does appear, go to step 3.
b. If it doesn't appear, refresh the tabular view twice or thrice and check If the object still exists in the
tabular view and if it continues giving the same error, contact Cisco MGM engineers with
appropriate defect information
Step 3 If the object being launched is a node or card, check if that particular node or card is supported in the
Cisco MGM version being used. A list of supported nodes/cards can be found in product literature.
a. If the node or card is supported, go to step 4
Step 4 Open /opt/svplus/log/CMSCclient.log file and check whether the FDN of the object being launched is
matching with the information got from the Step1. Contact Cisco MGM engineers. A typical example of
the log is shown below.
[DD Mon YYYY HH:MM:SS] DEBUG - [appsConfigCenter] :: CcElementInternalFrame :
modifyActionPerformed()
[DD Mon YYYY HH:MM:SS] DEBUG - [appsConfigCenter] CcTabularView : modify()
[DD Mon YYYY HH:MM:SS] INFO - [appsConfigCenter] Selected fdn =
/NW=X/RND=XX/CD=X/LN=X/PT=X
Defect Information—Collect the following information for further analysis:
• Collect CMSCclient.log file under the D:\Documents and Settings\<username>og folder
• Collect Java Console information.
• Contents of /opt/svplus/log/configserver.log file.
Possible alternative workaround—None
C.8.2.7 Element Data Inconsistent With Switch
Information displayed in the GUI and Switch are not same.
Step 1 First Make sure that the window has been launched for the correct element in the GUI. If yes, go to step
2, else contact Cisco MGM engineers with the defect information.
Step 2 SSH or Telnet to the Switch and change few parameters and check if the change is reflecting in the GUI.
If so, go to step3, else contact Cisco MGM engineers.
Step 3 Open /opt/svplus/log/configserver.log file and find the MIB OID of the element which displays
inconsistent data.
Step 4 Check if the MIB OID is pointing to correct information that the user is looking for. If they are correct
go to step 5, otherwise Contact Cisco MGM engineers.
Step 5 Perform a SNMP GET operation on the MIB object which shows inconsistent data using any SNMP tool.
If the value got via SNMP GET operation and that is shown in the GUI are same go to step 6: , else
contact Cisco MGM engineers. Syntax of SNMP GET operation in a HP-OV is shown below.
snmpget [-Cf] [options...] <hostname> {<community>} [<objectID> ...]