Top
PRIMECLUSTER  Installation and Administration Guide4.3

G.4.2 During Operation

Controlling Guest Domains

Never use the ldm(1M) command immediately to start or stop a guest domain or to bind its resources.
Guest domains have to be started and stopped from PRIMECLUSTER.
Otherwise, you risk loss or damage of data.

Stopping the System While Guest Domains Are Operational

When Control Domain Is Stopped

Sometimes, guest domains on a forcibly stopped node, which have been monitored by the cluster system, are not stopped although the control domain has been forced to stop. This may possibly cause data loss when restoring the control domain while any of the guest domains are not stopped.
In order to stop absolutely all input and output from guest domains, please make sure to interrupt the electrical power in the server rack by either of the following methods before restoring the stopped control domain. After that, reboot the disconnected nodes. Also note that no kernel crash dump is collected for operating systems in guest domains.

See

For details on the remote control, please refer to the "Integrated Lights Out Manager User's Guide".

Manual Switching of Cluster Applications

When guest domains are switched to a standby system, PRIMECLUSTER uses the ldm(1M) command to stop those guest domains.
Therefore, whenever PRIMECLUSTER suspends a guest domain, the OS and all applications in that guest domain stop abruptly.
In order to avoid such abrupt stops when switching cluster applications manually, log in to the guest domain OS and stop the OS by running the shutdown(1M) or a similar command before switching the cluster application.

Shutting Down the Control Domains

Before shutting down a control domain, stop RMS on the control domain to set Cmdline resources which control guest domains offline. For how to stop RMS, refer to "7.2.1.2 Stopping RMS".