我已经安装了一台新的Cobbler服务器,并将其configuration为DHCP / TFTP服务器。 我configuration了/etc/dhcp/dhcpd.conf,如下所示:
[root@centolel ~]# cat /etc/dhcp/dhcpd.conf ddns-update-style interim; allow booting; allow bootp; ignore client-updates; set vendorclass = option vendor-class-identifier; option boot-server code 66 = string; option option-66 code 66 = text; option pxe-system-type code 93 = unsigned integer 16; authorative; subnet 10.13.0.0 netmask 255.255.255.0 { option routers 10.13.0.138; option domain-name-servers 10.13.0.1; option subnet-mask 255.255.255.0; range dynamic-bootp 10.13.0.20 10.13.0.150; default-lease-time 3600; max-lease-time 3600; next-server 10.13.0.1; 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"; } } }
我创build了一个新的虚拟机,并将其configuration为从networking启动。
这个想法是,补鞋匠(dhcp)将提供一个IP地址给新创build的虚拟机,并将发行安装CentOS 6。
当我重新启动新创build的虚拟机时,我看到以下几行:
gPXE 0.9.7 -- Open Source Boot Firmware.... net0: 52:54:00:41:a7:91 on PCI00:03.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] Waiting for link-up on net0... ok DHCP (net0 52:54:00:41:a7:91)... ok net0: 10.13.0.19/255.255.255.0 gw 10.13.0.138 No filename or root path specified No more network devices Booting from Hard Disk... Boot failed: not a bootable disk . . .
正如你所看到的,它收到一个不包含在“dynamic-bootp”范围内的IP … 10.13.0.19,范围从10.13.0.20开始。
在重新启动虚拟机之后查看Cobbler服务器的/var/log/messages ,我看到:
Jun 29 18:52:07 localhost dhcpd: DHCPDISCOVER from 52:54:00:41:a7:91 via br0 Jun 29 18:52:08 localhost dhcpd: DHCPOFFER on 10.13.0.101 to 52:54:00:41:a7:91 via br0 Jun 29 18:52:08 localhost dhcpd: DHCPDISCOVER from 52:54:00:41:a7:91 via br0 Jun 29 18:52:08 localhost dhcpd: DHCPOFFER on 10.13.0.101 to 52:54:00:41:a7:91 via br0 Jun 29 18:52:10 localhost dhcpd: DHCPREQUEST for 10.13.0.19 (10.13.0.138) from 52:54:00:41:a7:91 via br0: unknown lease 10.13.0.19. Jun 29 18:52:13 localhost kernel: br0: port 2(vnet0) entering forwarding state
/var/lib/tftpboot :
[root@centolel ~]# ll /var/lib/tftpboot/ total 332 drwxr-xr-x 3 root root 4096 2015-06-29 18:38 boot drwxr-xr-x 2 root root 4096 2015-06-22 21:08 etc drwxr-xr-x 2 root root 4096 2015-06-29 18:38 grub drwxr-xr-x 4 root root 4096 2015-06-29 18:38 images drwxr-xr-x 2 root root 4096 2015-06-22 21:08 images2 -rw-r--r--. 2 root root 24988 2014-04-15 17:36 memdisk -rw-r--r-- 2 root root 54964 2015-06-14 14:25 menu.c32 drwxr-xr-x 2 root root 4096 2015-06-22 21:08 ppc -rw-r--r-- 2 root root 16794 2015-06-14 14:25 pxelinux.0 drwxr-xr-x 2 root root 4096 2015-06-29 18:43 pxelinux.cfg drwxr-xr-x 2 root root 4096 2015-06-29 18:38 s390x -rw-r--r-- 2 root root 198236 2015-06-14 14:25 yaboot
运行命令cobbler sync完成通知“任务完成!!”。
所以我想知道为什么服务器是专门请求这个地址,而不是范围的一部分,我也想知道为什么它不能find图像…任何想法?
您的networking中可能还有其他竞争的DHCP服务器。 使用Wireshark运行stream量捕获可以帮助您查明这个问题。
BTW
range dynamic-bootp 10.13.0.20 10.13.0.150; option routers 10.13.0.138;
路由器的IP在分配范围内; 不好。