qfle3 Adapter link state incorrect after interface is marked down and physical link status changes
Article ID: 337992
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
Users can bring down an interface administratively using esxcli network nic down command. When an interface is marked down administratively and qfle3 driver receives a link up event, it still tries to communicate the link status change to vmkernel. Since interface is marked down, vmkernel rejects the notification. However, driver assumes that link state change has been communicated to vmkernel and does not send link up notification after the interface is made up using esxcli network nic up command. This results in the interface showing link down even though the physical link is actually up.
Users can bring down an interface administratively using esxcli network nic down command. When an interface is marked down administratively and qfle3 driver receives a link up event, it still tries to communicate the link status change to vmkernel. Since interface is marked down, vmkernel rejects the notification. However, driver assumes that link state change has been communicated to vmkernel and does not send link up notification after the interface is made up using esxcli network nic up command. This results in the interface showing link down even though the physical link is actually up.
Environment
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.7
Resolution
This is a known issue.
Currently, there is no resolution.
Workaround:
To workaround this issue, perform an additional esxcli network nic down followed by esxcli network nic up. This will ensure that the interface status is reflected correctly.
Currently, there is no resolution.
Workaround:
To workaround this issue, perform an additional esxcli network nic down followed by esxcli network nic up. This will ensure that the interface status is reflected correctly.
Feedback
Yes
No
Powered by
