You could set up your node object with the DNS name and IP address of the 100G interface, and just set the MAC to that of the 1Gb boot interface. Create a postscript that updates the interface config files (e.g. "ifcfg-p1p1" and "ifcfg-em1") so that traffic flows over the 100G interface when the node reboots into the OS. Set that postscript as the last one in the postscript list.
> On 04/12/2022 11:53 AM Hannum, Keith <keith.han...@lmco.com> wrote: > > > > We’ve done this in our environment. Use confignetwork to set up your 100G > NID first then, the key is to use setroute to add a route to continue to talk > to the xcat master over the original boot interface, otherwise, xcat gets > requests from an unknown node. > > > > -Keith > > ____________________ > > Keith Hannum > > keith.han...@lmco.com mailto:keith.han...@lmco.com > > > > From: Jeffrey R. Lang <jrl...@uwyo.edu> > Sent: Thursday, March 31, 2022 6:05 PM > To: xcat-user@lists.sourceforge.net > Subject: EXTERNAL: [xcat-user] Booting from one interface and then > switching to another interface > > > So I have a new machine that has 4 x 1g ports and a Mellanox HBA in 100G > Ethernet mode. I need to boot the node from the 1g interface (BIOS doesn’t > support booting from the Mellanox HBA) then switch over to using the 100G > after the node is booted. > > > I believe that I have seen this type of request in the past. Anyone out > their doing this that can provide some knowledge on how you were able to > accomplish this? > > > Thanks, > > Jeff > > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user >
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
