RE: iSCSI Target (LIO)
Moin,
mittlererweile habe ich es rausgefunden:
Mit target_status kann man das herausfinden. Das ruft aber letztendlich nur lio_node auf.
lio_node --listtargetnames zeigt dann die targets an...
Gesendet von meinem Fujitsu LIFEBOOK E754
Mit freundlichen Grüßen
Dirk Laurenz
Principal Account Technology Consultant
Projektmanager
Sales Germany
FUJITSU
Hildesheimer Strasse 25, 30880 Laatzen, Deutschland
Tel.: +49 (511) 84 89 18 08
Mob.: +49 (170) 22 10 781
Fax: +49 (511) 84 89 25 18 08
E-mail: dirk.laurenz@ts.fujitsu.com
Web: ts.fujitsu.com
Firmenangaben: Fujitsu Technology Solutions GmbH / ts.fujitsu.com/imprint
Folgen Sie uns! Die Fujitsu Community
This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation.
Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission.
-----Original Message-----
From: Martin Johannes Dauser <mdauser@cs.sbg.ac.at>
Sent: Thursday, September 19, 2019 1:49 PM
To: debian-user-german@lists.debian.org
Subject: Re: iSCSI Target (LIO)
Aso! Naja, Serverseitig fehlt mir da leider auch die Erfahrung, da mir von den Kollegen eine NetApp zur Verfügung gestellt wird.
* Bei Linux target framework (TGT) gäbe es ja tgtadmin aber bei LIO liefert targetcli besten Falls alle aktiven Sessions:
# targetcli sessions [ list | detail ] [sid]
* Man kann nachsehen, ob zumindest etwas auf Port 3260 horcht.
# ss
-tnlp | grep 3260
LISTEN
0 256 0.0.0.0:3260 0.0.0.0:*
oder
# netstat -tnlp | grep 3260
tcp 0 0 0.0.0.0:3260 0.0.0.0:*
* systemd könnte bei groben Schnitzern Hinweise liefern:
# systemctl status <name_von_target.service>
* russisch: Ein lokaler Initiator, welcher sich auf eine Test-LUN verbindet, dann weiss man wenigstens dass LIO an sich läuft. 😛
Mmh, es könnte aber möglich sein, dass man auf eine LUN einen Test- Initiator read-only und einen zweiten Initiator read-write einbindet.
Liebe Grüße
Martin
On Thu, 2019-09-19 at 09:07 +0000, dirk.laurenz@ts.fujitsu.com wrote:
> Moin.
>
> Danke erst mal, das ist der client teil, ich mein wenn ich ein linux als iscsi server nutze... iscsiadm gibt ja nur den client aus...
>
> Gesendet von meinem Fujitsu LIFEBOOK E754
>
> Mit freundlichen Grüßen
> Dirk Laurenz
> Principal Account Technology Consultant Projektmanager Sales Germany
>
>
> FUJITSU
> Hildesheimer Strasse 25, 30880 Laatzen, Deutschland
> Tel.: +49 (511) 84 89 18 08
> Mob.: +49 (170) 22 10 781
> Fax: +49 (511) 84 89 25 18 08
> E-mail: dirk.laurenz@ts.fujitsu.com
> Web: ts.fujitsu.com
> Firmenangaben: Fujitsu Technology Solutions GmbH /
> ts.fujitsu.com/imprint
>
>
> Folgen Sie uns! Die Fujitsu Community
>
>
> This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation.
> Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission.
>
>
>
> -----Original Message-----
> From: Martin Johannes Dauser <mdauser@cs.sbg.ac.at>
> Sent: Thursday, September 19, 2019 10:35 AM
> To: debian-user-german@lists.debian.org
> Subject: Re: iSCSI Target (LIO)
>
> Liste alle aktuellen Sessions:
>
> # iscsiadm -m session
> tcp: [1] 192.168.90.239:3260,1033
> iqn.1992-08.com.netapp:sn.62a9975d35cf11e5abb600a0985789e1:vs.6
> (non-flash)
>
> ------------------------------
> Zeige iSCSI Database bezüglich eingeloggter Sessions:
>
> # iscsiadm -m session -o show -P 3
> iSCSI Transport Class version 2.0-870
> version 6.2.0.874-10
> Target: iqn.1992-08.com.netapp:sn.62a9975d35cf11e5abb600a0985789e1:vs.6 (non-flash)
> Current Portal: 192.168.90.239:3260,1033
> Persistent Portal: 192.168.90.239:3260,1033
> **********
> Interface:
> **********
> Iface Name: default
> Iface Transport: tcp
> Iface Initiatorname: iqn.1994-05.com.redhat:412deb1b2c62
> Iface IPaddress: 192.168.4.4
> Iface HWaddress: <empty>
> Iface Netdev: <empty>
> SID: 1
> iSCSI Connection State: LOGGED IN
> iSCSI Session State: LOGGED_IN
> Internal iscsid Session State: NO CHANGE
> *********
> Timeouts:
> *********
> Recovery Timeout: 5
> Target Reset Timeout: 30
> LUN Reset Timeout: 30
> Abort Timeout: 15
> *****
> CHAP:
> *****
> username: mink
> password: ***********
> username_in: <empty>
> password_in: *****************
> ************************
> Negotiated iSCSI params:
> ************************
> HeaderDigest: None
> DataDigest: None
> MaxRecvDataSegmentLength: 262144
> MaxXmitDataSegmentLength: 65536
> FirstBurstLength: 65536
> MaxBurstLength: 1048576
> ImmediateData: Yes
> InitialR2T: Yes
> MaxOutstandingR2T: 1
> ************************
> Attached SCSI devices:
> ************************
> Host Number: 3 State: running
> scsi3 Channel 00 Id 0 Lun: 0
> Attached scsi disk sdb State: running
> Current Portal: 192.168.90.240:3260,1030
> Persistent Portal: 192.168.90.240:3260,1030
> **********
> Interface:
> **********
> Iface Name: default
> Iface Transport: tcp
> Iface Initiatorname: iqn.1994-05.com.redhat:412deb1b2c62
> Iface IPaddress: 192.168.4.4
> Iface HWaddress: <empty>
> Iface Netdev: <empty>
> SID: 2
> iSCSI Connection State: LOGGED IN
> iSCSI Session State: LOGGED_IN
> Internal iscsid Session State: NO CHANGE
> *********
> Timeouts:
> *********
> Recovery Timeout: 5
> Target Reset Timeout: 30
> LUN Reset Timeout: 30
> Abort Timeout: 15
> *****
> CHAP:
> *****
> username: mink
> password: **************
> username_in: <empty>
> password_in: ****************
> ************************
> Negotiated iSCSI params:
> ************************
> HeaderDigest: None
> DataDigest: None
> MaxRecvDataSegmentLength: 262144
> MaxXmitDataSegmentLength: 65536
> FirstBurstLength: 65536
> MaxBurstLength: 1048576
> ImmediateData: Yes
> InitialR2T: Yes
> MaxOutstandingR2T: 1
> ************************
> Attached SCSI devices:
> ************************
> Host Number: 4 State: running
> scsi4 Channel 00 Id 0 Lun: 0
> Attached scsi disk sdc State: running
>
> ------------------------------
>
> Liste LUNS, die verbunden sind auf:
>
> # lsscsi
> [0:0:0:0] disk VMware Virtual disk 1.0 /dev/sda
> [2:0:0:0] cd/dvd NECVMWar VMware IDE CDR10 1.00 /dev/sr0
> [3:0:0:0] disk NETAPP LUN C-Mode 9400 /dev/sdb
> [4:0:0:0] disk NETAPP LUN C-Mode 9400 /dev/sdc
>
>
>
> On Thu, 2019-09-19 at 07:57 +0000, dirk.laurenz@ts.fujitsu.com wrote:
> > Moin,
> >
> > wie kann ich einfach feststellen, dass mein iSCSI Target läuft?
> > Da es ja Teil des Kernels ist, kann ich ja kaum auf einen Prozess gucken.
> >
> > Gruß,
> >
> > Dirk
>
>
Reply to: