Hi all. My x86 based DHCP/PXE solaris installs recently stopped working and I've tracked it down to a change in the pxegrub behavior. I don't know what could have changed that would have caused this.
All along, the PXE boot ROM would do the whole DHCP disc,offer,request,ack thing. Then from the info it received in the DHCP response it would load pxegrub through TFTP. That much at least is the same. Previously, (To the best of my memeory) pxegrub would then repeat the DHCP conversation, minus the PXE client ID (not that it should matter since I have all the important info in the host Macro.) and in the response it would find the GRUB site option 150 that specifies the file name for the menu file. Now, I don't see pxegrub sending any DHCP queries at all, it seems to reuse the data from the PXE boot ROM query. It doesn't know the name of the menu file and can't load it so I get a prompt. Snoop shows one DHCP query<->response, and then the TFTP for pxegrub. The debug output of the DHCP server shows the same. Questions: 1) Did pxegrub ever do it's own DHCP queries? or has it always just reused the existing data? 2) If it really used to make it's own queries, what would make it stop? 3) If it always reused the info, then in the past the DHCP server must have been including the contents of the host macro in the first response. What would make the DHCP server stop doing that? I've verified all the Macro names match, and the DHCP server doesn't complain about missing macros when it starts. I really don't get it, as this used to work. I keep asking myself 'What's changed?' and I can't come up with anything. Anyone got any ideas? -Kyle
