|
Actually the kickstart infrastructure that I have setup today uses a generic boot cd. I have the SA’s specify the IP on the boot: line along with the ks=http://, the ks url is actually a cgi script that reads a static config file. The config file has markers in it that are replaced with actual values based on certain things. For instance, the cgi looks at the IP making the connection, does a reverse lookup to get the fqdn, the hostname is plucked from the fqdn, and the actual hostname replaces the hostname_marker in the static config file just before it’s sent to the install client. This allows me to have one config for a type of install, but allows it to be customizable on a per client basis.
I just ran into the stupid server NIC to switchport timeout problem.
I guess I could get to the same place if I had a generic ks.cfg imbedded in the initrd, and used wget and %include. This actually might work better than what I have today as it should work with the timeout problem where as my stuff did not. Hmmm.
-Bill
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Shabazian, Chip
> (So typically when an issue is solved, does the person with the issue and resolution write a summary for the list?)
Usually all I see is either a "it worked" or those with problems stop asking questions :(
If you ever want to make a "generic" boot cd, you can assign the IP address on the boot: line, then have just what you need to get the machine up in the embedded ks.cfg, and use wget, or nfs (not sure about ftp/tftp) to pull in the system specific config, then use %include to add it into the ks.cfg. This is the way we are moving to.
Glad you got things working,
Chip
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Ramthun, William Chip,
Thanks for the help!
I did try setting ethtool_opts=”autoneg off speed 100 duplex full” along with the nicdelay=50 earlier and received no love for my efforts.
I did build the 20 configs and wrapped them in the initrd.img – and that worked. I did have to edit all 20 configs for a cut/paste line-wrap error. But now the 20 systems are built.
I really appreciate the help in working to a solution. Since this problem is solved for now and for all my other installation needs the ks=http:// works, I am not sure that I will ever learn what my network problem was.
(So typically when an issue is solved, does the person with the issue and resolution write a summary for the list?)
Regards, -Bill
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Shabazian, Chip
Try the following:
If you are connected to a gigabit switch:
Boot: ap10903-02-net ksdevice=eth0 ip=10.196.254.122 netmask=255.255.255.0 gateway=10.196.254.1 nicdelay=50 linksleep=50 ETHTOOL_OPTS="autoneg on speed 1000 duplex full"
If you are connected to a 100Mb switch:
Boot: ap10903-02-net ksdevice=eth0 ip=10.196.254.122 netmask=255.255.255.0 gateway=10.196.254.1 nicdelay=50 linksleep=50 ETHTOOL_OPTS="autoneg off speed 100 duplex full"
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Ramthun, William
Summarizing my situation:
Client HW: HP DL385 Client OS: RHEL3U5 The boot cd is mounted via the virtual cdrom thru HP’s ILO port.
My isolinux.cfg contains the entry:
label ap10903-02-net kernel vmlinuz append ks=http://10.1.181.252/cgi-bin/avamar/dl385_data_node initrd=initrd.img text
And on the boot: line I use:
Boot: ap10903-02-net ksdevice=eth0 ip=10.196.254.122 netmask=255.255.255.0 gateway=10.196.254.1 <nicdelay/linksleep=options>
I’ve used both nicdelay and linksleep with values of 50, 500, 5000, and 50000 with no discernable boot delays.
The result is: I see vmliniz and initrd loading. I am presented the “welcome to red hat linux” blue screen (I’m in text mode) Then I see the usb and raid controller drivers load Then I see a “determine hostname and domain” ( I think this is where the timeout occurs ) Then I am prompted to “choose a language”
In a different terminal window I am “pinging” the 10.196.154.122 IP during the whole boot process. Once the “choose a language” prompt appears, then the interface begins responding to my pings.
My next step is to include the Kickstart config in the initrd.
If anyone sees any issues with my method, please drop me a note. Thanks -Bill
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Vivek.Kalia@xxxxxxxxxxxxx
|
