After attempting to disable Flow Control on Intel adapters using the i40en driver, users may observe the following:
esxcli network nic pauseParams set are immediate but lost after a reboot.esxcli system module parameters set --module i40en --parameter-string "pause_rx=0 pause_tx=0" result in inconsistent reporting after a host reboot.esxcli network nic pauseParams list may show one vmnic as false (Disabled) while another vmnic returns to true (Enabled), even though the module parameters are correctly set to 0.VMware vSphere ESXi
This is a reporting inconsistency between the ESXi runtime network stack and the driver module state.
esxcli network nic pauseParams list queries the runtime network stack. This stack is initialized during boot and does not automatically inherit its "display" state from the driver's advanced module parameters unless those parameters are explicitly pushed to the stack.To ensure Flow Control is disabled and consistently reported across reboots, verify the operational state and use the local.sh method to synchronize the runtime reporting.
esxcli network nic get -n vmnicX
#Example for a 2-port card:
esxcli system module parameters set --module i40en --parameter-string "pause_rx=0,0 pause_tx=0,0"
esxcli network nic pauseParams set, the runtime commands must be executed at every boot:esxcli network nic pauseParams set -n vmnic0 --rx=false --tx=false
esxcli network nic pauseParams set -n vmnic1 --rx=false --tx=false