Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

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 clresourcegroup(8CL) man page 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

You can also use the Oracle Solaris Cluster Manager browser interface to disable a resource and move a resource group into the unmanaged state. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Administering an Oracle Solaris Cluster 4.4 Configuration.


Note -  When a shared address resource is disabled, the resource might still be able to respond to ping commands from some hosts. To ensure that a disabled shared address resource cannot respond to ping commands, you must bring the resource's resource group to the UNMANAGED state. See the ping(8) man page for more information.

Before You Begin

Ensure that you have the following information.

  • The name of each resource 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, type:

# clresourcegroup show -v
  1. On any cluster member, assume the root role that provides solaris.cluster.admin RBAC authorization.
  2. Disable all resources in the resource group.
    # clresource disable [-n nodelist] -g resource-group +
    –n nodelist

    Specifies a comma-separated, ordered list of nodes on which to disable the resource.

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


    Note -  If you specify more than one node with the –n option, you can specify only one resource.
  3. Switch the resource group offline.
    # clresourcegroup offline resource-group
    resource-group

    Specifies the name of the resource group to take offline.

  4. Move the resource group into the UNMANAGED state.
    # clresourcegroup unmanage resource-group
    resource-group

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

  5. Verify that the resources are disabled and that the resource group is in the UNMANAGED state.
    # clresourcegroup show resource-group
Example 21  Disabling a Resource and Moving Its 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.

# clresource disable resource-1
# clresourcegroup offline resource-group-1
# clresourcegroup unmanage resource-group-1
# clresourcegroup show resource-group-1

=== Resource Groups and Resources ===

Resource Group:                                 resource-group-1
RG_description:                                 <NULL>
RG_mode:                                        Failover
RG_state:                                       Unmanaged
Failback:                                       False
Nodelist:                                       phys-schost-1 phys-schost-2

--- Resources for Group resource-group-1 ---

Resource:                                      resource-1
Type:                                          SUNW.LogicalHostname: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

See Also