07-14-2005 03:17 PM - edited 03-03-2019 10:02 AM
I have a local IOS DHCP server with PXE clients and a remote PXE server. The DHCP server responds with an IP address and a next server IP address of the remote PXE server in the DHCPOFFER. The client never sends a request to the PXE server to obtain the bootfile. I have tried configuring the IP helper address for the PXE server as well as using the next-server DHCP configuration without luck. Since the PXE server can not listen to the DHCP request (since they are on different subnets) then I need a way to force the client to query the PXE server for a bootfile. Has anyone successfully created a PXE and DHCP server setup when the machines are on different subnets?
Thanks,
RJ
07-14-2005 03:37 PM
Usually Next-servers are TFTP servers, i dont know if your client uses TFTP for booting or some other protocol. Put a sniffer (ethereal) on the segment and look at what udp ports (traffic) passes through that segment. YOu can forward extra UDP ports on the router using ip forward-protocol udp
http://www.answers.com/topic/preboot-execution-environment
07-14-2005 05:09 PM
Thanks for the reply. Our PXE clients use TFTP to download a bootfile and it is able to start the download but gets an error before finishing it.
Thanks,
RJ
07-14-2005 05:14 PM
Can you paste what error you get ?
07-14-2005 08:04 PM
Error PXE-E76: Bad or missing multicast discovery address.
Description - Multicast discovery is enabled but the multicast discovery address tag is missing.
I have other PXE clients on the same LAN as the PXE server but in different (adjacent) VLANs. The Layer 3 Vlan interface has the ip helper-address of the PXE server and also the ip helper-address of a DHCP server on the same subnet as the PXE server. This setup works fine so I know it is not a problem with the bootfile. It is related to the setup of the PXE and DHCP servers on different subnets.
Thanks,
RJ
07-14-2005 08:14 PM
I think your PXE clients are using MTFTP which uses Multicast. Again this traffic wont be forward using helper-address as its not a broadcast. ITs a multicast. YOu will need to enable multicast forwarding on your router to forward this multicast TFTP traffic to the PXE server which holds the bootfile. It works in the adjacent vlan, as the clients are on the same LAN as the PXE server. Can you put a sniffer such as ethereal and filter multicast packets and see what Multicast packet on port 69 is used (TFTP). THen you can enable PIM routing to forward multicast traffic from this vlan to the PXE server vlan.
Here is a guide to multicast routing.
Here is a link to ethereal - download.
http://www.ethereal.com/download.html
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide