For basic operational procedures, follow "Chapter 7 Operations," but in some cases special procedures and considerations are necessary. This section describes those sorts of special procedures and considerations.
Starting Up and Stopping the Non-Global Zone
When starting up or stopping the cluster applications with the PRIMECLUSTER on the global zone, the non-global zone and the applications running on it will start or stop accordingly. The startup and stop procedures do not change from the normal PRIMECLUSTER operations. For details, refer to "7.2 Operating the PRIMECLUSTER System."
When one performs a stop to the cluster applications, if using warm-standby, the RMS will stop with the non-global zone still started up. If using cold-standby, the non-global zones will enter a detached status in all nodes.
Points of Caution
During system operation, the RMS and cluster applications on the non-global zone are monitored from the global zone. Because of this, do not perform operations of the PRIMECLUSTER on the non-global zone besides those methods which follow this manual.
When performing maintenance for the non-global zone, use the global zone maintenance mode. (For details, refer to "13.5 Maintenance").
When you make the addition of cluster applications and configuration changes on the global-zone, such as adding non-global zones, stop the RMS and all non-global zones.
If sharing non-global zone images
Things such as software, parameters, and files are stored to the volume for the non-global zone's root file system. Because of this, if these files are destroyed, the failover may fail.
Since the various types of logs on the non-global zone are stored to the volume for the non-global zone's root file system, they are output to the same log files on the operational system and standby system.
