Compaq ProLiant CL1850 Compaq ProLiant CL1850 Software User Guide - Page 67

Cluster Management Concepts Using Microsoft Windows NT

Page 67 highlights

5-2 Compaq ProLiant CL1850 Software User Guide Cluster Management Concepts Using Microsoft Windows NT Managing a Cluster without Interrupting Applications or Services At some time during the life of your system, it is likely you will need to perform an operation on a server node that will require it to be powered down. Always use Cluster Administrator to fail over (or at a minimum, bring offline) clustered applications before powering down the server. Managing a Cluster in a Degraded Condition Due to the high-availability nature of clustering, applications and network clients remain operational even while some cluster components do not. When the cluster is in this degraded condition, it is important to follow this process: 1. Understand what caused the degradation. 2. Determine whether the condition will continually worsen. 3. Determine how critical it is to repair the problem. a. If the problem is considered noncritical, wait until a nonpeak time to service the problem. b. If the problem is considered critical, fail over all clustered applications and resources to the other server node before servicing the problem. Managing Hardware Components of Individual Server Nodes Compaq Insight Manager has been enhanced to operate with the Compaq ProLiant CL1850. While Compaq Insight Manager maintains its current features of viewing and managing servers and their components, it now allows you to view two server nodes as a single cluster entity. A comprehensive overview of Compaq Insight Manager's cluster capabilities appears later in this chapter.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90

5-2
Compaq ProLiant CL1850 Software User Guide
Cluster Management Concepts Using
Microsoft Windows NT
Managing a Cluster without Interrupting
Applications or Services
At some time during the life of your system, it is likely you will need to
perform an operation on a server node that will require it to be powered down.
Always use Cluster Administrator to fail over (or at a minimum, bring offline)
clustered applications before powering down the server.
Managing a Cluster in a Degraded Condition
Due to the high-availability nature of clustering, applications and network
clients remain operational even while some cluster components do not. When
the cluster is in this degraded condition, it is important to follow this process:
1.
Understand what caused the degradation.
2.
Determine whether the condition will continually worsen.
3.
Determine how critical it is to repair the problem.
a.
If the problem is considered noncritical, wait until a nonpeak time to
service the problem.
b.
If the problem is considered critical, fail over all clustered
applications and resources to the other server node before servicing
the problem.
Managing Hardware Components of Individual
Server Nodes
Compaq Insight Manager has been enhanced to operate with the Compaq
ProLiant CL1850. While Compaq Insight Manager maintains its current
features of viewing and managing servers and their components, it now allows
you to view two server nodes as a single cluster entity. A comprehensive
overview of Compaq Insight Manager’s cluster capabilities appears later in
this chapter.