Link to home
Start Free TrialLog in
Avatar of halejr1
halejr1Flag for United States of America

asked on

iscsi connection between hp msa2312i and ESX Server

I have an ESX server running on HP, and an MSA2312i running in my network.  Currently no disks have been allocated on the MSA, the volumes and all that have been created, etc, however nothing has been assigned to a host.

What I am looking for is a "common sense" approach to assigning a volume to the ESX Server for storage.  Now I know that the specific device procedures are intricate, and I can deal with that, however I need the basic over view, and I will do the research to complete the process.

Here is what I have...

flat network:
192.168.1.0/24

ESX Host

Disk Array

an example of what I am looking for is the following:

ON MSA -- Do this first
Create VDISK
Create Volume
Assign ISCSI ID to Volume

ON ESX Server
go to Configuration
Storage
Add Storage
Input ISCSI ID to create Virtual Disk

your done... disk should work.

That's how simple I would like it.

Thanks.
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

That sounds just about right except on the ESX side you should enable multipath

iscsi vsphere

mpio p32-34

http://www.vmware.com/pdf/vsphere4/r40/vsp_40_iscsi_san_cfg.pdf
Oh, and don't forget to zone your ESX hosts and setup a separate VLAN or a separate network for the SAN.
Avatar of Member_2_231077
Member_2_231077

And add a second switch for redundancy, and 2 seperate VLANs really since the two controllers in the MSA should be on seperate subnets.
Avatar of halejr1

ASKER

Paul - thanks for the input... zone the esx - do you mean to just put the ESX on seperate subnet as well as the MSI?  and is this a requirement?  It's a small network 6 workstations, 2 virtuals, 1 MSI (2 controllers) 1 ESX, and 2 File Servers.  

Thanks again.

Andyalder, thanks too for the "Optimum" redundancy suggestion.
ASKER CERTIFIED SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Let me clarify, you should zone the LUNs for the ip address of the vmkernel ip address (that connects your iscsi software initiator)  on your SAN, the iscsi vmkernel ip address is what is talking to your SAN