Thank you, that information is very useful. I just realized that I have an older version of xCAT (2.7.3) and need to upgrade to get those commands for node discovery. I will do that soon.
Also when I did a 'nodeset' on one of the service nodes I saw an error, as if xcat were already trying to delegate commands to service nodes that aren't even provisioned yet. I'm pretty sure it would do this regardless of what node I tried to nodeset. What I can't tell is whether the command was successful or not, despite the errors saying that it can't reach the service node daemons. Here is what I got: [root@x3650-head01 ~]# nodeset xcat-serv1 Error: Unable to dispatch hierarchical sub-command to xcat-serv1:3001. This service node may be down or its xcatd daemon may not be responding. Error: Unable to dispatch hierarchical sub-command to xcat-serv2:3001. This service node may be down or its xcatd daemon may not be responding. That is very odd since this presents a chicken-and-egg problem if the nodeset is not working (the nodes can't be required to be present before they are provisioned). I followed the xCAT guide to fully define the service nodes in the xCAT tables first, but it appears something in the tables is making xCAT think that the service nodes are/should be up already. Can I ignore this or is nodeset not going to work until I fix this somehow? Maybe this will be fixed by upgrading xCAT though. -Josh On Sun, Jan 12, 2014 at 8:29 PM, Xiao Peng Wang <[email protected]> wrote: > You saw the discovery message was because of the node configuration was > not finished yet. After running 'nodeset' and start the node deployment, > the discovery message won't show again. > > Regarding the discovery, you can use 'sequential discovery' to discover > virtual node. Refer to: > https://sourceforge.net/apps/mediawiki/xcat/index.php?title=XCAT_iDataPlex_Cluster_Quick_Start#Option_1:_Sequential_Discovery > Another easy manual method is: > > You can check the undiscovered node by command: 'nodediscoverls -t > all' (Any nodes which is sending discovery request will be recorded in > discoverydata table and can be dispalyed by nodediscoverls command). And > run 'nodediscoverdef' to define the undiscovered node to a node definition > in xCAT db. > > See examples: > # nodediscoverls -t all > UUID NODE METHOD > MTM SERIAL > 643CC79B-B7BD-224F-8105-9AEF8329E195 undef undef > 9AA99E16 > > # nodediscoverls -t all -l > Object uuid: 643CC79B-B7BD-224F-8105-9AEF8329E195 > method=undef > discoverytime=01-13-2014 01:14:28 > arch=x86_64 > cpucount=2 > cputype=Intel Core 2 Duo P9xxx (Penryn Class Core 2) > memory=3770188 > serial=9AA99E16-BAAA-11E1-B9E3-3440B5E0E828_34:40:B5:E0:E8:28 > nicdriver=eth0!e1000 > nicipv4=eth0!10.1.100.114/16 > nichwaddr=eth0!00:1A:4A:01:00:5D > nicpci=eth0!0000:00:03.0 > > Thanks > Best Regards > ---------------------------------------------------------------------- > Wang Xiaopeng (王晓朋) > IBM China System Technology Laboratory > Tel: 86-10-82453455 > Email: [email protected] > Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, > Haidian District Beijing P.R.China 100193 > > [image: Inactive hide details for Josh Nielsen ---2014/01/11 08:09:31---I > tried the manual insertion of the MAC address and I was able]Josh Nielsen > ---2014/01/11 08:09:31---I tried the manual insertion of the MAC address > and I was able to get a DHCP lease for the VM (IP 10 > > From: Josh Nielsen <[email protected]> > To: xCAT Users Mailing list <[email protected]>, > Date: 2014/01/11 08:09 > Subject: Re: [xcat-user] Node discovery for VMs in VMWare > ------------------------------ > > > > I tried the manual insertion of the MAC address and I was able to get a > DHCP lease for the VM (IP 10.20.240.254) but for some reason it just kept > saying it was processing the discovery request like this over and over > again: > > Jan 10 17:45:11 x3650-head01 xCAT: xcatd: Processing discovery request > from 10.20.240.254 > Jan 10 23:45:14 10.20.240.254 (none) dhclient[310]: XMT: Solicit on eth0, > interval 125010ms. > Jan 10 17:45:16 x3650-head01 xCAT: xcatd: Processing discovery request > from 10.20.240.254 > Jan 10 23:45:17 10.20.240.254 (none) dhclient[321]: XMT: Solicit on eth1, > interval 112560ms. > Jan 10 17:45:21 x3650-head01 xCAT: xcatd: Processing discovery request > from 10.20.240.254 > Jan 10 17:45:36 x3650-head01 last message repeated 3 times > > I'll have to debug this more after the weekend. > > -Josh > > > > On Fri, Jan 10, 2014 at 3:22 PM, Josh Nielsen > <*[email protected]*<[email protected]>> > wrote: > > Hello all, > > I would like to provision some new nodes in my xCAT cluster inside > VMWare but I just realized that the way xCAT has identified and discovered > my nodes in the past has been by dedicated physical port numbers on the > switches as defined in the xCAT switch database table. That is not a > problem for physical nodes which have a single cable going into a port on a > switch dedicated only to that node. > > For example one of my nodes has this entry in the switch table: > > #node,switch,port,vlan,interface,comments,disable > "hinode","bnt01","44","1","eth0","bnt01:p44" > > This tells xCAT that the node found connected to port 44 on switch > bnt01 can be identified as node "hinode". With a VMWare cluster however a > VM may reside on many ports (in my case I have 3 ESX servers - and 3 > corresponding cables to the switch - which the VM may be on) at any given > time, depending on which VMWare host it is running on. And on top of that > the network connection is trunked so that every VM running on each ESX host > goes through the same network port. > > Has anyone provisioned nodes in VMWare before with xCAT? And if there > is not a way to do this automatically by the switch/port associations, is > there another manual way that I can discover the node? Would manually > inserting the node's MAC address into the xCAT 'mac' table work, or is more > than that required for (auto)discovery? > > Thanks, > Josh Nielsen > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user > >
<<graycol.gif>>
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
