We have been doing it with self booting knl nodes without issue, though we do
switch discovery. Nothing occurs to me off hand that would explain this
scenario. I'll think more on it, but I'm out of office. Just wanted to say
lenovo havd been doing knl deployments internally. Sshd in Genesis
xCAT team will take a look of this issue and give you feedback soon.
ThanksBest Regards--Wang Xiaopeng (王晓朋)IBM China System Technology LaboratoryTel: 86-10-82453455Email: w...@cn.ibm.comAddress: 28,ZhongGuanCun Software Park,No.8
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?
On 28/07/16 07:58, Berryhill, Jerome wrote:
> 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.
Can you ping the IP addres
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 o
Bringing this up again, now that I have upgraded to 2.12.1 on the MN.
We've hit this off and on ever since, but with 2.12 it seems to occur
whenever there's a removal from kvm_nodedata cache of a node def and try to
rpower on:
# rpower w30234 on
w30234: Error: internal error Only 1 ide controller
