Where to set the virtual subnet ID?
Ran across this question and would like some consensus on the correct answer.
You need to implement network virtualization.
On which object should you configure the virtual subnet ID?
A. Virtual switch
B. Hyper-V Server
C. VM
D. Virtual network adapter
All my research points to the "Virtual network adapter". Mostly because the "Set-VMNetworkAdaper" powershell command as a switch called "-VirtualSubnetID" whereas set-VMSwitch does not.
Regards,
Adam Tyler
ok. I believe you're correct D is the answer. To do this remember that the reason you set it the on Virtual Network Adapter is that you have to:
Windows Network Virtualization Binding of the physical NIC on a Hyper-V host.new-networkvirtualizationlookuprecord and new-netVirtualizationCustomerRoute on the Hyper-V host.Provider Address and Route on per Hyper-V host on your binding.VirtualSubnetID from the lookuprecords and customerroute on the virtual adapter.So, I think you're correct but the Microsoft Triumvirate or other members may here at ITProTV may post an alternative.
Thank you Ronnie.. This network virtualization stuff has me pretty confused. I mean, I get the concept of a VXLAN rather than a VLAN, it opens up many more possibilities for large enterprise to go beyond the 4096 limit of the VLAN. I'm even comfortable with the idea of using a GRE tunnel between the hyper-v hosts to tunnel the "virtual network" traffic (NVGRE).
However it appears there are two different versions of Microsoft network virtualization that have been released and the implementation walk-throughs I have run across are extremely complex. I sat through the ITPro 70-740, 741, and 742 courses and don't remember seeing anything related to network virtualization. Does ITPro have a class that focuses on this subject alone? Other good getting started guides you can point me to?
Regards,
Adam Tyler