On the Solaris 10 OS, a zone cluster is a cluster of non-global zones. All nodes of a zone cluster are configured as non-global zones of the cluster brand. No other brand type is permitted in a zone cluster. You can run supported services on the zone cluster similar to a global cluster, with the isolation that is provided by Solaris zones.
Consider the following points when you plan the creation of a zone cluster.
Global cluster – The zone cluster must be configured on a global Sun Cluster configuration. A zone cluster cannot be configured without an underlying global cluster.
Minimum Solaris OS – The global cluster must run at least the Solaris 10 5/08 OS.
Cluster mode – The global-cluster voting node from which you create or modify a zone cluster must be in cluster mode. If any other voting nodes are in noncluster mode when you administer a zone cluster, the changes that you make are propagated to those nodes when they return to cluster mode.
Adequate private -IP addresses – The private IP-address range of the global cluster must have enough free IP-address subnets for use by the new zone cluster. If the number of available subnets is insufficient, the creation of the zone cluster fails.
Changes to the private IP-address range – The private IP subnets and the corresponding private IP-addresses that are available for zone clusters are automatically updated if the global cluster's private IP-address range is changed. If a zone cluster is deleted, the cluster infrastructure frees the private IP-addresses that were used by that zone cluster, making the addresses available for other use within the global cluster and by any other zone clusters that depend on the global cluster.
Supported devices – Devices that are supported with Solaris zones can be exported to a zone cluster. Such devices include the following:
Solaris disk devices (cNtXdYsZ)
DID devices (/dev/did/*dsk/dN)
Solaris Volume Manager and Solaris Volume Manager for Sun Cluster multi-owner disk sets (/dev/md/setname/*dsk/dN)
Distribution of nodes – You cannot host multiple nodes of the same zone cluster on the same node of the global cluster. A global-cluster node can host multiple zone-cluster nodes as long as each node is a member of a different zone cluster.
Node creation – You must create at least one zone-cluster node at the time that you create the zone cluster. The names of the nodes must be unique within the zone cluster. The infrastructure automatically creates an underlying non-global zone on each global-cluster node that hosts the zone cluster. Each non-global zone is given the same zone name, which is derived from, and identical to, the name that you assign to the zone cluster when you create the cluster. For example, if you create a zone cluster that is named zc1, the corresponding non-global zone name on each global-cluster node that hosts the zone cluster is also zc1.
Cluster name – The name of the zone cluster must be unique throughout the global cluster. The name cannot also be used by a non-global zone elsewhere in the global cluster, nor can the name be the same as that of a global-cluster node. You cannot use “all” or “global” as a zone-cluster name, because these are reserved names.
Public-network IP addresses – You assign a specific public-network IP address to each zone-cluster node.
Private hostnames – During creation of the zone cluster, a private hostname is automatically created for each node of the zone cluster, in the same way that hostnames are created in global clusters. Currently, you cannot rename the private hostname of a zone-cluster node. For more information about private hostnames, see Private Hostnames.
Conversion to a zone-cluster node – You cannot add an existing non-global zone to a zone cluster.
File systems – You can use the clzonecluster command to add the following types of file systems for use by a zone cluster. You configure an HAStoragePlus resource to manage the mounting of the file system:
Local file systems
QFS shared file systems, only when used to support Oracle Real Application Clusters
ZFS storage pools
To add a local file system that is not managed by an HAStoragePlus resource to a zone cluster, you instead use the zonecfg command as you normally would in a stand-alone system.
No fencing support for NAS devices in non-global zones – Sun Cluster software does not provide fencing support for NFS-exported file systems from a NAS device when such file systems are used in a non-global zone, including nodes of a zone cluster. Fencing support is provided only for NFS-exported file systems in the global zone.