Problems doing a ks over NFS

[MW Mike Weiner (5028)]

Ok, here are some log entries to indicate that the dhcp IS working over
the dhcrelays

Dec 19 14:57:06 yum1 dhcpd: DHCPDISCOVER from 00:50:da:6e:41:58 via
192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPOFFER on 192.168.31.106 to
00:50:da:6e:41:58 via 192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPDISCOVER from 00:50:da:6e:41:58 via
192.168.30.58: network 192.168.30/24: no free leases
Dec 19 14:57:06 yum1 dhcpd: DHCPDISCOVER from 00:50:da:6e:41:58 via
192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPOFFER on 192.168.31.106 to
00:50:da:6e:41:58 via 192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPREQUEST for 192.168.31.106
(192.168.34.248) from 00:50:da:6e:41:58 via 192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPACK on 192.168.31.106 to
00:50:da:6e:41:58 via 192.168.31.129
Dec 19 14:57:06 yum1 dhcpd: DHCPREQUEST for 192.168.31.106
(192.168.34.248) from 00:50:da:6e:41:58 via 192.168.30.58: ignored (not
authoritative).

This indicates that this specific box (31.106) SHOULD work and be able
to be kickstarted and install via NFS (providing everything else is ok),
as the dhcp issues across the subnets has been resolved (in part) by
adding another dhcrelay server onto the 31 subnet rather than leaving it
on the 30 subnet, as our masking doesn't necessarily allow the two
subnets to talk to one another. So, in short I have the following:

192.168.30.x - dhcrelay server already here
192.168.31.x - dhcrelay server added
192.168.32.x - dhcrelay server already here
192.168.33.x - dhcrelay server *needed* here (though subnet mask allows
some cross subnet communication)
192.168.34.x - no dhcrelay server as the dhcpd server sits here (which
is also the same box doing the NFS and yum/ks portions of this
exercise).

I am hoping this will alleviate my headaches. Anything else I may have
missed? Anyone?

Thanks in advance, and thanks for all the responses to my problem.

This e-mail and any attachments may contain confidential information
that is legally privileged. The information is solely for the use of the
intended recipient(s); any disclosure, copying, distribution, or other
use of this information is strictly prohibited. If you have received
this e-mail in error, please notify the sender by return e-mail and
delete this message. Thank you.

-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Philip Rowlands
Sent: Monday, December 19, 2005 10:21 AM
To: Discussion list about Kickstart
Subject: RE: Problems doing a ks over NFS 

On Mon, 19 Dec 2005, MW Mike Weiner (5028) wrote:

>> Are you sure the DHCP relay is working? What happens outside of a 
>> kickstart install?
>
> Well I would think that since I see messages on the kickstart server 
> FROM the dhcprelay server, that this would imply things are kinda 
> sorta working, yes.

I'd suggest checking to make sure.

> As for NFS, yes I know that's working as I can do a 'same vlan' 
> kickstart over NFS and that works fine.

I'd suggest checking to make sure. In both cases you appear to have
given reasons why things should be working through indirect evidence.

> I just keep seeing this on the dhcp/kickstart/repo server whenever I 
> attempt to do a box on another subnet:
>
> Dec 19 09:22:03 yum1 dhcpd: DHCPDISCOVER from 00:30:48:29:c9:55 via 
> 192.168.20.58: unknown network segment Dec 19 09:22:05 yum1 dhcpd: 
> DHCPDISCOVER from 00:30:48:29:c9:55 via 192.168.20.58: unknown network

> segment Dec 19 09:22:06 yum1 dhcpd: DHCPINFORM from 192.168.20.160 via

> eth1: unknown subnet 192.168.20.58

This is far from a complete DHCP exchange; the client is not receiving
any "offer". Why the "unknown subnet" errors?


Cheers,
Phil

_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list