Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Reference Manual, Page: 208 / 318

Chapter 11. Cobbler
196
•
httpd
— Will check to see if the HTTPD service is running.
•
iptables
— Will remind you that if you are running an IPTables firewall, that you have rules set to
allow ports 69 (TFTP), 80 (HTTPD), 25150 and 25151 (Cobbler).
Run the
cobbler check
command as root on your system to see what settings and services need to
be enabled to properly run Cobbler on your boot server.
Note
If you make any changes to the
/etc/cobbler/settings
file, you must run
service
cobblerd restart
and
cobbler sync
for the changes to take effect.
11.1.2. Configuring Cobbler with
/etc/cobbler/settings
Cobbler configuration is mainly done within the
/etc/cobbler/settings
file. The file contains
several configurable settings, and offers detailed explanations for each setting regarding how it affects
the functionality of Cobbler and whether it is recommended for users to change the setting for their
environment.
Most of the settings can be left default and Cobbler will run as intended. For more information about
configuring Cobbler settings, consult the
/etc/cobbler/settings
file, which documents each
setting in detail.
11.1.3. Cobbler and DHCP
Cobbler supports bare-metal kickstart installation of systems configured to perform network boots
using a PXE boot server. To properly implement a Cobbler installation server, administrators need to
either have administrative access to the network's DHCP server or implement DHCP on the Cobbler
server itself.
11.1.3.1. Configuring an Existing DHCP Server
If you have a DHCP server deployed on another system on the network, you will need administrative
access to the DHCP server in order to to edit the DHCP configuration file so that it points to the
Cobbler server and PXE boot image.
As root on the DHCP server, edit the /etc/dhcpd.conf file and append a new class with options for
performing PXE boot installation. For example:
allow booting;
allow bootp;
class "PXE" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 192.168.2.1;
filename "pxelinux.0";
}
Following each action step-by-step in the above example:
1. The administrator enables network booting with the
bootp
protocol.