Yes, TFTP is very unreliable protocol, particularly if you put the service under load. I recommend to chainboot iPXE and boot systems via HTTP. This is undocumented, but you can google that out easily. This will scale fine, TFTP will be only used to download PXELinux config and iPXE (a megabyte), the rest will be HTTP.
Blogpost required if you find this working! LZ On Sun, Feb 12, 2017 at 4:11 PM, Marcus Torres <[email protected]> wrote: > Hi, > I have an environment where I'm rebooting multiple clients at the same time > to pxe boot. When I do so, only one client at a time is able to load the > foreman discovery image from my tftp server. One client will win the race and > the others will wait and eventually timeout. This even happens if I set my > 'wait' parameter to "no" in my tftp config file. Shouldn't I be able to pxe > boot more than one discovery image at a time ? My tftp server has a 10G link. > I don't seem to have an issue if I attempt to pxe boot multiple clients to > another pxe file for instance rhel 7.2 images. Has anyone run into this issue > ? > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
