BIG-IP Virtual Edition Setup Guide for Amazon EC2. Version 11.3

Transcription

1 BIG-IP Virtual Edition Setup Guide for Amazon EC2 Version 11.3

2

3 Table of Contents Table of Contents Legal Notices...5 Chapter 1: Getting Started with BIG-IP Virtual Edition...7 What is BIG-IP Virtual Edition?...8 About BIG-IP VE compatibility with EC2 hypervisor products...8 About the hypervisor guest definition requirements...8 Chapter 2: Deploying BIG-IP Virtual Edition...11 About BIG-IP VE EC2 deployment...12 Creating a key pair...12 Creating a new virtual private cloud...12 Adding an additional subnet...13 Creating new security groups...13 Adding a route for external subnet accessibility...14 Launching a new BIG-IP Virtual Edition Amazon Machine Image...14 Adding a third network interface...15 Making the BIG-IP Virtual Edition management port accessible...16 Logging in and setting the Admin password...16 Adding a secondary IP address...17 Making the secondary IP address accessible...18 Creating VLANs mapped to external and internal interfaces...18 Creating self IP addresses for external and internal VLANs

4 Table of Contents 4

5 Legal Notices Publication Date This document was published on November 14, Publication Number MAN Copyright Copyright , F5 Networks, Inc. All rights reserved. F5 Networks, Inc. (F5) believes the information it furnishes to be accurate and reliable. However, F5 assumes no responsibility for the use of this information, nor any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent, copyright, or other intellectual property right of F5 except as specifically described by applicable user licenses. F5 reserves the right to change specifications at any time without notice. Trademarks Access Policy Manager, Advanced Client Authentication, Advanced Routing, APM, Application Security Manager, ARX, AskF5, ASM, BIG-IP, BIG-IQ, Cloud Extender, CloudFucious, Cloud Manager, Clustered Multiprocessing, CMP, COHESION, Data Manager, DevCentral, DevCentral [DESIGN], DNS Express, DSC, DSI, Edge Client, Edge Gateway, Edge Portal, ELEVATE, EM, Enterprise Manager, ENGAGE, F5, F5 [DESIGN], F5 Management Pack, F5 Networks, F5 World, Fast Application Proxy, Fast Cache, FirePass, Global Traffic Manager, GTM, GUARDIAN, IBR, Intelligent Browser Referencing, Intelligent Compression, IPv6 Gateway, iapps, icontrol, ihealth, iquery, irules, irules OnDemand, isession, L7 Rate Shaping, LC, Link Controller, Local Traffic Manager, LTM, Message Security Manager, MSM, OneConnect, OpenBloX, OpenBloX [DESIGN], Packet Velocity, Policy Enforcement Manager, PEM, Protocol Security Manager, PSM, Real Traffic Policy Builder, Rosetta Diameter Gateway, Scale N, Signaling Delivery Controller, SDC, SSL Acceleration, StrongBox, SuperVIP, SYN Check, TCP Express, TDR, TMOS, Traffic Management Operating System, Traffix Diameter Load Balancer, Traffix Systems, Traffix Systems (DESIGN), Transparent Data Reduction, UNITY, VAULT, VIPRION, vcmp, virtual Clustered Multiprocessing, WA, WAN Optimization Manager, WebAccelerator, WOM, and ZoneRunner, are trademarks or service marks of F5 Networks, Inc., in the U.S. and other countries, and may not be used without F5's express written consent. All other product and company names herein may be trademarks of their respective owners. Patents This product may be protected by U.S. Patents 6,374,300; 6,473,802; 6,970,733; 7,197,661; 7,287,084; 7,975,025; 7,996,886; 8,004,971; 8,010,668; 8,024,483; 8,103,770; 8,108,554; 8,150,957. This list is believed to be current as of November 14, Export Regulation Notice This product may include cryptographic software. Under the Export Administration Act, the United States government may consider it a criminal offense to export this product from the United States.

6 Legal Notices RF Interference Warning This is a Class A product. In a domestic environment this product may cause radio interference, in which case the user may be required to take adequate measures. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This unit generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user, at his own expense, will be required to take whatever measures may be required to correct the interference. Any modifications to this device, unless expressly approved by the manufacturer, can void the user's authority to operate this equipment under part 15 of the FCC rules. Canadian Regulatory Compliance This Class A digital apparatus complies with Canadian ICES-003. Standards Compliance This product conforms to the IEC, European Union, ANSI/UL and Canadian CSA standards applicable to Information Technology products at the time of manufacture. 6

7 Chapter 1 Getting Started with BIG-IP Virtual Edition What is BIG-IP Virtual Edition?

8 Getting Started with BIG-IP Virtual Edition What is BIG-IP Virtual Edition? BIG-IP Virtual Edition (VE) is a version of the BIG-IP system that runs as a guest in specifically-supported hypervisors. BIG-IP VE virtualizes a hardware-based BIG-IP system running a VE-compatible version of BIG-IP software. Note: The BIG-IP VE product license determines the maximum allowed throughput rate. To view this rate limit, you can display the BIG-IP VE licensing page within the BIG-IP Configuration utility. Lab editions have no guarantee of throughput rate and are not supported for production environments. About BIG-IP VE compatibility with EC2 hypervisor products Each time there is a new release of BIG-IP Virtual Edition (VE) software, it includes support for additional hypervisor management products. The Virtual Edition and Supported Hypervisors Matrix on the AskF5 website, details which hypervisors are supported for each release. BIG-IP VE is compatible with the Amazon Web Services (AWS) EC2 hypervisors. This guide documents the AWS interface as it exists at the time of the version BIG-IP software release to Amazon Web Services. Important: Hypervisors other than those identified in the matrix are not supported with this BIG-IP version; installation attempts on unsupported platforms might not be successful. About the hypervisor guest definition requirements The EC2 virtual machine guest environment for the BIG-IP Virtual Edition (VE), at minimum, must include: a 64 bit EC2 instance with at least 2 virtual cores (up to 16 are supported in this release) at least 4 GB RAM (64GB has been tested, F5 Networks recommends at least 2GB per virtual core) 2 x virtual Network Adapter cards (NICs). Up to 8 (1 management + 7 dataplane) are supported). Important: F5 Networks recommends three or more Network Adapters for most topologies, but the minimum requirement is two (one for management and one for traffic). Important: To support NICs on an Amazon Web Services you must create a virtual private cloud (VPC). 1 x virtual private cloud (VPC). Important: Not supplying at least the minimum virtual configuration limits will produce unexpected results. Important: There is no longer any limitation on the maximum amount of RAM supported on the hypervisor guest. Note: Refer to instance-types.html#availableippereni for their most current definition of the service that meets these requirements. 8

9 BIG-IP Virtual Edition Setup Guide for Amazon EC2 Important: At the time of this publishing, BIG-IP VE requires launch in a VPC so that NICs can be attached. This configuration is supported from the Launch with EC2 Console option, but not the 1-Click Launch option. 9

10

11 Chapter 2 Deploying BIG-IP Virtual Edition About BIG-IP VE EC2 deployment

12 Deploying BIG-IP Virtual Edition About BIG-IP VE EC2 deployment To deploy the BIG-IP Virtual Edition (VE) system on Amazon EC2, you need to perform these tasks: Create a key pair (if none exists) Create a VPC (if none exists) Launch a new AMI After you complete these tasks, you can log in to the BIG-IP VE system and run the Setup utility. Using the Setup utility, you can perform basic network configuration tasks, such as assigning VLANs to interfaces. Creating a key pair To create a virtual private cloud (VPC) from which you can deploy BIG-IP Virtual Edition (VE), you need a (private-public encryption) key pair to authenticate your sessions. Key pairs are reusable, so if you have a key pair, you do not need to repeat this task. For the most current instructions for creating a key pair, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site Important: It is crucial to your success that you be consistent in the Region that you choose throughout the configuration process. Objects configured in one region are not visible within other regions, so they cannot function together. There are a number factors that determine which region will best suit your requirements. Refer to Amazon user documentation for additional detail. The file that downloads from AWS uses the extension.pem. If you plan to use this key pair with the PuTTY terminal emulator application, you will need to convert the key pair from a.pem to a.ppk file. At the time of this release, PuTTY does not support the extension.pem. PuTTY does have a tool (called PuTTYgen) that converts your key pair to the required PuTTY format. Creating a new virtual private cloud You need a virtual private cloud (VPC) to deploy BIG-IP Virtual Edition (VE) because Amazon Web Services (AWS) only provides multiple network interface support for instances that reside within a VPC. At the time of this release, Amazon does not support EC2 instances outside of a VPC. For the most current instructions for creating a Virtual Private Cloud, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site Important: It is crucial to your success that you be consistent in the Availability Zone that you choose throughout the configuration process. Objects configured in one zone are not visible within other zones, so they cannot function together. Important: The first choice you have when creating a VPC is to select a VPC configuration. Choose the VPC with Public and Private Subnets option. 12

13 BIG-IP Virtual Edition Setup Guide for Amazon EC2 Adding an additional subnet When you create a VPC, AWS creates two subnets (Management and External) for it. For many network topologies, three or more subnets (Management, External, and Internal) are required. For the most current instructions for creating an internal subnet, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site If you are following a typical deployment strategy, when you finish adding the Internal subnet, your VPC will have three subnets. a Management subnet on an External subnet on an Internal subnet on Creating new security groups To use your virtual private cloud (VPC) to deploy BIG-IP Virtual Edition (VE), the VPC needs two security groups. The table details the rules required that govern the security behavior for the traffic routed through each group. Group Name Group Description Rule Name Source Rule Type allow-only-ssh-https-ping Allow only SSH HTTPS or PING Inbound SSH /0 Inbound HTTP /0 Inbound Custom ICMP /0 Echo Request Outbound Custom ICMP /0 Echo Request Outbound Custom ICMP /0 Echo Reply allow-all-traffic Allow all traffic Inbound All Traffic /0 Outbound All Traffic /0 Tip: The "Outbound All Traffic" rule is only necessary if you need to pass SNAT traffic with your outbound connection. For the most current instructions for creating security groups, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site When you finish adding the two groups and their associated rules, your VPC should be ready to go with three subnets and two security groups. It is a good idea to test connectivity before proceeding. Important: F5 Networks recommends enhancing your security by using the security group source fields to allow subnets only restricted management access; however, we recognize that this does not complete your security solution. For enhanced security, you may wish to deploy a topology with limited management network access. For example, you could restrict source addresses to an AWS VPN circuit, or to a fixed IP address block unique to your organization. 13

14 Deploying BIG-IP Virtual Edition Adding a route for external subnet accessibility Most network topologies require an Amazon Web Services route to the VPC that makes the External subnet used by the BIG-IP Virtual Edition (VE) accessible to the Internet. 1. From the Services tab at the top of the Amazon Web Services Management Console screen, select VPC. 2. In the Navigation pane, select Route Tables. The Route Tables screen opens. 3. Select the routing table with one subnet. 4. Click the Associations tab at the bottom of the window. 5. From the Select a subnet list, select the /24 subnet. 6. Click Associate. The Associate Route Table dialog box opens. 7. Click Yes, Associate. Launching a new BIG-IP Virtual Edition Amazon Machine Image You need to know the name of your key pair and the Availability Zone from which they were created before you can complete this task. You need to have an EC2 Amazon Machine Image (AMI) to deploy BIG-IP Virtual Edition (VE). Important: At publication, this task illustrates the Amazon web interface. However, F5 recommends that you refer to Amazon user documentation for the latest documentation. 1. Log in to your account on Amazon Web Services (AWS) marketplace. 2. In the Search AWS Marketplace bar, type F5 BIG-IP and then click GO. The F5 BIG-IP Virtual Edition for AWS option is displayed. 3. Click F5 BIG-IP Virtual Edition for AWS and then click CONTINUE. Tip: You may wish to take a moment here to browse the pricing details to confirm that the region in which you created your security key pair provides the resources you require. If you determine that the resouces you need are provided in a region other than the one in which you created your key pair, create a new key pair in the correct region before proceeding. The Launch on EC2 page is displayed. 4. Click the Launch with EC2 Console tab. Important: At the time of this publishing, BIG-IP VE requires launch in a VPC so that NICs can be attached. This configuration is supported from the Launch with EC2 Console option, but not the 1-Click Launch option. Launching Options for your EC2 AMI are displayed. 5. Select the BIG-IP software version appropriate for your installation and then click the Launch with EC2 button that corresponds to the Region that provides the resources you plan to use. Important: There are a number factors that determine which region will best suit your requirements. Refer to Amazon user documentation for additional detail. Bear in mind though that the region you choose must match the region in which you created your security key pair. 14

15 BIG-IP Virtual Edition Setup Guide for Amazon EC2 The Request Instances Wizard opens. 6. Select an Instance Type appropriate for your use. 7. From the Launch Instances list, select VPC. 8. From the Subnet list, select the /24 subnet. 9. Click Continue The Advanced Instance Options view of the Request Instances Wizard opens. 10. From the Number of Network Interfaces list, select Click the horizontal eth1 tab to set values for the second network interface adapter, and then from the Subnet list, select the /24 subnet. 12. Click Continue. The Storage Device Configuration view of the Request Instances Wizard opens. 13. Click Continue The Instance Details view of the Request Instances Wizard opens. 14. In the Value field, type in an intuitive name that identifies this AMI (for example, BIG-IP VE <version>. 15. Click Continue. The Create Key Pair view of the Request Instances Wizard opens. 16. From Your existing Key Pairs, select the key pair you created for this AMI. 17. Click Continue. The Configure Firewall view of the Request Instances Wizard opens. 18. Under Choose one or more of your existing Security Groups, select the allow-all-traffic security group. 19. Click Continue. The Review view of the Request Instances Wizard opens. 20. Confirm that all settings are correct, and then click Launch. The Launch Instance Wizard displays a message to let you know your instance is launching. 21. Click Close. Your new AMI will appear in the list of instances when it is fully launched. Adding a third network interface When you first create a virtual private cloud (VPC), there are typically only two network interfaces associated with it. F5 Networks recommends adding a third network interface to the VPC before you use it to deploy BIG-IP Virtual Edition (VE). 1. From the Services tab at the top of the Amazon Web Services Management Console screen, select EC2. 2. In the Navigation pane, select Network Interfaces. The Network Interfaces screen opens. 3. Click the Create Network Interface button (at top left). The Create Network Interface dialog box opens. 4. In the Description field, type Internal (or a similarly mnemonic name). 5. In the Subnet field, select / From the Security Groups list, select allow-all-traffic. 7. Click Yes, Create AWS adds your network interface to the list. 8. Right-click the new network interface, and then select Attach. The Attach Network Interface dialog box opens. 9. From the Instance list, select the VE AMI that you created. 10. Click Yes, Attach 15

16 Deploying BIG-IP Virtual Edition AWS updates the Status column from available to in-use. Making the BIG-IP Virtual Edition management port accessible The Management port for your BIG-IP Virtual Edition (VE) may require accessibility over the Internet. Alternative topologies exist that do not require exposing the Management port to the Internet. F5 Networks recommends, at a minimum, adding restrictions to your source addresses in the allow-only-ssh-https-ping security group. Alternatively, you may find the AWS EC2 VPN sufficiently effective so that you do not need to associate an Internet accessible Elastic IP with the Management port. 1. From the Services tab at the top of the Amazon Web Services Management Console screen, select EC2. 2. In the Navigation pane, select Elastic IPs. The Addresses screen opens. 3. Click Allocate New Address. The Allocate New Address dialog box opens. 4. From the EIP used in list, select VPC. 5. Click Yes, Allocate. 6. In the Address column, right-click the newly created Elastic IP and select Associate from the popup menu. The Associate Address dialog box opens. 7. From the Instance list, select the VE AMI that you created as an EC2 hypervisor. 8. From the Private IP Address list, select /24 (the Management subnet). 9. Click Yes, Associate. Logging in and setting the Admin password To perform this task, you must have completed the following tasks: Created a key pair Created and configured a VPC Instantiated and launched a BIG-IP VE AMI Made the BIG-IP VE Management port accessible via the Internet To maintain security, the first time you log in to your EC2 AMI, you should log in as root, and change the Admin password. 1. Log in to the new AMI that you just launched. Use the name of the key pair (.pem file), and the elastic IP address of your EC2 instance. $ ssh -i <username>-aws-keypair.pem root@<elastic IP address of EC2 instance> Tip: You can also use a terminal emulator such as PuTTY to test your connectivity. At publication, PuTTY does not support the extension.pem, so remember that you will also need to convert the key pair.pem file to a.ppk file before you can use it with PuTTY. 2. At the command prompt, type tmsh modify auth password admin. Caution: Because this login is visible externally, make sure to use a strong, secure password. 16

17 BIG-IP Virtual Edition Setup Guide for Amazon EC2 The terminal window displays the message: changing password for admin, and then prompts: new password. 3. Type in your new password and then press Enter. The terminal window displays the message: confirm password. 4. Re-type the new password and then press Enter. 5. To ensure that the system retains the password change, type tmsh save sys config, and then press Enter. Important: Without your security key pair, you cannot access this AMI. Once you login with your key pair, you could create a root password. However, if you decide to do this, choose the root password wisely, bearing in mind that depending on your Security Group policies, this login may provide external SSH access. The Admin password is now changed. Adding a secondary IP address Secondary IP addresses are required for each subnet on which a Virtual Server resides. This task documents the process of adding a Secondary IP address to a network interface of a BIG-IP VE instance. This process describes the Amazon Web Services user interface at the time of this release. 1. From the Services tab at the top of the Amazon Web Services Management Console screen, select EC2. 2. In the Navigation pane, select Network Interfaces. The Network Interfaces screen opens. 3. Identify the External network interface (that is the NIC that uses the subnet). 4. Right-click the external NIC, and select Manage Private IP Addresses. The Manage Private IP Addresses dialog box opens. 5. Below the list of existing addresses and the corresponding subnets, select Assign a secondary private address. 6. Click Yes, Update. AWS adds a new IP address to the subnet. 7. Click Close. The IP address you just added is displayed in the Secondary Private IPs column of the Network Interfaces screen. Important: Make a note of the new IP address so that you will have it readily available when you want to access your VPC. Inside Amazon Web Services, this new secondary IP address is used to access the BIG-IP VE virtual server in the Amazon EC2 configuration. Tip: Before these IP addresses can be used with the BIG-IP VE system, they must be configured within TMOS. Important: Before proceeding, verify that your allow-only-ssh-https-ping security group rule is functioning properly. That is, confirm that you can successfully access the BIG-IP VE using SSH, HTTPS, and PING, but other protocols (such as HTTP) are blocked. 17

18 Deploying BIG-IP Virtual Edition Making the secondary IP address accessible You may need to make the external IP address for the virtual server Internet-accessible. Tip: Recall that the IP address for the virtual sever is the secondary IP address that is assigned to the external (ETH1) network interface. 1. From the Services tab at the top of the Amazon Web Services Management Console screen, select EC2. 2. In the Navigation pane, select Elastic IPs. The Addresses screen opens. 3. Click Allocate New Address. The Allocate New Address dialog box opens. 4. From the EIP used in list, select VPC. 5. Click Yes, Allocate, and then click Close. 6. Right-click the just-created address, and select Associate from the popup menu. The Associate Address dialog box opens. 7. From the Network Interface box, use the Network Interface ID to select the virtual server's just-created external interface. Important: Make a note of the new external IP address so that you will have it readily available when you want to access your VPC. When you configure BIG-IP VE, this secondary private IP address identifies your virtual server outside of AWS. Now you must license the BIG-IP Virtual Edition (VE) and add your configuration objects. For most of these tasks, you can use the Config utility For information on performing these tasks, see AskF5.com ( You must create and map VLANs and then create self IP addresses for those VLANs manually. Creating VLANs mapped to external and internal interfaces Before you can configure VLANs, you must license the BIG-IP VE and set up the root and admin passwords. Use the Setup Utility to perform these tasks. You will create two VLANs (an external and an internal). You map the external VLAN to the 1.1 interface and the internal VLAN to the 1.2 interface. Important: When you complete the licensing tasks, you'll need to log in again with the admin password. At this point, you'll have the option between the Standard and Advanced Network configuration. The standard option uses the Setup Utility to step you through each setting. Because you only to need to set up a couple items, it's better to choose advanced options and configure them manually. 1. Under Advanced Network Configuration on the Setup Utility Network page, click Finished to close the Setup Utility. 2. On the Main tab, click Network > VLANs. The VLAN List screen opens. 3. Click Create. The New VLAN screen opens. 4. In the Name field, type external. 18

19 BIG-IP Virtual Edition Setup Guide for Amazon EC2 5. For the Interfaces setting, click interface 1.1 from the Available list, and use the Move button to add the selected interface to the Untagged list. 6. You can leave the remaining controls as is. The system will use default settings. 7. Click Repeat. 8. Repeat steps 4 and 5, but this time type Internal for the Name and select 1.2 for the interface number. Tip: You may have to select the 1.1 interface and use the Move button to remove it from the Untagged list, so that when you are finished, only the 1.2 interface is listed. 9. Click Finished. The screen refreshes, and displays the two new VLANs in the list. Creating self IP addresses for external and internal VLANs You must assign one self IP address to the external VLAN and another self IP address to the internal VLAN. 1. On the Main tab, click Network > Self IPs. The Self IPs screen opens. 2. Click Create. The New Self IP screen opens. 3. In the IP Address field, type the private IP address that is assigned to the ETH1 network interface. 4. From the VLAN/Tunnel list, select external. 5. Click Repeat. 6. In the IP Address field, type the private IP address that is assigned to the ETH2 network interface. 7. From the VLAN/Tunnel list, select internal. 8. Click Finished. One self IP address is assigned to the external VLAN and the other is assigned to the internal VLAN. Now that you have your VLANs configured and associated with the EC2 self IPs, you can proceed with configuring configuration objects such as pools and servers normally. Recall that the Amazon EC2 configuration uses the secondary private IP created earlier in this process to access the BIG-IP VE virtual server. 19

20

21 Index Index A Admin password changing 16 setting 16 AMI launching new 14 C CPU and guest definition 8 D deployment overview 12 E EC2 AMI launching 14 EC2 VPC creating 12 Elastic Compute Cloud and compatible versions 8 elastic IP address making accessible 18 environment, for guest 8 external subnet adding route for accessibility 14 G guest environment 8 H hypervisor, See guest environment. hypervisor guest definition 8 I IP address making secondary accessible 18 IP addresses adding secondary 17 K key pairs creating 12 M maximum allowed throughput rate 8 N network interface adding 15 P password changing Admin 16 setting Admin 16 product license 8 R route adding for external subnet 14 S secondary IP address making accessible 18 secondary IP addresses adding 17 security groups creating 13 Setup utility 12 subnet adding additional 13 adding route for external 14 T task list for deploying on virtual machine 12 U untagged interfaces configuring 18 V virtual configuration, and hypervisor guest definition 8 virtual machine settings 8 virtual private cloud creating 12 VLAN external creating self IP addresses for 19 VLANs creating with untagged interfaces 18 management port making it accessible 16 21

22 Index 22