- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I have found the answers.
1) "In the IP address for incoming storage traffic", you enter the IP address of the VMKernel adaptor that you have configured for vSphere Replication traffic on that appliance
2) "When adding a static route on the source VR appliances, you enter the default gateway that the network needs to use to go to the target site":
On the VR appliance you enter the following section in the VR traffic eth1 adaptor file (10-eth1.network):
[Route]
Gateway=<gateway for the VR traffic subnet>
Destination=<ip subnet range of vr-traffic subnet at DR site> in CIDR format e.g. 192.168.0.1/24
FYI it seems to be better to fully separate the traffic rather than just the VR traffic so you would need to add 2 NICs to the VR appliance (one for VR traffic - inbound traffic - and one for VR NFC traffic - outbound traffic).
If you add 2 NICs then the network directory on the VR appliance will have 3 files like this:
10-eth0.network for the mgmt traffic
10-eth1.network for the VR inbound traffic
10-eth2network for the VR NFC outbound traffic.
3) As already mentioned it seems to be more recommended to separate all traffic so you would use 2 port groups with 2 VMKernel adaptors instead of 1 VMkernel adaptor with both types of traffic enabled.
Also don´t forget that you actually need to add static routes (if required) to both the ESXi hosts AND the VR appliances. -> a static route in 2 places.
I hope this info helps someone.
Cheers