Warewulf IPXE boot

[Roger Robinson]

Hi,

I have setup a warewulf controller. But when I try to PXE boot I get the messages in the attached image.

In the dhcp I can see this.

if exists user-class and option user-class = "iPXE" {
    filename "http://10.4.44.99:9873/ipxe/${mac:hexhyp}";
} else {
    if option architecture-type = 00:0B {
        filename "/warewulf/arm64.efi";
    } elsif option architecture-type = 00:09 {
        filename "/warewulf/x86_64.efi";
    } elsif option architecture-type = 00:07 {
        filename "/warewulf/x86_64.efi";
    } elsif option architecture-type = 00:00 {
        filename "/warewulf/x86_64.kpxe";
    }
}

So the first option must be chosen. But what is this referring to I can not find ipxe/${mac:hexhyp}"; on my warewulf controller.

I can see the directory with the  warewulf/*.kpxe files.

Thanks

Roger

[Jason Stover]

It's looking for the file: /ipxe/b0-26-28-e3-c1-f0

b0:26:28:e3:c1:f0 is the MAC of the NIC that made the request....
${mac:hexhyp} .... MAC address Hex, Hyphenated.

-J

> --
> You received this message because you are subscribed to the Google Groups "Warewulf" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to warewulf+u...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/13fcae95-6f79-4de9-8876-41cd24550625n%40lbl.gov.

[Roger Robinson]

Yes and I've added this in with 

wwctl node add catcompute5-2 --ipaddr 10.4.44.5 --hwaddr b0:26:28:e3:c1:f0 --discoverable yes

[Roger Robinson]

My question is why is it not finding this ? or where should this file be ? Why is it http: instead of tftp: ?

[Roger Robinson]

I've done a dnf remove warewulf and a dnf install -y warewulf and set everything back up.
It has worked this time.
I had obviously configured something incorrectly. But was unable to spot it.

Thanks 

[Jonathon Anderson]

Roger,

I'm glad to see that you were able to get it working.

Regarding your question of where the "http://10.4.44.99:9873/ipxe/${mac:hexhyp}" file comes from: this is dynamically generated and served by the Warewulf daemon itself.

The compute node, when booting, will pull the ipxe binary over tftp, but then ipxe uses http to download the image itself, as it is more robust.

If it's not working in the future, you can check the Warewulf log (e.g., /var/log/warewulfd.log) to see if it's reporting any error messages.

~jonathon

To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/0fc4481b-8fd2-493a-b681-d06b49d6df3bn%40lbl.gov.