we have PXE servers distributed globally as well, but without NAT beeing involved, as it all happens inside our corporate network.
I wonder what you mean with MAC not found ?
Have you set auto_discover_disabled to 1 in your pxe.conf ?
My location A and Location B are connected over public network across WAN, so Application server IP (which is in location A) is not reachable from the network where I am booting my target server, or you can say my DHCP server of location B.
So I believe target server MAC address is not forewarded to application server or DB, due to which my pxe.log saying Device 00-15-5d-41-04-07: not present in db. correct me if I am wrong here.
I have set auto_discover_disabled is 0.
below is architecture for reference. Please let me know in case I missed anything or I need to check any cofigurations.
Your clients will try to talk back to an application server on 9831 (SSL Port). If site B can not route to site A then you need to set your BMI call back address as the PXE server in Site B. The PXE server then needs to forward all 9831 traffic back to the application server in site A (to a job instance running 9831 of course) and you can use iptables for this.
The current error should be relative to your site B only. Try using broadcast in pxe.conf with the multicast Ip address as the PXE server IP.
I am bit confused here, does client (Target) server try to connect application server using port 9831 during initial boot ? as per my understanding initial boot instrauctions are send by PXE (broadcast / multicast).
I believe that BMI call back option is in system package. correct me if I am wrong here.
Is there any pxe configuration I am missing ??
I have configured iptable as below at PXE server (PXE server is what I am using as router) -
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward
/sbin/iptables -t nat -A POSTROUTING -o seth0 -j MASQUERADE
as per your suggestion I made changes in pxe.conf, restarted pxe and tftp service but no luck
below is client VM screen showing output on boot -
any document or reference would be very helpful.
no 9831 is after the PXE and TFTP process
I notice you have the DHCP option 211 to your appserver. Change that to your PXE server and retest. I assume you have populated your datastore on the PXE server with the boot image and OS media etc?
I have DHCP scop 211 option has value as PXE server IP. on PXE server I have populated gentoo boot image at /tftproot/X86PC/pxelinux/
yet not uploaded rest of OS in pxestore.
I am expecting atleast initial boot should be there using gentoo boot image.
Sorry for the delayed reply Omkar.
Your image above does not suggest the dhcp options were set for the PXE server. Have you had any progress with this case? The only further point I can suggest is ensuring that broadcasts are allowed to hit both your PXE and DHCP server. So for switched networks this means that IPhelper settings on the switch should be set for the DHCP and PXE server IP addresses.
i believe his problem is that this is a hyper-v guest and it's not clear if that supports a full pxe implementation. it dosn't seem to be getting the pxe response or know what to do w/ it.