http://support.microsoft.com/kb/921181 goes into great depth explaining the algorithms
used to determine heartbeat failures.
This example sets the heartbeat for the interface to four missed heartbeats, which is about 5 seconds. The
node heartbeat is set to 8, which is about 9.6 seconds.
1. First, make sure all the cluster nodes are up with the following command:
Cluster $cluster_name node
The output should look something like this:
Listing status for all available nodes:
Node Node ID Status
-------------- ------- ---------------------
MB101 2 Up
MB100 1 Up
Part III: Working with PowerShell in a Production Environment
342
2. Next, configure the heartbeat parameters. The HeartBeatLostInterfaceTicks should be set
to one number higher than the desired missed heartbeats due to the way the algorithm works.
Cluster $Cluster_Name /priv HeartBeatLostInterfaceTicks=5:DWORD
Cluster $Cluster_Name /priv HeartBeatLostNodeTicks=8:DWORD
3. Finally, restart the cluster service on both nodes:
Net stop clussvc
Net start clussvc
Configuring the Network Interfaces
One last configuration is to change the private network for cluster use. By default the private adapter
is set for all communications. Because the private interfaces are connected via cross - over cables or a
non - routed network, the interface should be set to handle only internal cluster communication.
Pages:
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486