I will confess I have not used it so I have not much to say about the
traditional xCAT sequential discovery beyond:
https://xcat-docs.readthedocs.io/en/stable/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.html
For reference, in confluent things are evolving a bit, e.g.:
# nodediscover list -t pxe-client -o node -f node,mac,switch,port|head
Node| Mac| Switch| Port
-----|------------------|---------------|----------------
| 40:f2:e9:c5:d8:8a| switch8| Port-Channel105
n166| 08:94:ef:1e:5c:6f| 172.16.2.10| Ethernet19
n167| 08:94:ef:1e:5e:2f| 172.16.2.10| Ethernet20
n168| 7c:d3:0a:e3:21:c8| 172.16.2.74| Ethernet31
n169| 7c:d3:0a:e2:bf:00| 172.16.2.74| Ethernet32
n178| 08:94:ef:1e:5d:9f| switch8| Port-Channel105
n179| 08:94:ef:1e:5d:27| switch8| Port-Channel105
n521| 08:94:ef:4f:5d:50| 172.16.2.67| Ethernet1/23
The above shows me that my cluster currently has exactly one unknown node that
has tried to pxe boot. I could skip ahead to a mac.csv:
# nodediscover list -t pxe-client -o node -f node,mac -c |head
Node,Mac
,40:f2:e9:c5:d8:8a
Then fill in node names. You can also do: ‘nodegroupattrib everything
discovery.policy=permissive,pxe net.compute.bootable=1’ which when in effect
will enable the following:
[jjohnson2@leonidas ~]$ confluent2xcat d3 -o nodes.def
[jjohnson2@leonidas ~]$ cat nodes.def
d3:
objtype=node
arch=x86_64
netboot=xnba
mgt=ipmi
bmc=fe80::a94:efff:fe3f:e0af%eth1
mac=08:94:ef:3f:e1:32
slotid=3
groups=dense,compute,everything
mpa=smm1
Additionally, for Lenovo equipment it can actually do discovery and bmcsetup
while the server is off:
$ nodediscover list -t lenovo-xcc -o node -f node,model,serial,mac
Node| Model| Serial| Mac
------|-----------|---------|------------------
| 7X2106Z009| DVJJ1086| 08:94:ef:2f:2e:9d
| 7X02CTO1WW| J30008VD| 7c:d3:0a:d8:35:25
d2| 7X21CTO1WW| J1001PNG| 08:94:ef:50:9b:3b
d3| 7X2104Z000| DVJJ1042| 08:94:ef:3f:e0:af
d4| 7X2104Z000| DVJJ1022| 08:94:ef:41:01:b5
d5| 7X21CTO1WW| J1001PNF| 08:94:ef:50:b7:5d
d6| 7X21CTO1WW| J1001PNE| 08:94:ef:50:1c:6b
d7| 7X2104Z023| 00000864| 08:94:ef:2f:2b:c7
d8| 7X2104Z000| DVJJ1003| 08:94:ef:40:89:31
r8u32| 7X07CTO1WW| J30002HG| 08:94:ef:3c:81:83
r8u33| 7X98RCZ000| DVJBJ286| 08:94:ef:4f:55:bd
[jjohnson2@leonidas ~]$ nodedefine d1; nodediscover assign -s DVJJ1086 -n d1
d1: created
Assigned: d1
[jjohnson2@leonidas ~]$ nodepower d1
d1: off
And then could either proceed to gather pxe-client as above or just ask for the
mac addresses:
$ nodeinventory d3 mac
d3: Intel X722 LOM MAC Address 1: 08:94:ef:3f:e1:32
d3: Intel X722 LOM MAC Address 2: 08:94:ef:3f:e1:33
d3: Mellanox ConnectX-5 2x100GbE / EDR IB QSFP28 VPI Adapter MAC Address 1:
50:6b:4b:09:2a:5c
d3: Mellanox ConnectX-5 2x100GbE / EDR IB QSFP28 VPI Adapter MAC Address 2:
50:6b:4b:09:2a:5d
From: Jacob Bonek <[email protected]>
Sent: Wednesday, August 14, 2019 2:44 PM
To: xCAT Users Mailing list <[email protected]>
Subject: [External] Re: [xcat-user] Sequential Discovery
I would just like to second this. I’ve tried getting this to work in the past
but with not a lot of luck.
From: Sam Davis <[email protected]<mailto:[email protected]>>
Sent: Thursday, August 8, 2019 9:59 AM
To: xCAT Users Mailing list
<[email protected]<mailto:[email protected]>>
Subject: [xcat-user] Sequential Discovery
CAUTION: External Email
Hello,
In the past, I've always had issues getting sequential discovery to work.
I'm about to add 15 more nodes to our cluster and would prefer not to have to
add them all manually. I normally fumble about with sequential for a while each
time I add nodes before giving up. Does anyone happen to have a procedure they
would be willing to share with me on how to properly perform sequential
discovery?
Thanks,
Sam
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
