Compaq ProLiant CL1850 Software User Guide

5-10 Compaq ProLiant CL1850 Software User Guide
Compaq Confidential – Need to Know Required
Writer: Bryan Hicks Project: Compaq ProLiant CL1850 Software User Guide Comments:
Part Number: 157839-001 File Name: f-ch5 System Management Using Microsoft Windows NT 4.0.doc Last Saved On: 9/8/99 5:03 PM
Microsoft Cluster Administrator
While the primary responsibility of Compaq Insight Manager is to monitor the
overall status of the cluster hardware, services, and resources, Microsoft’s
Cluster Administrator is most adept at managing the groups, resources, and
operating state of the cluster. Cluster Administrator gives you the ability to:
■ View the current status of cluster groups and resources
■ Bring groups and resources online and offline
■ Manually move groups and resources to another server node
■ Manually move groups and resources to their preferred server
■ Pause groups and resources
■ Restructure a group’s resource dependency tree
Cluster Administrator can be run remotely or on a server node. If Cluster
Administrator is installed remotely, the remote node must be in the same
domain as the server node. When running Cluster Administrator remotely, you
should connect to the cluster via Compaq Insight Manager or by using the
cluster IP address or cluster name.
NOTE: The remote feature is not supported in Microsoft Windows 95/98.
Refer to the Microsoft Cluster Server Administrator’s Guide for a thorough
description of Cluster Administrator’s features and specifics on how to use the
utility.
Modifying Physical Cluster Resources
Removing Shared Storage
Each server node, and the cluster as a whole, depends on the shared storage for
data, log, and, possibly, application program files. If the shared storage is
removed, all clustered applications that are dependent on that shared storage
system will be offline. Clearly, network clients will not have access to the
clustered applications.
Before removing a shared storage system (that is, the cluster), use Cluster
Administrator to bring offline all cluster groups and resources on both server
nodes. This ensures the groups and resources are gracefully brought offline,
rather than causing an abrupt interruption of service by powering down the
cluster.