Sun Cluster 3.0 12/01 Data Services Installation and Configuration Guide

Chapter 13 Administering Data Service Resources

This chapter describes how to use the scrgadm(1M) command to manage resources, resource groups, and resource types within the cluster. See "Tools for Data Service Resource Administration" to determine if you can use other tools to complete a procedure.

This chapter contains the following procedures.

See Chapter 1, Planning for Sun Cluster Data Services and the Sun Cluster 3.0 12/01 Concepts document for overview information about resource types, resource groups, and resources.

Administering Data Service Resources

Table 13-1 lists the sections that describe the administration tasks for data service resources.

Table 13-1 Task Map: Data Service Administration


Task	For Instructions, Go To ...
Register a resource type	"How to Register a Resource Type"
Create failover or scalable resource groups	"How to Create a Failover Resource Group" "How to Create a Scalable Resource Group"
Add logical hostnames or shared addresses and data service resources to resource groups	"How to Add a Logical Hostname Resource to a Resource Group" "How to Add a Shared Address Resource to a Resource Group" "How to Add a Failover Application Resource to a Resource Group" "How to Add a Scalable Application Resource to a Resource Group"
Enable resources and resource monitors, manage the resource group, and bring the resource group and its associated resources online	"How to Bring a Resource Group Online"
Disable and enable resource monitors independent of the resource	"How to Disable a Resource Fault Monitor" "How to Enable a Resource Fault Monitor"
Remove resource types from the cluster	"How to Remove a Resource Type"
Remove resource groups from the cluster	"How to Remove a Resource Group"
Remove resources from resource groups	"How to Remove a Resource"
Switch the primary for a resource group	"How to Switch the Current Primary of a Resource Group"
Disable resources and move their resource group into the unmanaged state	"How to Disable a Resource and Move Its Resource Group Into the Unmanaged State"
Display resource type, resource group, and resource configuration information	"How to Display Resource Type, Resource Group, and Resource Configuration Information"
Change resource type, resource group, and resource properties	"How to Change Resource Type Properties" "How to Change Resource Group Properties" "How to Change Resource Properties"
Clear error flags for failed Resource Group Manager (RGM) processes	"How to Clear the `STOP_FAILED` Error Flag on Resources"
Re-register the built-in resource types `LogicalHostname` and `SharedAddress`	"How to Re-register Preregistered Resource Types"
Update the network interface ID list for the network resources, and update the node list for the resource group	"How to Add a Node to a Resource Group"
Remove a node from a resource group	"How to Remove a Node From a Resource Group"
Set up `SUNW.HAStorage` for resource groups so as to synchronize the startups between those resource groups and disk device groups	"How to Set Up `SUNW.HAStorage` Resource Type for New Resources"

Note -

The procedures in this chapter describe how to use the scrgadm(1M) command to complete these tasks. Other tools also enable you to administer your resources. See "Tools for Data Service Resource Administration" for details about these options.

Configuring and Administering Sun Cluster Data Services

Configuring a Sun Cluster data service is a single task composed of several procedures. These procedures enable you to perform the following tasks.

Register a resource type.
Create resource groups.
Add resources into the resource groups.
Bring the resources online.

Use the procedures in this chapter to update your data service configuration after the initial configuration. For example, to change resource type, resource group, and resource properties, go to "Changing Resource Type, Resource Group, and Resource Properties".

Registering a Resource Type

A resource type provides specification of common properties and callback methods that apply to all of the resources of the given type. You must register a resource type before you create a resource of that type. See Chapter 1, Planning for Sun Cluster Data Services for details about resource types.

How to Register a Resource Type

To complete this procedure, you must supply the name for the resource type that you plan to register. The resource type name is an abbreviation for the data service name. This name maps to the name shown on your data service license certificate. See the Sun Cluster 3.0 12/01 Release Notes for details on the mapping between the names and the license certificate names.

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Register the resource type.
# scrgadm -a -t resource-type
-a

Adds the specified resource type.

-t resource-type

Specifies name of the resource type to add. See the Sun Cluster 3.0 12/01 Release Notes to determine the predefined name to supply.

Verify that the resource type has been registered.
# scrgadm -pv -t resource-type

Example - Registering Resource Types

The following example registers Sun Cluster HA for iPlanet Web Server (internal name iws).

# scrgadm -a -t SUNW.iws
# scrgadm -pv -t SUNW.iws
Res Type name:                                   SUNW.iws
  (SUNW.iws) Res Type description:               None registered
  (SUNW.iws) Res Type base directory:            /opt/SUNWschtt/bin
  (SUNW.iws) Res Type single instance:           False
  (SUNW.iws) Res Type init nodes:                All potential masters
  (SUNW.iws) Res Type failover:                  False
  (SUNW.iws) Res Type version:                   1.0
  (SUNW.iws) Res Type API version:               2
  (SUNW.iws) Res Type installed on nodes:        All
  (SUNW.iws) Res Type packages:                  SUNWschtt

Where to Go From Here

After registering resource types, you can create resource groups and add resources to the resource group. See "Creating a Resource Group" for details.

Creating a Resource Group

A resource group contains a set of resources, all of which are brought online or offline together on a given node or set of nodes. You must create an empty resource group before you place resources into it.

The two resource group types are failover and scalable. A failover resource group can be online on one node only at any time, while a scalable resource group can be online on multiple nodes simultaneously.

The following procedure describes how to use the scrgadm(1M) command to register and configure your data service.

See Chapter 1, Planning for Sun Cluster Data Services and the Sun Cluster 3.0 12/01 Concepts document for conceptual information on resource groups.

How to Create a Failover Resource Group

A failover resource group contains network addresses, such as the built-in resource types LogicalHostname and SharedAddress, as well as failover resources, such as the data service application resources for a failover data service. The network resources, along with their dependent data service resources, move between cluster nodes when data services fail over or are switched over.

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Create the failover resource group.
# scrgadm -a -g resource-group [-h nodelist]
-a

Adds the specified resource group.

-g resource-group

Specifies your choice of the name of the failover resource group to add. This name must begin with an ASCII character.

-h nodelist

Specifies an optional, ordered list of nodes that can master this resource group. If you do not specify this list, it defaults to all of the nodes in the cluster.

Verify that the resource group has been created.
# scrgadm -pv -g resource-group

Example - Creating a Failover Resource Group

This example shows the addition of a failover resource group (resource-group-1) that two nodes (phys-schost-1 and phys-schost-2) can master.

# scrgadm -a -g resource-group-1 -h phys-schost1,phys-schost-2
# scrgadm -pv -g resource-group-1
Res Group name:                                          resource-group-1
  (resource-group-1) Res Group RG_description:           <NULL>
  (resource-group-1) Res Group management state:         Unmanaged
  (resource-group-1) Res Group Failback:                 False
  (resource-group-1) Res Group Nodelist:                 phys-schost-1  
                                                         phys-schost-2
  (resource-group-1) Res Group Maximum_primaries:        1
  (resource-group-1) Res Group Desired_primaries:        1
  (resource-group-1) Res Group RG_dependencies:          <NULL>
  (resource-group-1) Res Group mode:                     Failover
  (resource-group-1) Res Group network dependencies:     True
  (resource-group-1) Res Group Global_resources_used:    All
  (resource-group-1) Res Group Pathprefix:

Where to Go From Here

After you create a failover resource group, you can add application resources to this resource group. See "Adding Resources to Resource Groups" for the procedure.

How to Create a Scalable Resource Group

A scalable resource group is used with scalable services. The shared address feature is the Sun Cluster networking facility that enables the multiple instances of a scalable service to appear as a single service. You must first create a failover resource group that contains the shared addresses on which the scalable resources depend. Next, create a scalable resource group, and add scalable resources to that group.

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Create the failover resource group that holds the shared addresses that the scalable resource will use.

Create the scalable resource group.
# scrgadm -a -g resource-group \ -y Maximum_primaries=m \ -y Desired_primaries=n \ -y RG_dependencies=depend-resource-group \ -h nodelist]
-a

Adds a scalable resource group.

-g resource-group

Specifies your choice of the name of the scalable resource group to add.

-y Maximum_primaries=m

Specifies the maximum number of active primaries for this resource group.

-y Desired_primaries=n

Specifies the number of active primaries on which the resource group should attempt to start.

-y RG_dependencies=depend-resource-group

Identifies the resource group that contains the shared address resource on which the resource group that is being created depends.

-h nodelist

Specifies an optional list of nodes on which this resource group is to be available. If you do not specify this list, the value defaults to all of the nodes.

Verify that the scalable resource group has been created.
# scrgadm -pv -g resource-group

Example - Creating a Scalable Resource Group

This example shows the addition of a scalable resource group (resource-group-1) to be hosted on two nodes (phys-schost-1, phys-schost-2). The scalable resource group depends on the failover resource group (resource-group-2) that contains the shared addresses.

# scrgadm -a -g resource-group-1 \
-y Maximum_primaries=2 \
-y Desired_primaries=2 \
-y RG_dependencies=resource-group-2 \
-h phys-schost-1,phys-schost-2
# scrgadm -pv -g resource-group-1
Res Group name:                                          resource-group-1
  (resource-group-1) Res Group RG_description:           <NULL>
  (resource-group-1) Res Group management state:         Unmanaged
  (resource-group-1) Res Group Failback:                 False
  (resource-group-1) Res Group Nodelist:                 phys-schost-1
                                                         phys-schost-2
  (resource-group-1) Res Group Maximum_primaries:        2
  (resource-group-1) Res Group Desired_primaries:        2
  (resource-group-1) Res Group RG_dependencies:          resource-group-2
  (resource-group-1) Res Group mode:                     Scalable
  (resource-group-1) Res Group network dependencies:     True
  (resource-group-1) Res Group Global_resources_used:    All
  (resource-group-1) Res Group Pathprefix:

Where to Go From Here

After you have created a scalable resource group, you can add scalable application resources to the resource group. See "How to Add a Scalable Application Resource to a Resource Group" for details.

Adding Resources to Resource Groups

A resource is an instantiation of a resource type. You must add resources to a resource group before the RGM can manage the resources. This section describes the following three resource types.

logical hostname resources
shared address resources
data service (application) resources

Always add logical hostname resources and shared address resources to failover resource groups. Add data service resources for failover data services to failover resource groups. Failover resource groups contain both the logical hostname resources and the application resources for the data service. Scalable resource groups contain only the application resources for scalable services. The shared address resources on which the scalable service depends must reside in a separate failover resource group. You must specify dependencies between the scalable application resources and the shared address resources for the data service to scale across cluster nodes.

See the Sun Cluster 3.0 12/01 Concepts document and Chapter 1, Planning for Sun Cluster Data Services for more information on resources.

How to Add a Logical Hostname Resource to a Resource Group

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

the name of the failover resource group into which you are adding the resource
the hostnames that you plan to add to the resource group

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Add the logical hostname resource to the resource group.
# scrgadm -a -L [-j resource] -g resource-group -l hostnamelist, ... [-n netiflist]
-a

Adds a logical hostname resource.

-L

Specifies the logical hostname resource form of the command.

-j resource

Specifies an optional resource name of your choice. If you do not specify this option, the name defaults to the first hostname that is specified with the -l option.

-g resource-group

Specifies the name of the resource group in which this resource resides.

-l hostnamelist, ...

Specifies a comma-separated list of UNIX hostnames (logical hostnames) by which clients communicate with services in the resource group.

-n netiflist

Specifies an optional, comma-separated list that identifies the NAFO groups on each node. All of the nodes in the resource group's node list must be represented in netiflist. See the scrgadm(1M) man page for a description of the syntax for specifying netiflist. If you do not specify this option, the scrgadm command attempts to discover a net adapter on the subnet that the hostnamelist identifies for each node in the node list.

Verify that the logical hostname resource has been added.
# scrgadm -pv -j resource
Adding the resource causes the Sun Cluster software to validate the resource. If the validation succeeds, you can enable the resource, and you can move the resource group into the state where the RGM manages it. If the validation fails, the scrgadm command produces an error message and exits. If the validation fails, check the syslog on each node for an error message. The message appears on the node that performed the validation, not necessarily the node on which you ran the scrgadm command.

Example - Adding a Logical Hostname Resource to a Resource Group

This example shows the addition of logical hostname resource (resource-1) to a resource group (resource-group-1).

# scrgadm -a -L -j resource-1 -g resource-group-1 -l schost-1
# scrgadm -pv -j resource-1
Res Group name: resource-group-1
(resource-group-1) Res name:                              resource-1
  (resource-group-1:resource-1) Res R_description:
  (resource-group-1:resource-1) Res resource type:        SUNW.LogicalHostname
  (resource-group-1:resource-1) Res resource group name:  resource-group-1
  (resource-group-1:resource-1) Res enabled:              False
  (resource-group-1:resource-1) Res monitor enabled:      True

Where to Go From Here

After you add logical hostname resources, use the procedure "How to Bring a Resource Group Online" to bring them online.

How to Add a Shared Address Resource to a Resource Group

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

The name of the resource group into which you are adding the resource. This group must be a failover resource group that you created previously.
The hostnames that you plan to add to the resource group.

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Add the shared address resource to the resource group.
# scrgadm -a -S [-j resource] -g resource-group -l hostnamelist, ... \ [-X auxnodelist] [-n netiflist]
-a

Adds shared address resources.

-S

Specifies the shared address resource form of the command.

-j resource

Specifies an optional resource name of your choice. If you do not specify this option, the name defaults to the first hostname that is specified with the -l option.

-g resource-group

Specifies the resource group name.

-l hostnamelist, ...

Specifies a comma-separated list of shared address hostnames.

-X auxnodelist

Specifies a comma-separated list of physical node names or IDs that identify the cluster nodes that can host the shared address but never serve as primary if failover occurs. These nodes are mutually exclusive, with the nodes identified as potential masters in the resource group's node list.

-n netiflist

Specifies an optional, comma-separated list that identifies the NAFO groups on each node. All of the nodes in the resource group's node list must be represented in the netiflist. See the scrgadm(1M) man page for a description of the syntax for specifying netiflist. If you do not specify this option, the scrgadm command attempts to discover a net adapter on the subnet that the hostnamelist identifies for each node in the node list.

Verify that the shared address resource has been added and validated.
# scrgadm -pv -j resource
Adding the resource causes the Sun Cluster software to validate the resource. If the validation succeeds, you can enable the resource, and you can move the resource group into the state where the RGM manages it. If the validation fails, the scrgadm command produces an error message and exits. If the validation fails, check the syslog on each node for an error message. The message appears on the node that performed the validation, not necessarily the node on which you ran the scrgadm command.

Example - Adding a Shared Address Resource to a Resource Group

This example shows the addition of a shared address resource (resource-1) to a resource group (resource-group-1).

# scrgadm -a -S -j resource-1 -g resource-group-1 -l schost-1
# scrgadm -pv -j resource-1
(resource-group-1) Res name:                                resource-1
    (resource-group-1:resource-1) Res R_description:
    (resource-group-1:resource-1) Res resource type:        SUNW.SharedAddress
    (resource-group-1:resource-1) Res resource group name:  resource-group-1
    (resource-group-1:resource-1) Res enabled:              False
    (resource-group-1:resource-1) Res monitor enabled:      True

Where to Go From Here

After you add a shared resource, use the procedure "How to Bring a Resource Group Online" to enable the resource.

How to Add a Failover Application Resource to a Resource Group

A failover application resource is an application resource that uses logical hostnames that you previously created in a failover resource group.

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

the name of the failover resource group into which you are adding the resource
the name of the resource type for the resource
the logical hostname resources that the application resource uses, which are the logical hostnames that you previously included in the same resource group

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Add a failover application resource to the resource group.
# scrgadm -a -j resource -g resource-group -t resource-type \ [-x Extension_property=value, ...] [-y Standard_property=value, ...]
-a

Adds a resource.

-j resource

Specifies your choice of the name of the resource to add.

-g resource-group

Specifies the name of the failover resource group created previously.

-t resource-type

Specifies the name of the resource type for the resource.

-x Extension_property=value, ...

Specifies a comma-separated list of extension properties that depend on the particular data service. See the chapter for each data service to determine whether the data service requires this property.

-y Standard_property=value, ...

Specifies a comma-separated list of standard properties that depends on the particular data service. See the chapter for each data service and Appendix A, Standard Properties to determine whether the data service requires this property.

Note -
You can set additional properties. See Appendix A, Standard Properties and the chapter in this book on how to install and configure your failover data service for details.

Verify that the failover application resource has been added and validated.
# scrgadm -pv -j resource
Adding the resource causes the Sun Cluster software to validate the resource. If the validation succeeds, you can enable the resource, and you can move the resource group into the state where the RGM manages it. If the validation fails, the scrgadm command produces an error message and exits. If the validation fails, check the syslog on each node for an error message. The message appears on the node that performed the validation, not necessarily the node on which you ran the scrgadm command.

Example - Adding a Failover Application Resource to a Resource Group

This example shows the addition of a resource (resource-1) to a resource group (resource-group-1). The resource depends on logical hostname resources (schost-1, schost-2), which must reside in the same failover resource groups that you defined previously.

# scrgadm -a -j resource-1 -g resource-group-1 -t resource-type-1 \
-y Network_resources_used=schost-1,schost2 \
# scrgadm -pv -j resource-1
(resource-group-1) Res name:                                resource-1
    (resource-group-1:resource-1) Res R_description:
    (resource-group-1:resource-1) Res resource type:        resource-type-1
    (resource-group-1:resource-1) Res resource group name:  resource-group-1
    (resource-group-1:resource-1) Res enabled:              False
    (resource-group-1:resource-1) Res monitor enabled:      True

Where to Go From Here

After you add a failover application resource, use the procedure "How to Bring a Resource Group Online" to enable the resource.

How to Add a Scalable Application Resource to a Resource Group

A scalable application resource is an application resource that uses shared addresses in a failover resource group.

To complete this procedure, you must supply the following information:

the name of the scalable resource group into which you are adding the resource
the name of the resource type for the resource
the shared address resources that the scalable service resource uses, which are the shared addresses that you previously included in a failover resource group

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Add a scalable application resource to the resource group.

# scrgadm -a -j resource -g resource-group -t resource-type \
-y Network_resources_used=network-resource[,network-resource...] \
-y Scalable=True
[-x Extension_property=value, ...] [-y Standard_property=value, ...]

-a: Adds a resource.
-j resource: Specifies your choice of the name of the resource to add.
-g resource-group: Specifies the name of a scalable service resource group that you previously created.
-t resource-type: Specifies the name of the resource type for this resource.
-y Network_resources_used= network-resource[,network-resource...]: Specifies the list of network resources (shared addresses) on which this resource depends.
-y Scalable=True: Specifies that this resource is scalable.
-x Extension_property=value, ...: Specifies a comma-separated list of extension properties that depend on the particular data service. See the chapter for each data service to determine whether the data service requires this property.
-y Standard_property=value, ...: Specifies a comma-separated list of standard properties that depends on the particular data service. See the chapter for each data service and Appendix A, Standard Properties to determine whether the data service requires this property.

Note -

You can set additional properties. See Appendix A, Standard Properties and the chapter in this book on how to install and configure your scalable data service for information on other configurable properties. Specifically for scalable services, you typically set the Port_list, Load_balancing_weights, and Load_balancing_policy properties, which Appendix A, Standard Properties describes.

Verify that the scalable application resource has been added and validated.
# scrgadm -pv -j resource
Adding the resource causes the Sun Cluster software to validate the resource. If the validation succeeds, you can enable the resource, and you can move the resource group into the state where the RGM manages it. If the validation fails, the scrgadm command produces an error message and exits. If the validation fails, check the syslog on each node for an error message. The message appears on the node that performed the validation, not necessarily the node on which you ran the scrgadm command.

Example - Adding a Scalable Application Resource to a Resource Group

This example shows the addition of a resource (resource-1) to a resource group (resource-group-1). Note that resource-group-1 depends on the failover resource group that contains the network addresses that are in use (schost-1 and schost-2 in the following example). The resource depends on shared address resources (schost-1, schost-2), which must reside in one or more failover resource groups that you defined previously.

# scrgadm -a -j resource-1 -g resource-group-1 -t resource-type-1 \
-y Network_resources_used=schost-1,schost-2 \
-y Scalable=True
# scrgadm -pv -j resource-1
(resource-group-1) Res name:                                resource-1
    (resource-group-1:resource-1) Res R_description:
    (resource-group-1:resource-1) Res resource type:        resource-type-1
    (resource-group-1:resource-1) Res resource group name:  resource-group-1
    (resource-group-1:resource-1) Res enabled:              False
    (resource-group-1:resource-1) Res monitor enabled:      True

Where to Go From Here

After you add a scalable application resource, follow the procedure "How to Bring a Resource Group Online" to enable the resource.

Bringing Resource Groups Online

To enable resources to begin providing HA services, you must enable the resources in the resource group, enable the resource monitors, make the resource group managed, and bring the resource group online. You can perform these tasks individually or by using the following one-step procedure. See the scswitch(1M) man page for details.

Note -

Perform this procedure from any cluster node.

How to Bring a Resource Group Online

Become superuser on a cluster member.

Enable the resource, and bring the resource group online.

If the resource monitor was disabled, it will be enabled also.
# scswitch -Z -g resource-group
-Z

Brings a resource group online by first enabling its resources and fault monitors.

-g resource-group

Specifies the name of the resource group to bring online. The group must be an existing resource group.

Verify that the resource is online.

Run the following command on any cluster node, and check the resource group state field to verify that the resource group is online on the nodes that are specified in the node list.
# scstat -g

Example - Bring a Resource Group Online

This example shows how to bring a resource group (resource-group-1) online and verify its status.

# scswitch -Z -g resource-group-1
# scstat -g

Where to Go From Here

After you bring a resource group online, it is configured and ready for use. If a resource or node fails, the RGM switches the resource group online on alternate nodes to maintain availability of the resource group.

Disabling and Enabling Resource Monitors

The following procedures disable or enable resource fault monitors, not the resources themselves. A resource can continue to operate normally while its fault monitor is disabled. However, if the fault monitor is disabled and a data service fault occurs, automatic fault recovery is not initiated.

See the scswitch(1M) man page for additional information.

Note -

Run this procedure from any cluster node.

How to Disable a Resource Fault Monitor

Become superuser on a cluster member.

Disable the resource fault monitor.
# scswitch -n -M -j resource
-n

Disable a resource or resource monitor.

-M

Disable the fault monitor for the specified resource.

-j resource

The name of the resource.

Verify that the resource fault monitor has been disabled.

Run the following command on each cluster node, and check for monitored fields (RS Monitored).
# scrgadm -pv

Example-Disabling a Resource Fault Monitor

This example shows how to disable a resource fault monitor.

# scswitch -n -M -j resource-1
# scrgadm -pv
...
RS Monitored: no...

How to Enable a Resource Fault Monitor

Become superuser on a cluster member.

Enable the resource fault monitor.
# scswitch -e -M -j resource
-e

Enables a resource or resource monitor.

-M

Enables the fault monitor for the specified resource.

-j resource

Specifies the name of the resource.

Verify that the resource fault monitor has been enabled.

Run the following command on each cluster node, and check for monitored fields (RS Monitored).
# scrgadm -pv

Example-Enabling a Resource Fault Monitor

This example shows how to enable a resource fault monitor.

# scswitch -e -M -j resource-1
# scrgadm -pv
...
RS Monitored: yes...

Removing Resource Types

You do not need to remove resource types that are not in use. However, if you want to remove a resource type, you can use this procedure to do so.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Remove a Resource Type

Before you remove a resource type, you must disable and remove all of the resources of that type in all of the resource groups that are in the cluster. Use the scrgadm -pv command to identify the resources and resource groups that are in the cluster.

Become superuser on a cluster member.

Disable each resource of the resource type that you will remove.
# scswitch -n -j resource
-n

Disables the resource.

-j resource

Specifies the name of the resource to disable.

Remove each resource of the resource type that you will remove.
# scrgadm -r -j resource
-r

Removes the specified resource.

-j

Specifies the name of the resource to remove.

Remove the resource type.
# scrgadm -r -t resource-type
-r

Removes the specified resource type.

-t resource-type

Specifies the name of the resource type to remove.

Verify that the resource type has been removed.
# scrgadm -p

Example - Removing a Resource Type

This example shows how to disable and remove all of the resources of a resource type (resource-type-1) and then remove the resource type itself. In this example, resource-1 is a resource of the resource type resource-type-1.

# scswitch -n -j resource-1
# scrgadm -r -j resource-1
# scrgadm -r -t resource-type-1

Removing Resource Groups

To remove a resource group, you must first remove all of the resources from the resource group.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Remove a Resource Group

Become superuser on a cluster member.

Run the following command to switch the resource group offline.
# scswitch -F -g resource-group
-F

Switches a resource group offline.

-g resource-group

Specifies the name of the resource group to take offline.

Disable all of the resources that are part of the resource group.

You can use the scrgadm -pv command to view the resources in the resource group. Disable all of the resources in the resource group that you will remove.
# scswitch -n -j resource
-n

Disables the resource.

-j resource

Specifies the name of the resource to disable.

If any dependent data service resources exist in a resource group, you cannot disable the resource until you have disabled all of the resources that depend on it.

Remove all of the resources from the resource group.

Use the scrgadm command to perform the following tasks.
- Remove the resources.
- Remove the resource group.
# scrgadm -r -j resource # scrgadm -r -g resource-group
-r

Removes the specified resource or resource group.

-j resource

Specifies the name of the resource to be removed.

-g resource-group

Specifies the name of the resource group to be removed.

Verify that the resource group has been removed.
# scrgadm -p

Example - Removing a Resource Group

This example shows how to remove a resource group (resource-group-1) after you have removed its resource (resource-1).

# scswitch -F -g resource-group-1
# scrgadm -r -j resource-1
# scrgadm -r -g resource-group-1

Removing Resources

Disable the resource before you remove it from a resource group.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Remove a Resource

Become superuser on a cluster member.

Disable the resource that you want to remove.
# scswitch -n -j resource
-n

Disables the resource.

-j resource

Specifies the name of the resource to disable.

Remove the resource.
# scrgadm -r -j resource
-r

Removes the specified resource.

-j resource

Specifies the name of the resource to remove.

Verify that the resource has been removed.
# scrgadm -p

Example - Removing a Resource

This example shows how to disable and remove a resource (resource-1).

# scswitch -n -j resource-1
# scrgadm -r -j resource-1

Switching the Current Primary of a Resource Group

Use the following procedure to switch over a resource group from its current primary to another node that will become the new primary.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Switch the Current Primary of a Resource Group

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

The name of the resource group that you will switch over.
The names of the nodes on which you want the resource group to be brought online or to remain online. These nodes must be cluster nodes that have been set up to be potential masters of the resource group that you will switch. To see a list of potential primaries for the resource group, use the scrgadm -pv command.

Become superuser on a cluster member.

Switch the primary to a potential primary.
# scswitch -z -g resource-group -h nodelist
-z

Switches the specified resource group online.

-g resource-group

Specifies the name of the resource group to switch.

-h nodelist

Specifies the node or nodes on which the resource group is to be brought online or is to remain online. This resource group is then switched offline on all of the other nodes.

Verify that the resource group has been switched to the new primary.

Run the following command, and check the output for the state of the resource group that has been switched over.
# scstat -g

Example - Switching the Resource Group to a New Primary

This example shows how to switch a resource group (resource-group-1) from its current primary (phys-schost-1) to the potential primary (phys-schost-2). First, verify that the resource group is online on phys-schost-1. Next, perform the switch. Finally, verify that the group is switched to be online on phys-schost-2.

phys-schost-1# scstat -g
...
Resource Group Name:          resource-group-1
  Status                                           
    Node Name:                phys-schost-1
    Status:                   Online

    Node Name:                phys-schost-2
    Status:                   Offline
...
phys-schost-1# scswitch -z -g resource-group-1 -h phys-schost-2
phys-schost-1# scstat -g
...
Resource Group Name:          resource-group-1
  Status                                           
    Node Name:                phys-schost-2
    Status:                   Online

    Node Name:                phys-schost-1
    Status:                   Offline
...

Disabling Resources and Moving Their Resource Group Into the Unmanaged State

At times, you must bring a resource group into the unmanaged state before you perform an administrative procedure on it. Before you move a resource group into the unmanaged state, you must disable all of the resources that are part of the resource group and bring the resource group offline.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Disable a Resource and Move Its Resource Group Into the Unmanaged State

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

the name of the resources to be disabled
the name of the resource group to move into the unmanaged state

To determine the resource and resource group names that you need for this procedure, use the scrgadm -pv command.

Become superuser on a cluster member.

Disable the resource.

Repeat this step for all of the resources in the resource group.
# scswitch -n -j resource
-n

Disables the resource.

-j resource

Specifies the name of the resource to disable.

Run the following command to switch the resource group offline.
# scswitch -F -g resource-group
-F

Switches a resource group offline.

-g resource-group

Specifies the name of the resource group to take offline.

Move the resource group into the unmanaged state.
# scswitch -u -g resource-group
-u

Moves the specified resource group in the unmanaged state.

-g resource-group

Specifies the name of the resource group to move into the unmanaged state.

Verify that the resources are disabled and the resource group is in the unmanaged state.
# scrgadm -pv -g resource-group

Example - Disabling a Resource and Moving the Resource Group Into the Unmanaged State

This example shows how to disable the resource (resource-1) and then move the resource group (resource-group-1) into the unmanaged state.

# scswitch -n -j resource-1
# scswitch -F -g resource-group-1
# scswitch -u -g resource-group-1
# scrgadm -pv -g resource-group-1
Res Group name:                                               resource-group-1
  (resource-group-1) Res Group RG_description:                <NULL>
  (resource-group-1) Res Group management state:              Unmanaged
  (resource-group-1) Res Group Failback:                      False
  (resource-group-1) Res Group Nodelist:                      phys-schost-1
                                                              phys-schost-2
  (resource-group-1) Res Group Maximum_primaries:             2
  (resource-group-1) Res Group Desired_primaries:             2
  (resource-group-1) Res Group RG_dependencies:               <NULL>
  (resource-group-1) Res Group mode:                          Failover
  (resource-group-1) Res Group network dependencies:          True
  (resource-group-1) Res Group Global_resources_used:         All
  (resource-group-1) Res Group Pathprefix:
 
  (resource-group-1) Res name:                                resource-1
    (resource-group-1:resource-1) Res R_description:
    (resource-group-1:resource-1) Res resource type:          SUNW.apache
    (resource-group-1:resource-1) Res resource group name:    resource-group-1
    (resource-group-1:resource-1) Res enabled:                True
    (resource-group-1:resource-1) Res monitor enabled:        False
    (resource-group-1:resource-1) Res detached:               False

Displaying Resource Type, Resource Group, and Resource Configuration Information

Before you perform administrative procedures on resources, resource groups, or resource types, use the following procedure to view the current configuration settings for these objects.

See the scrgadm(1M) and scswitch(1M) man pages for additional information.

Note -

Perform this procedure from any cluster node.

How to Display Resource Type, Resource Group, and Resource Configuration Information

The scrgadm command provides the following three levels of configuration status information.

With the -p option, the output shows a very limited set of property values for resource types, resource groups, and resources.

With the -pv option, the output shows more details on other resource type, resource group, and resource properties.

With the -pvv option, the output provides a detailed view, including resource type methods, extension properties, and all of the resource and resource group properties.

You can also use the -t, -g, and -j (resource type, resource group, and resource, respectively) options, followed by the name of the object that you want to view, to check status information on specific resource types, resource groups, and resources. For example, the following command specifies that you want to view specific information on the resource apache-1 only.

# scrgadm -p[v[v]] -j apache-1

See the scrgadm(1M) man page for details.

Changing Resource Type, Resource Group, and Resource Properties

Resource groups and resources have standard configuration properties that you can change. The following procedures describe how to change these properties.

Resources also have extension properties-some of which the data service developer predefines-that you cannot change. See the individual data service chapters in this document for a list of the extension properties for each data service.

See the scrgadm(1M) man page for information on the standard configuration properties for resource groups and resources.

How to Change Resource Type Properties

To complete this procedure, you must supply 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 one property-the list of nodes on which resources of this type can be instantiated.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Run the scrgadm command to determine the name of the resource type that you need for this procedure.
# scrgadm -pv

Change the resource type property.

The only property that can be changed for a resource type is the Installed_node_list property.
# scrgadm -c -t resource-type -h installed-node-list
-c

Changes the specified resource type property.

-t resource-type

Specifies the name of the resource type.

-h installed-node-list

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

Verify that the resource type property has been changed.
# scrgadm -pv -t resource-type

Example - Changing a Resource Type Property

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

# scrgadm -c -t SUNW.apache -h phys-schost-1,phys-schost-2 
# scrgadm -pv -t SUNW.apache
Res Type name:                               SUNW.apache
  (SUNW.apache) Res Type description:        Apache Resource Type
  (SUNW.apache) Res Type base directory:     /opt/SUNWscapc/bin
  (SUNW.apache) Res Type single instance:    False
  (SUNW.apache) Res Type init nodes:         All potential masters
  (SUNW.apache) Res Type failover:           False
  (SUNW.apache) Res Type version:            1.0
  (SUNW.apache) Res Type API version:        2
  (SUNW.apache) Res Type installed on nodes: phys-schost1 phys-schost-2
  (SUNW.apache) Res Type packages:           SUNWscapc

How to Change Resource Group Properties

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

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

This procedure describes the steps to change resource group properties. See Appendix A, Standard Properties for a complete list of resource group properties.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Change the resource group property.
# scrgadm -c -g resource-group -y property=new-value
-c

Changes the specified property.

-g resource-group

Specifies the name of the resource group.

-y property

Specifies the name of the property to change.

Verify that the resource group property has been changed.
# scrgadm -pv -g resource-group

Example - Changing a Resource Group Property

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

# scrgadm -c -g resource-group-1 -y Failback=True
# scrgadm -pv -g resource-group-1

How to Change Resource Properties

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

the name of the resource with the property to change
the name of the property to change

This procedure describes the steps to change resource properties. See Appendix A, Standard Properties for a complete list of resource group properties.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Run the scrgadm -pvv command to view the current resource property settings.
# scrgadm -pvv -j resource

Change the resource property.
# scrgadm -c -j resource -y property=new-value | -x extension-property=new-value
-c

Changes the specified property.

-j resource

Specifies the name of the resource.

-y property=new-value

Specifies the name of the standard property to change.

-x extension-property=new-value

Specifies the name of the extension property to change. For data services that Sun supplies, see the extension properties that are documented in the chapters on how to install and configure the individual data services.

Verify that the resource property has been changed.
# scrgadm pvv -j resource

Example - Changing a Standard Resource Property

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

# scrgadm -c -j resource-1 -y start_timeout=30
# scrgadm -pvv -j resource-1

Example - Changing an Extension Resource Property

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

# scrgadm -c -j resource-1 -x Log_level=3
# scrgadm -pvv -j resource-1

Clearing the `STOP_FAILED` Error Flag on Resources

When the Failover_mode resource property is set to NONE or SOFT and the STOP of a resource fails, the individual resource goes into the STOP_FAILED state, and the resource group goes into the ERROR_STOP_FAILED state. You cannot bring a resource group in this state on any node online, nor can you edit the resource group (create or delete resources, or change resource group or resource properties).

How to Clear the `STOP_FAILED` Error Flag on Resources

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

the name of the node where the resource is STOP_FAILED
the name of the resource and resource group that are in STOP_FAILED state

See the scswitch(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

Become superuser on a cluster member.

Identify which resources have gone into the STOP_FAILED state and on which nodes.
# scstat -g

Manually stop the resources and their monitors on the nodes on which they are in STOP_FAILED state.

This step might require that you kill processes or run commands that are specific to resource types or other commands.

Manually set the state of these resources to OFFLINE on all of the nodes on which you manually stopped the resources.
# scswitch -c -h nodelist -j resource -f STOP_FAILED
-c

Clears the flag.

-h nodelist

Specifies the node names on which the resource was running.

-j resource

Specifies the name of the resource to switch offline.

-f STOP_FAILED

Specifies the flag name.

Check the resource group state on the nodes where you cleared the STOP_FAILED flag in Step 4.

The resource group state should now be OFFLINE or ONLINE.
# scstat -g
The command scstat -g indicates whether the resource group remains in the ERROR_STOP_FAILED state. If the resource group is still in the ERROR_STOP_FAILED state, then run the following scswitch command to switch the resource group offline on the appropriate nodes.
# scswitch -F -g resource-group
-F

Switches the resource group offline on all of the nodes that can master the group.

-g resource-group

Specifies the name of the resource group to switch offline.

This situation can occur if the resource group was being switched offline when the STOP method failure occurred and the resource that failed to stop had a dependency on other resources in the resource group. Otherwise, the resource group reverts to the ONLINE or OFFLINE state automatically after you have run the command in Step 4 on all of the STOP_FAILED resources.

Now you can switch the resource group to the ONLINE state.

Re-registering Preregistered Resource Types

Two preregistered resource types are SUNW.LogicalHostname and SUNW.SharedAddress. All of the logical hostname and shared address resources use these resource types. You never need to register these two resource types, but you might accidentally delete them. If you have deleted resource types inadvertently, use the following procedure to re-register them.

See the scrgadm(1M) man page for additional information.

Note -

Perform this procedure from any cluster node.

How to Re-register Preregistered Resource Types

Re-register the resource type.

# scrgadm -a -t SUNW.resource-type

-a: Adds a resource type.
-t SUNW.resource-type: Specifies the resource type to add (re-register). The resource type can be either SUNW.LogicalHostname or SUNW.SharedAddress.

Example - Re-registering a Preregistered Resource Type

This example shows how to re-register the SUNW.LogicalHostname resource type.

# scrgadm -a -t SUNW.LogicalHostname

Adding or Removing a Node to or From a Resource Group

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

Configure a cluster node to be an additional master of a resource group.
Remove a node from a resource group

The procedures are slightly different, depending on whether you plan to add or remove the node 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 NAFO groups that it uses. For failover resource groups, you must update the complete list of NAFO groups for each network resource that the resource group includes (the netiflist resource property).

For scalable resource groups, in addition to changing the scalable group to be mastered on the new set of hosts, you must repeat the procedure for failover groups that contain the network resources that the scalable resource uses.

See the scrgadm(1M) man page for additional information.

Note -

Run either of these procedures from any cluster node.

How to Add a Node to a Resource Group

This procedure contains the following sections.

You must supply the following information to complete this 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 NAFO group that will 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

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 4 in the following procedure for details.

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.
# scrgadm -c -g resource-group -h nodelist
-c

Changes a resource group.

-g resource-group

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

-h nodelist

Specifies a comma-separated list of nodes that can master the resource group.

(Optional) Update the Load_balancing_weights property of the scalable resource to assign a weight to the node that you want to add to the resource group.

Otherwise, the weight defaults to 1. See the scrgadm(1M) man page for more information.

How to Add a Node to a Failover Resource Group

Display the current node list and the current list of NAFO groups that are configured for each resource in the resource group.
# scrgadm -pvv -g resource-group | grep -i nodelist # scrgadm -pvv -g resource-group | grep -i netiflist
Note -
The output of the command line for nodelist identifies the nodes by node name. The output for netiflist identifies the nodes by node ID.

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 of the NAFO groups here. Also, you must input nodes to netiflist by node ID. To find the node ID, use scconf -pv | grep "Node ID".
# scrgadm -c -j network-resource -x netiflist=netiflist
-c

Changes a network resource.

-j network-resource

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

-x netiflist=netiflist

Specifies a comma-separated list that identifies the NAFO groups on each node. Each element in netiflist must be in the form of NAFO-group-name@nodeid.

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.
# scrgadm -c -g resource-group -h nodelist
-c

Changes a resource group.

-g resource-group

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

-h nodelist

Specifies a comma-separated list of nodes that can master the resource group.

Verify the updated information.

# scrgadm -pvv -g resource-group | grep -i nodelist
# scrgadm -pvv -g resource-group | grep -i netiflist

Example - Adding a Node to a Resource Group

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

# scrgadm -pvv -g resource-group-1 | grep -i nodelist
(resource-group-1) Res Group Nodelist:    phys-schost-1 phys-schost-3
# scrgadm -pvv -g resource-group-1 | grep -i netiflist
(resource-group-1:schost-2) Res property name: NetIfList
(resource-group-1:schost-2:NetIfList) Res property class: extension
(resource-group-1:schost-2:NetIfList) List of NAFO interfaces on each node
(resource-group-1:schost-2:NetIfList) Res property type: stringarray
(resource-group-1:schost-2:NetIfList) Res property value: nafo0@1 nafo0@3
 
(Only nodes 1 and 3 have been assigned NAFO groups. You must add a NAFO group 
for node 2.)

# scrgadm -c -j schost-2 -x netiflist=nafo0@1,nafo0@2,nafo0@3
# scrgadm -c -g resource-group-1 -h phys-schost-1,phys-schost-2,phys-schost-3
# scrgadm -pvv -g resource-group-1 | grep -i nodelist
(resource-group-1) Res Group Nodelist:     phys-schost-1 phys-schost-2 
                                           phys-schost-3
# scrgadm -pvv -g resource-group-1 | grep -i netiflist
(resource-group-1:schost-2:NetIfList) Res property value: nafo0@1 nafo0@2
                                                          nafo0@3

How to Remove a Node From a Resource Group

This procedure contains the following sections.

To complete these procedures, you must supply the following information.

the names and node IDs of all of the cluster nodes
the name(s) of the resource group or groups from which you plan to remove the node
the names of the NAFO groups that will host the network resources that are used by the resource group(s) on all of the nodes

Additionally, be sure to verify that the resource group is not mastered on the node that you will remove. If the resource group is mastered on the node that you will remove, run the scswitch command to switch the resource group offline from that node. The following scswitch command will bring the resource group offline from a given node, provided that new-masters does not contain that node.

# scswitch -z -g resource-group -h new-masters

-g resource-group: Specifies the name of the resource group (mastered on the node that you will remove) that you are switching offline.
-h new-masters: Specifies the node(s) that will now master the resource group.

See the scswitch(1M) man page for additional information.

Caution -

If you plan to remove a node from all of the resource groups, and you use a scalable services configuration, first remove the node from the scalable resource group(s). Then, remove the node from the failover group(s).

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. See Appendix A, Standard Properties for details on this property.

See the Sun Cluster 3.0 12/01 Concepts document for details about scalable service configuration.

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

Remove the node from the list of nodes that can master the scalable resource group (the nodelist resource group property).
# scrgadm -c -g scalable-resource-group -h nodelist
-c

Changes a resource group.

-g scalable-resource-group

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

-h nodelist

Specifies a comma-separated list of nodes that can master this resource group.

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

See "How to Remove a Node From a Failover Resource Group That Contains Shared Address Resources" for details.

(Optional) Update the Load_balancing_weights property of the scalable resource to remove the weight of the node that you want to remove from the resource group.

See the scrgadm(1M) man page for more information.

How to Remove a Node From a Failover Resource Group

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

Caution -

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

Note -

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

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

This step removes the node and overwrites the previous value of the node list. Be sure to include all of the nodes that can master the resource group here.
# scrgadm -c -g failover-resource-group -h nodelist
-c

Changes a resource group.

-g failover-resource-group

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

-h nodelist

Specifies a comma-separated list of nodes that can master this resource group.

Display the current list of NAFO groups that are configured for each resource in the resource group.
# scrgadm -pvv -g failover-resource-group | grep -i netiflist
Note -
The output of the preceding command line identifies the nodes by node ID.

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

This step overwrites the previous value of netiflist. Be sure to include all of the NAFO groups here. Also, you must input nodes to netiflist by node ID. Run the command line scconf -pv | grep "Node ID" to find the node ID.
# scrgadm -c -j network-resource -x netiflist=netiflist
-c

Changes a network resource.

-j network-resource

Specifies the name of the network resource that is hosted on the netiflist entries.

-x netiflist=netiflist

Specifies a comma-separated list that identifies the NAFO groups on each node. Each element in netiflist must be in the form of NAFO-group-name@nodeid.

Verify the updated information.

# scrgadm -pvv -g failover-resource-group | grep -i nodelist
# scrgadm -pvv -g failover-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 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 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 recreate the shared address resource.

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

Note -

You can also use the following procedure to remove the node from the auxnodelist of the shared address resource. To remove the node from the auxnodelist, you must delete and recreate the shared address resource.

Switch the scalable service resource offline.

Remove the shared address resource from the failover resource group.

Create the shared address resource.

Add the node ID or node name of the node that you removed from the failover resource group to the auxnodelist.
# scrgadm -a -S -g failover-resource-group -l shared-address -X new-auxnodelist
failover-resource-group

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

shared-address

The name of the shared address.

new-auxnodelist

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

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), which contains a logical hostname resource (schost-1).

# scrgadm -pvv -g resource-group-1 | grep -i nodelist
(resource-group-1) Res Group Nodelist:       phys-schost-1 phys-schost-2 
                                             phys-schost-3
# scrgadm -c -g resource-group-1 -h phys-schost-1,phys-schost-2
# scrgadm -pvv -g resource-group-1 | grep -i netiflist
(resource-group-1:schost-1) Res property name: NetIfList
(resource-group-1:schost-1:NetIfList) Res property class: extension
(resource-group-1:schost-1:NetIfList) List of NAFO interfaces on each node
(resource-group-1:schost-1:NetIfList) Res property type: stringarray
(resource-group-1:schost-1:NetIfList) Res property value: nafo0@1 nafo0@2
                                                          nafo0@3

(nafo0@3 is the NAFO group to be removed.)

# scrgadm -c -j schost-1 -x netiflist=nafo0@1,nafo0@2
# scrgadm -pvv -g resource-group-1 | grep -i nodelist
(resource-group-1) Res Group Nodelist:       phys-schost-1 phys-schost-2
# scrgadm -pvv -g resource-group-1 | grep -i netiflist
(resource-group-1:schost-1:NetIfList) Res property value: nafo0@1 nafo0@2

Synchronizing the Startups Between Resource Groups and Disk Device Groups

After a cluster boots up or services fail over to another node, global devices and cluster file systems might require time to become available. However, a data service can run its START method before global devices and cluster file systems-on which the data service depends-come online. In this instance, the START method times out, and you must reset the state of the resource groups that the data service uses and restart the data service manually.The resource type SUNW.HAStorage monitors the global devices and cluster file systems and causes the START method of the other resources in the same resource group to wait until they become available. To avoid additional administrative tasks, set up SUNW.HAStorage for all of the resource groups whose data service resources depend on global devices or cluster file systems.

How to Set Up `SUNW.HAStorage` Resource Type for New Resources

In the following example, the resource group resource-group-1 contains three data services.

iPlanet Web Server, which depends on /global/resource-group-1
Oracle, which depends on /dev/global/dsk/d5s2
NFS, which depends on dsk/d6

To create a SUNW.HAStorage resource hastorage-1 for new resources in resource-group-1, read "Synchronizing the Startups Between Resource Groups and Disk Device Groups" and then perform the following steps.

Become superuser on a cluster member.

Create the resource group resource-group-1.
# scrgadm -a -g resource-group-1

Determine whether the resource type is registered.

The following command prints a list of registered resource types.
# scrgadm -p | egrep Type

If you need to, register the resource type.
# scrgadm -a -t SUNW.HAStorage

Create the SUNW.HAStorage resource hastorage-1, and define the service paths.
# scrgadm -a -j hastorage-1 -g resource-group-1 -t SUNW.HAStorage \ -x ServicePaths=/global/resource-group-1,/dev/global/dsk/d5s2,dsk/d6
ServicePaths can contain the following values.
- global device group names, such as nfs-dg
- paths to global devices, such as /dev/global/dsk/d5s2 or dsk/d6
- cluster file system mount points, such as /global/nfs
Note -
Global device groups might not be collocated with the resource groups that correspond to them if ServicePaths contains cluster file system paths.

Enable the hastorage-1 resource.
# scswitch -e -j hastorage-1

Add the resources (iPlanet Web Server, Oracle, and NFS) to resource-group-1, and set their dependency to hastorage-1.

For example, for iPlanet Web Server, run the following command.

# scrgadm -a -j resource -g resource-group-1 -t SUNW.iws \
-x Confdir_list=/global/iws/schost-1 -y Scalable=False \
-y Network_resources_used=schost-1 -y Port_list=80/tcp \
-y Resource_dependencies=hastorage-1

Verify that you have correctly configured the resource dependencies.
# scrgadm -pvv -j resource | egrep strong

Set resource-group-1 to the managed state, and bring resource-group-1 online.
# scswitch -Z -g resource-group-1

The SUNW.HAStorage resource type contains another extension property, AffinityOn, which is a Boolean that specifies whether SUNW.HAStorage must perform an affinity switchover for the global devices and cluster file systems that are defined in ServicePaths. See the SUNW.HAStorage(5) man page for details.

Note -

SUNW.HAStorage does not permit AffinityOn to be set to TRUE if the resource group is scalable. SUNW.HAStorage checks the AffinityOn value and internally resets the value to FALSE for a scalable resource group.

How to Set Up `SUNW.HAStorage` Resource Type for Existing Resources

To create a SUNW.HAStorage resource for existing resources, read "Synchronizing the Startups Between Resource Groups and Disk Device Groups", and then perform the following steps.

Determine whether the resource type is registered.

The following command prints a list of registered resource types.
# scrgadm -p | egrep Type

If you need to, register the resource type.
# scrgadm -a -t SUNW.HAStorage

Create the SUNW.HAStorage resource hastorage-1.

# scrgadm -a -g resource-group -j hastorage-1 -t SUNW.HAStorage \
-x ServicePaths= ... -x AffinityOn=True

Enable the hastorage-1 resource.
# scswitch -e -j hastorage-1

Set up the dependency for each of the existing resources, as required.
# scrgadm -c -j resource -y Resource_Dependencies=hastorage-1

Verify that you have correctly configured the resource dependencies.
# scrgadm -pvv -j resource | egrep strong

Chapter 13 Administering Data Service Resources

Administering Data Service Resources

Configuring and Administering Sun Cluster Data Services

Registering a Resource Type

How to Register a Resource Type

Example - Registering Resource Types

Where to Go From Here

Creating a Resource Group

How to Create a Failover Resource Group

Example - Creating a Failover Resource Group

Where to Go From Here

How to Create a Scalable Resource Group

Example - Creating a Scalable Resource Group

Where to Go From Here

Adding Resources to Resource Groups

How to Add a Logical Hostname Resource to a Resource Group

Example - Adding a Logical Hostname Resource to a Resource Group

Where to Go From Here

How to Add a Shared Address Resource to a Resource Group

Example - Adding a Shared Address Resource to a Resource Group

Where to Go From Here

How to Add a Failover Application Resource to a Resource Group

Example - Adding a Failover Application Resource to a Resource Group

Where to Go From Here

How to Add a Scalable Application Resource to a Resource Group

Example - Adding a Scalable Application Resource to a Resource Group

Where to Go From Here

Bringing Resource Groups Online

How to Bring a Resource Group Online

Example - Bring a Resource Group Online

Where to Go From Here

Disabling and Enabling Resource Monitors

How to Disable a Resource Fault Monitor

Example-Disabling a Resource Fault Monitor

How to Enable a Resource Fault Monitor

Example-Enabling a Resource Fault Monitor

Removing Resource Types

How to Remove a Resource Type

Example - Removing a Resource Type

Removing Resource Groups

How to Remove a Resource Group

Example - Removing a Resource Group

Removing Resources

How to Remove a Resource

Example - Removing a Resource

Switching the Current Primary of a Resource Group

How to Switch the Current Primary of a Resource Group

Example - Switching the Resource Group to a New Primary

Disabling Resources and Moving Their Resource Group Into the Unmanaged State

How to Disable a Resource and Move Its Resource Group Into the Unmanaged State

Example - Disabling a Resource and Moving the Resource Group Into the Unmanaged State

Displaying Resource Type, Resource Group, and Resource Configuration Information

How to Display Resource Type, Resource Group, and Resource Configuration Information

Changing Resource Type, Resource Group, and Resource Properties

How to Change Resource Type Properties

Example - Changing a Resource Type Property

How to Change Resource Group Properties

Example - Changing a Resource Group Property

How to Change Resource Properties

Example - Changing a Standard Resource Property

Example - Changing an Extension Resource Property

Clearing the STOP_FAILED Error Flag on Resources

How to Clear the STOP_FAILED Error Flag on Resources

Re-registering Preregistered Resource Types

How to Re-register Preregistered Resource Types

Example - Re-registering a Preregistered Resource Type

Adding or Removing a Node to or From a Resource Group

How to Add a Node to a Resource Group

How to Add a Node to a Scalable Resource Group

How to Add a Node to a Failover Resource Group

Example - Adding a Node to a Resource Group

How to Remove a Node From a Resource Group

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

Example - Removing a Node From a Resource Group

Synchronizing the Startups Between Resource Groups and Disk Device Groups

How to Set Up SUNW.HAStorage Resource Type for New Resources

How to Set Up SUNW.HAStorage Resource Type for Existing Resources

Clearing the `STOP_FAILED` Error Flag on Resources

How to Clear the `STOP_FAILED` Error Flag on Resources

How to Set Up `SUNW.HAStorage` Resource Type for New Resources

How to Set Up `SUNW.HAStorage` Resource Type for Existing Resources