Adding or Removing a Node to or From a Resource Group

The procedures in this section enable you to perform the following tasks.

• Configuring a cluster node or zone to be an additional master of a resource group

• Removing a node or zone from a resource group

The procedures are slightly different, depending on whether you plan to add or remove the node or zone to or from a failover or scalable resource group.

Failover resource groups contain network resources that both failover and scalable services use. Each IP subnetwork connected to the cluster has its own network resource that is specified and included in a failover resource group. The network resource is either a logical hostname or a shared address resource. Each network resource includes a list of IP Networking Multipathing groups that it uses. For failover resource groups, you must update the complete list of IP Networking Multipathing groups for each network resource that the resource group includes (the netiflist resource property).

The procedure for scalable resource groups involves the following steps:

1. Repeating the procedure for failover groups that contain the network resources that the scalable resource uses

2. Changing the scalable group to be mastered on the new set of hosts

For more information, see the clresourcegroup(1CL) man page.

Run either procedure from any cluster node.

Adding a Node to a Resource Group

The procedure to follow to add a node or zone 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:

• How to Add a Node to a Scalable Resource Group

• How to Add a Node to a Failover Resource Group

You must supply the following information to complete the procedure.

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

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

• The name of the IP Networking Multipathing group that is to host the network resources that are used by the resource group on all of the nodes or zones

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 or zone to the list of nodes or zones 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 node-zone-list] resource-group

   -n node-zone-list

   Specifies a comma-separated, ordered list of nodes or zones that can master this resource group. This resource group is switched offline on all of the other nodes. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

   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 or zone is being added.

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

   Otherwise, the weight defaults to 1. See the clresourcegroup(1CL) 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 IP Networking Multipathing groups 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 or zone addition affects.

   This step overwrites the previous value of netiflist, and therefore you must include all the IP Networking Multipathing groups here.

   # clresource set -p netiflist=netiflist network-resource

   -p netiflist=netiflist

   Specifies a comma-separated list that identifies the IP Networking Multipathing groups that are on each node or zone. Each element in netiflist must be in the form of netif@node. netif can be given as an IP Networking Multipathing group 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 disk set or device group.

   • If you are using Solstice DiskSuite or Solaris Volume Manager, use the metaset command.

     # metaset -s disk-set-name -a -h node-name

     -s disk-set-name

     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

   • SPARC: If you are using VERITAS Volume Manager, use the clsetup utility.

     1. On any active cluster member, start the clsetup utility.

        # clsetup

        The Main Menu is displayed.

     2. On the Main Menu, type the number that corresponds to the option for device groups and volumes.

     3. On the Device Groups menu, type the number that corresponds to the option for adding a node to a VxVM device group.

     4. Respond to the prompts to add the node to the VxVM device group.

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

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

   # clresourcegroup set [-n node-zone-list] resource-group

   -n node-zone-list

   Specifies a comma-separated, ordered list of zones that can master this resource group. This resource group is switched offline on all the other nodes. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

   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 or zone is being added.

5. Verify the updated information.

   # clresourcegroup show -vresource-group | grep -i nodelist # clresourcegroup show -vresource-group | grep -i netiflist

Example 2–29 Adding a Node to a Resource Group

This example shows how to add a global zone(phys-schost-2) to a resource group (resource-group-1) that contains a 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 IP Networking Multipathing
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 IP Networking Multipathing groups. 
You must add an IP Networking Multipathing 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 -n  phys-schost-1,phys-schost-2,phys-schost-3 resource-group-1
# clresourcegroup show -v resource-group-1 | grep -i nodelist
 Nodelist:     phys-schost-1 phys-schost-2
               phys-schost-3
# clresourcegroup show -v resource-group-1 | grep -i netiflist
 Res property value: sc_ipmp0@1 sc_ipmp0@2
                     sc_ipmp0@3

Removing a Node From a Resource Group

The procedure to follow to remove a node or zone from 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:

• How to Remove a Node From a Scalable Resource Group

• How to Remove a Node From a Failover Resource Group

• How to Remove a Node From a Failover Resource Group That Contains Shared Address Resources

To complete the procedure, you must supply the following information.

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

  # clnode show -v | grep -i “Node ID”

• The name of the resource group or the names of the resource groups from which you plan to remove the node or zone

  # clresourcegroup show | grep “Nodelist”

• Names of the IP Networking Multipathing groups that are to host the network resources that are used by the resource groups on all of the nodes or zones

  # clresourcegroup show -v | grep “NetIfList.*value”

Additionally, be sure to verify that the resource group is not mastered on the node or zone that you are removing. If the resource group is mastered on the node or zone that you are removing, run the clresourcegroup command to switch the resource group offline from that node or zone. The following clresourcegroup command brings the resource group offline from a given node or zone, provided that new-masters does not contain that node or zone.

# clresourcegroup switch -n new-masters resource-group

-n new-masters

Specifies the nodes or zones that is now to master the resource group.

resource-group

Specifies the name of the resource group that you are switching . This resource group is mastered on the node or zone that you are removing.

For more information, see the clresourcegroup(1CL) man page.

If you plan to remove a node or zone from all the resource groups, and you use a scalable services configuration, first remove the node or zone from the scalable resource groups. Then remove the node or zone from the failover groups.

How to Remove a Node From a Scalable Resource Group

A scalable service is configured as two resource groups, as follows.

• One resource group is a scalable group that contains the scalable service resource.

• One resource group is a failover group that contains the shared address resources that the scalable service resource uses.

Additionally, the RG_dependencies property of the scalable resource group is set to configure the scalable group with a dependency on the failover resource group. For information about this property, see Appendix B, Standard Properties.

For details about scalable service configuration, see Sun Cluster Concepts Guide for Solaris OS.

Removing a node or zone from the scalable resource group causes the scalable service to no longer be brought online on that node or zone. To remove a node or zone from the scalable resource group, perform the following steps.

1. Remove the node or zone from the list of nodes or zones that can master the scalable resource group (the nodelist resource group property).

   # clresourcegroup set [-n node-zone-list] scalable-resource-group

   -n node-zone-list

   Specifies a comma-separated, ordered list of zones that can master this resource group. This resource group is switched offline on all the other nodes. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

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

   scalable-resource-group

   Specifies the name of the resource group from which the node or zone is being removed.

2. (Optional) Remove the node or zone from the failover resource group that contains the shared address resource.

   For details, see How to Remove a Node From a Failover Resource Group That Contains Shared Address Resources.

3. (Optional) Update the Load_balancing_weights property of the scalable resource to remove the weight of the node or zone that you are removing from the resource group.

See Also

The clresourcegroup(1CL) man page.

How to Remove a Node From a Failover Resource Group

Perform the following steps to remove a node or zone from a failover resource group.

If you plan to remove a node or zone from all of the resource groups, and you use a scalable services configuration, first remove the node or zone from the scalable resource groups. Then use this procedure to remove the node or zone from the failover groups.

If the failover resource group contains shared address resources that scalable services use, see How to Remove a Node From a Failover Resource Group That Contains Shared Address Resources.

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

   This step removes the node or zone and overwrites the previous value of the node list. Be sure to include all of the nodes or zones that can master the resource group here.

   # clresourcegroup set [-n node-zone-list] failover-resource-group

   -n node-zone-list

   Specifies a comma-separated, ordered list of zones that can master this resource group. This resource group is switched offline on all the other nodes. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

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

   failover-resource-group

   Specifies the name of the resource group from which the node or zone is being removed.

2. Display the current list of IP Networking Multipathing groups that are configured for each resource in the resource group.

   # clresourcegroup show -v failover-resource-group | grep -i netiflist

3. Update netiflist for network resources that the removal of the node or zone affects.

   This step overwrites the previous value of netiflist. Be sure to include all of the IP Networking Multipathing groups here.

   # clresource set -p netiflist=netiflist network-resource

   ---

   Note –

   The output of the preceding command line identifies the nodes by node name. Run the command line clnode show -v | grep -i “Node ID” to find the node ID.

   ---

   -p netiflist=netiflist

   Specifies a comma-separated list that identifies the IP Networking Multipathing groups that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as an IP Networking Multipathing group 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 that is hosted on the netiflist entries.

   ---

   Note –

   Sun Cluster does not support the use of the adapter name for netif.

   ---

4. Verify the updated information.

   # clresourcegroup show -vfailover-resource-group | grep -i nodelist # clresourcegroup show -vfailover-resource-group | grep -i netiflist

How to Remove a Node From a Failover Resource Group That Contains Shared Address Resources

In a failover resource group that contains shared address resources that scalable services use, a node or zone can appear in the following locations.

• The node list of the failover resource group

• The auxnodelist of the shared address resource

To remove the node or zone from the node list of the failover resource group, follow the procedure How to Remove a Node From a Failover Resource Group.

To modify the auxnodelist of the shared address resource, you must remove and re-create the shared address resource.

If you remove the node or zone from the failover group's node list, you can continue to use the shared address resource on that node or zone to provide scalable services. To continue to use the shared address resource, you must add the node or zone to the auxnodelist of the shared address resource. To add the node or zone to the auxnodelist, perform the following steps.

You can also use the following procedure to remove the node or zone from the auxnodelist of the shared address resource. To remove the node or zone from the auxnodelist, you must delete and re-create the shared address resource.

1. Switch the scalable service resource offline.

2. Remove the shared address resource from the failover resource group.

3. Create the shared address resource.

   Add the node ID or node name of the node or the zone name of the zone that you removed from the failover resource group to the auxnodelist.

   # clressharedaddress create -g failover-resource-group \ -X new-auxnodelist shared-address

   failover-resource-group

   The name of the failover resource group that used to contain the shared address resource.

   new-auxnodelist

   The new, modified auxnodelist with the desired node or zone added or removed.

   shared-address

   The name of the shared address.

Example – Removing a Node From a Resource Group

This example shows how to remove a node (phys-schost-3) from a resource group (resource-group-1) that contains a logical hostname resource (schost-1).

# clresourcegroup show -v resource-group-1 | grep -i nodelist
Nodelist:       phys-schost-1 phys-schost-2
                                             phys-schost-3
# clresourcegroup set -n phys-schost-1,phys-schost-2 resource-group-1
# clresourcegroup show -v resource-group-1 | grep -i netiflist
( Res property name: NetIfList
Res property class: extension
( List of IP Networking Multipathing 
interfaces on each node
( Res property type: stringarray
 Res property value: sc_ipmp0@1 sc_ipmp0@2
                     sc_ipmp0@3

(sc_ipmp0@3 is the IP Networking Multipathing group to be removed.)

# clresource set  -p  netiflist=sc_ipmp0@1,sc_ipmp0@2 schost-1
# clresourcegroup show -v resource-group-1 | grep -i nodelist
Nodelist:       phys-schost-1 phys-schost-2
# clresourcegroup show -v resource-group-1 | grep -i netiflist
 Res property value: sc_ipmp0@1 sc_ipmp0@2