JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster System Administration Guide     Oracle Solaris Cluster 3.3 3/13
search filter icon
search icon

Document Information


1.  Introduction to Administering Oracle Solaris Cluster

2.  Oracle Solaris Cluster and RBAC

3.  Shutting Down and Booting a Cluster

4.  Data Replication Approaches

5.  Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems

6.  Administering Quorum

7.  Administering Cluster Interconnects and Public Networks

8.  Adding and Removing a Node

Adding a Node to a Cluster

How to Add a Node to an Existing Cluster

Creating a Non-Voting Node (Zone) in a Global Cluster

How to Create a Non-Voting Node in a Global Cluster

Removing a Node From a Cluster

How to Remove a Node From a Zone Cluster

How to Remove a Node From the Cluster Software Configuration

How to Remove a Non-Voting Node (Zone) From a Global Cluster

How to Remove Connectivity Between an Array and a Single Node, in a Cluster With Greater Than Two-Node Connectivity

How to Correct Error Messages

9.  Administering the Cluster

10.  Configuring Control of CPU Usage

11.  Patching Oracle Solaris Cluster Software and Firmware

12.  Backing Up and Restoring a Cluster

13.  Administering Oracle Solaris Cluster With the Graphical User Interfaces

A.  Example


Adding a Node to a Cluster

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:

  1. 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.

  2. 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

Install the host adapter on the node and verify that the existing cluster interconnects can support the new node
Add shared storage
Add the node to the authorized node list
/usr/cluster/bin/claccess allow -h node-being-added
Install and configure the software on the new cluster node
Add the new node to an existing cluster
If the cluster is configured in an Oracle Solaris Cluster Geographic Edition partnership, configure the new node as an active participant in the configuration

How to Add a Node to an Existing 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.

  1. Ensure that you have correctly completed all prerequisite hardware installation and configuration tasks that are listed in the task map for Table 8-1.
  2. Ensure that the switches, adapters, and cables were created using the scinstall utility.
  3. On the node being added, use the scinstall utility and choose menu items to add a cluster node, and follow the prompts.
  4. To manually add a node to a zone cluster, follow these additional steps:
    1. Specify the Oracle Solaris host and the virtual node name. You must also specify a network resource to be used for public network communication on each node. In the following example, the zone name is sczone, and bge0 is the public network adapter on both machines
      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>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
    2. After you configure the node, reboot the node into cluster mode and install the zone cluster on the node.

      # 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.

  5. To prevent any new machines from being added to the cluster, from the clsetup utility type the number for the option to instruct the cluster to ignore requests to add new machines.

    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.]

See Also


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.

Creating a Non-Voting Node (Zone) in a Global Cluster

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.

How to Create a Non-Voting Node in a Global Cluster

  1. Become superuser on the global-cluster node where you are creating the non-voting node.

    You must be working in the global zone.

  2. Verify on each node that multiuser services for the Service Management Facility (SMF) are online.

    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
  3. Configure, install, and boot the new zone.

    Note - You must set the autoboot property to true to support resource-group functionality in the non-voting node on the global cluster.

    Follow procedures in the Oracle Solaris documentation:

    1. Perform procedures in Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.
    2. Perform procedures in Installing and Booting Zones in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.
    3. Perform procedures in How to Boot a Zone in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.
  4. Verify that the zone is in the ready state.
    phys-schost# zoneadm list -v
    ID  NAME     STATUS       PATH
     0  global   running      /
     1  my-zone  ready        /zone-path
  5. (Optional) For a shared-IP zone, assign a private IP address and a private hostname to the zone.

    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.

  6. Perform the initial internal zone configuration.

    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.

  7. In the non-voting node, modify the nsswitch.conf file.

    These changes enable the zone to resolve searches for cluster-specific hostnames and IP addresses.

    1. Log in to the zone.
      phys-schost# zlogin -c zonename
    2. Open the /etc/nsswitch.conf file for editing.
      sczone# vi /etc/nsswitch.conf
    3. Add the cluster switch to the beginning of the lookups for the hosts and netmasks entries, followed by the files switch.

      The modified entries should appear similar to the following:

      hosts:      cluster files nis [NOTFOUND=return]
      netmasks:   cluster files nis [NOTFOUND=return]
    4. For all other entries, ensure that the files switch is the first switch that is listed in the entry.
    5. Exit the zone.
  8. If you created an exclusive-IP zone, configure IPMP groups in each /etc/hostname.interface file that is on the zone.

    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.

  9. Set up name-to-address mappings for all logical hostname resources that are used by the zone.
    1. Add name-to-address mappings to the /etc/inet/hosts file on the zone.

      This information is not inherited from the global zone.

    2. If you use a name server, add the name-to-address mappings.