Though simplistic in its nature, this naming convention of
network interfaces is not very intuitive. A better way to name the NICs is to differentiate between the
production interface and the private interface. Figure 13 - 6 shows the standard NIC configuration.
Figure 13-6
As shown here, using netsh from within PowerShell allows for variables to be used within the
command:
$Interface1=???Local Area Connection???
$Interface1_New=???Public???
$Interface2=???Local Area Connection 2???
$Interface2_New=???Private???
$IP=???10.10.10.1???
$Subnet=???255.255.255.0???
Chapter 13: Single Copy Clusters
371
netsh interface set interface name = ???$Interface1??? newname = ???$Interface1_New???
netsh interface set interface name = ???$Interface2??? newname = ???$Interface2_New???
netsh interface ip set address name=???$Interface2_New??? source=static ???$IP??? ???$Subnet???
netsh interface ip set dns name=???$Interface2_New??? static none none
netsh interface set interface ???$Interface2_New??? enable
This script configures the first interface ??™ s name ($Interface1) and renames the interface
($Interface1_New) . The second interface is the heartbeat connection between both servers. Typically
this connection would not be actively used in a regular server and would be disabled.
Pages:
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521