Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

Encapsulating an SMF Service Into a Failover Proxy Resource Configuration

For information about failover configuration, see Creating a Resource Group.


Note -  Perform this procedure from any cluster node.
  1. On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
  2. Register the proxy SMF failover resource type.
    # clresourcetype register -f \
    /opt/SUNWscsmf/etc/SUNW.Proxy_SMF_failover SUNW.Proxy_SMF_failover
  3. Verify that the proxy resource type has been registered.
    # clresourcetype show 
  4. Create the SMF failover resource group.
    # clresourcegroup create [-n node-zone-list] resource-group
    –n nodelist

    Specifies a comma-separated, ordered list of nodes that can master this resource group.

    This list is optional. If you omit this list, the resource group is configured on all cluster nodes.

    resource-group

    Specifies your choice of the name of the resource group to add. This name must begin with an ASCII character.

  5. Verify that the SMF resource group has been created.
    # clresourcegroup status resource-group
  6. Add an SMF failover application resource to the resource group.
    # clresource create -g resource-group -t SUNW.Proxy_SMF_failover \
    -p Port_list=portnumber/protocol \
    -x Proxied_service_instances=/tmp/dns_svcs.txt
    –g resource-group

    Specifies the name of the SMF failover resource group that you previously created.

    –p Port_list=portnumber/protocol

    Specifies the port number the instance will use to listen for activity. The protocol can be either tcp or udp.

    –p Proxied_service_instances

    Specifies the path to the file you created that specifies the mapping of SMF services and their corresponding manifests for the SMF services to be proxied. In the example above, /tmp/dns_svcs.txt is the path to the text file.

    The resource is created in the enabled state.

  7. Verify that the SMF failover application resource has been added and validated.
    # clresource show resource
  8. Bring the failover resource group online.
    # clresourcegroup online -M resource-group

    Note -  If you use the clresource status command to view the state of the SMF proxy resource type, the status is displayed as online but not monitored. This is not an error message. The SMF proxy resource is enabled and running and this status message is displayed because there is no monitoring support provided for the resources of SMF proxy resource type.
Example 36  Registering an SMF Proxy Failover Resource Type

The following example registers the SUNW.Proxy_SMF_failover resource type.

# clresourcetype register SUNW.Proxy_SMF_failover
# clresourcetype show SUNW.Proxy_SMF_failover

Resource Type:              SUNW.Proxy_SMF_failover
RT_description:             Resource type for proxying failover SMF services
RT_version:                 2.0
API_version:                7
RT_basedir:                 /opt/SUNWscsmf/bin
Single_instance:            False
Proxy:                      False
Init_nodes:                 All potential masters
Installed_nodes:            <All>
Failover:                   True
Pkglist:                    <NULL>
RT_system:                  False
Global_zone:                False
Example 37  Adding an SMF Proxy Failover Application Resource to a Resource Group

This example shows the addition of a proxy resource type, SUN.Proxy_SMF_failover to a resource group resource-group-1.

# clresource create -g resource-group-1 -t SUNW.Proxy_SMF_failover \
-x proxied_service_instances=/var/tmp/svslist.txt resource-1
# clresource show resource-1

=== Resources ===

Resource:                                  resource-1
Type:                                      SUNW.Proxy_SMF_failover
Type_version:                              2.0
Group:                                     resource-group-1
R_description:
Resource_project_name:                     default
Enabled{phys-schost-1}:                    True
Monitored{phys-schost-1}:                  True