The PXE-E32 error indicates that the PXE client did not receive a response from the TFTP server when attempting to download the boot file during network boot.

This typically means the PXE request is reaching the network, but the correct TFTP service is either not reachable, misconfigured, or overridden.

Possible Causes

1. No TFTP server configured for the IP range/subnet from which the device is PXE booting.
2. Incorrect or invalid settings in:
   • Configuration >> Properties >> Network Boot Listener
3. The BCM Agent service is not running on the configured Network Boot Listener for the relevant subnet / VLAN / site.
4. DHCP options 66 and 67 are misconfigured, for example:
5. Option 66 is set to the OSD Manager IP instead of the local Network Boot Listener IP.
6. Another TFTP server or application is responding on the same subnet, causing a conflict.

DHCP Option 66 and 67 Configuration

• Option 66 must contain the IP address (or resolvable hostname) of the OSD Network Boot Listener for the scope.
• Option 67 must contain the boot file name, depending onthe  firmware type:
  • BIOS x86
  • BIOS x64
  • UEFI

For detailed guidance, refer to the following KA:

Client Management: Os Deployment - Options 66 or 67, to use them or not to deploy or capture OS images

A) Common Configuration Scenarios

Scenario 1: Internal DHCP Gateway Enabled + DHCP Options 66/67 Configured

• This configuration is not supported.
• Only one method should be used:
• Either Internal DHCP Gateway
• Or DHCP Options 66 and 67

Recommended approach: Internal DHCP Gateway

Limitation: The target device must be in the same subnet as the Network Boot Listener.

Scenario 2: Internal DHCP Gateway Disabled + DHCP Options 66/67 Used

Verify the following:

• Option 66 points to the local Network Boot Listener, not the OSD Manager.
  • A common mistake is setting this to the OSD Manager IP/hostname.
• If using a hostname in Option 66:
  • Ensure it is resolvable from the target device (DNS resolution works).

Scenario 3: Another TFTP Server Exists on the Subnet

• Another network boot listener or third-party application may be acting as a TFTP server.
• This is a very common cause of PXE-E32 errors.
• Review the PXE boot screen or network capture details to identify the responding TFTP server.

B) Validate TFTP File Download Manually

To verify TFTP connectivity:

Install the TFTP Client feature on:

1. A PXE target device, or
2. Any system in the same subnet
3. (Windows: Programs and Features → Turn Windows features on or off)
4. Open Command Prompt
5. Run the following commands (replace with the Network Boot Listener hostname/IP):

tftp <NETWORK_BOOT_LISTENER> GET pxeboot.0
tftp <NETWORK_BOOT_LISTENER> GET bootx64.efi

Expected Result

• If the file download succeeds, PXE boot should work for devices on that subnet.
• If the download fails:
  • Capture network packets during a BCM OS Deployment or Capture attempt.
  • Share the packet capture with BMC Support for further analysis.