On 10/23/24 5:18 PM, Jarrod Johnson via xCAT-user wrote:
So, for now, I'll put aside all the BMC discovery and just consider the
xCAT-style PXE based discovery, to have a common reference point. Same
capabilities, same limitations.
When PXE goes, the dynamic range is not needed because the following packet is
emitted by a node doing PXE boot:
Hello, thanks for this explanation. This is a pretty nice feature (I did
not understand at first because I was missing the concept that conflent
kink act as a "clever" dhcp server for that matter)
The 'can do it off' relies on the BMC first approach, in which all the
multicast IPv6/IPv4 trickery potentially involving IPv6 link local addresses to
overcome messed up IPv4 comes in, and requires a supported BMC with either
preconfigured user/password or firmware default user/password to be vaguely
alive on a connected network.
Still I don't understand how conceptually this approach works : what's
the purpose : to extract node mac address from the BMC ? If so, how do
you know this BMC is for this node on this switch/port without powering
the node on ?
In any case, confluent indeed seem to be a superset of xCAT for this
kind of use cases
Thanks for your help
--
Thomas HUMMEL
HPC Group
Institut PASTEUR
Paris, FRANCE
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
