So we're trying to do some provisioning of some blade servers (HP BL465c). We're on 7.4.1. The application server and pxe server and datastore are all on the same vlan/network segment as the bare-metal box.
Instead of configuring a linux or windows dhcp server, the client is configuring the router to give out DHCP.
So when we initially reboot the baremetal server, we get this error:
PXE-E53: No boot filename received
I know that typically means that the dhcp server did not reply to the broadcast request from the baremetal server (and that the baremetal server has no dhcp IP) but from our dhcp logs, we see that an IP was given out on the same network segment. We didn't do DHCP/IP helper because everything is on the same vlan/network segment.
What's weird is that if we set the boot file scope option on the dhcp router (giving it a specific boot file name), then we seem to get past the PXE-E53 error. We then are able to actually see the IP that was given out by the dhcp router on the bare metal console screen.
So I guess the question is, has anyone ever seen the need to set the boot file scope option to give the specific boot filename? (we also set the normal 211 and 212 option as well).
After all that and after we kept the boot filename option set to some file name, we then get this error:
PXE-E32: TFTP Open Timeout
Which again typically means the tftp server is not running or we can't connect to it. If we manually do a tftp command to our pxe/tftp server on the same vlan/network segment, it succeeds, but the baremetal server never seems to execute the tftp request or is pointing to something incorrect and nothing gets logged in the tftpsvr.log file when the baremetal server gives the PXE-E32 error. I double checked the Provisioning Manager Console for the Tools->Configuration TFTP tab and the correct IP address is set there. There are 2 NICs on the bare metal server, 1 NIC is connected to a production network, the other NIC is connected to the provisioning network. I'm specifying the IP of the NIC that is on the provisioning network.
Both pxesvr.log and tftpsvr.log are set to the DEBUG levels. I can't completely decipher the pxesvr.log but this one message stood out: Does anyone know what this means?
Thanks for any help/insight!