Did you follow the Equallogic setup guide for vSphere5? The screenshot of your vSwitch only shows a single vmkernel, but the network configuration tab shows 2.
Here is a pretty good guide for vSphere configurations for EQL: www.equallogic.com/.../DownloadAsset.aspx. Note: if you're using ESXi 5.1.x, you can skip the heartbeat that's mentioned there.
The 3 paths you can see is for the one datastore volume across 3 enclosures. I have rebooted several times due to implementing the DelayedACK and LRO settings you recommended. I cannot tell which adapter is making which connection. If I look in the EQL gui for the volume under connections I can typically see 3 connections for each server, 2 under 1 iscsi adapter IP address and 1 under the same server's other iscsi adapter IP address.
I thought using MEM that for any given volume/datastore I would see a path to each enclosure for each server adapter. Is that not the case?
Took your advice and opened a support case. Had someone from Dell EQL and ESX teams webex in and check the setup. They confirmed everything was set up correctly and also by disabling alternate adapters on a given server that they were still able to ping all the enclosures from the server shell.
Eventually they said that there was not a problem and the reason that I was not seeing all the paths to all enclosures was that the latest MEM (1.1.2) dynamically created the paths on load/request.
Thanks, I have asked for the case to be re-opened. Is it possible you can post a screenshot of what you see both at the ESX end i.e what you see in your system. I am very confused between what I should see undser the esx "manage paths" and the EQL connections.
Just to be clear In my case I have been looking from the ESX side and under the paths on device/datastore properties I expected to see 2 paths for each EQL member i.e 1 for each NIC, SO for a datastore across 3 members I would see 6 paths, which is not the case.
The server iscsi adapters are Broadcom 57810 GB adapters.
Double checked in each view as you said and each server iscsi adapter or datastore shows just one connection per server per eql member. Hopefully Dell support will either look again or escalate.
I think I mentioned before that the original dell engineer forgot to configure the storage heartbeat and that I had to delete the iscsi vswitch vmkernel ports, recreate them and add them back to the software adapter. That was all after MEM had been installed, so I suppose it's possible that that screwed up MEM. Do you think it is worth uninstalling MEM (how) and re-installing it on one of the servers to see if that sorts it out?
I think I made a mistake regarding the 6510. I just moved 2 6510 members into the same pool, created a volume and presented it to an ESX hosts as a datastore. On EQL I can see the volume is across both 6510 members and when I look at vsphere manage paths there are 4 which is what I am led to expect. i.e 1 path per member per server iscsi vmk.
When you say the 6110 works differently does that mean that it cannot take advantage of the MEM MPIO and have all paths active for greater I/O?
Dev Mgr
4 Operator
•
9.3K Posts
0
February 28th, 2013 09:00
Did you follow the Equallogic setup guide for vSphere5? The screenshot of your vSwitch only shows a single vmkernel, but the network configuration tab shows 2.
Here is a pretty good guide for vSphere configurations for EQL: www.equallogic.com/.../DownloadAsset.aspx. Note: if you're using ESXi 5.1.x, you can skip the heartbeat that's mentioned there.
gerrybarnett
129 Posts
0
February 28th, 2013 15:00
Don,
The 3 paths you can see is for the one datastore volume across 3 enclosures. I have rebooted several times due to implementing the DelayedACK and LRO settings you recommended. I cannot tell which adapter is making which connection. If I look in the EQL gui for the volume under connections I can typically see 3 connections for each server, 2 under 1 iscsi adapter IP address and 1 under the same server's other iscsi adapter IP address.
I thought using MEM that for any given volume/datastore I would see a path to each enclosure for each server adapter. Is that not the case?
gerrybarnett
129 Posts
0
March 1st, 2013 15:00
Don,
Took your advice and opened a support case. Had someone from Dell EQL and ESX teams webex in and check the setup. They confirmed everything was set up correctly and also by disabling alternate adapters on a given server that they were still able to ping all the enclosures from the server shell.
Eventually they said that there was not a problem and the reason that I was not seeing all the paths to all enclosures was that the latest MEM (1.1.2) dynamically created the paths on load/request.
Sound right to you?
gerrybarnett
129 Posts
0
March 2nd, 2013 11:00
Don,
Thanks, I have asked for the case to be re-opened. Is it possible you can post a screenshot of what you see both at the ESX end i.e what you see in your system. I am very confused between what I should see undser the esx "manage paths" and the EQL connections.
Just to be clear In my case I have been looking from the ESX side and under the paths on device/datastore properties I expected to see 2 paths for each EQL member i.e 1 for each NIC, SO for a datastore across 3 members I would see 6 paths, which is not the case.
thx
gerrybarnett
129 Posts
0
March 3rd, 2013 11:00
Thanks again Don,
The server iscsi adapters are Broadcom 57810 GB adapters.
Double checked in each view as you said and each server iscsi adapter or datastore shows just one connection per server per eql member. Hopefully Dell support will either look again or escalate.
I think I mentioned before that the original dell engineer forgot to configure the storage heartbeat and that I had to delete the iscsi vswitch vmkernel ports, recreate them and add them back to the software adapter. That was all after MEM had been installed, so I suppose it's possible that that screwed up MEM. Do you think it is worth uninstalling MEM (how) and re-installing it on one of the servers to see if that sorts it out?
gerrybarnett
129 Posts
0
March 3rd, 2013 13:00
Don,
The output from those commands from one of the servers (all 5 have the same issue) is below. AFAIR the procededure I followed was:-
- unbind both iscsi adapters (iscsi1/iscsi2) from the software iscsi adapter
- delete both iscsi adapter vmkernel ports from the vswitch
- create the storage heartbeat vmk
- recreate iscsi1 and iscsi2 vmk ports
- bind iscsi1/iscsi2 to software iscsi adapter
(iscsi1 and iscsi2 are vmnic8 and vmnic10)
~ # esxcli iscsi adapter list
Adapter Driver State UID Description
------- --------- ------- -------------------------------------------- ----------------------
vmhba41 iscsi_vmk online iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa iSCSI Software Adapter
vmhba32 bnx2i unbound iscsi.vmhba32 Broadcom iSCSI Adapter
vmhba33 bnx2i unbound iscsi.vmhba33 Broadcom iSCSI Adapter
vmhba34 bnx2i unbound iscsi.vmhba34 Broadcom iSCSI Adapter
vmhba35 bnx2i unbound iscsi.vmhba35 Broadcom iSCSI Adapter
# esxcli iscsi networkportal list
vmhba41
Adapter: vmhba41
Vmknic: vmk2
MAC Address: 00:10:18:d6:45:60
MAC Address Valid: true
IPv4: 192.168.100.31
IPv4 Subnet Mask: 255.255.255.0
IPv6:
MTU: 9000
Vlan Supported: true
Vlan ID: 0
Reserved Ports: 63488~65536
TOE: false
TSO: true
TCP Checksum: false
Link Up: true
Current Speed: 10000
Rx Packets: 635013
Tx Packets: 712656
NIC Driver: bnx2x
NIC Driver Version: 1.72.18.v50.4
NIC Firmware Version: FFV7.2.20 bc 7.2.25
Compliant Status: compliant
NonCompliant Message:
NonCompliant Remedy:
Vswitch: vSwitch2
PortGroup: ISCSI2
VswitchUuid:
PortGroupKey:
PortKey:
Duplex:
Path Status: active
vmhba41
Adapter: vmhba41
Vmknic: vmk3
MAC Address: 00:10:18:d6:46:90
MAC Address Valid: true
IPv4: 192.168.100.30
IPv4 Subnet Mask: 255.255.255.0
IPv6:
MTU: 9000
Vlan Supported: true
Vlan ID: 0
Reserved Ports: 63488~65536
TOE: false
TSO: true
TCP Checksum: false
Link Up: true
Current Speed: 10000
Rx Packets: 899200
Tx Packets: 1031192
NIC Driver: bnx2x
NIC Driver Version: 1.72.18.v50.4
NIC Firmware Version: FFV7.2.20 bc 7.2.25
Compliant Status: compliant
NonCompliant Message:
NonCompliant Remedy:
Vswitch: vSwitch2
PortGroup: ISCSI1
VswitchUuid:
PortGroupKey:
PortKey:
Duplex:
Path Status: active
~ #
esxcli iscsi physicalnetworkportal list
Adapter Vmnic MAC Address MAC Address Valid Current Speed Max Speed Max Frame Size
------- ------- ----------------- ----------------- ------------- --------- --------------
vmhba41 vmnic9 00:10:18:d6:46:92 true 0 0 1500
vmhba41 vmnic11 00:10:18:d6:45:62 true 0 0 1500
vmhba41 vmnic0 d4:ae:52:a6:50:90 true 1000 1000 1500
vmhba41 vmnic7 00:10:18:e5:8a:43 true 1000 1000 1500
vmhba41 vmnic4 00:10:18:e5:8a:40 true 1000 1000 1500
vmhba41 vmnic5 00:10:18:e5:8a:41 true 1000 1000 1500
vmhba41 vmnic6 00:10:18:e5:8a:42 true 1000 1000 1500
vmhba41 vmnic1 d4:ae:52:a6:50:91 true 1000 1000 1500
vmhba41 vmnic2 d4:ae:52:a6:50:92 true 1000 1000 1500
vmhba41 vmnic3 d4:ae:52:a6:50:93 true 1000 1000 1500
vmhba41 vmnic10 00:10:18:d6:45:60 true 10000 10000 9000
vmhba41 vmnic8 00:10:18:d6:46:90 true 10000 10000 9000
vmhba32 vmnic8 00:10:18:d6:46:90 true 10000 10000 9000
vmhba33 vmnic9 00:10:18:d6:46:92 true 0 0 1500
vmhba34 vmnic10 00:10:18:d6:45:60 true 10000 10000 9000
vmhba35 vmnic11 00:10:18:d6:45:62 true 0 0 1500
# esxcli iscsi logicalnetworkportal list
Adapter Vmknic MAC Address MAC Address Valid Compliant
------- ------ ----------------- ----------------- ---------
vmhba41 vmk0 d4:ae:52:a6:50:90 true false
vmhba41 vmk1 00:50:56:75:e5:5a true false
vmhba41 vmk2 00:50:56:7f:2a:5f true true
vmhba41 vmk3 00:50:56:69:6a:9d true true
vmhba32 vmk1 00:50:56:75:e5:5a true false
vmhba32 vmk3 00:50:56:69:6a:9d true true
vmhba34 vmk2 00:50:56:7f:2a:5f true true
gerrybarnett
129 Posts
0
March 3rd, 2013 14:00
esxi 5.0 u2.
Which bit of the output shows the problem, the esxcli iscsi networkportal list shows vmk1 and vmk2 as active and enable on the iscsi software adapter?
gerrybarnett
129 Posts
0
March 4th, 2013 00:00
Don,
Output below, also included an ( esxcfg-mpath -l)
Please run:
#esxcfg-vswitch -l
esxcfg-vswitch -l
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 128 4 128 1500 vmnic0,vmnic7
PortGroup Name VLAN ID Used Ports Uplinks
Management Network 0 1 vmnic0,vmnic7
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch1 128 13 128 1500 vmnic4,vmnic5,vmnic6,vmnic1,vmnic2,vmnic3
PortGroup Name VLAN ID Used Ports Uplinks
Production VM Network 0 0 vmnic4,vmnic5,vmnic6,vmnic1,vmnic2,vmnic3
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch2 128 6 128 9000 vmnic10,vmnic8
PortGroup Name VLAN ID Used Ports Uplinks
ISCSI1 0 1 vmnic8
ISCSI2 0 1 vmnic10
Storage_Heartbeat 0 1 vmnic8,vmnic10
#esxcfg-vmknic -l
esxcfg-vmknic -l
Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type
vmk0 Management Network IPv4 10.57.104.10 255.255.255.128 10.57.104.127 d4:ae:52:a6:50:90 1500 65535 true STATIC
vmk1 Storage_Heartbeat IPv4 192.168.100.40 255.255.255.0 192.168.100.255 00:50:56:75:e5:5a 9000 65535 true STATIC
vmk2 ISCSI2 IPv4 192.168.100.31 255.255.255.0 192.168.100.255 00:50:56:7f:2a:5f 9000 65535 true STATIC
vmk3 ISCSI1 IPv4 192.168.100.30 255.255.255.0 192.168.100.255 00:50:56:69:6a:9d 9000 65535 true STATIC
#vmware -v
vmware -v
VMware ESXi 5.0.0 build-914586
#esxcfg-mpath -l
esxcfg-mpath -l
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d010001,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1-naa.6090a0c85079c0ac570fb58b92013012
Runtime Name: vmhba41:C2:T0:L0
Device: naa.6090a0c85079c0ac570fb58b92013012
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079c0ac570fb58b92013012)
Adapter: vmhba41 Channel: 2 Target: 0 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d010001,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2 Alias= Session=00023d010001 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000002,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1-naa.6090a0c85079c0ac570fb58b92013012
Runtime Name: vmhba41:C1:T0:L0
Device: naa.6090a0c85079c0ac570fb58b92013012
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079c0ac570fb58b92013012)
Adapter: vmhba41 Channel: 1 Target: 0 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000002,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2 Alias= Session=00023d000002 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000001,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1-naa.6090a0c85079c0ac570fb58b92013012
Runtime Name: vmhba41:C0:T0:L0
Device: naa.6090a0c85079c0ac570fb58b92013012
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079c0ac570fb58b92013012)
Adapter: vmhba41 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000001,iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-acc07950c-123001928bb50f57-syn06esxvmdatastore2 Alias= Session=00023d000001 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d010002,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1-naa.6090a0c85079d05e570f958b920190ec
Runtime Name: vmhba41:C2:T4:L0
Device: naa.6090a0c85079d05e570f958b920190ec
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079d05e570f958b920190ec)
Adapter: vmhba41 Channel: 2 Target: 4 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d010002,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1 Alias= Session=00023d010002 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000002,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1-naa.6090a0c85079d05e570f958b920190ec
Runtime Name: vmhba41:C1:T4:L0
Device: naa.6090a0c85079d05e570f958b920190ec
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079d05e570f958b920190ec)
Adapter: vmhba41 Channel: 1 Target: 4 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000002,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1 Alias= Session=00023d000002 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000003,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1-naa.6090a0c850790082b312058c9201e0cf
Runtime Name: vmhba41:C3:T3:L0
Device: naa.6090a0c850790082b312058c9201e0cf
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790082b312058c9201e0cf)
Adapter: vmhba41 Channel: 3 Target: 3 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000003,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2 Alias= Session=00023d000003 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000001,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1-naa.6090a0c85079d05e570f958b920190ec
Runtime Name: vmhba41:C0:T4:L0
Device: naa.6090a0c85079d05e570f958b920190ec
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c85079d05e570f958b920190ec)
Adapter: vmhba41 Channel: 0 Target: 4 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000001,iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-5ed07950c-ec9001928b950f57-syn06esxvmdatastore1 Alias= Session=00023d000001 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d010002,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1-naa.6090a0c850790082b312058c9201e0cf
Runtime Name: vmhba41:C2:T3:L0
Device: naa.6090a0c850790082b312058c9201e0cf
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790082b312058c9201e0cf)
Adapter: vmhba41 Channel: 2 Target: 3 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d010002,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2 Alias= Session=00023d010002 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000001,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1-naa.6090a0c850790082b312058c9201e0cf
Runtime Name: vmhba41:C1:T3:L0
Device: naa.6090a0c850790082b312058c9201e0cf
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790082b312058c9201e0cf)
Adapter: vmhba41 Channel: 1 Target: 3 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000001,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2 Alias= Session=00023d000001 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000003,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1-naa.6090a0c850790069b312e58b9201b0fc
Runtime Name: vmhba41:C3:T2:L0
Device: naa.6090a0c850790069b312e58b9201b0fc
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790069b312e58b9201b0fc)
Adapter: vmhba41 Channel: 3 Target: 2 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000003,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1 Alias= Session=00023d000003 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000002,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1-naa.6090a0c850790082b312058c9201e0cf
Runtime Name: vmhba41:C0:T3:L0
Device: naa.6090a0c850790082b312058c9201e0cf
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790082b312058c9201e0cf)
Adapter: vmhba41 Channel: 0 Target: 3 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000002,iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-82007950c-cfe001928c0512b3-eql-dilib-ds2 Alias= Session=00023d000002 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d010001,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1-naa.6090a0c850790069b312e58b9201b0fc
Runtime Name: vmhba41:C2:T2:L0
Device: naa.6090a0c850790069b312e58b9201b0fc
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790069b312e58b9201b0fc)
Adapter: vmhba41 Channel: 2 Target: 2 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d010001,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1 Alias= Session=00023d010001 PortalTag=1
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000002,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1-naa.6090a0c850790069b312e58b9201b0fc
Runtime Name: vmhba41:C1:T2:L0
Device: naa.6090a0c850790069b312e58b9201b0fc
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790069b312e58b9201b0fc)
Adapter: vmhba41 Channel: 1 Target: 2 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000002,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1 Alias= Session=00023d000002 PortalTag=1
unknown.vmhba1-unknown.2:0-naa.6d4ae520a710be00187da3240617db76
Runtime Name: vmhba1:C2:T0:L0
Device: naa.6d4ae520a710be00187da3240617db76
Device Display Name: Local DELL Disk (naa.6d4ae520a710be00187da3240617db76)
Adapter: vmhba1 Channel: 2 Target: 0 LUN: 0
Adapter Identifier: unknown.vmhba1
Target Identifier: unknown.2:0
Plugin: NMP
State: active
Transport: parallel
iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa-00023d000001,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1-naa.6090a0c850790069b312e58b9201b0fc
Runtime Name: vmhba41:C0:T2:L0
Device: naa.6090a0c850790069b312e58b9201b0fc
Device Display Name: EQLOGIC iSCSI Disk (naa.6090a0c850790069b312e58b9201b0fc)
Adapter: vmhba41 Channel: 0 Target: 2 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Identifier: 00023d000001,iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1,t,1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:syn06srvesx1-3955d5fa
Target Transport Details: IQN=iqn.2001-05.com.equallogic:0-8a0906-69007950c-fcb001928be512b3-eql-dilib-ds1 Alias= Session=00023d000001 PortalTag=1
sata.vmhba39-sata.0:0-mpx.vmhba39:C0:T0:L0
Runtime Name: vmhba39:C0:T0:L0
Device: mpx.vmhba39:C0:T0:L0
Device Display Name: Local TSSTcorp CD-ROM (mpx.vmhba39:C0:T0:L0)
Adapter: vmhba39 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: sata.vmhba39
Target Identifier: sata.0:0
Plugin: NMP
State: active
Transport: sata
~ #
gerrybarnett
129 Posts
0
March 4th, 2013 08:00
Don,
PS6110XV
Thanks
gerrybarnett
129 Posts
0
March 4th, 2013 10:00
Don,
Is it the same with the 6510E coz that displays the same "symptoms"
gerrybarnett
129 Posts
0
March 4th, 2013 10:00
Don,
I think I made a mistake regarding the 6510. I just moved 2 6510 members into the same pool, created a volume and presented it to an ESX hosts as a datastore. On EQL I can see the volume is across both 6510 members and when I look at vsphere manage paths there are 4 which is what I am led to expect. i.e 1 path per member per server iscsi vmk.
When you say the 6110 works differently does that mean that it cannot take advantage of the MEM MPIO and have all paths active for greater I/O?