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 209
GATEWAY Device Monitor
When certain network failures occur, the servers in a cluster can lose
communication with each other. This situation can result in a partition, or
split, of the cluster. For example, in a two-server cluster, each server
would assume that it remained in the cluster and that the other server
was down. The gateway device monitor detects the network failure and
prevents the cluster from partitioning. A gateway device monitor is
multi-active and can be configured on multiple servers.
When you configure the monitor, you will be asked for the network
address of a router or other gateway probe device. The IP address of the
device should be on a different subnet than the servers in the cluster. The
device should respond to a ping and should be visible on each server.
After the gateway device monitor is configured on a server, it pings the
gateway device periodically. If a network failure occurs and the ping fails,
any active virtual hosts on the server will become inactive and fail over to
another server.
NTSERVICE Device Monitor
The
NTSERVICE device monitor is configured for a specific NT service.
When the device monitor instance becomes active, it will start the NT
service if it is not already started. When the device monitor instance
becomes inactive, the monitor stops the NT service if the probe type for
the monitor is set to Single-Probe. When you configure the monitor, you
will need to indicate whether dependent services of the specified NT
service should also be started and stopped.
When the monitored NT service is started on a server, it is provided with
four environment variables that are set as follows:
•
COMPUTERNAME = <IP address of server hostname>
•
_CLUSTER_NETWORK_FQDN_ = <IP address of server
hostname>.<domainname>
•
_CLUSTER_NETWORK_HOSTNAME_ = <IP address of server hostname>
•
_CLUSTER_NETWORK_NAME_ == <IP address of server hostname>