HPE StoreVirtual Storage / LeftHand
cancel
Showing results for 
Search instead for 
Did you mean: 

HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

mdmazher
Frequent Visitor

HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

Dear All,

 

Could you please help me out how to setup HP P4500 with 5 Hyper-V R2 host failover cluster using CSV feature.  If anybody have step-by-step instructions and best practice.


This is my first time setup using HP Lefthand P4500 for Hyper-V R2 failover cluster.

We already configured the HP P4500 in a cluster

Node 1 IP : 192.168.1.11
Node 2 IP : 192.168.1.12
VIP    IP : 192.168.1.15


Below is our hardware setup:-


1xHP C7000 Enclosure
5xHP BL380 G7
2xHP P4500 G2 Cluster
2xHP Procurve Switch with 10Gb for iSCSI traffic
2xCisco switches with 1GB for CSV, Live Migration traffic
2xCisco Core Switches with 2 10Gbps for Management and VMs traffic


We’ve seven NIC’s available in each Hyper-V host

2 NIC for Domain Access and Management
2 NIC for Live Migration + CSV + HB
2 NIC for Production VM’s (8
1 NIC for iSCSI (Using only 1 nic because Microsoft is not supporting Teaming for iSCSI network)


We are using only 1 NIC for iSCSI network still we have to install HP DSM MPIO on each Hyper-V host?

 

I'm confused about HP DSM, Flow Control, Jumbo frame, iSCSI teaming.

 

If we use two nics for iSCSI network on same subnet then I am getting warnings both IP's on same subnet during Microsoft Failover Validation check. How to resolve this issue?


I greatly appreciate all your suggestion/advice on how to setup this.

6 REPLIES
Emilo
Trusted Contributor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

At this time, NIC teaming isn't supported for connectivity to iSCSI. If you want redundant connections, you should use the Microsoft Multipart I/O (MPIO) component, which allows multiple paths to a storage platform.

 

 regarding HP DSM, Flow Control, Jumbo frame, iSCSI teaming.

You will need to install the HP DSM and configure it.

 

You should turn on flow control on the all the ports that are on the SAN network. Flow control must be enabled on the switches.  You will need to configure each NIC separately to enable flow control and jimbo frames. Jumbo frames can add complexity to the network as you have to insure that it implemented end to end. You could certainly do your initial implementation with default frame size then when you have it stable and configured correctly you can always add them latter. The easiest thing to do is create the BOND using ALB but with the 10gb cards you will need to make sure you have the latest firmware revisions..

 

So to keep it real simple setup you NIC bond with default frame size

Flow control enabled on the receive

Set the bond to failover

 

Here is the link to the fw upgrades for the 10gb cards

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=4324629&prodNameId=4324630&swEnvOID=54&swLang=8&mode=2&taskId=135&swItem=co-99913-1

 

P4000 Series Windows Solution Pack release notes this document contains the information on dsm/mpio setup

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02076582/c02076582.pdf

its a little dated so Ill try to find a newer one.

Anyway that's a start for  you

 

 

 

Emilo
Trusted Contributor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

mdmazher
Frequent Visitor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

Dear Emilo,

 

Thanks for the HP DSM/MPIO document and other suggestion.

 

Still I have doubts about iSCSI NICs, Below is my network configuation details:-

 

We already configured the HP P4500 in a cluster bonding using ALB :-

Node 1 IP        : 192.168.1.11/24
Node 2 IP        : 192.168.1.12/24
Cluster VIP IP : 192.168.1.15/24


Hyper-V R2 Hosts:

2 NIC User/Management Team Network: 172.16.10.0/24

2 NIC Heartbeat/Live Migration Team Network: 10.0.0.0/24

1 NIC iSCSI1: 192.168.1.51/24

1 NIC iSCSI2: 192.168.1.52/24


As you can see both iSCSI networks are on the same subnet, which is against Hyper V R2 cluster best practices, and is causing the validation wizard to fail - when I tried to use a different subnet on iSCSI2 interfaces, then I couldn't connect to the P4000 SAN - I could only get iSCSI to connect to the VIP IP.

 

Can anybody help me out of this issue? Can anyone implemented the setup same like ours.

 

Regards,

Mazher.

Emilo
Trusted Contributor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

Hello,

 

I believe you do want it to connect to the SAN VIP.

Have you implemented MPIO?

You can always call in to the HP P4000 help line and have them look at the configuration.

 

mdmazher
Frequent Visitor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

Hi,

 

  •  Yes, I want to connect to the HP P4000 SAN Virtual IP (VIP).
  • No, I did not implement the MPIO, I dont know how to implement this,  HP engineer only installed the HP_DSM_Installer_9.5.0.981 software on all Hyper-V host and left. Please help me how to configure this.
  • Can you please provide me the HP P4000 helpline number.
  • I am requesting you all to help me out from this issue.

 

Emilo
Trusted Contributor

Re: HP P4500 G2 Virtulization SAN, HP C7000 Enclosure with 5x BL380 G7 server running Hyper-V R2..

OK here you go.

Microsoft iSCSI Software Initiator Version 2.X Users Guide

www.microsoft.com/download/en/details.aspx?id=18986

Read the section on how to setup MPIO

it has step by step intructions.