No, bmcdiscovery is not mandatory for sequential discovery.
The correct procedure should be:
1. start sequential discovery first: nodediscoverstart
2. boot the node, then you could see the following messages
xcat.discovery.seqdiscovery
But in your case that there was no any discovery messages after starting 'nodediscoverstart', so you need check the status of the your nodes.
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
Manager for HPC SW Dev: xCAT, ESSL, SMI, Test
IBM China Systems Laboratory (CSL)
----- Original message -----
From: Nicolas Roosen <[email protected]>
To: <[email protected]>
Cc:
Subject: Re: [xcat-user] 回复： xcat.genesis.doxcat: Unrecognized directive (dest=)
Date: Wed, Jul 5, 2017 3:53 PM
Hi,
here are some logs.
So first we removed an unwanted server from the discovery process:
Jul 4 10:42:02 adm xcat[2941]: xcatd: Processing discovery request from
10.33.241.181
Jul 4 10:42:02 adm xcat[2941]: xcat.discovery.aaadiscovery:
(0c:c4:7a:70:e0:80) Got a discovery request, attempting to discover the
node...
Jul 4 10:42:02 adm xcat[2941]: xcat.discovery.blade:
(0c:c4:7a:70:e0:80) Warning: Could not find any nodes using blade-based
discovery
Jul 4 10:42:02 adm xcat[2941]: xcat.discovery.switch:
(0c:c4:7a:70:e0:80) Warning: Could not find any nodes using switch-based
discovery
Jul 4 10:42:02 adm xcat[2941]: xcat.discovery.mtms: (0c:c4:7a:70:e0:80)
Warning: Could not find any node for Supermicro:*A00AD6F3 using
mtms-based discovery
Jul 4 10:42:02 adm xcat[2941]: xcat.discovery.zzzdiscovery:
(0c:c4:7a:70:e0:80) Failed to discover the node.
Jul 4 10:43:49 adm xcat[2820]: xCAT: Allowing nodediscoverls for root
from localhost
Jul 4 10:44:25 adm xcat[2843]: xCAT: Allowing nodediscoverdef -h for
root from localhost
Jul 4 10:44:32 adm xcat[2852]: xCAT: Allowing nodediscoverdef -r -u
00000000-0000-0000-0000-0CC47A70E080 for root from localhost
Jul 4 10:44:35 adm xcat[2859]: xCAT: Allowing nodediscoverls for root
from localhost
Jul 4 10:44:39 adm xcat[2869]: xCAT: Allowing nodediscoverstatus for
root from localhost
Jul 4 10:45:25 adm xcat[2889]: xCAT: Allowing nodels for root from
localhost
The we tried to create a new one, but couldn't see any discovery process
information in the logs:
Jul 4 16:02:23 adm xcat[6639]: DEBUG xcatd: open new process : xcatd
SSL: mkdef for root@localhost
Jul 4 16:02:23 adm xcat[6639]: xCAT: Allowing mkdef -t node -o n043
groups=all,ipmi,node-giga arch=x86_64 mgt=ipmi bmc=172.30.192.57
mac=0c:c4:7a:71:f1:17 ip=172.30.240.57
chain=runcmd=bmcsetup,osimage=centos7.3-x86_64-node-giga
provmethod=centos7.3-node-giga for root from localhost
Jul 4 16:02:23 adm xcat[6640]: DEBUG xcatd: dispatch request 'mkdef -t
node -o n043 groups=all,ipmi,node-giga arch=x86_64 mgt=ipmi
bmc=172.30.192.57 mac=0c:c4:7a:71:f1:17 ip=172.30.240.57
chain=runcmd=bmcsetup,osimage=centos7.3-x86_64-node-giga
provmethod=centos7.3-node-giga' to plugin 'DBobjectdefs'
Jul 4 16:02:23 adm xcat[6640]: DEBUG xcatd: handle request 'mkdef' by
plugin 'DBobjectdefs''s process_request
Jul 4 16:02:23 adm xcat[6639]: DEBUG xcatd: close connection with
root@localhost
Jul 4 16:02:29 adm xcat[6660]: DEBUG xcatd: connection from root@localhost
Jul 4 16:02:29 adm xcat[6660]: DEBUG xcatd: open new process : xcatd
SSL: lsdef for root@localhost
Jul 4 16:02:29 adm xcat[6660]: xCAT: Allowing lsdef n043 for root from
localhost
Jul 4 16:02:29 adm xcat[6661]: DEBUG xcatd: dispatch request 'lsdef
n043' to plugin 'DBobjectdefs'
Jul 4 16:02:29 adm xcat[6661]: DEBUG xcatd: handle request 'lsdef' by
plugin 'DBobjectdefs''s process_request
Jul 4 16:02:29 adm xcat[6660]: DEBUG xcatd: close connection with
root@localhost
Jul 4 16:02:58 adm xcat[6680]: DEBUG xcatd: connection from root@localhost
Jul 4 16:02:58 adm xcat[6680]: DEBUG xcatd: open new process : xcatd
SSL: nodediscoverstart for root@localhost
Jul 4 16:02:58 adm xcat[6681]: DEBUG xcatd: dispatch request
'nodediscoverstart noderange=n043' to plugin 'seqdiscovery'
Jul 4 16:02:58 adm xcat[6681]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'seqdiscovery''s process_request
Jul 4 16:02:58 adm xcat[6680]: xCAT: Allowing nodediscoverstart
noderange=n043 for root from localhost
Jul 4 16:02:58 adm xcat[6682]: DEBUG xcatd: dispatch request
'nodediscoverstart noderange=n043' to plugin 'profilednodes'
Jul 4 16:02:58 adm xcat[6682]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'profilednodes''s process_request
Jul 4 16:02:58 adm xcat[6680]: DEBUG xcatd: close connection with
root@localhost
Jul 4 16:03:01 adm xcat[6688]: DEBUG xcatd: connection from root@localhost
Jul 4 16:03:01 adm xcat[6688]: DEBUG xcatd: open new process : xcatd
SSL: lsdef for root@localhost
Jul 4 16:03:01 adm xcat[6688]: xCAT: Allowing lsdef n043 for root from
localhost
Jul 4 16:03:01 adm xcat[6689]: DEBUG xcatd: dispatch request 'lsdef
n043' to plugin 'DBobjectdefs'
Jul 4 16:03:01 adm xcat[6689]: DEBUG xcatd: handle request 'lsdef' by
plugin 'DBobjectdefs''s process_request
Jul 4 16:03:01 adm xcat[6688]: DEBUG xcatd: close connection with
root@localhost
I might miss something, but can't find out what.
Is the "bmcdiscover" absolutely mandatory in a sequential discovery process?
Thanks.
Nicolas
On 07/05/2017 03:23 AM, Xiao Peng Wang wrote:
> Please show out the logs in MN during the discovery happens.
>
> Using IBM Verse, send from my iPhone.
>
> ------------------------------------------------------------------------
> 在 2017年7月5日，上午12:37:37，[email protected] 写道：
>
> From: [email protected]
> To: [email protected]
> Cc:
> Date: 2017年7月5日 上午12:37:37
> Subject: [xcat-user] xcat.genesis.doxcat: Unrecognized directive (dest=)
>
> Hello,
[...]
--
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
------------------------------------------------------------------------------ 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
