Start a Conversation

Unsolved

This post is more than 5 years old

8020

August 30th, 2013 07:00

Client browsing failed with “Client refused browse request” message on Avamar GUI

Client browsing failed with “Client refused browse request” message on Avamar GUI


Symptom

I have added a new Avamar client to Avamarserver. But when I try to back up the client and define dataset on Avamar GUI, the browsing failed and an error window popped up with below error messages:

Error messages:

Client refused browse request. (6207)Message intended for Client '21eac08f9ac3dc432e7056e671b63d2fc51e8eb0' received incorrectly at agent on xqd1:xx.xx.x.xx(58a5fdfcd52f0c579228fb860a7fc695d821e3ba) currently registered to 'xx.xx.x.xx'

Also I saw two similar clients on Avamar GUI, one with the long name and one with the short name.

So, how can I resolve the issue to complete the client backup?

Solution

From error messages above, it is a cid mismatch issue due to multiple clients with the same name, one has a long name and the other has a short name.

If check avagent.log of client, you will see similar error messages as following:

2012-06-27 09:32:29 avagent Info <5964>: Requesting work from xx.xx.x.xx

2012-06-27 09:32:29 avagent Info <5264>: Workorder received: sleep

2012-06-27 09:32:29 avagent Info <5996>: Sleeping 1884 seconds

2012-06-27 09:32:38 avagent Warning <6229>: Mismatching CIDs - '21eac08f9ac3dc432e7056e671b63d2fc51e8eb0' vs. '58a5fdfcd52f0c579228fb860a7fc695d821e3ba'

2012-06-27 09:32:38 avagent Warning <6209>: Invalid browse request (mismatched cids) (6207)Messageintended for Client '21eac08f9ac3dc432e7056e671b63d2fc51e8eb0' received incorrectly at agent on xqd1:10.91.3.61(58a5fdfcd52f0c579228fb860a7fc695d821e3ba) currently registered to 'xx.xx.x.xx'

You can try to follow the steps as below to resolve the issue:

1.   Re-activate the client.

2.   Delete the incorrect (short name) client they do not want.

3.   Unregister the client from the Avamar GUI.

4.   Rename the cid.binfile on the client.

5.   On the Admin GUI with the one LONG client account still there, rename it to the same as the short name client.

6.   Register the client and verify if it went into the correct newly-renamed short client account.

7.   Optionally: rename the client back to long name on Avamar GUI if requested.

                                                                                                                   Author: Leo Li

             

iEMC APJ

Please click here for for all contents shared by us.

No Responses!
No Events found!

Top