User guide

C-73
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
Defect Information—Collect the following information for further analysis:
• Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory.
• Collect screen snapshots. In particular, error/information message dialog boxes.
• Collect Java Console information (In particular any java raised exceptions).
• Collect cmsvr.log file under the /opt/svplus/log directory.
• Collect configserver.log file under the /opt/svplus/log directory.
Possible alternative workaround—None
C.9.2.2 Connection Template Creation/Modification/Deletion/Retrieval Errors
When performing any connection template creation/modification/deletion/retrieval the CM Server could
encounter an error and notify the Configuration Center by throwing an application exception error that
contains information describing the error. As a result, the Configuration Center will display the error
message. The following lists some CM Server related connection template exceptions.
CONN_TEMPLATE_ALREADY_PRESENT: "The Connection Template[%s] is already present in the
conn_template table";
CONN_TEMPLATE_NOT_PRESENT: "The Connection Template[%s] is not present in the
conn_template table";
CONN_TEMPLATE_TABLE_INCONSISTENT: "The Connection Template table contains more than
one entry for the template[%s]";
CONN_TEMPLATE_PARAMS_NOT_PRESENT: "The Connection Template[%s] is not present in the
conn_templ_param table";
DATABASE_ERROR:"Database error [%s]."
UNKNOWN_EXCEPTION: "Program Error. Unknown Exception is caught in [%s]."
SUBSYSTEM_EXCEPTION:"Program Error. Subsystem exception [%s] caught in [%s]"
INTERNAL_ERROR: "Program or System Error. Function [%s] reports: [%s]"
Step 1 Verify that the CM Server and databroker are up and running by perform a "psg sdbroker", "psg
xdbroker" and "psg cmserver" on the command line.
Step 2 Verify if the CM Server re-started while the operation was being done by checking the cmsvr.log and
searching for the string "START OF THE PROCESS". Verify the timestamp if the server process was
either re-started while the operation was being performed. Also check for any cmsvr coredumps under
/opt/svplus/corefilesdir/