Once the install is complete, the second node can be added by using
the following script:
$Cluster_Name (reused from the initial configuration above)
$Node2_Hostname=???MB002B???
$Password (reused from user configuration)
cluster /cluster:$Cluster_Name /add:$Node2_Hostname /password:$Password /verbose
When complete, the cluster will look like the one shown in Figure 13 - 12 .
Figure 13-12
Part III: Working with PowerShell in a Production Environment
378
And via the command line, it looks like Figure 13 - 13 .
Figure 13-13
There are two final post - installation tasks. One is required for correct performance, and the other is for
ease of management once Exchange is installed. The required configuration change is to set the Private
interface ??™ s communication mode. Because this interface is either directly connected to the other node by
a cross - over cable or is connected to a non - routable VLAN on a switch, it cannot take public traffic and
needs to be configured for internal cluster communications only (private network). The following single
cluster command fixes this:
$Interface2_New (reused from the network configuration section)
cluster network $Interface2_New /prop Role=1
Chapter 13: Single Copy Clusters
379
The next two commands consolidate the non quorum disks into a single group and delete the
empty group:
$Disk3_Drive (reused from the disk format section)
$Cluster_Name (reused from the MSCS install section)
cluster resource ???Disk $Disk3_Drive??? /move: ???Group 0???
cluster /cluster:$Cluster_Name group ???group 1??? /delete
Figure 13 - 14 shows verification of the cluster configuration through cluadmin .
Pages:
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526