Additionally, Lenovo did some work that might help on the KNL discovery in 
general.  I don't have a good memory of what we did off hand, but our 
self-booting KNL nodes are fine with current xCAT release for discovery and all.

From: Xiao Peng Wang [mailto:[email protected]]
Sent: Thursday, July 28, 2016 10:01 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [xcat-user] xCAT and Knights Landing Xeon Phi

Your xCAT is too old, could you try to update your xCAT to 2.12.1? In the 
2.12.1, xCAT shipped a new command 'xcatprobe discovery' which an be used to 
monitoring the discovery process.

Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: [email protected]<mailto:[email protected]>
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian 
District Beijing P.R.China 100193


----- Original message -----
From: "Berryhill, Jerome" 
<[email protected]<mailto:[email protected]>>
To: xCAT Users Mailing list 
<[email protected]<mailto:[email protected]>>
Cc:
Subject: Re: [xcat-user] xCAT and Knights Landing Xeon Phi
Date: Fri, Jul 29, 2016 4:40 AM


1 – We are using the bootable KNL processor.

2 – We used xCAT to run the nodediscover process. Normally, after discovery has 
occurred, the Genesis program will display a prompt on the node console saying 
‘xCAT Genesis running on <hostname>”. That did not happen. Instead, the process 
apparently timed out on the KNL, and restarted. This repeats indefinitely.

Q – Is there a way to get a log from the nodediscover program?



3 - Since the MAC address was updated in the xCAT data base, I tried doing a 
nodeset and reboot. The node does not respond to rpower. I rebooted manually, 
and it began loading an OS. I believe it is the OS I chose in nodeset, which is 
working an RHEL 7.2 that works fine on other machines. But I can’t be sure, 
because it is hung in the startup process.



4 – [root@sfs-head ~]# lsxcatd -a

Version 2.9.1 (git commit 7f6043fffd62d482931b17b60f9488eb5754fdc1, built Thu 
Mar 19 03:25:35 EDT 2015)

This is a Management Node

dbengine=SQLite











From: Xiao Peng Wang [mailto:[email protected]]
Sent: Wednesday, July 27, 2016 5:09 PM
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [xcat-user] xCAT and Knights Landing Xeon Phi



xCAT team does not have experience to handle the 'Knight Landing' processor. 
Base on your description, looks like you were using the server which installed 
the bootable 'Knight Landing' processor, am I right?



Did you try to use xCAT to do a general OS installation for the 'Knight 
Landing' server?



For your scenario, since the mac has been collected, could you run the 
'nodeset' against the node and perform an OS deployment to see what will happen.



Please run 'lsxcatd -a' to show your xCAT version.



Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: [email protected]<mailto:[email protected]>
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian 
District Beijing P.R.China 100193





----- Original message -----
From: "Berryhill, Jerome" 
<[email protected]<mailto:[email protected]>>
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Cc:
Subject: [xcat-user] xCAT and Knights Landing Xeon Phi
Date: Thu, Jul 28, 2016 5:59 AM


I am trying to use xCAT to manage some Knights Landing Xeon Phis (KNL).



I am currently trying to use node discovery to configure one of them. After 
enabling legacy PXE, I reboot and it displays



Intel Boot Agent GE v1.5.78



When it displays “beginning discovery process”, I run nodediscoverstart on our 
xCAT server.



After a while, the correct MAC address is inserted in the xCAT database for the 
node. But the node never displays the usual message, “xCAT Genesis running on 
f078”. Instead, it loops and restarts the discovery process.



I am wondering if this process is supported on KNL.



   Jerome



------------------------------------------------------------------------------

_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user




------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user


------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to