Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

Adding a Node to a Resource Group

The procedure to follow to add a node to a resource group depends on whether the resource group is a scalable resource group or a failover resource group. For detailed instructions, see the following sections:

You must supply the following information to complete the procedure.

  • The names and node IDs of all of the cluster nodes

  • The names of the resource groups to which you are adding the node

  • The name of the PNM object that is to host the network resources that are used by the resource group on all of the nodes

Also, be sure to verify that the new node is already a cluster member.

How to Add a Node to a Scalable Resource Group

  1. For each network resource that a scalable resource in the resource group uses, make the resource group where the network resource is located run on the new node.

    See Step 1 through Step 5 in the following procedure for details.

  2. Add the new node to the list of nodes that can master the scalable resource group (the nodelist resource group property).

    This step overwrites the previous value of nodelist, and therefore you must include all of the nodes that can master the resource group here.

    # clresourcegroup set [-n nodelist] resource-group
    –n nodelist

    Specifies a comma-separated, ordered list of nodes that can master this resource group. This resource group is switched offline on all of the other nodes.

    This list is optional. If you omit this list, the Nodelist property is set to all nodes in the cluster.

    resource-group

    Specifies the name of the resource group to which the node is being added.

  3. (Optional) Update the scalable resource's Load_balancing_weights property to assign a weight to the node that you are adding to the resource group.

    Otherwise, the weight defaults to 1. See the clresourcegroup(8CL) man page for more information.

How to Add a Node to a Failover Resource Group

  1. Display the current node list and the current list of PNM objects that are configured for each resource in the resource group.
    # clresourcegroup show -v resource-group | grep -i nodelist
    # clresourcegroup show -v resource-group | grep -i netiflist

    Note -  The output of the command line for nodelist and netiflist identifies the nodes by node name. To identify node IDs, run the command clnode show -v | grep -i node-id.
  2. Update netiflist for the network resources that the node addition affects.

    This step overwrites the previous value of netiflist, and therefore you must include all the PNM objects here.

    # clresource set-p netiflist=netiflist network-resource
    –p netiflist=netiflist

    Specifies a comma-separated list that identifies the PNM objects that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as a PNM object name, such as sc_ipmp0. The node can be identified by the node name or node ID, such as sc_ipmp0@1 or sc_ipmp@phys-schost-1.

    network-resource

    Specifies the name of the network resource (logical hostname or shared address) that is being hosted on the netiflist entries.

  3. If the HAStoragePlus AffinityOn extension property equals True, add the node to the appropriate Solaris Volume Manager disk set.
    # metaset -s disk-set -a -h node-name
    –s disk-set

    Specifies the name of the disk set on which the metaset command is to work

    –a

    Adds a drive or host to the specified disk set

    –h node-name

    Specifies the node to be added to the disk set

  4. Update the node list to include all of the nodes that can now master this resource group.

    This step overwrites the previous value of nodelist, and therefore you must include all of the nodes that can master the resource group here.

    # clresourcegroup set [-n nodelist] resource-group
    –n nodelist

    Specifies a comma-separated, ordered list of nodes that can master this resource group. This resource group is switched offline on all the other nodes.

    This list is optional. If you omit this list, the Nodelist property is set to all nodes in the cluster.

    resource-group

    Specifies the name of the resource group to which the node is being added.

  5. Verify the updated information.
    # clresourcegroup show -v resource-group | grep -i nodelist
    # clresourcegroup show -v resource-group | grep -i netiflist
Example 34  Adding a Node to a Resource Group

This example shows how to add a cluster node, phys-schost-2, the to the resource group resource-group-1 that contains the logical hostname resource schost-2.

# clresourcegroup show -v resource-group-1 | grep -i nodelist
Nodelist:phys-schost-1 phys-schost-3
# clresourcegroup show -v resource-group-1 | grep -i netiflist
Res property name: NetIfList
Res property class: extension
List of IPMP
interfaces on each node
Res property type: stringarray
Res property value: sc_ipmp0@1 sc_ipmp0@3

Only nodes 1 and 3 have been assigned IPMP groups. You must add an IPMP group for node 2.

# clresource set-p netiflist=sc_ipmp0@1,sc_ipmp0@2,sc_ipmp0@3 schost-2


# metaset -s red -a -h phys-schost-2
# clresourcegroup set -nphys-schost-1,phys-schost-2,phys-schost-3 resource-group-1
# clresourcegroup show -v resource-group-1 | grep -i nodelist
Nodelist: phys-schost-1phys-schost-2phys-schost-3
# clresourcegroup show -v resource-group-1 | grep -i netiflist
Res property value: sc_ipmp0@1 sc_ipmp0@2 sc_ipmp0@3