Sun Cluster System Administration Guide for Solaris OS

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.

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

Task 

Instructions 

Install the host adapter on the node and verify that the existing cluster interconnects can support the new node 

Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS

Add shared storage 

Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS

Prepare the cluster for additional nodes 

How to Prepare the Cluster for Additional Global-Cluster Nodes in Sun Cluster Software Installation Guide for Solaris OS

Add the node to the authorized node list by using clsetup

How to Add a Node to the Authorized Node List

Install and configure the software on the new cluster node 

Chapter 2, Installing Software on Global-Cluster Nodes, in Sun Cluster Software Installation Guide for Solaris OS

If the cluster is configured in a Sun Cluster Geographic Edition partnership, configure the new node as an active participant in the configuration 

How to Add a New Node to a Cluster in a Partnership in Sun Cluster Geographic Edition System Administration Guide

ProcedureHow to Add a Node to the Authorized Node List

Before adding a 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 Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS 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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.

  1. On a current global-cluster member, become superuser on the current cluster member. Perform these steps from a node of a global cluster.

  2. Ensure that you have correctly completed all prerequisite hardware installation and configuration tasks that are listed in the task map for Table 8–1.

  3. Start the clsetup utility.


    phys-schost# clsetup
    

    The Main Menu is displayed.


    Note –

    To add a node to a zone cluster, use the clzonecluster utility. See Step 9 for instructions to manually add a zone to a zone cluster.


  4. Type the number that corresponds to the option for displaying the New Nodes Menu and press the Return key.

  5. Type the number that corresponds to the option to modify the authorized list and press the Return key. Specify the name of a machine that can add itself.

    Follow the prompts to add the node's name to the cluster. You are asked for the name of the node to be added.

  6. Verify that the task has been performed successfully.

    The clsetup utility prints a “Command completed successfully” message if it completes the task without error.

  7. To prevent any new machines from being added to the cluster, type the number that corresponds to option to instruct the cluster to ignore requests to add new machines. Press the Return key.

    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.

  8. Quit the clsetup utility.

  9. To manually add a node to a zone cluster, you must specify the 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: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
    

    For detailed instructions on configuring the node, see Configuring a Zone Cluster in Sun Cluster Software Installation Guide for Solaris OS.

  10. Install and configure the software on the new cluster node.

    Use either scinstall or JumpStartTM software to complete the installation and configuration of the new node, as described in the Sun Cluster Software Installation Guide for Solaris OS.


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 scconf 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

clsetup(1CL)

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 Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

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.

ProcedureHow 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. For the Solaris 10 OS, 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 Solaris documentation:

    1. Perform procedures in Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

    2. Perform procedures in Installing and Booting Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

    3. Perform procedures in How to Boot a Zone in System Administration Guide: Solaris Containers-Resource Management and 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. For a whole-root zone with the ip-type property set to exclusive: If the zone might host a logical-hostname resource, configure a file system resource that mounts the method directory from the global zone.


    phys-schost# zonecfg -z sczone
    zonecfg:sczone> add fs
    zonecfg:sczone:fs> set dir=/usr/cluster/lib/rgm
    zonecfg:sczone:fs> set special=/usr/cluster/lib/rgm
    zonecfg:sczone:fs> set type=lofs
    zonecfg:sczone:fs> end
    zonecfg:sczone> exit
    
  6. (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
    
    -p

    Specifies a property.

    zprivatehostname=hostalias

    Specifies the zone private hostname, or host alias.

    node

    The name of the node.

    zone

    The name of the global-cluster non-voting node.

  7. Perform the initial internal zone configuration.

    Follow the procedures in Performing the Initial Internal Zone Configuration in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones. Choose either of the following methods:

    • Log in to the zone.

    • Use an /etc/sysidcfg file.

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

  9. 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 Sun Cluster Software Installation Guide for Solaris OS for more information about configuring IPMP groups in a cluster.

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