Hi Susendra, Can you please provide the mtcAgent.log file for this failure case. Is your controller-1 server BMC provisioned and using Redfish ? Eric. From: Selvaraj, Susendra <susendra.selvaraj@intel.com> Sent: Wednesday, November 4, 2020 10:53 AM To: starlingx-discuss@lists.starlingx.io Cc: An, Ran1 <ran1.an@intel.com>; Kumar, Sharath <sharath.kumar@intel.com>; John, Jaiber J <jaiber.j.john@intel.com>; Sun, Austin <austin.sun@intel.com> Subject: [Starlingx-discuss] Bare metal AIO Duplex Installation - PXE Boot Issue with Controller-1 [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, Install guide: https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/aio_du... Image deployed on Controller-0: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/latest_release/cen... Network setup with 3 segments for OAM, MGMT & DATA0/1 is done as per attached Network Diagram. On Controller-0, installation, boot strapping, configuration & unlock is successful. On Controller-1, facing issue with PXE boot. Below is the summary - * Controller-0 can identify Controller-1 in 'system host-list' * 169.254.202.1 is PXE boot interface on Controller-0 * dnsmasq is the PXE boot service running on Controller-0 * Physical network connectivity is appropriate between the Controllers * But still Controller-1 couldn't boot with PXE interface. Any other HW issue? Attached the build information of Controller-0 & dnsmasq daemon logs. Please provide inputs to fix the PXE boot issue on Controller-1. Regards, Susendra.