SUNW.Proxy_SMF_multimaster, Proxy_SMF_multimaster - resource type for proxying multi-master SMF services
The SUNW.Proxy_SMF_multimaster resource type represents the proxy for multi-master Service Management Facility (SMF) services.
Standard properties and extension properties that are defined for the SUNW.proxysmfmultimaster resource type are described in the subsections that follow. To set these properties for an instance of the SUNW.Proxy_SMF_multimaster resource type, use the clresource command (clresource(8CL)).
See r_properties(7) for a description of the following resource properties.
Default: 3600
Minimum: 60
Default: 3600
Minimum: 60
Default: 3600
Minimum: 60
Default: 3600
Minimum: 60
Default: 3600
Minimum: 60
Default: 3600
Minimum: 60
Default: SOFT
Tunable: Anytime
Default: ""
Tunable: Anytime
Default: 2
Minimum: 0
Maximum: 3
Tunable: Anytime
Default: 300
Maximum: 3600
Tunable: Anytime
Default: 60
Tunable: Anytime
Number of PMF restarts allowed for the fault monitor.
Default: 2
Tunable: Any time
Time window (in minutes) for fault monitor restarts.
Default: 2
Tunable: Any time
Name of the command to be run by the SMF proxy probe.
Default: " "
Tunable: When disabled
Timeout value for the probe (in secons).
Default: 30
Minimum: 2
Tunable: Any time
Specifies information about the SMF services to be proxied by the resource. Its value is either one or more fmri names for the SMF services to proxy or the path to a file that contains all the proxied SMF services.
The preferred method to specify this property is by direct use in the clresource command. If using the fmri name, use the following syntax:
-x Proxied_service_instances=svc:service-name
You can specify multiple SMF services in a comma-delimited list. For example:
-x Proxied_service_instances=svc:/network/ntp:default,svc:/network/dhcp-server:default
The use of a file to provide the Proxied_service_instances values is deprecated but still supported. When specifying the property in a file, the property's value is the path to a file that contains all the proxied SMF services. Each line in the file is dedicated to one SMF service and specifies svc fmri and the path to the corresponding service manifest file. For example, if the resource has to manage two services, restarter_svc_test_1:default and restarter_svc_test_2:default, the file must include the following two lines:
<svc:/system/cluster/restarter_svc_test_1:default>, </var/svc/manifest/system/cluster/restarter_svc_test_1.xml> <svc:/system/cluster/restarter_svc_test_2:default>, </var/svc/manifest/system/cluster/restarter_svc_test_2.xml>
Default: ""
Tunable: When disabled
This example shows how to register the SUNW.Proxy_SMF_multimaster resource type, create a resource group for the application, create the multi-master application resource, manage the resource group, and enable resources.
Register the resource type:
# clresourcetype -f <path-to-rtrfile> SUNW.Proxy_SMF_multimaster
Create a resource group called rg1 for the application:
# clresourcegroup create rg1
Create the failover application resource called mymultimasterres:
# clresource create -t SUNW.Proxy_SMF_multimaster -g rg1 \ -x proxied_service_instances="/usr/local/app/svc" mymultimasterres
where /usr/local/app/svc is a text file.
Manage the resource group rg1:
# clresourcegroup manage rg1
Enable the mymultimasterres resource:
# clresource enable mymultimasterres
Use the following command to check the status of the application:
# clresource status
attributes(7), r_properties(7), clresource(8CL), clresourcegroup(8CL), clresourcetype(8CL), scha_resource_get(8HA), pmfadm(8)
Planning and Administering Data Services for Oracle Solaris Cluster 4.4