|
Greetings, I am trying to use cobbler for automated cent OS deployment.
we have a multi vlan ( about 5 vlans) network environment.
We do not have remote consoles to most of these servers so we cant see pre install server status or PXE boot status
how should be dhcp bootp services utilized ? should we need to have a dhcp server on each vlan/subnet ? Thanks | |||
|
feedback
|
|
Greetings! You need to have at least one DHCP server listening in each vlan, remember that vlans are logically separated and DHCP won't cross over magically, the easiest way to do this if it's temporary is to have one linux box with a switching trunk to all those 5 networks with 5 subinterfaces configured and one DHCP running them all, although the dhcp config will be a bit complicated it'll get all the work done. It's an interesting setup, let me know how it works | |||||||||
feedback
|
|
I'm doing this on our network. If your switch/router supports it, just relay the dhcp to the cobbler server with dhcp-agent or equivilent on the router. That way you don't have to have mulitple nic's etc on the cobbler server and make your life all confusing. Cobbler's default setup should do the rest once you have things up and running. Although you may have to setup a stub zone for the network for dhcp only clients if you haven't pre-populated the mac addresses of your machines. | |||
|
feedback
|
