VVR Replication fails to start/send data from primary to secondary in environments that use Network Address Translation (NAT). The failure is: ENC_NOT_READY, which is caused by VVR's inability to complete heartbeat communication between the primary and secondary servers.
VVR sends heartbeats to the remote node only if the local IP address mentioned on the RLINK is online on that node.
In a NAT environment, the primary host communicates with the NAT IP of the secondary, and since the NAT IP is never online on the secondary node, the VVR secondary does not send heartbeats to the primary host. This results in the primary not sending a connection request to the secondary.
It is also observed that in a NAT environment when the primary's private IP address is same as the secondary's private IP address, VVR incorrectly concludes that the primary and secondary nodes are the same server.
This issue has been identified and a private fix is available from Symantec Enterprise Technical Support. To obtain the private fix, contact Symantec Support and reference this TechNote during the call.
If it is determined that the private fix addresses the problem, the support representative will further assist in obtaining the private fix. For a complete list of Symantec Enterprise Technical Support contact numbers, go to http://www.symantec.com/enterprise/support/index.jsp
Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.