Weird iSCSI ==> NetApp Problem

iprigger

iprigger

Renowned Member
Proxmox Subscriber
Sep 5, 2009
192
43
93
earth!
Hi All,

I have a cluster of two systems running and have two storage devices:
- One QNAP 459 Pro
- One NetApp FAS270

I have (for the luns that need to run 24h w/o interruption) an iSCSI Target on the QNAP already. Now I wanted to create another iSCSI Lun on the NetApp Filer.

I can attach it - but I don't see anything in /proc/scsi/scsi or elsewhere. Short: I can't use the NetApp LUN.

PVE Version:
running kernel: 2.6.35-2-pve
proxmox-ve-2.6.35: 1.8-13
pve-kernel-2.6.35-1-pve: 2.6.35-11
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.35-2-pve: 2.6.35-13
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

ONTAP Version: 7.3.6P5

bluelagoon> iscsi show initiator
iscsi show initiator: This command has been deprecated.
Please consider using 'iscsi initiator show' instead.


Initiators connected:
TSIH TPGroup Initiator/ISID/IGroup
83 2000 oestersund (iqn.1993-08.org.debian:01:60f389a37eb / 00:02:3d:0e:00:00 / )


On the PVE Node:
cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: SAMSUNG HD501LJ Rev: CR10
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: QNAP Model: iSCSI Storage Rev: 3.1
Type: Direct-Access ANSI SCSI revision: 05

Does anyone of you have a clue what's going on here? I think the error is on my side - but I have no clue what I've messed up...

Tobias
 
Hi,

What is the ouput for : iscsiadm -m node && iscsiadm -m session
 
Hi MrJack!

Here you are:

First host:
oestersund:~# iscsiadm -m node
172.30.0.20:3260,-1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscs1.c61f2e
172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscs1.c61f2e
172.30.33.9:3260,1 iqn.2004-04.com.qnap:ts-859:iscsi.test.c67276
172.30.0.23:3260,2000 iqn.1992-08.com.netapp:sn.84257535
172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscsi0.c61f2e

oestersund:~# iscsiadm -m session
tcp: [1] 172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscsi0.c61f2e
tcp: [18] 172.30.0.23:3260,2000 iqn.1992-08.com.netapp:sn.84257535

Second host:
stockholm:~# iscsiadm -m node
172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscsi0.c61f2e
172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscs1.c61f2e
172.30.0.20:3260,-1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscs1.c61f2e
172.30.33.9:3260,1 iqn.2004-04.com.qnap:ts-859:iscsi.test.c67276

stockholm:~# iscsiadm -m session
tcp: [1] 172.30.0.20:3260,1 iqn.2004-04.com.qnap:ts-459:iscsi.qeiscsi0.c61f2e


Note that the Qnap is functioning perfectly.... (as good as a qnap can be...)

CU
Tobias
 
Maybe you can shutdown the netapp session, reconnect it and see what append with dmesg
Also check the configuration on your netapp, it must like your qnap reflect the content of /etc/iscsi/initiatorname.iscsi
 
Hi MrJack

This is all I get...
scsi22 : iSCSI Initiator over TCP/IP

Looks a bit little...

But your Tip with /etc/iscsi/initiatorname.iscsi - that's been it!

Seems to work now!

Thanks a lot!

Tobias
 
You must log in or register to reply here.
Top Bottom