v.: 2020-09-04
Copyright of the European Union is effective (Copyright EU) (c) 2019 GENEREX Systems GmbH, Hamburg, Germany, All rights reserved
TEL +49(40)22692910 - EMAIL generex@generex.de - WEB www.generex.de (This and all other product datasheets are available for download.)
26
Enter data for the vSAN managing vCenter
Since RCCMD must coordinate with the vCenter over the entire process, the access data for the vCenter, which manages the
vSAN, is mandatory.
At this configuration dialog, do not enter credentials for individual host.
Define the vSAN managing RCCMD client:
RCCMD has the task of shutting down all virtual machines and turning off the hosts at the end. Since within a vCenter not only a
vSAN but further hosts can be mapped, RCCMD can shut them down, too.There are two exceptions that need more attention:
Information about the virtual machine running RCCMD
Although RCCMD itself cannot run in the vSAN that should be shut down, the vCenter that manages
the vSAN may include additional hosts in its list. The RCCMD appliance is a virtual machine that must
comply with the control commands of the host on which it is running itself - if the host advices a
shutdown, the appliance will do it. To prevent RCCMD from inadvertently giving itself a shutdown
command, enter the name of the virtual machine you chose for RCCMD. When entered, the virtual
machine that holds this name will be excluded from the shutdown process.
Define the virtual machine that contains the vSAN managing vCenter
Within the vSAN system, the vCenter performs special administrative tasks, but is also a virtual machine. During the shutdown,
RCCMD first gets an overview of active virtual machines and then shuts them down, migrates them, etc. With this setting,
RCCMD will know which of the virtual machines is the vCenter and will shut down it exclusively as the last machine in the vSAN
shutdown procedure.
To Next Page
Loading...
