Check next_server in /etc/cobbler settings, restart xinetd, add -v (or
-vv or -vvv) to /etc/xinetd.d/tftp file, what is in
/var/lib/tftp/pxelinux.cfg? Is there a file with the mac address in this
dir? Check logging in /var/log/messages... All this should give you an
idea of what is going on.
If you are using a different subnet to the primary one in cobbler
settings, set the server override to be the ip of the interface for the
subnet (this propogates to the tftp next server and the server address
in the pxelinux cfg file; change the next_server setting in the dhcp
template to be $iface.next_server).
On 2014-07-31 20:17, Michael Tiernan wrote:
On 7/31/14 2:57 PM, Jörgen Maas wrote:
if you are using the python tftp server these system definitions don't
get generated iirc.
I'm sorry, maybe I'm dense. I'm obviously saying the wrong thing here
because the tftp server selection doesn't change this. (I've tested it
too.)
When the target system initiates the PXE boot process, after the
address
is assigned, the target system requests, via tftp protocol a file
which,
if the MAC address of the target matches, is sent back to the target to
then boot from.
It is *those* files and confgs that are not being created and prepared
for these target systems.
_______________________________________________
cobbler mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/cobbler
