Error 0x3e11613b With PXE Boot

I'm running K2000 version 6.1.251 and am having trouble booting my Dell PowerEdge Servers via PXE boot. 

During the boot process, I'm shown this on the Server:

iPXE 1.0.0 -- Open Source Network Boot Firmware -- http://ipxe.org
Configuring (net0 <MAC ADDRESS SHOWN>)...... ok
Welcome to K2000
http:///boot/boot.php... Error 0x3e11613b (http://ipxe.org/0x3e11613b)

After that, the server continues it's boot sequence. The page referenced doesn't exist yet, so that's less than helpful.

Over in the logs of the K2000, I see this:

Jun 4 16:28:18 sysman in.tftpd[82920]: RRQ from filename undionly.kpxe
Jun 4 16:28:18 sysman in.tftpd[82919]: tftp: client does not accept options
Jun 4 16:28:18 sysman in.tftpd[82919]: RRQ from filename undionly.kpxe

I'm able to PBX boot into my Dell Latitude laptops with no issue. Any help with this would be great.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: SMal.tmcc 4 years ago
Red Belt

Could be the servers are on a different network from the laptops and you do not have dns/dhcp configured for that subnet.

Also check the settings for boot type (legacy or uefi) on the machines and in dhcp for that network. 

There my be firewall or acl settings blocking the server on that subnet

Take a laptop you know that boots and plug it into were the servers are and see what it does there.  That will tell you if it is the servers settings or the network configuration

  • Some laptops are set for Legacy boot, while others are set for UEFI. Our environment only has one Subnet, and I can see that when the server tries to boot via PXE, it is given an IP address from DHCP that is in the same range as laptops that are able to connect.

    Oddly enough, the PXE boot IS successful sometimes, with me doing something other than simply restarting the server. Yesterday when I posted this question, it was never able to boot via PXE, however today, it did boot successfully at random times... - nick.chirchirillo@richardson.com 4 years ago
    • Are you using the built in dhcp or external. if external what platform is dhcp on
      is your dhcp configured for dual pxe boot? (supporting both legacy and uefi)

      also check the bios version on the power edge

      you may also have to tweek the settings on the kbox
      For UEFI - KBE Boot delay on network page
      For Legacy you may have to check "Use Memdisk to boot this Boot Environment for BIOS clients " under the boot env detail - SMal.tmcc 4 years ago
      • the line RRQ from filename undionly.kpxe is the server trying to get the legacy boot file from the kbox the uefi file is ipxe.efi - SMal.tmcc 4 years ago
Posted by: Channeler 4 years ago
Red Belt

It seems to be DNS related:

You can safely ignore this line:

Jun 4 16:28:18 sysman in.tftpd[82919]: tftp: client does not accept options
Make sure the DHCP's option 66 for that subnet is the KACE SDA IP , no it's hostname.

I have seen this happening in networks where there are multiple DHCPs working.... You could do a test by moving (if possible) that PowerEdge server to the same subnet where your Latitudes are, and attempt to PXE boot there. (or maybe the other way around is easier, take one Latitude into the PowerEdge Subnet, and attempt to PXE boot).

If it works, is an environmental issue.... In a good environment PXE boot should work fine across states even countries(not recommended, but it's possible).

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ