Quoting Scott Henson <[email protected]>: > On Tue, 28 Jun 2011 15:01:50 +0100, [email protected] wrote: >> Quoting Owen Beckley <[email protected]>: >> >> >> >> >> I've got a need to deploy servers across multiple VLANs from the same >> >> cobbler server - is this possible? >> >> >> >> Ideally, I'd like to manage/build all servers from the same cobbler >> >> instance, however it would appear that cobbler only allows for the >> >> management on a single subnet (we're faced with one subnet on >> >> 192.168.x.x and another on 172.16.x.x :( ) >> >> >> >> Is this possible, or should I just drop DHCP management from cobbler >> >> (the servers are set to static IP after build), serve up a basic image >> >> using PXE and go from there? >> >> >> >> Kind regards, >> >> >> >> Matt >> > >> > There are a couple of ways to handle this. If the second subnet is >> > available locally, you could add a second interface to your cobbler >> > server and have it serve dhcp to both subnets directly. You should be >> > able to do this with either a physically separate interface or by VLAN >> > tagging your existing interface so it has both subnets on it. >> >> Thanks for the reply. >> >> This is how the server is currently configured, I'm having issues with >> the /etc/cobbler/settings file to get cobbler to manage the IP Ranges >> on both VLANS. >> >> Do you use cobbler to manage the DHCP server or do you do that by >> another method? > > In /etc/cobbler/settings you just have to tell it to manage dhcp. Then > you will want to add subnet definitions for each vlan in > /etc/cobbler/dhcp.template. Then do a cobbler sync and your dhcp server > should be able to answer dhcp requests for the subnets listed in > dhcp.template.
lol, that easy huh? Thanks, I'll try it out. M. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
