JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Services Planning and Administration Guide
search filter icon
search icon

Document Information

Preface

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

Registering a Resource Type

How to Register a Resource Type

Upgrading 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

Downgrading a Resource Type

How to Downgrade a Resource to an Older Version of Its Resource Type

Creating a Resource Group

How to Create a Failover Resource Group

How to Create a Scalable Resource Group

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 Online Resource Groups

How to Bring Online Resource Groups

Enabling a Resource

How to Enable a Resource

Quiescing Resource Groups

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

Removing Resource Types

How to Remove a Resource Type

Removing Resource Groups

How to Remove a Resource Group

Removing Resources

How to Remove a Resource

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

Migrating the Application From a Global-Cluster Voting Node to a Global-Cluster Non-Voting Node

How to Migrate the Application From a Global-Cluster Voting Node to a Global-Cluster Non-Voting Node

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 Set Up the HAStoragePlus Resource Type to Make File Systems Highly Available Other Than Solaris ZFS

How to Set Up the HAStoragePlus Resource Type to Make a Local Solaris ZFS Highly Available

How to Delete an HAStoragePlus Resource That Makes a Local Solaris ZFS Highly Available

Upgrading From HAStorage to HAStoragePlus

How to Upgrade From HAStorage to HAStoragePlus When Using Device Groups or CFS

How to Upgrade From HAStorage With CFS to HAStoragePlus With Highly Available Local File System

Modifying Online the Resource for a Highly Available 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

How to Recover From a Fault After Modifying the FileSystemMountPoints Property of an 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

Resource Group Affinities

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

Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources

How to Replicate Configuration Data on a Cluster Without Configured Resource Groups, Resource Types, and Resources

How to Upgrade Configuration Data on a Cluster With Configured Resource Groups, Resource Types, and Resources

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

Specifying the Failover Behavior of a Resource

Denying Cluster Services For a Selected Non-Global Zone

How to Deny Cluster Services For a Non-Global Zone

How to Allow Cluster Services For a Non-Global Zone

A.  Standard Properties

B.  Legal RGM Names and Values

C.  Data Service Configuration Worksheets and Examples

Index

Clearing the Start_failed Resource State

The Start_failed resource state indicates that a Start or Prenet_start method failed or timed out on a resource, but its resource group came online anyway. The resource group comes online even though the resource has been placed in a faulted state and might not be providing service. This state can occur if the resource's Failover_mode property is set to None or to another value that prevents the failover of the resource group.

Unlike the Stop_failed resource state, the Start_failed resource state does not prevent you or the Oracle Solaris Cluster software from performing actions on the resource group. You need only to execute a command that restarts the resource.

Use any one of the following procedures to clear this condition.

How to Clear a Start_failed Resource State by Switching Over a Resource Group


Note - Perform this procedure from any cluster node.


Before You Begin

Ensure that the following conditions are met:

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
  2. Switch the resource group to the new node.
    # clresourcegroup switch [-n node-zone-list] resource-group
    -n node-zone-list

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

    This list is optional. If you omit this list, the resource group is switched on all nodes in the resource group's node list.

    resource-group

    Specifies the name of the resource group to switch.


    Note - If any resource group that you are switching declares a strong affinity for other resource groups, the attempt to switch might fail or be delegated. For more information, see Distributing Online Resource Groups Among Cluster Nodes.


  3. Verify that the resource group has been switched to the new node and that the Start_failed resource state is cleared.
    # clresourcegroup status

    The output from this command indicates the state of the resource and the resource group that has been switched over.

Example 2-23 Clearing a Start_failed Resource State by Switching Over a Resource Group

This example shows how to clear a Start_failed resource state that has occurred on the rscon resource in the resource-group-1 resource group. The command clears this condition by switching the resource group to the global cluster voting node phys-schost-2.

  1. To verify that the resource is in the Start_failed resource state on phys-schost-1, the following command is run:

    # clresource status
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Faulted         Faulted
                         phys-schost-2       Offline          Offline
    
     hastor              phys-schost-1       Online          Online
                         phys-schost-2       Offline         Offline
  2. To perform the switch, the following command is run:

    # clresourcegroup switch -n phys-schost-2 resource-group-1
  3. To verify that the resource group is switched to be online on phys-schost-2 and that the Start_failed resource status is cleared, the following command is run:

    # clresource status
    
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Offline         Offline
                         phys-schost-2       Online          Online
    
     hastor              phys-schost-1       Online          Online
                         phys-schost-2       Offline         Offline

See Also

The clresourcegroup(1CL) man page.

How to Clear a Start_failed Resource State by Restarting a Resource Group


Note - Perform this procedure from any cluster node.


Before You Begin

Ensure that the following conditions are met:

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
  2. Restart the resource group.
    # clresourcegroup restart -n node resource-group
    -n node

    Specifies the name of the node on which the resource group is to be restarted. This resource group is switched offline on all of the other nodes.

    resource-group

    Specifies the name of the resource group to restart.

  3. Verify that the resource group has been restarted on the new node and that the Start_failed resource state is cleared.
    # clresourcegroup status

    The output from this command indicates the state of the resource and the resource group that has been restarted.

Example 2-24 Clearing a Start_failed Resource State by Restarting a Resource Group

This example shows how to clear a Start_failed resource state that has occurred on the rscon resource in the resource-group-1 resource group. The command clears this condition by restarting the resource group on the global-cluster voting node phys-schost-1.

  1. To verify that the resource is in the Start_failed resource state on phys-schost-1, the following command is run:

    # clresource status
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Faulted         Faulted
                         phys-schost-2       Offline          Offline
    
     hastor              phys-schost-1       Online          Online
                         phys-schost-2       Offline         Offline
  2. To restart the resource, the following command is run:

    # clresourcegroup restart -n phys-schost-1 –g resource-group-1
  3. To verify that the resource group is restarted on phys-schost-1 and that the Start_failed resource status is cleared, the following command is run:

    # clresource status
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Offline         Offline
     rscon               phys-schost-2       Online          Online
    
     hastor              phys-schost-1       Online          Online
     hastor              phys-schost-2       Offline         Offline

See Also

The clresourcegroup(1CL) man page.

How to Clear a Start_failed Resource State by Disabling and Enabling a Resource


Note - Perform this procedure from any cluster node.


Before You Begin

Ensure that you have the name of the resource that you are disabling and enabling.

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
  2. Disable and then enable the resource.
    # clresource disable resource
    # clresource enable resource
    resource

    Specifies the name of the resource.

  3. Verify that the resource has been disabled and enabled and that the Start_failed resource state is cleared.
    # clresource status

    The output from this command indicates the state of the resource that has been disabled and re-enabled.

Example 2-25 Clearing a Start_failed Resource State by Disabling and Enabling a Resource

This example shows how to clear a Start_failed resource state that has occurred on the rscon resource by disabling and enabling the resource.

  1. To verify that the resource is in the Start_failed resource state, the following command is run:

    # clresource status
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Faulted         Faulted
                         phys-schost-2       Offline          Offline
    
     hastor              phys-schost-1       Online          Online
                         phys-schost-2       Offline         Offline
  2. To disable and re-enable the resource, the following commands are run:

    # clresource disable rscon
    # clresource enable rscon
  3. To verify that the resource is re-enabled and that the Start_failed resource status is cleared, the following command is run:

    # clresource status
    
    
    === Cluster Resources ===
    
    Resource Name             Node Name       Status        Message
    --------------            ----------      -------        -------
     rscon               phys-schost-1       Online         Online
                         phys-schost-2       Offline        Offline
    
     hastor              phys-schost-1       Online          Online
                         phys-schost-2       Offline         Offline

See Also

The clresource(1CL) man page.