F5 Self IP is not reachable over the network. New F5 virtual env.

Hi Sona,

Can you check in tmsh mode on your VE, why you are getting all the same MAC Address for all the interfaces, if the output is global instead of unique this could be the reason for getting same mac address

list sys db vlan.macassignment
sys db vlan.macassignment {
    value "unique"
}

The possible database values for vlan.macassignment are:

• unique - Each VLAN is assigned a unique MAC address this is only true as long as there are available MAC addresses to assign. If you create many VLANs, the BIG-IP system will start assigning the same MAC address to multiple VLANs. This is the default database value for vlan.macassignment. Note that this is only true as long as there are available MAC addresses to assign. If you create more VLANs than there are available MAC addresses, multiple VLANs are assigned the same MAC address.
• global - All VLANs are assigned the same MAC address.
• vmw-compat - Specific to VE systems, only one interface is allowed per VLAN, and the VLAN will use the MAC address of its corresponding interface. No trunks may be attached to these VLANs.

Note: Multiple VLANs can safely share the same MAC address as long as your other network devices support a per-VLAN MAC address table. This allows those devices to learn the same MAC address on multiple VLANs without issue. This is a common feature.

Note: VLAN MAC assignment may change after upgrade, restart, or restarting the mcpd process.

Viewing the current database variable

To view the current database variable for vlan.macassignment enter the following command:

tmsh list /sys db vlan.macassignment

Changing the database variable using tmsh

To change the database variable with tmsh, use the following syntax:

tmsh modify /sys db vlan.macassignment value <preferred variable unique, global or vmw-compat>

====================================

Also can you make sure you are not using 

default vmxnet3 driver

Trunking is supported on BIG-IP Virtual Edition (VE) from BIG-IP version 13.1.0 and later, and it is intended to be used with the Single Root I/O Virtualization (SR-IOV) interfaces but not with the default vmxnet3 driver.

Note: You can enter tmsh list net trunk to display the trunks configured on your BIG-IP system.

Trunking of the interfaces with the vmxnet3 driver may result in unstable network traffic.

Environment

• BIG-IP Virtual Edition running in the VMWare ESXi hypervisor
• A trunk is configured with interfaces, which use vmxnet3 driver

Cause

Trunking is not supported for the default vmxnet3 driver.


https://my.f5.com/manage/s/article/K14513

https://my.f5.com/manage/s/article/K97995640

Rate if it helps isolate your issue.

HTH

F5 Design Engineer