کد:
With vSphere 5, the process for determining if a host is isolated is only slightly different. A host
that is the master is looking for communication from its slave hosts; a host that is running as a
slave is looking for updates from the master host. In either case, if the master or slave is not
receiving any vSphere HA network heartbeat information, it will then attempt to contact the
isolation address (by default, the default gateway on the management network). If it can reach the
default gateway, then the ESXi host considers itself to be in a network partition state If the host can’t
reach the isolation address, then it considers itself isolated.
کد:
At this point, an ESXi host that has determined it is network-isolated will modify a special bit in
the binary host-X-poweronfile on all datastores that are configured for datastore heartbeating
The master sees that this bit, used to denote isolation, has been set and is therefore notified that this
slave host has been isolated. When a master sees that a slave has been isolated, the master locks
another file used by vSphere HA on the heartbeat datastore. When the isolated node sees that this
file has been locked by a master, it knows that the master is assuming responsibility for restarting
the VMs — remember that only a master can restart VMs — and the isolated host is then free to
execute the configured isolation response. Therefore, even if the isolation response is set to Shut
Down or Power Off, that action won’t take place until the isolated slave has confirmed, via the
datastore heartbeating structures, that a master has assumed responsibility for restarting the VMs.
3سپاس
LinkBack URL
About LinkBacks
نوشته اصلی توسط A.Yazdani
