[ipxe-devel] Default path in IPXE chain command

Lee Turchin lee.turchin at hitachivantara.com
Wed Jan 16 15:15:40 UTC 2019

Hi Christian,
Your advice re: IPXE script changes worked and now I am faced with fact that image is too large to be loaded.  But, at least I am making progress toward the bare metal install completion.
Thanks millions sir.
Screenshot attached.

-----Original Message-----
From: Christian Nilsson <nikize at gmail.com> 
Sent: Tuesday, January 15, 2019 3:38 PM
To: Lee Turchin <lee.turchin at hitachivantara.com>
Cc: ipxe-devel at lists.ipxe.org
Subject: Re: [ipxe-devel] Default path in IPXE chain command

On Wed, 16 Jan 2019 at 00:30, Lee Turchin <lee.turchin at hitachivantara.com> wrote:
> Hi,
> I need to figure out the default search path for configuring IPXE
> I receive an error that files cannot be located during TFTP boot.
> Chain command in bootstrap.ipxe is the below.  Please note the first line- chain https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F172.17.11.119%3A8150%2Fsvc%2Fboot&data=01%7C01%7Clee.turchin%40hitachivantara.com%7C416d08bb9ff848cf820808d67b428a27%7C18791e1761594f52a8d4de814ca8284a%7C0&sdata=Zhji8NjciDbl7XpY%2BYjopZ0IUAmH8jtdoHv7WsCWjf8%3D&reserved=0?  Where is the /svc/boot directory location supposed to be on a CentOS 7 system? How do I change that to a viable directory and/or create that same directory with the correct files?
> Thank you,
> Lee turchin
> chain 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F172.17
> .11.119%3A8150%2Fsvc%2Fboot%3Fnet0%3D%24&data=01%7C01%7Clee.turchi
> n%40hitachivantara.com%7C416d08bb9ff848cf820808d67b428a27%7C18791e1761
> 594f52a8d4de814ca8284a%7C0&sdata=YXovg%2BSw1Pkd%2FqidSrK1h%2BYnkRu
> %2BUYCUOMyIAe2usTA%3D&reserved=0{net0/mac:hexhyp}&net1=${net1/mac:
> hexhyp}&net2=${net2/mac:hexhyp}&net3=${net3/mac:hexhyp}&dhcp_mac=${dhc
> p_mac}&serial=${serial}&asset=${asset}&uuid=${uuid}&fact_boot_type=${p
> latform} || goto error

in iPXE there is no default search path, default filename or anything similar.
It is configured via dhcp options, or possibly embeded script.

Your example chain command would load the next iPXE script.
So there is no correct path, or correct files for iPXE But depending on your goal there might be a "required" set of files.

Also a note of your chain command... if you replace net0=${net0/mac:hexhyp} and it's friends with net=${netX/mac:hexhyp} you will get the last opened interface.
for example if dhcp runs before this and net0 and net1 fails but net2 succeds, you would get the data for net2.
Also remember to escape serial and uuid - since they might contain some for url none well handled chars.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IPXE-Update.JPG
Type: image/jpeg
Size: 72158 bytes
Desc: IPXE-Update.JPG
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20190116/9f0b1318/attachment.jpe>

More information about the ipxe-devel mailing list