Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Boot fails with No DHCP Root Path Option 17 found
2013-05-25, 10:13 (This post was last modified: 2013-05-25 10:30 by robinsmidsrod.)
Post: #2
RE: Boot fails with No DHCP Root Path Option 17 found
You're using the Intel iSCSI boot support, not iPXE. You'll have to configure the root-path in your ISC DHCPd config according to "Intel iSCSI Remote Boot" specifications.

I found the IntelĀ® iSCSI Remote Boot pages where I downloaded the User Guide (PROINFO.zip). I then unpacked that one and opened up APPS/iSCSI/index.htm which indeed shows that the Intel iSCSI Remote boot agent uses the same syntax for the root-path as iPXE.

You have configured in your dhcpd.conf to only give out the root-path option to iPXE clients. Intel iSCSI Remote Boot is not iPXE, so it sees no root-path option. Remove the conditional and you should be set. Also make sure you provide a hostname, as the Intel iSCSI Remote boot client seems to need that as well.

I do wonder why you're using the Intel iSCSI Remote Boot agent instead of iPXE, though. If you switch your Intel adapter firmware to PXE mode (instead of iSCSI) and chainload iPXE you'll get all the benefits of iPXE scripting AND iSCSI in one package. It's your call. Just don't confuse the two of them. They're different pieces of software (that does the same thing).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Boot fails with No DHCP Root Path Option 17 found - robinsmidsrod - 2013-05-25 10:13



User(s) browsing this thread: 2 Guest(s)