How does Bigip F5 LTM select which VM Adapter it assigns to the management interface

i will add before i leave for the weekend. I did manage to find a configuration that consistently assigned the management interface successfully to eth0. Again, I do not know exactly why or if this is the only configuration, but in any case:

I have 3 private networks. (with 2, it failed inconsistently) go figure. eg, in Vagrant file: bigip_config.vm.network "private_network", ip: "172.16.1.55" bigip_config.vm.network "private_network", ip: "10.10.10.16" bigip_config.vm.network "private_network", ip: "192.168.61.6"

and I make sure the nic type using the virtual box provider:

     bigip_config.vm.provider :virtualbox do |vb|
         vb.customize ["modifyvm", :id, "--nictype1", "Am79C973"]
     end

any my vagrant up is consistently booting with mgmt on eth0.

go figure!

Big ip takes the first interface in the ltm as management (eth0)

go for ssh and do (ifconfig eth0 X.X.X.X netmask Y.Y.Y.Y) do ifconfig eth0 to check that the ip has been taken

or fix this ip as managment by tmsh create sys management-ip X.X.X.X/Z

but in both cases u should disable the dhcp option from the mgmt interface by tmsh command

for other interfaces in the virtual machine they will be the data interfaces (1.1 1.2 1.3 1.4 ..etc)

so interface 1 (eth0): is mgmt interface 2: is 1.1 interface 3 is : 1.2 interface 4 is :1.3

Hi Hamzeh. Thanks so much for your reply. What I'm seeing is that chmand is skipping the first interface and instead assigning a separate interface (in some cases) to mgmt. literally, it would do this, and in the above example, I only added an additional host-only adapater (virtualbox) and chmand then selected eth0 consistently (i.e to fix it). i post some logs to illustrate when i get a chance