PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System)

6.6.5 Attributes

Resource attributes

Attribute	Outline
InParallel	Normally, in Online or Offline processing, the programs for starting or stopping all the monitored programs run sequentially. If this attribute is set to yes, the programs run simultaneously. The default value is No (the programs are processed sequentially).
NeedAll	If this attribute is set to No, Online processing succeeds if there's at least one monitored Online program. If the attribute is set to "Yes", all defined monitoring programs must be Online to bring userApplicaiton Online. The default value differs according to the resource. Cmdline: No Fsystem: Yes Takeover network: Yes Process monitoring: No
Timeout SCRIPTTIMEOUT	Sets the timeout duration (seconds) for resource start and stop processing. The default value differs according to the resource. Fsystem: 180 Gds: 1800 Gls: 60 Takeover network: 60 Procedure: 1800
AutoRecover	If this attribute is set to Yes, RMS attempts to recover the faulted resources to prevent userApplication from switching to other host. This attempt is executed only once. If this attribute is set to No, userApplication switches to other host in the event of a failure according to the AutoSwitchOver setting. The default value for Gds resources is "No."

userApplication attributes

Attribute	Outline
AutoStartUp	If this attribute is set to "Yes," the userApplication starts automatically when RMS is started. The default value is "No," and automatic userApplication startup is disabled.
AutoSwitchOver	If a failure occurs in a userApplication, this attribute allows userApplication to be switched over automatically. The switchover condition can be selected from the following: No Automatic switchover by RMS is not executed. The cluster application must be switched over manually by the administrator. HostFailure If a failure occurs in the host (SysNode). ResourceFailure If a failure occurs in a resource. ShutDown If RMS shuts down. Combinations of the above values can be selected. Example) HostFailure|ResourceFailure HostFailure|ShutDown ResourceFailure|ShutDown HostFailure|ResourceFailure|ShutDown The default value is "No."
PersistentFault	If this attribute is set to 1, the Faulted state of userApplication remains the same even after RMS restart.
OnlinePriority	If this attribute is set to 1, when all clusters are stopped and restarted, RMS starts userApplication in the host that was Online last. The default value is "0," and after RMS is restarted, userApplication goes Online in the node with the highest priority. The priority is determined by the node setup sequence that was specified in "SysNode Setup" when userApplication was created.
ShutdownPriority	This attribute is a weight coefficient that is assigned to userApplication. If a failure occurs in a cluster interconnect, this attribute also becomes one of the factors in determining which node has the highest priority to survive. The higher value, the higher is the priority of that userApplication. Select a value from the range of 1 to 20. The default value is "NONE," which means no weight coefficient is assigned. The node in which this userApplication is Online may be stopped because it does not contain elements that have a high priority to survive. For details on ShutdownPriority, see "PRIMECLUSTER Reliant Monitor Service (RMS) with Wizard Tools Configuration and Administration Guide."
StandbyTransitions	Set up the condition whereby a standby resource will make the transition to the Standby state. You can select any of the following for the setup value: NONE Select this when you do not wish to set a condition for Standby state transition. ClearFaultRequest Select this when you want to clear the userApplication Faulted state and make a state transition to Offline. StartUp If AutoStartUp is set to "No," the operating userAppoication will be also changed to Standby state when you start up RMS. SwitchRequest The userApplication is switched to another node. You can select the following values in combination with the above values: Example) ClearFaultRequest|StartUp ClearFaultRequest|SwitchRequest StartUp|SwitchRequest ClearFaultRequest|StartUp|SwitchRequest The default is "NONE." Note) When you use the redundant line control function of GLS, set up the following value to enable monitoring of Gls resource state on the standby node: "ClearFaultRequest|StartUp|SwitchRequest"
HaltFlag	If this attribute is set to "Yes," the node is forcibly shut down when another failure occurs (double failure) during fault processing. In this case, RMS forcibly stops the node and completes failover of userApplication even if a resource failure occurs during failover processing. The default value is "No," and node elimination is not executed. Accordingly, userApplication does not execute failover. For details on HaltFlag (Halt attribute), see "PRIMECLUSTER Reliant Monitor Service (RMS) with Wizard Tools Configuration and Administration Guide."