Menu
▾
▴
[xcat-user] nodeset install results in Windows netboot error message
|
From: jeroen.van.hoof at nl.ibm.c. (J. v. Hoof) - 2009-10-24 11:48:14
|
Hi Maarten, Add "brokenmodules=lpfc" as field addkcmdline to the bootparams table for the node ;-) Jeroen From: Maarten J Kreuger/Netherlands/IBM@IBMNL To: xCAT Users Mailing list <xca...@li...> Date: 23-10-2009 18:27 Subject: Re: [xcat-user] nodeset install results in Windows netboot error message Having a nodename that translates to a different network then the install network does seem to cause problems, even if I change the nodename to be an alias to installation network interface address in the hosts table and DNS. The node installation hangs in the first item during the autoyast phase just after all RPMS are installed, when the next screen is displayed, just before the boot image is created: "copy files to system". After I deleted the node definition, and added the node again with the intallation network name by manipulating the stanza file created by rscan, the node installed fine. Even though it may be possible to set the nodename to something other then the installation address' name, SuSE autoyast does not seem to like it. So I would think that "normally" should be read as "mandatory". Best regards, Maarten Kreuger xca...@li... wrote on 10/23/2009 01:41:12 PM: > Bruce M Potter <bp...@us...> > Sent by: xca...@li... > > 10/23/2009 01:41 PM > > Please respond to > xCAT Users Mailing list <xca...@li...> > > To > > xCAT Users Mailing list <xca...@li...> > > cc > > Subject > > Re: [xcat-user] nodeset install results in Windows netboot error message > > Hmmm, normally you should give the node the same name in the DB as > it will have on the installation NIC. I.e. in your case I would have > defined the node in the DB as p6024-mgmt. This would have avoided > your /etc/hosts problem. > > The xcat node name can be different from the LPAR name. Rscan just > uses the LPAR name as the xcat node name by default, for lack of > anything else to use. You instead could have run rscan with -z and > without -w and saved the stanza output to a file, changed the node > names to add -mgmt, and then piped the file into mkdef. When all is > said and done, I don't think xcat even stores the LPAR name in the > DB, just the LPAR number. > > But I haven't heard of an xcat installation in which the xcat node > name in the DB is different from the installation NIC hostname in / > etc/hosts. I don't know what other problems you might run into as a > result of this. Has anyone else tried this? > > BTW, we opened a bug for the erroneous Windows error msg: https:// > sourceforge.net/tracker/?func=detail&aid=2884205&group_id=208749&atid=1006945 > . Probably won't get fixed until 2.3.1, because it's a little bit involved. > > > Bruce Potter STSM, Linux & AIX Cluster Development, IBM, Poughkeepsie, NY > Email: bp...@us... Phone: external: 845-433-7073, internal: TL 293-7073 > > [image removed] Maarten J Kreuger ---10/23/2009 07:15:17 AM---That > was it. Thanks! I added p6024 as an alias to the management network > entry in /etc/hosts, > > [image removed] > From: > > [image removed] > Maarten J Kreuger <maa...@nl...> > > [image removed] > To: > > [image removed] > xCAT Users Mailing list <xca...@li...> > > [image removed] > Date: > > [image removed] > 10/23/2009 07:15 AM > > [image removed] > Subject: > > [image removed] > Re: [xcat-user] nodeset install results in Windows netboot error message > > [image removed] > Sent by: > > [image removed] > xca...@li... > > > > > That was it. Thanks! > I added p6024 as an alias to the management network entry in /etc/ > hosts, and removed all other references, now it does not complain > about Windows anymore. > > Because I'm migrating from a CSM cluster, the lpar names are linked > to the wrong network. In an overview: > > The installation network is 192.168.86.0/23, on which nodes are > called like p6024-mgmt > The external access network is 145.x.y.0/24 on which nodes are > called like p6024 > The LPARs defined on the p575 servers are called like p6024 > nodenames in xcat were set by rscan the LPAR names. > It does not seem possible to have a different name for the LPAR, the > xCAT node and the installation network hostname. That is a shame, > and should be more clear in the Documentation. > > Best regards, > Maarten Kreuger > > > > > > I just caught this bug too. For me it was doing it because I didn't > have an IP defined in /etc/hosts for p6024. Once I added the IP > address and ran makedns; service named restart; then it worked. > > This bug should get fixed for the GA release next week. Right guys? > > On Thu, Oct 22, 2009 at 8:00 AM, Maarten J Kreuger <maa...@nl... > > wrote: > I'm trying to set up xCAT 2.3 (latest build) to install p6 p575 > nodes with SLES11. I have power control and console access working, > and all my nodes are put into the database, including MAC addresses. > The first node I try to install results in a weird error message: > > xcatserver:/ # nodeset p6024 install > Error: The Windows netboot image is not created, consult > documentation on how to add Windows deployment support to xCAT > > csm2:/var/lib/named # nodels p6024 noderes > p6024: noderes.primarynic: eth4 > p6024: noderes.installnic: eth4 > p6024: noderes.netboot: yaboot > p6024: noderes.node: p6024 > p6024: noderes.nfsserver: 192.168.86.5 > > The netboot setting looks like yaboot to me, not windows boot. The > nodetype has the setting for sles and the architecture: > > xcatserver:/ # nodels p6024 nodetype > p6024: nodetype.profile: compute > p6024: nodetype.provmethod: install > p6024: nodetype.arch: ppc64 > p6024: nodetype.nodetype: lpar > p6024: nodetype.node: p6024 > p6024: nodetype.os: sles11 > > How do I tell xcat I want an autoyast install with SLES11 on ppc64, > instead of Windows? Have I missed something? > > Best regards, > Maarten Kreuger > > Tenzij hierboven anders aangegeven: / Unless stated otherwise above: > IBM Nederland B.V. > Gevestigd te Amsterdam > Inschrijving Handelsregister Amsterdam Nr. 33054214 > > _______________________________________________ > xcat-user mailing list > xca...@li... > http://www.xcat.org/mailman/listinfo/xcat-user > > _______________________________________________ > xcat-user mailing list > xca...@li... > http://www.xcat.org/mailman/listinfo/xcat-user > > > > Tenzij hierboven anders aangegeven: / Unless stated otherwise above: > IBM Nederland B.V. > Gevestigd te Amsterdam > Inschrijving Handelsregister Amsterdam Nr. 33054214 > _______________________________________________ > xcat-user mailing list > xca...@li... > http://www.xcat.org/mailman/listinfo/xcat-user > _______________________________________________ > xcat-user mailing list > xca...@li... > http://www.xcat.org/mailman/listinfo/xcat-user Tenzij hierboven anders aangegeven: / Unless stated otherwise above: IBM Nederland B.V. Gevestigd te Amsterdam Inschrijving Handelsregister Amsterdam Nr. 33054214 _______________________________________________ xcat-user mailing list xca...@li... http://www.xcat.org/mailman/listinfo/xcat-user Tenzij hierboven anders aangegeven: / Unless stated otherwise above: IBM Nederland B.V. Gevestigd te Amsterdam Inschrijving Handelsregister Amsterdam Nr. 33054214 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xcat.org/pipermail/xcat-user/attachments/20091024/8f82c07e/attachment-0001.htm |