Kickstart across subnets

[MW Mike Weiner (5028)]

Philip -

Good question, no real reason other than this was an old ks.cfg modified
for this project - I will clean it up, though I doubt that has mich
impact.

Thanks!! 
Michael

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: Tuesday, December 27, 2005 10:55 PM
To: Discussion list about Kickstart
Subject: Re: Kickstart across subnets

On Tue, 27 Dec 2005, MW Mike Weiner (5028) wrote:

> I created a ks boot cd, with all the required files (i.e. vmlinuz, 
> initrd.img, isolinux.bin, etc) and the key line in my isolinux.cfg is 
> as
> follows:
>
> label linux
>  kernel vmlinuz
>  append ksdevice=eth1 console=tty0 load_ramdisk=1 prompt_ramdisk=0 
> initrd=initrd.img network ip=dhcp 
> ks=nfs:192.168.34.248:/tftpboot/ks-fc2.cfg selinux=0

Why the console, load_ramdisk, prompt_ramdisk, and network arguments? 
I'm not sure these are necessary, and they potentially cloud the
problem.

Is it possible that the network switches for the problematic machines
are taking some time to bring up the port? This can happen with high(er)
end hardware and the Spanning Tree Protocol. anaconda's undocumented
"linksleep" setting can help here.

> I have to complete these 400+ kickstarts by the end of January 2006.

Good luck!


Cheers,
Phil

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