What to configure to support DELL SAN Storage?

This is a project in which 2 DELL Poweredge R720 servers, 1 DELL Equallogic 4100 with 2 controllers, and a DELL Powerconnect NX2024 switch. The servers will be setup as MS HyperV 2K12 R2 with hyperv server role. MS clustering will also be setup for VM failover. These 2 HyperV servers will be connected to the equallogic 4100 san with 2 iSCSI connections for HA. I know that on equallogic, I have set the access permissions for the server's NICs, then how should I configure the servers to support the SAN? just install MPIO? or else?

Thanks in advance.
LVL 1
MichaelBalackAsked:
Who is Participating?
 
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Hi,

You have to separate the storage network from the heartbeat!!

You can use NIC teaming for both NIC1 and NIC2 then creat Vethernet port for Management, CSV and Live migration network

Here is some guides:

Network Recommendations for a Hyper-V Cluster in Windows Server 2012

Windows Server 2012 Hyper-V Converged Fabric

Hyper-V: Live Migration Network Configuration Guide

Failover Cluster Network Design with Hyper-V–How many NICs are required?

Best Regards.

Salah
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Did you download the HiT from Dell Equallogic, and follow the guides?

Download and install the Host Integration Kits, and it will guide you and install MPIO.
0
 
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Hi,

You will have windows server hosting the hyper v use SAN for OS boot or you will have local disks??, you will use CSV or attach the VM to the SAN directly??

Please give more explanation regarding you setup so I can help you.

Else attached some documents describing how to Set Up the EqualLogic and Failover Cluster on Dell PowerEdge(I never use before but kept with other documents!)

Good Luck.

Salah
Setting-Up-the-EqualLogic---Hype.docx
Configuring-a-Microsoft-Windows-Server-2
configuring-hyper-v-failover-cluster-on-
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
MichaelBalackAuthor Commented:
Hi Salah,

Both hosts have their os install in local disks.
All VMs will be hosted in csv.

As for the san, 2 volumes will be created.host 1  and 2 will hosted 1 volume each. As for the san connections, 2 nic connections from each hosts directly to san controllers.

The objective is, if host 1 is down or disconnected, all volumes/VMs will be failover to hist 2, and vice versa.

Thanks,
0
 
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Hi,

I think documents that I provided will help you setting up your environnement, you have to follow this order:

Install Hyper-v role in both servers
Install Cluster fail-over in both servers
map ISCSI volumes to your server
validate the cluster configuration
create the cluster
create VM role from fail-over cluster management console so the VM will be high available automatically,
define preferred host for VMs (in order to use both servers, split the number of VM and run each part preferred in one host, if any host failed the other on will take the fail-over and rollback once the host is up again)
If you still need more help, I can share some IBM guides for reference.

Best Regards.

Salah
0
 
MichaelBalackAuthor Commented:
Hi Salah,

Please see the connectivity as attached.

Eash hyperv host has 4 NICs. NIC1 for hyperv host, NIC 2 for vSwtich, NIC3 for iSCSI2 & heartbeat, and NIC4 for iSCSI1. HyperV host and VMs are in one segment, and iSCSI storage is on another segment.

I managed to run and stop at:

Install Hyper-v role in both servers
Install Cluster fail-over in both servers
map ISCSI volumes to your server
validate the cluster configuration

When I attempt to create cluster, it failed.

From the cluster validating results, it looks like the IP/network may have some problems.

Appreciate your help!
EE---SAN-Clustering-Network-Connectivity
CFE---Cluster-Validating-results.pdf
0
 
MichaelBalackAuthor Commented:
Hi Salah,

thanks for the articles. Let's me go through them and get back to you later.
0
 
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Good luck!
0
 
MichaelBalackAuthor Commented:
Hi Salah,

Please see the updated network connectivity as attached.
EE---SAN-Clustering-Network-Connectivity
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
looks good for a single physical switch. (which is you single point of failure!)
0
 
MichaelBalackAuthor Commented:
Hi Andrew,

Precisely, the ideal way is having 2 switches in stack. But, I was given just one physical switch.
0
 
MichaelBalackAuthor Commented:
Hi Salah & Andrew,

Please see the network adapter configuration and failover cluster section as attached.
EE---Network-Configurations-for-SAN-and-
0
 
MichaelBalackAuthor Commented:
Hi Salah & Andrew,

Please enlightening...
0
 
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Hi,

The attachment is without extension?? which type of file??

BR
0
 
MichaelBalackAuthor Commented:
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you run the Failover Clusterr Wizard, does it include it in the report?
0
 
MichaelBalackAuthor Commented:
Hi Andrew,

The report on wizard didn't stated any thing about using a single switch.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I was not referring to the single switch, but it should show all the networks in use ?
0
 
MichaelBalackAuthor Commented:
Hi Andrew,

Please see the create cluster report:
CreateCluster.txt
0
 
MichaelBalackAuthor Commented:
Hi Andrew,

Please see the cluster validating report
ClusterValidatingReport.pdf
0
 
MichaelBalackAuthor Commented:
Hi Andrew and Salah,

I got the updates, and will update you guys in 12 hours' time.
0
 
MichaelBalackAuthor Commented:
Hi Andrew and Salah,

The clustering is working now. The critical part in on the network segment. Besides the 2 SCSI segment, if i configure different network segments for CSV, LiveMigration, and Management, I would see them appear in the cluster networks. Even now all CSv, livemigration and management are on the same network segment, the clustering still works.

In cluster manager, I tried live migration, quick migration and storage migration, all working fine.

thanks,
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you tested Cluster Update Manager (if you had installed it!), and also check for HA failover.
0
 
MichaelBalackAuthor Commented:
Hi Andrew and Salah,

I think I forgot to mention, the root cause of cluster wizard is because initially, one of the ms hyperv 2012 R2 server is working as the dc. I did a simple test, when running the wizard, i just add in the other hyperv host that is not DC, and the cluster can form. But, attempt to add in the hyperv with DC, wizard failed to proceed.
0
 
MichaelBalackAuthor Commented:
Thanks for both experts in pinpoint the root causes of the problem.

Salah show the setup of a teaming of multiple NICs, with Vswitch that carried management os traffic for csv, livemigration and management. Without these info, a network part must be one of the failure to form cluster.

Andrew pinpoint the problem is on the switch.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.