Building on this, if you are not running discovery for any nodes in this
cluster, you can remove or disable the following lines in the chain table:
"ipmi",,,"runcmd=bmcsetup,shell","nodediscover",,
"blade",,,"standby","nodediscover",,
Adding a “1” to the end of each line will disable it. I’m not sure if that will
stop xCAT from attempting to discover nodes, or if there’s a way to just have
any unknown nodes boot to the genesis shell. Possibly an entry like:
“compute”,,,”shell”,”nodediscover”,,
You could also possibly do manual discovery using the nodediscover command. I
have not used this method, but my understanding is that you basically tell xCAT
to expect a PXE request from n02, so it will assume the next MAC that pings the
DHCP server is n02. Again, if chain is not configured to run bmcsetup (a la my
example above), it should just run nodediscover and drop you to the genesis
shell prompt on the node.
The chain table “Controls what operations are done (and it what order) when a
node is discovered and deployed.” See the “man chain” for details, but this is
one of the areas that dictates how the DHCP server responds to PXE requests.
You control what is served to PXE clients using the nodeset command.
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872
From: Er Tao Zhao [mailto:erta...@cn.ibm.com]
Sent: Wednesday, October 25, 2017 3:58 AM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] How to disable BMC discovery
Hi, Imam
Have you assign IP address for n02?
Pls follow the steps below to install OS.
1. chdef n02 ip=x.x.x.x
2. makehosts n02
makedns n02 ==> To generate nodename/IP mapping.
3. nodeset n02 osimage=centos6.9-x86_64-install-compute ==> 1. generate the
IP/Mac of n02 mapping(DHCP lease entry) internally
2. generate boot configuration file
3. generate kickstart configuration file.
Then, pls reboot your compute node.
Feel free to let me know if there is any more issue. Thx!
Best Regards,
-----------------------------------
Zhao Er Tao
IBM China System and Technology Laboratory, Beijing
Tel:(86-10)82450485
Email: erta...@cn.ibm.com<mailto:erta...@cn.ibm.com>
Address: 1/F, 28 Building,ZhongGuanCun Software Park,
No.8 DongBeiWang West Road, Haidian District,
Beijing, 100193, P.R.China
----- Original message -----
From: Imam Toufique <techie...@gmail.com<mailto:techie...@gmail.com>>
To: xCAT Users Mailing list
<xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>>
Cc:
Subject: Re: [xcat-user] How to disable BMC discovery
Date: Wed, Oct 25, 2017 12:25 PM
Hi Christian (and everyone in this list),
My apology for the long post here.
the dump on the chain table is:
[root@xcatmaster xcat]# tabdump chain
#node,currstate,currchain,chain,ondiscover,comments,disable
"ipmi",,,"runcmd=bmcsetup,shell","nodediscover",,
"blade",,,"standby","nodediscover",,
"n03",,,,,,
"n01","install centos6.9-x86_64-compute","boot",,,,
what is the chain table do?
So, I noticed that when I add a node and i power it up (these nodes have no BMC
), get the following output in the screen:
Oct 24 10:17:41 10.1.1.63 (none) xcat.genesis.dodiscovery: Couldn't find MTM
information in FRU, falling back to DMI (MTMS-based discovery may fail)
Oct 24 10:17:41 10.1.1.63 (none) xcat.genesis.dodiscovery: Beginning echo
information to discovery packet file...
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Discovery packet
file is ready.
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Sending the
discovery packet to xCAT (10.1.1.20:3001)...
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Sleeping 5
seconds...
Then, when I do nodediscoverls , i get this:
[root@xcatmaster xcat]# nodediscoverls -t undef
UUID NODE METHOD
MTM SERIAL
4C4C4544-0059-3410-8048-C3C04F4D4E31 undef undef
Dell Inc:OptiPlex 980 CY4HMN1
then, when I define the node, with:
> nodediscoverdef -u <uuid> -n <node>
then I see in the log:
Oct 24 18:50:37 n06 xcat.genesis.doxcat: Received request=standby, will call
xCAT back in 30 seconds. Discovery is complete, run nodeset on this node to
provision an Operating System
what nodeset command am I supposed to run for the node? is it, 'nodeset
<nodename> osimage?
I have another issue about renaming a node. So, I had a node built with node
name 'n02'. and I wanted to see how xcat worked for a node name changeover.
So, here is my scenario. node 'n2' is renamed with 'n6'. I did this with the
'noderm' command. and then I added the same system with node name 'n6'. node
n2 had an IP address of 10.1.1.61 . with the same MAC address when I set the
new node IP addr to 10.1.1.125, it looks like xcat discovery process still
refers to the MAC address with it old associated IP address(?)
see below:
Oct 24 18:19:34 xcatmaster xcat[1748]: xcatd: Processing discovery request from
10.1.1.61
Oct 24 18:19:34 xcatmaster xcat[1748]: xcat.discovery.zzzdiscovery: Notify
10.1.1.61 that its findme request has been processed
See below, the MAC address listed shows 2 IP addresses that had been assigned
before, they are all in the dhcpd.leases table, along with the newly assigned
IP address for the MAC address.
MAC addr 84:2b:2b:a7:80:46 , old IP assignments:
lease 10.1.1.61 {
starts 3 2017/10/25 01:12:17;
ends 3 2017/10/25 01:19:39;
tstp 3 2017/10/25 01:19:39;
cltt 3 2017/10/25 01:12:17;
binding state free;
hardware ethernet 84:2b:2b:a7:80:46;
}
lease 10.1.1.60 {
starts 3 2017/10/25 01:31:15;
ends 3 2017/10/25 01:34:07;
tstp 3 2017/10/25 01:34:07;
cltt 3 2017/10/25 01:31:15;
binding state free;
hardware ethernet 84:2b:2b:a7:80:46;
uid "\001\204++\247\200F";
}
MAC addr 84:2b:2b:a7:80:46, old IP assignments:
host n06 {
dynamic;
hardware ethernet 84:2b:2b:a7:80:46;
fixed-address 10.1.1.125;
supersede server.ddns-hostname = "n06";
supersede host-name = "n06";
if option user-class-identifier = "xNBA" and option client-architecture
= 00:00 {
supersede server.always-broadcast = 01;
supersede server.filename =
"http://${next-server}/tftpboot/xcat/xnba/nodes/n06<http://$%7bnext-server%7d/tftpboot/xcat/xnba/nodes/n06>";
} elsif option user-class-identifier = "xNBA" and option
client-architecture = 00:09 {
supersede server.filename =
"http://${next-server}/tftpboot/xcat/xnba/nodes/n06.uefi<http://$%7bnext-server%7d/tftpboot/xcat/xnba/nodes/n06.uefi>";
} elsif option client-architecture = 00:07 {
supersede server.filename = "xcat/xnba.efi";
} elsif option client-architecture = 00:00 {
supersede server.filename = "xcat/xnba.kpxe";
} else {
supersede server.filename = "";
}
}
So, it looks like node rename ( deleting the node + adding the node with a new
name and new IP ) ) did not work. what is the preferred method of cleaning up
a node information in its entirety? Should this dhcpd.leases file not be
refreshed automatically when 'makedhcp -n' and 'makedns -n' command is run
after removing and adding a node?
I have a small cluster that i support, all I want is add a node in xcat , set
up it's IP address statically and image the node with centOS
Sorry for the long post, but I am stuck with this issue. Please give me a hand
with this.
thanks.
On Tue, Oct 24, 2017 at 2:18 PM, Christian Caruthers
<ccaruth...@lenovo.com<mailto:ccaruth...@lenovo.com>> wrote:
What is the output of ‘nodeset n02 stat’? Also, what is the contents of the
chain table (tabdump chain)?
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872<tel:(757)%20289-9872>
From: Imam Toufique [mailto:techie...@gmail.com<mailto:techie...@gmail.com>]
Sent: Tuesday, October 24, 2017 1:28 PM
To: xCAT Users Mailing list
<xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>>
Subject: [xcat-user] How to disable BMC discovery
Hello everyone,
We are trying to test xcat out in our cluster and I need some help.
Here is the issue I have:
I have followed the following document to setup the environment:
https://sourceforge.net/p/xcat/wiki/XCAT_iDataPlex_Cluster_Quick_Start/<https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_xcat_wiki_XCAT-5FiDataPlex-5FCluster-5FQuick-5FStart_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=GXZJILRYuh625D1P_w_8vxyNDAEGDWoFmPVwQ0NBUcY&m=-3-86HzaadL7aUaNa7hrA3p3heUgsDt_S_MFmzvCRDE&s=9DnWihJJaGatnovAFdPEdyBW-IQaSe0sv6MuXFawpWc&e=>
I added my first node manually, as I did not want auto discovery. Here is my
[root@xcatmaster xcat]# lsdef n02
Object name: n02
arch=x86_64
groups=compute
installnic=mac
mac=00:24:E8:36:AD:95
netboot=xnba
os=centos6.9
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
primarynic=mac
profile=compute
provmethod=centos6.9-x86_64-install-compute
The node above does not have BMC, it is a standard PC. when I power on the
node, i see the following messages in syslog:
Oct 24 10:16:20 10.1.1.61 (none) xcat.genesis.dodiscovery: Beginning echo
information to discovery packet file...
Oct 24 10:16:20 10.1.1.61 (none) xcat.genesis.dodiscovery: Discovery packet
file is ready.
Oct 24 10:16:20 10.1.1.61 (none) xcat.genesis.dodiscovery: Sending the
discovery packet to xCAT (10.1.1.20:3001)...
Oct 24 10:16:20 10.1.1.61 (none) xcat.genesis.dodiscovery: Sleeping 5
seconds...
Oct 24 10:16:21 10.1.1.63 (none) xcat.genesis.dodiscovery: Couldn't find MTM
information in FRU, falling back to DMI (MTMS-based discovery may fail)
Oct 24 10:16:21 10.1.1.63 (none) xcat.genesis.dodiscovery: Beginning echo
information to discovery packet file...
^C
[root@xcatmaster xcat]# tail -f computes.log
Oct 24 10:17:41 10.1.1.63 (none) xcat.genesis.dodiscovery: Couldn't find MTM
information in FRU, falling back to DMI (MTMS-based discovery may fail)
Oct 24 10:17:41 10.1.1.63 (none) xcat.genesis.dodiscovery: Beginning echo
information to discovery packet file...
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Discovery packet
file is ready.
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Sending the
discovery packet to xCAT (10.1.1.20:3001)...
Oct 24 10:17:42 10.1.1.63 (none) xcat.genesis.dodiscovery: Sleeping 5
seconds...
I think it is trying to look for BMC and not finding it, therefore, it just
keep looking for it? I am no expert in xcat, but is there a way to disable BMC
discovery in xcat for nodes that do not have BMC?
Please help, I need to get this thing up and going.
Thanks a lot!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_xcat-2Duser&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=GXZJILRYuh625D1P_w_8vxyNDAEGDWoFmPVwQ0NBUcY&m=-3-86HzaadL7aUaNa7hrA3p3heUgsDt_S_MFmzvCRDE&s=OVcHJfOOC5KyRtuC-TNuzmRgEdUWKi92Xdu2sU2DKBE&e=>
--
Regards,
Imam Toufique
213-700-5485
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=GXZJILRYuh625D1P_w_8vxyNDAEGDWoFmPVwQ0NBUcY&m=-3-86HzaadL7aUaNa7hrA3p3heUgsDt_S_MFmzvCRDE&s=NZaKnwH52y7HyXj-fELHQNADYOHxkNyZhQbnIOemIgA&e=
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_xcat-2Duser&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=GXZJILRYuh625D1P_w_8vxyNDAEGDWoFmPVwQ0NBUcY&m=-3-86HzaadL7aUaNa7hrA3p3heUgsDt_S_MFmzvCRDE&s=OVcHJfOOC5KyRtuC-TNuzmRgEdUWKi92Xdu2sU2DKBE&e=
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
