Setting up Failover with a different interface

Procedure

  1. The interface configured by running the command set ip is used to send replication traffic and heartbeats to another appliance and to send heartbeats to the other appliance as well.
  2. If multiple such interfaces are to be configured, the user is asked to select which one is going to be used for HA replication and heartbeat.
  3. The interface configured by running the command set failover is used to assign the public IP address and therefore receives logs. The LogLogic software requires that it be one of the interfaces configured by the command set ip.
  4. It is possible to select an interface other than any selected in Steps 1 and 2. The disadvantage of this configuration is the interface might still send heartbeats while logs are not received. The advantage is that replication traffic does not interfere with the logs, and may use a back-to-back crossover, avoiding dependency on a switch.
  5. 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.