How to Configure vNode outbound Links between HA redundant pairs (Double Redundancy)

Stablishing Redundant pair outbound link to a redundant pair central vNode need to be performed thru vNode redundancy agent.

At the lower redundant pair you need to create the outbound link pointing to a local port (on origin computer) where you have configured the redundancy agent connection, that connection will point to the upper vNodes IP address and the destination port will be the vNode link port (3001).

This configuration need to be created on the Primary node for the redundant pair at the lowest part of the architecture (since this is an OUTBOUND link).

After this you need to configure the outbound link pointing to localhost and the port you have configured as incoming port in the redundancy agent connection.

the Outbound link should look like this:

Please notice that:

• Node Name: refers to the name of the primary node on the lower redundant pair
• The link name in this case is "Central178" which is the primary node on the upper redundant pair
• Host IP: is the loopback ip address, since we will connect to our same computer and reach the port configured on he redundancy agent connection (in this case 3010)
• the TLS settings should be configured to trust all certificates, since we are pointing to a HA redundant pair

On the upper redundant pair primary node, you need to create an inbound link using a configuration similar to:

where:

• network Interface is 0.0.0.0 because since this is a redundant pair, the node name will be dynamic, but the IP address will be static for each node
• the TCP port is the default port, if you change this you will need to point to the new assigned port on the redundancy agent at the lower pair
• you need to trust all certificates, since the incoming link can change depending on the active computer at the lower redundant pair

All these configurations have to be created only at the primary nodes on both lower and upper redundant pairs, because the configuration will be automatically transferred to the secondary nodes.

After this you just need to restart the vNode bootstrap services and the double redundancy should work.