Network uplink redundancy lost with failed criteria:160
Article ID: 419622
Updated On:
Products
Issue/Introduction
Evidences from the log files with failed criteria:160
Log File: /var/run/log/vobd.log2025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [vob.net.pg.uplink.transition.down] Uplink: vmnic3 is down. Affected portgroup: vMotion. 1 uplinks up. Failed criteria: 1602025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [vob.net.pg.uplink.transition.down] Uplink: vmnic3 is down. Affected portgroup: VLAN XX- Backup. 1 uplinks up. Failed criteria: 1602025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [vob.net.pg.uplink.transition.down] Uplink: vmnic3 is down. Affected portgroup: vMotion. 1 uplinks up. Failed criteria: 1602025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [vob.net.vmnic.linkstate.down] vmnic vmnic3 linkstate down2025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [vob.net.vmnic.linkstate.down] vmnic vmnic3 linkstate down2025-XX-XXXXX:XX:XX.XXXX In(14) vobd[XXXXXXX]: [netCorrelator] XXXXXXXXXXXXXX: [esx.clear.net.vmnic.linkstate.up] Physical NIC vmnic3 linkstate is up
This can lead to connectivity issues across the ESXi environment for any traffic traversing a vSwitch or port group configured with Beacon Probing, including iSCSI storage, virtual machines, vCenter services, vMotion, and other dependent components.
Environment
VMware vSphere ESXi
Cause
This issue can occur when Beacon Probing is enabled but the NIC team contains fewer than three physical uplinks
Resolution
To resolve this issue, set Network Failover Detection to Link Status Only. Avoid using Beacon Probing in combination with the Route based on originating virtual port load-balancing policy
Additional Information
For more information on Beacon Probing, see What is beacon probing?
For reference KB: Network adapter (vmnic) is down or fails with a Failed Criteria Code
Feedback
