vSphere Storage Appliance

 View Only

  • 1.  hardware vs software iSCSI initiator compatibility

    Posted Sep 13, 2010 06:10 PM

    Hello,

    I recently purchased an Infortrend ESDS-S16E-R1130 iSCSI array. I may not have done all my homework before purchasing because I am having a lot of trouble getting it working properly. I apologize if some of these questions might be self-explanatory.

    I just noticed that on the Compatibility Matrix it lists the configuration for this array as "HW iSCSI".

    However, I am using VMWare software initiator. I am able to see the LUNs from the array when I scan the HBA, but I typically get errors, timeouts, when trying to add the storage to vSphere.

    Couple questions:

    Does the above mean that it will ONLY work with a hardware iSCSI HBA? I had thought that hardware iSCSI HBA's offload the processing required for iSCSI and would improve performance. Curious why it just wouldn't work at all with the software initiator? The reason I ask is Infortrend insists that it should work with the Software Initiator.

    As a comparison I used the Microsoft iSCSI Initiator from within a VM and mapped to a LUN and everything seems to be working correctly. Because of this I am pretty certain the configuration on the array itself is correct, but trying to get it added as a Datastore has been a nightmare. Can anyone elaborate on the that certification note of HW iSCSI?

    I have 2 hosts, an ESX 4.0 and ESXi 4.1 host, both seem to behave the same way.

    One other thing of note, on the same iSCSI initiators on the hosts I am connecting to a Dell Equallogic PS5000 array with no issues.

    Thanks.



  • 2.  RE: hardware vs software iSCSI initiator compatibility

    Posted Sep 14, 2010 04:21 AM

    I seen some other devices listed with both SW and HW iSCSI so it's safe to assume that in your case the HW iSCSI is what the device is certified for. What kind of path are you using for the iSCSI and do you see anything in the vmkernel log?

    If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

    Twitter:



  • 3.  RE: hardware vs software iSCSI initiator compatibility

    Posted Sep 14, 2010 01:38 PM

    Yes, constant errors being dropped into the vmkernel log.

    The storage adapter shows 2 dead paths, but not sure why. screenshot attached.

    vmkernel log:

    Sep 14 09:22:13 CK-ESX02 vmkernel: 0:21:45:02.431 cpu0:4602)WARNING: NMP: nmp_path_claim_end: Device, seen through path vmhba33:C0:T2:L3 is not registered (no active paths)

    Sep 14 09:22:13 CK-ESX02 vmkernel: 0:21:45:02.432 cpu1:4602)WARNING: NMP: nmp_path_claim_end: Device, seen through path vmhba33:C0:T2:L3 is not registered (no active paths)

    Sep 14 09:17:17 CK-ESX02 vmkernel: 0:21:40:05.840 cpu4:4123)vmw_psp_fixed: psp_fixedSelectPathToActivateInt: Changing active path from NONE to vmhba33:C0:T2:L1 for device "naa.600d023100040def00000001506b1728".

    Sep 14 09:17:17 CK-ESX02 vmkernel: 0:21:40:05.843 cpu4:4123)vmw_psp_fixed: psp_fixedSelectPathToActivateInt: Changing active path from NONE to vmhba33:C0:T2:L2 for device "naa.600d023100040def000000007c2999e4".

    Sep 14 09:17:19 CK-ESX02 vmkernel: 0:21:40:07.815 cpu2:4098)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4100020df180) to NMP device "mpx.vmhba1:C0:T0:L0" failed on physical path "vmhba1:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    Sep 14 09:17:19 CK-ESX02 vmkernel: 0:21:40:07.815 cpu2:4098)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    Sep 14 09:22:13 CK-ESX02 vmkernel: 0:21:45:02.431 cpu0:4602)WARNING: NMP: nmp_path_claim_end: Device, seen through path vmhba33:C0:T2:L3 is not registered (no active paths)

    Sep 14 09:22:13 CK-ESX02 vmkernel: 0:21:45:02.432 cpu1:4602)WARNING: NMP: nmp_path_claim_end: Device, seen through path vmhba33:C0:T2:L3 is not registered (no active paths)