Troubleshooting: Hosts not added to IMS after migration to cloud data center
Following are the steps required to be performed for troubleshooting the add host operation failure:
To troubleshoot the add host operation failure
- Ensure that the reasons for the add host failure are resolved:
- After the migrate workflow completes successfully, migrated virtual machine (protected host) fails to add itself to the IMS after migrate operation completes. The host will not show up under the Data Mover page in the Replication Hosts section.
Check if xprtld service is in started state using CLI /opt/VRTSsfmh/adm/xprtldctrl status.
If it is in the stopped state, start it using the CLI /opt/VRTSsfmh/adm/xprtldctrl start.
Verify that the getvitals is working for localhost using CLI /opt/VRTSsfmh/bin/xprtlc -u nobody -l https://localhost:5634/world/getvitals.
If this still fails, reach out to Veritas Support for more assistance.
- When the add host to IMS operation fails with an error, a script
local_ims_attach.plis automatically invoked that periodically keeps retrying the operation. The maximum number of retry to be performed by this script is 13. Check thegendep_retryfile for the maximum number of retry operation that has been performed automatically. Thegendep_retryfile is located at the following location:On Linux:
/var/opt/VRTSsfmh/dr_data/gendep_retry
On Windows:
%PROGRAMDATA%\Veritas\VRTSsfmh\dr_data\gendep_retry
- If the maximum number of retry mentioned in the
gendep_retryfile is 13, then the script needs to be invoked manually. To manually invoke the script, run the following command on the host:On Linux:
/opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/adm/local_ims_attach.pl
On Windows:
%PROGRAMFILES%\Veritas\VRTSsfmh\bin\perl.exe %PROGRAMFILES%\Veritas\VRTSsfmh\adm\local_ims_attach.pl
The above command adds the host to the IMS.