Perform this procedure to configure a new global-cluster node by using an XML cluster configuration file. The new node can be a duplication of an existing cluster node that runs the Oracle Solaris Cluster 4.4 software.
This procedure configures the following cluster components on the new node:
Cluster node membership
Before You Begin
Perform the following tasks:
Ensure that the Oracle Solaris OS is installed to support the Oracle Solaris Cluster software.
If the Oracle Solaris software is already installed on the node, you must ensure that the Oracle Solaris installation meets the requirements for the Oracle Solaris Cluster software and any other software that you intend to install on the cluster. See How to Install Oracle Solaris Software for more information about installing the Oracle Solaris software to meet Oracle Solaris Cluster software requirements.
SPARC: If you are configuring Oracle VM Server for SPARC I/O domains or guest domains as cluster nodes, ensure that the Oracle VM Server for SPARC software is installed on each physical machine and that the domains meet Oracle Solaris Cluster requirements. See How to Install Oracle VM Server for SPARC Software and Create Domains.
Ensure that Oracle Solaris Cluster software packages and any necessary updates are installed on the node. See How to Install Oracle Solaris Cluster Software (pkg).
Ensure that the cluster is prepared for the addition of the new node. See How to Prepare the Cluster for Additional Global-Cluster Nodes.
phys-schost-new# /usr/sbin/clinfo -n
The Oracle Solaris Cluster software is not yet configured on the node. You can add the potential node to the cluster.
Before you can add the node to a different cluster, you must remove the existing cluster configuration information.
ok boot -x
For more information about GRUB based booting, see About Run Level Booting in Booting and Shutting Down Oracle Solaris 11.4 Systems.
The screen displays the edited command.
phys-schost-new# /usr/cluster/bin/clnode remove
phys-schost# clnode export -o clconfigfile
Specifies the output destination.
The name of the cluster configuration XML file. The specified file name can be an existing file or a new file that the command will create.
For more information, see the clnode(8CL) man page.
The Oracle Solaris TCP wrappers for RPC feature prevents internode communication that is necessary for cluster configuration.
TCP wrappers are enabled if config/enable_tcpwrappers is set to true, as shown in the following example command output.
# svccfg -s rpc/bind listprop config/enable_tcpwrappers config/enable_tcpwrappers boolean true
# svccfg -s rpc/bind setprop config/enable_tcpwrappers = false # svcadm restart rpc/bind
If you are duplicating an existing cluster node, open the file that you created with the clnode export command.
If you are not duplicating an existing cluster node, create a new file.
Base the file on the element hierarchy that is shown in the clconfiguration(7CL) man page. You can store the file in any directory.
Modify the values of the XML elements to reflect the node configuration that you want to create.
See the clconfiguration(7CL) man page for details about the structure and content of the cluster configuration XML file.
phys-schost-new# xmllint --valid --noout clconfigfile
phys-schost-new# clnode add -n sponsor-node -i clconfigfile
Specifies the name of an existing cluster member to act as the sponsor for the new node.
Specifies the name of the cluster configuration XML file to use as the input source.
Without this addition to the /etc/hosts.allow file, TCP wrappers prevent internode communication over RPC for cluster administration utilities.
# /usr/sbin/ipadm show-addr ADDROBJ TYPE STATE ADDR clprivnet0/N static ok ip-address/netmask-length …
phys-schost# clnode set -p reboot_on_path_failure=enabled +
Specifies the property to set
Enables automatic node reboot if failure of all monitored shared-disk paths occurs.
phys-schost# clnode show === Cluster Nodes === Node Name: node … reboot_on_path_failure: enabled …
Unsuccessful configuration – If one or more nodes cannot join the cluster, or if the wrong configuration information was specified, first attempt to perform this procedure again. If that does not correct the problem, perform the procedure How to Unconfigure Oracle Solaris Cluster Software to Correct Installation Problems on each misconfigured node to remove it from the cluster configuration. You do not need to uninstall the Oracle Solaris Cluster software packages. Then perform this procedure again.
If you added a node to a cluster that uses a quorum device, go to How to Update Quorum Devices After Adding a Node to a Global Cluster.
Otherwise, go to How to Verify the Quorum Configuration and Installation Mode.