Recovering the Active or Standby Node

If the current active node fails, the standby node takes over and becomes the active node.

When a node joins the failover it becomes the standby and a node resynchronization operation starts. The standby resynchronizes both the missing and existing data from the active node (including the currently modified data set) and the active node resynchronizes the missing data from the standby node.

The following is a sample Failover configuration using the following parameters:

  • Active appliance: 10.20.0.10
  • Standby1: 10.20.0.11 (old, to be replaced by Standby2)
  • Standby2: 10.20.0.11 (new, will use same IP as Standby1)
  • Public: 10.20.0.12
  • Subnet Mask: 255.255.0.0
  • Broadcasting: 10.1.255.255
  • Gateway: 10.1.1.1
  • NTP Server: 10.1.1.250

Procedure

Replacing the old Standby1 with a new Standby2:

  1. Unplug all the network cables from the old Standby1 appliance (10.20.0.11) and plug them into the new Standby2.
  2. Log in to the Standby2 appliance from a serial console, using root/logapp (username/password) to enter the CLI.
    Note: Use a serial console instead of an SSH connection. Network configuration changes can disconnect an SSH connection during this procedure. In all circumstances, a serial connection is maintained.
  3. Set the IP address on Standby2 with the following command: 
    > set ip 10.20.0.11 255.255.255.0 10.1.1.1 bond0
> save
  4. Configure failover on Standby2: 
    > set failover configure
    1. Enter the public IP address: 
      10.20.0.12 255.255.255.0 10.1.1.255 bond0
    2. When prompted about this appliance being the destination of automatic migration, enter Y.
    3. Enter the IP address of the peer appliance: 
      10.20.0.10 
> save