Holger Baust
2015-Feb-05 18:02 UTC
[syslinux] Problems with EFI PXE boot on Hp DL380p Gen9
Hello.
We are using pxelinux for years to boot Linux via PXE since years.
Since EFI is spreading, I changed configuration to be able to boot EFI
systems.
The "Client":
- HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available
- NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3),
FW: 5719-v1.38
The Server:
- ISC-DHCP with tfpd-hpa running on Debian 6.x
- syslinux 6.03, all files taken from this official binary distribution
from kernel.org
- different directories for bios / efi x64 and efi ia32 and all binaries
are in their correct directory
Remark:
Using a VM Version 9 on ESXi 5.5 with EFI boot as client runs perfect.
Using PXE on BIOS machines works without problems.
The Problem:
- Proliant tries to boot via PXE.
- NIC FW displays Params it got via DHCP:
Station IP Address is 192.168.111.172
Server IP Address is 192.168.111.1
NBP filename is /efi64/bootx64.efi
NBP filesize is 199952 bytes
Downloading NBP file ...
NBP file downloaded successfully.
Getting chached packet
My IP is 0.0.0.0
core_udp_sendto: stalling on configure with no mapping
core_udp_sendto: stalling on configure with no mapping
core_udp_sendto: stalling on configure with no mapping
core_udp_sendto: stalling on configure with no mapping
...
I think, bootx64.efi aka syslinux.efi is fetched and startet, but it
does not get the IP
correctly from a cached packet. Perhaps it should be possible to do an
additional DHCP
request syslinux.efi thinks the local IP is 0.0.0.0?
A pcap from tcpdump is attached.
Any suggestion / hint ?
Regards,
Holger Baust
--
freenet Datenkommunikations GmbH
Ein Unternehmen der freenet Group
Willst?tterstra?e 13
D-40549 D?sseldorf
Tel.: +49 (0) 211 53087 519
Fax: +49 (0) 211 5381573
Mobil: +49 (0) 170 4930127
holger.baust at freenet.ag
www.freenet.de
mobil.freenet.de
www.mobilcom-debitel.de
Gesch?ftsf?hrung: Andreas J?rgensen, Dr. Frank R?ders
Sitz der Gesellschaft: Hamburg
HRB 88147, Amtsgericht Hamburg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hp380g9_efi_pxe.pcap
Type: application/vnd.tcpdump.pcap
Size: 221071 bytes
Desc: not available
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20150205/329a835f/attachment-0001.pcap>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20150205/329a835f/attachment-0001.sig>
Geert Stappers
2015-Feb-05 22:33 UTC
[syslinux] Problems with EFI PXE boot on Hp DL380p Gen9
On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote:> Hello. > > We are using pxelinux for years to boot Linux via PXE since years. > Since EFI is spreading, I changed configuration to be able to boot EFI > systems. > > The "Client": > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), > FW: 5719-v1.38 > > The Server: > - ISC-DHCP with tfpd-hpa running on Debian 6.x > - syslinux 6.03, all files taken from this official binary distribution > from kernel.org > - different directories for bios / efi x64 and efi ia32 and all binaries > are in their correct directory > > Remark: > Using a VM Version 9 on ESXi 5.5 with EFI boot as client runs perfect. > Using PXE on BIOS machines works without problems. > > The Problem: > - Proliant tries to boot via PXE. > - NIC FW displays Params it got via DHCP: > Station IP Address is 192.168.111.172 > > Server IP Address is 192.168.111.1 > NBP filename is /efi64/bootx64.efi > NBP filesize is 199952 bytes > Downloading NBP file ... > > NBP file downloaded successfully. > Getting chached packet > My IP is 0.0.0.0 > core_udp_sendto: stalling on configure with no mapping > core_udp_sendto: stalling on configure with no mapping > core_udp_sendto: stalling on configure with no mapping > core_udp_sendto: stalling on configure with no mapping > ... > > I think, bootx64.efi aka syslinux.efi is fetched and startet, but it > does not get the IP > correctly from a cached packet. Perhaps it should be possible to do an > additional DHCP > request syslinux.efi thinks the local IP is 0.0.0.0? > > A pcap from tcpdump is attached.Nice capture! ( I think it is made at the TFTP server ) In packet number 8 from the PCAP-file is the "DHCP Request" In packet number 9 is an ARP Request ( who has 192.168.111.1 tell 192.168.111.172 ) In packet #10 the ARP Reply. In #11 starts the TFTP of /efi64/bootx64.efi, that ends at #290. In #291, #292 and #293 is .1 asking for .172> Any suggestion / hint ?The (IMHO) missing information is the "DHCP Acknowledge" that should have been between package #8 and #9. Capture that missing package. It should be "visible" at the DHCP server Groeten Geert Stappers -- Leven en laten leven ------------- volgend deel ------------ Een niet-tekst bijlage is gescrubt... Naam: signature.asc Type: application/pgp-signature Grootte: 836 bytes Omschrijving: Digital signature URL : <http://www.zytor.com/pipermail/syslinux/attachments/20150205/b3631230/attachment.sig>
You kind of lost me w/ those packet numbers as I'm not seeing the same on my end. I'm going to send you captures from the tftp server. Also, the master node uses UEFI, but I don't understand how that should matter for booting the diskless nodes. The diskless nodes are using normal BIOS (non-UEFI) settings. 10.0.0.11 is the tftp server (master) 10.0.1.1 is the diskless client Sending you more captures. On Thu, Feb 5, 2015 at 4:33 PM, Geert Stappers via Syslinux < syslinux at zytor.com> wrote:> On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > > Hello. > > > > We are using pxelinux for years to boot Linux via PXE since years. > > Since EFI is spreading, I changed configuration to be able to boot EFI > > systems. > > > > The "Client": > > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > > - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), > > FW: 5719-v1.38 > > > > The Server: > > - ISC-DHCP with tfpd-hpa running on Debian 6.x > > - syslinux 6.03, all files taken from this official binary distribution > > from kernel.org > > - different directories for bios / efi x64 and efi ia32 and all binaries > > are in their correct directory > > > > Remark: > > Using a VM Version 9 on ESXi 5.5 with EFI boot as client runs perfect. > > Using PXE on BIOS machines works without problems. > > > > The Problem: > > - Proliant tries to boot via PXE. > > - NIC FW displays Params it got via DHCP: > > Station IP Address is 192.168.111.172 > > > > Server IP Address is 192.168.111.1 > > NBP filename is /efi64/bootx64.efi > > NBP filesize is 199952 bytes > > Downloading NBP file ... > > > > NBP file downloaded successfully. > > Getting chached packet > > My IP is 0.0.0.0 > > core_udp_sendto: stalling on configure with no mapping > > core_udp_sendto: stalling on configure with no mapping > > core_udp_sendto: stalling on configure with no mapping > > core_udp_sendto: stalling on configure with no mapping > > ... > > > > I think, bootx64.efi aka syslinux.efi is fetched and startet, but it > > does not get the IP > > correctly from a cached packet. Perhaps it should be possible to do an > > additional DHCP > > request syslinux.efi thinks the local IP is 0.0.0.0? > > > > A pcap from tcpdump is attached. > > Nice capture! > > ( I think it is made at the TFTP server ) > > > In packet number 8 from the PCAP-file is the "DHCP Request" > > In packet number 9 is an ARP Request ( who has 192.168.111.1 tell > 192.168.111.172 ) > > In packet #10 the ARP Reply. > > In #11 starts the TFTP of /efi64/bootx64.efi, that ends at #290. > > In #291, #292 and #293 is .1 asking for .172 > > > > > Any suggestion / hint ? > > The (IMHO) missing information is the "DHCP Acknowledge" > that should have been between package #8 and #9. > > Capture that missing package. It should be "visible" at the DHCP server > > > > Groeten > Geert Stappers > -- > Leven en laten leven > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
Holger Baust
2015-Feb-05 23:08 UTC
[syslinux] Problems with EFI PXE boot on Hp DL380p Gen9
Hello... Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux:> On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: >> Hello. >> >> We are using pxelinux for years to boot Linux via PXE since years. >> Since EFI is spreading, I changed configuration to be able to boot EFI >> systems. >> >> The "Client": >> - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available >> - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), >> FW: 5719-v1.38 >> >> The Server: >> - ISC-DHCP with tfpd-hpa running on Debian 6.x >> - syslinux 6.03, all files taken from this official binary distribution >> from kernel.org >> - different directories for bios / efi x64 and efi ia32 and all binaries >> are in their correct directory >> >> Remark: >> Using a VM Version 9 on ESXi 5.5 with EFI boot as client runs perfect. >> Using PXE on BIOS machines works without problems. >> >> The Problem: >> - Proliant tries to boot via PXE. >> - NIC FW displays Params it got via DHCP: >> Station IP Address is 192.168.111.172 >> >> Server IP Address is 192.168.111.1 >> NBP filename is /efi64/bootx64.efi >> NBP filesize is 199952 bytes >> Downloading NBP file ... >> >> NBP file downloaded successfully. >> Getting chached packet >> My IP is 0.0.0.0 >> core_udp_sendto: stalling on configure with no mapping >> core_udp_sendto: stalling on configure with no mapping >> core_udp_sendto: stalling on configure with no mapping >> core_udp_sendto: stalling on configure with no mapping >> ... >> >> I think, bootx64.efi aka syslinux.efi is fetched and startet, but it >> does not get the IP >> correctly from a cached packet. Perhaps it should be possible to do an >> additional DHCP >> request syslinux.efi thinks the local IP is 0.0.0.0? >> >> A pcap from tcpdump is attached. > Nice capture!thx.> ( I think it is made at the TFTP server )Sure.> > In packet number 8 from the PCAP-file is the "DHCP Request" > > In packet number 9 is an ARP Request ( who has 192.168.111.1 tell 192.168.111.172 ) > > In packet #10 the ARP Reply. > > In #11 starts the TFTP of /efi64/bootx64.efi, that ends at #290. > > In #291, #292 and #293 is .1 asking for .172 > > > >> Any suggestion / hint ? > The (IMHO) missing information is the "DHCP Acknowledge" > that should have been between package #8 and #9. > > Capture that missing package. It should be "visible" at the DHCP server >Hmm.. This might be difficult. tftpd and dhcp are on the same system. If there was one, this should have been captured. There are a lot of clients behind this system so getting the right filter syntax might be difficult. This Problem seems to be on all HP Proliant DL380Gen9 and DL360Gen9 which have in fact the same systemboard. MfG / regards, Holger Baust -- freenet Datenkommunikations GmbH Ein Unternehmen der freenet Group Willst?tterstra?e 13 D-40549 D?sseldorf Tel.: +49 (0) 211 53087 519 Fax: +49 (0) 211 5381573 Mobil: +49 (0) 170 4930127 holger.baust at freenet.ag www.freenet.de mobil.freenet.de www.mobilcom-debitel.de Gesch?ftsf?hrung: Andreas J?rgensen, Dr. Frank R?ders Sitz der Gesellschaft: Hamburg HRB 88147, Amtsgericht Hamburg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 204 bytes Desc: OpenPGP digital signature URL: <http://www.zytor.com/pipermail/syslinux/attachments/20150206/979a7359/attachment.sig>
Apologies to the OP and all, I got my wires crossed and replied in the wrong thread. On Thu, Feb 5, 2015 at 5:40 PM, Lane < software.research.development at gmail.com> wrote:> I didn't understand that either, why DHCP was not captured. The DHCP > server and the TFTP server are both on the master node. But I do have > another capture file that collects everything and shows them. > > And I do know that every time I try to boot the diskless node, I will see > a Discover, Offer, Request, and ACK in /var/log/messages of the master > node. Here is a screen grab of a full capture as shown in wireshark for > DHCP when booting the diskless node. > > 0x73f95441 is the diskless node. > > > > On Thu, Feb 5, 2015 at 5:08 PM, Holger Baust via Syslinux < > syslinux at zytor.com> wrote: > >> Hello... >> >> Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux: >> > On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: >> >> Hello. >> >> >> >> We are using pxelinux for years to boot Linux via PXE since years. >> >> Since EFI is spreading, I changed configuration to be able to boot EFI >> >> systems. >> >> >> >> The "Client": >> >> - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available >> >> - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), >> >> FW: 5719-v1.38 >> >> >> >> The Server: >> >> - ISC-DHCP with tfpd-hpa running on Debian 6.x >> >> - syslinux 6.03, all files taken from this official binary distribution >> >> from kernel.org >> >> - different directories for bios / efi x64 and efi ia32 and all >> binaries >> >> are in their correct directory >> >> >> >> Remark: >> >> Using a VM Version 9 on ESXi 5.5 with EFI boot as client runs perfect. >> >> Using PXE on BIOS machines works without problems. >> >> >> >> The Problem: >> >> - Proliant tries to boot via PXE. >> >> - NIC FW displays Params it got via DHCP: >> >> Station IP Address is 192.168.111.172 >> >> >> >> Server IP Address is 192.168.111.1 >> >> NBP filename is /efi64/bootx64.efi >> >> NBP filesize is 199952 bytes >> >> Downloading NBP file ... >> >> >> >> NBP file downloaded successfully. >> >> Getting chached packet >> >> My IP is 0.0.0.0 >> >> core_udp_sendto: stalling on configure with no mapping >> >> core_udp_sendto: stalling on configure with no mapping >> >> core_udp_sendto: stalling on configure with no mapping >> >> core_udp_sendto: stalling on configure with no mapping >> >> ... >> >> >> >> I think, bootx64.efi aka syslinux.efi is fetched and startet, but it >> >> does not get the IP >> >> correctly from a cached packet. Perhaps it should be possible to do an >> >> additional DHCP >> >> request syslinux.efi thinks the local IP is 0.0.0.0? >> >> >> >> A pcap from tcpdump is attached. >> > Nice capture! >> thx. >> > ( I think it is made at the TFTP server ) >> Sure. >> > >> > In packet number 8 from the PCAP-file is the "DHCP Request" >> > >> > In packet number 9 is an ARP Request ( who has 192.168.111.1 tell >> 192.168.111.172 ) >> > >> > In packet #10 the ARP Reply. >> > >> > In #11 starts the TFTP of /efi64/bootx64.efi, that ends at #290. >> > >> > In #291, #292 and #293 is .1 asking for .172 >> > >> > >> > >> >> Any suggestion / hint ? >> > The (IMHO) missing information is the "DHCP Acknowledge" >> > that should have been between package #8 and #9. >> > >> > Capture that missing package. It should be "visible" at the DHCP server >> > >> Hmm.. This might be difficult. tftpd and dhcp are on the same system. >> If there was one, this should have been captured. >> There are a lot of clients behind this system so getting the right >> filter syntax >> might be difficult. >> >> This Problem seems to be on all HP Proliant DL380Gen9 and DL360Gen9 >> which have in fact the same systemboard. >> >> >> MfG / regards, >> Holger Baust >> >> -- >> freenet Datenkommunikations GmbH >> Ein Unternehmen der freenet Group >> Willst?tterstra?e 13 >> D-40549 D?sseldorf >> >> Tel.: +49 (0) 211 53087 519 >> Fax: +49 (0) 211 5381573 >> Mobil: +49 (0) 170 4930127 >> >> holger.baust at freenet.ag >> www.freenet.de >> mobil.freenet.de >> www.mobilcom-debitel.de >> >> Gesch?ftsf?hrung: Andreas J?rgensen, Dr. Frank R?ders >> Sitz der Gesellschaft: Hamburg >> HRB 88147, Amtsgericht Hamburg >> >> >> >> _______________________________________________ >> Syslinux mailing list >> Submissions to Syslinux at zytor.com >> Unsubscribe or set options at: >> http://www.zytor.com/mailman/listinfo/syslinux >> > >