VMware Cloud Community
jdixon86
Contributor
Contributor
Jump to solution

ESX with iSCSI & LACP

I have some questions I wanted to ask and try to learn before I started this project. Right now we have two ESX servers located on one switch. Our VM's are using different VLANs per customer.

Here is going to be our new setup that I have planned:

  • (1) HP StorageWorks P2000 G3 iSCSI SAN
  • (2) Cisco/Linksys SRW2024P switches (Supports VLAN, LAG, LACP, Jumbo Frames)
  • (3) HP Proliant DL360 G6 servers
  • Each server will have 3 network cards
  • (2) Sonicwall routers

How exactly do I get redunandcy out of the iSCSI traffic? Using LACP on the switches I would connect the swithes together right? So SW1 Port 1 goes to SW2 Port 1 and the same for Port 2.

Then on the ESX side I would team two NICs together for the iSCSI traffic. I would use IP Hash. I would connect NIC #1 to SW1 and connect NIC #2 to SW2. So technically I could pull out the cord on NIC#1 and the VMs should be able to run due to the multiple paths right?

If I'm way off please let me know. I want to be able to lose one switch, lose one NIC and still be able to run without a hiccup.

0 Kudos
1 Solution

Accepted Solutions
illvilja
Hot Shot
Hot Shot
Jump to solution

Hi,

Attaching a great document to help you implement the P2000 with vSphere.

It is generally recommended to use multi-pathing instead of bonding/team.

View solution in original post

0 Kudos
3 Replies
illvilja
Hot Shot
Hot Shot
Jump to solution

Hi,

Attaching a great document to help you implement the P2000 with vSphere.

It is generally recommended to use multi-pathing instead of bonding/team.

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

I agree with the other poster, follow the vendors best practices guides.

Regarding LACP. ESX(i) does NOT support LACP, neither with standard vSwitches nor with vDS! Only the Cisco NEXUS 1000V add-on supports LACP.

André

jdixon86
Contributor
Contributor
Jump to solution

Thanks for the document! Exactly what I needed!

0 Kudos