vSphere Replication can consume a lot of bandwidth during initial replication, and when virtual machines are added or destroyed. To avoid network problems and enhances network performance in the data center, isolate replication traffic from other network traffic.
What to read next
Create a Port Group for vSphere Replication Traffic for Site Protection and Disaster Recovery for VMware Cloud Foundation You isolate the network traffic to the vSphere Replication server by creating a dedicated port group for vSphere Replication traffic.
Add a Network Adapter and Configure Static Routes for vSphere Replication for Site Protection and Disaster Recovery for VMware Cloud Foundation You isolate the network traffic by adding a dedicated network adapter to the vSphere Replication appliance to handle data from each management ESXi host.
Create a VMkernel Adapter on the ESXi Hosts for vSphere Replication Traffic for Site Protection and Disaster Recovery for VMware Cloud Foundation You isolate the network traffic to the vSphere Replication server by dedicating a VMkernel network adapter on each management ESXi host in both the protected and the recovery VMware Cloud Foundation instances.
Configure ESXi Host Static Routes for vSphere Replication for Site Protection and Disaster Recovery for VMware Cloud Foundation You configure static routes on each ESXi host in the protected VMware Cloud Foundation instance to the recovery VMware Cloud Foundation instance. For replication traffic to flow in the opposite direction, you must configure reverse routes on the ESXi hosts in the recovery VMware Cloud Foundation instance.