C-89
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
C.9.4.4.1 Cmgrd—Addition/Modification Errors. Provisioning a Connection Results in a Switch Error "Agent reported bad/wrong
value for one of the variables in the request."
Related key index entries: cmgrd, bad value
When any Connection Add or Mod request is issued, an SNMP VarBind is SET on the switch via cmgrd.
The switch can reject this VarBind with the above error.
The reason for the error is that cmgrd sent an invalid value for one of the mib objects. The Cisco MGM
DE should do the investigation for this error, as it indicates that there is a problem in the data that cmgrd
either received from the clients or internally mapped from the other side of the connection.
The user should try the same connection from both Connection Proxy and CmGui interface and note the
behavior from both of the clients. If the provisioning result from both clients is the same, it tends to
indicate that this is either a cmgrd issue or a sdbroker vpi/vci issue.
Defect Information—The cmgrd.log, ConnProxy*, cmsvr.log and sdbroker*.logs should be collected.
Possible alternative workaround—If the user is doing a Add, and default values are being used, then
there is no work around. But, if the user is doing a MOD and then the user could change the value of the
Object that is being modified and retry the connection.Also if this is a sdbroker vpi/vci issue, retry the
connection as sdbroker does not re-use the previous vpi/vci combination.
C.9.4.4.2 Cmgrd—Addition Errors. Provisioning a Connection Results in a Switch Error "Object Exists on the Agent or Specified
VPI/VCI not available".
Related key index entries: cmgrd, object exists
When any Connection Add request is issued, an SNMP VarBind is SET on the switch via cmgrd. The
switch can reject this VarBind and the subsequent cmgrd query to switch error table can return the above
errors.
The reason for the error is that the connection that Cisco MGM is trying to Add already exists on the
switch. This could be a user endpoint or an intermediate endpoint.
Step 1 The user should retry the same connection, if this second attempt succeeds it indicates that the
intermediate endpoints vpi/vci was already present on the switch. If this is the case look at the
cmgrd-sdbroker error "EndPoint Exists Local/Remote/Both end of the connection already exists".
Step 2 If on the second attempt the switch still returns the same error. Then this has to be debugged by a
Cisco MGM DE, as it could indicate an inconsistency between the Cisco MGM database and the Switch.
Defect Information—Save the cmgrd.log, ConnProxy*.log, cmsvr.log and sdbroker*.log.
Possible alternative workaround—Retrying the connection addition more than once, if that still fails a
Cisco MGM DE has to look into the issue.
Comments to this Manuals