User Tools

Site Tools


nndocs:iscsi

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
nndocs:iscsi [2024/09/08 22:00] – Move IQN info to sandbox naptasticnndocs:iscsi [2025/01/03 02:32] (current) – [Initiator] naptastic
Line 1: Line 1:
-TODO: Make all the initiator and target names match please 
- 
 TODO: Explain why I don't have iSCSI boot working yet, please TODO: Explain why I don't have iSCSI boot working yet, please
  
Line 17: Line 15:
     > portals/ create 172.19.12.1 3260     > portals/ create 172.19.12.1 3260
     > portals/172.19.12.1:3260 enable_iser boolean=true     > portals/172.19.12.1:3260 enable_iser boolean=true
- 
-TODO: enable_iser doesn't work on shark. Any ideas why yet? Or is it just time to nuke and re-pave? 
  
 =====Initiator===== =====Initiator=====
Line 26: Line 22:
  
 ===Login. Must use a node record id found by the discovery=== ===Login. Must use a node record id found by the discovery===
-    iscsiadm --mode node --targetname iqn.2001-05.com.doe:test --portal 172.20.64.11:3260 --login+    iscsiadm --mode node --targetname iqn.2014-08.rocks.narf.southpark --portal 172.20.64.11:3260 --login
  
 [[https://www.thegeekdiary.com/iscsi-connection-command-examples-cheat-sheet/]] [[https://www.thegeekdiary.com/iscsi-connection-command-examples-cheat-sheet/]]
Line 33: Line 29:
  
     # iscsiadm -m session     # iscsiadm -m session
-    tcp: [1] 172.21.0.80:3260,1 iqn.2003-01.org.linux-iscsi.happy.x8664:sn.9eb52ac74563 (non-flash)+    tcp: [1] 172.20.0.80:3260,1 iqn.2014-08.rocks.narf.southpark (non-flash)
  
 The session number (sid) is the 1 in brackets. The session number (sid) is the 1 in brackets.
  
 ===Use iSER instead of TCP (initiator side)=== ===Use iSER instead of TCP (initiator side)===
-If performance is poor, the initiator may have logged in using TCP instead of iSER. In my testing, to a ramdisk over IB, TCP got ~520 MiB/s, where iSER got 1.9 GiB/s.+If performance is poor, the initiator may have logged in using TCP instead of iSER. In my testing, to a ramdisk over IB, TCP got ~520 MiB/s, where with iSER I have gotten 3.2 GB/s.
  
 You know you got TCP if dmesg describes your LUN like this: You know you got TCP if dmesg describes your LUN like this:
Line 53: Line 49:
     [123.45678] scsi host1: iSCSI Initiator over iSER     [123.45678] scsi host1: iSCSI Initiator over iSER
     [123.45678] scsi 1:0:0:0: Direct-Access     LIO-ORG  volume       4.0  PQ: 0 ANSI: 6     [123.45678] scsi 1:0:0:0: Direct-Access     LIO-ORG  volume       4.0  PQ: 0 ANSI: 6
- 
-FDR InfiniBand should be able to move over 6 GB/s of traffic. 1.9 GiB/s is nothing to be sad about. 
  
 ===Rescan after the target adds a LUN=== ===Rescan after the target adds a LUN===
  
     # iscsiadm -m session --sid=1 --rescan     # iscsiadm -m session --sid=1 --rescan
-    Rescanning session [sid: 1, target: iqn.2003-01.org.linux-iscsi.happy.x8664:sn.9eb52ac74563, portal: 172.21.0.80,3260]+    Rescanning session [sid: 1, target: iqn.2014-08.rocks.narf.southpark, portal: 172.20.0.80,3260]
  
 ===Log out when you're done (very, very carefully)=== ===Log out when you're done (very, very carefully)===
nndocs/iscsi.1725832811.txt.gz · Last modified: 2024/09/08 22:00 by naptastic