Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Server 2012 Hyper-V Cluster Network Configuration

$
0
0

I have not been able to find any documentation that explicitly says if my network configuration is supported or not. It passes cluster validation but after a crash last weekend I am questioning it.  Hopefully one of the experts here can chime in.

Here is our setup:

Server 2012 Hyper-V cluster, two nodes with a disk witness.  Dell R520 Servers and a Dell Equalogic iSCSI SAN.  CSV and witness disk are running on the SAN (on different volumes).  Currently running four VMs, will expand to eight, possibly nine in the near future.

Each host has (all gigabit):

a 4-port NIC dedicated to the SAN using Dell mpio on its own subnet

a 4-port NIC team dedicated to the VM network

a 2-port NIC team for management, heartbeat and live migration

All are connected to a Dell two-switch stack with load balancing and failover at the switch level.  All teams are using link aggregation and the SAN connections are using aggregation and jumbo frames.

My concern is having the live migration network on the same network team as management.  I know this is not recommended but I have not seen this configuration listed as "not supported" either.  Redundancy shouldn't be an issue with failover at the team and the switches.  I am concerned with possible bottle-necking though.

If I were to add QoS to the 2-port team to cap the management and heartbeat bandwidth would that be enough?  How much of a cap should I set?

Or should I break the team and create another network exclusively for live migration?

Or is the current configuration okay?


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>