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";;
} elsif option user-class-identifier = "xNBA" and option
client-architecture = 00:09 {
supersede server.filename =
"http://${next-server}/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 <[email protected]>
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 <(757)%20289-9872>
>
>
>
> *From:* Imam Toufique [mailto:[email protected]]
> *Sent:* Tuesday, October 24, 2017 1:28 PM
> *To:* xCAT Users Mailing list <[email protected]>
> *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/
>
>
>
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
--
Regards,
*Imam Toufique*
*213-700-5485*
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
