About NAT support in Veritas Resiliency Platform
Network Address Translation (NAT) is a process in which one or more computers inside a private network are assigned a public address. NAT reduces the need for IPv4 public addresses and hides private network address ranges.
Resiliency Platform 3.3 provides support for NAT to enable communication from a private network to an external network. If there is a non-routable network between the source data center and the target data center, then You need to configure NAT only using IPv4 address for communication between Resiliency Platform appliances.
Resiliency Platform supports NAT only for the communication between Resiliency Platform components deployed in different data centers. These components need to communicate with each other over public IP address. NAT can exist in both the data centers or in any one of the data centers.
Resiliency Platform does not support NAT for communication between components deployed in the same data center. The components based in the same data center can communicate with each other over private IP address.
If a communication channel has been setup in a way that private IP address of the Resiliency Platform components is accessible in the other data center, then you need not configure NAT during the bootstrap process. For example, if you have setup VPN for communication between on-premises data center to AWS datacenter, then you need not configure NAT for Resiliency Platform components .
If there are multiple Resiliency Managers in one data center, then either NAT configuration should be done for all of them or for none of them. A mix of NAT configured Resiliency Managers and non-NAT configured Resiliency Managers within a single data center is not supported.
Following are the scenarios in which NAT configuration is required for Resiliency Platform virtual appliances:
Table: Scenarios in which NAT configuration is required
Communication between | Description | NAT configuration |
|---|---|---|
Replication Gateway with Peer Replication Gateway | A Replication Gateway can communicate with the peer Gateway only over Public IP. | Required |
IMS with Resiliency Manager | If an IMS reports to a Resiliency Manager within the same data center, then it can communicate over private IP. | Not required |
If an IMS reports to a Resiliency Manager deployed in another data center, then it can communicate only over public IP. | Required | |
Resiliency Manager with another Resiliency Manager | If there are multiple Resiliency Managers in one data center and no Resiliency Manager in another data center, then all of the Resiliency Managers within the data center can communicate with each other over private IP. | Not required |
If there are multiple Resiliency Managers in one data center and at least one Resiliency Manager in another data center, then all of the Resiliency Managers need to communicate with each other only over public IP. In this case, you need to enable NAT reflection (Loopback NAT) for the data center where multiple Resiliency Managers are located. | Required |