Hyper-V 3.0, physical NICs & virtual switch


we running windows server 2012 in our small office.  roles include domain controller, dns & dhcp.   physical server has plenty of ram , disk space, wanted load hyper-v 3.0.   server dell poweredge t320 2 physical nics connected our unmanaged switch.   2 nics configured team static address , are functioning perfectly.

when install hyper-v role, wizard asks me assign nic virtual switch.  is required?  since physical nics teamed, choose nic team , restart.  after hyper-v configured , running, server loses connectivity.  i check ip address on nic team (which identical hyper-v virtual switch) , correct.

what doing wrong?  would better if dissolved nic team , dedicated 1 nic outside connectivity , other hyper-v?  if go scenario, ip address use hyper-v nic/virtual switch?  thanks help.

two things:

    • when create virtual switch, there option share network adpater host operating system. make sure have checked. also, post screen shot of virtual switch configuration page , i'll take look.
    • in situation, vote dissolve team , assign 1 nic per function (one per host/management, 1 per virtual switch). keep logical functionality separate, suppose there advantages both ways of doing it. team work if setup correctly.


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607