SCIENTIFIC-LINUX-USERS Archives

December 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Phillip Sorensen <[log in to unmask]>
Reply To:
Phillip Sorensen <[log in to unmask]>
Date:
Wed, 3 Dec 2014 09:10:51 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
On 12/2/2014 6:55 PM, William R Somsky wrote:
> Okay, I have an odd problem.
>
> I normally install SL using a net-install boot which then fetches a
> kickstart file from our local webserver. Lately, however, trying to
> fetch the kickstart file has been failing.
>
> Here is what seems to be the issue:
>
> We have a local /23 subnet (ie netmask 255.255.254.0) and some of our
> DHCP addresses are in the high half.  Sometimes when the net-install
> boots and does a DHCP setup for the initial network connection, it gets
> one of these high-half addresses.  Eg, from the F4 screen:
>
>      INFO NetworkManager: <info>  address XXX.XX.189.41
>      INFO NetworkManager: <info>  prefix 23 (255.255.254.0)
> INFO NetworkManager: <info>  gateway XXX.XX.188.1
> INFO NetworkManager: <info>  nameserver 'YYY.YY.yy.yy'
> INFO NetworkManager: <info>  nameserver 'YYY.YY.zz.zz'
>

I do PXE and other network installs on our /23 network all the time.  I 
don't think it is a bug on the installer.

> So far, so good.  However, trying to fetch the kickstart file fails.
> Looking on the F3 screen I see:
>
>      HH:MM:SS.sss ERROR   : failed to retrieve http://.....: Couldn't
> resolve host name
>

I would check the network configuration on the DNS server.  We saw 
issues like this when we expanded our network from a /24 to a /23, and 
missed changing the network mask/broadcast address on a server.

> So it's not properly accessing the nameservers.
>
> However, sometimes it gets a low-half ip (XXX.XX.188.xx) and then it
> works properly.
>
> It sounds like the NetworkManger isn't properly setting up routing for
> the extra-wide subnet, but I have no way to check further. (Note, other
> machines w/ high-half ip's work fine, so it's not problems w/ the local
> network.)
>
> Anyone have any ideas, or know if this is an existing, known bug?
>
> - WRSomsky

ATOM RSS1 RSS2