I've been wrestling with this for a couple days now. I cannot get the kickstart in RHEL 5 to work with static ip configuration. We have servers here that are in security zones that do not and will not have dhcp.

I've found some things out there to statically configure this. These servers are also boot from san so the command I'm trying to use is:

linux mpath ks=http://buildServer/rh64/ks/phys32G.cfg ksdevice=eth0 ip=x.x.x.x netmask=xxx.xxx.xxx.xxx gateway=x.x.x.x dns=x.x.x.x

Even though I use this with the network boot disk, it still tries to use DHCP on eth0 and is then unable to go get the kickstart file and proceed with the build.

If I use the command:

linux mpath askmethod

And then statically configure eth0 and point it to the http build server, it brings it up just fine but then I don't have my automated build. It just seems that the "ks" directive tells it to use DHCP no matter what.

Any ideas?

Chad

I found the problem. The command I entered in was just fine so it is able to download the kickstart file but then I needed to have all the static IP information in the kickstart file as well in order for the installation to work.

Chad