Configuring network settings for Replication Gateway
A Replication Gateway needs to communicate with multiple entities with in Veritas Resiliency Platform such as the IMS, protected hosts, and peer Gateway. To facilitate separate communication channels for all these communications, Resiliency Platform 10.4 extends support for configuring Replication Gateway with multiple Network Interface Cards (NIC).
The Replication Gateway appliance is shipped with four NICs. Out of these four NICs, you can configure three NICs to be used for the following three communications:
For communication with Infrastructure Management Server (IMS)
For communication with peer Replication Gateway
For communication with the virtual machines to be protected
Remaining one NIC is not configured during the bootstrap. Using the klish menu, you can configure that NIC later for communication between the appliance and any external entity. You can now configure this remaining NIC using IPv6 address with nic-configuration set command..
See Klish menu options for Replication Gateway.
If you do not plan to use three separate networks, you do not need to configure all the three NICs. You can configure only one NIC or two NICs based on your network layout. So if you have only one network, you can configure only one NIC and associate all three communications to go through the configured NIC. Likewise, if you have two networks, you can configure two NICs and associate appropriate communications to go through these two NICs.
Since IPv6 network support is provided from Resiliency Platform 3.3.1 version, you can configure the NICs using IPv4 and IPv6 addresses. For more information, See About IPv6 network support in Resiliency Platform.
Note:
The network configuration of the NICs performed during the bootstrap is final and you cannot edit the network configuration of the NICs at a later point of time.
To configure network settings for Replication Gateway
- In the Host Network Settings section, the bootstrap program first checks for network configuration of all the NICs of the appliance and prints the network details of the NICs. You are prompted to continue the process of bootstrap. You can see a list of sections that need to be completed as a part of host network settings:
Host Network Settings for communication to Infrastructure Management Server
Host Network Settings for communication to Peer Gateways
Host Network Settings for communication to virtual machines to be protected
- For each section listed above, do the following:
Enter the NIC to be used for the communication. The name and MAC address of NIC is displayed.
The Bootstrap process checks if the NIC is already configured.
If the NIC is already configured then the NIC network configuration details are printed and you are prompted to confirm if you want to continue with the printed configuration.
If the NIC is not configured or if you do not want to use the existing NIC configuration, then you can choose to use either DHCP protocol or static protocol. In case of static protocol, you need to provide static network details such as IP address, prefix length.
Note:
Ensure that appropriate subnet or virtual switch is assigned to the network adapter. Confirm this by matching the MAC address shown in the bootstrap with the one assigned to the virtual machine by the virtualization or cloud technology.
Confirm if you want to add a static route. You need to set a static route for the interface only If you want the interface to reach a subnet that is different from all the subnets configured on this appliance and the default gateway is unable to communicate with that subnet. In this case, provide the subnet details (in CIDR format) at the input prompt. You can also set a static route to a host. In this case, provide the IP address of the host at the input prompt.
Confirm if you are in Network Address Translation (NAT) environment and want to configure NAT when the NICs are configured in IPv4 networks only.
Note:
Since NAT is not supported for IPv6 address, hence when you configure the virtual appliance using IPv6 address only and both IPv4 and IPv6 address, you are not asked about the NAT configuration. To know more about NAT support in Resiliency Platform
See About NAT support in Veritas Resiliency Platform.
You can add NAT gateway for communication between the peer gateways.
- After successful configuration of the first NIC, confirm if you want to use the same NIC for other two communication channels. If you do not want to use the same NIC, perform step 2 for rest of the NICs.
- Enter details for default router and then enter the DNS server details.
- The details of Host Network Settings are displayed and you are prompted to confirm. Review the information. If any information is incorrect, choose n to go back to the networking inputs page and correct the details. Upon confirmation, the network is configured.
More Information