Changing Resource Type, Resource Group, and Resource Properties

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

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

Note - 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 the rt_properties(5) man page.

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

On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
Run the clresourcetype command to determine the name of the resource type that you need for this procedure.
```
# clresourcetype show -v
```
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 the rt_properties(5) man page.
```
# 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.
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 cluster nodes 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.2
  RT_description:                                  Apache Web Server on Oracle Solaris Cluster
  RT_version:                                      4.2
  API_version:                                     2
  RT_basedir:                                      /opt/SUNWscapc/bin
  Single_instance:                                 False
  Proxy:                                           False
  Init_nodes:                                      All potential masters
  Installed_nodes:                                 All
  Failover:                                        False
  Pkglist:                                         <NULL>
  RT_system:                                       False
  Global_zone:                                     False

How to Change Resource Group Properties

This procedure explains how to change resource group properties. For a description of resource group properties, see the rg_properties(5) man page.

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

On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
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
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 the r_properties(5) man page.
For a description of the extension properties of a resource, see the documentation for the resource's resource type.

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

On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
View the current resource property settings.
```
# clresource show -v resource
```
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.
The 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.

Note - The extension property that you specify with node-specifier must be declared in the RTR file as a per-node property.
resource

Specifies the name of the resource.
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 Change Resource Dependency Properties

This procedure explains how to set a resource dependency property. The RGM supports dependencies of one resource upon another. You can specify per-node resource dependencies, which might differ for each per-node instance of a resource. Per-node instances are instances of the resource that are online simultaneously (in a multi-mastered resource group) or disjointly in time (in a failover resource group) on different nodes. For a description of resource properties, see the r_properties(5) man page.

You can use the clsetup utility or the CLI to set a resource dependency. The following procedure shows the steps for the clsetup utility.

Assume the root role on any cluster node.
Start the clsetup utility.
```
# clsetup
```
The clsetup main menu is displayed.

Note - If you want to use the CLI to set a per-node dependency on a subset of cluster nodes, specify each per-node dependency in the following form: resourcename@nodename.
Type the number for the option for resource groups and press Return.
The Resource Group menu is displayed.
Type the number for the option for changing the properties of a resource and press Return.
The Change Properties of a Resource screen provides a description of this task.
Type yes and press Return.
A menu of options for this task is displayed.
Type the number for the option for changing standard resource properties and press Return.
A menu of options for this task is displayed.
Type the number for the option for the resource whose properties you want to change and press Return.
Only those standard properties that can be changed while the resource is in this state are shown. You might have to disable the resource in order to change certain properties. Check the r_properties(5) man page for more information on setting standard resource properties.
You can choose to change the resource_dependencies, resource_dependencies_weak, resource_dependencies_restart, or resource_dependencies_offline_restart properties.
Press Return when the resource state is displayed.
Type the number for the option for the dependency property you want to change and press Return.
The current property name, type, description, and value are displayed.
Type the new values for the dependency list and press Return.
Specify each resource on which this resource is to depend using the following format: resource-name, resource-name{qualifier}, or resource-name@node. See the text on the screen for more information.
For example, you can change the value of the resource_dependencies property from rs1 to rs1@mynode1,rs2@mynode2,rs3.
Type yes and press Return.
Verify that the dependency was set by pressing Return after the Command completed successfully message appears.
The new value you typed appears in the Current Setting column for the property.

Example 2-23 Changing Resource Dependency Properties

The following example shows how to use the clresource command to set a per-node resource dependency that is dependent on two different logical hostname resources. The example uses a scalable resource called gds-rs and sets the dependency of gds-rs on trancos-3-rs on ptrancos1 and trancos-4-rs on ptrancos2.

ptrancos1# clresource set -p resource_dependencies=trancos-3-rs@ptrancos1, \
trancos-4-rs@ptrancos2 gds-rs
ptrancos1# clresource show -p resource_dependencies gds-rs

=== Resources ===

Resource:                                       gds-rs
  Resource_dependencies: trancos-3-rs@ptrancos1 trancos-4-rs@ptrancos2

  --- Standard and extension properties ---

Example 2-24 Viewing Resource Dependency Properties

The following example shows how to use the scha_resource_get command to retrieve a per-node resource dependency that is dependent on two different logical hostname resources. To set a per-node resource dependency, you must use the clresource set command. The example uses a scalable resource called gds-rs and sets the dependency of gds-rs on trancos-3-rs on ptrancos1 and trancos-4-rs on ptrancos2.

From the ptrancos1 node:

ptrancos1(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES -R gds-rs
trancos-3-rs
ptrancos1(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES_NODE -R gds-rs ptrancos1
trancos-3-rs
ptrancos1(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES_NODE -R gds-rs ptrancos2
trancos-4-rs
ptrancos1(/root)$ scha_resource_get -Q -O RESOURCE_DEPENDENCIES -R gds-rs
trancos-3-rs@ptrancos1 
trancos-4-rs@ptrancos2
ptrancos1(/root)$ scha_resource_get -O NETWORK_RESOURCES_USED -R gds-rs
trancos-3-rs

From the ptrancos2 node:

ptrancos2(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES -R gds-rs
trancos-4-rs
ptrancos2(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES_NODE -R gds-rs ptrancos1
trancos-3-rs
ptrancos2(/root)$ scha_resource_get -O RESOURCE_DEPENDENCIES_NODE -R gds-rs ptrancos2
trancos-4-rs
ptrancos2(/root)$ scha_resource_get -Q -O RESOURCE_DEPENDENCIES -R gds-rs
trancos-3-rs@ptrancos1
trancos-4-rs@ptrancos2
ptrancos2(/root)$ scha_resource_get -O NETWORK_RESOURCES_USED -R gds-rs
trancos-4-rs

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.

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

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

On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
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.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Services Planning and Administration Guide Oracle Solaris Cluster 4.1