Symptoms
Replication may fail due to Avagent on the Avamar server being unable to get a new work order.An attempt to manually register Avamar with Avagent shows the following error:
2023-05-12 11:04:42 avagent Info : Updating IP address with the MCS. local IP='10.180.2.4', registered IP='(none)', port changed:false
2023-05-12 11:04:42 avagent Info : agent_message::resolve_client_ip ping to MCS : using local IP:(none) failed, char_to_sockaddr() Unable to resolve hostname (Check your DNS setting and server)
2023-05-12 11:04:42 avagent Info : Registration: Processing secure registration with the MCS.
2023-05-12 11:04:42 avagent Info : Registration: Requesting root CA from the MCS.
2023-05-12 11:04:42 avagent Info : Unable to securely register with the MCS ()
2023-05-12 11:04:42 avagent Error : Error trying to update MCS with new ip address
2023-05-12 11:04:42 avagent Info : Agent Main: Client ID (cid) = 8b81998b81565b510a70592e72e085d9d0acde9e
2023-05-12 11:04:42 avagent Info : Skipping registration, no MCS name
2023-05-12 11:04:42 avagent Info : MCS unknown, entering listen mode.
2023-05-12 11:04:42 avagent Info : Unable to connect to Management Console (), sleep 28 minutes, 8 seconds before retry
Cause
The error from the manual registration has the following line:
avagent Info : Skipping registration, no MCS name
The error shows that there is no MCS address that can be used to connect to. This process is looking for the MCS address in the avagent.cfg file.
root@avamar:/home/admin#: cat /usr/local/avamar/var/client/avagent.cfg
#
# DO NOT MODIFY THIS FILE!
# This file is maintained by avagent
# Please use avagent.cmd when adding options
#
--mcsport=28001
In the snippet above, it is missing the flag for storing the MCS address.
Resolution
In Avamar Administrator or the Avamar User Interface, go to the /MC_SYSTEM domain.Edit the Avamar client account by clearing the "Activated" checkbox.Remove the old cid.bin file as it gets regenerated upon re-registering.
rm /usr/local/avamar/var/client/cid.bin
Add the missing flag to the avagent.cfg file.
vi /usr/local/avamar/var/client/avagent.cfg
Example:
root@avamar:/home/admin#: cat /usr/local/avamar/var/client/avagent.cfg
#
# DO NOT MODIFY THIS FILE!
# This file is maintained by avagent
# Please use avagent.cmd when adding options
#
--mcsaddr=avamar.lab.dell.com
--mcsport=28001
Re-register the Avamar client account in the /MC_SYSTEM domain using the fully qualified domain name of the Avamar server.
/etc/init.d/avagent register /MC_SYSTEM
Example:
/etc/init.d/avagent register avamar.lab.dell.com /MC_SYSTEM
