Re: failure to recognize network config in ks.cfg

[John Fox <jpfox17@xxxxxxxxx>]

I added "ksdevice=link" to the append option in pxelinux.cfg/default and it seemed to help.  Now I am not prompted to choose which nic to use.  However, before the kickstart config file is found, the install tries to get the nic config from dhcp.  This fails and then I'm prompted to enter the network configuration.

 

Are there other options I can append in pxelinux.cfg/default that will tell the client what its network config should be?

 

What I don't understand is why the client is able to get an IP from DHCP to boot off the tftpboot server, but then it is unable to get or keep the IP to configure the nic during the insall.  Any ideas?  My pxe and dhcp configs are below.

 

Thanks!

 

[root@xxxxxxxxxxxx pxelinux.cfg]# pxeos -l
sec-trn-lnx01
        Description:    sec-trn-lnx01
        Protocol:       NFS
        isDiskless:     False
        Server:         192.168.1.61
        Location:       /kickstart/media/rhel4-u1-as

[root@xxxxxxxxxxxx pxelinux.cfg]# pxeboot -l
default sec-trn-lnx01

label sec-trn-lnx01
    kernel sec-trn-lnx01/vmlinuz
    append initrd=sec-trn-lnx01/initrd.img  ks=nfs:192.168.1.61:/kickstart/ks-files/192.168.1.62-kickstart.cfg ramdisk_size=10000  ksdevice=link

[root@xxxxxxxxxxxx pxelinux.cfg]# cat /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;

allow booting;
allow bootp;
subnet 192.168.1.0 netmask 255.255.255.0 {
# --- default gateway
        option routers                  192.168.1.1;
        option subnet-mask              255.255.255.0;

        option nis-domain               "blah.com";
        option domain-name              "blah.com";
        option domain-name-servers      blah blah;

        option time-offset              -18000; # Eastern Standard Time
        option ntp-servers              ntp.blah.blah.com;
        range dynamic-bootp 192.168.1.63 192.168.1.65;
        default-lease-time 600;
        max-lease-time 600;

        host sec-trn-lnx01 {
                next-server 192.168.1.61;
                #next-server marvin.redhat.com;
                hardware ethernet 00:0D:9D:DC:F6:89;
                fixed-address 192.168.1.62;
                filename "linux-install/pxelinux.0";
        }
}

 

On 12/16/05, Sébastien Aperghis-Tramoni <maddingue@xxxxxxx> wrote:

John Fox <jpfox17@xxxxxxxxx> wrote:

> Hi,
>
> I'm running RHEL 4 U1 AS.  I got my kickstart working with PXE, TFTP, DHCP,
> NFS, etc.  I'm able to see my kickstart config file and most of the config
> is picked up during the install, except for the network config.  I get
> prompted to choose which NIC to configure and then I have to specify the
> configuration.  After that, the install goes pretty well, but I need to be
> able to automate the NIC configuration piece.  Here is the network line from
> my kickstart file (all one line):
>
> network --device eth0 --bootproto static --ip 10.1.182.62 --netmask
> 255.255.255.0 --gateway 10.1.182.1 --nameserver 10.1.180.226 --hostname
> host1
>
> The machine that is being built is an HP DL380 w/2 GigE NIC cards.

I think someone previously said that this can be done by adding
"ksdevice=link" to the append option in your pxelinux.cfg/default.
This should autoselect the device physically connected to the network.

--
Sébastien Aperghis-Tramoni

Close the world, txEn eht nepO.

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