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

Cluster Groups and Cluster Resource, Table 6-5, Solving Other Problems

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 141 highlights

6-16 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Cluster Groups and Cluster Resource Microsoft Cluster Administrator solves many group and cluster resource problems. For troubleshooting tips on this topic, refer to the Microsoft Cluster Server Administrator's Guide and Cluster Administrator's Online Help. Problem An application starts but cannot be closed. Table 6-5 Solving Other Problems Possible Cause Cluster Administrator must be used to take applications offline. A resource hangs when taken offline. Some resources take time to go offline. An IP address added to a cluster group fails. IP address configuration may be incorrect. A resource fails over but does not fail back. Groups may be configured to fail back manually or the automatic failback may be scheduled to occur during a specific time frame. Action Use Cluster Administrator to take the application offline. Do not close or exit an application from the application interface. Wait several minutes, then check any dependencies the resource may have. Verify that each can be taken offline. 1. IP addresses must be different from every other IP address resource and from every other IP address on the network. 2. The IP address must either by reserved by the network administrator or statically assigned outside of a DHCP scope. 1. If expecting an automatic failback, verify the group is not set for a manual failback. 2. If expecting an immediate automatic failback, verify the group is not configured to fail back only during a user-defined timeframe.

  • 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
6-16
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
Cluster Groups and Cluster Resource
Microsoft Cluster Administrator solves many group and cluster resource
problems. For troubleshooting tips on this topic, refer to the
Microsoft Cluster
Server Administrator’s Guide
and Cluster Administrator’s Online Help.
Table 6-5
Solving Other Problems
Problem
Possible Cause
Action
An application starts but cannot
be closed.
Cluster Administrator must be
used to take applications offline.
Use Cluster Administrator to take
the application offline. Do not
close or exit an application from
the application interface.
A resource hangs when taken
offline.
Some resources take time to go
offline.
Wait several minutes, then check
any dependencies the resource
may have. Verify that each can be
taken offline.
An IP address added to a cluster
group fails.
IP address configuration may be
incorrect.
1.
IP addresses must be
different from every other IP
address resource and from
every other IP address on
the network.
2.
The IP address must either
by reserved by the network
administrator or statically
assigned outside of a DHCP
scope.
A resource fails over but does not
fail back.
Groups may be configured to fail
back manually or the automatic
failback may be scheduled to
occur during a specific time
frame.
1.
If expecting an automatic
failback, verify the group is
not set for a manual
failback.
2.
If expecting an immediate
automatic failback, verify the
group is not configured to
fail back only during a
user-defined timeframe.