Hyper V set up with failover and SAN storage

Rick_Penney
Rick_Penney used Ask the Experts™
on
Hi, I’m after some advice on HyperV setup with SAN
We currently have one Proliant Gen10 running HyperV
The first two NICs are Teamed together and plugged into Vlan 1. (Host management network team)
Two further NICs are teamed together and used for the Virtual switch. (Virtual Machine Network Team).
All VMs are currently stored locally on the Server

We will be introducing a second Proliant Gen10 and a HP MSA2052 SAN
The goal is to move the VMs to the SAN and set up failover between the two Hyper V hosts.
Does the second Hyper V Host get setup the same as the first Hyper V Host?
(Host management network team) and (Virtual Machine Network Team) plugged into a switch(s).

Then connect both Hyper V hosts directly to the SAN using the ISCSI controller ports?, or do the ISCSI network ports on the HyperV hosts and the ISCSI ports on the SAN both plug back into the network switches?
If it’s the latter, do we still need the (Virtual Machine Network Team) ?

Some guides mention MGMT, are they referring to MGMT in respect of having access to the server for say ILO access, or are they referring to connecting them to the primary VLAN for normal data traffic

Kind regards
Rick
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2014
Commented:
Unless you have already bought the MSA you may be better off buying the SAS rather than iSCSI variant. It is limited to 4 hosts as there are only 4 host ports on it but the bandwidth is higher. Whether iSCSI or SAS though you should buy an additional dual-port NIC or HBA for each server and direct connect them, no sense going through switches until you run out of host ports. Bear in mind that each cable is a separate subnet uf directly connected. Rather than teaming you use MPIO for iSCSI or SAS connections.
Commented:
first thing you have to configure Hyper -V failover
storage will be configured connect through ISCSI and the subnet should keep separate
you can connect through LAN switch but recommend is SAN switch.

all the best
Director, Information Systems
Commented:
"Does the second Hyper V Host get setup the same as the first Hyper V Host?
(Host management network team) and (Virtual Machine Network Team) plugged into a switch(s).
"
This is up to you, but yes, I try to make my hosts as identical as possible.

"Then connect both Hyper V hosts directly to the SAN using the ISCSI controller ports?, or do the ISCSI network ports on the HyperV hosts and the ISCSI ports on the SAN both plug back into the network switches?
If it’s the latter, do we still need the (Virtual Machine Network Team) ?
"
I'd recommend two switches between your hosts and your SANs, with a connection from each host and each SAN going to each switch, and a cross-over between switches.  This gives you the most redundancy, if that's what you're after.

"Some guides mention MGMT, are they referring to MGMT in respect of having access to the server for say ILO access, or are they referring to connecting them to the primary VLAN for normal data traffic"
The latter, though some folks set up a VLAN just for management purposes.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Top Expert 2014

Commented:
I'd never put management ports on the main vLAN, so me sites even have a separate network for it to keep users from hacking the SAN's web management port.

Author

Commented:
Many thanks to everyone who has posted, its very much appreciated,
I did think they meant that MGMT was the main vlan.  With ref to Andyalder comment ref web management, the management of our switches are on a separate vlan, i will configure the SANs management port to be on this management vlan.

Andy has suggested direct connection and MPIO, I will have a look at a guide i've just seen on petri.com ref this.
Paul has mentioned connection with redundant switches, so i will look further into both setups.

Sajid Shaik M, many thanks, i will set up a seperate subnet as you say for the ISCI traffic.

The MSA 2052 has been supplied with a STP + 4 pack transceiver kit.

Thanks to all , regards
Top Expert 2014

Commented:
> The MSA 2052 has been supplied with a STP + 4 pack transceiver kit.

Can you get your money back on them or flog them on eBay? If you use direct connection you can use SFP+ cables.

From quickspecs:
Each MSA 2052 SAN controller can be configured with 2 or 4 SFPs.
For MSA 2052 10Gb iSCSI configuration user can use DAC cables instead of SFPs
SteveArchitect/Designer

Commented:
Apologies for throwing the obvious in, but I recommend designing the setup first (either yourself if you have the experience or by paying a consultant) and then buy the kit and do the work.

Assuming these servers (VMS) are running stuff critical to a company, a lot of people's jobs may depend on those servers not being affected/broken.

Author

Commented:
Thanks Andy, i'm not in a position to purchase any more equipment as this is one of three sites and budgets have been met.
We don't really need to run it at 10Gbps.
The servers have 8 NICs in total (4 spare), so we plan to connect using the STP transceivers in the SAN to the server either directly or via a switch
Thanks anyway

Author

Commented:
Thanks to all, i have a better understand of connectivity now and will close this case and try and assign points to all
kind regards
Rick
Top Expert 2014

Commented:
The point was that DAC cables are cheaper than transceivers - 1 DAC cable Vs 2 transceivers and an Ethernet cable.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial