So, I'm still kinda new to sys-admining (I've been doing devops stuff in CentOS for about a year and a half at my company), but we have a setup at my work that I think you might find relevant to your issue.
At work, we have a Production network that is served by the PXE menu. It exists in a different subnet than the rest of the computers on other networks, and getting the other machines to talk to that PXE server requires setting up routes between the different subnets. We haven't actually done this yet (people are lazy), but I know that's what we'll have to do to make it accessible. I don't think there's a way to do what you're trying to do - if I understand correctly (and correct me if I'm wrong), your PXE menus are not being generated with the proper IP for your 10.13.200.XXX subnet systems to reach the files they need. If that's the case, the way I see it you have two options: - Make a set of sub-menus for your "gc.sv.domain.net" network and hard code it in to your pxelinux.default template with the correct IP, 10.13.200.101 - Find some way for your systems in the 10.13.200.XXX subnet to route to 10.13.5.100 If there's a cobbler wizard out there who knows how to manage PXE menus better than I do, I'd love to hear about it - at my work, I have to keep all the PXE menus in a git repo and deploy them every time I make a change because Cobbler is not very good at PXE sub-menu management. Or at least I couldn't figure out how to use it very effectively. I can provide more details about that setup if someone would like to know them. On Sat, Apr 30, 2016 at 8:21 PM, Tory M Blue <[email protected]> wrote: > So I'm running into some issues and I'm sure it's a minor brain fart > on my part. But the documentation has not squared me away. > > I have a cobbler server running DHCP for 3 networks, my cobbler > server has 3 interfaces and I have 3 dhcp stanzas (whatever). > > I can set a different next server, which is the interface IP on that > subnet/vlan. No issue. I can build a system from the 10.13.4 network > just fine. But if I try to build from the 10.13.200 net, I can get a > dhcp address, load the kernel, but the issue is the Distro has the IP > address from the 10.13.4.x network in it so the pxelinux.cfg/default > has the wrong subnet/vlan hardcoded; and thus tries to load the > kickstart > > LABEL CentOS7-x86_64_Standard > kernel /images/CentOS7-x86_64/vmlinuz > MENU LABEL CentOS7-x86_64_Standard > append initrd=/images/CentOS7-x86_64/initrd.img ksdevice lang= > kssendmac text > ks=http://10.13.4.101/cblr/svc/op/ks/profile/CentOS7-x86_64_Standard > ipappend 2 > > So obviously if a host is on the 10.13.200 net, receives a 10.13.200.x > address, and starts booting, cobbler is sending it that kickstart line > and it should not be going to 10.13.4.101 when the local network is > ready to receive at 10.13.200.101. > > The metadata tree has the 10.13.4.101 address, and I thought about > setting it to $next_server, but it seems if I do it in the profile via > cobbler_web, it over writes the default file with 10.13.4.101 (the > cobbler host server IP) > > I've removed $next-server from the cobbler settings file > > #next_server: 10.13.4.101 > > But server is still configured. > > server: 10.13.4.101 > > So the issue is really the server configuration inside settings. it > mentions --server-override, but I don't want to have a handful of > profiles for the same image.. I would like to just boot up a server > and say use Profile-CentOS-standard and ignore which network it's > coming from., want wildcards or other to figure things out. > > Any ideas? really i've been searching and "nothing" I've found has > made me understand where I'm falling short. -dhcp-tags, > --server-override > > Thanks > tory > > > ################## DHCP ############ > ddns-update-style interim; > > allow booting; > allow bootp; > > ignore client-updates; > set vendorclass = option vendor-class-identifier; > > subnet 10.13.4.0 netmask 255.255.255.0 { > option routers 10.13.4.6; > option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102; > option domain-name "eng.domain.net"; > option subnet-mask 255.255.255.0; > range dynamic-bootp 10.13.4.75 10.13.4.99; > filename "/pxelinux.0"; > default-lease-time 21600; > max-lease-time 43200; > next-server 10.13.4.101; > } > > subnet 10.13.5.0 netmask 255.255.255.0 { > option routers 10.13.5.6; > option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102; > option domain-name "eng.domain.net"; > option subnet-mask 255.255.255.0; > range dynamic-bootp 10.13.5.220 10.13.5.239; > filename "/pxelinux.0"; > default-lease-time 21600; > max-lease-time 43200; > next-server 10.13.5.100; > } > > subnet 10.13.200.0 netmask 255.255.255.0 { > option routers 10.13.200.6; > option domain-name-servers 216.249.24.15, 10.13.6.56; > option domain-name "gc.sv.domain.net"; > option subnet-mask 255.255.255.0; > range dynamic-bootp 10.13.200.75 10.13.200.85; > filename "/pxelinux.0"; > default-lease-time 21600; > max-lease-time 43200; > next-server 10.13.200.101; > } > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/admin/lists/[email protected] >
_______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/admin/lists/[email protected]
