Dell have just installed a new EQL PS SAN and configured it for our 5 x ESXi 5.0U1 hosts. Each host has 2 dedicated 10GB NICS on a dedicated vswitch for the iSCSi connections to the SAN. MPIO is via the add-on Dell MPIO driver.
They are configured in a 1:1 way to 2 VMK ports iSCSi1 ands iSCSi2 as per usual. However since Dell left I have come across a Dell/EQL white paper (TR1075-Configure-iSCSI-Connectivity-with-VMware-vSphere-5.pdf) which says that a separate vmk port should be configured to maintain "pingability" of the iscsi ports during failure/failover. This port should have an ip address on the iSCSi subnet and the 2 10GB nics should be active in the team but not be bound to the sopftware iSCSi adapter. It should also be the lowest vmk port no.
The following posts in various net forums seem to suggest this is vital:-
If it is there it is easy to create the additional vmk but how would I make it the lowest port without deleting the existing ports and interupting SAN access.
ESXi 5.1 does resolve the issue, so the Storage Heartbeat Kernel (SHB), is no longer required.
However, with ESXi v5.0 you do not have to delete both VMK ports and start from scratch. You can unbind the lowest VMK port via the ESX GUI. Then modify the NICs so that both are active. Then create a NEW VMK port in that subnet that's is bound to the iSCSI HBA to replace the lowest VMK port used for SHB.
It have to be the lowest VMK # of all your iSCSI ports, so you have to remove the 2 existing VMKs first and start from scratch. Reason is that vSphere use the lowest one to try the access the array when discovering/scaning the volumes on the EQL. If this pNic, Cable, pSwitch goes down and you press the Rescan button within vSphere you get into trouble.
With vSphere 5.1 this is not necessary any more so you may consider and upgrade to the latest version.
Thanks for the quick response. Rather than delete both existing iscsi vmk ports on the switch, would unbinding and deleting the existing lowest port i.e ISCSI1/vmk1 , add the heartbeat port as vmk1, then recreating ISCSI and rebinding it work? That would seem to maintain SAN access throughout
I've been told that as of ESXi 5.1.0 the storage heartbeat is no longer needed due to a change in how ESXi responds to pings or so.
Member since 2003
I currently have two PE R910's connected via stacked PC 6224's to an EQL PS4100X.
My vSwitch for iSCSI was originally configured by Dell PRIOR to vSphere 5.1 as follows:
Both hosts are configured the same.
Network Adapters: vmnic4 and vmnic5
* MTU 9000
* Active Adapters vmnic4, vmnic5
* Load Balancing: Route based on the originating virtual port ID
VM iSCSI Network
* Active Adapter vmnic5
* Active Adapter vmnic4
With the enhancements provided in vSphere 5.1 is it safe to simply delete the SHB VMKernel port on each host?
On your ESX iSCSI, you show both NICs as "active", only one can be active, the other must be UNUSED.
Re: SHB. Yes, once upgraded to 5.1 you can delete the Storage Heartbeat VMK port. It does no harm, so no need to rush to remove it.
My apologies, that was a typo. On iSCSI2 vmnic5 is active while vmnic4 is unused. On iSCSI1 vmnic4 is active while vmnic5 is unused.
Thank you for the quick response! Also thank you for the other information you've posted within the forum relating to setting LRO to zero, changing settings with respect to Round Robin, etc.
You are very welcome!
I'm glad I could help out.