OK so I am trying to understand this.
If it is recommended to have a separate NIC for management, how do VMs communicate with external networks (outside Hyper-V)?
I have built and managed many Hyper-V clusters over the years but always have used virtual switches which are shared with management partition....remember that option while creating a Hyper-V switch "Allow management operating system to share this network
adapter”?
Right
This time, I am trying to go with the "best practice".
- I have one dedicated NIC for host management.(I believe I do NOT need to create a virtual switch for this traffic)
- I have another NIC which I want to use for VM traffic going outside to the world.
For the second one, I should create a virtual switch and eventually my VMs would be able to communicate outside the host.
THAT is where I am stuck. I see no way to do that, yet. If I create a virtual switch with the checkbox checked for "Allow management operating system to share this network adapter” I do get a vNIC created and TCP/IP is there. (but isn't that what I am NOT supposed to do?). If I uncheck that, TCP/IP is removed from the switch. So no external network communication is possible by the VMs assigned to that switch.
What am I missing?
-Rajeev rajdude.com