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

baileyt_229731's avatar
baileyt_229731
Icon for Nimbostratus rankNimbostratus
Oct 19, 2015

disconnection from the network to F5 after ESXi patching

This morning we patched a few of our 5.5 hosts from build 2718055 to 3116895 and we were unable to ping the two F5's (big-ip load balancers) in the environment after the upgrade. I'm the VMware admin and don't know much about the F5 appliances other than the appliances are stamped with version 10.2.1-297.0 and when I reverted one of the hosts back to 2718055 the F5's were visible on the network again. We have around 30 other vm's running on these hosts after the upgrade without an issue. It was only the F5's giving us a problem. Anyone have any thoughts?

 

2 Replies

  • Andy_McGrath's avatar
    Andy_McGrath
    Icon for Cumulonimbus rankCumulonimbus
    Oct 19, 2015

    Could be the upgrade to ESXi change the eth0 MAC address in the VM, the F5 VE license is linked to the eth0 MAC so if it changes the license will become invalid so will not load or run the F5's config.

     

    Take a copy of the F5 VM's .vmx files before upgrading and check the settings, after upgrade compare the backup with new vmx and see if anything on eth0 has changed.

     

  • baileyt_229731's avatar
    baileyt_229731
    Icon for Nimbostratus rankNimbostratus
    Oct 21, 2015

    I'm pretty confident it's the version. 10.2.x doesn't "officially" support anything above ESXi 5.0 and I'm guessing we're lucky to have it running at all on 5.5. The admin for the F5's is working on remediating to at least 11.5.0 which has 5.5 support.