Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019

How to Add a Shared Address Resource to a Resource Group (CLI)

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.

  1. On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
  2. Add the shared address resource to the resource group.
    # clressharedaddress create -g resource-group -h hostnamelist,… \
    [-X auxnodelist] [-N netiflist] resource
    –g resource-group

    Specifies the resource group name.

    –h hostnamelist,…

    Specifies a comma-separated list of shared address hostnames.

    –X auxnodelist

    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.

    –N netiflist

    Specifies an optional, comma-separated list that identifies the PNM objects that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as a PNM object 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.

  3. Verify that the shared address resource has been added and validated.
    # clresource show resource
Example 11  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
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.


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