cobbler的过程需要用到 cobbler服务器 dhcp服务器 需要用到http服务器 tftp服务器 客户端pc
其中几个关键部位cobbler和dhcp
cobbler可以通过rsync同步接管dhcp的配置 此时就需要清醒的认识到是否需要接管
cobbler的配置文件中关于 manage dhcp 0 1 0表示不接管 1 表示接管
不接管的话dhcp的服务器大多和cobbler服务器不是同一台 此时在配置dhcp的服务器的时候需要指定的next-server给cobbler服务器的IP地址贴个配置文件如下;
# ******************************************************************
# Cobbler managed dhcpd.conf file
# generated from cobbler dhcp.conf template (Wed Dec 5 02:42:02 2018)
# Do NOT make changes to /etc/dhcpd.conf. Instead, make your changes
# in /etc/cobbler/dhcp.template, as /etc/dhcpd.conf will be
# overwritten.
# ******************************************************************
ddns-update-style interim;
allow booting;
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
option pxe-system-type code 93 = unsigned integer 16;
subnet 192.168.3.0 netmask 255.255.255.0 {
option routers 192.168.3.2;
option domain-name-servers 192.168.3.2;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.3.100 192.168.3.254;
default-lease-time 21600;
max-lease-time 43200;
next-server 192.168.3.128; #该条需要指定cobbler服务器ip
host cobbler {
hardware ethernet 00:0c:29:fc:bb:d0; # host cobbler 该条指定某个pc的静态IP
fixed-address 192.168.3.128;
}
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
if option pxe-system-type = 00:02 {
filename "ia64/elilo.efi";
} else if option pxe-system-type = 00:06 {
filename "grub/grub-x86.efi";
} else if option pxe-system-type = 00:07 {
filename "grub/grub-x86_64.efi";
} else {
filename "pxelinux.0";
}
manage=1的时候 cobbler和dhcp服务大多基于一台服务器上,此时dhcp的配置基本可以省略,在安装完dhcp的服务后,进入cobbler的dhcp关联文件 /etc/cobbler/dhcpd.default 配置如上代码,
每次更改后需要同步 cobbler sync