Re: [xcat-user] Fail to rinstall node on NextScale nx360m5

2016-05-05 Thread Xiao Peng Wang 
The error message said 'press cancel to get into interactive installation'.
ThanksBest Regards--Wang Xiaopeng (王晓朋)IBM China System Technology LaboratoryTel: 86-10-82453455Email: w...@cn.ibm.comAddress: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
 
 
- Original message -From: "Keiichi Suzuki" To: xcat-user@lists.sourceforge.netCc:Subject: Re: [xcat-user] Fail to rinstall node on NextScale nx360m5Date: Thu, May 5, 2016 4:19 PM 
Dear Wang Xiaopeng,Thank you for your support.>So could you try to use the installer console to reconfigure the network for the failed node to see whether it could succeed.In particular, how shoud I do for the failed node ? I can't find how reconfigure the network on failed node.Best Regards,Keiichi Suzuki.--Then looks like the failed node has problem to enable the nic. So could you try to use the installer console to reconfigure the network for the failed node to see whether it could succeed.ThanksBest Regards--Wang Xiaopeng (王?朋)IBM China System Technology LaboratoryTel: 86-10-82453455Email: wxp@...Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193- Original message -From: "Keiichi Suzuki" To: xcat-user@...Cc:Subject: Re: [xcat-user] Fail to rinstall node on NextScale nx360m5Date: Wed, May 4, 2016 11:35 AMDear Wang Xiaopeng,Thank you for your support.I can see only following messages from console for the failed node.(ex. Error messages on one of failed node)Unable to download the kickstart file. Please modify the kickstart parameter below or press Cansel to procees as an interactive installation.http://10.35.37.27:80/install/autoinst/testnode005For syslog, I can't find error messages, and failed nodes are get DHCP-IPaddress (but stop avobe Error messages)(xcat01 is xcat-server, testnode05 and 10.35.33.85 is failed node's IP-address)May 4 12:15:09 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:14 xcat01 dhcpd: Dynamic and static leases present for 10.35.33.85.May 4 12:15:14 xcat01 dhcpd: Remove host declaration testnode05 or remove 10.35.33.85May 4 12:15:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.85 (10.35.37.27) from 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:14 xcat01 dhcpd: DHCPACK on 10.35.33.85 to 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:14 xcat01 in.tftpd[8123]: RRQ from 10.35.33.85 filename xcat/xnba.kpxeMay 4 12:15:14 xcat01 in.tftpd[8124]: RRQ from 10.35.33.85 filename xcat/xnba.kpxeMay 4 12:15:14 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:14 xcat01 dhcpd: Dynamic and static leases present for 10.35.33.85.May 4 12:15:14 xcat01 dhcpd: Remove host declaration testnode05 or remove 10.35.33.85May 4 12:15:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.85 (10.35.37.27) from 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:14 xcat01 dhcpd: DHCPACK on 10.35.33.85 to 40:f2:e9:c6:7c:e6 via bond0May 4 12:15:53 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to 40:f2:e9:c6:7c:e6 via bond0(xcat01 is xcat-server, testnode10 and 10.35.33.96 is succeed node's IP-address)May 4 12:21:32 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:21:37 xcat01 dhcpd: Dynamic and static leases present for 10.35.33.96.May 4 12:21:37 xcat01 dhcpd: Remove host declaration testnode10 or remove 10.35.33.96May 4 12:21:37 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27) from 40:f2:e9:c6:80:be via bond0May 4 12:21:37 xcat01 dhcpd: DHCPACK on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:21:37 xcat01 in.tftpd[8224]: RRQ from 10.35.33.96 filename xcat/xnba.kpxeMay 4 12:21:37 xcat01 in.tftpd[8225]: RRQ from 10.35.33.96 filename xcat/xnba.kpxeMay 4 12:21:37 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:21:37 xcat01 dhcpd: Dynamic and static leases present for 10.35.33.96.May 4 12:21:37 xcat01 dhcpd: Remove host declaration testnode10 or remove 10.35.33.96May 4 12:21:37 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27) from 40:f2:e9:c6:80:be via bond0May 4 12:21:37 xcat01 dhcpd: DHCPACK on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:22:14 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:22:14 xcat01 dhcpd: Dynamic and static leases present for 10.35.33.96.May 4 12:22:14 xcat01 dhcpd: Remove host declaration testnode10 or remove 10.35.33.96May 4 12:22:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27) from 40:f2:e9:c6:80:be via bond0May 4 12:22:14 xcat01 dhcpd: DHCPACK on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:22:21 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to 40:f2:e9:c6:80:be via bond0May 4 12:22:21

Re: [xcat-user] How can I migrate to a new xCAT MN in a hierarchical environment?

2016-05-05 Thread Josh Nielsen 
Hi Christian,

Thanks for the response. So do I actually have to reinstall the SNs and/or
rerun the service node postscript? If reruning the SN post script just
makes some minor adjustments but doesn't clear the dhcpd.leases and the
.conf files for named and dhcp, as I have them configured, then that would
be fine, but if it blows all that away and starts over that would qualify
as disruptive for my environment since the cluster depends on slave DNS
services and dhcp on the SN. I would ideally like minimal changes on the
SNs except to point them to the new MN.

As far as the postscripts, my question was what common (if not default in
most installs) postscripts that come with xCAT have code in them that would
result in the hardcoding of the MN's IP in some configuration file. I
actually thought of one possible example along those lines, and that is
whatever configures the client compute nodes to send all their syslog
messages to the /var/log/messages log on the headnode instead of locally
will need to be rerun/updated. What will need to be run to change that to
make the clients log to the new MN server?

Regarding the server identity (even though it will have a new IP address
and hostname) can we just copy the keys in /etc/ssh/ to the new MN so that
the SSH fingerprint doesn't change?

Lastly, as regards running updatenode -k I definitely (in this case) do not
want to replace the root rsa_id private and public keys on the cluster, the
MN, or the SNs since other critical services like GPFS require the current
keys to remain in place. Why is rerunning the key deploy necessary and is
there not a way to make it work with the current keys?

I just need to be very careful with my current setup so that I don't knock
out critical services while changing the MN, which is why I was wondering
how disruptive doing this might be. I appreciate the help!

Thanks,
Josh

On Tue, May 3, 2016 at 10:05 AM, Christian Caruthers 
wrote:

> I would begin by looking at the servicenode postscript. It sets up the
> daemon and database communications between SN & MN. Beyond that, the
> default postscripts are listed in the "xcatdefaults" entry of the
> postscripts table. You will probably want to run updatenode -k once you
> have xCAT configured on the new MN. After that, you probably want to rerun
> the remoteshell and syslog postscripts on the cluster members (updatenode
> -P) at the very least.
>
>
>
> Second, you can dump the xCAT DB using dumpxCATdb command. After that,
> grep out the management node (hostname and/or IP) to see where changes need
> to be made for the DB on the new MN.
>
>
>
> If the SNs are handling DHCP, it only needs to be enabled on the MN if you
> plan in reinstaling a SN.
>
>
>
> Anything that resolves DNS through the MN will need an updated resolv.conf.
>
>
>
> Depending on how you're maintaining your /install directory on the SNs,
> that mechanism will need to be updated.
>
>
>
> If your MN is routing for any nodes, that will need to be addressed. You
> might want to check the network configuration on the IMMs. On discovery, if
> you have a gateway defined on your management network (I believe it
> defaults to ), they might be pointing to the old MN. Shouldn't
> be an issue, but it's something to think about. If you're not routing on
> that network, I would use pasu to set the IMM gateway to 0.0.0.0 and be
> done with it.
>
>
>
> The only other concern I can think of would be the installation repos
> configured on the cluster nodes and SNs. If any point to the MN, they will
> need to be changed.
>
>
>
> Aside from all of that, it really depends on the particulars your cluster.
>
>
>
> Regards,
> *Christian Caruthers*
> Lenovo xESS IT Consultant
>
> Mobile: 757-289-9872
>
>
>
>
>
> *From:* Josh Nielsen [mailto:jniel...@hudsonalpha.org]
> *Sent:* Monday, May 02, 2016 8:32 PM
> *To:* xCAT Users Mailing list
> *Subject:* [xcat-user] How can I migrate to a new xCAT MN in a
> hierarchical environment?
>
>
>
> Hello all,
>
> My team is trying to move the xCAT MN role off of an old server and get it
> over onto new virtual infrastructure, but I am a little unsure about
> whether it is possible to do while leaving everything else in its place as
> we currently have it in our environment. We have an MN with two SNs for our
> xCAT environment, and I would need to make the SNs recognize that the new
> MN (with a new IP and hostname) is now their xcatmaster, and they would
> need to take hierarchical command updates from the new MN, look to the new
> MN for the xCAT database (which is a MySQL database in our environment),
> etc.
>
> So a few questions along those lines.
>
> 1. Which/how many xCAT database fields would I need to update that use the
> MN's IP (other than "master" in the site table), and would I have to
> reinstall or otherwise update anything on the SNs (I imagine restarting the
> daemons is necessary at a minimum) in case they have anything statically
> configured for the current

Re: [xcat-user] rvitals leds on new lenovo nodes

2016-05-05 Thread Matthias Marx 
Hi Christopher,

I had this issue before. After I replaced the ipmi.pm module I had to clear the 
sdr sensor cache as well.

$ rm /var/cache/xcat/sdr*

Mit freundlichen Grüßen/Kind Regards

--
Matthias Marx
HPC Engineer
Professional Services
Enterprise Business Group

mail: mm...@lenovo.com
mobile: +49-162-1001688
phone: +49-711-65690-785

Lenovo (Deutschland) GmbH | Meitnerstrasse 9 | 70563 Stuttgart
Geschäftsführung: Bernhard Fauser | Sitz der Gesellschaft: Stuttgart | HRB-Nr.: 
25189, AG Stuttgart | WEEE-Reg.-Nr.: DE79679404

- Forwarded message from Jarrod Johnson  -
 Date: Thu, 5 May 2016 11:40:18 +
 From: Jarrod Johnson 
Reply-To: xCAT Users Mailing list 
  Subject: Re: [xcat-user] rvitals leds on new lenovo nodes
   To: xCAT Users Mailing list 

What does rinv show about the node?  Replacing just ipmi.pm in xCAT_plugin 
should have done the trick.  I'll be in the office in an couple of hours and I 
can double check.



From: "Christopher J. Walker" 
Sent: May 5, 2016 7:20 AM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] rvitals leds on new lenovo nodes

Thanks very much for the suggestion.

We've now tried upgrading just that file, and it doesn't fix the problem, 
though it does change the message from

"LED status not supported on this system"

to:

 [root@mgt.apocrita tmp]# rvitals sched0 leds
 sched0: No supported LEDs found in system


The version from 2.11.1 has similar results.

I guess we could upgrade the whole of xCAT to 2.10 - but that's a lot more work 
(we are still using pre osimage deployment on many of our nodes, and I believe 
we need to fix that first).

I assume that it gets the status via a vendor specific IPMI command. Is this 
documented somewhere?

Chris

PS, we are using the latest IMM firmware on the machines.

On 12/04/16 12:53, Markus Hilger wrote:
> Hi,
> yes we experienced the same issue.
> You have to upgrade to xCAT 2.10 or just update your ipmi.pm file.
> This one:
> https://raw.githubusercontent.com/xcat2/xcat-core/2.10/xCAT-server/lib
> /xcat/plugins/ipmi.pm Mit freundlichen Grüßen / Kind regards *Markus
> Hilger* Infrastructure Architect GTS / High Performance Computing 
> Services
>
> --
> --
> Phone: +49-7034-274-0859 | Mobile: +49-173-2105582
> E-mail: markus.hil...@de.ibm.com 
> Website: obihoernchen.net  Find me on: Xing: 
> https://www.xing.com/profile/Markus_Hilger8
>  LinkedIn:
> https://www.linkedin.com/profile/view?id=237120059
>  Github:
> https://github.com/Obihoernchen  and 
> within IBM on: IBM Connections:
> https://w3-connections.ibm.com/profiles/html/profileView.do?userid=f9e
> beb40-793f-1030-9788-8deeeb1cb
> 
>IBM
>
> Nahmitzer Damm 12
> Berlin, 12277
> Germany
>
> IBM Deutschland Business & Technology Services GmbH
> Geschäftsführung: Baerbel Altmann, Frank Hammer, Thorsten Moehring 
> Sitz der Gesellschaft: Ehningen
> Registergericht: Amtsgericht Stuttgart, HRB 17122
>
> - Original message -
> From: "Christopher J. Walker" 
> To: "xcat-user@lists.sourceforge.net" 
> Cc:
> Subject: [xcat-user] rvitals leds on new lenovo nodes
> Date: Mon, Apr 11, 2016 11:56 AM
> To find hardware issues, we use:
>
>   rvitals machinenames leds
>
> On some new lenovo machines, we get:
>
>   "LED status not supported on this system"
>
> The machines are Lenovo NeXtScale nx360 M5: -[546562G] - with the IMM
> advanced option.
>
> xCAT version is 2.9
>
> Has anyone else experienced this? Is there an easy solution?
>
> At our Lenovo technical sales contact's suggestion, a colleague has
> opened a support ticket - though it seems to be bouncing between
> hardware and software teams, so I thought I'd ask this list.
>
> Chris
>
>
>
>  
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into
> multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
>

Re: [xcat-user] rvitals leds on new lenovo nodes

2016-05-05 Thread Jarrod Johnson 
What does rinv show about the node?  Replacing just ipmi.pm in xCAT_plugin 
should have done the trick.  I'll be in the office in an couple of hours and I 
can double check.



From: "Christopher J. Walker" 
Sent: May 5, 2016 7:20 AM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] rvitals leds on new lenovo nodes

Thanks very much for the suggestion.

We've now tried upgrading just that file, and it doesn't fix the
problem, though it does change the message from

   "LED status not supported on this system"

to:

[root@mgt.apocrita tmp]# rvitals sched0 leds
sched0: No supported LEDs found in system


The version from 2.11.1 has similar results.

I guess we could upgrade the whole of xCAT to 2.10 - but that's a lot
more work (we are still using pre osimage deployment on many of our
nodes, and I believe we need to fix that first).

I assume that it gets the status via a vendor specific IPMI command. Is
this documented somewhere?

Chris

PS, we are using the latest IMM firmware on the machines.

On 12/04/16 12:53, Markus Hilger wrote:
> Hi,
> yes we experienced the same issue.
> You have to upgrade to xCAT 2.10 or just update your ipmi.pm file.
> This one:
> https://raw.githubusercontent.com/xcat2/xcat-core/2.10/xCAT-server/lib/xcat/plugins/ipmi.pm
> Mit freundlichen Grüßen / Kind regards
> *Markus Hilger*
> Infrastructure Architect
> GTS / High Performance Computing Services
>
> 
> Phone: +49-7034-274-0859 | Mobile: +49-173-2105582
> E-mail: markus.hil...@de.ibm.com 
> Website: obihoernchen.net 
> Find me on: Xing: https://www.xing.com/profile/Markus_Hilger8
>  LinkedIn:
> https://www.linkedin.com/profile/view?id=237120059
>  Github:
> https://github.com/Obihoernchen  and
> within IBM on: IBM Connections:
> https://w3-connections.ibm.com/profiles/html/profileView.do?userid=f9ebeb40-793f-1030-9788-8deeeb1cb
> 
>IBM
>
> Nahmitzer Damm 12
> Berlin, 12277
> Germany
>
> IBM Deutschland Business & Technology Services GmbH
> Geschäftsführung: Baerbel Altmann, Frank Hammer, Thorsten Moehring
> Sitz der Gesellschaft: Ehningen
> Registergericht: Amtsgericht Stuttgart, HRB 17122
>
> - Original message -
> From: "Christopher J. Walker" 
> To: "xcat-user@lists.sourceforge.net" 
> Cc:
> Subject: [xcat-user] rvitals leds on new lenovo nodes
> Date: Mon, Apr 11, 2016 11:56 AM
> To find hardware issues, we use:
>
>   rvitals machinenames leds
>
> On some new lenovo machines, we get:
>
>   "LED status not supported on this system"
>
> The machines are Lenovo NeXtScale nx360 M5: -[546562G] - with the IMM
> advanced option.
>
> xCAT version is 2.9
>
> Has anyone else experienced this? Is there an easy solution?
>
> At our Lenovo technical sales contact's suggestion, a colleague has
> opened a support ticket - though it seems to be bouncing between
> hardware and software teams, so I thought I'd ask this list.
>
> Chris
>
>
>
> 
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into
> multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>
>
>
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly

Re: [xcat-user] rvitals leds on new lenovo nodes

2016-05-05 Thread Christopher J. Walker 
Thanks very much for the suggestion.

We've now tried upgrading just that file, and it doesn't fix the 
problem, though it does change the message from

   "LED status not supported on this system"

to:

[root@mgt.apocrita tmp]# rvitals sched0 leds
sched0: No supported LEDs found in system


The version from 2.11.1 has similar results.

I guess we could upgrade the whole of xCAT to 2.10 - but that's a lot 
more work (we are still using pre osimage deployment on many of our 
nodes, and I believe we need to fix that first).

I assume that it gets the status via a vendor specific IPMI command. Is 
this documented somewhere?

Chris

PS, we are using the latest IMM firmware on the machines.

On 12/04/16 12:53, Markus Hilger wrote:
> Hi,
> yes we experienced the same issue.
> You have to upgrade to xCAT 2.10 or just update your ipmi.pm file.
> This one:
> https://raw.githubusercontent.com/xcat2/xcat-core/2.10/xCAT-server/lib/xcat/plugins/ipmi.pm
> Mit freundlichen Grüßen / Kind regards
> *Markus Hilger*
> Infrastructure Architect
> GTS / High Performance Computing Services
>
> 
> Phone: +49-7034-274-0859 | Mobile: +49-173-2105582
> E-mail: markus.hil...@de.ibm.com 
> Website: obihoernchen.net 
> Find me on: Xing: https://www.xing.com/profile/Markus_Hilger8
>  LinkedIn:
> https://www.linkedin.com/profile/view?id=237120059
>  Github:
> https://github.com/Obihoernchen  and
> within IBM on: IBM Connections:
> https://w3-connections.ibm.com/profiles/html/profileView.do?userid=f9ebeb40-793f-1030-9788-8deeeb1cb
> 
>   IBM
>
> Nahmitzer Damm 12
> Berlin, 12277
> Germany
>
> IBM Deutschland Business & Technology Services GmbH
> Geschäftsführung: Baerbel Altmann, Frank Hammer, Thorsten Moehring
> Sitz der Gesellschaft: Ehningen
> Registergericht: Amtsgericht Stuttgart, HRB 17122
>
> - Original message -
> From: "Christopher J. Walker" 
> To: "xcat-user@lists.sourceforge.net" 
> Cc:
> Subject: [xcat-user] rvitals leds on new lenovo nodes
> Date: Mon, Apr 11, 2016 11:56 AM
> To find hardware issues, we use:
>
>   rvitals machinenames leds
>
> On some new lenovo machines, we get:
>
>   "LED status not supported on this system"
>
> The machines are Lenovo NeXtScale nx360 M5: -[546562G] - with the IMM
> advanced option.
>
> xCAT version is 2.9
>
> Has anyone else experienced this? Is there an easy solution?
>
> At our Lenovo technical sales contact's suggestion, a colleague has
> opened a support ticket - though it seems to be bouncing between
> hardware and software teams, so I thought I'd ask this list.
>
> Chris
>
>
>
> 
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into
> multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>
>
>
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Re: [xcat-user] Fail to rinstall node on NextScale nx360m5

2016-05-05 Thread Keiichi Suzuki 

Dear Wang Xiaopeng,

Thank you for your support.

>So could you try to use the installer console to reconfigure the network
for the failed node to see whether it could succeed.
In particular, how shoud I do for the failed node ? I can't find how
reconfigure the network on failed node.


Best Regards,
Keiichi Suzuki.
--

Then looks like the failed node has problem to enable the nic. So could you
try to use the installer console to reconfigure the network for the failed
node to see whether it could succeed.

Thanks
Best Regards
--
Wang Xiaopeng (王?朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: wxp@...
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road,
Haidian District Beijing P.R.China 100193



- Original message -
From: "Keiichi Suzuki" 
To: xcat-user@...
Cc:
Subject: Re: [xcat-user] Fail to rinstall node on NextScale nx360m5
Date: Wed, May 4, 2016 11:35 AM


Dear Wang Xiaopeng,

Thank you for your support.

I can see only following messages from console for the failed node.


(ex. Error messages on one of failed node)
Unable to download the kickstart file. Please modify the kickstart
parameter below or press Cansel to procees as an interactive installation.
http://10.35.37.27:80/install/autoinst/testnode005


For syslog, I can't find error messages, and failed nodes are get
DHCP-IPaddress (but stop avobe Error messages)

(xcat01 is xcat-server, testnode05 and 10.35.33.85 is failed node's
IP-address)
May 4 12:15:09 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to
40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:14 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.85.
May 4 12:15:14 xcat01 dhcpd: Remove host declaration testnode05 or
remove 10.35.33.85
May 4 12:15:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.85 (10.35.37.27)
from 40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:14 xcat01 dhcpd: DHCPACK on 10.35.33.85 to
40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:14 xcat01 in.tftpd[8123]: RRQ from 10.35.33.85 filename
xcat/xnba.kpxe
May 4 12:15:14 xcat01 in.tftpd[8124]: RRQ from 10.35.33.85 filename
xcat/xnba.kpxe
May 4 12:15:14 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to
40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:14 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.85.
May 4 12:15:14 xcat01 dhcpd: Remove host declaration testnode05 or
remove 10.35.33.85
May 4 12:15:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.85 (10.35.37.27)
from 40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:14 xcat01 dhcpd: DHCPACK on 10.35.33.85 to
40:f2:e9:c6:7c:e6 via bond0
May 4 12:15:53 xcat01 dhcpd: DHCPOFFER on 10.35.33.85 to
40:f2:e9:c6:7c:e6 via bond0



(xcat01 is xcat-server, testnode10 and 10.35.33.96 is succeed node's
IP-address)
May 4 12:21:32 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:21:37 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.96.
May 4 12:21:37 xcat01 dhcpd: Remove host declaration testnode10 or
remove 10.35.33.96
May 4 12:21:37 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27)
from 40:f2:e9:c6:80:be via bond0
May 4 12:21:37 xcat01 dhcpd: DHCPACK on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:21:37 xcat01 in.tftpd[8224]: RRQ from 10.35.33.96 filename
xcat/xnba.kpxe
May 4 12:21:37 xcat01 in.tftpd[8225]: RRQ from 10.35.33.96 filename
xcat/xnba.kpxe
May 4 12:21:37 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:21:37 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.96.
May 4 12:21:37 xcat01 dhcpd: Remove host declaration testnode10 or
remove 10.35.33.96
May 4 12:21:37 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27)
from 40:f2:e9:c6:80:be via bond0
May 4 12:21:37 xcat01 dhcpd: DHCPACK on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0

May 4 12:22:14 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:22:14 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.96.
May 4 12:22:14 xcat01 dhcpd: Remove host declaration testnode10 or
remove 10.35.33.96
May 4 12:22:14 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27)
from 40:f2:e9:c6:80:be via bond0
May 4 12:22:14 xcat01 dhcpd: DHCPACK on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:22:21 xcat01 dhcpd: DHCPOFFER on 10.35.33.96 to
40:f2:e9:c6:80:be via bond0
May 4 12:22:21 xcat01 dhcpd: Dynamic and static leases present for
10.35.33.96.
May 4 12:22:21 xcat01 dhcpd: Remove host declaration testnode10 or
remove 10.35.33.96
May 4 12:22:21 xcat01 dhcpd: DHCPREQUEST for 10.35.33.96 (10.35.37.27)
from 40:f2:e9:c6:80:be via bond0
May 4 12:22:21 xcat01 dhcpd: DHCPACK