Maybe someone that knows more about DHCP and network that can help me out with this one. I've been thrown for a look with this for awhile now, so I'm reaching out to the ServerFault community.
We migrated a server out of our production datacenter as we are repurposing the system. In our local lab, I PXE booted the server into our environment and it PXE booted fine and loaded the image just fine. However, after loading the image, it couldn't download the kickstart. I noticed from the DHCP logs, it was trying to get a new IP address and couldn't. What it seems to look like is, it PXE boots using a local PXE/DHCP server and then once it loads up and then tries to DHCP again, it reaches out to a random server outside our lab environment. Here are the DHCP logs:
dhcpd: DHCPDISCOVER from 00:11:22:33:44:55 via 10.6.246.1 dhcpd: DHCPOFFER on 10.6.246.9 to 00:11:22:33:44:55 via 10.6.246.1 dhcpd: DHCPREQUEST for 10.6.246.9 (10.6.247.236) from 00:11:22:33:44:55 via 10.6.246.1 dhcpd: DHCPACK on 10.6.246.9 to 00:11:22:33:44:55 via 10.6.246.1 xinetd: START: tftp pid=26359 from=10.6.246.9 in.tftpd: RRQ from 10.6.246.9 filename /pxelinux.0 in.tftpd: tftp: client does not accept options in.tftpd: RRQ from 10.6.246.9 filename /pxelinux.0 in.tftpd: RRQ from 10.6.246.9 filename /pxelinux.cfg/44454c4c-5800-104e-8057-b9c04f4b4e31 in.tftpd: RRQ from 10.6.246.9 filename /pxelinux.cfg/01-00-11-22-33-44-55 in.tftpd: RRQ from 10.6.246.9 filename //images/RHEL-6.4-x86_64/vmlinuz in.tftpd: RRQ from 10.6.246.9 filename //images/RHEL-6.4-x86_64/initrd.img dhcpd: DHCPDISCOVER from 00:11:22:33:44:55 via 10.6.246.1 dhcpd: DHCPOFFER on 10.6.246.9 to 00:11:22:33:44:55 via 10.6.246.1 dhcpd: DHCPREQUEST for 10.88.254.102 (10.88.254.22) from 00:11:22:33:44:55 via 10.6.246.1: ignored (not authoritative).
Things to note are:
00:11:22:33:44:55is the MAC address I am referring to
- In the DHCP server, the subnet
10.6.246.0is set as
- In the DHCP server, the option routers section is set to
10.6.246.1, which is the default gateway - which in our network, can get to anything on the network
Does this seem weird or is it just me? I feel like it's reaching out to something that it shouldn't be.
Also - that 10.88.254.102 and .22 servers - those are not pingable from anywhere, however, when I run an nmap on them they show a squid-http servers (which would be proxy servers), however, my network team tells mem those don't have an ARP entry so they are "down".
I'm at a loss here.