I have cobbler managing dhcpd and the pxe booting worked fine on each of my configured VLANS. I recently changed the IP range of two of my VLANs and then modified the dhcp.template followed by a cobbler sync.
Now when I boot a server that is in one of those two modified VLANs I get "unknown network segment".
Is there some other modification I need to make to cobbler and/or dhcpd? None of the unmodified VLANs are having this issue.
Here is the config from the dhcp.template:
#vlan40 subnet 10.200.6.0 netmask 255.255.255.0 { option routers 10.200.6.1; option domain-name-servers 10.200.4.3, 10.200.4.4; option subnet-mask 255.255.255.0; range dynamic-bootp 10.200.6.242 10.200.6.251; filename "/pxelinux.0"; default-lease-time 1200; max-lease-time 1800; next-server $next_server; }
#vlan42 subnet 10.200.7.0 netmask 255.255.255.0 { option routers 10.200.7.1; option domain-name-servers 10.200.4.3, 10.200.4.4; option subnet-mask 255.255.255.0; range dynamic-bootp 10.200.7.242 10.200.7.251; filename "/pxelinux.0"; default-lease-time 1200; max-lease-time 1800; next-server $next_server; }
Thanks, David
Excerpts from Adurotec's message of Wed Apr 21 13:48:55 -0400 2010:
I have cobbler managing dhcpd and the pxe booting worked fine on each of my configured VLANS. I recently changed the IP range of two of my VLANs and then modified the dhcp.template followed by a cobbler sync.
Now when I boot a server that is in one of those two modified VLANs I get "unknown network segment".
Is there some other modification I need to make to cobbler and/or dhcpd? None of the unmodified VLANs are having this issue.
Can you give us the full error message? That generally means that dhcpd is seeing a request from a network segment that it doesn't have a configuration for. You have 10.200.6.0/24 and 10.200.7.0/24 configured, but maybe the request is coming in from 10.200.5.0/24?
Scott,
Here is the error I am seeing when a request is made from a host in VLAN40 10.200.6.0/24:
DHCPDISCOVER from 00:0c:29:54:6f:b1 via 10.200.6.1: unknown network segment
If I switch the host to VLAN42 I get a similar error:
DHCPDISCOVER from 00:0c:29:54:6f:b1 via 10.200.7.1: unknown network segment
It looks like the requests are coming from the correct network.
David
On 04/21/2010 03:26 PM, Scott Henson wrote:
Excerpts from Adurotec's message of Wed Apr 21 13:48:55 -0400 2010:
I have cobbler managing dhcpd and the pxe booting worked fine on each of my configured VLANS. I recently changed the IP range of two of my VLANs and then modified the dhcp.template followed by a cobbler sync.
Now when I boot a server that is in one of those two modified VLANs I get "unknown network segment".
Is there some other modification I need to make to cobbler and/or dhcpd? None of the unmodified VLANs are having this issue.
Can you give us the full error message? That generally means that dhcpd is seeing a request from a network segment that it doesn't have a configuration for. You have 10.200.6.0/24 and 10.200.7.0/24 configured, but maybe the request is coming in from 10.200.5.0/24?
Excerpts from Adurotec's message of Wed Apr 21 16:37:02 -0400 2010:
Scott,
Here is the error I am seeing when a request is made from a host in VLAN40 10.200.6.0/24:
DHCPDISCOVER from 00:0c:29:54:6f:b1 via 10.200.6.1: unknown network segment
If I switch the host to VLAN42 I get a similar error:
DHCPDISCOVER from 00:0c:29:54:6f:b1 via 10.200.7.1: unknown network segment
It looks like the requests are coming from the correct network.
Does /etc/dhcpd.conf contain the definitions for the vlans? Do they look correct? Does dhcpd -t return with a good exit code?
cobbler@lists.fedorahosted.org