When you deploy BIG-IP VE from the Azure Marketplace, BIG-IP VE has a single NIC and only one available IP address.
If you prefer a configuration with multiple NICs and/or IP addresses, you can deploy BIG-IP VE by using:
F5 maintains templates that you can use to create a multi-NIC deployments. For more information, see https://github.com/F5Networks.
For more information about multiple NICs in Azure, see https://azure.microsoft.com/en-gb/updates/ga-multiple-ips-per-nic.
When you create a multi-NIC configuration of BIG-IP VE in Azure, you can specify which NIC to use for which traffic.
You may want to have management and data (application) traffic on the same NIC. If you do:
A configuration with separate NICs and IP addresses is more of a traditional BIG-IP VE setup, with a management, internal, and external subnet, for example.
When you deploy BIG-IP VE with multiple NICs, you can use a separate NIC for management, data (application), and internal traffic.
In this configuration, each NIC can have one or more IP addresses associated with it. For example, your external NIC can now have multiple IP addresses, each of which you can use as a virtual server.
This deployment shows three subnets:
Traffic flows from clients through BIG-IP VE to application servers.
Note: This example shows a single, standalone BIG-IP VE. To use config sync with two or more BIG-IP VEs in the same availability set, add all virtual server IP addresses to traffic group none.
When you deploy BIG-IP VE with multiple NICs, you can separate your management, data (application), and internal traffic so that each has its own NIC.
To create this multi-NIC configuration in Azure, you need the following resources:
Depending on your region and the version of BIG-IP VE you want to deploy, you must choose a BIG-IP VE image. To view the list of available images:
The publisher is
Then you can deploy an instance of BIG-IP VE. If necessary, select the availability set during deployment.
After you deploy BIG-IP VE, you must:
In the Azure portal, there is an option to reset the password for your virtual machine.
You cannot use this option to reset the password for BIG-IP VE.
Instead, to reset the password for an account that has access to BIG-IP VE, complete the following steps.
Before you begin, note the name of the admin user whose account you want to reset. If you used an SSH key when you created the instance, you can use the
admin account to access BIG-IP VE.
In the Azure portal, click.
Filter the list to find your virtual machine and select it.
On the Virtual machine blade, click Extensions.
Click Custom Script for Linux and then click Create.
In the Command field, type
tmsh modify auth user <username> password <password>.
After several minutes, the extension shows in the list. When it is complete, the status changes to
You can now log into BIG-IP VE by using this username and password.
Choose the Microsoft Azure instance based on the F5 license you need. For more information about F5 licenses, see https://f5.com/products/how-to-buy/simplified-licensing.
F5 recommends the following Azure instances for this release of BIG-IP VE.
Note: Instance types with similar vCPU and memory are also supported.