Step A: Gather Information

Before you configure the leader-secondary node cluster, obtain the following information:

• The models and IP addresses (or hostnames) for all the nodes. The leader and secondary nodes must always be identical models.

• A list of Ethernet devices (for all nodes) and their IP addresses, including traffic rules such as:

  • Which IP addresses are intended to handle management and monitoring traffic.

  • Which IP addresses are intended to handle only incoming traffic (content ingest).

  • Which IP addresses are intended to handle only outgoing traffic (egress).

• A list of Ethernet devices (on the leader and secondary nodes) that are bonded, and the IP addresses for those bonds.

• A list of the Ethernet devices that were configured with IP addresses during installation of AWS Elemental Delta. The eth0 device is always configured during installation; other devices may or may not be. You need this information to determine which devices you need to figure in this configuration process and which you can assume are already configured.

• The addresses of any additional DNS servers and/or NTP servers the nodes access.

• The IP addresses of remote storage servers (CIFS, NFS or DAVFS) where ingested content is stored.

• The IP address of the remote server for AWS Elemental Delta database backups.

• The user credentials for Amazon (AWS) S3 storage, if applicable.

• A list of ports that you want to open beyond the ports that AWS Elemental Delta automatically opens.

• The IP addresses of VIPs on your network that are assigned to AWS Elemental Delta. These VIPs are associated with all of the incoming Ethernet devices on the leader and secondary nodes. (You have a load balancer so VIPs are not set up within Delta for the outgoing Ethernet devices.)

• The user credentials for users if you are setting up with user authentication.