User guide

C-60
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Management - Elements
This section includes the following information:
• C.8.2.1 XML Parsing Error
• C.8.2.2 SNMP No Data Error
• C.8.2.3 Details/Create/Delete/Refresh Buttons Are Not Enabled (highlighted)
• C.8.2.4 SNMP Timeout Error
• C.8.2.5 SNMP Set Error
• C.8.2.6 Object Not Found In Tree View Error
• C.8.2.7 Element Data Inconsistent With Switch
• C.8.2.8 Config Server Reported Error Messages
C.8.2.1 XML Parsing Error
XML Parsing error is seen while launching a Configuration Center GUI (either by drag and drop method
or right-lick method) for a network element. The pop-up window says "Internal Error: XML Parsing
Error". The diagram below shows the error message dialog box:
Check if the network element which resulted in this error is supported in the Cisco MGM version being
used. A list of the supported nodes/cards can be found in Reference
If this error is seen for a supported node/card go to step 2:
Step 1 Open /opt/svplus/log/configserver.log file and look for the message information when this error
occurred.
a. A typical message in the log looks like this:
ERR: Fatal Error at file, line 0, char 0, Message: An exception occurred! Type:RuntimeException,
Message:The primary document entity could not be opened.
Id=/opt/svplus/xml/configcenter/XXX/XXX-XXX.xml
( <someNumber>: <x>) <someTimeStamp> ERR: InternalError: XML Parsing Error
b. If the .xml file name mentioned above has two consecutive hyphens (example: ABC--XYZ.xml), or
if it has a preceding hyphen (example: -ABC.xml) or terminates with hyphen before the file
extension (example: ABC-.xml) proceed to step 3, where investigating incorrectly formed XML file
names is discussed.
c. Check if the .xml mentioned in the log message (as shown in the above step) exists. If it does not
exist, contact Cisco MGM engineers.
Step 2 This step is to investigate incorrectly formed XML file name strings. As a first note, the format of XML
file names is <Platform>-<Card>-<InterfaceType>-<SomeEntityName>.xml. This format is generic
with a few exceptions. Also note that Platform, InterfaceType are optional and will not be seen for many
files (example: ABC-Card.xml is a valid XML file name).
a. If the Platform part of the XML file name is incorrect/missing, check the NODE table to see if it is
correctly populated.
b. If the Card part of the XML file name is incorrect/missing, check the CARD table to verify if it is
correctly populated.
c. If the InterfaceType part of the XML file name is incorrect/missing, check the appropriate table to
verify if it is correctly populated.This table generally corresponds with the line/port table of the card
for which this error is noticed.