Hyper-V Networking (Server 2012 R2): Prioritizing Network Traffic with "Virtual Internal" Network switches and "Virtual External" Network switches

update:  on app server, tried reorder of bindings of nics , tried "interface metric" , set value both nics 1 lower , 1 higher.  the lowest 1 being 1 @ top , higher 1 , nothing worked.  i tried via mac address , yeah, nothing works.   thinking because "virtual switches" , not "virtual nics". 

 

note: did research via google, didn't find lot "useful", came here hoping answer.

 

what have set this.....

 

1) "database server" vm , located on hyper-v host called hyperv2

2) "app server" vm , located on hyper-v host called hyperv2.

3) have hyper-v host called hyperv2 using "windows server 2012 r2".

 

what want happen this....

 

1) want able have internal network "app server" can talk "database server" directly instead of going on physical nic.   have "internal virtual network" switch setup this.

2) want database server , app server both available internet development purposes , use "external virtual network switch" have set-up.  

 

my problem is, cannot prioritize network connections "internal network" connection used first.  the "internal network" doesn't use physical nic , uses internal, therefore not subject nic failure , has more performance. 

  

note: internal network gets used if disable "external network". 

 

i sure guys know , smarter me figuring out.  i got far , close, need figure rest out.

is there tutorial available of this?

right -- 2 nics, 1 team, 1 virtual switch. vnics on switch not isolated each other @ layer 2 if connectivity lost. reiterate, don't know happens if pnic suffers sort of hardware failure, although assumption internal connections still valid. if team, you'd have lose both of them anyway. also, because brought up, name resolution , things of nature can still issue, teaming first , best line of defense against well.

but, sounds me performance direct access target , that's i'd focus testing time.

---

eric siron
altaro hyper-v blog
independent blog contributor, not altaro employee. solely responsible content of posts.

Windows Server  >  Hyper-V