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

When a shared address resource is disabled, the resource might still be able to respond to ping(1M) 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.

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, become superuser or assume a role that provides solaris.cluster.admin RBAC authorization.

2. Disable all resources in the resource group.

   # clresource disable [-n node-zone-list] -g resource-group +

   -n node-zone-list

   Specifies a comma-separated, ordered list of nodes or zones on which to disable the resource. If you specify a zone, 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 non-global zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

   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 or zone 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.

   # clrsourcegroup show resource-group

Example 2–18 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

The following man pages:

• clresource(1CL)

• clresourcegroup(1CL)