
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.
1. The following command changes the private network interface from mixed mode to internal
cluster communications only:
Cluster network Private /prop Role=1
2. The network order must also be set to the public interface first, and then the private interface
next. To check the current binding order, run the following command:
Cluster $Cluster_Name /listnetpri
The output from the test environment is:
Listing the priority order of internal networks:
Network Name
---------------
1 Private
2 Public
3. Because this is the incorrect order, the next step is ...