The following lists each of the requisite rules with their associated service.In the past I've setup a PXE server several times by making the normal dhcp server return everything needed for network booting: both the regular ip config AND bootinfo in a single dhcp setup. According to the documentation i've read it (wikipedia has a nice summary) should be possible to have an unmodified dhcp server (for example if the admin at your location denies access) and a separate server that ONLY returns the boot information.The management node is on subnet 10.10.3.64/26, on VLAN n° 1301.The compute nodes' have to be provisionned with ip adresses in that subnet too. I have created a system object representing the node I want to provision.
If you have an existing firewall ruleset using IPTables, you need to add the following rules to open the requisite Cobbler-related ports.The easiest way to have cobbler installed is to add the Installed: cobbler.noarch 0:1.4.1-1.el5 Dependency Installed: apr.x86_64 0:1.2.7-11 apr-util.x86_64 0:1.2.7-7.el5 createrepo.noarch 0:0.4.11-3.el5 httpd.x86_64 0:2.2.3-11.el5_2.centos.4 mkisofs.x86_64 9:2.01-10 mod_python.x86_64 0:3.2.8-3.1 postgresql-libs.x86_64 0:8.1.11-1.el5_1.1 python-cheetah.x86_64 0:2.0.1-1.el5 python-devel.x86_64 0:2.4.3-21.el5 tftp-server.x86_64 0:0.42-3.1.el5.centos xinetd.x86_64 2:2.3.14-10.el5 Complete!Directories that are important are: ' field in /etc/cobbler/settings must be set to something other than localhost, or kickstarting features will not work.So before having it work, we have to disable the internal dhcp of vmware on the vmnet8 interface.More details can be found here Don't forget to top vmware first (/etc/init.d/vmware sto)!!!!!!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.