thr3ads.net - zfs discuss - [zfs-discuss] COMSTAR iSCSI with vSphere not working [Nov 2009]

If this information is useful, please help other people find it:
Share via:

Duncan Bradey

2009-Nov-12 05:51 UTC

[zfs-discuss] COMSTAR iSCSI with vSphere not working

I am at a loss of where else to look to work out why my vSphere 4 server cannot
access my iSCSI LUNs via the COMSTAR iSCSI target.

# uname -a
SunOS prmel1iscsi01 5.11 snv_111b i86pc i386 i86pc Solaris
# itadm list-target -v
TARGET NAME                                                  STATE    SESSIONS 
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094  online   6        
        alias:                  prmel1iscsi01
        auth:                   none (defaults)
        targetchapuser:         -
        targetchapsecret:       unset
        tpg-tags:               iSCSI = 2
# itadm list-tpg -v
TARGET PORTAL GROUP           PORTAL COUNT
iSCSI                         2        
    portals:    172.22.205.28:3260,172.22.205.27:3260

My vSphere server logs into the target OK

# stmfadm list-target -v
Target: iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094
    Operational Status: Online
    Provider Name     : iscsit
    Alias             : -
    Sessions          : 12
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:45:00 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
        Initiator: iqn.1998-01.com.vmware:PRMEL1VSPCOR02-74207c44
            Alias: -
            Logged in since: Thu Nov 12 16:44:20 2009
# itadm list-initiator
INITIATOR NAME                                               CHAPUSER  SECRET 
iqn.1998-01.com.vmware:prmel1vspcor02-74207c44               <none>       
unset
# stmfadm list-hg -v 
Host Group: prmel1vspcor
        Member: iqn.1998-01.com.vmware:prmel1vspcor02-74207c44
# stmfadm list-lu
LU Name: 600144F0B003090000004AFB990C0001
LU Name: 600144F0B003090000004AFB990D0002
LU Name: 600144F0B003090000004AFB990E0003
LU Name: 600144F0B003090000004AFB990F0004
# stmfadm list-view -l 600144F0B003090000004AFB990C0001
View Entry: 0
    Host group   : prmel1vspcor
    Target group : All
    LUN          : 0
# stmfadm list-view -l 600144F0B003090000004AFB990D0002
View Entry: 0
    Host group   : prmel1vspcor
    Target group : All
    LUN          : 1
# stmfadm list-view -l 600144F0B003090000004AFB990E0003
View Entry: 0
    Host group   : prmel1vspcor
    Target group : All
    LUN          : 2
# stmfadm list-view -l 600144F0B003090000004AFB990F0004
View Entry: 0
    Host group   : prmel1vspcor
    Target group : All
    LUN          : 3

The vSphere server shows the following:-

Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C0:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C0:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C0:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C1:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C1:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C1:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C2:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C2:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.441 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C2:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C3:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C3:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C3:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C4:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C4:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.442 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C4:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.443 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C5:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.443 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C5:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.443 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C5:T0:L0'': Peripheral qualifier 0x1 not
supported
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba34:CH:2 T:0 CN:0: Failed to receive
data: Connection closed by peer
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 172.22.205.39:58864 R:
172.22.205.27:3260]
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: vmhba34:CH:2 T:0 CN:0: Connection rx notifying
failure: Failed to Receive. State=Online
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 172.22.205.39:58864 R:
172.22.205.27:3260]
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: vmhba34:CH:2 T:0 CN:0: Processing CLEANUP
event
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 16:40:30 PRMEL1VSPCOR02 vmkernel: 0:00:25:57.543 cpu3:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 172.22.205.39:58864 R:
172.22.205.27:3260]
...

The issue appears to be here:-
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 839:
Path ''vmhba34:C0:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 842:
Path ''vmhba34:C0:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 16:39:35 PRMEL1VSPCOR02 vmkernel: 0:00:25:02.440 cpu0:4245)ScsiScan: 105:
Path ''vmhba34:C0:T0:L0'': [b]Peripheral qualifier 0x1 not
supported [/b]

Which according to VMware
(http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012270)
means "0x1 = 001b ? The device server is capable of supporting the
specified peripheral device type on this logical unit. However, the physical
device is not currently connected to this logical unit."

The way that I am interpreting this is that LUN0 hasn''t been defined,
yet it has (see output above).

I am at a complete loss, I''ve tried everything that I can think of,
using CHAP, disabling CHAP, recreating the target, I even reinstalled the OS and
reconfigured the COMSTAR stack from scratch.

Any advice?
-- 
This message posted from opensolaris.org

Rasmus Fauske

2009-Nov-12 06:10 UTC

head link

[zfs-discuss] COMSTAR iSCSI with vSphere not working

Duncan Bradey skrev:> I am at a loss of where else to look to work out why my vSphere 4 server
cannot access my iSCSI LUNs via the COMSTAR iSCSI target.
>
> I am at a complete loss, I''ve tried everything that I can think
of, using CHAP, disabling CHAP, recreating the target, I even reinstalled the OS
and reconfigured the COMSTAR stack from scratch.
>   How large are the volumes you are creating ? In my setup vSphere could 
not see the volume if it was above 2000GB

I am running b118 with comstar and vSphere and that works great. Using 
file backed iscsi luns (thin provisioned)

--
Rasmus Fauske

Duncan Bradey

2009-Nov-12 06:42 UTC

head link

[zfs-discuss] COMSTAR iSCSI with vSphere not working

Rasmus,

I had 4 volumes:-

Found 4 LU(s)

              GUID                    DATA SIZE           SOURCE
--------------------------------  -------------------  ----------------
600144f0b003090000004afb990f0004      1099511562240   
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-03
600144f0b003090000004afb990e0003      1099511562240   
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-02
600144f0b003090000004afb990d0002      2196875706368   
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-01
600144f0b003090000004afb990c0001      2196875706368   
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-00

I''ve reallocated these same LUN''s to a Windows server (a VM
with MS iSCSI initiator) and this works fine.

One your posting below I''ve created a new 1024GB LUN and tried
allocated this and only this LUN to vSphere, but I''m getting the same
issue.  Here are the new details:-

              GUID                    DATA SIZE           SOURCE
--------------------------------  -------------------  ----------------
600144f0b003090000004afbac8a0007      1099511562240   
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-04

# stmfadm list-view -l 600144f0b003090000004afbac8a0007
View Entry: 0
    Host group   : prmel1vspcor
    Target group : All
    LUN          : 0

# stmfadm list-hg -v
Host Group: prmel1vspcor
        Member: iqn.1998-01.com.vmware:prmel1vspcor02-74207c44

Unfortunately there is no change to the behaviour - same errors in the
/var/log/vmkernel:-

Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan: 839:
Path ''vmhba34:C0:T0:L0'': Vendor: ''SUN     '' 
Model: ''COMSTAR          ''  Rev: ''1.0 ''
Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan: 842:
Path ''vmhba34:C0:T0:L0'': Type: 0x1f, ANSI rev: 5, TPGS: 0
(none)
Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan: 105:
Path ''vmhba34:C0:T0:L0'': Peripheral qualifier 0x1 not
supported
...
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba34:CH:2 T:0 CN:0: Failed to receive
data: Connection closed by peer
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 172.22.205.39:52606 R:
172.22.205.27:3260]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: vmhba34:CH:2 T:0 CN:0: Connection rx notifying
failure: Failed to Receive. State=Online
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 172.22.205.39:52606 R:
172.22.205.27:3260]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: vmhba34:CH:2 T:0 CN:0: Processing CLEANUP
event
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
...

I''ve even tried a reboot of my vSphere server just to be sure that
nothing was invalid there (btw, CHAP is currently disabled as well), but no
good.
-- 
This message posted from opensolaris.org

zfs discuss - Nov 2009 - COMSTAR iSCSI with vSphere not working

[zfs-discuss] COMSTAR iSCSI with vSphere not working

[zfs-discuss] COMSTAR iSCSI with vSphere not working

[zfs-discuss] COMSTAR iSCSI with vSphere not working