Service group attributes lists the service group attributes.
Number of resources in a service group that are active (online or waiting to go online). When the number drops to zero, the service group is considered offline. | |
List of operating system user account groups that have administrative privileges on the service group. | |
List of VCS users with privileges to administer the group. Note A Group Administrator can perform all operations related to a specific service group, but cannot perform generic cluster operations. | |
Indicates whether or not the local cluster is allowed to bring the service group online. If set to 0, it is not, if set to 1, it is. Only one cluster can have this attribute set to 1 for a specific global group. | |
Indicates that VCS does not know the status of a service group (or specified system for parallel service groups). This can occur because the group is not probed (on specified system for parallel groups) in the SystemList attribute. Or the VCS engine is not running on a node designated in the SystemList attribute, but the node is visible. When VCS does not know the status of a service group on a node but you want VCS to consider the service group enabled, perform this command to change the AutoDisabled value to 0.
This command instructs VCS that even though VCS has marked the service group auto-disabled, you are sure that the service group is not online on sys1. For failover service groups, this is important because the service groups now can be brought online on remaining nodes. | |
Indicates whether VCS initiates an automatic failover if the service group faults. The attribute can take the following values:
See "Controlling failover on service group or system faults" on page 365. | |
Restarts a service group after a faulted persistent resource becomes online. See About service group dependencies. Note This attribute applies only to service groups containing persistent resources. | |
Designates whether a service group is automatically started when VCS is started. | |
Indicates whether to initiate bringing a service group online if the group is probed and discovered to be in a partial state when VCS is started. | |
List of systems on which, under specific conditions, the service group will be started with VCS (usually at system boot). For example, if a system is a member of a failover service group's AutoStartList attribute, and if the service group is not already running on another system in the cluster, the group is brought online when the system is started. VCS uses the AutoStartPolicy attribute to determine the system on which to bring the service group online. Note For the service group to start, AutoStart must be enabled and Frozen must be 0. Also, beginning with 1.3.0, you must define the SystemList attribute prior to setting this attribute. | |
Sets the policy VCS uses to determine on which system to bring a service group online if multiple systems are available. This attribute has three options: Order (default)—Systems are chosen in the order in which they are defined in the AutoStartList attribute. Load—Systems are chosen in the order of their capacity, as designated in the AvailableCapacity system attribute. System with the highest capacity is chosen first. Priority—Systems are chosen in the order of their priority in the SystemList attribute. Systems with the lowest priority is chosen first. | |
Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values: Manual—The group does not fail over to another cluster automatically. Auto—The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults. Connected—The group fails over automatically to another cluster only if it is unable to fail over within the local cluster. | |
Specifies the list of clusters on which the service group is configured to run. | |
Specifies if you can use the service group with the container. Assign the following values to the ContainerInfo attribute: | |
Indicates whether HAD defers the auto-start of a global group in local cluster in case the global cluster is not fully connected. | |
Indicates if a service group can be failed over or brought online. The attribute can have global or local scope. If you define local (system-specific) scope for this attribute, VCS prevents the service group from coming online on specified systems that have a value of 0 for the attribute. You can use this attribute to prevent failovers on a system when performing maintenance on the system. | |
Indicates if VCS initiates an automatic failover when user issues | |
Indicates the node ID from which the service group is being evacuated. | |
Sets the policy VCS uses to determine which system a group fails over to if multiple systems exist. This attribute can take the following values: Priority—The system defined as the lowest priority in the SystemList attribute is chosen. Load—The system defined with the least value in the system's Load attribute is chosen. RoundRobin—Systems are chosen according to how many active service groups they are hosting. The system with the least number of active service groups is chosen first. | |
Specifies if VCS should propagate the fault up to parent resources and take the entire service group offline when a resource faults. The value 1 indicates that when a resource faults, VCS fails over the service group, if the group's AutoFailOver attribute is set to 1. If The value 0 indicates that when a resource faults, VCS does not take other resources offline, regardless of the value of the Critical attribute. The service group does not fail over on resource fault. | |
Indicates the system name from which the service group is failing over. This attribute is specified when service group failover is a direct consequence of the group event, such as a resource fault within the group or a group switch. | |
Disables all actions, including autostart, online and offline, and failover, except for monitor actions performed by agents. (This convention is observed by all agents supplied with VCS.) | |
VCS sends email notification to the person designated in this attribute when an event occurs related to the service group. VCS also logs the owner name when an event occurs. Make sure to set the severity level at which you want notifications to the group owner to at least one recipient defined in the SmtpRecipients attribute of the NotifierMngr agent. For example, to send notifications at the Information severity level to user groupadmin@yourcompany.com:
| |
List of operating system user accounts that have Guest privileges on the service group. | |
Indicates whether to keep service groups online or offline. VCS sets this attribute to 1 if an attempt has been made to bring the service group online. For failover groups, VCS sets this attribute to 0 when the group is taken offline. For parallel groups, it is set to 0 for the system when the group is taken offline or when the group faults and can fail over to another system. VCS sets this attribute to 2 for failover groups if VCS attempts to autostart a service group; for example, attempting to bring a service group online on a system from AutoStartList. | |
Indicates the time when service group was last brought online. | |
Integer value expressing total system load this group will put on a system. For example, the administrator may assign a value of 100 to a large production SQL and 15 to a Web server. | |
Specifies if VCS manages resource failures within the service group by calling the Clean function for the resources. This attribute can take the following values. NONE—VCS does not call the Clean function for any resource in the group. User intervention is required to handle resource faults. See"Controlling Clean behavior on resource faults" on page 368. | |
Indicates if manual operations are allowed on the service group. | |
Indicates the system from which the service group is migrating. This attribute is specified when group failover is an indirect consequence (in situations such as a system shutdown or another group faults and is linked to this group). | |
Indicates the number of attempts made to bring a service group online. This attribute is used only if the attribute OnlineRetryLimit is set for the service group. | |
When a node or a service group is frozen, the OnlineAtUnfreeze attribute specifies how an offline service group reacts after it or a node is unfrozen. | |
Indicates the interval, in seconds, during which a service group that has successfully restarted on the same system and faults again should be failed over, even if the attribute OnlineRetryLimit is non-zero. This prevents a group from continuously faulting and restarting on the same system. | |
If non-zero, specifies the number of times the VCS engine tries to restart a faulted service group on the same system on which the group faulted, before it gives up and tries to fail over the group to another system. | |
List of operating system user groups that have Operator privileges on the service group. | |
List of VCS users with privileges to operate the group. A Group Operator can only perform online/offline, and temporary freeze/unfreeze operations pertaining to a specific group. | |
Indicates if service group is failover (0), parallel (1), or hybrid(2). | |
Number of resources in path not yet taken offline. When this number drops to zero, the engine may take the entire service group offline if critical fault has occurred. | |
Indicates that the VCS engine should not online a service group in response to a manual group online, group autostart, or group failover. The engine should instead run the PreOnline trigger. You can set a local (per-system) value for this attribute to control the firing of PreOnline triggers on each node in the cluster. This attribute is strictly a per system attribute, then you must set the value for each system. | |
Indicates that VCS engine invoked the preonline script; however, the script has not yet returned with group online. | |
Defines the maximum amount of time in seconds the preonline script takes to run the command | |
An unordered set of name=value pairs denoting specific resources required by a service group. If prerequisites are not met, the group cannot go online. The format for Prerequisites is: Prerequisites() = {Name=Value, name2=value2}. Names used in setting Prerequisites are arbitrary and not obtained from the system. Coordinate name=value pairs listed in Prerequisites with the same name=value pairs in Limits(). See "About system limits and service group prerequisites" on page 391. | |
Indicates whether VCS engine should invoke PreSwitch actions in response to a manual service group switch operation.
Note
The engine does not invoke the PreSwitch action during a group fault or when you use This attribute must be defined in the global group definition on the remote cluster. This attribute takes the following values: 0—VCS engine switches the service group normally. 1—VCS engine switches the service group based on the output of PreSwitch action of the resources. If you set the value as 1, the VCS engine looks for any resource in the service group that supports PreSwitch action. If the action is not defined for any resource, the VCS engine switches a service group normally. If the action is defined for one or more resources, then the VCS engine invokes PreSwitch action for those resources. If all the actions succeed, the engine switches the service group. If any of the actions fail, the engine aborts the switch operation. The engine invokes the PreSwitch action in parallel and waits for all the actions to complete to decide whether to perform a switch operation. The VCS engine reports the action's output to the engine log. The PreSwitch action does not change the configuration or the cluster state. | |
Indicates that the VCS engine invoked the agent's PreSwitch action; however, the action is not yet complete. | |
Indicates whether or not the resource dependency tree is written to the configuration file. The value 1 indicates the tress is written. Note For very large configurations, the time taken to print the tree and to dump the configuration is high. | |
Enables users to designate and prioritize the service group. VCS does not interpret the value; rather, this attribute enables the user to configure the priority of a service group and the sequence of actions required in response to a particular event. | |
Indicates whether all enabled resources in the group have been detected by their respective agents. | |
The number of resources that remain to be detected by the agent on each system. | |
Indicates VCS engine is responding to a failover event and is in the process of bringing the service group online or failing over the node. | |
File from which the configuration is read. Do not configure this attribute in main.cf. Make sure the path exists on all nodes before running a command that configures this attribute. Make sure the path exists on all nodes before configuring this attribute. | |
OFFLINE— All non-persistent resources are offline. ONLINE —All resources whose AutoStart attribute is equal to 1 are online. FAULTED—At least one critical resource in the group is faulted or is affected by a fault. PARTIAL—At least one, but not all, resources with Operations=OnOff is online, and not all AutoStart resources are online. STARTING—Group is attempting to go online. STOPPING— Group is attempting to go offline. A group state may be a combination of the multiple states described above. For example, OFFLINE | FAULTED, OFFLINE | STARTED, PARTIAL | FAULTED, PARTIAL | STARTING, PARTIAL | STOPPING, ONLINE | STOPPING | |
List of systems on which the service group is configured to run and their priorities. Lower numbers indicate a preference for the system as a failover target. Note You must define this attribute prior to setting the AutoStartList attribute. | |
Indicates the virtual sublists within the SystemList attribute that grant priority in failing over. Values are string/integer pairs. The string key is the name of a system in the SystemList attribute, and the integer is the number of the zone. Systems with the same zone number are members of the same zone. If a service group faults on one system in a zone, it is granted priority to fail over to another system within the same zone, despite the policy granted by the FailOverPolicy attribute. | |
Identifies special-purpose service groups created for specific VCS products. | |
Indicates the number of target systems on which the service group should be brought online. | |
Indicates if service groups can be brought online or taken offline on nodes in the cluster. Service groups cannot be brought online or taken offline if the value of the attribute is 1. | |
Indicates the node name to which the service is failing over. This attribute is specified when service group failover is a direct consequence of the group event, such as a resource fault within the group or a group switch. | |
Defines whether VCS invokes the resfault trigger when a resource faults. The value 0 indicates that VCS does not invoke the trigger. | |
Determines whether or not to invoke the resstatechange trigger if resource state changes. | |
Creates a dependency (via an ordered list) between resource types specified in the service group list, and all instances of the respective resource type. | |
VCS uses this attribute in the ClusterService group. Do not modify this attribute in the ClusterService group. | |