Changing Resource Type, Resource Group, and Resource Properties

Sun Cluster defines standard properties for configuring resource types, resource groups, and resources. These standard properties are described in the following sections:

• Resource Type Properties

• Resource Properties

• Resource Group Properties

Resources also have extension properties, which are predefined for the data service that represents the resource. For a description of the extension properties of a data service, see the documentation for the data service.

To determine whether you can change a property, see the Tunable entry for the property in the description of the property.

The following procedures describe how to change properties for configuring resource types, resource groups, and resources.

How to Change Resource Type Properties

Perform this procedure from any cluster node.

Before You Begin

Ensure that you have the following information.

• The name of the resource type to change.

• The name of the resource type property to change. For resource types, you can change only certain properties. To determine whether you can change a property, see the Tunable entry for the property in Resource Type Properties.

  ---

  Note –

  You cannot change the Installed_nodes property explicitly. To change this property, specify the -n installed-node-list option of the clresourcetype command.

  ---

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

2. Run the clresourcetype command to determine the name of the resource type that you need for this procedure.

   # clresourcetype show -v

3. Change the resource type property.

   For resource types, you can change only certain properties. To determine whether you can change a property, see the Tunable entry for the property in Resource Type Properties.

   # clresourcetype set -n installed-node-list \ [-p property=new-value]resource-type

   -n installed-node-list

   Specifies the names of nodes on which this resource type is installed.

   -p property=new-value

   Specifies the name of the standard property to change and the new value of the property.

   You cannot change the Installed_nodes property explicitly. To change this property, specify the -n installed-node-list option of the clresourcetype command.

4. Verify that the resource type property has been changed.

   # clresourcetype show resource-type

Example 2–19 Changing a Resource Type Property

This example shows how to change the SUNW.apache property to define that this resource type is installed on the global-cluster voting nodes of (phys-schost-1 and phys-schost-2).

# clresourcetype set -n phys-schost-1,phys-schost-2 SUNW.apache
# clresourcetype show SUNW.apache

Resource Type:                                     SUNW.apache:4
  RT_description:                                  Apache Web Server on Sun Cluster
  RT_version:                                      4
  API_version:                                     2
  RT_basedir:                                      /opt/SUNWscapc/bin
  Single_instance:                                 False
  Proxy:                                           False
  Init_nodes:                                      All potential masters
  Installed_nodes:                                 All
  Failover:                                        False
  Pkglist:                                         SUNWscapc
  RT_system:                                       False

How to Change Resource Group Properties

This procedure explains how to change resource group properties. For a description of resource group properties, see Resource Group Properties.

Perform this procedure from any cluster node.

Before You Begin

Ensure that you have the following information.

• The name of the resource group to change

• The name of the resource group property to change and its new value

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

2. Change the resource group property.

   # clresourcegroup set -p property=new-value resource-group

   -p property

   Specifies the name of the property to change

   resource-group

   Specifies the name of the resource group

3. Verify that the resource group property has been changed.

   # clresourcegroup show resource-group

Example 2–20 Changing a Resource Group Property

This example shows how to change the Failback property for the resource group (resource-group-1).

# clresourcegroup set-p Failback=True resource-group-1
# clrsourcegroup show resource-group-1

How to Change Resource Properties

This procedure explains how to change extension properties and standard properties of a resource.

• For a description of standard resource properties, see Resource Properties.

• For a description of the extension properties of a resource, see the documentation for the resource's resource type.

Perform this procedure from any cluster node.

Before You Begin

Ensure that you have the following information.

• The name of the resource with the property to change

• The name of the property to change

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

2. View the current resource property settings.

   # clresource show -v resource

3. Change the resource property.

   # clresource set -p standard-property=new-value | -p "extension-property \ [{node-specifier}]"=new-value resource

   -p standard-property=new-value

   Specifies the name of the standard property to change.

   -p "extension-property[{node-specifier}]"=new-value

   Specifies the name of the extension property to change.

   node-specifier is an optional qualifier to the -p and -x options. This qualifier indicates that the extension property or properties on only the specified node or nodes are to be set when the resource is created. The specified extension properties on other nodes in the cluster are not set. If you do not include node-specifier, the specified extension properties on all nodes in the cluster are set. You can specify a node name or a node identifier for node-specifier. Examples of the syntax of node-specifier include the following:

   -p "myprop{phys-schost-1}"

   The braces ({}) indicate that you are setting the specified extension property on only node phys-schost-1. For most shells, the double quotation marks (“) are required.

   You can also use the following syntax to set an extension property in two different global-cluster non-voting nodes on two different global-cluster voting nodes:

   -x "myprop{phys-schost-1:zoneA,phys-schost-2:zoneB}"

   ---

   Note –

   The extension property that you specify with node-specifier must be declared in the RTR file as a per-node property. See Appendix B, Standard Properties for information about the Per_node resource property attribute.

   ---

   resource

   Specifies the name of the resource.

4. Verify that the resource property has been changed.

   # clresource show -v resource

Example 2–21 Changing a Standard Resource Property

This example shows how to change the system-defined Start_timeout property for the resource (resource-1).

# clresource set -p start_timeout=30 resource-1
# clresource show -v resource-1

Example 2–22 Changing an Extension Resource Property

This example shows how to change an extension property (Log_level) for the resource (resource-1).

# clresource set -p Log_level=3 resource-1
# clresource show -v resource-1

How to Modify a Logical Hostname Resource or a Shared Address Resource

By default, logical hostname resources and shared address resources use name services for name resolution. You might configure a cluster to use a name service that is running on the same cluster. During the failover of a logical hostname resource or a shared address resource, a name service that is running on the cluster might also be failing over. If the logical hostname resource or the shared address resource uses the name service that is failing over, the resource fails to fail over.

Configuring a cluster to use a name server that is running on the same cluster might impair the availability of other services on the cluster.

To prevent such a failure to fail over, modify the logical hostname resource or the shared address resource to bypass name services. To modify the resource to bypass name services, set the CheckNameService extension property of the resource to false. You can modify the CheckNameService property at any time.

If your version of the resource type is earlier than 2, you must upgrade the resource type before you attempt to modify the resource. For more information, see Upgrading a Preregistered Resource Type.

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

2. Change the resource property.

   # clresource set -p CheckNameService=false resource

   -p CheckNameService=false

   Sets the CheckNameService extension property of the resource to false.

   resource

   Specifies the name of the logical hostname resource or shared address resource that you are modifying.