iPXE discussion forum

Full Version: XenServer 7.0 iPXE errors downloading SCCM image
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi guys, I am having some problems when attempting to build a VDI using a new XenServer 7.0 installation, via an SCCM image (iPXE looks the be the PXE client of choice for my XenServer installation).

iPXE> autoboot
net0: correct MAC address using rt18139 on PCI00:05.0 (open)
[Link:up, TX:11 TX:0, RX:1003, RXE:965]
[RXE: 625 x "The socket is not connected (http://ipxe.org/380f6001)"]
[RXE: 256 x "The operation not supported (http://ipxe.org/3c086003)"]
[RXE: 84 x "Error 0x440e6003 (http://ipxe.org/0x440e6003)"]
DHCP (net0 correct MAC)......... ok
net0: xxx.xxx.xxx.xxx/ gw xxx.xxx.xxx.xxx
Next Sever: xxx.xxx.xxx.xxx
Filename: /smsboot/x64/wdsnbp.com... Error 0x3d126001 (http://ipxe.org/380f6001)

Note that the RXE errors are not seen during the normal boot sequence, I just receive the last error 0x3d126001, to see the RXE errors I have to boot via the CLI.

Permissions and path to the folder all look good. The image is being used to build other machines via VMware or SCCM OK.

The error codes translate to:
http://ipxe.org/err/380f60 - Error: The socket is not connected
http://ipxe.org/err/3c0860 - Error: Operation not supported
http://ipxe.org/err/440e60 - Error: Protocol not supported

Any tips on how best to troubleshoot this would be appreciated.

(2016-09-15 15:27)dazzlr Wrote: [ -> ]Filename: /smsboot/x64/wdsnbp.com... Error 0x3d126001 (http://ipxe.org/380f6001)

When I follow that link I see this:
Quote:This error indicates that a UDP packet was received for a port on which iPXE was not listening. This error is generally harmless. For example, DHCP requests sent by other clients on the same network may trigger this error.

Can you check that you are using the latest version of iPXE
and also try to run these commands manually:
imgfetch ${filename}

Are you running in efi or legacy mode for this? and have you tried any other virtual nic, such as e1000 or virtio (Not a xen user myself, but think those are available as emulated nics as well)
So thanks for the reply NiKiZe, that really helped and I manually changed the config to point to a legacy Altiris boot file as a test, and that actually connected OK.

Filename: BStrap/x64/BStrap.0
tftp://xxx.xxx.xx.xx/BStrap/x64/BStrap.0... OK

Altiris, inc. X86PC PreBoot, PXE-2.x Enhanced
Build ID=402

PXEPreZero: Invalid PXE Server list format.

So the issue it seems is with our TFTP boot program wdsnbp.com and the other errors look like they can be safely ignored. I believe this file is either the original one that comes with SCCM, or perhaps a modified version... I'll need to check with our SCCM guys but this boot file is used throughout our organisation to build (thousands of) machines via SCCM so it seems that only XenServer 7.0 is having a problem with it. I'll do some digging and see what Citrix requires from a bootfile and what the problem might be.
(2016-09-23 12:24)dazzlr Wrote: [ -> ]Filename: BStrap/x64/BStrap.0
PXEPreZero: Invalid PXE Server list format.

So it has issues with one or more PXE options would be my guess. check the DHCP server and maybe do a packet capture of DHCP packets for a working and non working boot with that NBP.
Reference URL's