Applies To:

Show Versions Show Versions

Manual Chapter: Deploying Multi-NIC BIG-IP VE in AWS
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Checklist: Deploy BIG-IP VE in a multi-NIC AWS environment

Now deploy a BIG-IP® VE instance and configure basic networking for it.

Deploy a BIG-IP VE instance
From the AWS Marketplace, choose an F5® BIG-IP VE image. During the deployment process, assign interfaces to the subnets.
  • Management interface: eth0, primary private IP: 10.0.0.200
  • External interface: eth1, primary private IP: 10.0.1.200
Create an Elastic IP address for the BIG-IP Configuration utility
To access the BIG-IP Configuration utility from the Internet, create an Elastic IP (EIP) address and associate it with the BIG-IP VE instance.
  • EIP: 52.x.y.x
Create an internal network interface
This network interface is for the internal subnet. After you add it, you must reboot BIG-IP VE so it can recognize the new NIC. Rebooting is also required so that hourly instances of BIG-IP VE can get a license from F5.
  • Internal interface: eth2, primary private IP: 10.0.2.200
Assign a secondary private IP address to the external interface
This is the address BIG-IP VE will use for the virtual IP address.
  • Secondary private IP: 10.0.1.202
Create an Elastic IP address for the virtual server
You must create an EIP address and associate it with the secondary private IP address of the external subnet. This will make the virtual server accessible from the Internet.
  • EIP: 52.x.y.x

Deploy a BIG-IP VE instance in a multi-NIC environment

To create an EC2 instance of BIG-IP® Virtual Edition (VE), you deploy a version of it from the Amazon Web Services (AWS) Marketplace.
  1. Go to the AWS Marketplace.
  2. In the Search AWS Marketplace field, type F5 BIG-IP and then click GO.
  3. Click the version you want to deploy, and then click Continue.
    Important: Choose the region where you created your VPC.
  4. By the appropriate region, click Launch with EC2 Console.
  5. Select an instance type. (See Amazon instances for BIG-IP VE for details.)
  6. Click Next: Configure Instance Details.
  7. In the Number of Network Instances field, type 1.
  8. From the Network list, select your VPC.
  9. From the Subnet list, select the management subnet: 10.0.0.0/24.
  10. On the lower part of the screen, expand Network interfaces and click Add Device.
  11. For eth0, type the IP address of 10.0.0.200. For eth1, select the external subnet, and type the primary IP address of 10.0.1.200.
    Important: You must create the second interface (eth1) or BIG-IP VE will not install properly.
  12. Click Next: Add Storage.
  13. Click Next: Tag instance.
  14. In the Value field, type a name for the instance. If you plan to create multiple BIG-IP VEs, you might want to name it BIG-IP A.
  15. Click Next: Configure Security Group.
  16. For Assign a Security Group, select Select an existing security group and choose both ManagementTraffic and VirtualServerTraffic.
  17. Click Review and Launch.
  18. Confirm that all settings are correct, and then click Launch.
  19. Select the key pair you created, select the acknowledgement check box, and click Launch Instances.
  20. Click View Instances to view the new instance.
When the status in the Status Checks column has changed from Initializing to 2/2 checks passed, the instance is ready.
Important: If you chose an hourly instance, you must associate an AWS Elastic IP address with the instance while it is launching, so the instance can register the license with F5. If the instance does not have internet access when it first boots, you must reboot the instance so it can connect to F5 for licensing.

Create an Elastic IP for the BIG-IP Configuration utility

In order to access the BIG-IP® Configuration utility from the Internet, the BIG-IP VE instance must have an Elastic IP (EIP) address associated with it. Hourly instances of BIG-IP VE must also have internet access so that they can get a license from F5.
Note: EIPs are accessible to the Internet. Because of this, later you will set a strong password for the BIG-IP VE admin account, which is used to access the Configuration utility.
  1. In the AWS Management Console, from the Services menu at the top of the screen, select EC2.
  2. In the Navigation pane, under NETWORK & SECURITY, select Elastic IPs.
  3. Click Allocate New Address.
  4. From the EIP used in list, select VPC.
  5. Click Yes, Allocate and then click Close.
  6. Right-click the newly created EIP and select Associate Address from the popup menu screen.
  7. Select the BIG-IP VE instance and the management subnet's private IP address, 10.0.0.200.
  8. Click Associate.
Later, you use this EIP to access the BIG-IP Configuration utility.

Create an internal network interface

When you created the BIG-IP® VE instance, you associated two network interfaces with it (one for management and one for external). To connect BIG-IP VE with your internal servers, create an internal network interface, and attach it to your BIG-IP VE instance.

  1. In the AWS Management Console, from the Services menu at the top of the screen, select EC2.
  2. In the Navigation pane, under NETWORK & SECURITY, select Network Interfaces.
  3. Enter names for your existing network interfaces. In the list, there should be one interface for the NAT instance and two interfaces for BIG-IP VE. Use the values in the Primary private IP column to determine which NIC is for which subnet.
  4. Click Create Network Interface and populate the appropriate fields.
    Field Value
    Description Internal
    Subnet 10.0.2.0/24
    Private IP 10.0.2.200
    Security groups InternalTraffic
  5. Click Yes, Create.
    AWS adds the network interface to the list.
  6. Update the name in the list to Internal.
  7. Right-click the new Internal network interface and select Attach.
    The Attach Network Interface popup screen opens.
  8. From the Instance ID list, select the VE instance that you created and click Attach.
Important: You must now reboot the BIG-IP VE so that it can register the new NIC. To do this, right-click the instance in the Instances list and choose Instance State > Reboot.

Add a secondary private IP address for the virtual server

Before you can create a virtual server, you must assign a secondary IP address to the external network interface. This secondary IP will be associated with the BIG-IP® VE virtual server address.
  1. In the AWS Management Console, from the Services menu at the top of the screen, select EC2.
  2. In the Navigation pane, under NETWORK & SECURITY, select Network Interfaces.
  3. Identify the external network interface (the NIC that uses the 10.0.1.0 subnet).
  4. Right-click the external network interface and click Manage Private IP Addresses.
  5. Below the existing address, select Assign new IP.
  6. Type 10.0.1.202 for the address.
  7. Click Yes, Update.
  8. Click Cancel to close the dialog box.
The new IP address is displayed in the Secondary private IPs column of the Network Interfaces screen. Later, you will enter this IP address in BIG-IP VE as the virtual server address.

Create an Elastic IP for the virtual server

Before you begin, note the secondary private IP address assigned to the external network interface. If you followed the steps in the previous task, the secondary private IP address is 10.0.1.202.
Now make the virtual server IP address (the secondary private IP address) accessible to the Internet by associating an Elastic IP (EIP) address with it.
  1. In the AWS Management Console, from the Services menu at the top of the screen, select EC2.
  2. In the Navigation pane, under NETWORK & SECURITY, select Elastic IPs.
  3. Click Allocate New Address.
  4. From the EIP used in list, select VPC.
  5. Click Yes, Allocate, and then click Close.
  6. From the list of EIP addresses, right-click the newly created address, and select Associate Address from the popup menu screen.
  7. Select the external interface and the secondary IP address (10.0.1.202).
  8. Click Associate.
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)