Differences

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

--- nndocs:srp [2025/12/25 00:51] – [Dependencies] Note: using port 2 doesn't seem to work naptastic
+++ nndocs:srp [2026/06/11 17:57] (current) – update commands and "port 2 doesn't work" info naptastic
@@ Line 30: / Line 30: @@
 Find targets to connect to:
-    # srp_daemon -o -v -c -p 1
+    # srp_daemon -o -V -c
   * -o means "run once" otherwise dmesg on all your hosts will get polluted with SRP login noise.
-  * -v means "say what you're doing"
+  * -V means debug. This will give you the id_ext (lower 8 bytes) of every target.
   * -c means "emit target information in a format we can use later"
-  * -p 1 means "only scan on HCA port 1" so obviously change this if you are initiating from port 2...
+  * If all the information returned by srp_daemon is correct, you can replace -c with -e to connect to targets automatically. Otherwise, you can connect to individual targets manually using the steps below.
+Note: in my experimentation, port 2 is not actually usable. A target created a dual-port InfiniBand HCA always answers on port 1 even if the associated GUID is for port 2, and an initiator on port 2 always actually tries to use port 1. The answer is probably "use SR-IOV".
+On VPI cards configured IB/ETH, port 2 doesn't support SRP anyway.
-Note: in my experimentation, port 2 is not actually usable. A target created on a dual-port card always answers on port 1 even if the associated GUID is for port 2, and an initiator on port 2 always actually tries to use port 1. The answer is probably "use SR-IOV".
 ====Configuration====