At any time, VEA can support only one connection to a particular host. When VEA is connected to a cluster node using virtual IP addresses or the corresponding network names (virtual server), it may also allow another connection to the same physical host using different IP addresses that the node supports. This behavior is because of the constraints which virtual IP address and its network name has on the queries.
In such cases, VEA cannot identify if multiple connections are made to a same cluster node as a Volume Replicator host. These occurrences should be avoided as it causes ambiguities in identification and other such problems in VEA.
To avoid these multiple connections to the same cluster node, you can do the following:
Ensure that VEA has only one connection to the cluster node when using cluster virtual IP addresses to connect. If you want to have another connection through VEA to the same host use a separate instance of VEA.
When setting up the RDS, if the required replication IP address or name does not appear in the list of possible Primary hosts, then disconnect VEA from all connected hosts, then try connecting again.
If this does not solve the problem, close the VEA and reopen it. Then try connecting to the cluster IP name again.