On 2/13/19 3:33 PM, Thomas HUMMEL wrote:
I'm using the ip and nicips.eth0 and nicips.eth2 attributes on the
node to configure the correct IP addresses that I want. Also, be sure
to use nicextraparams.eth2=MTU=9000 if you want Jumbo frames on your
10 GB network.
Ok, I'll check that out.
I've just read the man.
Your idea is interesting indeed, even in the case you wouldn't mind
mixing administrative and workload data in the 10Gb/s connection as it
would remove the fear of PXE on the "wrong" nic.
The only thing is that we use a formula in the hosts table for the
primary ip (actually the only ip we have for one node, BMC ip aside of
course) so it's derived from the node number/name. Would nicpips
attribute support the formula ?
Finally, I'm using the nichostnamesuffixes attribute so the nodes have
different, but predictable, names on the 1 Gb network and the 10 Gb
network.
So you've got 2 names in DNS after makedns I guess ?
But how does it translate in sysconfig scripts/files (or the equivalent
is non centos/redhat OS) on the node ? What does 'hostname' returns if
run on the node ?
Thanks.
--
Thomas H.
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
