Windows 2008 R2 Hyper-V Cluster NIC Setup

·         i little confused trying nic setup correct windows 2008 r2 hyper-v servers clustered.

i have 4 nics in each server.  (i may try teaming couple of them - have read may fail).  take have 3 nics in each server.  have fibre channel connectivity san don't need nic iscsi.

1 nic management of os

1 nic cluster hearbeat

i nic vm connectivity. 

best practice have hearbeat , vm nics in own subnets.

i have cluster heartbeat nics on clustered servers in own subnet , can communicate workstations on subnet. 

1)  need communincate workstations?  should remove routing these heartbeat nics on each clustered server can only communicate each other?

i want have nics vms on each server in subnet of their own (which routed). 

2)     vm nics are my big issue.  uncheck "allow management operating system share network adapter" , removes static ip addressing have set used physical nic connect outside world.

however, cannot setup subnet , routing if don't know ip of physical nics.  there way of setting these phyiscal nic's ips?

i sure i have something not quite right, not sure what. 

3)  there way prioritise particular nics csv , live migration?  best go through cluster hearbeat nics?

thanks it's doing head in!

1) if using subnetting isolate heartbeat traffic, wont need route, can use vlan's isolate traffic.

2) uncheck "allow management operating system share network adapter" - design, should add virtual network in hyper-v , assign vm nics virtual network (switch), each vm nic assigned own ip configuration , uses card communicate, (no ip required if physical nic dedicated vm's)

3) open failover cluster manager console, expand services , applications, select vm, on right pane, right click , select properties, should see several options including "network live migration"

review networking guide live migration, covers number of network options.

http://technet.microsoft.com/en-us/library/ff428137(ws.10).aspx

 

regards

 

---

ronnie

Windows Server  >  Hyper-V