|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 3.3 3/13|
This section describes how to add a node to a global cluster or a zone cluster. You can create a new zone-cluster node on a node of the global cluster that hosts the zone cluster, as long as that global-cluster node does not already host a node of that particular zone cluster. You cannot convert an existing non-voting node on a global cluster into a zone-cluster node.
Specifying an IP address and NIC for each zone cluster node is optional.
Note - If you do not configure an IP address for each zone cluster node, two things will occur:
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.
If the original zone cluster node did not have a IP address or NIC specified, then you do not need to specify that information for the new zone cluster node.
In this chapter, phys-schost# reflects a global-cluster prompt. The clzonecluster interactive shell prompt is clzc:schost>.
The following table lists the tasks to perform to add a node to an existing cluster. Perform the tasks in the order shown.
Table 8-1 Task Map: Adding a Node to an Existing Global or Zone Cluster
Before adding an Oracle Solaris host or a virtual machine to an existing global cluster or a zone cluster, ensure that the node has all of the necessary hardware correctly installed and configured, including an operational physical connection to the private cluster interconnect.
For hardware installation information, refer to the Oracle Solaris Cluster 3.3 3/13 Hardware Administration Manual or the hardware documentation that shipped with your server.
This procedure enables a machine to install itself into a cluster by adding its node name to the list of authorized nodes for that cluster.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
clzc:sczone>add node clzc:sczone:node>set physical-host=phys-cluster-1 clzc:sczone:node>set hostname=hostname1 clzc:sczone:node>add net clzc:sczone:node:net>set address=hostname1 clzc:sczone:node:net>set physical=bge0 clzc:sczone:node:net>end clzc:sczone:node>end clzc:sczone>add node clzc:sczone:node>set physical-host=phys-cluster-2 clzc:sczone:node>set hostname=hostname2 clzc:sczone:node>add net clzc:sczone:node:net>set address=hostname2 clzc:sczone:node:net>set physical=bge0 clzc:sczone:node:net>end clzc:sczone:node>end
# clzc install zone-clustername
For detailed instructions on configuring the zone-cluster node, see Configuring a Zone Cluster in Oracle Solaris Cluster Software Installation Guide.
Follow the clsetup prompts. This option tells the cluster to ignore all requests over the public network from any new machine that is trying to add itself to the cluster. When finished, quit the clsetup utility.
Example 8-1 Adding a Global-Cluster Node to the Authorized Node List
The following example shows how to add a node named phys-schost-3 to the authorized node list in an existing cluster.
[Become superuser and execute the clsetup utility.] phys-schost# clsetup [Select New nodes>Specify the name of a machine which may add itself.] [Answer the questions when prompted.] [Verify that the command completed successfully.] claccess allow -h phys-schost-3 Command completed successfully. [Select Prevent any new machines from being added to the cluster.] [Quit the clsetup New Nodes Menu and Main Menu.] [Install the cluster software.]
For a complete list of tasks for adding a cluster node, see Table 8-1, “Task Map: Adding a Cluster Node.”
To add a node to an existing resource group, see the Oracle Solaris Cluster Data Services Planning and Administration Guide.
This section provides the following information and procedures to create a non-voting node, simply referred to as a zone, on a global-cluster node.
You must be working in the global zone.
If services are not yet online for a node, wait until the state changes to online before you proceed to the next step.
phys-schost# svcs multi-user-server node STATE STIME FMRI online 17:52:55 svc:/milestone/multi-user-server:default
Follow procedures in the Oracle Solaris documentation:
phys-schost# zoneadm list -v ID NAME STATUS PATH 0 global running / 1 my-zone ready /zone-path
The following command chooses and assigns an available IP address from the cluster's private IP-address range. The command also assigns the specified private hostname, or host alias, to the zone and maps it to the assigned private IP address.
phys-schost# clnode set -p zprivatehostname=hostalias node:zone
Specifies a property.
Specifies the zone private hostname, or host alias.
The name of the node.
The name of the global-cluster non-voting node.
Follow the procedures in Performing the Initial Internal Zone Configuration in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones. Choose either of the following methods:
Log in to the zone.
Use an /etc/sysidcfg file.
These changes enable the zone to resolve searches for cluster-specific hostnames and IP addresses.
phys-schost# zlogin -c zonename
sczone# vi /etc/nsswitch.conf
The modified entries should appear similar to the following:
… hosts: cluster files nis [NOTFOUND=return] … netmasks: cluster files nis [NOTFOUND=return] …
You must configure an IPMP group for each public-network adapter that is used for data-service traffic in the zone. This information is not inherited from the global zone. See Public Networks in Oracle Solaris Cluster Software Installation Guide for more information about configuring IPMP groups in a cluster.