ESX/ESXi reports a vmnic as down and displays the error: Failed criteria: 32
Article ID: 343115
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- ESX 4.1 and ESXi 4.1 and 5.0 reports an uplink as down or redundancy lost.
- You see the error:
- 102991187460us: [vob.net.dvport.uplink.transition.down] Uplink: vmnic1 is down. Affected dvPort: 1022/fd da 04 50 31 6d 42 cc-e9 37 47 67 a3 0b 2b 0c. 0 uplinks up. Failed criteria: 32.
102991187471us: [vob.net.dvport.uplink.transition.down] Uplink: vmnic5 is down. Affected dvPort: 1022/fd da 04 50 31 6d 42 cc-e9 37 47 67 a3 0b 2b 0c. 0 uplinks up. Failed criteria: 32.
102991187473us: [vob.net.dvport.uplink.transition.down] Uplink: vmnic7 is down. Affected dvPort: 1022/fd da 04 50 31 6d 42 cc-e9 37 47 67 a3 0b 2b 0c. 0 uplinks up. Failed criteria: 32.
- 6699435376000us: [vob.net.pg.uplink.transition.down] Uplink: vmnic3 is down. Affected portgroup: VLAN 519. 1 uplinks up. Failed criteria: 32
- 102991187460us: [vob.net.dvport.uplink.transition.down] Uplink: vmnic1 is down. Affected dvPort: 1022/fd da 04 50 31 6d 42 cc-e9 37 47 67 a3 0b 2b 0c. 0 uplinks up. Failed criteria: 32.
Environment
VMware vSphere ESXi 5.5
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.0
VMware ESX 4.1.x
VMware ESXi 4.1.x Installable
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.0
VMware ESX 4.1.x
VMware ESXi 4.1.x Installable
Resolution
Note: This issue requires investigation of the physical network. This is not a VMware issue.
The Failed criteria code of 32 indicates the link has failed due to Beacon Probing detecting a problem. Beacon Probing sends beacons per VLAN between physical NICs in a team. When these are not received by other NICs means that there is a problem in the physical network.
In this scenario the physical NIC is still Up.
To verify the NIC status, go to Configuration > Network Adapters on the vSphere Client and look at the columns for the NIC in question. On the ESX/ESXi console/shell, you see the status of the NIC using this command:
#esxcfg-nics -l
If you do not need to be notified of these issues, consider changing the Network Failover Detection on the vSwitch from Beacon Probing to the default Link Status only.
Note: There is a known issue affecting ESX 4.1, ESXi 4.1 and ESXi 5.0, resulting in the generation of unnecessary vobs messaging indicating vmnic is down when a virtual machine is migrated from one host to another. This is generated because the Beacon status is not updated on the destination host, so the Beacon Probing can incorrectly trigger a vmnic down message.
To resolve this issue in ESX 4.x, download Patch ESX410-201204401-SG. For more information, see VMware ESX 4.1 Patch ESX410-201204401-SG: Updates VMkernel, VMKLinux, Tools, others (2013067).
The Failed criteria code of 32 indicates the link has failed due to Beacon Probing detecting a problem. Beacon Probing sends beacons per VLAN between physical NICs in a team. When these are not received by other NICs means that there is a problem in the physical network.
In this scenario the physical NIC is still Up.
To verify the NIC status, go to Configuration > Network Adapters on the vSphere Client and look at the columns for the NIC in question. On the ESX/ESXi console/shell, you see the status of the NIC using this command:
#esxcfg-nics -l
If you do not need to be notified of these issues, consider changing the Network Failover Detection on the vSwitch from Beacon Probing to the default Link Status only.
Note: There is a known issue affecting ESX 4.1, ESXi 4.1 and ESXi 5.0, resulting in the generation of unnecessary vobs messaging indicating vmnic is down when a virtual machine is migrated from one host to another. This is generated because the Beacon status is not updated on the destination host, so the Beacon Probing can incorrectly trigger a vmnic down message.
To resolve this issue in ESX 4.x, download Patch ESX410-201204401-SG. For more information, see VMware ESX 4.1 Patch ESX410-201204401-SG: Updates VMkernel, VMKLinux, Tools, others (2013067).
To resolve this issue in ESXi 4.1, download the patch Patch ESXi410-201204401-SG. For more information, see VMware ESXi 4.1 Patch ESXi410-201204401-SG: Updates Firmware (2013069).
Note: This issue is resolved in ESX/ESXi 4.1 Update 3, ESXi 5.0 Update 2 and ESXi 5.1. For more information about these versions, see:
- VMware ESXi 4.1 Update 3 Release Notes
- VMware ESXi 5.0 Update 2 Release Notes
- VMware ESXi 5.1 Release Notes
You can download the latest release from the VMware Download Center.
Additional Information
Feedback
Yes
No
Powered by
