Hyper-V FLR Proxy showing disconnected after live migration from one host to another
Problem description
FLR proxy showing disconnected from the Druva console when this VM was migrated from one host to another host(live migration).
Cause
FLR Proxy network interface lost IP configuration during live migration and network service starts generating this Error: “bringing up interface eth0 error connection activation failed no suitable device found for this connection”
Traceback
Main-service Logs:
[2023-03-09 08:31:53,943] [INFO] Connecting to Sync Server…
[2023-03-09 08:31:53,944] [ERROR] Error <class 'socket.gaierror'>:[Errno -2] Name or service not known. Traceback -Traceback (most recent call last):
File "roboSyncController.py", line 581, in run
File "roboSyncController.py", line 559, in _run
File "roboSyncController.py", line 212, in connect_sync_server
File "inSyncLib/inSyncRPCBase.py", line 680, in __call__
File "inSyncLib/inSyncRPCBase.py", line 1294, in _safe_request
File "inSyncLib/inSyncRPCBase.py", line 1237, in connect
File "inSyncLib/inSyncRPCClient.py", line 173, in _connect
File "inSyncLib/inSyncRPCClient.py", line 224, in connect_with_filter
File "socket.py", line 228, in meth
gaierror: [Errno -2] Name or service not known
Resolution
- Verify the interface mac address(HWADDR) with the interface /etc/sysconfig/network-scripts/ifcfg-eth0 file
- If it is different from the one which is showing under interface using the command ip addr show like this:
- Then edit the network interface ifcfg-eth0 file by using this vi editor:
vi /etc/sysconfig/network-scripts/ifcfg-eth0
- Press i to put in insert mode, change the HWADDR value same as the current value and save by pressing Esc :wq
- Restart network service using this command:
systemctl restart network
- And it will assign the IP configuration as defined in the ifcfg-eth0 file like this:
- Once the IP is assigned, restart the Phoenix service using this command:
systemctl restart Phoenix