Differences

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

--- cmd:sanhook [2012/03/24 20:31]
mcb30
+++ cmd:sanhook [2017/03/26 13:38]
mcb30
@@ Line 3: / Line 3: @@
 ===== Synopsis =====
-    sanhook [--drive <drive>] [--no-describe] <uri>
+    sanhook [--drive <drive>] [--no-describe] <uri> [<uri>...]
 ===== Examples =====
@@ Line 10: / Line 10: @@
     sanhook iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage
+=== Attach a multipath iSCSI target ===
+    sanhook iscsi:192.168.0.101::::iqn.2010-04.org.ipxe.squirrel:storage \
+            iscsi:192.168.0.102::::iqn.2010-04.org.ipxe.squirrel:storage
+=== Attach two independent iSCSI targets ===
+    sanhook --drive 0x80 iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage
+    sanhook --drive 0x81 iscsi:192.168.0.1::::iqn.2010-04.org.ipxe.chipmunk:storage
 === Check ability to attach a SAN target ===
@@ Line 22: / Line 32: @@
 ===== Description =====
-Attach the specified [[:sanuri|SAN target URI]] as the specified SAN drive.  If no SAN drive is explicitly specified then the default SAN drive (''%%0x80%%'') will be used.
+Attach the specified [[:sanuri|SAN target URIs]] as the specified SAN drive.  If no SAN drive is explicitly specified then the default SAN drive (''%%0x80%%'') will be used.
 The SAN drive will be described via an appropriate mechanism (such as an iBFT for an iSCSI drive) unless the ''%%--no-describe%%'' option is specified.
@@ Line 39: / Line 49: @@
 ===== Notes =====
-If you wish to attach to multiple SAN targets, each target must be attached as a different SAN drive.
+You can create a multipath SAN device by specifying multiple SAN target URIs.  iPXE will use whichever SAN target responds first, and will retry all URIs if the original SAN target fails for any reason.  You must ensure that all SAN URIs in a multipath SAN device point to the same underlying SAN drive.
+If you wish to attach to multiple independent SAN drives, then you must use the ''sanhook'' command once for each independent SAN drive.