Folks,
Im hoping you guys can help me. Here is a description of what I have going on.

Fresh VM, trying to run a Kickstart Install on it for RHEL5. I am looking to access the kickstart file through nfs.

I boot from a local ISO image and everything goes fine, I get to the boot prompt and enter linux ks=nfs:43.145.XXX.XX:/data/ks/ksrh5x86_64.cfg

---it is at this point where I am confused on what to do---
I have in a document left to me by someone who used to work here, the following information.

#linux ks=nfs:43.136.2.31:/data/ks/ksrh5x86_64.cfg
ksdevice=eth0
ip=xx.xxx.xx.xx
netmask=xxx.xxx.xxx.x
gateway=xx.xxx.xxx.xx
noipv6

---Here is my problem----

I do this at the boot prompt, everything flows until it comes back saying sending request for IP information for eth0"...That goes on for a few minutes then I get a screen that pops up saying "Error Downloading Kickstart File"

"Unable to Download the Kickstart file, Please modify the Kickstart paramater below or press cancel to proceed as an interactive installation"


---Questions---
I am not well versed in RHEL5 and this is my first time doing a Kickstart install.

-Am I supposed to enter the KSdevice,IP,netmask,gateway and noipv6 on the same line that I am entering the ks=nfs path?

-Is there something I am missing?


I would be forever greatfull if someone could assist me with this.
I am stumped and confused.

I am looking forward to learning more about this and would appreciate the assistance.

Many Thanks,
Mathew

from RHEL5 guide:

(http://www.redhat.com/docs/manuals/e...nginstall.html)

ks=nfs:<server>:/<path>

The installation program looks for the kickstart file on the NFS server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share /mydir/ks.cfg, the correct boot command would be ks=nfs:server.example.com:/mydir/ks.cfg.


so you need to have a dhcp server for your ksdevice network settings.

Many thanks for the response. I did read that when I first started the project, I have the path and the server name correct.

Are you saying that I cannot run KS unless I have a DHCP server setup that will automatically propogate the IP, Gateway, Subnet, etc of the new server I am trying to setup?

I am not sure what you meant by "so you need to have a dhcp server for your ksdevice network settings"

Here is my Kickstart .cfg file.

#platform=x86, AMD64, or Intel EM64T
key 6f06ca8b6f8a84ca
# System authorization information
auth --useshadow --enablemd5
# System bootloader configuration
bootloader --location=mbr
# Partition clearing information
clearpart --all
#part /boot --fstype ext3 --size=100
#part / --fstype ext3 --size=14000
#part swap --size=48000
#part pv.5 --size=1 --grow
#part /boot --fstype ext3 --onpart sda1
#part pv.2 --noformat --onpart sda2
#part / --fstype ext3 --onpart sda3
#part swap --onpart sda5
#volgroup VolGroup00 --noformat --useexisting --pesize=32768 pv.2
#logvol /home --useexisting --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1984
# Use graphical install
#graphical
text
# Firewall configuration
firewall --disabled
# Run the Setup Agent on first boot
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# Installation logging level
logging --level=info
# Use NFS installation media
nfs --server=43.145.xxx.xxx --dir=/data/Redhat/es5_64
#url --url http://43.145.xxx.xxx/linux/Redhat/es5_64
# Network information
network --bootproto static --ip 43.145.xxx.xxx --netmask 255.255.255.0 --gateway 43.145.xxx.xxx --nameserver 43.144.xxx.xxx noipv6
#Root password
rootpw --iscrypted $1$1IHJQFxxxxvv$/vE.zulxxxxWTzSueEkdy14W/0

# SELinux configuration
selinux --disabled
# System timezone
timezone America/New_York
# Install OS instead of upgrade
install
# X Window System configuration information
skipx
#xconfig --defaultdesktop=GNOME --depth=8 --resolution=800x600 --startxonboot


%packages
@admin-tools
@base
@base-x
@core
@development-libs
@development-tools
@editors
@gnome-desktop
#@java
#@java-development
@legacy-software-development
@legacy-software-support
@server-cfg
@system-tools
@web-server
kernel-devel
-bluetooth
-cpuspeed
-ip6tables
-kudzu
-pcscd
-avahi-daemon
-setroubleshoot
-autofs
-cups
-mcstransd
-hidd
-libXp
#require for IBM RSA RPM installation
libusb-devel

%post
/bin/sleep 5
/etc/init.d/portmap start > /root/postinstall.log 2>&1
#/bin/mkdir /mnt/nfs > /root/postinstall.log 2>&1
#/bin/mount 43.136.xxx.xxx:/data/linux /mnt/nfs > /root/postinstall.log 2>&1
#/bin/cp /mnt/nfs/ks/postinstall_rh5x86_64.sh /root/ > /root/postinstall.log 2>&1
/usr/bin/wget -P /root/ http://43.145.xxx.xxx/linux/ks/postinstall_rh5x86_64.sh > /root/postinstall.log 2>&1
/bin/chmod 500 /root/postinstall_rh5x86_64.sh
/root/postinstall_rh5x86_64.sh > /root/postinstall.log 2>&1








Many thanks for the response though born.

-Matt

Matt,

You don't need DHCP in that moment, just need to run in the boot: at the first time:

boot: linux nfs:43.145.XXX.XX:/data/ks/ksrh5x86_64.cfg ksdevice=eth0 ip=xx.xxx.xx.xx netmask=xxx.xxx.xxx.x gateway=xx.xxx.xxx.xx noipv6

note:Everything in one line and the ip configuration will be the static IP of this new virtual Server

And just comment the line with http call in the post% and uncoment the nfs mount:


%post
/bin/sleep 5
/etc/init.d/portmap start > /root/postinstall.log 2>&1
/bin/mkdir /mnt/nfs > /root/postinstall.log 2>&1
/bin/mount 43.136.xxx.xxx:/data/linux /mnt/nfs > /root/postinstall.log 2>&1
/bin/cp /mnt/nfs/ks/postinstall_rh5x86_64.sh /root/ > /root/postinstall.log 2>&1
#/usr/bin/wget -P /root/ http://43.145.xxx.xxx/linux/ks/postinstall_rh5x86_64.sh > /root/postinstall.log 2>&1
/bin/chmod 500 /root/postinstall_rh5x86_64.sh
/root/postinstall_rh5x86_64.sh > /root/postinstall.log 2>&1

Trust me that this will work....Noel

DHCP simplifies the kickstart process so you don't have to specify an IP and other network settings when performing kickstarts. You may want to consider setting up a small range of IP's with DHCP if you plan to kickstart machines on an ongoing basis.

I agree of create a pool of DHCP for that and this will help us to make the server more quicly.

But sometimes we don't have access to the DHCP server or we cannot have the rights to create a new one in a production enviroment (security reasons or internal policies).

I think depend of the enviroment we use or not DHCP and I think Matt need static IP's for this servers, and I know too that we can configure later this statics IP but will be double work.

nrodri72,
Thanks for your response. I ended up using http and it works great...
You are correct, we don't have DHCP access in our Data Center facility for this project.

On another note.. you wouldnt happen to be Noel Rodriguez that worked for Sony would you?

Thanks,
Matt

tricky,
DHCP would make my life a HECK of alot easier, unfortunately establishing DHCP is not in the cards for this project, I have already tried to get that implemented for this project, with no luck.

Thanks,
Matt

Yes you got it, thats the reason that I know your problem, and actually I working with ks in rh5.1 and rh4 disaster recovery project....

Do you still work for Sony?

If you want, hit me up on AOL Instant Message. My screen name is "Icestain"

I left Sony in the moment that you saw me, I working in another client with the same Linux platform (RH5) I have filter all IM's here, but I can do it from home at night...

I don't think I have ever met you, I think you left Sony just as Jim was coming in, I replaced Jim. Jim ended up getting a great job at Yahoo in the city doing Linux for them...

IM me tonight, we can chat over IM.

The above at least pointed me in the right direction. Though I was not using NFS. I had to upload my ks.cfg file to another web server and point to that web server from grub.conf.

Here is my grub.conf that seemed to work for me. Where #.#.#.# is a location where I uploaded the ks.cfg file to.
Full details can be found here.
http://www.techdruid.com/index.php/c...start-problems