This is probably out-of-scope for this forum, but as I am running BLAG 70001 on my NFS/Kickstart server, I'll post here anyway. Heck, HP and RedHat have been useless to me, and BLAG quite the opposite, so there!
I'm using HP's SmartStart Toolkit to create an automated Red Hat install process, but can't seem to initiate a kickstart build due to an apparent failure to load network drivers upon boot. SmartStart successfully loads a saved BIOS and hardware configuration and then creates an initial MBR and boot partition on the hard drive of an HP Proliant DL585. The boot loader (via syslinux), initrd.img, vmlinuz and syslinux.cfg are all loaded to this new partition during a pre-boot phase, and everything seems to start out normally upon reboot. The QLogic, USB and cciss drivers are all loaded, but instead of invoking kickstart, I am prompted for keyboard language, installation method and network configuration info. All of this is in the kickstart config file, which evidently is not being seen due to a failure to connect to the network.
My initial syslinux.cfg file looks like this:
say Performing RedHat Kickstart Installation
append initrd=initrd.img lang=en devfs=nomount ramdisk_size=9216
append initrd=initrd.img lang=en devfs=nomount ramdisk_size=9216 init=/sbin/init root=/dev/nfs ip=:192.168.5.10:192.168.5.252:255.255.0.0:::'bootp' ks=nfs:192.168.1.43:/home/pablo/tmp/ks/ha2_net.ks.cfg ksdevice=eth2 network=1
As there is very little documentation available on this sort of thing, I've basically slapped together the second "append" line from a number of sources. In a perfect world this would be merely a syntax error, but I don't think I'm even getting that far. In any event, an extra set of eyes would be greatly appreciated. Thanks!