Differences

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

cmd:sanboot [2012/08/03 13:30]
mcb30
cmd:sanboot [2017/03/26 14:35] (current)
mcb30
Line 3: Line 3:
===== Synopsis ===== ===== Synopsis =====
-    sanboot [--drive <drive>] [--no-describe] [--keep] [<uri>]+    sanboot [--drive <drive>] [--no-describe] [--keep] [<uri>] [<uri>...]
===== Examples ===== ===== Examples =====
Line 10: Line 10:
    sanboot iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage     sanboot iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage
 +
 +=== Boot from a multipath iSCSI target ===
 +
 +    sanboot iscsi:192.168.0.101::::iqn.2010-04.org.ipxe.squirrel:storage \
 +            iscsi:192.168.0.102::::iqn.2010-04.org.ipxe.squirrel:storage
=== Boot from an HTTP target === === Boot from an HTTP target ===
Line 26: Line 31:
===== Description ===== ===== Description =====
-Boot from the specified SAN drive.  If no SAN drive is explicitly specified then the default SAN drive (''%%0x80%%'') will be used.  If a [[:sanuri|SAN target URI]] is specified then it will be automatically attached as the specified SAN drive.+Boot from the specified SAN drive.  If no SAN drive is explicitly specified then the default SAN drive (''%%0x80%%'') will be used.  If one or more [[:sanuri|SAN target URIs]] are specified then they will be automatically attached as the specified SAN drive.
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. 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 46: Line 51:
The Master Boot Record (MBR) code present on most SAN targets will be unable to boot unless the target is attached as the default SAN drive (''%%0x80%%''). The Master Boot Record (MBR) code present on most SAN targets will be unable to boot unless the target is attached as the default SAN drive (''%%0x80%%'').
- 
-If you wish to attach to multiple SAN targets, each target must be attached as a different SAN drive. 
You can optionally specify a [[:sanuri|SAN target URI]] that will be automatically attached as the specified SAN drive before booting is attempted.  This drive will be automatically detached if booting then fails, unless the ''%%--keep%%'' option is specified. You can optionally specify a [[:sanuri|SAN target URI]] that will be automatically attached as the specified SAN drive before booting is attempted.  This drive will be automatically detached if booting then fails, unless the ''%%--keep%%'' option is specified.
 +
 +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 ''[[:cmd:sanhook]]'' command to attach each non-boot drive individually.
For the sake of backwards compatibility, you can use the ''[[:cfg:keep-san]]'' setting to prevent iPXE from detaching a SAN drive, and you can use the ''[[:cfg:skip-san-boot]]'' setting to prevent iPXE from booting from a SAN drive.  The combination of both of these settings provides functionality which is approximately equivalent to the ''[[:cmd:sanhook]]'' command. For the sake of backwards compatibility, you can use the ''[[:cfg:keep-san]]'' setting to prevent iPXE from detaching a SAN drive, and you can use the ''[[:cfg:skip-san-boot]]'' setting to prevent iPXE from booting from a SAN drive.  The combination of both of these settings provides functionality which is approximately equivalent to the ''[[:cmd:sanhook]]'' command.
 
cmd/sanboot.1343997003.txt.gz · Last modified: 2012/08/03 13:30 by mcb30
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki
All uses of this content must include an attribution to the iPXE project and the URL http://ipxe.org
References to "iPXE" may not be altered or removed.