@lists.sourceforge.net
Date: 01/22/2014 02:58 AM
Subject:Re: [xcat-user] Frustrating time with sequential node discovery
Why do you say that you need nbk.x86_64? Is this file listed in the
/tftpboot/xcat/xnba/nets/?
With the latest xCAT build, it needs /tftpboot/xcat/genesis.kernel.x86_64
instead
: Xiao Peng Wang w...@cn.ibm.com
To: xCAT Users Mailing list xcat-user@lists.sourceforge.net,
Cc: xCAT Users Mailing list xcat-user@lists.sourceforge.net
Date: 01/22/2014 02:58 AM
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
Why do you say that you
@lists.sourceforge.net
mailto:xcat-user@lists.sourceforge.net
Date: 01/22/2014 02:58 AM
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
Why do you say that you need nbk.x86_64? Is this file listed
/22/2014 08:11 AM
Subject:Re: [xcat-user] Frustrating time with sequential node discovery
I've been lurking on this discussion, and just checked to see what we've
got -- nbroot or genesis -- and we have both of them.
I had given up on node discovery years ago, we originally used the switch
I can answer that point from a personal viewpoint - it's just a pain. A
real bad pain, especially when you do not have homogenous switch
models/vendors in the environment. By the time you've finally gotten it
to work you could have just went node to node and hand-written down the
MAC's and
To: xCAT Users Mailing list xcat-user@lists.sourceforge.net
Date: 01/22/2014 08:53 AM
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
On Jan 22, 2014, at 8:30 AM, Jonathan Mills jonmi...@renci.org
wrote: Comments inline...
From: David D Johnson david_john...@brown.edu
To: xCAT Users Mailing list xcat-user@lists.sourceforge.net
Date: 01/22/2014 08:53 AM
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
/2014 08:11 AM
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
--
I've been lurking on this discussion, and just checked to see what we've
got -- nbroot or genesis -- and we have both of them.
I had given up on node discovery years ago
xNBA is a customized gpxe image that xCAT uses.
NBFS is the older maintenance image that was used for if you set your
node to boot to shell, or booted a runimage script. NBFS is deprecated,
and Genesis replaced NBFS as the maintenance image for these tasks.
In a standard 2.8 install, there
Russell,
That's what I had been thinking.
# rpm -qa | grep -i xcat | sort
conserver-xcat-8.1.16-10.x86_64
elilo-xcat-3.14-4.noarch
ipmitool-xcat-1.8.11-3.x86_64
perl-xCAT-2.8.3-snap201311122316.noarch
syslinux-xcat-3.86-2.noarch
xCAT-2.8.3-snap201311122318.x86_64
Evidently though something in his xCAT setup it creating the files in
/tftpboot/pxelinux.cfg/ with reference to xnba just like my
installation. Where does xCAT grab the configuration for that? Maybe
it was because I didn't do a completely clean install and did an
in-place upgrade, but my cluster
It *should* work with xNBA and Genesis - xNBA is the PXE image that
loads Genesis. :-)
Genesis is the utility image that handles shell commands, runimages, etc.
Don't confuse NBFS with xNBA - NBFS is deprecated via Genesis. xNBA is
the gpxe image that loads Genesis or your normal OS image
...@hudsonalpha.org
To: xCAT Users Mailing list xcat-user@lists.sourceforge.net,
Date: 2014/01/22 05:56
Subject: Re: [xcat-user] Frustrating time with sequential node discovery
Ah, I see what you are saying now. Well, I
@lists.sourceforge.net,
Date: 2014/01/22 14:10
Subject:Re: [xcat-user] Frustrating time with sequential node discovery
It would seem to me that what I am missing is the whole of the
xCAT-nbroot infrastructure...because it isn't part of xcat-core, nor
xcat-dep. So I didn't grab it. But it just so
xCAT is using genesis (an xCAT customized pxe tool) to function the
discovery process. The configuration for genesis is put
in /tftpboot/xcat/xnba/nets/ for a specific network. Could you check your
specific xnba configuration file for your deployment network has been put
in
15 matches
Mail list logo
