Cisco Systems 78-16845-01 J.10.8.2.2 Connection Template Creation, Modification, Deletion, and Retrieval Errors

J-89
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.8 Connection Ma nagement Problems
Step 1 Verify that the CM Server and sdbroker are up and running by entering psg sdbroker and psg cmserver
on the command line.
Step 2 Verify if the CmServer restarted while the operation was being done by checking the cmsvr.log and
searching for the string "START OF THE PROCESS". Verify that the time stamp of the server process
was restarted while the operation was being performed. Also check for any cmsvr coredumps under the
/opt/svplus/corefilesdir/ directory.
Defect Information—Collect the following information for further analysis:
•CMSCclient.log file under the D:\Documents and Settings\<username>\log directory.
•Java Console information; in particular, any Java-raised exceptions.
•Screen snapshots; in particular, error/information messages dialog boxes.
•Cmsvr.log file under the /opt/svplus/log directory.
•Configserver.log file under the /opt/svplus/log directory.
Possible alternative workaround—None.
J.10.8.2.2 Connection Template Creation, Modification, Deletion, and Retrieval Errors
When performing any connection template creation, modification, deletion, and 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 displays 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, sdbroker, and xdbroker are up and running by entering psg sdbroker,
psg xdbroker, and psg cmserver on the command line.
Step 2 Verify if the CM Server restarted while the operation was being done by checking the cmsvr.log and
searching for the string "START OF THE PROCESS". Verify that the time stamp of the server process
was restarted while the operation was being performed. Also check for any cmsvr coredumps under the
/opt/svplus/corefilesdir/ directory.
Defect Information—Collect the following information for further analysis: