By "vReplicator" do you mean vSphere Replication or something else?
yes, I mean vSphere Replication
I add some additional info.
- the number of VMs under replica and protection will be around 40-50 VMs
- all VMs used around 20-25 TB
- in the VLAN A (in replica with the VLAN C through VPN) we have also replica from systems backup. We had choise to put backup server in the same VLAN to avoid traffic through FW
Hi for your infrastructure its best practice to run the same version of vSphere at both sites as if failing over from 6.7 to 6.5 the VMware tools will be different and then when failing back the VMs will go from 6.5 to 6.7 so best to have 6.7 at both sites. I see the comparability with the storage is why its 6.5, so best to replace that storage so your on the same at both sites. if thats not an option then at least test a VM failover from 6.7 to 6.5 and then failback to make sure there are no issues.
For replication it looks like you are aiming for Traffic Isolation for the replication. If so then create a new vss/vds and port group for replication, then create a vmkernel port for replication service on each host / vds then on each Replication appliance add an additional interface so then each appliance will have 2 interfaces, one for management and one for replication. in the replication interface set a static ip via the vami for replication appliance (:5480 login) then once thats set go back to the configuration page and set the same IP Address in the "IP Address for Incoming Storage Traffic" that will then set the segregation.
By default, management NIC on source ESXi host and management NIC of target VR appliance is used to send and receive VR NFC traffic. If you wish to segregate vSphere replication traffic to isolate the traffic, yes you can do that.
If you wish to segregate vSphere replication traffic, yes you can do that. Adding to what user "MJMSRI" had mentioned below, I would request you to refer following document for instructions:
Hope that helps