F5 in Azure Question

Hi Devlin,

you may choose either a 1-NIC or 2-NIC depending if you want to seperate MGMT and PROD traffic or not.

https://github.com/F5Networks/f5-azure-arm-templates/tree/master/supported/standalone

I always keep the pre-installation wizard as simple as possible and only perform a minimalistic setup without specifying additonal IPs (just the SelfIP for each interface). Right after the installation is completed, I'm going to remove most of the wizard based configuration objects and start my own configuration from the scratch. I'm heavily OCD'ed and simply MUST to use my own naming convention... ;-)

You can later add as many as needed additional IPs to your F5-VM-Interfaces via the Azure Management and then use those IPs for Virtual Servers or SNAT-Pools.

Note: If you plan at some point to extent your single-node F5 to become a cluster, then make sure to use a the 2-NIC template to seperate your MGMT and PROD interfaces. By doing so you can reuse your PROD network as a sync/failover link. And with the help of an front-ending Azure-LB you will be able to create SYNC-Failover cluster pretty much comparable to the ones you are using in a fully featured Layer2 environment (far better than the feature limited Active/Active via-LB templates or the pretty much overengineered Active/Passive via-API templates supported by F5).

Cheers, Kai