Dave,
I looked into this a little more.  In your case you have "sharedtftp=0" set
in your site table.  So, that means /tftboot is not mounted from the
management to your service nodes, so nodeset needs to get sent to all the
service nodes to create the correct /tftpboot files.    As a quick test, if
you set "disjointdhcps=1" and "sharedtftp=1", the nodeset should only go to
the service node for that node.

What I need to investigate still is why we would need ALL service nodes to
have /tftpboot files for ALL nodes, or if this code needs to be made
smarter, too.

Linda




From:   Dave Barry <[email protected]>
To:     xCAT Users Mailing list <[email protected]>
Date:   10/11/2011 02:54 PM
Subject:        Re: [xcat-user] Why are service nodes sent commands for *all*
            nodes?



Thanks! I'm pretty sure this only applies to service node pools however,
and if "disjointdhcps" is set to 0. In this particular setup I have
"disjointdhcps" set to 1:

[root@mn ~]# tabdump site
#key,value,comments,disable
"blademaxp","64",,
"domain","xcat",,
"fsptimeout","0",,
"installdir","/install",,
"ipmimaxp","64",,
"ipmiretries","3",,
"ipmitimeout","2",,
"consoleondemand","no",,
"master","192.168.1.1",,
"maxssh","8",,
"ppcmaxp","64",,
"ppcretry","3",,
"ppctimeout","0",,
"sharedtftp","0",,
"SNsyncfiledir","/var/xcat/syncfiles",,
"tftpdir","/tftpboot",,
"xcatdport","3001",,
"xcatiport","3002",,
"xcatconfdir","/etc/xcat",,
"timezone","America/New_York",,
"useNmapfromMN","no",,
"enableASMI","no",,
"vsftp","y",,
"nameservers","192.168.1.1",,
"forwarders","4.2.2.1",,
"installloc","storage01:/install",,
"svloglocal","0",,
"disjointdhcps","1",,
"dhcpinterfaces","mn|eth1;service01|eth0;service02|eth0",,
"dhcpsetup","n",,
"dnshandler","bind",,




So Service02 would not have any DHCP information for this node, yet my
management node is still trying to talk to Service02. Is this a bug then
perhaps?



On Tue, Oct 11, 2011 at 1:26 PM, Linda Mellor <[email protected]> wrote:
  For the nodeset command in particular, often there is a single network
  between all service nodes and compute nodes. During compute node
  deployment, DHCP broadcasts can be picked up by any service node, so xCAT
  will set up identical DHCP configuration for ALL nodes on every service
  node so that any one of them can respond to the initial DHCP request, and
  then have the "next-server" value set to the correct service node for
  that compute node for subsequent deployment data requests.

  Linda

  Inactive hide details for Dave Barry ---10/11/2011 01:22:50 PM---Just
  curious, I noticed that even when a compute node is set tDave Barry
  ---10/11/2011 01:22:50 PM---Just curious, I noticed that even when a
  compute node is set to only use, for example, "service01" a

  From: Dave Barry <[email protected]>
  To: xCAT Users Mailing list <[email protected]>
  Date: 10/11/2011 01:22 PM
  Subject: [xcat-user] Why are service nodes sent commands for *all* nodes?




  Just curious, I noticed that even when a compute node is set to only use,
  for example, "service01" as their service node, the other service nodes
  still seem to be sent commands for that node.

  Example:

  [root@mn ~]# lsdef c1n01
  Object name: c1n01
      arch=x86_64
      bmc=c1n01-bmc
      bmcport=0
      chain=runcmd=standby
      currchain=boot
      currstate=netboot centos5.5-x86_64-compute
      groups=compute,all,ipmi
      initrd=xcat/netboot/centos5.5/x86_64/compute/initrd-stateless.gz
      installnic=eth0
      interface=eth0
      ip=192.168.1.2

  
kcmdline=imgurl=http://!myipfn!/install/netboot/centos5.5/x86_64/compute/rootimg.gz
 XCAT=!myipfn!:3001 ifname=eth0:00:50:56:11:11:15 netdev=eth0
      kernel=xcat/netboot/centos5.5/x86_64/compute/kernel
      mac=00:50:56:11:11:15
      mgt=ipmi
      netboot=pxe
      nfsserver=mn
      nodetype=osi
      ondiscover=nodediscover
      os=centos5.5
      postbootscripts=otherpkgs
      postscripts=updaterepos.sh,syslog,remoteshell,syncfiles
      power=ipmi
      primarynic=eth0
      profile=compute
      provmethod=netboot
      servicenode=service01
      status=booted
      statustime=10-11-2011 12:13:27

  [root@mn ~]# nodeset c1n01 netboot
  Error: Unable to dispatch hierarchical sub-command to service02:3001.
  This service node may be down or its xcatd daemon may not be responding.
  c1n01: netboot centos5.5-x86_64-compute


  As you can see, c1n01 has "service01" only as its service node, but the
  management node is still trying to talk to service02 about this command.
  Is this expected behavior, or have I misconfigured something?


  Thanks!
  ------------------------------------------------------------------------------

  All the data continuously generated in your IT infrastructure contains a
  definitive record of customers, application performance, security
  threats, fraudulent activity and more. Splunk takes this data and makes
  sense of it. Business sense. IT sense. Common sense.
  http://p.sf.net/sfu/splunk-d2d-oct
  _______________________________________________
  xCAT-user mailing list
  [email protected]
  https://lists.sourceforge.net/lists/listinfo/xcat-user


  ------------------------------------------------------------------------------

  All the data continuously generated in your IT infrastructure contains a
  definitive record of customers, application performance, security
  threats, fraudulent activity and more. Splunk takes this data and makes
  sense of it. Business sense. IT sense. Common sense.
  http://p.sf.net/sfu/splunk-d2d-oct
  _______________________________________________
  xCAT-user mailing list
  [email protected]
  https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------

All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

<<inline: graycol.gif>>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to