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

Sona 

Hello, while I have not run into this scenario this is something to take a look at, using GenAI to help with the information 

1. VLAN Configuration: Ensure that the VLANs are correctly configured on both the F5 VE and the ACI side. Since you mentioned that multiple VLANs are allowed, double-check that the VLAN IDs match on both sides and that they are properly tagged.
2. Trunk Mode: Verify that the trunk mode settings are consistent across all devices. Since you have allowed VLANs 0-4094, make sure that this range is correctly configured on the F5 VE, VMware, and ACI sides.
3. LACP Disabled: Since LACP is disabled on all sides, ensure that the interfaces are correctly configured for static trunking. Sometimes, issues can arise if the interfaces expect LACP but it's disabled.
4. ARP Learning: The issue with ARP learning might be due to misconfigurations in the network settings. Ensure that the ARP settings are correctly configured on the F5 VE and that there are no firewall rules blocking ARP traffic.

Regarding your specific question about passing multiple VLANs from F5 to Nutanix VMs, it is indeed possible. The key is to ensure that the VLANs are correctly tagged and that the trunk ports are properly configured to allow the VLAN traffic. Here are some steps to consider:

• VLAN Tagging: Ensure that the VLANs are tagged correctly on the F5 VE and that the Nutanix VMs are configured to recognize these VLAN tags.
• Trunk Ports: Verify that the trunk ports on the F5 VE and the Nutanix VMs are configured to allow the necessary VLANs.
• Network Policies: Check the network policies on both the F5 VE and the Nutanix VMs to ensure that they allow the VLAN traffic.
  
  If these steps do not resolve the issue, it might be helpful to review the specific configurations and logs on the F5 VE and the ACI to identify any discrepancies or errors.