Inbound network traffic received on incorrect vSwitch uplink with Broadcom BCM57414 NPAR
search cancel

Inbound network traffic received on incorrect vSwitch uplink with Broadcom BCM57414 NPAR

book

Article ID: 439194

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Network connectivity issues occur when a virtual machine on an ESXi host communicates with a virtual machine on the same ESXi host.

  • Packet captures indicate outbound traffic (e.g., ICMP echo requests) exits through the expected virtual switch uplink but does not exit the host.

  • Inbound return traffic (e.g., ICMP echo replies) is received on a different Network Partition (NPAR).

  • The mismatched NPAR partition is assigned to a completely different virtual switch.

  • The physical NIC incorrectly routes the return packet across partitions on the shared physical interface.

Environment

VMware vSphere ESXi

Broadcom BCM57414 network adapters configured with NPAR

Cause

The physical NIC's internal hardware switching, Virtual Ethernet Bridging (VEB) incorrectly routes return traffic internally across NPAR partitions, bypassing the ESXi virtual switch.

Resolution

This is a condition that may occur in a VMware vSphere environment.

 

Workaround: 

Disable the internal hardware switching behavior directly within the host hardware BIOS by modifying the EVB method:

  1. Reboot the affected ESXi host and access the system BIOS.

  2. Navigate to the Device Configuration Menu for the Broadcom BCM57414 network adapter.

  3. Locate the Default EVB method configuration setting.

  4. Change the value from VEB to None.

  5. Save the configuration changes and allow the host to boot into ESXi.

Note: SR-IOV must not be in use as VEB is generally required for SR-IOV environments

Additional Information

VMs drop out of network randomly on NPAR enabled Dell Servers

Broadcast and Multicast Traffic looping back on uplink connected to distributed switch (vDS).