User guide

C-82
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
C.9.4.2.3 Cmgrd—Sdbroker Addition Errors. Adding a Connection Results in an Error "MGM syncup in progress".
Related key index entries: cmgrd, sdbroker, sync-up
While the system is in the process of syncing up, the user cannot provision connections. The user will
be returned the error "MGM syncup in progress"
We need to determine if the system is really in syncup or not. If the system is still syncing up then this
is proper operation.
Step 1 View the sync log located in /opt/svplus/log/.DBKR_SYNCHUP_MESSAGE (note the "." before the
filename). search for the last "xxx Start Begin at" line where xxx is ether 'Warm' or 'Cold'. Warm start
will take a short time compared to Coldstart which could take several hours. If there is a line at the end
of the file stating "Declare Syncup Complete" or "Warmstart Cache Rebuild Complete" then syncup is
done and there is a problem with dmd.
Step 2 If syncup is not complete, view the start time of syncup. Compare this to the maximum sync time
identified in the /usr/user/svplus/config/dmd.conf file next to the keyword
SYNCHUP_ALL_NODES_SYNC_WAIT_LIMIT. If the time taken to sync is larger than the time
identified in the dmd.conf file, then dmd has a problem.
Step 3 If the system is truly still syncing up, then the system behavior is correct.
Defect Information—If there is a DMD problem, save the dmd, cmgrd, sdbroker logs and message logs
along with the .DBKR_SYNCHUP_MESSAGE and .DMD_SYNCHUP_MESSAGE* files located in
the /opt/svplus/log directory.
Possible alternative workaround—The user can force the system to declare sync-up by sending the dmd
a forced sync signal. This will not place the nodes into mode '3' any faster, but will allow the user to
attempt provisioning some nodes, while other nodes are in the process of syncing up.
Step 1 Execute command 'selnd' from the cwm command line. Note the nodes in mode '3'. All connections
provisioned after forced sync-up can only go through nodes with mode = 3. (they actually can go through
specific cards on nodes in mode = 4, but let's stick with mode 3 nodes for now).
Step 2 Send the sync-up signal to the dmd by entering command "kill -ALRM dmd".
Step 3 view the .DBKR_SYNCUP_MESSAGE file for the sync-up completion.
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".
Related key index entries: cmgrd, sdbroker, vpi/vci
Provisioning fails and the error message is displayed.
"No more vpi/vci available for local trunk end" Also "Remote trunk"
"Local end of the connection already exists" Also 'Remote end" and "Both end"
"Vpcon already exists for Local Vpi" Also "Remote Vpi" and "Both ends"
Each of these error messages identifies the reason for the failure of provisioning. They sometimes can
be displayed in error. The reason is a mismatch between the switch and the DMD's cache. To find this
out, dump the DMD cache "pkill -USR1 dmd" and compare the values in the cache with those on the
switch for endpoint associated with the error.