PVS created a new PVS site and updated option 66 and 67 in the DHCP servers, but Targets failed to connect to the PVS servers in the new PVS site during boot, and it continued to use the PVS servers in old PVS Site. 

 

• Configure the DHCP Relay configuration in Gateway to use the correct DHCP servers. 
• For eg: Cisco Routers you can configure DHCP Relay using: DHCP - Configuring the Cisco IOS DHCP Relay Agent  [Support] - Cisco Systems 

Problem Cause

• PVS Servers and the PVS targets were in different Subnets. 
• Gateway of Target network had PVS servers from old PVS site as part of DHCP Relay configuration, and PVS servers had PXE service running on the host, due to this configuration PVS servers in the old PVS site responded to Target DHCP requests with DHCP Offers with "Next Server IP address" value set to its own IP address. 
• In such configuration Target will get DHCP offers from all the servers running DHCP service or PXE service, and configured as part of DHCP Relay configuration.
• The target can attempt to boot from any of the PXE servers it got as the boot server in DHCP offers.