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 | ||
sanuri [2011/12/05 21:17] mcb30 |
sanuri [2011/12/05 21:37] mcb30 |
||
---|---|---|---|
Line 9: | Line 9: | ||
option root-path "iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage"; | option root-path "iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage"; | ||
+ | |||
+ | or as the ''[[:cfg:root-path]]'' DHCP option (using the [[:howto:msdhcp|Microsoft DHCP server]]): | ||
+ | |||
+ | {{ :screenshots:msdhcp_set_root_path.png?202x224 |Root path in the Microsoft DHCP server}} | ||
The format of the SAN URI depends upon the SAN protocol that you are using. | The format of the SAN URI depends upon the SAN protocol that you are using. | ||
Line 74: | Line 78: | ||
* ''<lun>'' is the SCSI LUN of the boot disk. | * ''<lun>'' is the SCSI LUN of the boot disk. | ||
- | There is no specific syntax for FCoE, and there is no way to specify a particular network device within an FCP/FCoE SAN URI. FCoE interfaces are created automatically whenever an FCoE fabric is detected, and iPXE will search for the FCP target on all open FCoE interfaces. | + | There is no separate syntax for FCoE, and there is no way to specify a particular network device within an FCP/FCoE SAN URI. FCoE interfaces are created automatically whenever an FCoE fabric is detected, and iPXE will search for the FCP target on all open FCoE interfaces. |