Cisco Systems 78-16845-01 appendix 106

Appendix J Troubleshooting

J.10.8 Connection Management Problems

During an add or modify connection request, if the local endpoint’s remote parameters do not match the remote endpoint’s local parameters, then this error is indicated by the switch. The particular parameter depends on the service type of the connection.

Note This error cannot be easily debugged. I just has to be checked by a Connection Management DE, because the error indicates that the mapping of local to remote (and/or remote to local) has a problem in the value that is being set on the switch.

Step 1 Retry the connection from both the CM GUI 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 likely 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 retry the connection.

J.10.8.4.23 Cmgrd—Addition, Modification, and Deletion Errors: Provisioning a Connection Results in "Network Busy, try later" Switch Error

Related key index entries: cmgrd, network busy

During an add or modify connection request, if the switch returns this 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 this error will be returned. However, the operation is not backed off for a delete operation, because this is a destructive command.

There is no workaround for this error. You will have to wait and retry the request later. If you continue to receive the error after waiting and retrying multiple times, then the problem must be checked from the switch side.

Defect Information—Not applicable.

Possible alternative workaround—Wait and try the connection at a later time.

J.10.8.4.24 Cmgrd—Modification Errors: Modifying a Connection Results in "Connection does not exist in CproDb/Agent returned no such name" Switch Error

Related key index entries: cmgrd, cprodb

During a modify connection request, the switch could return this error when the connection is truly not present on the switch.

Check the connection in the user_connection table. From this entry, verify that all of the segments do exist on the switch CLI. If all segments are truly present in the switch CLI then the issue must be checked from the switch side. However, if any of the segments is not present on the switch, then this could be a sdbroker or EM issue.

Defect Information—If it is deemed a sdbroker or EM issue, collect the appropriate logs and cmgrd.log. If all of the segments of the connection are present on the switch and the switch still returns this error, contact the switch DEs.

Possible alternative workaround—None.

	Cisco Transport Manager Release 6.0 User Guide
J-106	78-16845-01