Since you already ran updatenode, then everything in /tmp/wget.log
and /var/log/xcat/xcat.log should already be right. Do we still have nodes
that just finished the os installation and have not run updatenode?
the /tmp/wget.log and /var/log/xcat/xcat.log should include useful hints.
Thanks,
--
On Wed, 25 Jul 2012 07:06:39 Lissa Valletta wrote:
> In fact make sure all files in the /install/postscripts directory and
> subdirectories are world readable. This can cause a failure that will
> show up in the wget.log that Guang Cheng Li asked for below.
> Thanks!
>
Ok I will give you a bi
Okay, thanks for the explanation.
Cheers,
Josh
On Wed, Jul 25, 2012 at 2:28 PM, Jarrod B Johnson wrote:
> So the issue is that the xnba can work fine. The problem is the linux
> image that subsequently loads lacked the driver update. In an ideal world,
> we make an efi executable that does eve
So the issue is that the xnba can work fine. The problem is the linux image that subsequently loads lacked the driver update. In an ideal world, we make an efi executable that does everything in UEFI that is moderately future proof. In a practical world we work with the much richer linux toolset
Okay, we will be doing an upgrade of xCAT soon. I just wanted to double
check.
P.S. Can you take a crack at answering that gPXE/UNDI question?
On Wed, Jul 25, 2012 at 1:37 PM, Jarrod B Johnson wrote:
> Hmm, with xcat 2.7.3 you should be pulling in the 'xCAT-genesis' packages
> that replace the e
Hmm, with xcat 2.7.3 you should be pulling in the 'xCAT-genesis' packages that replace the environment with something newer that has the appropriate nic drivers...-Josh Nielsen wrote: -To: xcat-user@lists.sourceforge.netFrom: Josh Nielsen Date: 07/25/2012 12:59PMSubject: [xcat-user] Getdes
Thanks for the information Lissa.
I do have another more general question as well though. It is regarding the
xnba boot image itself, which appears to be based off of gPXE. The idea of
gPXE is that it is UNDI-capable and does not have to use TFTP to serve the
images correct? And looking at the xnb
Version 2.3.x has not been supported for a long time. You need to be on
the latest level of 2.6 for support , but you might as well go to the
latest release which is 2.7.3. You can upgrade xCAT and stay at your
current Centos level.
Lissa K. Valletta
2-3/T12
Poughkeepsie, NY 12601
(tie 293
Hello,
I have some new IBM System X DX360M4 nodes (all our previous ones were
DX360M3s) that I am trying to autodiscover with xCAT and I am running into
the same problem as in this mail thread:
http://www.mail-archive.com/xcat-user@lists.sourceforge.net/msg01267.html.
Essentially the node boots up
Hello,
Yes there is an entry in the networks table and an alias on the xCAT
server so that it can communicate with the client nodes imm where the
address is properly configured as shared when I do runcmd=bmcsetup.
Actually, the entry in the table was created at installation because the
alias e
Does your network table has a definition for the bmc network?
On 25 July 2012 17:22, Antoine Tabary wrote:
> Hello,
>
> When I power on a node, discovery works fine the mac address is added to
> table mac, and /var/lib/dhcpd/dhcpd.leases is updated. The node renews its
> IP address changing the
Hello,
When I power on a node, discovery works fine the mac address is added to
table mac, and /var/lib/dhcpd/dhcpd.leases is updated. The node renews its
IP address changing the discovery address by its final address, but then
it loops forever with an Unrecognized directive coming from
/bin/
In the past, I added 'nostorage' to bootparams.addkcmdline and then in the
KS template added:
For RHEL <= 5.x:
device scsi mptsas
In the ongoing effort to fix that which is not broken, Red Hat apparently
removed this from kickstart, but I found the following which might prove
helpful:
https://w
In fact make sure all files in the /install/postscripts directory and
subdirectories are world readable. This can cause a failure that will
show up in the wget.log that Guang Cheng Li asked for below.
Thanks!
Lissa K. Valletta
2-3/T12
Poughkeepsie, NY 12601
(tie 293) 433-3102
From: Lis
Do the postscripts you added to /install/postscripts have the correct
permission. They must be world-readable and executable at least by root.
Check against our postscripts, something like
-rwxr-xr-x 1 root root 9869 Jul 3 09:50 syslog
Also run lsdef
what is in the postscripts attribute?
L
15 matches
Mail list logo
