Hello,

last week I was able to discover sequentially 4 nodes.

Today I try to discover a new one, using the same set of commands.

But then I get this on the console:

Jul 4 18:17:10 10.33.241.3 (none) rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="2361" x-info="http://www.rsyslog.com";] start Jul 4 18:17:10 10.33.241.3 (none) xcat.genesis.doxcat: Getting initial certificate --> 10.33.240.1:3001 Jul 4 18:17:30 10.33.241.3 (none) xcat.genesis.doxcat: Running getdestiny --> 10.33.240.1:3001
Jul  4 18:17:50 10.33.241.3 (none)  xcat.genesis.doxcat: Received destiny=
Jul 4 18:17:50 10.33.241.3 (none) xcat.genesis.doxcat: The destiny=, destiny parameters= Jul 4 18:17:50 10.33.241.3 (none) xcat.genesis.doxcat: Unrecognized directive (dest=) Jul 4 18:17:54 10.33.241.3 (none) xcat.genesis.doxcat: ... Will retry xCAT in 90 seconds Jul 4 18:18:04 10.33.241.3 (none) xcat.genesis.doxcat: ... Will retry xCAT in 80 seconds Jul 4 18:18:14 10.33.241.3 (none) xcat.genesis.doxcat: ... Will retry xCAT in 70 seconds Jul 4 18:18:24 10.33.241.3 (none) xcat.genesis.doxcat: ... Will retry xCAT in 60 seconds

I tried different settings, but cannot find out why the node doesn't get a discover destiny parameter?


Here is what I've done:

* mkdef -t node -o n043 groups="all,ipmi,node-giga" arch=x86_64 mgt=ipmi bmc=10.33.192.57 mac=0c:c4:7a:71:f1:17 ip=10.33.240.57 chain="runcmd=bmcsetup,osimage=centos7.3-x86_64-node-giga" provmethod=centos7.3-node-giga

* nodediscoverstart noderange=n043

Then booted the node via IPMI ...


Any thoughts?
Thanks.

--
Nicolas

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to