[Bug 1034015] Re: Fails to connect to iSCSI target

[Peter Petrakis]

So here's your problem, which I identified by running wireshark on the pcap
(very helpful, thanks for providing), typing 'iscsi' to filter on that only
and identified the inquiry exchange.

The inquiry cmd open-iscsi send looks fine. The response from the target
however...

0060  00 00 00 00 00 00 7f 00  05 00 00 00 00 00 00 00   ........ ........
0070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0080  00 00 00 00 00 00 00 00  00 00                     ........ ..      

Definitely no make and model information there...

Wireshark was so kind as to translate it for me.

Peripheral: 0x7f, Qualifier: Device type is not supported by server, Device Type: Unknown or no device type
011. .... = Qualifier: Device type is not supported by server (0x03)
...1 1111 = Device Type: Unknown or no device type (0x1f)

So sure it's advertising a lun,  but when we reach out in touch it we
get garbage.

This is decidedly SAN side. That Centos "works" at all is simply a race condition *or*
it has a quirk allowance for your SAN, which you have yet to articulate.

Contact your SAN vendor to determine why it's responding this way.


** Summary changed:

- Fails to connect to iSCSI target
+ iSCSI target returns "Device type is not supported by server", discovery fails.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to open-iscsi in Ubuntu.
https://bugs.launchpad.net/bugs/1034015

Title:
  iSCSI target returns "Device type is not supported by server",
  discovery fails.

Status in “linux” package in Ubuntu:
  Triaged
Status in “open-iscsi” package in Ubuntu:
  Incomplete

Bug description:
  Connecting from an Ubuntu 12.04LTS server to a
  SANRAD (http://www.sanrad.com) switch offering iSCSI connectivity, fails.
  First, look for targets

  root at media2:~# iscsiadm -m discovery -t st -p 172.31.1.15
  172.31.1.15:3260,65535 bigmedia1
  172.31.1.14:3260,65535 bigmedia1
  172.31.1.16:3260,65535 bigmedia1
  172.31.1.15:3260,65535 media1target
  172.31.1.14:3260,65535 media1target
  172.31.1.16:3260,65535 media1target
  172.31.1.15:3260,65535 bigmedia2
  172.31.1.14:3260,65535 bigmedia2
  172.31.1.16:3260,65535 bigmedia2

  Lots of nice targets - now connect to one

  root at media2:~# iscsiadm -m node -T bigmedia1 -p 172.31.1.15 -l
  Logging in to [iface: default, target: bigmedia1, portal: 172.31.1.15,3260]
  Login to [iface: default, target: bigmedia1, portal: 172.31.1.15,3260]: successful
  root at media2:~# echo $?
  0

  Apparently connected - it says successful, and returns zero. Now,
  check partitions

  root at media2:~# cat /proc/partitions
  major minor  #blocks  name

    11        0    1048575 sr0
     8        0  731445248 sda
     8        1    1048576 sda1
     8        2  730395648 sda2
   252        0   20971520 dm-0
   252        1    8388608 dm-1

  Nothing new - sda is my root drive, the new one should be in there as
  sdb. Checking dmesg, it has two new lines

  [  358.391438] scsi6 : iSCSI Initiator over TCP/IP
  [  358.645490] scsi scan: INQUIRY result too short (5), using 36

  Please see http://karlsbakk.net/tmp/iscsi-debug.txt for a login
  attempt with -d 200 and http://karlsbakk.net/tmp/iscsi-fail.pcap for a
  traffic dump between the two machines during login attempt.

  Please note that with open-iscsi on a CentOS 5.8 machine of the same
  make, this works perfectly.

  roy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034015/+subscriptions