Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

KeithMayer — Thu, 02 May 2013 18:29:34 GMT

Hi Artur,

Communication between virtualized networks and physical networks is handled by a Hyper-V Network Virtualization Gateway. Check out the Gateway architecture guide for more details at technet.microsoft.com/.../jj618319.aspx.

It sounds like, in your environment, network virtualization for your VM traffic makes the most sense to avoid ongoing management of over 400 VLANs.

Hope this helps!

Keith

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

Artur Rodrigues — Thu, 18 Apr 2013 00:15:36 GMT

I have a shared environment where the network team is talking about to create (a crazy) 400 VLANs. Network virtualization is definitely an option. However I have two questions. If I use Hyper-V virtualization, how my VMs using CA will reach physical servers/devices on specific physical VLANs? What makes more sense for Hyper-V network virtualization in relation to my physical NIC configuration tunneled or mapped VLAN modes?

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

KeithMayer — Thu, 07 Feb 2013 01:17:12 GMT

Hi Darryl,

There hasn't been an official announcement yet on availability of the Hyper-V Network Virtualization Gateway provider yet for System Center 2012 SP1. I'll be sure to share more info as soon as I have it.

Best regards,

Keith

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

Darryl — Mon, 04 Feb 2013 07:56:35 GMT

"You can use either Windows Server 2012 or a 3rd party appliance for a Hyper-V Network Virtualization Gateway. I believe that a configuration provider for Windows Server 2012 Hyper-V Gateways will be made available after SP1 of System Center 2012 is made generally available"

Any clue when this is made available?

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

KeithMayer — Mon, 28 Jan 2013 18:09:41 GMT

Hi Eric,

The Hyper-V network virtualization gateway will have at least one physical NIC that is virtualized with the WNV driver and will have a connection and valid IP for each virtualized subnet through that NIC. This permits the VMs to be assigned a default gateway IP address that appears to be for a router that is on their local subnet, but in fact is an IP in the customer address (CA) space and is present in the virtualized routing domain tables on the host as a default gateway - in PowerShell, the command on the host to set this up would look something like this:

New-NetVirtualizationLookupRecord -CustomerAddress "10.0.0.1" -ProviderAddress "169.254.254.254" -VirtualSubnetID "6000" -MACAddress "101010101101" -Rule "TranslationMethodEncap" -VMName "BlueS1-DG"

Take a look at the gateway PowerShell script example linked above in the article - it provides a good walk-through of this scenario.

Hope this helps!

Keith

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

ericjmail — Sun, 27 Jan 2013 16:14:32 GMT

Keith

Thanks very much for the cogent presentation. I've been looking for good info on this since before RTM last July.

What I'm wondering is what IP to assign as the GATEWAY IP in the VM's when configuring their internal network addressing? Would their private, isolated IP's use a gateway address of the IP address of the HV GATEWAY APPLIANCE then?

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

Shekhar — Fri, 28 Dec 2012 09:31:55 GMT

Hi Keith,

Thanks !!! was looking for a very long time for this. Glad that search ends here.

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

KeithMayer — Sat, 22 Dec 2012 11:27:14 GMT

Hi Steven,

You can use either Windows Server 2012 or a 3rd party appliance for a Hyper-V Network Virtualization Gateway. I believe that a configuration provider for Windows Server 2012 Hyper-V Gateways will be made available after SP1 of System Center 2012 is made generally available, but the general recommendation is to prefer one of the appliance solutions for production usage.

Hope this helps!

Keith

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

Stitter — Fri, 21 Dec 2012 10:05:25 GMT

Hi Keith,

When you mention Hyper-V Network Virtualization Gateway as a server, is there any way you can configure Server 2012 to be a gateway or are they all 3rd party servers/appliances?

If you can configure Server 2012 then how do you then import it into SCVMM 2012 SP1 as a configuration provider in order to define it when creating your VM Networks?

This seems to be the missing piece in my jigsaw at the moment

Thanks for any help

Steven

re: Step-by-Step: Hyper-V Network Virtualization - 31 Days of Favorite Features in #WinServ 2012 ( Part 8 of 31 )

Chris N — Tue, 11 Dec 2012 07:30:52 GMT

Hello Keith,

Thank you, that helped a lot to get a better understanding.