User guide

C-86
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
Defect Information:
• If after re-issuing the request and still getting the same time-out error than collect the cmgrd.log and
snmpcomm .log.
• And if after warm-starting the snmpcomm process does not run, then collect the watchdog.log file.
Possible alternative workaround—Re-issue the request after some time, this interval could enable
snmpcomm to clear its pending requests. Do a warm-start to ensure that the snmpcomm process starts up.
C.9.4.3.3 Cmgrd—Addition/Modification/Deletion Errors. Provisioning a Connection Results in an Error "Outstanding request
exists for same object."
Related key index entries: cmgrd, outstanding request
When any Connection Add/Mod/Del request is made, cmgrd process these requests in a multi-threaded
manner. Sometimes a request can take greater than 3 minutes to process, because of the different
scenarios that the switch responds with (i.e. timeouts.). If the request takes greater than 3 minutes from
the CMGui, then the GUI will time-out and indicate this to the user. And from the Connection Proxy
path the time-out value is 2 minutes, subsequently it will indicate a time-out error to the user.
The tendency of the user will be to re-issue this request immediately, upon which cmgrd could return
the error "Outstanding requests exists for the same object".
The reason that error is returned is because cmgrd is still processing the initial request which the clients
(CMGui and Connection Proxy) timed out on. An ideal case for this would be when a switch time-out is
received for a multi-segment case, and cmgrd is still busy backing-off other segments and waiting for
the time-out response of some other segments. Just to be sure that cmgrd is still running, issue the
following commands.
Step 1 Issue the command "psg cmgrd" to ensure that the process is indeed running.
Step 2 Check for cmgrd coredumps in the corefilesdir directory. If there indeed was a coredump collect the
corefile.
Step 3 Do a "tail -f cmgrd.log in the logs directory to see if cmgrd is processing requests."
Re-issue the request after waiting for few minutes.
Defect Information—If after re-issuing the request and still getting the same error than collect the
cmgrd.log.
Possible alternative workaround—Re-issue the request after some time, this interval could enable cmgrd
to clear its pending request.
C.9.4.3.4 Cmgrd—Addition/Modification/Deletion Errors. Provisioning a Connection Results in an Error "Fatal error, IOSMGR is
not running, may need to be manually started"
Related key index entries: cmgrd, iosmgr
When any Connection Add/Mod/Del. request is made with a Popeye1 RPM Card, cmgrd issues a request
to the switch, but the request is actually first issued to the process iosmgr. Which in turn sends the
request to the node, via an expect script session In this scenario the above error can be returned when
cmgrd could not talk to iosmgr via the ILOG Communication.