Description
LANDESK provides the ability to put one PXE Rep on each subnet so that settings on the network never have to be configured.
While not having to change any the configuration on any network device is a good feature, it may be beneficial and easier in certain environments to make network changes. For example, an environment that has 5 sites with 20 subnets each, would require 100 PXE Reps to avoid network configuration. However, with network configuration, they would only have to manage 5 PXE Representatives. Such a design would likely be preferred and LANDESK supports this design.
A PXE Representative can be used for multiple subnets similar to how any DHCP/Bootp server can be used for multiple subnets. This requires that a DHCP Relay agent exist that can forward DHCP/Bootp requests.
Diagram
The following diagram shows how subnets do not have a PXE Representative. Instead a DHCP Relay agent (often called an IP Helper with Cisco switches) exists on the network and must be configured to forward traffic to both the DHCP server and the PXE Representative, which can be on any other subnet.
Troubleshooting
Troubleshooting the PXE Representative is as simple as using Wireshark to verify that the PXE Rep received the DHCP/Bootp packets and responded.
Add the following filter to limit Wireshark traffic to bootp protocol on port 4011:
bootp || udp.port == 4011
Also, for TFPT, Wireshark can demonstrate the packet arriving and the response.