When you deploy BIG-IP® VE from the Azure Marketplace, BIG-IP VE has a single NIC and only one available IP address.
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 is used for which traffic.
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.
F5 maintains templates that you can use to create a multi-NIC deployments. For more information, see https://github.com/f5networks.
When you deploy BIG-IP® VE with multiple NICs, your management and data (application) traffic can share the external NIC and use the same IP address (with different ports). The internal NIC is used for internal traffic.
In this example, eth0 is used for the external VLAN, and eth1 for the internal VLAN.
There are a few cautions to this solution.
You can also enable config sync now. You should not change the provision.1nic database variable value when you do.
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 can be used for a virtual server.
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.
Then you can deploy an instance of BIG-IP VE. If necessary, select the availability set during deployment.