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 187
• The PanPulse process controls whether a network interface is
marked up or down. When PanPulse determines that an interface
currently hosting a virtual host is down, ClusterPulse will begin
searching for another server on which to locate the virtual host.
3. ClusterPulse narrows the list to those servers without inactive, down,
or disabled HP Clustered File System device monitors. If there are no
servers that meet this criteria, the virtual host is not made active
anywhere.
4. If the virtual host is currently active on a server and that virtual host
has the
NOFAILBACK policy, then this active server is moved to the
head of the list of preferred servers to be considered.
5. From this list, ClusterPulse tries to find a server with all services up
and enabled. If ClusterPulse finds a server meeting these conditions, it
will use it, preferring servers earlier in the list of servers configured
for the virtual host.
6. If there are no servers with completely healthy services, ClusterPulse
picks a server that has at least one service up and enabled. If the
services have different priorities, ClusterPulse uses a server where a
service with the highest available priority is up. If ClusterPulse finds a
server meeting these conditions, it will use it, preferring servers earlier
in the list of servers configured for the virtual host.
7. The selected server will have one interface that was configured for this
virtual host. The virtual host will be active on this interface. If
ClusterPulse cannot locate a server meeting these conditions, it does
not place the virtual host anywhere.
Customize Service and Device Monitors for Failover
By default, when a service or device monitor probe fails, indicating that
the watched service is down or the monitored device cannot be accessed,
ClusterPulse will fail over the associated virtual host to another server
where the monitored service or device is up.
You can customize this behavior using the Advanced monitor settings.