<div dir="ltr"><div><div><div><div>We currently use cobbler 2.7 with "manage_dhcp=1" on Redhat to install clients with a static IP address i.e.<br><br> # cobbler system add --name=scratch2 --profile=rhel6 --mac=00:50:56:b2:53:36 --ip-address=10.10.3.27 --netmask=255.255.255.0 \<br>
--gateway=10.10.3.1 --static=1 --dns-name=<a href="http://scratch2.example.com">scratch2.example.com</a> --hostname=scratch2 --interface=eth0<br><br></div>The target system boots and the installation proceeds automatically with no use intervention required. Good.<br>
<br></div>Is is possible to configure cobbler so that it also adds the system "scratch2" to /var/lib/tftpboot/pxelinux.cfg/default file? This would allow me to configure a dhcpd server in a remote subnet that just assigns a dhcp address and sets "next-server cobbler-central-ip" . On boot, the client console would then present a pxe menu from the "default" file that includes all the cobbler dhcp profiles, but also a new menu item for each static-ip system. I'd then scroll through the pxe menu and select "scratch2", and it would then be assigned the desired static IP address and hostname.<br>
<br></div>I suspect I'm missing something in the docs, since this seems a common use case.<br><br></div>Cheers,<br><br>Paul<br></div>