There is no network connectivity between the source host and the target broker
Article ID: 414263
Updated On:
Products
Issue/Introduction
After upgrade to VLSR 9.0.4, we are not able to communicate between source VR appliance and target ESXi hosts.
We notice errors under Replication Mappings
There is no network connectivity between the source host (id: 'host-XXXX', name: 'esxi_host_fqdn') and the target broker 'Replication_appliance_IP_address'. Details: 'Connect: Input/output error'.
There is no network connectivity between the source host (id: 'host-XXXX', name: 'esxi_host_fqdn') and the target broker 'Replication_appliance_IP_address'. Details: 'Connect: Input/output error'.
The source host (id: 'host-XXXX', name: 'esxi_host_fqdn') successfully connected to the target broker 'Replication_appliance_IP_address', but there is no network connectivity between the source host 'esxi_host_fqdn' and the target host (id: 'host-XXXX', name: 'esxi_host_fqdn'). Details: 'Connect: Input/output error'.
The source host (id: 'host-XXXX', name: 'esxi_host_fqdn') successfully connected to the target broker 'Replication_appliance_IP_address', but there is no network connectivity between the source host 'esxi_host_fqdn' and the target host (id: 'host-XXXX', name: 'esxi_host_fqdn'). Details: 'Connect: Input/output error'.
There is no network connectivity between the source host (id: 'host-XXXX', name: 'esxi_host_fqdn') and the target broker 'Replication_appliance_IP_address'. Details: 'Connect: Input/output error'.
There is no network connectivity between the source host (id: 'host-XXXX', name: 'esxi_host_fqdn') and the target broker 'Replication_appliance_IP_address'. Details: 'Connect: Input/output error'.
There is no network connectivity between the source host (id: 'host-XXXX', name: 'esxi_host_fqdn') and the target broker 'Replication_appliance_IP_address'. Details: 'Connect: Input/output error'.
Environment
Vmware Live Recovery 9.0.4
Cause
By default, the combined VMware Live Recovery appliance has one VM network adapter.
With enhanced replication mode, the VR broker service in target VLR appliance will talk to source ESXi server's and vice-versa.
Even though the broker does not accept replication traffic, it still needs to talk with source ESXi's replication network.
Resolution
If the ESXi replication network is isolated from the management network, it will be unable to connect to the broker service.
We have to configure the same network services on the ESXi management network.
Perform this procedure for every ESX host that is used as a replication source.
1) In the vSphere Client, navigate to the ESX host.
2) Click the Configure tab and under Networking, select VMkernel adapters.
3) Edit the settings of the management network
By default the vmk0 adapter is used for management traffic.
4) Under Available services, select vSphere Replication and vSphere Replication NFC services for the local and remote ESXi replication network adapter.
5) Apply the settings and finish to complete the wizard.
Re-run the Replication Mapping test and it should succeed.
Additional Information
Note :
If ESXi needs to isolate replication traffic to a separate network, it will be unable to connect to VLR broker service as it is listening management network IP.
As VLR config UI does not support setting additional network for replication, we need perform these steps
Feedback
