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

Seth_81884's avatar
Seth_81884
Historic F5 Account
Jun 11, 2014

Another check you can do is to confirm the mapping of the BIG-IP management interface to the correct network adapter in the Virtual Machine Properties.

 

On the BIG-IP: [root@localhost:Active:Standalone] config ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:0C:29:XX:XX:XX

 

From the vSphere Client click on: the deployed guest > Edit virtual machine settings > Network Adapter 1. Confirm that the MAC Address matches the output you recieved with ifconfig and that the device status is 'Connected' and 'Connect at power on'.

 

  • Steve_M__153836's avatar
    Steve_M__153836
    Icon for Nimbostratus rankNimbostratus
    Jun 11, 2014
    This is a good catch. Sorry I didn't remember this. Every VE I've deployed has always come up with eth0 matched to the first virtual NIC, but if that didn't happen for some reason this could easily explain the problem.