This section provides procedures on how to use the clsetup utility to create a zone cluster, and add a network address, file system, ZFS storage pool, and storage device to the new zone cluster.
If any node is in noncluster mode, changes that you make are propagated when the node returns to cluster mode. Therefore, you can create a zone cluster even if some global-cluster nodes are in noncluster mode. When those nodes return to cluster mode, the system performs zone-cluster creation tasks on those nodes.
You can alternatively use the clzonecluster utility to create and configure a cluster. See the clzonecluster (1CL) man page for more information.
This section contains the following procedures:
This procedure prepares the global cluster to use the Trusted Extensions feature of Oracle Solaris with zone clusters. If you do not plan to enable Trusted Extensions, proceed to Creating a Zone Cluster.
Perform this procedure on each node in the global cluster.
Before You Begin
Perform the following tasks:
Ensure that the Oracle Solaris OS is installed to support Oracle Solaris Cluster and Trusted Extensions software. See How to Install Oracle Solaris Software for more information about installing Oracle Solaris software to meet Oracle Solaris Cluster software requirements.
If an external name service is used, ensure that an LDAP naming service is configured for use by Trusted Extensions. See Chapter 5, Configuring LDAP for Trusted Extensions, in Trusted Extensions Configuration and Administration
Review requirements and guidelines for Trusted Extensions in a zone cluster. See Guidelines for Trusted Extensions in a Zone Cluster.
Follow procedures in Chapter 3, Adding the Trusted Extensions Feature to Oracle Solaris, in Trusted Extensions Configuration and Administration .
The Trusted Extensions zoneshare and zoneunshare scripts support the ability to export home directories on the system. An Oracle Solaris Cluster configuration does not support this feature.
Disable this feature by replacing each script with a symbolic link to the /bin/true utility.
phys-schost# ln -s /usr/lib/zones/zoneshare /bin/true phys-schost# ln -s /usr/lib/zones/zoneunshare /bin/true
phys-schost# svcadm enable rlogin
Modify the account management entries by appending a Tab and typing allow_remote or allow_unlabeled respectively, as shown below.
other account requisite pam_roles.so.1Tab allow_remote other account required pam_unix_account.so.1Tab allow_unlabeled
# tncfg -t admin_low tncfg:admin_low> add host=ip-address1 tncfg:admin_low> add host=ip-address2 … tncfg:admin_low> exit
# tncfg -t admin_low remove host=0.0.0.0
# tncfg -t cipso tncfg:cipso> add host=ip-address1 tncfg:cipso> add host=ip-address2 … tncfg:cipso> exit
When all steps are completed on all global-cluster nodes, perform the remaining steps of this procedure on each node of the global cluster.
The LDAP server is used by the global zone and by the nodes of the zone cluster.
Next Steps
Create the zone cluster. Go to Creating a Zone Cluster.
Perform this procedure to create a zone cluster using the clsetup utility.
To modify the zone cluster after it is installed, see Performing Zone Cluster Administrative Tasks in Oracle Solaris Cluster System Administration Guide and the clzonecluster (1CL) man page.
Before You Begin
Create a global cluster. See Chapter 3, Establishing the Global Cluster.
Read the guidelines and requirements for creating a zone cluster. See Zone Clusters.
If the zone cluster will use Trusted Extensions, ensure that you have installed, configured, and enabled Trusted Extensions as described in How to Install and Configure Trusted Extensions.
If the cluster does not have sufficient subnets available to add a zone cluster, you must modify the private IP address range to provide the needed subnets. For more information, see How to Change the Private Network Address or Address Range of an Existing Cluster in Oracle Solaris Cluster System Administration Guide .
Have available the following information:
The unique name to assign to the zone cluster.
The zone path that the nodes of the zone cluster will use. For more information, see the description of the zonepath property in Resource Types and Properties in Introduction to Oracle Solaris Zones . By default, whole-root zones are created.
The name of each node in the global cluster on which to create a zone-cluster node.
The zone public hostname, or host alias, that you assign to each zone-cluster node.
If applicable, the public-network IP address that each zone-cluster node uses. Specifying an IP address and NIC for each zone cluster node is required if the zone cluster will be used in a Geographic Edition configuration. Otherwise, this requirement is optional. For more information about this Geographic Edition requirement, see Geographic Edition.
If applicable, the name of the public-network IPMP group that each zone-cluster node uses to connect to the public network.
That specific zone cluster will not be able to configure NAS devices for use in the zone cluster. The cluster uses the IP address of the zone cluster node when communicating with the NAS device, so not having an IP address prevents cluster support for fencing NAS devices.
The cluster software will activate any Logical Host IP address on any NIC.
You can also use the Oracle Solaris Cluster Manager GUI to create a zone cluster. For GUI log-in instructions, see How to Access Oracle Solaris Cluster Manager in Oracle Solaris Cluster System Administration Guide .
You perform all steps of this procedure from a node of the global cluster.
phys-schost# clnode status === Cluster Nodes === --- Node Status --- Node Name Status --------- ------ phys-schost-2 Online phys-schost-1 Online
phys-schost# clsetup
The Main Menu is displayed.
A zone cluster name can contain ASCII letters (a-z and A-Z), numbers, a dash, or an underscore. The maximum length of the name is 20 characters.
You can set the following properties:
|
A root account password is required for a solaris10 brand zone.
You can set the following properties:
|
You can set the following properties:
|
You can set the following properties:
|
You can also use the Oracle Solaris Cluster Manager GUI to view the capped-cpu memory configuration of a zone cluster, as well as the dedicated-CPU configuration. For GUI log-in instructions, see How to Access Oracle Solaris Cluster Manager in Oracle Solaris Cluster System Administration Guide .
You can select one or all of the available physical nodes (or hosts), and then configure one zone-cluster node at a time.
You can set the following properties:
|
The network addresses can be used to configure a logical hostname or shared IP cluster resources in the zone cluster. The network address is in the zone cluster global scope.
The results of your configuration change are displayed, similar to the following:
>>> Result of the Creation for the Zone Cluster(sczone) <<< The zone cluster is being created with the following configuration /usr/cluster/bin/clzonecluster configure sczone create set brand=solaris set zonepath=/zones/sczone set ip-type=shared set enable_priv_net=true add capped-memory set physical=2G end add node set physical-host=phys-schost-1 set hostname=zc-host-1 add net set address=172.1.1.1 set physical=net0 end end add net set address=172.1.1.2 end Zone cluster, zc2 has been created and configured successfully. Continue to install the zone cluster(yes/no) ?
The clsetup utility performs a standard installation of a zone cluster and you cannot specify any options.
The verify subcommand checks for the availability of the specified resources. If the clzonecluster verify command succeeds, no output is displayed.
phys-schost-1# clzonecluster verify zone-cluster-name
phys-schost-1# clzonecluster status zone-cluster-name
=== Zone Clusters ===
--- Zone Cluster Status ---
Name Node Name Zone HostName Status Zone Status
---- --------- ------------- ------ -----------
zone basenode1 zone-1 Offline Configured
basenode2 zone-2 Offline Configured
From the global zone, launch the txzonemgr GUI.
phys-schost# txzonemgr
Select the global zone, then select the item, Configure per-zone name service.
phys-schost-1# clzonecluster install options zone-cluster-name Waiting for zone install commands to complete on all the nodes of the zone cluster "zone-cluster-name"...
|
Use either the –a or –d option to install Geographic Edition software, core packages, and agents that are supported in the zone cluster. Also, you can use the –d and –p options in the same command.
|
For more information, see the clzonecluster (1CL) man page.
Otherwise, skip to Step 26.
Configure only one zone-cluster node at a time.
phys-schost# zoneadm -z zcnode boot
phys-schost# zlogin zcnode zcnode# sysconfig unconfigure zcnode# reboot
The zlogin session terminates during the reboot.
phys-schost# zlogin -C zcnode
For information about methods to exit from a non-global zone, see How to Exit a Non-Global Zone in Creating and Using Oracle Solaris Zones .
phys-schost# zoneadm -z zcnode halt
phys-schost# clzonecluster boot zone-cluster-name
phys-schost# zlogin zcnode zcnode# sysconfig unconfigure zcnode# reboot
The zlogin session terminates during the reboot.
phys-schost# zlogin -C zcnode
For information about methods to exit from a non-global zone, see How to Exit a Non-Global Zone in Creating and Using Oracle Solaris Zones .
phys-schost# clzonecluster boot zone-cluster-name
phys-schost# zlogin -C zcnode
For information about methods to exit from a non-global zone, see How to Exit a Non-Global Zone in Creating and Using Oracle Solaris Zones .
Installation of the zone cluster might take several minutes.
phys-schost# clzonecluster boot zone-cluster-name
The clsetup utility does not automatically configure IPMP groups for exclusive-IP zone clusters. You must create an IPMP group manually before you create a logical-hostname or shared-address resource.
phys-schost# ipadm create-ipmp -i interface sc_ipmp0 phys-schost# ipadm delete-addr interface/name phys-schost# ipadm create-addr -T static -a IPaddress/prefix sc_ipmp0/name
Next Steps
To configure Oracle Solaris Cluster 3.3 data services that you installed in a solaris10 brand zone cluster, follow procedures for zone clusters in the applicable data-service manual. See Oracle Solaris Cluster 3.3 Documentation.
To complete Trusted Extensions configuration, go to How to Configure a Zone Cluster to Use Trusted Extensions.
Otherwise, add file systems or storage devices to the zone cluster. See the following sections:
After you create a labeled brand zone cluster, perform the following steps to finish configuration to use Trusted Extensions.
Perform this step on each node of the zone cluster.
phys-schost# cat /etc/cluster/nodeid N
Ensure that the SMF service has been imported and all services are up before you log in.
The cluster software automatically assigns these IP addresses when the cluster software configures a zone cluster.
In the ifconfig -a output, locate the clprivnet0 logical interface that belongs to the zone cluster. The value for inetis the IP address that was assigned to support the use of the cluster private interconnect by this zone cluster.
zc1# ifconfig -a lo0:3: flags=20010008c9<UP,LOOPBACK,RUNNING,NOARP,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 zone zc1 inet 127.0.0.1 netmask ff000000 net0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.11.166.105 netmask ffffff00 broadcast 10.11.166.255 groupname sc_ipmp0 ether 0:3:ba:19:fa:b7 ce0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4 inet 10.11.166.109 netmask ffffff00 broadcast 10.11.166.255 groupname sc_ipmp0 ether 0:14:4f:24:74:d8 ce0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 zone zc1 inet 10.11.166.160 netmask ffffff00 broadcast 10.11.166.255 clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1500 index 7 inet 172.16.0.18 netmask fffffff8 broadcast 172.16.0.23 ether 0:0:0:0:0:2 clprivnet0:3: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1500 index 7 zone zc1 inet 172.16.0.22 netmask fffffffc broadcast 172.16.0.23
The hostname for the private interconnect, which is clusternodeN-priv, where N is the global-cluster node ID
172.16.0.22 clusternodeN-priv
Each net resource that was specified to the clzonecluster command when you created the zone cluster
Create new entries for the IP addresses used by zone-cluster components and assign each entry a CIPSO template. These IP addresses which exist in the zone-cluster node's /etc/inet/hosts file are as follows:
Each zone-cluster node private IP address
All cl_privnet IP addresses in the zone cluster
Each logical-hostname public IP address for the zone cluster
Each shared-address public IP address for the zone cluster
phys-schost# tncfg -t cipso tncfg:cipso> add host=ipaddress1 tncfg:cipso> add host=ipaddress2 … tncfg:cipso> exit
For more information about CIPSO templates, see How to Configure a Different Domain of Interpretation in Trusted Extensions Configuration and Administration .
Perform the following commands on each node of the zone cluster.
phys-schost# ipadm set-prop -p hostmodel=weak ipv4 phys-schost# ipadm set-prop -p hostmodel=weak ipv6
For more information about the hostmodel property, see hostmodel (ipv4 or ipv6) in Oracle Solaris 11.2 Tunable Parameters Reference Manual .
Next Steps
To add file systems or storage devices to the zone cluster. See the following sections:
See also
If you want to update the software on a zone cluster, follow procedures in Chapter 11, Updating Your Software, in Oracle Solaris Cluster System Administration Guide . These procedures include special instructions for zone clusters, where needed.