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 | ||
|
sanuri [2011/12/05 21:31] mcb30 |
sanuri [2013/04/11 12:21] mcb30 |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| * ''<protocol>'' is ignored and can be left empty.((The only valid value for ''<protocol>'' is ''6'', indicating that the protocol is TCP.)) | * ''<protocol>'' is ignored and can be left empty.((The only valid value for ''<protocol>'' is ''6'', indicating that the protocol is TCP.)) | ||
| * ''<port>'' is the TCP port of the iSCSI target. It can be left empty, in which case the default port (3260) will be used. | * ''<port>'' is the TCP port of the iSCSI target. It can be left empty, in which case the default port (3260) will be used. | ||
| - | * ''<LUN>'' is the SCSI LUN of the boot disk. It can be left empty, in which case the default LUN (0) will be used. | + | * ''<LUN>'' is the SCSI LUN of the boot disk, in hexadecimal. It can be left empty, in which case the default LUN (0) will be used. |
| * ''<targetname>'' is the iSCSI target IQN. | * ''<targetname>'' is the iSCSI target IQN. | ||
| Line 78: | 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. |
