I'm not following your network layout real well with the text you provided, however there's a networks.tftpserver for each network definition that you can change. Set the tftpserver definition for each network to the correct IP you need it to return back to the client.
On 7/26/2015 12:19 PM, Russell Auld wrote: > Yes, setting site.dhcpinterfaces="bond0,!remote!" worked! > > Thank you. It places the subnets in the global scope, which is the right > thing to do. > > However, in our current configuration, I am wrapping the subnets in the bond0 > shared network so that the server IP returned to the DHCP client is the > public facing address. > When the subnets are in the global scope, the DHCP server returns the private > IP of the MN. Then the tftp doesn't work. > There's probably a way to get it to return the correct address. > > On Jul 26, 2015 10:31 AM, Russell Jones <[email protected]> wrote: >> I don't recall if this is required or not, and I am not able to login to a >> system right now to verify, however try adding !remote! to >> site.dhcpinterfaces and see if your remote VLAN shows up when you do a >> makedhcp -n >> >> >> On 7/25/2015 2:11 PM, Russell Auld wrote: >> >> I added definitions to the networks table that identify separate VLANs in >> our environment. >> >> When I run makedhcp -n’ it appears that only the subnets that the MN’s >> interface are attached to get created. >> >> The MN is a on routable VLAN 10.10.10.0/24. The MN is also connected to >> another local, private LAN 172.132.10.0/24 (used for BMCs). The node talks >> to both via bond0. >> >> Another set of nodes are on a different routable VLAN, 10.10.20.0/24. >> >> The networks table contains definitions for all three. I set >> networks.mgtifname to !remote! for the 10.10.20.0/24 VLAN. >> >> For the other two, I set it to bond0. >> >> When I run makedhcp -n, the dhcpd.conf file only contains two subnets, the >> two that are connected to the MN. >> >> I want the dhcp server on the MN to serve IPs to the 10.10.20.0/24 VLAN for >> the provisioning of stateful nodes. >> >> The switch managing the VLANs is configured to forward the DHCP requests >> from the 20 VLAN to the 10VLAN. >> >> It won’t do that if there isn’t a subnet definition for that network >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> >> xCAT-user mailing list >> >> [email protected] >> >> https://lists.sourceforge.net/lists/listinfo/xcat-user >> >> > ------------------------------------------------------------------------------ > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
