User guide

C-80
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
The Connection subsystem comprises the following modules:
• ConnProxy—Is the SNMP Agent Interface for Connection Management, client to cmgrd.
• CmServer—Provides the backend functionality to the Connection Management GUI, client to
cmgrd.
• Cmgrd—Is the backend module which accepts requests from ConnProxy, CmsServer Clients and
issues the SNMP Varbinds to the Switch for Addition, Modification and Deletion. Subsequently
cmgrd informs sdbroker after an ADD/MOD/DEL operation for the status of the particular request,
upon which sdbroker updates the Cisco MGM database.
The following errors are applicable to all types of connections PVC, SPVC, XPVC, and Hybrid.
C.9.4.2 Cmgrd - Sdbroker Errors
During an Addition request cmgrd could return errors which cmgrd has received from sdbroker, the
following are some of the most common errors seen when a Provisioning request is issued.
This section includes the following information:
• C.9.4.2.1 Cmgrd—Sdbroker Addition/Modification/Deletion Errors. Adding a Connection Results
in an Error "Fail to Communicate with sDatabroker"
• C.9.4.2.2 Cmgrd—Sdbroker Addition/Modification/Deletion Errors. Provisioning a Connection
Results in an Error "sDatabroker process busy. Please retry"
• C.9.4.2.3 Cmgrd—Sdbroker Addition Errors. Adding a Connection Results in an Error "MGM
syncup in progress".
• C.9.4.2.4 Cmgrd—Sdbroker Addition Errors. Adding a Connection Results in an Error "No more
vpi/vci available for local trunk end".
• C.9.4.2.5 Cmgrd—Sdbroker Addition Errors. Adding a Connection Results in an Error "EndPoint
Exists Local/Remote/Both end of the connection already exists.".
• C.9.4.2.6 Cmgrd—Sdbroker Modification/Deletion Errors. Modifying or Deleting a Connection
Results in an Error "sDatabroker Could not lock connection entry.".
C.9.4.2.1 Cmgrd—Sdbroker Addition/Modification/Deletion Errors. Adding a Connection Results in an Error "Fail to Communicate
with sDatabroker"
Related key index entries: cmgrd, sdbroker
When any Connection Add/Mod/Del request is made, cmgrd checks its ILOG connection with
sDatabroker. The above error will result when cmgrd could not verify that sdbroker is available for
servicing requests. In other words the ILOG connection between them is broken.
The problem must be researched on the sdbroker side.
Step 1 Verify that the sdbroker is up and running. Do a "psg sdbroker" on the command line.
Step 2 View the sDbroker log for ilog errors There could be multiple sdbrokers running on the machine, the
way to check which sdbroker cmgrd talked to for that particular request is as follows.
a. vi the cmgrd.log file, and go to the very end of the file. Then do a backward search for the string
sdbroker, that string should indicate the number (#) of the sdbroker that cmgrd could not talk to.
b. Do a "psg sdbroker" and then check the corresponding log file of this sdbroker.