Beacon probing is a network failover detection mechanism that sends out and listens for beacon probes on all NICs in the team and uses this information along with link status to determine link failure. Beacon probing detects failures, such as cable pulls and physical switch power failures on the immediate physical switch and also on the downstream switches.
ESXi periodically (in every 10 seconds) broadcasts beacon packets (approx. of 62 bytes) from all uplinks in a team. The physical switch is expected to forward all packets to other ports on the same broadcast domain. Therefore, a team member is expected to see beacon packets from other team members. If an uplink fails to receive three consecutive beacon packets, it is marked as bad. The failure can be due to the immediate link or a downstream link.
Note: Beaconing is most useful with three or more uplinks in a team because ESXi can detect failures of a single uplink. When there are only two NICs in service and one of them loses connectivity, it is unclear which NIC needs to be taken out of service because both do not receive beacons and as a result all packets sent to both uplinks. Using at least three NICs in such a team allows for n-2 failures where n is the number of NICs in the team before reaching an ambiguous situation.
*Do not use beacon probing with IP HASH load balancing
You must enable beacon probing when downstream link failures may impact availability and there is no Link State Tracking on the physical switch.
Thanks to VMware, Information is from the white paper provided by VMware.
0 comments:
Post a Comment