For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

rmarsf_152525's avatar
rmarsf_152525
Icon for Nimbostratus rankNimbostratus
May 22, 2014

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

I want my management interface to use adapter 0 of my VM. It has an affinity to adapter 1 not matter what I seem to do. I have tried editing base-mac in bigip_base.conf. No matter what I do it uses...
Brad_146558's avatar
Brad_146558
Icon for Nimbostratus rankNimbostratus
May 22, 2014

Also, if you are in a VMWare environment make sure the first NIC's type is set to 'Flexible' and subsequent NICs are set to VMXNet3.

 

The instructions below are ONLY if you are adding NICs to an existing deployment and you know for sure things are getting reordered. I'd test them in a lab environment before running them on your production. That is my only warning =)

 

First step for adding NICs after the fact in a virtual environment is to screenshot the hardware settings in your hypervisor so you can match the NICs to the MAC addresses after you make any changes. Do the same inside of the BIG-IP as well. When you do this in the BIG-IP document your VLAN settings as well, I've seen these get reordered as well.

 

Before bringing the BIG-IP down to add the NIC, run this command. touch /service/mcpd/forceload

 

Now bring the machine down and add the NIC.

 

Compare your documentation against what is currently running right now, check your pools and do some basic functionality tests, if everything looks good then you don't need to go any further.

 

If the NICs are out of alignment at this point, via the command line run 'rm /var/db/mcpd*' reboot and check the NIC alignment again. If things still aren't working right check your VLAN alignment in the web interface.