User guide

C-91
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
C.9.4.4.5 Cmgrd—Addition Errors. Provisioning a Connection Results in a Switch Error "Local Channels not enough."
Related key index entries: cmgrd, channels
During a connection Addition request it is possible that the user endpoint port or card that the connection
is being SET on, has already reached its limit of allowable connections.
Check the port or card of the user endpoints on the CLI.
Step 1 Check the port resources of the endpoint via "dsppnportrsrc".
Step 2 If the number of LCNs is zero, delete some connections from this interface.
Step 3 After changing the configuration retry the connection request.
Defect Information—Not applicable, as the above error has to be a Switch Configuration issue.
Possible alternative workaround—Indicated in the Investigation part.
C.9.4.4.6 Cmgrd—Addition/Modification Errors. Provisioning a Connection Results in a Switch Error "Error in Traffic
Parameters."
Related key index entries: cmgrd, traffic parameters
During a connection Addition/Modification request if the local endpoints remote parameters do not
match the remote endpoints local parameters, then the above error is indicated by the switch. The
particular parameter depends on the Service type of the connection.
This error cannot be easily debugged it has to be looked at by a Connection Management DE. Because
the error indicates that the mapping of local to remote (and/or vice versa) has a problem in the value that
is being SET on the Switch.
Step 1 Retry the connection from both CMGUI and Connection Proxy interfaces.
Step 2 If the result from both the interfaces is the same this could be a cmgrd bug. If the request succeeds from
one of the interfaces then this is more possibly a Client issue.
Defect Information—Collect cmgrd.log, ConnProxy*.log and cmsvr.log.
Possible alternative workaround—Change some of the traffic parameter values in the connection request
and re-try the connection.
C.9.4.4.7 Cmgrd—Addition/Modification/Deletion Errors. Provisioning a Connection Results in a Switch Error "Network Busy, try
later"
Related key index entries: cmgrd, network busy
During a connection Addition/Modification request if the switch returns the above error, it indicates that
there is some CPU intensive activity happening on the Controller Card. The Cmgrd request will be
backed off the other segments and the error will be Returned to the user. But, for a Delete operation
(since it is a Destructive command) the operation will not be backed off.
The error has no work around, the user has to wait and try the request on the Switch later. If after waiting
and retrying multiple times and the error keeps repeating, then it has to be looked at from the Switch side.
Defect Information—Not applicable.
Possible alternative workaround—Wait and try the connection at a later time.