When configuring VM replication to use enhanced replication, the following error is seen in the configuration wizard:
"Some of the selected virtual machines are not in a valid state for replication"
"The virtual machine host does not support enhanced replication"
The following error is seen when running the Enhanced Replication Mappings test on Site Recovery:
"Fault occurred while performing health check. Details: '404 Not Found from GET https://<esxi_ip>/hbragent/api/v1.0/appPing?broker_ip=<vr_ip>&broker_port=32032&group=PING-GID-##########################'."
VMware vSphere Replication 9.x
This issue is caused due the host on which the VM resides on does not have the hbr-agent vib installed on it.
Due to the vib being unavailable on the host, the host will not supported enhanced replication.
Also since the vib is not installed, the ESXi firewall will not list the hbr-agent under outgoing connection.
To resolve this issue:
If this is a new setup, it could be possible that the vib is not pushed to all (or any) hosts in the environment. The vSphere Replication's /opt/vmware/hms/conf/hms-configuration.xml file can be validated to see if the hbragent auto install is disabled (<hms-auto-install-hbragent-vib>false</hms-auto-install-hbragent-vib>). If it is disabled, perform the below:
SSH to vSphere Replication appliance as root user.
Type following command to edit the hms-configuration.xml and set the parameter's value to true: vi /opt/vmware/hms/conf/hms-configuration.xml
Press 'i' and then change the configuration of parameter from 'false' to 'true': <hms-auto-install-hbragent-vib>true</hms-auto-install-hbragent-vib>
Save the file by pressing: Esc + ':wq!'
Finally, restart hms service on the VR appliance using command: systemctl restart hms
Repeat the same steps on the other VR appliance as well.
If this issue is only observed on a few hosts in the environment and if the above resolution does not fix the issue, manually install the vib on the ESXi host:
Once the vib is installed on the host, the configuration of replication should work. If another error arises post performing this fix or if vSphere Enhanced replication is still not working, open a case with Broadcom Technical Support to investigate further.