Thanks for the suggestion. The DHCP interfaces are indeed set in the site table. There are no service nodes in the equation (yet). The nodes respond properly to the MN, but it seems as though I'm missing the link between assigning the nodes fixed IPs and the nodes getting random IPs as they do now.
Will On 05/13/2015 10:21 AM, [email protected] wrote: > Date: Wed, 13 May 2015 10:12:08 -0400 > From: Ling Gao<[email protected]> > Subject: Re: [xcat-user] help with second domain > To: xCAT Users Mailing list<[email protected]> > Message-ID: > <ofe12832b4.08d6ac32-on87257e44.004d355f-85257e44.004e0...@us.ibm.com> > Content-Type: text/plain; charset="us-ascii" > > Hi Will, > Do you have "dhcpinterfaces" attribute defined in the site table. > Please make sure the interface on the the mn that's in the second domain > is in this attribute. > Did you run makedhcp -n after adding the second domain? > # makedhsp -n > # makedhcp -a > > Are there any service nodes in your cluster? > > dhcpinterfaces: The network interfaces DHCP should listen on. If it is > the same > for all nodes, use a simple comma-separated list of > NICs. To > specify different NICs for different nodes: > xcatmn|eth1,eth2;service|bond0. > In this example xcatmn is the name of the xCAT MN, and > DHCP there > should listen on eth1 and eth2. On all of the nodes in > group > 'service' DHCP should listen on the bond0 nic. > > In fact for xCAT mn, you do not have to put the name there if there are no > service nodes. Just "eth1,eth2". > > > Thanks, > > Ling > > Ling Gao > Poughkeepsie Unix Development Lab > IBM Systems and Technology Group > Internal: T/L 293-5692 > External:[email protected], 845-433-5692 > > "I never worry about the future. It comes soon enough." --- Albert > Einstein > > > > From: Will Robinson<[email protected]> > To:[email protected] > Date: 05/12/2015 09:40 PM > Subject: [xcat-user] help with second domain > > > > Hello, > > I'm trying to configure a second domain in xCAT. I have the interface > configured both with an IP and as a DHCP interface on the master node. > The networks table has been populated and the appropriate fixed IPs for > nodes in that domain have been added to the host file. All the nodes > have been added to the appropriate tables and the lsdef commands work as > expected, as does DNS. However, DHCP does not seedm as willing to > cooperate. The nodes are defined in the leases file without issue, but > there is never a fixed IP assigned to them (there is a dynamic range > defined for this network, but these nodes are not in that range). There > are also times when the MACs are defined in the leases file, but not > with the fixed IPs that are desired. The results seems to be a > discovery loop. makedhcp -q never responds with the appropriate > information. I've also tried defining the nodes in the hosts tables, > which isn't necessary for the default domain. I've also configured a > node for the default domain and everything works as it should. Any info > that will help me resolve this issue would be appreciated. Thanks. > > -- Will ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
