HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 322

where certain application-specific actions must be taken before the failback can occur. For more information on the interaction between the Timeout and Failure Severity attribute and the virtual host failback policy, see Virtual hosts and failover, page 309. To set the Timeout and Failure Severity attribute from the command line, use this option: --probeSeverity nofailover|autorecover|noautorecover Service priority The service priority is used by HP Scalable NAS when it fails over services. Service priorities are natural numbers, with 0 (zero) representing the highest priority and higher numbers representing lower priorities. If multiple failures prevent HP Scalable NAS from placing a virtual host on a server where all of its associated services are available, HP Scalable NAS next looks for a server where the associated service with the highest priority is available. By default, all service monitors have a priority of 0. To set the Service Priority from the command line, use this option: --priority Probe type Service monitors can be configured to be either single-probe or multi-probe. A multi-probe monitor performs the probe function on each node where the monitor is configured, regardless of whether the monitor instance is active or inactive. This is the default for the built-in monitors. Single-probe monitors perform the probe function only on the node where the monitor instance is active. This type of configuration is useful for applications such as databases that are not cluster-aware and should be run on only one node at a time. The monitor instance is activated on the node where the associated virtual host is activated, and the probe takes place on that node. The monitor instances on other nodes are marked as "standby" on the Management Console. If the virtual host fails over to a backup node, the monitor instance on the original node becomes inactive and the probe is no longer run on that node. HP Scalable NAS activates the virtual host on the new node, which causes the monitor instance on that node to change status from "standby" to "active." The monitor then begins probing on that node and the Start script starts the application. If the monitor instance cannot be activated on the new node, the virtual host will fail over to another backup node if possible. 322 Configure service monitors