Topic
3 replies Latest Post - ‏2009-07-29T05:42:56Z by SystemAdmin
Rajbatra
Rajbatra
22 Posts
ACCEPTED ANSWER

Pinned topic CSM installation issue

‏2009-07-28T17:49:28Z |
Hi Team,

Setup Detail
Blade Center H
Blades (JS22)
SUSE Linux (for Pseries)
CSM 1.7.1

Problem:

We have installed CSM management server and installed server on same machine, now we are going to install Linux through csm command on other nodes,then we are getting this error by installnode command .
Error:
========================
bicb01:/etc # installnode -n bicb02
WARNING: The InstallTemplate /opt/csm/install/yastcfg.SLES10-ppc64-bicb02-14.xml for node bicb02.imtech.res.in does not match the default value /opt/csm/install/yastcfg.SLES10-ppc64.xml. It might be a user-provided template, please make sure the template file exists and is valid for full installation or diskless installation. If you want to use the default template, blank out the InstallTemplate field and rerun csmsetupinstall
Rebooting Node for full install: bicb02.imtech.res.in
2651-941 Unrecognized flag: -1
======================

Log details.

Nodecond Status: Invoking /opt/csm/csmbin/hmc_nodecond bicb02.imtech.res.in
05:36:40: Wed Jul 29 2009
05:36:40: Nodecond Status: process id is 17129
05:36:40: Nodecond Status: using server IP address of 172.141.101.38
05:36:40: Nodecond Status: using gateway IP address of 0.0.0.0
05:36:40: Nodecond Status: using client IP address of 172.141.101.39
05:36:40: Nodecond Status: using kernel parameters of autoyast=nfs://172.141.101.38//csminstall/csm/SLES10/AC8D6527 dhcptimeout=150 netdevice=eth1 install=nfs://172.141.101.38//csminstall/Linux/SLES/10/ppc64/SP2/CD1
05:36:40: Nodecond Status: node bicb02.imtech.res.in
05:36:40: Nodecond Status: HMCNAME is 172.141.101.58
05:36:40: Nodecond Status: NODETYPE is blade
05:36:40: Nodecond Status: BladeCenter node detected
05:36:41: Nodecond Status: POWER6-based blade detected
05:36:41: Nodecond Status: node type is js20_blade
05:36:41: Nodecond Status: Hardware address is 00:1A:64:46:57:6D
05:36:41: Nodecond Status: install adapter speed is auto
05:36:41: Nodecond Status: install adapter duplex is auto
05:36:41: Nodecond Status: Querying conserver daemon
05:36:41: Nodecond Status: conserver is available
05:36:41: Nodecond Status: Conserver version is 8.1.7
05:36:41: Nodecond Status: Parsing console data
05:36:41: Nodecond Status: Searching for bicb02.imtech.res.in
05:36:41: Nodecond Status: Found target node
05:36:41: Nodecond Status: state is down
05:36:41: Nodecond Status: open S1 port
05:36:41: Nodecond Status: console command is /opt/csm/bin/rconsole -z -t -f -n bicb02.imtech.res.in
05:36:43: Nodecond Status: rconsole failure detected
05:36:43: ^M
/opt/csm/bin/blade_s1: invalid option -- 1^M
(null): 2651-941 Unrecognized flag: -1^M
^M
^M
attached^M
/opt/csm/bin/blade_s1: invalid option -- 1^M
(null): 2651-941 Unrecognized flag: -1^M
^M
^M
attached^M
/opt/csm/bin/blade_s1: invalid option -- 1^M
(null): 2651-941 Unrecognized flag: -1^M

Pls. help me to resolve this issue.

Regards
RajBatra
Updated on 2009-07-29T05:42:56Z at 2009-07-29T05:42:56Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    476 Posts
    ACCEPTED ANSWER

    Re: CSM installation issue

    ‏2009-07-29T02:29:29Z  in response to Rajbatra
    Hi,

    It seems your rconsole command does not work, so installnode can not transfer the kernel parameters to bicb02, could you check your console configurations to make rconsole works first?

    Thanks
    Jing
  • Rajbatra
    Rajbatra
    22 Posts
    ACCEPTED ANSWER

    Re: CSM installation issue

    ‏2009-07-29T05:33:39Z  in response to Rajbatra
    Hi Sunjing,

    Thanks for reply,we have only one ESM in BC and due to we can not use SOL and network installed method in js22 blades simultaneously. so can we disable rconsole in the installnode script or any other way to install linux node without using rconsole.

    Regards
    RajBatra
    • SystemAdmin
      SystemAdmin
      476 Posts
      ACCEPTED ANSWER

      Re: CSM installation issue

      ‏2009-07-29T05:42:56Z  in response to Rajbatra
      Hi Rajbatra,

      You can try installnode with --noreboot flag, this will hack the kernal parameters into zImage, then you reboot your target node manually