HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)
Table Of Contents
- Contents
- HP Technical Support
- Quick Start Checklist
- Introduction to HP Clustered File System
- Cluster Administration
- Administrative Considerations and Restrictions
- Tested Configuration Limits
- Volume and Filesystem Limits
- User Authentication
- Start the Management Console
- Cluster Management Applications
- The HP CFS Management Console
- View Installed Software
- Start HP Clustered File System
- Stop HP Clustered File System
- Back Up and Restore the Cluster Configuration
- HP Clustered File System Network Port Numbers
- Configure Servers
- Configure Network Interfaces
- Configure the SAN
- Configure Dynamic Volumes
- Configure PSFS Filesystems
- Manage Disk Quotas
- Manage Hardware Snapshots
- Configure Security Features
- Configure Event Notifiers and View Events
- Overview
- Install and Configure the Microsoft SNMP Service
- Cluster Event Viewer
- Configure Event Notifier Services
- Select Events for a Notifier Service
- Configure the SNMP Notifier Service
- Configure the Email Notifier Service
- Configure the Script Notifier Service
- View Configurations from the Command Line
- Test Notifier Services
- Enable or Disable a Notifier Service
- Restore Notifier Event Settings to Default Values
- Import or Export the Notifier Event Settings
- Using Custom Notifier Scripts
- Cluster Operations on the Applications Tab
- Configure Virtual Hosts
- Configure Service Monitors
- Configure Device Monitors
- Advanced Monitor Topics
- SAN Maintenance
- Other Cluster Maintenance
- Management Console Icons
- Index
Chapter 15: Configure Virtual Hosts 188
Specify Failover/Failback Behavior
The Probe Severity setting allows you to specify whether a failure of the
service or device monitor probe should cause the virtual host to fail over.
For example, you could configure a gateway device monitor to watch a
router. The device monitor probe might occasionally time out because of
heavy network traffic to the router; however the router is still
functioning. In this case, you can configure the device monitor so that the
virtual host will not fail over if only the device monitor has failed.
The Probe Severity setting also affects the failback behavior of the virtual
host.
There are three settings for Probe Severity:
•
NOFAILOVER. The virtual host does not fail over when a monitor
probe fails.
•
AUTORECOVER. The virtual host fails over when a monitor probe
fails. When the service or device 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
Select a Backup Interface for Failover
When ClusterPulse needs to fail over a virtual host, it determines the best
network interface to receive the virtual host. It bases its decision on the
status of the available backup interfaces and their underlying servers.
Typically, it looks for an “up” network interface where all services are
“up” on the underlying server.
You can use the following Advanced settings to affect how ClusterPulse
selects the network interface for failover.
• The Event Severity setting allows you to specify whether ClusterPulse
should consider the existence of monitor events (such as a script
failure or timeout) when it chooses a network interface for failover. If
the events are considered, the network interface for the affected server
becomes less desirable.