Hi. If I can start by explaining the Server 2012 Hyper-V clustering set up I've just implemented (not necessarily 100% best-practice):
- 2 x Dell R720 hosts, 8 x NIC ports (1 PCIE, 1 On-Board; 1 x 2-port LAN team spanning both cards, 1 x 2-port CSV team spanning both cards, 1 x 2-port LiveMig team spanning both cards, 1 x individual iSCSI port on each card);
- 2 x EqualLogic PS4100E units, 2 x 1GB ports on each unit;
- 2 x stacked Dell 6224 switches w/ default and 3 x VLANS (CSV, iSCSI, LiveMig)
- Hosts have Dell Host Integration Tools; to confirm the answer in this link, the Dell HIT kit really does not like having iSCSI traffic on different subnets (learnt this the hard way, had a perfectly functioning cluster with a single iSCSI subnet, re-built to Windows standards (2 subnets) involving re-configuring hosts and switches, completely messed up HIT kit so had to rebuild again back to how it was);
- Physical host cabling is meshed onto both switches for resilience;
With iSCSI network on a single subnet, the hosts work just fine. I then started building up a 2-node Hyper-V guest cluster. With each node in a clustered role on the hosts, these also work fine (although again, Windows complained about the single iSCSI subnet but there's not much I can do about that as it's driven by the hosts).
My problem is running "Get-ClusterNetwork -cluster cdfwc06 | Sort-Object Metric | FT Name, Metric, AutoMetric". On the host cluster, the sequence of networks (lowest-highest value) is:
- CSV (cluster comms, no clients)
- LiveMig (cluster comms, no clients)
- iSCSI (disabled for cluster)
- LAN (cluster and client comms)
On the guest cluster however, it goes:
- CSV (cluster comms, no clients)
- LiveMig (cluster comms, no clients)
- LAN (cluster and client comms)
- iSCSI (disabled for cluster)
Anyone know which of these is right? Obviously the CSV and LiveMig subnets are fine, I'm just puzzled as to why the iSCSI and LAN order is different. The only difference is that obviously the Hyper-V guests don't have the Dell HIT kit installed. I've also looked up this link and it's really helpful, but doesn't explicitly adress this configuration issue.