static ips and automation

[Joe Van Dyk]

On 2/14/06, Shabazian, Chip <Chip.Shabazian at bankofamerica.com> wrote:
> You can give the system it's IP information on the boot: line... (IP=
> NETMASK= GATEWAY=) then get that information in %pre, create a network
> line, and viola, you have a static entry that is dependent on the boot:
> options

Hm... that's a good idea!  I'll try that out.

> Also, is the address you are getting from DHCP the correct and permanent
> address?

No, it's just a temporary address.

> -----Original Message-----
> From: kickstart-list-bounces at redhat.com
> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe Van Dyk
> Sent: Tuesday, February 14, 2006 3:31 PM
> To: Discussion list about Kickstart
> Subject: Re: static ips and automation
>
> So, a kickstart config file needs to be created for each different
> computer, and then, when I start the kickstart installation, I point
> it to the appropriate kickstart file?
>
> Joe
>
> On 2/14/06, Lavender, Leo <LLavender at kmg.com> wrote:
> > Check out
> >
> http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-gui
> > de/index.html for kickstart.
> >
> > Here's a couple of example lines.
> >
> > network --device eth0 --bootproto static --ip nnn.nnn.nnn.nnn
> --netmask
> > 255.255.248.0 --gateway nnn.nnn.nnn.nnn --nameserver nnn.nnn.nnn.nnn
> > --hostname george03
> > authconfig --enableshadow --enablemd5 --enablenis --nisdomain kmgep
> > --nisserver nnn.nnn.nnn.nnn
> >
> > Post install scripts can do the rest for you.
> >
> > I defer to the experts fot update methods. However, since you are RHEL
> > 3, I assume that your applications are release sensitive. Could be
> worth
> > dedicating a test machine. Local satillite servers, etc., will take
> more
> > admin.
> >
> > Use more Google.
> >
> > Good luck, Leo
> >
> > -----Original Message-----
> > From: kickstart-list-bounces at redhat.com
> > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe Van Dyk
> > Sent: Monday, February 13, 2006 9:55 PM
> > To: Discussion list about Kickstart
> > Subject: static ips and automation
> >
> >
> > Hi,
> >
> > Is there some obvious way that I'm missing to easily give a computer a
> > static IP address (and gateway/nameserver) during an automated
> kickstart
> > installation?  Each computer has their own IP and some are on multiple
> > networks (i.e. more than NIC).
> >
> > Currently, the kickstart installation gives each one a DHCP address,
> > then after the installation is complete and the computer reboots,
> > someone then has to go through the redhat GUI and enter in its
> > networking information.  (And then run a script that nfs mounts a
> > directory and installs some additional rpms that depend on it being
> > networked correctly.)
> >
> > And say I've got twenty computers all set up (with RHEL 3).  Would I
> use
> > up2date on them to keep them err, up to date?  That involves me
> setting
> > up a server somewhere with updated RPMs?
> >
> > Sorry for the silly questions.  I'm not a system administrator at all
> > and I have no idea why I'm the one doing this.
> >
> > Joe
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> >
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>