vmnic using qedentv linked down with below vmkernel log.
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)[OSAL_LINK_UPDATE:1285(vmnic#)]HWFN:0, Duplex:1, Link_up:0, Speed:0Mbps, udev->link_state:1
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)[OSAL_LINK_UPDATE:1285(vmnic#)]HWFN:0, Duplex:1, Link_up:0, Speed:0Mbps, udev->link_state:1
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)qedentv: OSAL_LINK_UPDATE:1318: NIC Link is down. vmnic#
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel:
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)qedentv: OSAL_LINK_UPDATE:1318: NIC Link is down. vmnic#This article explains how to understand meaning of this log.
VMware vSphere ESXi
According to the vmkernel log, we could understand link was recognized based on HW register information.
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)[OSAL_LINK_UPDATE:1285(vmnic#)]HWFN:0, Duplex:1, Link_up:0, Speed:0Mbps, udev->link_state:1
Link_up:0 -> Based on HW register information, driver determined the link down
Speed:0Mbps -> Based on HW register information, driver cannot recognize pre-defined link speed and set 0
udev->link_state:1 -> As a perspective of driver's software Layer, the link was treated as link upBased on the link information from HW register, driver explicitly have the link down.
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu##:#######)qedentv: OSAL_LINK_UPDATE:1318: NIC Link is down. vmnic#qedentv driver treated its link down when it cannot read pre-defined link speed from HW register, so we could say link down was initiated because qedentv driver failed to read legitimate link speed from HW register.
Broadcom recommends validating the physical network path, including: