On Sun, May 1, 2016 at 11:53 AM, <alastair(a)alastair-munro.com> wrote:
Hi
We have multiple networks that we pxe boot off and have no problem with
fixed ip addresses being passed throught. Cobbler works on the server
override ip for each of the networks we pxe boot off, and this is passed
through as http_server, next server, etc. i can only conclude your cobbler
config is not setup correctly. basically you add a system, set ip settings
AND ip for the server override, and cobbler passes the server override ip
through to wherever its needed.
--
Alastair Munro
Thanks Alastair.
I'll repeat myself, I'm not really wanting to muck with the profiles.
I want a single profile (for each server class) that can be used from
X networks. Sure I can add server overrides and have x*3 profiles, vs
a single. This makes no sense. The DHCP has the right address in
next-server already, why cobbler can't use that value vs inserting
it's own and utilizing the "server" switch inside cobbler, is exactly
why you are creating multiple profiles, when in reality, I don't see
why you have to..
Yes it works but having to add these to duplicated profiles for each
attached network just doesn't seem like the right answer.
If it's the only answer then I guess it's not going to be a face palm.
But it seems simple enough that I just don't think anyone has ever
gotten the correct answer (many incomplete web posts, questions around
this). That's either because there really is no answer, you work
around the issue. But if DHCP has the information, why can't Cobbler
use it?
Also I'm not adding systems, so it's not a necessary step for me, a
server is unboxed and imaged.
Thanks for the response.
Tory