Clients not booting into the k2 RSA
Hi people
I have built The RSA. Its replicated from the SDA . Connections both ways is successful
in "linked appliances" settings.
The license has been synced on both appliances.
DHCP options 66 and 67 on the RSA configured based on the settings we have on the SDA.
DHCP server for that subnet has Option 66 set to the ip of the RSA in that subnet, and option 67 is "undionly.kpxe" just
as we configured it on the SMA .....(I assure you I have not added the same IP address of the SMA to the RSA DHCP options).
All these settings on the SMA work perfectly.
BUT...
I still am not able to network boot clients into the RSA. Clients can't seem to find the KBE. .....(TFTP timeout as in screenshot)
Is there a way to test to see where the problem is. Whether its from the RSA or the DHCP server or anything else?
Help is greatly appreciated
Answers (2)
You can check in the logs of the RSA if the client at least tried to contact it.
Also verify the settings in the DHCP (especially if there are additional spaces where they should not) and the logs there.
If you are unsure, post the logs here or open a support ticket for help.
Based on that screenshot, your devices are unable to find a DHCP capable of handling their PXE boot request.
That means they are able to reach the RSA in the first place.
If they are able to do so, you should see their IP addresses in your RSA TFTP Log.
It looks like a DHCP issue here. Make sure the DHCP is properly configured, and is replicating fine.
Also if your option 67 is undionly.kpxe, that is for Legacy devices Only, newer devices are not capable of booting Legacy (only UEFI) out of the box, make sure the BIOS has Legacy OPTION ROM enabled (if available).
