Virtual NIC's in Hyper-V and how I've been doing it wrong!

My server hardware hasn’t changed

4 x 1GB NIC's on a Quad adapter

2 x 10GB NIC's on a Dual adapter

If you've seen my previous posts you'll see that I created teams in Server Manager

Across from NIC Teaming if you haven’t created a Team this option is marked as Disabled

 Click on Tasks and create a virtual Switch

Select the NIC’s you want to add to the Team, In the above example you can see I left the Additional properties as default

I left the default options under additional properties.

The next step is what I’ve been doing incorrectly for some time, thankfully I got some great advice 

from some friends and I suggest you read his blog.

Credit for script: Aidan Finn - http://www.aidanfinn.com/?p=12609

My network is slightly different so my script is different although I used Aidan’s as a template. 

I have added some additions from Technet article - http://technet.microsoft.com/en-us/library/dn550728.aspx

Storage – Switch and vNIC (283)

Do not put a Virtual Switch on top of the Storage network
Create team and assign vLAN from Windows teaming

**********************

Production Switch and 3 x vNIC’s, MGMT(101), Live Migration (2828) and VMNetwork (102)

New-VMSwitch “ProductionNetSwitch” -NetAdapterName “Production” -AllowManagementOS 0

Add-VMNetworkAdapter -ManagementOS -Name “MGMT” -SwitchName “ProductionNetSwitch”

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "MGMT" -Access -Vlanid 101

Add-VMNetworkAdapter -ManagementOS -Name “VMNetwork” -SwitchName “ProductionNetSwitch”

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "VMNetwork" -Access -Vlanid 102

Add-VMNetworkAdapter -ManagementOS -Name “LiveMigration” -SwitchName “ProductionNetSwitch”

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LiveMigration" -Access -Vlanid 2828

What will I end up with??

This script will give you a virtual switch

ProductionNetSwitch

Then it will give you 4 x vNIC's total

Storage on VLAN 283

VMNetwork 102

MGMT 101

Live Migration 2828

What does that look like in real life?

Gridstore and Hyper-V Teaming

Hyper-V Cluster with Gridstore

In this configuration we have a 3 host Hyper-V cluster and 3 Gridstore nodes. We are using 2 x Juniper 4550’s for the storage network and 2 x Juniper 3300’s.

There are 4 x 1GB NICS and 2 x 10GB SFP’s

4 x 1GB NIC’s will be configured in a Team using Windows Server 2012R2
              Live Migration on VLAN 1

              Management on VLAN 2

              Production on VLAN 3

              DMZ on VLAN 4

2 x 10GB SFP’s will be configured in a team for the storage network and will be configured 1 Port per switch.

As Gridstore is based on WS2008R2 best practice is to use the manufacturer’s drivers for teaming.

The Broadcom network card will be configured in a load balanced failover team using the drivers supplied.

The Junipers will be configured to tag all traffic to VLAN 283. There will be a 2 x 10GB ports configured as a 20GB trunk to allow the switches communicate between each other and send VLAN 283 traffic.

 Gridstore NIC Teaming

•       Plug Ethernet port 0 into a switch on each Gridstore node

•       Boot a DHCP server

•       Boot the Gridstore Nodes

•       Each node should be assigned an IP address from the DHCP server

•       Contact Gridstore Support and ask them to log into each node.

•       Set a static IP on the Ethernet address

•       To do this type in “control”

•       Click on “Network and Sharing Center”

•       Name the active interface and set a static IP on it to make things easier for later

•       Once you have set the static IP the RDP session will drop. Reconnect using the new IP

•       Cable your 10GB Ethernet to each switch and go back to the control panel

•       Click on Broadcom Control Suite 4 in Control panel

•       Click on Filter and select Team View

•       Right click on the server name “GS-DHBS6CZ1” in this case

•       Select create a new Team

•       Click Next

•       Name the team and click Next

•       Name the team and click Next

•       Select the adapters you want and click Add and then Next to continue

•       Leave the defaults and click Next

•       Leave the defaults and click Next

•       Click Add VLAN and click next

•       Name the VLAN this is important as it might help later in the process

•       Click on Tagged and click Next

•       Type in your VLAN ID and click next

•       After the Team is created open Network and sharing center and set the IP address on the Teamed NIC

•       RDP to the Gridstore using the new Teamed IP address

•       The next configuration you have to complete is in the registry

•       Open the command prompt and type in regedit and browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Gridstore\NetworkAdapter”

•       If you see anything but the BASP adapter Follow the next steps

•       Disable the MGMT Interface

•       In the command prompt type in Service.msc

•       Disable the Gridstore Service

•       Open regedit

•       delete the Folder “NetworkAdapter” in “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Gridstore\NetworkAdapter”

•       Start the service and refresh the Gridstore Registry key by pressing F5

•       The BASP adapter should now be present.

•       Duplicate for each node

Windows Server 2012 NIC Teaming

•       Open Server Manager

• Click on NIC Teaming

    

•       Under teams click Tasks and select “New Team”

•       Name the team and select the adapters

•       Select the team then click Team Interfaces, Then click tasks and Add Interfaces

•       Name the new Virtual Adapter and the VLAN for the network

•       Set the Static IP on the StorageLAN – VLAN 283 Adapter

•       The team is now configured

Fun and games with MDT - Microsoft Deployment Toolkit

First most useful part of this for me was finding out the defaults for the bootstrap.ini and the CustomSettings.ini files


Bootstrap.ini

[Settings]
Priority = MACADDRESS, Default
[Default]
DeployRoot=\\DUBWDS001\DeploymentShare$
SkipBDDWelcome=YES
KeyboardLocale=en-IE

USerID=administrator
USerDomain=Gargan.me
UserPassword=

****************************************************

CustomSettings.ini

[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
 OSInstall=Y
 SkipTaskSequence=YES
 TaskSequenceID=002
 SkipPackageDisplay=NO
 SkipApplications=NO
 SkipAppsOnUpgrade=YES
 SkipCapture=YES
 SkipProductKey=YES
 SkipComputerBackup=YES
 SkipBDDWelcome=YES
 SkipAdminPassword=YES
 AdminPassword=defaultpassword
 SkipDeploymentType=YES
 DeploymentType=NEWCOMPUTER
 SkipUserData=YES
 SkipDomainMembership=YES
 JoinDomain=Gargan.me
 DomainAdmin=administrator
 DomainAdminDomain=Gargan.me
 DomainAdminPassword=defaultpassword
 SkipFinalSummary=YES
 SkipLocaleSelection=YES
 SkipComputerName=NO
 ComputerName=DUBXXXLP
 SkipTimeZone=YES
 KeyboardLocale=1809:00001809
 UserLocale=en-IE
 TimeZone=085
 TimeZoneName=GMT Standard Time
 _SMSTSOrgName=gargan.me
 SkipRoles=YES
 SkipBitLocker=YES
 SkipSummary=YES


These settings are configured for UK or Ireland and I pieced this together from a number of helpful websites. In my next post I will go into more detail on the setup of MDT

http://msdn.microsoft.com/en-us/library/ms912391(v=winembedded.11).aspx
http://systemspecialist.net/2011/06/20/mdt-2010-mega-tips-and-tricks-collection/