PXE boot fails with "PXE-E53: No boot filename received" only on a VM vlan
search cancel

PXE boot fails with "PXE-E53: No boot filename received" only on a VM vlan


Article ID: 248938


Updated On:


Deployment Solution


Attempting to network boot endpoints on a different subnet/vlan from where the NBS/PXE server resides. Between the PXE server and endpoints that are network booting there is a Cisco ACI fabric equipment acting as a DHCP relay.

The ACI fabric network is dropping offers that do not include Option 82 - it appears our NBS server does not offer option 82 so the offer is silently dropped by the fabric.


ITMS 8.6 RU2


Cisco ACI fabric with IP helpers is dropping DHCP offers (from PXE/NBS) because they do not include Option 82.

Wireshark capture shows no Option-82 offered from PXE/NBS and this appears to be standard for most PXE servers.


A Feature Request has been entered to have the NBS/PXE respond with option 82 in the offer.


  • Create a bootable ISO of the preboot environment and boot to that on the VM’s
  • Place a PXE server on a supported OS within the VM environment the clients are able to PXE boot to without issue
  • Create and deploy Automation Folders to the endpoints

Additional Information

KB Document:

DHCP Relay Section:

Customer using Cisco, not Juniper but same issue: