Can confirm success, thanks Jarrod! For anyone else reading this, the file did not exist so I created it with just the [netboot] stanza, Node instantly got a pxe answer on the deployment interface.
Sincerely, Brian Joiner On Thu, Jul 24, 2025 at 8:49 AM Jarrod Johnson via xCAT-user < [email protected]> wrote: > Indeed, split by commas. > ------------------------------ > *From:* Christian Caruthers via xCAT-user <[email protected] > > > *Sent:* Thursday, July 24, 2025 9:45 AM > *To:* xCAT Users Mailing list <[email protected]> > *Cc:* Christian Caruthers <[email protected]> > *Subject:* Re: [xcat-user] [External] Re: Confluent server TFTP interface > bind > > > For multiple NICs, would this be comma-separated? > > > > Regards, > > Christian Caruthers > > Lenovo Professional Services > > Mobile: +1 757-289-9872 > > > > *From:* Jarrod Johnson via xCAT-user <[email protected]> > *Sent:* Thursday, July 24, 2025 9:40 AM > *To:* Ryan Novosielski <[email protected]> > *Cc:* Jarrod Johnson <[email protected]>; > [email protected] > *Subject:* Re: [xcat-user] [External] Re: Confluent server TFTP interface > bind > > > > 3.13 > ------------------------------ > > *From:* Ryan Novosielski <[email protected]> > *Sent:* Thursday, July 24, 2025 8:56 AM > *To:* Jarrod Johnson <[email protected]> > *Cc:* [email protected] <[email protected]> > *Subject:* Re: [External] Re: [xcat-user] Confluent server TFTP interface > bind > > > > Thanks, Jarrod! > > > > Do you know in what version that was added? > > > > Sent from my iPhone > > > > On Jul 24, 2025, at 08:44, Jarrod Johnson <[email protected]> wrote: > > > > Another example of how we've been derlict in documentation... There is > now a way to indicate nics to ignore for netboot purposes, in a little > known file called service.cfg: > > # cat /etc/confluent/service.cfg > #[http] > #bindhost = /var/run/confluent/httpapi > > [netboot] > ignorenics=enp65s0f1np1 > > > ------------------------------ > > *From:* Ryan Novosielski via xCAT-user <[email protected]> > *Sent:* Thursday, July 24, 2025 1:30 AM > *To:* [email protected] <[email protected]> > *Cc:* Ryan Novosielski <[email protected]>; > [email protected] <[email protected]> > *Subject:* [External] Re: [xcat-user] Confluent server TFTP interface bind > > > > I most recently did this with a firewall rule, but agreed, it would be > good if there were a better way. And maybe there now is. There was not in > the version I was running at the time. > > > > Sent from my iPhone > > > > On Jul 23, 2025, at 22:12, Brian Joiner <[email protected]> wrote: > > > > In xCAT it was very easy to set the tftp/dhcp listening interface in the > main config file, so that nodes would get a pxe response from the desired > interface and not conflict with any other dhcp servers. > > > > My Confluent server is configured to start TFTP but nodes are not getting > a pxe response from the non-routable deployment network. Instead they are > getting responses from the enterprise network. How can I force tftp/dhcp > to use a particular interface on the head node? > > > > deployment: 10.13.13.0/24 > > Enterprise (really home): 192.168.0.0/24 > > DHCP and DNS handled by FreeIPA server > > > > > > Thanks, > > Brian Joiner > > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user > > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user >
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
