Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Services Planning and Administration Guide Oracle Solaris Cluster 4.1 |
1. Planning for Oracle Solaris Cluster Data Services
2. Administering Data Service Resources
Overview of Tasks for Administering Data Service Resources
Configuring and Administering Oracle Solaris Cluster Data Services
How to Register a Resource Type
How to Install and Register an Upgrade of a Resource Type
How to Migrate Existing Resources to a New Version of the Resource Type
How to Unregister Older Unused Versions of the Resource Type
How to Downgrade a Resource to an Older Version of Its Resource Type
How to Create a Failover Resource Group
How to Create a Scalable Resource Group
Configuring Failover and Scalable Data Services on Shared File Systems
How to Configure a Failover Application Using the ScalMountPoint Resource
How to Configure a Scalable Application Using the ScalMountPoint Resource
Tools for Adding Resources to Resource Groups
How to Add a Logical Hostname Resource to a Resource Group by Using the clsetup Utility
How to Add a Logical Hostname Resource to a Resource Group Using the Command-Line Interface
How to Add a Shared Address Resource to a Resource Group by Using the clsetup Utility
How to Add a Shared Address Resource to a Resource Group Using the Command-Line Interface
How to Add a Failover Application Resource to a Resource Group
How to Add a Scalable Application Resource to a Resource Group
Bringing Resource Groups Online
How to Bring Resource Groups Online
Switching Resource Groups to Preferred Primaries
How to Switch Resource Groups to Preferred Primaries
How to Quiesce a Resource Group
How to Quiesce a Resource Group Immediately
Suspending and Resuming the Automatic Recovery Actions of Resource Groups
Immediately Suspending Automatic Recovery by Killing Methods
How to Suspend the Automatic Recovery Actions of a Resource Group
How to Suspend the Automatic Recovery Actions of a Resource Group Immediately
How to Resume the Automatic Recovery Actions of a Resource Group
Disabling and Enabling Resource Monitors
How to Disable a Resource Fault Monitor
How to Enable a Resource Fault Monitor
How to Remove a Resource Group
Switching the Current Primary of a Resource Group
How to Switch the Current Primary of a Resource Group
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
Displaying Resource Type, Resource Group, and Resource Configuration Information
Changing Resource Type, Resource Group, and Resource Properties
How to Change Resource Type Properties
How to Change Resource Group Properties
How to Change Resource Properties
How to Change Resource Dependency Properties
How to Modify a Logical Hostname Resource or a Shared Address Resource
Clearing the STOP_FAILED Error Flag on Resources
How to Clear the STOP_FAILED Error Flag on Resources
Clearing the Start_failed Resource State
How to Clear a Start_failed Resource State by Switching Over a Resource Group
How to Clear a Start_failed Resource State by Restarting a Resource Group
How to Clear a Start_failed Resource State by Disabling and Enabling a Resource
Upgrading a Preregistered Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Reregistering Preregistered Resource Types After Inadvertent Deletion
How to Reregister Preregistered Resource Types After Inadvertent Deletion
Adding or Removing a Node to or From a Resource Group
Adding 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
Removing 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 Device Groups
Managed Entity Monitoring by HAStoragePlus
Troubleshooting Monitoring for Managed Entities
Additional Administrative Tasks to Configure HAStoragePlus Resources for a Zone Cluster
How to Set Up the HAStoragePlus Resource Type for New Resources
How to Set Up the HAStoragePlus Resource Type for Existing Resources
Configuring an HAStoragePlus Resource for Cluster File Systems
Sample Entries in /etc/vfstab for Cluster File Systems
How to Set Up the HAStoragePlus Resource for Cluster File Systems
How to Delete an HAStoragePlus Resource Type for Cluster File Systems
Enabling Highly Available Local File Systems
Configuration Requirements for Highly Available Local File Systems
Format of Device Names for Devices Without a Volume Manager
Sample Entries in /etc/vfstab for Highly Available Local File Systems
How to Set Up the HAStoragePlus Resource Type by Using the clsetup Utility
How to Delete an HAStoragePlus Resource That Makes a Local Solaris ZFS Highly Available
Sharing a Highly Available Local File System Across Zone Clusters
Modifying Online the Resource for a Highly Available Local File System
How to Add File Systems Other Than Solaris ZFS to an Online HAStoragePlus Resource
How to Remove File Systems Other Than Solaris ZFS From an Online HAStoragePlus Resource
How to Add a Solaris ZFS Storage Pool to an Online HAStoragePlus Resource
How to Remove a Solaris ZFS Storage Pool From an Online HAStoragePlus Resource
Changing a ZFS Pool Configuration That is Managed by an HAStoragePlus Resource
How to Change a ZFS Pool Configuration That is Managed by an Online HAStoragePlus Resource
How to Recover From a Fault After Modifying the Zpools Property of an HAStoragePlus Resource
Changing the Cluster File System to a Local File System in an HAStoragePlus Resource
How to Change the Cluster File System to Local File System in an HAStoragePlus Resource
Upgrading the HAStoragePlus Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Distributing Online Resource Groups Among Cluster Nodes
Enforcing Collocation of a Resource Group With Another Resource Group
Specifying a Preferred Collocation of a Resource Group With Another Resource Group
Distributing a Set of Resource Groups Evenly Among Cluster Nodes
Specifying That a Critical Service Has Precedence
Delegating the Failover or Switchover of a Resource Group
Combining Affinities Between Resource Groups
Zone Cluster Resource Group Affinities
Configuring the Distribution of Resource Group Load Across Nodes
How to Configure Load Limits for a Node
How to Set Priority for a Resource Group
How to Set Load Factors for a Resource Group
How to Set Preemption Mode for a Resource Group
How to Concentrate Load Onto Fewer Nodes in the Cluster
Enabling Oracle Solaris SMF Services to Run With Oracle Solaris Cluster
Encapsulating an SMF Service Into a Failover Proxy Resource Configuration
Encapsulating an SMF Service Into a Multi-Master Proxy Resource Configuration
Encapsulating an SMF Service Into a Scalable Proxy Resource Configuration
Tuning Fault Monitors for Oracle Solaris Cluster Data Services
Setting the Interval Between Fault Monitor Probes
Setting the Timeout for Fault Monitor Probes
Defining the Criteria for Persistent Faults
Complete Failures and Partial Failures of a Resource
Dependencies of the Threshold and the Retry Interval on Other Properties
System Properties for Setting the Threshold and the Retry Interval
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
Oracle Solaris Cluster provides the following tools for adding resources to resource groups:
The clsetup utility. See the clsetup(1CL) man page for more information.
Oracle Solaris Cluster maintenance commands.
You can use the clsetup utility or the Oracle Solaris Cluster maintenance commands to add the logical hostname resources and shared-address resources to the resource group.
The clsetup utility enables you to add resources to the resource group interactively. Configuring these resources interactively reduces the possibility for configuration errors that might result from command syntax errors or omissions. The clsetup utility ensure that all required resources are created and that all required dependencies between resources are set.
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.
Note - The DEPRECATED flag marks the logical hostname or shared address resource as a deprecated address. These addresses are not suitable for outbound requests since they can migrate to a different cluster node due to a failover or switchover.
For more information about resources, see Oracle Solaris Cluster Concepts Guide and Chapter 1, Planning for Oracle Solaris Cluster Data Services.
The following instructions explain how to add a logical hostname resource to a resource group by using the clsetup utility. Perform this procedure from one node only.
This procedure provides the long forms of the Oracle Solaris Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
Before You Begin
Ensure that the following prerequisites are met:
An entry for each logical hostname that is to be made available by the resource is added to the name service database.
If you are using IP Networking Multipathing (IPMP) groups, the groups are configured on the nodes where the logical hostname resource can be brought online.
Ensure that you have the following information:
The hostnames that you plan to add to the resource group
# clsetup
The clsetup main menu is displayed.
The Data Services menu is displayed.
The clsetup utility provides the list of prerequisites for performing this task.
The clsetup utility provides a list of the cluster nodes where the logical hostname resource can be brought online.
Ensure that the nodes are listed in the order in which the nodes are to appear in the logical hostname resource group's node list. The first node in the list is the primary node of this resource group.
The clsetup utility provides a screen where you can specify the logical hostname that the resource is to make available.
The clsetup utility lists the names of the Oracle Solaris Cluster objects that the utility will create.
The clsetup utility provides a screen where you can specify the new name.
The clsetup utility returns you to the list of the names of the Oracle Solaris Cluster objects that the utility will create.
The clsetup utility provides information about the Oracle Solaris Cluster configuration that the utility will create.
The clsetup utility provides a progress message to indicate that the utility is running commands to create the configuration. When configuration is complete, the clsetup utility lists the commands that the utility ran to create the configuration.
If you prefer, you can leave the clsetup utility running while you perform other required tasks before using the utility again. If you choose to quit clsetup, the utility recognizes your existing logical hostname resource group when you restart the utility.
Use the clresource(1CL) utility for this purpose. By default, the clsetup utility assigns the name node_name-rg to the resource group.
# clresource show node_name-rg
Note - When you add a logical hostname resource to a resource group, the extension properties of the resource are set to their default values. To specify a nondefault value, you must modify the resource after you add the resource to a resource group. For more information, see How to Modify a Logical Hostname Resource or a Shared Address Resource.
Perform this procedure from any cluster node.
Before You Begin
Ensure that you have the following information.
The name of the failover resource group to which you are adding the resource
The hostnames that you plan to add to the resource group
Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.
# clreslogicalhostname create -g resource-group -h hostnamelist, … [-N netiflist] resource
Specifies the name of the resource group in which this resource resides.
Specifies a comma-separated list of UNIX hostnames (logical hostnames) by which clients communicate with services in the resource group.
You must specify the fully qualified name with the -h option if you require a fully qualified hostname.
Specifies an optional, comma-separated list that identifies the IPMP groups that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as an IPMP group name, such as sc_ipmp0. The node can be identified by the node name or node ID, such as sc_ipmp0@1 or sc_ipmp@phys-schost-1.
Note - Oracle Solaris Cluster does not support the use of the adapter name for netif.
Specifies an optional resource name of your choice. You cannot use the fully qualified name in the resource name.
# clresource show resource
Example 2-6 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).
# clreslogicalhostname create -g resource-group-1 -h schost-1 resource-1 # clresource show resource-1 === Resources === Resource: resource-1 Type: SUNW.LogicalHostname:2 Type_version: 2 Group: resource-group-1 R_description: Resource_project_name: default Enabled{phys-schost-1}: True Enabled{phys-schost-2}: True Monitored{phys-schost-1}: True Monitored{phys-schost-2}: True
Example 2-7 Adding Logical Hostname Resources That Identify IPMP Groups
This example shows the addition of the following logical host name resources to the resource group nfs-fo-rg:
A resource that is named cs23-rs, which identifies the IPMP group sc_ipmp0 on node 1 and node 2
A resource that is named cs24-rs, which identifies the IPMP group sc_ipmp1 on node 1 and node 2
# clreslogicalhostname create -g nfs-fo-rg -h cs23-rs -N sc_ipmp0@1,sc_ipmp0@2 cs23-rs # clreslogicalhostname create -g nfs-fo-rg -h cs24-rs -N sc_ipmp1@1,sc_ipmp1@2 cs24-rs
Next Steps
After you add logical hostname resources, see How to Bring Resource Groups Online to bring the resources online.
Troubleshooting
Adding a resource causes the Oracle Solaris Cluster software to validate the resource. If the validation fails, the clreslogicalhostname command prints an error message and exits. To determine why the validation failed, 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 clreslogicalhostname command.
See Also
The clreslogicalhostname(1CL) man page.
The following instructions explain how to add a shared address resource to a resource group by using the clsetup utility. Perform this procedure from any cluster node.
This procedure provides the long forms of the Oracle Solaris Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
Before You Begin
Ensure that the following prerequisites are met:
The shared address that is to be made available by the resource has an entry in a name service database.
If you are using IP Networking Multipathing (IPMP) groups, the groups are configured on the nodes where the shared address resource can be brought online.
Ensure that you have the following information:
The hostnames that you plan to add to the resource group.
# clsetup
The clsetup main menu is displayed.
The Data Services menu is displayed.
The clsetup utility provides the list of prerequisites for performing this task.
The clsetup utility lists the cluster nodes where the shared address resource can be brought online.
The clsetup utility provides a screen where you can specify the shared address that the resource is to make available.
The clsetup utility lists the names of the Oracle Solaris Cluster objects that the utility will create.
The clsetup utility provides a screen where you can specify the new name.
The clsetup utility returns you to the list of the names of the Oracle Solaris Cluster objects that the utility will create.
The clsetup utility provides information about the Oracle Solaris Cluster configuration that the utility will create.
The clsetup utility provides a progress message to indicate that the utility is running commands to create the configuration. When configuration is complete, the clsetup utility lists the commands that the utility ran to create the configuration.
If you prefer, you can leave the clsetup utility running while you perform other required tasks before using the utility again. If you choose to quit clsetup, the utility recognizes your existing shared address resource group when you restart the utility.
Use the clresource(1CL) utility for this purpose. By default, the clsetup utility assigns the name node_name-rg to the resource group.
# clresource show node_name-rg
Note - When you add a shared address resource to a resource group, the extension properties of the resource are set to their default values. To specify a non–default value, you must modify the resource after you add the resource to a resource group. For more information, see How to Modify a Logical Hostname Resource or a Shared Address Resource.
Perform this procedure from any cluster node.
Before You Begin
Ensure that you have 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.
Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.
# clressharedaddress create -g resource-group -h hostnamelist, … \ [-X auxnodelist] [-N netiflist] resource
Specifies the resource group name.
Specifies a comma-separated list of shared address hostnames.
Specifies a comma-separated list of 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. If no auxiliary node list is explicitly specified, the list defaults to the list of all cluster node names that are not included in the node list of the resource group that contains the shared address resource.
Specifies an optional, comma-separated list that identifies the IPMP groups that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as an IPMP group name, such as sc_ipmp0. The node can be identified by the node name or node ID, such as sc_ipmp0@1 or sc_ipmp@phys-schost-1.
Note - Oracle Solaris Cluster does not support the use of the adapter name for netif.
Specifies an optional resource name of your choice.
# clresource show resource
Example 2-8 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).
# clressharedaddress create -g resource-group-1 -h schost-1 resource-1 # clresource show resource-1 === Resources === Resource: resource-1 Type: SUNW.SharedAddress:2 Type_version: 2 Group: resource-group-1 R_description: Resource_project_name: default Enabled{phys-schost-1}: False Enabled{phys-schost-2}: False Monitored{phys-schost-1}: True Monitored{phys-schost-2}: True
Next Steps
After you add a shared address resource, use the procedure How to Bring Resource Groups Online to enable the resource.
Troubleshooting
Adding a resource causes the Oracle Solaris Cluster software to validate the resource. If the validation fails, the clressharedaddress command prints an error message and exits. To determine why the validation failed, 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 clressharedaddress command.
See Also
The clressharedaddress(1CL) man page.
A failover application resource is an application resource that uses logical hostnames that you previously created in a failover resource group.
Note - Perform this procedure from any cluster node.
Before You Begin
Ensure that you have the following information.
The name of the failover resource group to 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
Note - This procedure also applies to proxy resources.
# clresource create -g resource-group -t resource-type \ [-p "extension-property[{node-specifier}]"=value, …] [-p standard-property=value, …] resource
Specifies the name of a failover resource group. This resource group must already exist.
Specifies the name of the resource type for the resource.
Specifies a comma-separated list of extension properties that you are setting for the resource. The extension properties that you can set depend on the resource type. To determine which extension properties to set, see the documentation for the resource type.
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.
Specifies a comma-separated list of standard properties that you are setting for the resource. The standard properties that you can set depend on the resource type. To determine which standard properties to set, see the following man pages: rt_properties(5), cluster(1CL), rg_properties(5), r_properties(5), and property_attributes(5).
Specifies your choice of the name of the resource to add.
The resource is created in the enabled state.
# clresource show resource
Example 2-9 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.
# clresource create -g resource-group-1 -t resource-type-1 \ -p Resource_dependencies=schost-1,schost2 resource-1 \ # clresource show resource-1 === Resources === Resource: resource-1 Type: resource-type-1 Type_version: Group: resource-group-1 R_description: Resource_project_name: default Enabled{phys-schost-1}: False Enabled{phys-schost-2}: False Monitored{phys-schost-1}: True Monitored{phys-schost-2}: True
Next Steps
After you add a failover application resource, use the procedure How to Bring Resource Groups Online to enable the resource.
Troubleshooting
Adding a resource causes the Oracle Solaris Cluster software to validate the resource. If the validation fails, the clresource command prints an error message and exits. To determine why the validation failed, 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 clresource command.
See Also
The clresource(1CL) man page.
A scalable application resource is an application resource that uses the network load balancing features of Oracle Solaris Cluster software. The scalable application resource is in a multi-mastered resource group and has a dependency on one or more shared-address resources. The shared-address resources are in a failover resource group.
Note - Perform this procedure from any cluster node.
Before You Begin
Ensure that you have the following information.
The name of the scalable resource group to 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
Note - This procedure also applies to proxy resources.
# clresource create -S -g resource-group -t resource-type \ -p Resource_dependencies=network-resource[,network-resource...] \ -p Scalable=True [-p "extension-property[{node-specifier}]"=value, …] [-p standard-property=value, …] resource
Specifies that the resource group is to be multi-mastered. If the -p Maximum_primaries and -p Desired_primaries options are omitted, both properties are set to the number of nodes in the resource group's node list.
Specifies the name of a scalable service resource group that you previously created.
Specifies the name of the resource type for this resource.
Specifies the list of network resources (shared addresses) on which this resource depends.
Specifies that this resource uses the network load balancing feature of Oracle Solaris Cluster software.
Specifies a comma-separated list of extension properties that you are setting for the resource. The extension properties that you can set depend on the resource type. To determine which extension properties to set, see the documentation for the resource type.
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.
Specifies a comma-separated list of standard properties that you are setting for the resource. The standard properties that you can set depend on the resource type. For scalable services, you typically set the Port_list, Load_balancing_weights, and Load_balancing_policy properties. To determine which standard properties to set, see the following man pages: cluster(1CL), rt_properties(5), rg_properties(5), r_properties(5), and property_attributes(5).
Specifies your choice of the name of the resource to add.
The resource is created in the enabled state.
# clresource show resource
Example 2-10 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.
# clresource create -S -g resource-group-1 -t resource-type-1 \ -p Resource_dependencies=schost-1,schost-2 resource-1 \ -p Scalable=True # clresource show resource-1 === Resources === Resource: resource-1 Type: resource-type-1 Type_version: Group: resource-group-1 R_description: Resource_project_name: default Enabled{phys-schost-1}: False Enabled{phys-schost-2}: False Monitored{phys-schost-1}: True Monitored{phys-schost-2}: True
Next Steps
After you add a scalable application resource, follow the procedure How to Bring Resource Groups Online to enable the resource.
Troubleshooting
Adding a resource causes the Oracle Solaris Cluster software to validate the resource. If the validation fails, the clresource command prints an error message and exits. To determine why the validation failed, 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 clresource command.
See Also
The clresource(1CL) man page.