Separating Management and Replication Networks Using Dual NICs ZVM Setup

KB Number:

000001221

Symptoms:

An administrator wants to separate traffic per NIC, allowing for Management to go through one NIC, and Replication to go through the other.

Cause:

Zerto's best practices for a CSP or large enterprises is to separate vCenter/vCD/Management traffic from replication traffic and VRA traffic.

This can be accomplished by configuring two NICs for the ZVM - one for management and one for replication.

Solution:

When implementing such a configuration, the following should be taken into consideration:

Ensure that the ZVM's IP that's configured is able to access vCenter/SCVMM.
Ensure that the ZVM's IP that's configured is able to access the VRAs.

The VRAs and ZVM should be installed on separate networks to allow for the segregation, for example:
- vCenter is installed on dVportgroup 2.
- All VRAs are installed on dVportgroup 1.
- 1 ZVM NIC is installed on dVportgroup 1, while the second one is on dVportgroup 2.

For fresh installs:
1. When running through the ZVM installer, in the NICs drop down list, please choose the NIC that can talk to vCenter.
2. After installation has completed, add a NIC using the vSphere client: Right click the ZVM machine in the inventory -> Edit Settings -> Add device -> Virtual NIC.

Once the NIC has been added, set it to the network onto which the VRAs were installed.

For running ZVMs:
Add a NIC using the vSphere client. Right click the ZVM machine in the inventory -> Edit Settings -> Add device -> Virtual NIC.

Once the NIC has been added, set it to the network onto which the VRAs were installed.
NOTE: You can change the NIC that is communicating to vCenter any time, using the Zerto Diagnostics Utility.

Affected Versions:

All versions

Hypervisor:

VMWare