我正在通过Zero Touch Provisioning配置 Juniper Networks 交换机。在 CentOS 7 上,journal/log/(systemd 不管它是什么) 包含以下内容:
Nov 28 10:08:46 server dhcpd[8800]: Checking if packet is permitted.
Nov 28 10:08:46 server dhcpd[8800]: Permit list: unknown clients
Nov 28 10:08:46 server dhcpd[8800]: OK
Nov 28 10:08:46 server dhcpd[8800]: Checking if packet is permitted.
Nov 28 10:08:46 server dhcpd[8800]: Permit list: unknown clients
Nov 28 10:08:46 server dhcpd[8800]: OK
Nov 28 10:08:46 server dhcpd[8800]: matched a Juniper Networks QFX-5100
Nov 28 10:08:46 server dhcpd[8800]: DHCPDISCOVER from 08:b2:58:ab:dc:00 via eth2
Nov 28 10:08:47 server dhcpd[8800]: DHCPOFFER on 192.168.0.100 to 08:b2:58:ab:dc:00 (TR0217010017) via eth2
Nov 28 10:08:47 server dhcpd[8800]: Checking if packet is permitted.
Nov 28 10:08:47 server dhcpd[8800]: Permit list: unknown clients
Nov 28 10:08:47 server dhcpd[8800]: OK
Nov 28 10:08:47 server dhcpd[8800]: Checking if packet is permitted.
Nov 28 10:08:47 server dhcpd[8800]: Permit list: unknown clients
Nov 28 10:08:47 server dhcpd[8800]: OK
Nov 28 10:08:47 server dhcpd[8800]: matched a Juniper Networks QFX-5100
Nov 28 10:08:47 server dhcpd[8800]: DHCPREQUEST for 192.168.0.100 (192.168.0.250) from 08:b2:58:ab:dc:00 (TR0217010017) via eth2
Nov 28 10:08:47 server dhcpd[8800]: DHCPACK on 192.168.0.100 to 08:b2:58:ab:dc:00 (TR0217010017) via eth2
服务器是从“未知”池中提供的。以下是配置的相关部分:
# Global options
max-lease-time 1800;
default-lease-time 1800;
dynamic-bootp-lease-length 120;
ddns-update-style none;
# TFTP Server IP and file
next-server 192.168.0.250; # Assumed to be the DHCP server
filename "pxelinux.0";
# Define the pxe grub filename option
option zone-pxegrub-filename code 150 = text;
option zone-pxegrub-filename "/opt/tftp_files/boot/pxelinux.0";
# Options for Juniper switch to download FW and configuration from this server
# as described here: https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/software-image-and-configuration-automatic-provisioning-confguring.html
option space NEW_OP;
option NEW_OP.config-file-name code 1 = text;
option NEW_OP.image-file-name code 0 = text;
option NEW_OP.image-file-type code 2 = text;
option NEW_OP.transfer-mode code 3 = text;
option NEW_OP.alt-image-file-name code 4 = text;
option NEW_OP-encapsulation code 43 = encapsulate NEW_OP;
option option-150 code 150 = ip-address;
# bringing in the vendor specific options
vendor-option-space NEW_OP;
option NEW_OP.image-file-name "/juniper/fw/jinstall-host-qfx-5-17.2R1.13-signed.tgz";
option NEW_OP.config-file-name "/juniper/cfg/qfx-5100.cfg";
option NEW_OP.alt-image-file-name "/juniper/fw/jinstall-host-qfx-5-17.2R1.13-signed.tgz";
option NEW_OP.image-file-type "filename";
option NEW_OP.transfer-mode "tftp";
option option-150 192.168.0.250;
class "workers" {
match if substring(hardware, 1, 3) = 00:20:0c or substring(hardware, 1, 3) = 00:18:7D;
log(info, "matched a worker bee");
}
class "monitor" {
match if substring(hardware, 1, 3) = 00:d0:24;
log(info, "matched to a monitor");
}
class "JuniperSwitch" {
match if option vendor-class-identifier ~~ "^juniper-qfx5100.+$";
log(info, "matched a Juniper Networks QFX-5100");
}
subnet 192.168.0.0 netmask 255.255.255.0 {
#authoritative;
option routers 192.168.0.250;
pool {
allow members of "workers";
range 192.168.0.1 192.168.0.99;
log(info, concat("Issuing DHCP address to worker bootp requestor: ", binary-to-ascii(16, 8, ":", substring(hardware, 1, 6))));
}
pool {
allow members of "monitor";
range 192.168.0.245;
log(info, concat("Issuing DHCP address to monitor bootp requestor: ", binary-to-ascii(16, 8, ":", substring(hardware, 1, 6))));
}
pool {
allow members of "JuniperSwitch";
allow dynamic bootp clients;
range 192.168.0.201;
}
pool {
allow unknown-clients;
range 192.168.0.100 192.168.0.150;
}
}
请帮助我理解为什么这没有给出我期望的地址。
假设它是唯一一个通过 DHCP 请求 IP 地址的交换机,我怀疑这是一个旧的/已知的 ISC DHCP 错误/“功能”:
已经给出的动态租约优先于其他一些新配置,尤其是当它们在同一个网络中时。
可以这么说,在您配置特定情况之前,交换机从通用/“未知”池中获得了一个地址,并且 DHCP 守护程序优先考虑该地址。
要么删除 DHCP 租约文件 var/lib/dhcp/dhcpd.leases ,要么停止 DHCP 服务并从租约文件中编辑出给相关交换机 MAC 的所有 IP 地址租约。这样,它将获得预期的新地址。