I have been tasked with setting up a Hyper-V R2 3 node failover cluster. I have very limited clustering or Virtualization experience. So here I am asking for some Best Practices and if my implementation will work.
3 HP DL380 G8 with 1 4p onboard nic and 1 4p pci nic
1 HP D380 G8 with 14p onboard nic (used for VMM)
Dual HBA - SAN
My network team carved out several VLANs for me but they are NOT trunced.
SAN Team will setup all SAN connections
So here is my plan.
1 NIC - Management, 1 NIC - Backup, 1 NIC - Live Migration, 1 NIC - CSV/HB, 1 NIC - VM
Here is my confusion - I was given IP address ranges for the Management, Backup, VM, HB networks but none for the Live Migration. I was told by the networking team that internal non routable communication is setup as layer 2 and I could pick any IP range I wanted.
All the reading I have been doing on Hyper-V seems that every setup with LM has an IP range associated with it. So should I request an IP range from them or go ahead and pick an IP range (excluding the internal ranges like 192.168..etc).
This cluster will all be in the same datacenter and in the same site and will host currently planned 10 - 15 VM.
Thanks for any suggestions/Guideance
Nick
Nick