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 AWS.

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.

Task List: 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 instance (BIG-IP A) in an Amazon VPC with multiple subnets.

Then complete the following tasks, which are a subset of the tasks in the Multi-NIC guide, to create a second BIG-IP VE instance (BIG-IP B). These tasks are explained in detail in the Multi-NIC guide.
Note: Both BIG-IP VE instances must be in the same availability zone.

In AWS:

Step Task Description Details
1 Deploy a BIG-IP VE instance The second BIG-IP VE should be in the same VPC as the first. Ensure you assign an IAM role with HA policy and add the extra, external NIC.
Note: If you do not assign a role when you deploy, you can use an IAM user's keys instead. See the Use an IAM user instead of an IAM role topic for more information.
  • Management: 10.0.0.201
  • External: 10.0.1.201
2 Create an internal network interface (NIC) and attach it to the instance You created NICs for the management and external subnets when you deployed the instance.

You must create an internal NIC and reboot, so BIG-IP VE can recognize the new NIC, and hourly instances can license with F5.

Internal: 10.0.2.201
3 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):

Step Task Description Details
1 Connect to the BIG-IP VE instance and set the admin password Before you can license and provision BIG-IP VE, use SSH and your key pair to connect to the instance and set a strong password. In tmsh, type modify auth password admin
2 Log in and provision BIG-IP VE Log in to the BIG-IP Configuration utility (https://<ElasticIP>) and provision BIG-IP VE. If you chose a BYOL license, you must license BIG-IP VE before provisioning.  
3 Create external and internal VLANs These VLANs correspond to the external and internal subnets in your VPC.
  • external VLAN interface: 1.1
  • internal VLAN interface: 1.2
4 Create static self IP addresses for the external and internal VLANs These addresses should match the private IP addresses you assigned to the external and internal subnets in AWS.
  • 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)