kickstart-list-bounces@xxxxxxxxxx wrote on 05/14/2007 02:48:04 PM:
> How many NIC's do you have in the box? Are they all embedded, or
> are there some on cards?
2 NICs. Only one is active an plugged in to a switch.
While it may be powerful, it seems to be way more complicated than should be required.
If the server can find its initial IP via DHCP to load pxelinux and to load the kernel, why is it
unable to complete the last step and locate the kickstart file? I have specified the ksdevice
several different ways and none have been successful (ksdevice=eth0, =link, =bootip with ipappend, =eth1)
and in all cases anaconda ends up unable to get the IP and prompts me for static network configuration.
I enter the needed network information and provide the NFS information to reach the RH install image and
the box is able to read the o/s image and start an interactive install.
I have also dropped to command line (ctl-alt-f2) and verified that the nfs directory holding the KS file
can be mounted. And I have verified it can be retrieved with http using wget. And still anaconda is
unable to retrieve the file with either nfs or http.
>
> Kickstart is a very powerful and useful tool that we use globally to
> build over 1000 distributed systems each year from a centralized and
> managed location, and although it has bugs like any product, most
> issues like you are having tend to be infrastructure or manufacturer related.
>
> From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-
> bounces@xxxxxxxxxx] On Behalf Of SSTinsley@xxxxxxxxxxxxxx
> Sent: Monday, May 14, 2007 11:36 AM
> To: Discussion list about Kickstart
> Cc: Discussion list about Kickstart; kickstart-list-bounces@xxxxxxxxxx
> Subject: Re: Kickstart via PXE/NFS
>
> I made a change to pxe cfg file to have ks.cfg file read via http.
>
> It fails too. However, if I look in the anaconda log I see the
> message getting ks.cfg
> but then failed to transfer ks.cfg to fd. The snoop from the KS
> server side shows the HTTP
> retrieval of the KS config file. Is it really trying to use an fd
> device, a floppy? These
> Dell servers do not include floppys.
>
> Redhat sure has taken something that should be relatively easy and
> made it a pain in the butt.
>
>
> kickstart-list-bounces@xxxxxxxxxx wrote on 05/14/2007 01:29:54 PM:
>
> > if you page-up in vty3, can you see what your kernel command line is?
> > alternately if it makes it to shell in vty2, 'cat /proc/cmdline' - i
> > wonder if it's actually doing the ipappend stuff. you might need a
> > newer pxelinux.0 if not. also, instead of 'ksdevice=bootif' you can do
> > 'ksdevice=link ip=dhcp' ; the bootif argument is more useful if you
> > have 2 nics enabled/link-up and want to make sure it doesnt pxeboot
> > out one interface and then ks out the other.
> >
> > -=Eric
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC
> INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR
> ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO
> RECEIVE IT. If you are not the intended recipient of this document,
> you are notified that any review, dissemination, distribution or
> copying of this communication is prohibited. If you have received
> this communication in error, please notify me immediately by return
> email, delete the electronic message and destroy any printed copies.
> Thank you for your cooperation._______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not the intended recipient of this document, you are notified that any review, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify me immediately by return email, delete the electronic message and destroy any printed copies. Thank you for your cooperation.
