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 Multi-Master Proxy Resource Configuration

  1. On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
  2. Register the SMF proxy multi-master resource type.
    # clresourcetype register -f \
    /opt/SUNWscsmf/etc/SUNW.Proxy_SMF_multimaster SUNW.Proxy_SMF_multimaster
  3. Create the SMF multi-master resource group.
    # clresourcegroup create -S [-p Maximum_primaries=m] [-p Desired_primaries=n] \
    [-n node-zone-list] resource-group
    –S

    Specifies that the resource group is to be multi-mastered. If the –p Maximum_primaries and –p Desired_primaries options are omitted, both properties are set to the number of nodes in the resource group's node list.

    –p Maximum_primaries=m

    Specifies the maximum number of active primaries for this resource group.

    –p Desired_primaries=n

    Specifies the number of active primaries on which the resource group should attempt to start.

    –n nodelist

    Specifies a comma-separated, ordered list of nodes in which this resource group is to be available.

    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 scalable resource group to add. This name must begin with an ASCII character.

  4. Verify that the SMF proxy multi-master resource group has been created.
    # clresourcegroup show resource-group
  5. Add an SMF proxy multi-master resource to the resource group.
    # clresource create -g resource-group -t SUNW.Proxy_SMF_multimaster \
    -p Port_list=portnumber/protocol \
    -x Proxied_service_instances=/tmp/dns_svcs.txt
    –g resource-group

    Specifies the name of the SMF multi-master 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.

  6. Verify that the SMF proxy multi-master application resource has been added and validated.
    # clresource show resource
  7. Bring the multi-master 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 38  Registering an SMF Proxy Multi-Master Resource Type

The following example registers the SUNW.Proxy_SMF_multimaster resource type.

# clresourcetype register SUNW.Proxy_SMF_multimaster
# clresourcetype show SUNW.Proxy_SMF_multimaster

Resource Type:            SUNW.Proxy_SMF_multimaster
RT_description:           Resource type for proxying multimastered 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 39  Creating and Adding an SMF Proxy Multi-Master Application Resource to a Resource Group

This example shows the creation and addition of a multi-master proxy resource type SUN.Proxy_SMF_multimaster to a resource group resource-group-1.

# clresourcegroup create -S \
-p Maximum_primaries=2 \
-p Desired_primaries=2 \
-n phys-schost-1, phys-schost-2 resource-group-1
# clresourcegroup show resource-group-1

=== Resource Groups and Resources ===

Resource Group:                        resource-group-1
RG_description:                        <NULL>
RG_mode:                               multimastered
RG_state:                              Unmanaged
RG_project_name:                       default
RG_affinities:                         <NULL>
Auto_start_on_new_cluster:             True
Failback:                              False
Nodelist:                              phys-schost-1 phys-schost-2
Maximum_primaries:                       2
Desired_primaries:                       2
Implicit_network_dependencies:         True
Global_resources_used:                 <All>
Pingpong_interval:                       3600
Pathprefix:                            <NULL>
RG_System:                             False
Suspend_automatic_recovery:            False
# clresource create -g resource-group-1 -t SUNW.Proxy_SMF_multimaster \
-x proxied_service_instances=/var/tmp/svslist.txt resource-1
# clresource show resource-1

=== Resources ===

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