Cisco Systems 78-16845-01 J.10.9.2.1 XML Parser Error , J.10.9.2.2 SNMPCOMM_TIMEOUT Error While Polling MIB Objects

J-113
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.9 Diagnostics Center Problems
J.10.9.2.1 XML Parser Error
The XML parsing error is seen while launching the Diagnostics Center (either by the drag-and-drop
method or the right-click method) for a network element. The popup window says "Internal Error: XML
Parsing Error."
Step 1 Verify whether the entity (node, card, line, or port) that caused this error is supported in the CTM version
being used. If this error is seen for a supported node/card, go to step 2.
Step 2 Open the /opt/svplus/log/DCServer.log file and look for the message information from 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/diagcenter/XXX/XXX-XXX.xml ( <someNumber>: <x>) <someTime Stamp>
ERR: InternalError: XML Parsing Error
b. If the .xml filename mentioned previously has two consecutive hyphens (for example:
ABC--XYZ.xml), or if it has a preceding hyphen (for example: -ABC.xml) or terminates with a
hyphen before the file extension (for example: ABC-.xml), proceed to step 3, where investigating
incorrectly formatted XML filenames is discussed.
c. See if the .xml file mentioned in the log message (as shown in the previous substep) exists under the
/opt/svplus/xml/diagcenter directory. If it does not exist, contact the CTM engineers with the defect
information.
Step 3 Perform the following substeps to investigate incorrectly formed XML filename strings. The format of
XML filenames is <Platform>-<Card>-<InterfaceType>-<SomeEntityName>.xml. This format is
generic with a few exceptions. Also note that Platform and InterfaceType are optional and will not be
seen in many files (for example: ABC-Card.xml is a valid XML filename).
a. If the Platform part of the XML filename is incorrect/missing, check the Node table to see if it is
correctly populated.
b. If the Card part of the XML filename is incorrect/missing, check the Card table to verify if it is
correctly populated.
c. If the InterfaceType part of the XML filename 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.
d. If the EntityName part of the XML filename is incorrect, contact the CTM engineers with the defect
information required.
Defect Information—Collect the following information for further analysis:
•Complete screen snapshots for the investigative commands used for debugging this issue.
•DCServer.log file from the log directory.
Possible alternative workaround—None.
J.10.9.2.2 SNMPCOMM_TIMEOUT Error While Polling MIB Objects
The Diagnostics Center shows an SNMP timeout error when polling real-time counters.
Step 1 Check the status of the node.