We help IT Professionals succeed at work.

IP Storage Connections on LAN for ESXi

Mr_OCD asked
Last Modified: 2013-11-14
I am currently in the process of expanding our Virtual Environment that has grown substancially over the past twelve months. We have just taken delivery of an Overland SAN S2000 with high speed disks and is now configured but I am struggling how to setup the network side and am looking for ideas.

Outline of environment:

- 3 x ESXi 4.0 hosts each with 4 NICS
- 1 SAN with 6 NICS
- 1 subnet

All iSCSI traffic and Management traffic in the past have gone down the same NIC's / Switches on the LAN and due to the size of the virtual environment network performance issues were not a problem but they certainly are now ...

So we need to seperate the iSCSI traffic with dedicated NICS that directly attach to the SAN off the LAN to improve performance.

I have a spare procurve to use if needed. (mostly likely)

How would you configure using the above information and why?

500 points for this as I've been tieing my head in knots trying to come to a conclusion!
Watch Question

AWS Solutions & Security Architect
Unlock this solution and get a sample of our free trial.
(No credit card required)
Top Expert 2010

I would create seperate isolated networks (VLANs) for your iSCSI storage. Assuming two storage processors in your SAN, I would put each SP onto a seperate network (configure VLANs on your procurve to isolate them from one another) - then use two NICs on each of your ESXi boxes - one into each VLAN.

This will allow you take advantage of multi-pathing for performance, as well as fault tolerance.

Good Luck
Top Expert 2010

Note that you will need to present your datastore volumes to both storage processors...


Procurve is a 1GB switch... I like the idea of a seperate vswitch on each host specifically for IP Storage.. will be obviously to any Staff looking at the configuration what the vswitch is for as well.

I presume would just set static IP addresses on the san and ESXi NIC's which connect to the switch then ensure the switch is routing properly? Is that it?!
Top Expert 2010
Unlock this solution and get a sample of our free trial.
(No credit card required)
Justin CAWS Solutions & Security Architect

If you go with the seperate vSwitch and use the Procurve to create a storage network, you can just use non-routable IPs that are within the same subnet.  Ideal, you don't want to route storage traffic, so it's a general best practice to keep the iSCSI traffic within the same layer 2 subnet (which is what you get with a single non-routing switch).

Once that is configured, you'll have to make sure your iSCSI LUNs are presented to the ESXi initiators like bgoering said above, then you should be able to see your storage and access it.  


SAN only has one storage processor (although a second can be installed in the future) ...

Existing LAN is on ... to keep it simple planned to keep all on same subnet with binded NIC's to the new vswitch / s on the hosts which connect directly to the SAN ports through the Procurve.

Make sense?

Looks like I was making it much harder than I needed ... always good to look at another persons approach!

You have both been very helpful so will split the points equally between you.
Top Expert 2010

You would need to go with a different IP subnet for your isolated storage network. Otherwise you would need to link the procurve to your existing switch because ESX will not be able to tell which network to use in order to access the storage. You already have a VMkernel port for the service console on your network.

Besides most of the benefit occurs because you are isolating your storage traffic from your other traffic. Use something like (anything so long as it is different) for your storage.

Good Luck


Ok Update time ...

Have setup the SAN's iSCSI NIC's on the subnet ... have created new vSwitches on the ESX hosts with NIC also set to subnet and everything is connected to the new switch installed...

I have created a test target on the SAN to see if it discovers under the iSCSI ESX initiator using the IP addresses setup for the iSCSI ESX traffic ... it is not discovering ...

Actually for the ESX initiator (dynamic list) should I be listing the SAN NIC's of the new ESX iSCSI traffic NICS?

Top Expert 2010

Yes, enter the IP address(es) of the SAN for dynamic or static discovery
Top Expert 2010

Guess I should add that on the SAN be sure to present to the iqns for each esx server that will share the storage and allow the ESX IP addresses. Are you using any security? chap?


Ok thanks. It seems I can see the SAN now but have network issues which I'm resolving now so should be fine once that is sorted. ESX isnt complaining anyway.

No CHAP setup.

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.