Windows 2012 R2 HyperV clustering

hi everyone,

we have purchased 2 windows 2012 r2 datacenter editions , trying setup hyper-v cluster.

i have installed , configured failover cluster windows feature, enabled hyper-v on both servers , created hyper-v cluster.

want accomplish few things:

1. have total of 6 nic's per server, dont know how create full fail on , ha nics (extremely simple in vmware)

2. hyperv cluster keep assigning 169.254 ip automatically, , have manually configured 192.168.1.x

3. can use remote management both hosts in 1 window?

4. why hosts cant show shared disk, 1 server @ time can see shared disk, other server shows reserved.

we using dell vrtx, servers , storage within 1 chassis.
servers , storage connected internally
servers has 2 internal ports plus got 1, 4 port nic each server, each server have 6 nic ports.
want see if possible wise vmware, every host can see , manage shared disks
disks sas, again no external connection think doesn't matter

right when try open hyperv manager, cant change default vm , disk path shared storage, 1 server can see it.

not mention vmware extremely simple , reliable

thanks in advance.

its highly recommended assign static addresses hosts before creating cluster cluster require ip in same network hosts.

so break cluster , assign addresses nics first. recommend renaming nics simplicity , troubleshooting

do following:

1. destroy cluster in fail on cluster manager.

2. rename the nics used in fail on cluster, name them mgmt, csv, live.
 then assign addresses them manually... mgmt 1 remote , should corp network address... csv , live can want not requited routable outside cluster assign them: csv- 10.0.0.1/24 , live: - 10.0.1.1/24, other nics disable them (you can create teamed interfaces later when confident cluster working)

3. create cluster, make sure assign ip cluster on corp network

when add disks fail on cluster need create volume on disk in disk manager add cluster , click add csv inside fail on cluster manager.

this should create cluster csv... should have 3 nics spare mentioned had 6... can try using nic teaming found on server manager screen local server create teamed interface ... requires understand switch setup need know if using lacp or switch independent options inside teaming configuration.. add 3 spare nics , use switch independent add virtual interfaces team... these virtual nics found in network connections.. can treat if physical nics , assign ips them

on side note wrt comment on vmware being simple use... bear in mind...

these simple cluster setups covered in length within mcse 2012 course , certification.... time familiarise content within course , put down test king papers....

Windows Server  >  High Availability (Clustering)