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



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

<<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