Applies To:

Show Versions Show Versions

Manual Chapter: Preparing for High Availability in AWS
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

High availability configuration overview

This illustration shows the additional network objects you must create for a typical BIG-IP® VE high availability (HA) configuration in an Amazon Virtual Private Cloud (VPC).

In this configuration, the BIG-IP VEs continually communicate their availability status to one another through the HA VLAN and the associated static self IP address on each BIG-IP VE.

To create this configuration, in AWS, you create an HA subnet with primary private IP addresses and network interfaces. Then in BIG-IP VE, you create corresponding objects, represented by the shaded boxes in the diagram.

Checklist: Create a second BIG-IP VE instance

Before you can configure high availability (HA), follow the steps in the BIG-IP Virtual Edition and Amazon Web Services: Multi-NIC Setup guide to create one BIG-IP® VE in an Amazon VPC with multiple subnets. Then use the checklist below and the tasks in that guide and to create a second BIG-IP VE instance.

Both BIG-IP VE instances must be in the same availability zone.

Note: In this guide, the BIG-IP VE instances are referred to as BIG-IP A and BIG-IP B.

In AWS, do these tasks:

Deploy an instance in a multi-NIC environment
This includes choosing an instance type and associating the instance with the correct VPC, subnets, NAT instance, and so on. Sample name: BIG-IP B.
Create a network interface (NIC) for the internal subnet
You already created NICs for the management and external subnets when you deployed the instance.
Create an Elastic IP address (EIP) for the BIG-IP management interface
An EIP address is a publicly-routable address that provides access to the BIG-IP Configuration utility. If the BIG-IP VE is rebooted, stopped, or terminated, the EIP address persists on that NIC.

On the new BIG-IP VE instance (BIG-IP B), do these tasks:

Run the BIG-IP Setup utility
Activate the license, provision modules, and set the passwords for the root and admin accounts.
Create VLANs for the external and internal networks
These VLANs correspond to the external and internal subnets in your VPC.
Create static self IP addresses for the external and internal VLANs
These addresses should match the primary private IP addresses assigned to the NICs for the corresponding subnets.

High availability prerequisites

After you have two running BIG-IP® VE instances (BIG-IP A and BIG-IP B) but before you configure high availability (HA), confirm that your configuration includes all of the following objects.

VPC objects in AWS

BIG-IP A and BIG-IP B share a VPC, which includes:

  • Network address translation (NAT)
  • A subnet for the management, external, and internal networks
  • A security group for each subnet
  • A route table entry to provide Internet access for the management and external subnets

BIG-IP A objects

These objects for BIG-IP A are configured in AWS:

  • For each subnet (management, external, and internal), a network interface (NIC) with associated primary private IP address:

    NIC Device index IP address
    mgmt_A eth0 10.0.0.200
    external_A eth1 10.0.1.200
    internal_A eth2 10.0.2.200
  • An Elastic IP (EIP) address for the management interface, for example 52.x.x.x
  • A secondary private IP address attached to NIC external_A: 10.0.1.202 (used as the virtual server address in BIG-IP VE)

These objects for BIG-IP A are configured in BIG-IP:

  • Internal and external VLANs
  • Static (non-floating) self IP addresses for the external and internal VLANs:

    VLAN Self IP address
    external 10.0.1.200
    internal 10.0.2.200
  • A virtual server: 10.0.1.202
  • A load balancing pool

BIG-IP B objects

These objects for BIG-IP B are configured in AWS:

  • For each subnet (management, external, and internal), a network interface (NIC) with an associated primary private IP address:

    NIC Device index IP address
    mgmt_B eth0 10.0.0.201
    external_B eth1 10.0.1.201
    internal_B eth2 10.0.2.201
  • An EIP address for the management interface, for example 52.x.x.x

These objects for BIG-IP B are configured in BIG-IP:

  • Internal and external VLANs
  • Static (non-floating) self IP addresses for the external and internal VLANs:

    VLAN BIG-IP VE B
    external 10.0.1.201
    internal 10.0.2.201
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)