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 18: Advanced Monitor Topics 228
When a failure occurs on the Primary, the virtual host needs to fail over to
a backup. HP Clustered File System now looks for the best location for
the virtual host. Because the probe status on the first backup is “down,”
HP Clustered File System chooses the second backup, where the probe
status is “up.”
At i5 in the following example, the probe fails on the Primary. At i6, the
virtual host is deconfigured on the Primary. At i7, the monitor stop script
begins on the Primary. At i8, the virtual host is configured on the second
backup. At i9, the monitor start script begins on the second backup. At
i10, probing begins on the second backup.
Primary
First Bac k up
Second Backup
Vhost status
Probe status
Monitor activity
down
stopping
active
Vhost status
Probe status
Monitor activity
inactive
down
Vhost status
Probe status
Monitor activity
inactive
inactive
i5 i6 i9 i10
inactive
starting
active
inactive
up
up
active
inactive
active
i7 i8
Time