3.1.2 Matrix Server Administration Guide

Chapter 13: Configure Device Monitors 181

The Probe Severity setting works with the virtual host policy (either

AUTOFAILBACK or NOFAILBACK) to determine what happens when a

monitored device fails.

The default policies (

AUTOFAILBACK for the virtual host and

AUTORECOVERY for the device monitor) cause ClusterPulse to fail over

the associated virtual hosts to a backup network interface on another

server when the monitor probe fails. When the device is restored,

ClusterPulse fails back the virtual hosts to the network interface on the

original server.

You can use the Probe Severity attribute to change this behavior. There

are three settings for Probe Severity:

NOFAILOVER, AUTORECOVER, and

NOAUTORECOVER.

NOFAILOVER. When the monitor probe fails, ClusterPulse does not fail

over to a backup network interface. This option is useful when the

monitored resource is not critical, but is important enough that you want

to keep a record of its health.

AUTORECOVER. This is the default. The virtual host fails over when a

monitor probe fails. When device access is recovered on the original

node, failback occurs according to the virtual host’s failback policy.

NOAUTORECOVER. The virtual host fails over when a monitor probe

fails and the monitor is disabled on the original node, preventing

automatic failback. When the monitor is reenabled, failback occurs

according to the virtual host’s failback policy.

The

NOAUTORECOVER option is useful when integrating Matrix Server

with a custom application where certain application-specific actions must

be taken before failback can occur.

For more information on the interaction between the Probe Severity

attribute and the virtual host failback policy, see “Virtual Hosts and

Failover” on page 154.

To set the Probe Severity from the command line, use this option:

--probeSeverity nofailover|autorecover|noautorecover