Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Coliver222_3604's avatar
Coliver222_3604
Icon for Nimbostratus rankNimbostratus
May 03, 2018

F5 lab setup, not able to ping

Hoping some of you pros can give me a hand here. I'm trying to set up a very basic topology with Vmware/GNS3 to learn the basics of big ip LTM.   I'm unable to access or ping my the any IP address...
application delivery
big-ip
LTM
René_Geile's avatar
René_Geile
Icon for Cirrus rankCirrus
May 04, 2018

Hi,

 

from my experience a lot of trouble is caused if VMWare is dynamically changing interface order or changing MAC adresses which sometimes happens after reboot or any host system configuration changes. I suggest to carefully check in the hypervisor and in F5 guest: Is the interface for internal VLAN in hypervisor having the same MAC like the interface for internal VLAN in F5 VM? Check every VLAN and interface. If something is wrong you need to remap the interfaces to the correct VLANs in the hypervisor.

 

There are instructions in the web how to configure static MACs in VMWare Workstation to prevent this from happening.

 

You can ignore the VLAN ID 409x in F5. The F5 platform always works with a VLAN ID internally, even if the traffic is send out untagged to the network. I suggest to set the VLAN ID to the ID used within your network/switches even for untagged traffic, like some kind of documentation.