Windows Server 2012 R2 with PowerShell 4.0 has hugely expanded support for configuring multiple NICs on a Cluster/ISCSI Initiator node via command line. After deploying multiple Network Interface Cards on my Hyper-v host, it took me a while to figure out how to properly configure the NICS with PowerShell .
Prior to Windows Server 2012, NIC configurations could be accomplished with the GUI, Netsh command line utility or mainly WmiObject classes. The following cmdlets enabled me complete the configuration of multiple NICs on a cluster node:
List Available NICs on Host Server.
Rename Network Adapter for Storage/ISCSI Connection.
Get-NetAdapter -InterfaceIndex 15 | Rename-NetAdapter -NewName StorageNIC1
Set Private IP Address on Selected NIC.
Get-NetAdapter -InterfaceIndex 14 | New-NetIPAddress -IPAddress 192.168.3.8 -PrefixLength 24 -AddressFamily ipv4
Disable Network Adapter Bindings.
Usually the Storage Network Adapter needs just the IPv4 TcpIp binding enabled:
PS C:\ Get-NetAdapterBinding -Name StorageNIC1
Name DisplayName ComponentID Enabled
View original post 345 more words