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

Verifying Network Client Failover, the changes and return to the main Cluster Administrator screen.

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

Setting Up the Compaq ProLiant Clusters HA/F100 and HA/F200 3-25 3. Make sure all predefined resources and groups are online. Verify that some of the resources and groups are owned by the server you will be powering off, so that a failure event will result in failover of resources and/or groups. 4. Power off one of the cluster nodes. Within several seconds, Microsoft Cluster Administrator will bring online all of the predefined resources and groups that were previously owned by the powered-off server. If, after a minute, nothing appears to have happened, refresh the screen by selecting Refresh (F5). 5. If failover is not working correctly, see the installation troubleshooting tips in Chapter 6. Verifying Network Client Failover After you have verified that each server is correctly running as a cluster node, the next step is to verify that network clients can interact with the cluster. The following steps will lead you through this validation procedure: 1. Ensure both cluster nodes are running, and verify, by means of Microsoft Cluster Administrator, that all groups and resources are online. 2. For each hard disk in the shared storage, MSCS automatically creates a cluster group that consists of a single resource, the disk drive. Using Microsoft Cluster Administrator, add an existing IP address as another resource to one of these groups. (Do NOT use the Cluster Group.) Save the changes and return to the main Cluster Administrator screen. 3. Open a DOS window on a network client machine. 4. Ensure the network client can access the IP address. Regardless of whether you are using WINS or DHCP, you can execute the DOS command ping to check the connection. Execute a Ping command from the network client , using the cluster IP address as the argument. The client has successfully accessed the cluster resource if you get a response similar to: Reply from : bytes=xx time=xxxms TTL=xx. The client has not successfully accessed the cluster resource if you get a response of: Reply from : Destination host unreachable

  • 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
Setting Up the Compaq ProLiant Clusters HA/F100 and HA/F200
3-25
3.
Make sure all predefined resources and groups are online. Verify that
some of the resources and groups are owned by the server you will be
powering off, so that a failure event will result in failover of resources
and/or groups.
4.
Power off one of the cluster nodes.
Within several seconds, Microsoft Cluster Administrator will bring
online all of the predefined resources and groups that were previously
owned by the powered-off server. If, after a minute, nothing appears to
have happened, refresh the screen by selecting Refresh (
F5
).
5.
If failover is not working correctly, see the installation troubleshooting
tips in Chapter 6.
Verifying Network Client Failover
After you have verified that each server is correctly running as a cluster node,
the next step is to verify that network clients can interact with the cluster.
The following steps will lead you through this validation procedure:
1.
Ensure both cluster nodes are running, and verify, by means of
Microsoft Cluster Administrator, that all groups and resources are
online.
2.
For each hard disk in the shared storage, MSCS automatically creates a
cluster group that consists of a single resource, the disk drive. Using
Microsoft Cluster Administrator, add an existing IP address as another
resource to one of these groups. (Do NOT use the Cluster Group.) Save
the changes and return to the main Cluster Administrator screen.
3.
Open a DOS window on a network client machine.
4.
Ensure the network client can access the IP address. Regardless of
whether you are using WINS or DHCP, you can execute the DOS
command ping to check the connection.
Execute a Ping command from the network client , using the cluster IP
address as the argument.
The client has successfully accessed the cluster resource if you get a
response similar to:
Reply from <IP Address>: bytes=xx time=xxxms TTL=xx.
The client has not successfully accessed the cluster resource if you get a
response of:
Reply from <IP Address>: Destination host unreachable