iSCSI issue

[Batistuta10]

Hi

In our test environment, I recently upgraded an esx4 update 2 host to esxi 4.1 update. Now the iSCSI storage can't be seen by the esxi host.

Model of the storage is A12E-G2121-2 and it is unsupported by VMWare but I would have thought that it will still work.

I have configured the iSCSI vmkernel and initiators exactly same as it was on ESX host. I get the following error when trying to scan the vmhba using ssh

~ # esxcfg-rescan vmhba34
Dead path vmhba34:C0:T1:L2 for device  not removed.
Device is in use by worlds:
Dead path vmhba34:C0:T1:L4 for device  not removed.
Device is in use by worlds:
Dead path vmhba34:C0:T0:L1 for device  not removed.
Device is in use by worlds:
Dead path vmhba34:C0:T0:L3 for device  not removed.
Device is in use by worlds:

~ # esxcfg-mpath -l
iqn.1998-01.com.vmware:pptestesx01-4e423439-00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.10,t,1-
   Runtime Name: vmhba34:C0:T1:L2
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba34 Channel: 0 Target: 1 LUN: 2
   Adapter Identifier: iqn.1998-01.com.vmware:pptestesx01-4e423439
   Target Identifier: 00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.10,t,1
   Plugin: (unclaimed)
   State: dead
   Transport: iscsi

iqn.1998-01.com.vmware:pptestesx01-4e423439-00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.10,t,1-
   Runtime Name: vmhba34:C0:T1:L4
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba34 Channel: 0 Target: 1 LUN: 4
   Adapter Identifier: iqn.1998-01.com.vmware:pptestesx01-4e423439
   Target Identifier: 00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.10,t,1
   Plugin: (unclaimed)
   State: dead
   Transport: iscsi

iqn.1998-01.com.vmware:pptestesx01-4e423439-00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.00,t,1-
   Runtime Name: vmhba34:C0:T0:L1
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba34 Channel: 0 Target: 0 LUN: 1
   Adapter Identifier: iqn.1998-01.com.vmware:pptestesx01-4e423439
   Target Identifier: 00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.00,t,1
   Plugin: (unclaimed)
   State: dead
   Transport: iscsi

iqn.1998-01.com.vmware:pptestesx01-4e423439-00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.00,t,1-
   Runtime Name: vmhba34:C0:T0:L3
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba34 Channel: 0 Target: 0 LUN: 3
   Adapter Identifier: iqn.1998-01.com.vmware:pptestesx01-4e423439
   Target Identifier: 00023d000001,iqn.2002-10.com.infortrend:raid.sn7531214.00,t,1
   Plugin: (unclaimed)
   State: dead
   Transport: iscsi

sas.5005076b0342483c-sas.6a2f6b07bb9adf-naa.600508e000000000df9abb076b2f6a00
   Runtime Name: vmhba1:C1:T0:L0
   Device: naa.600508e000000000df9abb076b2f6a00
   Device Display Name: Local LSILOGIC Disk (naa.600508e000000000df9abb076b2f6a00)
   Adapter: vmhba1 Channel: 1 Target: 0 LUN: 0
   Adapter Identifier: sas.5005076b0342483c
   Target Identifier: sas.6a2f6b07bb9adf
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Transport Details: 5005076b0342483c
   Target Transport Details: 6a2f6b07bb9adf

I have also attached the messages file if someone wants to see the logs

Any help would be much appreciated and let me know if more info is required.

Thanks

M

[jamesbowling]

Unfortunately with it being unsupported there are no guarantees that it will work.  The first thing to normally live by is the VMware HCL, if it isn't on there then I would have checked around before trying to use it with 4.1.  The next thing I would try is making sure that your storage appliance's firmware is up to date.  At that point, I would try to recreate the iSCSI connections on the new host from scratch, not mimicking the previous setup, just for the sake of making sure something might not need to be set differently now.