Setting up Failover with a different interface

Procedure

The interface configured by “set ip” is used to send replication traffic and heartbeats to another appliance and to send heartbeats to the other appliance as well.
If more than one such interface is to be configured, the user will be asked to select which one is going to be used for HA replication and heartbeat.
The interface configured by “set failover” will be used to assign the public IP address and will therefore receive logs. The LogLogic software requires that it be one of the interfaces configured by “set ip”.
It is possible to select an interface other than any selected in Steps 1 and 2. The “downside” of this configuration is the interface may still send heartbeats while logs are not received. The “upside” is that replication traffic will not interfere with the logs, and may use a back-to-back crossover, avoiding dependency on a switch.
“Ip address of the peer appliance” is the destination of the replication traffic and of the heartbeats. It must therefore match the IP address assigned to the interface configured ON THE OTHER NODE during Steps Step 1 and Step 2.

Warning: Remember that bond interfaces encapsulate actual network interfaces. Therefore, if a bond interface is configured, then the encapsulated network interfaces may not be configured separately. For that reason, it is not advisable to configure bond interfaces and non-bond interfaces on the same appliance.