iSCSI target not showing in devices

[illuminate1]

Hi all! Very new user here..

I started to get some storage errors when bringing up new VMs, so it's time to add on. I have some Nexsan Sataboys around my lab and have easily hooked them up in the past. I created a vswitch just for iSCSI:

I then went to storage adapters and enabled software initiator, set the network to vswitch3 (vmk1), dynamically discovered my storage and then the target name showed up in the static. I then rescanned and nothing is showing up under connected devices.

So I have been looking around in the CLI and here is some further info (not sure how helpful but hey, I learned how to do it):

# esxcli iscsi networkportal list
vmhba33
   Adapter: vmhba33
   Vmknic: vmk1
   MAC Address: 00:21:9b:9f:7d:75
   MAC Address Valid: true
   IPv4: 172.18.160.53
   IPv4 Subnet Mask: 255.255.255.0
   IPv6:
   MTU: 1500
   Vlan Supported: true
   Vlan ID: 0
   Reserved Ports: 63488~65536
   TOE: false
   TSO: true
   TCP Checksum: false
   Link Up: true
   Current Speed: 1000
   Rx Packets: 24764
   Tx Packets: 647
   NIC Driver: bnx2
   NIC Driver Version: 2.0.15g.v50.11-5vmw
   NIC Firmware Version: 5.0.12 bc 5.0.11 NCSI 2.0.5
   Compliant Status: compliant
   NonCompliant Message:
   NonCompliant Remedy:
   Vswitch: vSwitch3
   PortGroup: iSCSI
   VswitchUuid:
   PortGroupKey:
   PortKey:
   Duplex:
   Path Status: unused

# esxcli iscsi session connection list
vmhba33,iqn.1999-02.com.nexsan:p0:sataboy2:019153ca,00023d000001,0
   Adapter: vmhba33
   Target: iqn.1999-02.com.nexsan:p0:sataboy2:019153ca
   ISID: 00023d000001
   CID: 0
   DataDigest: NONE
   HeaderDigest: NONE
   IFMarker: false
   IFMarkerInterval: 0
   MaxRecvDataSegmentLength: 131072
   MaxTransmitDataSegmentLength: 65536
   OFMarker: false
   OFMarkerInterval: 0
   ConnectionAddress: 172.18.160.xx
   RemoteAddress: 172.18.160.xx
   LocalAddress: 172.18.160.xx
   SessionCreateTime: 05/15/12 13:48:09
   ConnectionCreateTime: 05/15/12 13:48:09
   ConnectionStartTime: 05/15/12 13:48:09
   State: logged_in

Can anyone provide further information on what I may be missing here?

[eeg3]

This may be a silly question, but it wasn't explicitly stated in the original post... have you granted the ESXi host's initiator access rights to any volumes?

[john23]

check some of the stufs

- do vmkping to the target ip from esxi server

- check static discovery tab (what it shows)

- confirm that initiator iqn is mentioned correctly on target side

[illuminate1]

- vmkping to the target from the ESXi server was fine.

- Static discovery tab looks good, shows proper iqn:

-This is my storage side setup, I think that was mentioned as well:

Any further assistance is most appreciated! It seems as though it SHOULD be working..

[john23]

what vmkernel messages shows when you rescan iscsi adapter?

[illuminate1]

I rescanned and checked the logs:

2012-05-16T13:03:55.370Z cpu3:2205)ScsiUid: 273: Path 'vmhba0:C0:T0:L0' does not support VPD Device Id page.
2012-05-16T13:03:55.372Z cpu3:2205)VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0
2012-05-16T13:03:55.374Z cpu8:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.413Z cpu9:2057)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x412441416c40) to dev "t10.DP______BACKPLANE000000" on path "vmhba1:C0:T32:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.Act:NONE
2012-05-16T13:03:55.413Z cpu9:2057)ScsiDeviceIO: 2316: Cmd(0x412441416c40) 0x1a, CmdSN 0x3e81 to dev "t10.DP______BACKPLANE000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2012-05-16T13:03:55.413Z cpu8:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.429Z cpu8:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.437Z cpu8:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.439Z cpu8:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.441Z cpu8:449766)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T13:03:55.463Z cpu8:449766)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T13:03:55.463Z cpu8:449766)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T13:03:55.485Z cpu8:449766)VC: 1449: Device rescan time 56 msec (total number of devices 7)
2012-05-16T13:03:55.485Z cpu8:449766)VC: 1452: Filesystem probe time 38 msec (devices probed 5 of 7)
2012-05-16T13:03:55.494Z cpu8:449766)ScsiScan: 1098: Path 'vmhba1:C0:T0:L0': Vendor: 'SEAGATE '  Model: 'ST973452SS      '  Rev: 'HT62'
2012-05-16T13:03:55.494Z cpu8:449766)ScsiScan: 1101: Path 'vmhba1:C0:T0:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
2012-05-16T13:03:55.495Z cpu8:449766)megasas_slave_configure: do not export physical disk devices to upper layer.
2012-05-16T13:03:55.495Z cpu8:449766)WARNING: ScsiScan: 1485: Failed to add path vmhba1:C0:T0:L0 : Not found
2012-05-16T13:03:55.496Z cpu8:449766)ScsiScan: 1098: Path 'vmhba1:C0:T1:L0': Vendor: 'SEAGATE '  Model: 'ST973452SS      '  Rev: 'HT62'
2012-05-16T13:03:55.496Z cpu8:449766)ScsiScan: 1101: Path 'vmhba1:C0:T1:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
2012-05-16T13:03:55.496Z cpu8:449766)megasas_slave_configure: do not export physical disk devices to upper layer.
2012-05-16T13:03:55.496Z cpu8:449766)WARNING: ScsiScan: 1485: Failed to add path vmhba1:C0:T1:L0 : Not found
2012-05-16T13:03:55.497Z cpu8:449766)ScsiScan: 1098: Path 'vmhba1:C0:T2:L0': Vendor: 'SEAGATE '  Model: 'ST973452SS      '  Rev: 'HT62'
2012-05-16T13:03:55.497Z cpu8:449766)ScsiScan: 1101: Path 'vmhba1:C0:T2:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
2012-05-16T13:03:55.498Z cpu8:449766)megasas_slave_configure: do not export physical disk devices to upper layer.
2012-05-16T13:03:55.498Z cpu8:449766)WARNING: ScsiScan: 1485: Failed to add path vmhba1:C0:T2:L0 : Not found
2012-05-16T13:03:55.499Z cpu8:449766)ScsiScan: 1098: Path 'vmhba1:C0:T3:L0': Vendor: 'SEAGATE '  Model: 'ST973452SS      '  Rev: 'HT62'
2012-05-16T13:03:55.499Z cpu8:449766)ScsiScan: 1101: Path 'vmhba1:C0:T3:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
2012-05-16T13:03:55.499Z cpu8:449766)megasas_slave_configure: do not export physical disk devices to upper layer.
2012-05-16T13:03:55.499Z cpu8:449766)WARNING: ScsiScan: 1485: Failed to add path vmhba1:C0:T3:L0 : Not found
2012-05-16T13:03:55.691Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.698Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.705Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.713Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.715Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.717Z cpu13:449766)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T13:03:55.728Z cpu13:449766)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T13:03:55.728Z cpu13:449766)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T13:03:55.730Z cpu13:449766)VC: 1449: Device rescan time 15 msec (total number of devices 7)
2012-05-16T13:03:55.730Z cpu13:449766)VC: 1452: Filesystem probe time 23 msec (devices probed 5 of 7)
2012-05-16T13:03:55.746Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.758Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.777Z cpu13:449766)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T13:03:55.777Z cpu13:449766)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T13:03:55.777Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.788Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.790Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.792Z cpu13:449766)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T13:03:55.794Z cpu13:449766)VC: 1449: Device rescan time 20 msec (total number of devices 7)
2012-05-16T13:03:55.794Z cpu13:449766)VC: 1452: Filesystem probe time 26 msec (devices probed 5 of 7)
2012-05-16T13:03:55.845Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.857Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.869Z cpu13:449766)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T13:03:55.869Z cpu13:449766)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T13:03:55.876Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.884Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.886Z cpu13:449766)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.889Z cpu13:449766)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T13:03:55.891Z cpu13:449766)VC: 1449: Device rescan time 20 msec (total number of devices 7)
2012-05-16T13:03:55.891Z cpu13:449766)VC: 1452: Filesystem probe time 23 msec (devices probed 5 of 7)
2012-05-16T13:03:55.922Z cpu4:2912)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.936Z cpu4:2912)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.943Z cpu4:2912)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.951Z cpu4:2912)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.953Z cpu4:2912)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T13:03:55.955Z cpu4:2912)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T13:03:55.959Z cpu4:2912)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T13:03:55.959Z cpu4:2912)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T13:03:55.968Z cpu6:2912)VC: 1449: Device rescan time 21 msec (total number of devices 7)
2012-05-16T13:03:55.968Z cpu6:2912)VC: 1452: Filesystem probe time 23 msec (devices probed 5 of 7)

Is any of that helpful?

[john23]

nope..these logs are not at all showing the iscsi adapter scanning.... can you run this command and check the vmkernel logs esxcfg-swiscsi -s

[illuminate1]

# esxcfg-swiscsi -s
Scanning vmhba33...

The vmkernel log shows:

2012-05-16T14:34:30.974Z cpu6:1250585)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T14:34:31.014Z cpu2:2050)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x41240038c840) to dev "t10.DP______BACKPLANE000000" on path "vmhba1:C0:T32:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.Act:NONE
2012-05-16T14:34:31.014Z cpu2:2050)ScsiDeviceIO: 2316: Cmd(0x41240038c840) 0x1a, CmdSN 0x4023 to dev "t10.DP______BACKPLANE000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2012-05-16T14:34:31.014Z cpu6:1250585)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T14:34:31.028Z cpu6:1250585)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T14:34:31.040Z cpu6:1250585)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T14:34:31.042Z cpu6:1250585)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-05-16T14:34:31.044Z cpu6:1250585)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-05-16T14:34:31.066Z cpu6:1250585)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-05-16T14:34:31.066Z cpu6:1250585)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-05-16T14:34:31.095Z cpu6:1250585)VC: 1449: Device rescan time 66 msec (total number of devices 7)
2012-05-16T14:34:31.095Z cpu6:1250585)VC: 1452: Filesystem probe time 51 msec (devices probed 5 of 7)

[illuminate1]

Anyone? Anymore ideas? I really need to be able to expand my storage so I can create more VMs.

[john23]

illuminate1  From logs its not at all scanning vmhba33....

check this KB , if you miss anything during configuration

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008083

hope some one can give more info ...

[illuminate1]

Thank you for that KB link.. I have checked everything there. I do have another question.. Could it not be showing up due to the size? I have a 5.5TB device, is there a limitation perhaps?

[sa2057]

Hi,

what about host and iSCSI subnets ?  Are they on the same subnets or different?

I'm asking this because I faced same issue and ruled out  this problems after changing iSCSI on to different subnet.

Thanks

SA

[illuminate1]

The host is on a trunk, with many vlans. See here:

My iSCSI adapter has the Vlan 3 tag:

[beckham007fifa]

make sure your networking is perfectly done. If so there is nothing to be done more from esxi end, your setting looks correct from the screensshots you shared. Now from here on its the storage side which can be checked for.

[sa2057]

Hi,

Pl.  check the security settings from your storage end. Something might be blocking. Pl. post the screen shots ( start from enabling  iSCSI settings).

Thanks

SA

[illuminate1]

I am adding screenshots of my Iscsi info from the array:

I do not have CHAP enabled

[sa2057]

Hi,

Pl. check this

http://www.davidklee.net/2012/02/09/vsphere-5-software-iscsi-cannot-route-between-subnets/

Thanks

SA

[illuminate1]

SA, Thanks for the link..

So I have my VMkernel set to look like this:

Both the host and the iSCSI are on the same Vlan 3. Should I have specified Vlan 3 here as well?

[sa2057]

I would specify vlan ID and rescan.

Thanks

SA

[rickardnobel]

illuminate1 wrote:

Could it not be showing up due to the size? I have a 5.5TB device, is there a limitation perhaps?

Since you are using ESXi 5 (right?) there should be no size limit for your 5.5 TB LUN, however it could be really interesting if you could create something smaller, like a second LUN with just 10 GB or something, and see if that shows up correctly on the ESXi side.