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...
rmarsf_152525's avatar
rmarsf_152525
Icon for Nimbostratus rankNimbostratus
May 22, 2014

thanks for your answers. ok. sorry for the question. it seems what was causing all my pain was persistent udev rules. I thought it was the F5 somehow deciding what should be eth0 / mgmt all this time. thanks again for taking the time to consider my question.

 

  • rmarsf_152525's avatar
    rmarsf_152525
    Icon for Nimbostratus rankNimbostratus
    May 26, 2014
    Ok. no, using virtualbox. I found the answer. chmand (chassy manager) on startup, inspects adapters and assigns to interfaces. chmand skips the adapter if it was set to Intel adapter type. saw it being inspected and skipped in /var/log/ltm. setting adapter 1 to PCnet-FAST III (Am79C973) it was inspected and selected as the management interface. Note, setting any other adapters to Am79C973 they would not be assigned to LTM interfaces - and your interfaces would be empty. Setting those to Intel PRO/1000 MT Server (8245EM) worked. I have not tried other adapter types - so the above solution may not be the only one. I also don't know why this works at this point.