Hyper-V Server with Single NIC. NAT vs. "Allow management OS to share connection"?
hello, have acquired dedicated server host hyper-v.
after doing research have found recommendation have 2 nics, unfortunately, dedicated server set 2 nics, 1 of them has internet access. second 1 used backend servers , vlans, etc.
so leaves me no choice consider single nic infrastructure. nic exposed internet has been assigned 5 static ip addresses, here's accomplish.
- need host separate vm for: web server, sql server , mail server. each of these 3 vms should able accessed 1 of public static ip addresses assigned nic.
i know have 2 alternatives,
a. 1 create external virtual network on nic connected internet, , check option "allow management os share connection." understanding create virtua switch , vnic , network traffic follow larger route, management purposes, kind of makes me uncomfortable.
b. second option to: create internal network , add network policy , access services role host os, way somehow route traffic coming to, let's say: public ip 1.2.3.4 internal 192.* web server, public ip 1.2.3.5 internal 192.* sql server , on... think need nat accomplish this.
so question is, following option b. give me better performance , faster overall network traffic? there better recommended way accomplish need? second dedicated nic not option @ moment.
any advice appreciated.
hi,
it seems there misunderstanding.
for example, if have 2 physical network adapter on hyper-v machine, create 1 external virtual network bind 1 physical network adapter , leave hyper-v communication, that's microsoft recommend——delicate 1 physical network adapter hyper-v host communication. if have more nics, can create other external virtual network balance load of vms.
with external virtual network, vms connect can ip addresses physical network(just hyper-v host does). if want assign public ip addresses vms, it's easy use external virtual network.
by way, if there 1 physical network adapter on hyper-v host machine, have check box "allow management os share connection", create virtual network adapter hyper-v host communication, option not affect communication of vms connect external virtual network.
vincent hu
Windows Server > Hyper-V
Comments
Post a Comment