|
Hi John, Anaconda depends on DHCP even if you use static IPs. I have made some progress on this... I have posted this on the group but here it is for you anyways (it’s
rather long): I did what Kennedy suggested. Thanks much. Connected the KVM and did the Alt-F commands. What I found is this: " ... ... getting kickstart file looking for first netDev with link eth0 has link, using it doing kickstart...setting it up waiting for link... 4 seconds no DNS servers, can't look up hostname ks location: http://171.67.39.130/ENT_LINUX_64/Enterprise/ks.cfg transferring http://171.67.39.130//./ENT_LINUX_64/Enterprise/ks.cfg to
a fd failed to retrieve
http://171.67.39.130///ENT_LINUX_64/Enterprise/ks.cfg trying to " As I said before, I could retrieve all the above http links from
another system on the same subnet as my kickstart install server and the
client. After which I modified my default file to the following: label 1 kernel ENT_LINUX_64/vmlinuz append nofb initrd=ENT_LINUX_64/initrd.img ramdisk_size=10000 lang=
devfs=nomount ramdisk_size=9216 ksdevice=link ip=171.67.39.139
netmask=255.255.255.224 gateway=171.67.39.129 dns=171.64.7.77
ks=http://171.67.39.130/ENT_LINUX_64/Enterprise/ks.cfg I put the dns= entry in there. The I get the following: " ... Adding 171.64.7.77 dnsserver is 171.64.7.77 doing kickstart...setting it up waiting for link 4 seconds reverse name lookup failed ks location: http://171.67.39.130/ENT_LINUX_64/Enterprise/ks.cfg transferring http://171.67.39.130//./ENT_LINUX_64/Enterprise/ks.cfg to
a fd failed to retrieve
http://171.67.39.130///ENT_LINUX_64/Enterprise/ks.cfg trying to " Here is the network information from my ks.cfg file: #Network information network --device=eth0 --bootproto=static --ip=171.67.39.130
--netmask=255.255.255.224 --gateway=171.67.39.129 --nameserver=171.64.7.77
--hostname=as-kickball.stanford.edu The hostname is invalid. It’s a bogus name. I’ll try to
make it a valid name and check it out. Should there be a hostname in the default file as well since I am using
static IP? I think I am getting close here. Something else is missing for the reverse
lookup to work. Suggestions would be helpful at this point. Thanks -Mukarram. -----Original Message----- muksyed@xxxxxxxxxxxx wrote: > Quoting John Summerfield <debian@xxxxxxxxxxxxxxxxxxxxxx>: > >> Mukarram Syed wrote: >>> John, >>> Sorry...just to make things clear. >>> eth0 works to get the dhcp/tftp request and eth1 does
not. However, >>> I tried >>> using both is what I meant. >>> >>> We have a problem with dhcp, the networking folks here did
not enable >>> "spanning tree" on the switch ports, until that
happens I am using >>> static >>> ip. I double checked the syntax etc. >> >> I don't understand... pxelinux works and can load the
kernel/initrd, >> and the kernel/initrd doesn't work. Is that what you said? > > Sorry for the confusion John. > > pxelinux works and it loads the vmlinuz and initrd. > > >> >> How does the BIOS know to load pxelinux, and where to get it?
Doesn't >> that require dhcp (or at least bootp)? >> >> How does pxelinux get its menus and then the kernel? Doesn't
that >> require dhcp (or at least bootp) too? >> >> And then the kernel/initrd can't get the IP address the same
way. Have >> I got the facts straight? >> > > Actually I have dhcpd configured for static IP address. Not for a
range > of IP addresses to pick from. dhcpd is running. After PXE loads
up the > kernel, I think the installer anaconda uses dhcp to again look for
the > ks.cfg file. This is after the menu. That's the part which does
not > work. That's why I put in the static IP's in my default file
under > label 1. Putting the static IP's don't work as well. > What I don't understand is how the BIOS and pxelinux can both get an IP
address, and Anaconda can't. Have you tried using IPAPPEND instead of ip= on the kernel parameters. Read syslinux.doc for clarification. -- Cheers John -- spambait 1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx Please do not reply off-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list |
