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 17: Configure Device Monitors 212
The device monitor activeness policy decision is made as follows:
1. If the device monitor on a specific server is disabled, then the device
monitor will not be made active on that server.
2. ClusterPulse considers the list of servers that are both up and enabled
and that are configured for the device monitor. Note the following:
• A server that has not finished joining the cluster (see “Server
Access to the SAN” on page 235) is not considered up for the
purpose of activating the device monitor.
• A server is considered down if it loses coordinated communication
with the cluster (for example, the server crashed or was shut down,
HP Clustered File System was shut down on the server, the server
failed to schedule a cluster group communication process for an
extended period of time).
3. If the device monitor is multi-active, it will be active on all servers
passing evaluation for steps 1 and 2. If the device monitor is single-
active, then the list of servers is filtered by the following policy items
to determine the one server where the device monitor will be active.
4. From the list of servers that pass evaluation for steps 1 and 2,
ClusterPulse tries to find a server with all services up and enabled on
the virtual hosts associated with this device monitor. If Clusterpulse
finds a server meeting these conditions, it will use it, preferring
servers earlier in the list of servers for this device monitor.
5. If there are no servers with completely healthy services, ClusterPulse
picks a server that has at least one service up and enabled. If
ClusterPulse finds a server meeting these conditions, it will use it,
preferring services earlier in the list of servers for this device monitor.
6. If ClusterPulse cannot locate a server meeting these conditions, it will
make the device monitor active on the first server in the list of servers
for this device monitor.