Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sanboot:iscsi_boot [2009/07/10 05:17] rulerof Added a section for Microsoft DHCP, separated DHCPd section, pictures for MS DHCP and sanboot, extended root path information and description of arguments. Link to RFC 4173. |
sanboot:iscsi_boot [2009/10/29 17:21] (current) mcb30 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Booting from an iSCSI target ====== | ====== Booting from an iSCSI target ====== | ||
| - | =====Configuring Root Path on your DHCP Server==== | + | ===== Configuring your DHCP Server ===== |
| - | ===Using DHCPd=== | + | ==== Using ISC dhcpd ==== |
| Place the following two lines in ///etc/dhcpd.conf//: | Place the following two lines in ///etc/dhcpd.conf//: | ||
| Line 14: | Line 14: | ||
| You will probably need to restart your DHCP server for the changes to take effect: | You will probably need to restart your DHCP server for the changes to take effect: | ||
| - | root@chipmunk# /etc/init.d/dhcpd restart | + | /etc/init.d/dhcpd restart |
| - | ===Using Microsoft DHCP Server=== | + | ==== Using Microsoft DHCP Server ==== |
| - | Depending on your deployment, right click either "Server Options," "Scope Options," or a reservation for the client you wish to boot (if you're unsure, use "Server Options"), and then click "Configure Options." In the options window, scroll down to and click the checkbox next to "017 Root Path," and enter the root path string for your iSCSI target in the "String Value" field, for example: | + | In the DHCP administrative tool, right-click on //Server Options// and choose //Configure Options//. Click on "017 Root Path" and set the "String value" to |
| - | iscsi:my.target.dns.name::::iqn.2007-08.name.dns.target.my:iscsiboot | + | iscsi:my.target.dns.name::::iqn.2007-08.name.dns.target.my:iscsiboot |
| - | {{:sanboot:msrootpath.jpg}} | + | where //my.target.dns.name// is the DNS name (or IP address) of your iSCSI target, and //iqn.2007-08.name.dns.target.my:iscsiboot// is the iSCSI target IQN that you wish to boot from. |
| - | + | ||
| - | Where //my.target.dns.name// is the DNS name (or IP address) of your iSCSI target, and //iqn.2007-08.name.dns.target.my:iscsiboot// is the iSCSI target IQN that you wish to boot from. | + | |
| - | =====Booting Your Client===== | + | {{ :screenshots:winnt_dhcp_iscsi.png?716×511 |Windows DHCP server configuration}} |
| + | ===== Booting Your Client ===== | ||
| Boot your diskless client using gPXE. If all has gone well, you should see it boot from your iSCSI target image. | Boot your diskless client using gPXE. If all has gone well, you should see it boot from your iSCSI target image. | ||
| Line 38: | Line 37: | ||
| \\ | \\ | ||
| - | ====== Troubleshooting ====== | + | ===== Troubleshooting ===== |
| If you have difficulties booting Windows from SAN, take a look at [[:sanboot:winnt_iscsi_debug|Debugging Windows iSCSI boot]]. | If you have difficulties booting Windows from SAN, take a look at [[:sanboot:winnt_iscsi_debug|Debugging Windows iSCSI boot]]. | ||
| - | =====Extended Description of iSCSI Root Path Syntax===== | + | ===== iSCSI Root Path Syntax ===== |
| - | ===Root Path Arguments=== | + | ==== Theory ==== |
| Described heavily in depth in RFC 4173, the root path string used to boot from SAN can range from relatively simple, to a //very// explicit, information packed line. According to the RFC, the root path string is formatted as follows: | Described heavily in depth in RFC 4173, the root path string used to boot from SAN can range from relatively simple, to a //very// explicit, information packed line. According to the RFC, the root path string is formatted as follows: | ||
| Line 57: | Line 56: | ||
| **"targetname"** is required, and should be the iSCSI target IQN you wish to boot from.\\ | **"targetname"** is required, and should be the iSCSI target IQN you wish to boot from.\\ | ||
| - | ===Practically Speaking=== | + | ==== Practice ==== |
| For most non-complex deployments, such as the samples in above sections, your root path will look like: | For most non-complex deployments, such as the samples in above sections, your root path will look like: | ||
| Line 69: | Line 68: | ||
| Furthermore, the LUN ID itself has a rather sophisticated set of rules for how it can be defined, but that goes beyond the scope of this article. | Furthermore, the LUN ID itself has a rather sophisticated set of rules for how it can be defined, but that goes beyond the scope of this article. | ||
| - | ===Advanced Reading=== | + | ==== Advanced Reading ==== |
| For more information, please see pages 3 and 4 of [[http://www.rfc-archive.org/getrfc.php?rfc=4173|RFC 4173]]. | For more information, please see pages 3 and 4 of [[http://www.rfc-archive.org/getrfc.php?rfc=4173|RFC 4173]]. | ||
| + | |||
