which condition will vCenter Server communicate directly with a vSphere HA slave?

Under which condition will vCenter Server communicate directly with a vSphere HA slave?

Under which condition will vCenter Server communicate directly with a vSphere HA slave?

A.
When distributing the host compatibility list

B.
When an update is needed for the list of powered on VMs

C.
When powering on a FT secondary VM

D.
When distributing cluster configuration updates



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Silencioso

Silencioso

If the host membership list, compatibility list, or cluster configuration is updated, vpxd reports these changes to the master. The master advertises to the slaves that updated configuration information is available. The hosts detect that their configuration information is out of date and fetch the new information from the master. Each host writes the updated configuration information to its local storage
VMware vSphere 5.0 What’s New

Silencioso

Silencioso

The process to protect a virtual machine:
• The virtual machine is powered off. Its protection state is N/A.
• The user powers on the virtual machine.
• vpxa tells vpxd that a virtual machine powered on.
• vpxd adds the virtual machine to the protected set for the cluster. vpxd changes the virtual machine’s protection state to Unprotected.
• vpxd tells the master agent with which it is in contact for that cluster to protect the virtual machine. • If the master owns the datastore, it updates the protectedlist file and notifies vpxd. • vpxd updates the configuration information and changes the state of the virtual machine to Protected.
VMware vSphere 5.0 What’s New

celembribor

celembribor

according VMware vSphere 5 Clustering Technical Deepdive (index 561): “vCenter is also responsable for communicationg configuration changes in the cluster to the host which is elected as the master” can’t be D.

celembribor

celembribor

vCenter may communicate to the Slaves in certain situations, such as:
* Scanning for an existing Master.
* If the Master states that it cannot reach a Slave, vCenter will contract the Slave to determine why.
* When powering on a FT Secondary VM.
* When host is reported isolated or partitioned.

runwinged

runwinged

i agree with celembribor
so C is correct

kopigao

kopigao

confirmed the answer is C, verified in VMware mock up test