Read the first blog post here about Dell MEM and ESXi 5.5

As part of the EqualLogic MEM script it creates a new vSwitch and also its iSCSI VMkernel’s, but due to that script not currently being compatible with ESXi 5.5 U2 we had to manually create the connections. Below is the setup we have used and a few differences compared to the Dell EqualLogic best practice document.

In the document it states that the heartbeat connection is no longer required for ESXi servers of version 5.1 or above. I had issues with this and found that if a switch that one of the adapters connected to failed, the pings would stop to the storage device and ESXi would report that all paths were down for the EqualLogic array, and therefore lose access to the datastore. I added a heartbeat connection in and was able to keep a path active when an adapter failed. Below will cover the settings I have in place and the tests I did to determine successful failover in various scenarios

The Storage Heartbeat VMkernel port is no longer required for ESX servers running version 5.1 and greater

vSwitch Setup

  • Create a new Standard VMkernel vSwitch on your host and assign two or more network adapters to it (these are obviously the adapters that connect to your storage network where the EqualLogic sits)
  • Name the adapter “EQL Heartbeat”
  • Assign an IP to the EQL Heartbeat VMkernel port
  • Finish the setup screen
  • Find the vSwitch in the Networking window and select Properties
  • Add a new VMkernel port to the vSwitch; press Add, select VMkernel, label it EQL_1
  • Assign an IP address (same subnet as your heartbeat port), finish the setup
  • Repeat the process again and label the new VMkernel EQL_2, again this needs to be in the same subnet as the other two VMkernel ports

Once you have done that you should have something that looks similar to this;

vSwitch Layout
vSwitch Layout

We need to make a few more changes to this vSwitch;

  • Edit each of the items in the screen shot to have an MTU of 9000 (your switch must also support this!)
  • Edit vSwitch > NIC teaming tab, all adapters should be active
  • Edit EQL Heartbeat > NIC teaming tab, all adapters should be active (will most likely be grayed out as inherits settings from vSwitch)
  • Edit EQL_1 > NIC teaming tab, under Failover Order tick Override switch failover adapter, keep one in Active and move the other to unused
  • Edit EQL_2 > NIC teaming tab, under Failover Order tick Override switch failover adapter, keep one in Active and move the other to unused – this needs to be different to the one used in EQL_1

EQL_1 Properties
EQL_1 Properties

EQL_2 Properties
EQL_2 Properties

iSCSI Software Adapter

If you don’t yet have an iSCSI software adapter now is the time to add one in, once you have done that select it and press Properties. Under Network Configuration and press Add, select the two adapters you just configured (EQL_1 and EQL_2).

While you are here also add in your EqualLogic’s group IP address in to the Dynamic Discovery tab

Setup VMware Round Robin

The next steps I have documented in the post Dell MEM v1.2 and ESXi 5.5 U2, so I wont cover them again here. These steps setup cover the remaining recommendations from Dell.

Testing Failover

To confirm the above settings I did the followings tests to confirm failover – during these tests you should not have all paths down.\ These tests make the assumption that you have at least two switches, two network adapters and two controllers in your EqualLogic, and that you return to default before running the next test.

  • Remove a network cable from the host (which connects to the storage network)
  • Remove the other network cable
  • Power off 1 switch
  • Power off other switch
  • Disconnect controller
  • Disconnect other controller

If you do encounter an APD scenario double-check your cabling, as per this diagram from Dell, a long with the heartbeat adapter the cabling also caused a problem. This was resolved with the help of this diagram.

PS4100 Cabling
PS4100 Cabling

Share to TwitterShare to FacebookShare to LinkedinShare to PocketCopy URL address
Written by

Sam Perrin@samperrin

Automation Consultant, currently working at Xtravirt. Interested in all things automation/devops related.

Related Posts