User guide

C-83
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
Defect Information—If the switch and DMD cache are not in sync, we will need the DMD logs and
message logs, dmd cache dump and the EM logs for the node in question. We will also need the switch
CLI screen shot of the connection in question.
Possible alternative workaround—If there is a cache inconsistency, the only work around is a complete
cache resync(/opt/svplus/tools/CacheResync). If there is no DMD cache inconsistency, it is a normal
operational scenario. Different connection add parameters should be chosen.
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.".
Related key index entries: cmgrd, sdbroker, endpoint exists
During a connection add, the cmgrd will request intermediate endpoint vpi/vci from sdbroker. If the
sdbroker incorrectly chooses endpoints that are already in use by the switch the cmgrd will try to
provision these endpoints and return the error "endpoint exists" to the user.
Step 1 Determine which of the endpoints already exist on the switch. If it is the intermediate endpoints then it
is a databroker problem.
a. When provisioning hybrid connections the CMGRD requests intermediate endpoints from the
sDbroker. The sDbroker then requests them from DMD and then forwards them back to CMGRD.
First identify the DMD which is to process the node use /opt/svplus/tools/dbcmap command. Then
dump that dmd's cache. Verify that the DMD does not contain the end points in question in it's cache.
b. We now need to determine why the dmd doesn't have the information on endpoints that exist on a
switch. We first need to determine if the EM sent the add message to the DMD. See
C.15.2.1 Connection Inconsistency Between the Switch and GUI . If the add message is not found
and the logs do not go back to coldstart, then we will need to check to see if EM has done any
processing of this endpoint. Check for the endpoint in the xxx_Connection table. If the endpoint is
not there, check the EM to determine why it didn't process the endpoint. If the endpoint is in the
xxx_connection table we know that EM processed it, but we don't know if it forwarded it to DMD.
Defect Information:
• If the problem is an intermediate endpoint and it is on the switch but EM didn't process it or didn't'
send the message to DMD. Check the EM log, nts log from the /opt/svplus/log
• If the problem is within the DMD we ill need the dmd logs, dmd message logs and the dmd cache
dump.
Possible alternative workaround—None