HP ProLiant 4500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 105

Managing a Cluster Without Interrupting, Managing a Cluster in a Degraded

Get HP ProLiant 4500 PDF manuals and user guides View all HP ProLiant 4500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 105 highlights

5-2 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide The chapter also details the utilities and programs used in the ongoing management of Compaq ProLiant Clusters HA/F100 and HA/F200. The tools addressed in this chapter include: s Compaq Redundancy Manager (Fibre Channel) s Compaq Insight Manager s Compaq Insight Manager XE s Compaq Intelligent Cluster Administrator s Microsoft Cluster Administrator Managing a Cluster Without Interrupting Cluster Services At some time during the life of a cluster, it is likely that a cluster node will have to be powered off in order for the administrator to perform an operation. Always use Cluster Administrator to fail over (or at a minimum to bring offline) clustered applications before powering off the server. Managing a Cluster in a Degraded Condition Due to the highly available nature of clustering, applications and network clients remain operational even while some cluster components do not. When the cluster is in this degraded condition, follow this process: 1. Understand what caused the degradation. Use Compaq Insight Manager or Compaq Insight Manager XE to determine the problem. 2. Determine whether the condition will continue to worsen. 3. Determine how critical the problem is. a. If the problem is considered noncritical, wait until a nonpeak time to service the problem. (Using Intelligent Cluster Administrator, you can usually work around the problem and continue successful cluster operations.) b. If the problem is considered critical, fail over all clustered applications and resources to the other server before servicing the problem. (This can be accomplished using Intelligent Cluster Administrator through a browser or using the Insight Manager console when linked with MSCS Cluadmin.)

  • 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
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
5-2
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
The chapter also details the utilities and programs used in the ongoing
management of Compaq ProLiant Clusters HA/F100 and HA/F200. The tools
addressed in this chapter include:
■
Compaq Redundancy Manager (Fibre Channel)
■
Compaq Insight Manager
■
Compaq Insight Manager XE
■
Compaq Intelligent Cluster Administrator
■
Microsoft Cluster Administrator
Managing a Cluster Without Interrupting
Cluster Services
At some time during the life of a cluster, it is likely that a cluster node will
have to be powered off in order for the administrator to perform an operation.
Always use Cluster Administrator to fail over (or at a minimum to bring
offline) clustered applications before powering off the server.
Managing a Cluster in a Degraded
Condition
Due to the highly available nature of clustering, applications and network
clients remain operational even while some cluster components do not. When
the cluster is in this degraded condition, follow this process:
1.
Understand what caused the degradation. Use Compaq Insight Manager
or Compaq Insight Manager XE to determine the problem.
2.
Determine whether the condition will continue to worsen.
3.
Determine how critical the problem is.
a.
If the problem is considered noncritical, wait until a nonpeak time to
service the problem. (Using Intelligent Cluster Administrator, you
can usually work around the problem and continue successful cluster
operations.)
b.
If the problem is considered critical, fail over all clustered
applications and resources to the other server before servicing the
problem. (This can be accomplished using Intelligent Cluster
Administrator through a browser or using the Insight Manager
console when linked with MSCS Cluadmin.)