VMware recommends having 3 or more physical NICs in a team for beaconing to work properly. If you have only 2 uplinks in a team, ESXi host will not be able to correctly determine which uplink has gone down.
Beacon probing is a network failover detection mechanism provided by VMware to detect upstream switch failures & also use to keep the track of health state of each uplink configured in a team.
Administrator has to configure link failure detection mechanism as part of teaming policy to detect uplink (pNIC0 and pNIC1) failures.
Considering this topology, which link detection mechanism would you recommend vSphere admin to configure in below mentioned failure scenarios:
1. Link Failure between Access and Distributed switch
2. Link Failure between Distributed Switch and Core Switch.
A VMware Virtual Switch is Layer-2 Switch embedded in VMkernel itself. It’s a software switch runs under the control of the ESXi Hypervisor and responsible for providing all network-based communications with and within an ESXi Host System.
Similar to esxcfg-*, vSphere has another Command Line API called “ESXCLI-*” which allows system admin or ESXi shell user to configure, manage & troubleshoot vSphere issues. In this article, we’re going to focus mainly on vSphere Networking related commands & we’ll be setting up basic ESXi Network configuration using ESXCLI-* commands.
Check out this Article to know about creating & configuring ESXi Networking using CLIs. This Articles deep-dive into step by step procedure of creating and deploying vSphere Networking on ESXi Host using esxcfg-vswitch APIs.