In understanding (kinda) how slot reservations work with clusters, what I do not understand is why our slot sizes are changing in terms of RAM (MB) when we start up the vShield Manager to support a Cloud Director installation.
So in the lab we have a few hosts and all is running fine with a heathly amount of slots as depicted here:
Then when I startup the vShield Manager (note that no Cloud VM's are running hence no vShield Edge devices are running) the slots sizes change as depicted here:
Would setting obnormally affect the cluster?
das.slotmeminmb = max bound on the memory slot size.
das.slotcpuinmhz = max bound on the cpu slot size.
Or is this is 'normal'?
I am concerned with the drain on cluster capacity.
In looking at this further, it was the memory reservation for the vShield Manager (VMware-vShield-Manager-4.1.0-287872.ova) deployment for Cloud Director package which was affecting the slot size.
I wonder if this reservation is necessary for vShield Manager?
So did you test the HA capability of VSE device ? how long it takes for backup VSE to initiate for specific network ? what happened to your sessions through VSE , how long they were down ? (my tests shows several minutes , looking for another verification)