Step F: Configure the Secondary Node - AWS Elemental Delta

This is version 2.3 of the AWS Elemental Delta documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Delta Documentation.

Step F: Configure the Secondary Node

Most of the information from the leader node is copied over to the secondary node. However, you must manually set up some features on the secondary node.

To configure the secondary node

  1. Access the web interface via the VIP address for the management interface (eth0). You set up this VIP when you configured the leader node. See Creating VIPs.

    Note

    Do not access the web interface from the IP address of the leader or secondary nodes.

  2. Address these features if you enabled them on the leader node:

    Ethernet devices or bonds

    Setup the secondary node with identical bonds. You can't assign the same IP address on both nodes, but you must create the same device names and bonds. For example, if the leader node is set up with eth0, eth2 and eth3 (bonded to bond0), and eth4 and eth5 (bonded to bond1), then on the secondary node, you must create eth2, eth3, eth4, eth5, bond0, and bond1.

    If you don't set-up identically, then when a fail over occurs, some traffic might not failover.

    For assistance, see Configuring Ethernet Network Devices.

    Mount points

    Set up the secondary with identical mount points as the leader node.

    For assistance, see Adding Mount Points.

    AWS credentials

    Set up the secondary node with identical credentials as the leader node.

    For assistance, see Adding AWS Credentials.

    Firewall ports

    Start the firewall and open the same ports on the secondary node that you opened on the leader node.

    For assistance, see Opening Ports on the Firewall.