These tasks are required to deploy BIG-IP® VE in the Microsoft Azure cloud environment. When you are done, you should be able to send traffic to your application servers through BIG-IP VE.
Each of these tasks is documented in detail later in this guide.
|1||Prepare to deploy BIG-IP VE||
|2||In Azure, deploy BIG-IP VE||You can find an F5® BIG-IP VE image in the Azure Marketplace and create an instance in the same resource group as your application. If you are using the Classic deployment model, the process will be different than the Resource Manager deployment model.|
|3||In Azure, create rules that allow inbound traffic to BIG-IP VE||When you deploy BIG-IP VE, a network security group is created in Azure. Add an inbound security rule to allow traffic to port 8443 for the BIG-IP Configuration utility and port 443 for your application.|
|4||SSH to BIG-IP VE and set admin password||If you used a key when you deployed the instance, use SSH to connect to BIG-IP VE and set a password for the admin account. The admin account is used to access the BIG-IP Configuration utility.|
|5||Log in to the BIG-IP Configuration utility and license, provision BIG-IP VE||Use the admin account to log in to the BIG-IP Configuration utility (https://<public-ip-address:8443>). Then license and provision BIG-IP VE.|
|6||In the BIG-IP Configuration utility, create a pool and virtual server||Create a virtual server, which provides a destination for your inbound web traffic and points to the pool of web servers. Because IP addresses in Azure may change, use the DNS name of your application server as the pool member.|
In order to create a virtual machine running BIG-IP® VE in Azure, you can deploy BIG-IP VE in the Azure Resource Manager deployment model.
For Azure Classic instructions, see Deploying BIG-IP VE in Azure Classic.
|Name||A name for the instance.|
|VM disk type||Accept the default or change it.|
|User name||A name for the person who will log in to BIG-IP VE. You can't change or access this field later.|
|Authentication type||SSH keys are more secure than passwords. For information about getting public keys, see Create a key pair for authentication.|
|Subscription||Accept the default or change it.|
|Resource group||A resource group is a logical container of related resources. Accept the default or change it.|
|Location||Accept the default or change it.|
For Azure Resource Manager instructions, see Deploy BIG-IP VE in Azure Resource Manager.
|Host Name||A name for the virtual appliance.|
|User name||A name for the person who will log in. You can't change or access this field later.|
|Authentication type||SSH keys are more secure than passwords. For information on getting public keys, see Create a public key for authentication.|
|Pricing Tier||For a list of instances supported for each F5 license, see Azure instances for BIG-IP VE.|
|Network||Select the Classic virtual network of your choice. If you accept the default, a new virtual network is created under the Resource Manager deployment model.|
|Storage||Select existing Classic storage or create new Classic storage.|
A separate web page opens.
BIG-IP VE logs you out.
|Name||A unique name|
|Destination Address/Mask||BIG-IP VE's private IP address|
|SSL Profile (Client)||clientssl|
|SSL Profile (Server)||serverssl|
|Source Address Translation||Auto Map|