Windows 2012 server cluster configuration

hi gurus

i have quick question. setting brand new infrastructure. consists of 2 servers, 2 switches , iscsi san. have not done hyper-v clustering before , hence have following questions. server has 4 x 1gb nics , 2 x10gb iscsi nics.

• i believe can use mpio on iscsi nics. 1gb nics can use 2 vm access , 2 live migration? best or logical practice in regard?
• should cluster nodes on different subnets/vlan?
• how tell hyper-v network use live migration?
• i believe minimum need create 2 luns, 1 quorum disk , other vm storage. of these need csv?
• if use nics explained above, should iscsi, live migration, vm on separate subnets/vlans?
• also necessary use smb quorum disk , vm storage, or provisioning lun , making them available server enough?

any appreciated. in advance.

regards

a lot of things you're asking not have quick answers. deep architectural issues have more few considerations. recommend if you're in hurry, contract in expert. otherwise, spend time finding materials, doing research, , testing.

i can give few pointers, should not end of search:

• yes, can use mpio on iscsi, , should. how use depend on find in discovery , needs are. can storage system come anywhere near saturation of 10gbps link? vms need kind of storage horsepower? better served aggregating 1 gbps links storage , using 10 gbps communications? mix? of architectural consideration.
• the cluster nodes should not on separate subnets unless it's absolutely unavoidable. real use when nodes geographically dispersed.
• failover clustering determines networks use cluster live migrations, not hyper-v. use networks node in failover cluster manager. there powershell ways it, fcm easier understand in regard.
• overall, use or non-use of csv architectural consideration. quorum disk cannot csv.
• do not confuse cluster networks vm networks. vms , cluster networks can share subnet, if desired. whether or not architectural decision, although people not use networks dedicated live migration , cluster communications other purpose. management network can in same subnet vms. hyper-v admins use cluster networks 3 distinct purposes: management, live migration, , else. unfortunately, confusingly-worded documentation confused lot of , find lot of talk special cluster networks dedicated csv; there no such thing. csv traffic falls "everything else" category. people wind architecting clusters 2 "everything else" cluster networks; 1 of them has human label "csv", cluster uses them both wants to. cluster networks configured in failover cluster manager (or powershell). there more information on can provide in little forum interaction, go research , testing.
• you cannot use smb disk witness. disk witness can lun. have never tried using disk witness other purpose; it's not recommended , not supported so. may use smb file share witness in lieu of disk witness, although disk witness preferred. file share witness can on anything, anywhere, can expose standard windows smb share. smb shares vms must smb 3 or higher. however, if you're exposing luns directly hosts, show local disks , there's no purpose in trying have nodes connect them on smb 3. convert them csv, or not, depending on architectural plans. again, there's lot of information here , can't adequately explain in little bullet point.

---

eric siron altaro hyper-v blog
independent blog contributor, not altaro employee. solely responsible content of posts.
"every relationship have in worse shape think."

Windows Server  >  Hyper-V