BTW. If, in fact, "discover" is not a valid chain value, and happens
automatically whenever there is no mac address, then the "chain" attribute
description on the "chain" man page is not up to date.
Thanks
_____________________________________________
From: Pocina, Goran
Sent: Wednesday, March 27, 2013 4:04 PM
To: 'xCAT Users Mailing list'
Subject: RE: "Unrecognized directive" during auto-discovery.
Ok, I think I see what the problem is: the "discover" destiny does not seem
to be valid. If instead of chain="discover,runcmd=bmcsetup,install,boot", we
use:
Chain="runcmd=bmcsetup,install,boot", and delete the mac address, dhcpd entry,
etc., then discovery proceeds as expected.
Thanks.
On a related note, is there any documentation for the new workflow the new
"nodeset" command? Lots of things now have to be manually, like creating
"osimage" table entries. This is especially true when new profile types are
created.
Our system has been running a while under 2.7 so we have example table entries
that were created before the nodeset changes, and can figure out by example
what's needed, but it would be difficult for a new user.
_____________________________________________
From: Pocina, Goran
Sent: Wednesday, March 27, 2013 2:14 PM
To: 'xCAT Users Mailing list'
Subject: RE: "Unrecognized directive" during auto-discovery.
If the node name in the xcat tables is changed from the short name, to the fqdn
(labcm0005.nyc.desres.deshaw.com), the "unrecognized directive" and "dhclient"
messages disappear from the console, but the looping otherwise continues.
See below for corresponding output..
I wonder if xcatdebug can be used to pinpoint the problem? I tried running it
with call trace and comments enabled, but it produced so much information it's
hard to spot what's significant.
Thanks
Console
. . .
Beginning node discovery process
No link detected on eth1
Waiting on nics to get addresses
eth0|149.77.53.153
Network configuration complete, commencing transmit of discovery
packets
Done waiting
Beginning node discovery process
No link detected on eth1
Waiting on nics to get addresses
eth0|149.77.53.153
Network configuration complete, commencing transmit of discovery
packets
Done waiting
Log
. . .
Mar 27 14:04:23 drdkvm0003 xCAT node discovery:
labcm0005.nyc.desres.deshaw.com has been discovered
Mar 27 14:04:27 drdkvm0003 dhcpd: DHCPRELEASE of 149.77.53.205 from
00:25:90:a2:9f:54 via eth0 (not found)
Mar 27 14:04:30 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 14:04:30 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 14:04:30 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.205
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 14:04:30 drdkvm0003 dhcpd: DHCPACK on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 14:04:47 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from labcm0005
Mar 27 14:04:59 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.205
Mar 27 14:05:00 drdkvm0003 xCAT node discovery:
labcm0005.nyc.desres.deshaw.com has been discovered
Mar 27 14:05:04 drdkvm0003 dhcpd: DHCPRELEASE of 149.77.53.205 from
00:25:90:a2:9f:54 via eth0 (not found)
Mar 27 14:05:04 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 14:05:04 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 14:05:04 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.205
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 14:05:04 drdkvm0003 dhcpd: DHCPACK on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 14:05:24 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from labcm0005
Mar 27 14:05:36 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.205
. . .
_____________________________________________
From: Pocina, Goran
Sent: Wednesday, March 27, 2013 10:00 AM
To: 'xCAT Users Mailing list'
Subject: "Unrecognized directive" during auto-discovery.
Discovery appears to work, the mac is discovered, the DHCP entry is created,
and the genesis dhclient gets the new MAC address, but then it keeps looping in
discovery, with the console displaying an "unrecognized directive
<error>unknown" message. If I run: "chdef labcm0005 curstate=<some state
other than discover>", then discovery ends. The only thing that's changed is
that since 2.8.0, whe're no longer using "nodeset host discover", but setting
the chain manually.
Thanks
Details:
We used to be able to run the following to initiate node discovery before 2.8.0:
rmnodecfg host
nodeset host discover
(BTW: the rmnodecfg should delete the dhcp entry BEFORE deleting the MAC
address from the xCAT table. Here's a diff to make it work.)
[root@drdkvm0003 bin]# diff rmnodecfg.old rmnodecfg.new
33c33
< $cmd = "chtab -d node=$blade mac";
---
> $cmd = "makedhcp -d $blade";
36c36
< $cmd = "makedhcp -d $blade";
---
> $cmd = "chtab -d node=$blade mac";
Now "nodeset ... discover" provides the error:
[root@drdkvm0003 xcat]# nodeset labcm0005 discover
Error: Unknown state discover requested
If the chain is set up manually as follows, discovery starts to happen, and
seems to work, but never ends:
[root@drdkvm0003 xcat]# chdef labcm0005
chain="discover,runcmd=bmcsetup,install,boot" ondiscover=nodediscover
The discovery process initiates, the node gets a dynamic address and
communicates back, the mac address is discovered, a correct DHCP lease is
created, and it gets its assigned IP and hostname (not dynamic.). However it
never recognizes that discovery was successful and complains about
"Unrecognised directive"
Here's the console output:
Aquiring network addresses..Aquired IPv4 address on eth0:
149.77.53.153/23 (this is a dynamic address)
Beginning node discovery process
No link detected on eth1
Waiting on nics to get addresses
eth0|149.77.53.153
Network configuration complete, commencing transmit of discovery
packets
Done waiting
/bin/doxcat: line 178: 684 Terminated dhclient -6 -pf
/var/run/dhclient6.$bootnic.pid $bootnic -lf /var/lib/dhclient6.leases
/bin/doxcat: line 178: 684 Terminated dhclient -cf
/var/run/dhclient.conf -6 -pf /var/run/dhclient6.$nic.pid -lf
var/lib/dhclient/dhclient6.leases $nic
^\/bin/getdestiny: line 25: 3260 Quit sleep 1
^\/bin/getdestiny: line 25: 3266 Quit sleep 1
Retrying in 16 seconds
...
Done waiting
Unrecognised directive <error>Unknown
Beginning node discovery process
No link detected on eth1
Waiting for nics to get addresses
eth0|149.77.53.205 (this is the correct, discovered address, not
dynamic.)
Network configuration complete, commencing transmit of discovery
packets
Done waiting
... keeps repeating ...
The system log is below. The key data is:
Labcm0005 - node being discovered
149.77.53.153 - dynamic address assigned
149.77.53.205 - permanent IP address
00:25:90:a2:9f:54 - MAC address of eth0
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: USB disconnect, device
number 61
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: new high speed USB device
number 62 using ehci_hcd
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: New USB device found,
idVendor=03eb, idProduct=0002
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: Product: anton2_bc
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: Manufacturer: desres
Mar 27 08:21:58 labcm0005 kernel: usb 2-1.1: SerialNumber: cage0-slot0
Mar 27 08:29:23 drdkvm0003 xCAT: xCAT: Allowing lsdef labcm0005 for root
from localhost.localdomain
Mar 27 08:29:50 drdkvm0003 xCAT: xCAT: Allowing nodels to labcm0005 for
root from localhost.localdomain
Mar 27 08:29:53 drdkvm0003 xCAT: xCAT: Allowing makedhcp to labcm0005 -d
for root from localhost.localdomain
Mar 27 08:29:53 drdkvm0003 dhcpd: Wrote 0 class decls to leases file.
Mar 27 08:29:53 drdkvm0003 dhcpd: Wrote 0 deleted host decls to leases
file.
Mar 27 08:29:53 drdkvm0003 dhcpd: Wrote 0 new dynamic host decls to
leases file.
Mar 27 08:29:53 drdkvm0003 dhcpd: Wrote 20 leases to leases file.
Mar 27 08:30:14 drdkvm0003 xCAT: xCAT: Allowing nodeset to labcm0005
discover for root from localhost.localdomain
Mar 27 08:32:38 drdkvm0003 xCAT: xCAT: Allowing chdef labcm0005
chain=discover,runcmd=bmcsetup,install,boot ondiscover=nodediscover for root
from localhost.localdomain
Mar 27 08:33:51 drdkvm0003 xCAT: xCAT: Allowing rsetboot to labcm0005 net
for root from localhost.localdomain
Mar 27 08:34:01 drdkvm0003 xCAT: xCAT: Allowing rpower to labcm0005
status for root from localhost.localdomain
Mar 27 08:34:06 drdkvm0003 xCAT: xCAT: Allowing rpower to labcm0005 boot
for root from localhost.localdomain
<test node just rebooted - discovery begins>
Mar 27 08:34:50 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:34:51 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.152 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.152
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPACK on 149.77.53.152 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:34:52 drdkvm0003 xinetd[5682]: START: tftp pid=29586
from=149.77.53.152
Mar 27 08:34:52 drdkvm0003 in.tftpd[29587]: RRQ from 149.77.53.152
filename xcat/xnba.kpxe
Mar 27 08:34:52 drdkvm0003 in.tftpd[29587]: tftp: client does not accept
options
Mar 27 08:34:52 drdkvm0003 in.tftpd[29588]: RRQ from 149.77.53.152
filename xcat/xnba.kpxe
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.152 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.152
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:34:52 drdkvm0003 dhcpd: DHCPACK on 149.77.53.152 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:35:03 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:35:04 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.153 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:35:04 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.153
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:35:04 drdkvm0003 dhcpd: DHCPACK on 149.77.53.153 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:35:04 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from drdn0026
Mar 27 08:35:16 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.153
Mar 27 08:35:19 drdkvm0003 xCAT node discovery: labcm0005 has been
discovered
Mar 27 08:35:21 drdkvm0003 dhcpd: DHCPRELEASE of 149.77.53.153 from
00:25:90:a2:9f:54 via eth0 (found)
Mar 27 08:35:25 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:35:25 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:35:25 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.205
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:35:25 drdkvm0003 dhcpd: DHCPACK on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:35:41 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from labcm0005
<discovery restarts!>
Mar 27 08:39:35 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.205
Mar 27 08:39:36 drdkvm0003 xCAT node discovery: labcm0005 has been
discovered
Mar 27 08:39:40 drdkvm0003 dhcpd: DHCPRELEASE of 149.77.53.205 from
00:25:90:a2:9f:54 via eth0 (not found)
Mar 27 08:39:43 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:39:43 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:39:43 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.205
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:39:43 drdkvm0003 dhcpd: DHCPACK on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:40:00 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from labcm0005
<discovery restarts!>
Mar 27 08:44:07 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.205
Mar 27 08:44:09 drdkvm0003 xCAT node discovery: labcm0005 has been
discovered
Mar 27 08:44:12 drdkvm0003 dhcpd: DHCPRELEASE of 149.77.53.205 from
00:25:90:a2:9f:54 via eth0 (not found)
Mar 27 08:44:12 drdkvm0003 dhcpd: DHCPDISCOVER from 00:25:90:a2:9f:54 via
eth0
Mar 27 08:44:12 drdkvm0003 dhcpd: DHCPOFFER on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:44:12 drdkvm0003 dhcpd: DHCPREQUEST for 149.77.53.205
(149.77.53.252) from 00:25:90:a2:9f:54 via eth0
Mar 27 08:44:12 drdkvm0003 dhcpd: DHCPACK on 149.77.53.205 to
00:25:90:a2:9f:54 via eth0
Mar 27 08:44:32 drdkvm0003 xCAT: xCAT: Allowing getcredentials x509cert
from labcm0005
<discovery restarts!>
Mar 27 08:46:54 drdkvm0003 xCAT: xcatd: Processing discovery request from
149.77.53.205
Here's the current state of the chain and mac tables:
[root@drdkvm0003 bin]# nodels labcm0005 chain
labcm0005: chain.ondiscover: nodediscover
labcm0005: chain.chain: discover,runcmd=bmcsetup,install,boot
labcm0005: chain.node: labcm0005
labcm0005: chain.currstate: discover
labcm0005: chain.currchain: runcmd=bmcsetup,install,boot
labcm0005: chain.comments:
labcm0005: chain.disable:
[root@drdkvm0003 bin]# nodels labcm0005 mac
labcm0005: mac.interface: eth0
labcm0005: mac.node: labcm0005
labcm0005: mac.mac: 00:25:90:a2:9f:54!labcm0005.nyc.desres.deshaw.com
labcm0005: mac.comments:
labcm0005: mac.disable:
Thanks
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
