Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
cmd:sanboot [2017/03/26 13:32] mcb30 |
cmd:sanboot [2017/04/12 15:26] mcb30 |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Synopsis ===== | ===== Synopsis ===== | ||
| - | sanboot [--drive <drive>] [--no-describe] [--keep] [<uri>] [<uri>...] | + | sanboot [--drive <drive>] [--filename <filename>] [--no-describe] |
| + | [--keep] [<uri>] [<uri>...] | ||
| ===== Examples ===== | ===== Examples ===== | ||
| Line 15: | Line 16: | ||
| sanboot iscsi:192.168.0.101::::iqn.2010-04.org.ipxe.squirrel:storage \ | 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 | iscsi:192.168.0.102::::iqn.2010-04.org.ipxe.squirrel:storage | ||
| + | |||
| + | === Boot from an iSCSI target with a non-default filename === | ||
| + | |||
| + | sanboot --filename \EFI\redhat\grub.efi \ | ||
| + | iscsi:192.168.0.2::::iqn.2010-04.org.ipxe.chipmunk:rhel6 | ||
| === Boot from an HTTP target === | === Boot from an HTTP target === | ||
| Line 34: | Line 40: | ||
| 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. | ||
| + | |||
| + | On some platforms (e.g. UEFI), the ''%%--filename%%'' option may be used to specify the path to the bootloader within the specified SAN drive. | ||
| ===== Command status ===== | ===== Command status ===== | ||
| Line 54: | Line 62: | ||
| 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 disk. | + | 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. | 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. | ||
| + | |||
| + | On a UEFI platform, some older operating systems (e.g. RHEL6) will install the bootloader with a non-default filename. You can use the ''%%--filename%%'' option (or the ''[[:cfg:san-filename]]'' setting) to specify the correct bootloader filename. For example: | ||
| + | |||
| + | sanboot --filename \EFI\redhat\grub.efi \ | ||
| + | iscsi:192.168.0.2::::iqn.2010-04.org.ipxe.chipmunk:rhel6 | ||
| 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. | ||
