NimbostratusHey Ron
What you're basically asking for is a Single-NIC Deployment which is quite common in Cloud deployments (Azure, AWS etc.). This can be done for local VMs as well and here is a complete guide on how to deploy it from an ESXi perspective.
In order to turn your BIG-IP into a Single-NIC deployment is to delete interfaces 2,3 and 4, leaving you only with the first one. This kind of goes outside of how a normal BIG-IP is being deployed and changes how it behaves. For instance, you cannot configure it in an HA mode in a Single-NIC deployment. Usually you have one interface for management, one for internal and one for external. The last one can be used for HA but I usually just run it over the internal interface.
I have a guide of the traditional setup on the old DevCentral site:
It has links to the back-end server that you can load-balance to and a Linux "Jumphost" for MGMT and External access.
My guide runs the whole environment locally on your computer and can be set up within minutes.
I'm curious, what requires you to deploy it in a Single-NIC (one-arm) mode?
NimbostratusAt this point, it is a matter of simplicity. While I would prefer to deploy with 4 physical interfaces, I will need to purchase a manged switch to allow me to break out the individual interfaces. If I am going to do that, I may think about purchasing a used server with multiple interfaces instead.
MVPin principle you can manage the system on the external interfaces (look at port lockdown), not best practice but for testing that is possible.
