How to Change Resource Properties (GUI)

This procedure explains how to use the Oracle Solaris Cluster Manager GUI to change a resource's standard and extension properties. You can also use the GUI to create a resource.

1. Log in to Oracle Solaris Cluster Manager on your cluster.

   For log-in instructions, see How to Access Oracle Solaris Cluster Manager in Oracle Solaris Cluster System Administration Guide .

2. Click Resource Groups, click the name of resource group to which the resources belong, and click the resource you want to edit.
3. Click the Properties tab and click Edit.

   The resource properties are divided into four categories: extension, system, timeout, and per-node extension properties.

4. Select the editable property value you want to change and enter a new value.

   The extension properties vary for each resource, and some of the extension properties are defined by node. Some of these properties are editable in the GUI based on the value set for the tunable property for each of the properties in the RTR file. Some properties are edited inline and others are edited with a wizard. The following properties can be edited in the GUI:

   Property Type Name Description System Description Provides a description of this resource. RGM response to Start/Stop method failure Controls the failover behavior when a Start or Stop method fails: NONE – The RGM will not take any recovery action when a start or stop methods fails. SOFT – If a Start or Prenet_start method fails, the RGM relocates the resource to a different node. If a stop method (Monitor_Stop, Stop, or Postnet_Stop) fails, SOFT is the same as NONE. Hard – If a Start or Prenet_start method fails, the RGM relocates the resource to a different node. If a Stop method fails, the RGM reboots the node to force the resource group offline and might attempt to start the resource on another node. Strong Resource Dependencies Provides a list of resources in the same group or in different groups upon which this resource has a strong dependency. This resource cannot be started if the start of any resource in the list fails. Weak Resource Dependencies Provides a list of resources in the same group or in different groups upon which this resource has a weak dependency. A weak dependency determines the order of method calls within the group. Restart Resource Dependencies Provides a list of resources in the same group or in different groups upon which this resource has a restart dependency. Offline Restart Resource Dependencies Provides a list of resources in the same group or in different groups upon which this resource has an offline-restart dependency. Perform resource group evictions before initiating a switchover Determines whether the RGM attempts to perform resource group evictions before initiating a switchover of the resource group containing this resource. System properties used only for scalable services System Resource Group Determines whether certain actions, such as deleting a resource group, can be performed on this resource group. Description Provides a description of this resource. Available primary nodes Determines the nodes that can serve as primary nodes for this resource. The order of the nodes in the list indicates usage preference. Desired number of nodes for normal operation Determines the number of nodes where the resource group can run simultaneously during normal operation. Autostart on New Cluster Controls whether the RGM automatically starts the resource group when a new cluster is formed. Failback Indicates whether to recalculate the set of nodes where the resource group is online when the cluster membership changes. A recalculation can cause the RGM to bring the group offline on less preferred nodes and online the on more preferred nodes. Pingpong Interval Reflects the number of seconds used by the RGM to determine where to bring the resource group online in the event of a reconfiguration or a giveover. Resource group colocations Indicates the type of colocation you require for the resource group in relation to other resource groups on a node. If a resource group depends so strongly on a service in a second group that both services must run on the same node, the resource groups are collocated. Resource group dependencies Controls dependencies of one resource group on another group. Shared Storage Indicates whether cluster file systems are used by any resource in this resource group. Non-network-address resources depend on network resources Indicates whether the RGM should enforce implicit strong dependencies of non-network address resources on network address resources within the group. Path Prefix Reflects a directory in the cluster file system in which resources in the group can write essential administrative files. Oracle Solaris Project Name Reflects the Oracle Solaris Cluster associated with this project. Use this to apply Oracle Solaris resource management features to a data service. Monitoring Indicates if monitoring is enabled. Processor Set Determines the minimum number of processors in the processor set in which the resource group executes. Resource Group CPU Shares Determines the number of CPU shares and the size of the Processor Set associated with the resource group. Minimum CPU Reflects the minimum number of CPUs available in the default processor set. Priority Determines the order in which resource groups are assigned to master nodes. A higher priority indicates a more important service. Default is 500. Preemption Mode Determines the likelihood that a resource group will be preempted from a node by a higher-priority resource group because of node overload. A Has_Cost value means that preempting this resource group has a cost associated with it. A No_Cost value indicates that the cost of preempting this resource group is zero. A Never value indicates that the resource group cannot be displaced from its current master to satisfy load limits. Load Factors Enables automatic distribution of resource group load across nodes by setting load limits. Load factors correspond to how much of the load limit that the resource group consumes. Default value for each load factor is 0 and the maximum value is 1000. Timeout Thorough probe interval Reflects the number of seconds between invocations of a high-overhead fault probe of the resource. Number of restarts attempts after failure Determines the number of restart requests that have occurred on this resource within the past n seconds, where n in the value of the Time period during which restart attempts should be counted property. Time period during which restart attempts should be counted Sets the number of seconds in which to count attempts to restart a failed resource. Initialization method timeout Performs a one-time initialization of the resource when the resource becomes managed. Update method timeout Default is 300. Validate method timeout Default is 300. Monitor start method timeout Reflects the number of seconds after which the RGM concludes that an invocation of this method has failed. Default is 300. Monitor stop method timeout Reflects the number of seconds after which the RGM concludes that an invocation of this method has failed. Default is 300. Monitor check method timeout Reflects the number of seconds after which the RGM concludes that an invocation of this method has failed. Default is 300. Network interface pre-start method timeout Default is 300. Network interface post-stop method timeout Default is 300.

   For more detail on these properties, see the r_properties(5), rg_properties(5), and rt_properties(5) man pages.

5. Click Save.