|
Ok, you are getting your initial pxeboot IP, it
successfully sends the kernel and initrd via tftp. At this point, the NIC
recycles itself, and the negotiation between NIC and switch starts all
over. This looks so far like the exact problem we experience, with the
same HP DL servers.
What does your pxeboot config file contain?
Oct 7 20:10:28 edcappsrhat7 in.tftpd[9105]: RRQ from 10.xxx.xxx.xxx filename pxelinux.cfg/0xxxxxx
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Elizabeth.Brosch@xxxxxxxxxxx Sent: Friday, October 07, 2005 1:19 PM To: kickstart-list@xxxxxxxxxx Subject: RE: Kickstart fails The server receives an
address during PXE:
output from
syslog: Oct 7 16:10:24
edcappsrhat7 dhcpd: DHCPDISCOVER from 00:14:c2:3c:a9:d2 via
eth0 Oct 7 16:10:24
edcappsrhat7 dhcpd: DHCPOFFER on 10.xxx.xxx.xxx to 00:14:c2:3c:a9:d2 via
eth0 Oct 7 16:10:28
edcappsrhat7 dhcpd: DHCPREQUEST for 10.xxx.xxx.xxx (10.xxx.xxx.xxx) from
00:14:c2:3c:a9:d2 via eth0 Oct 7 16:10:28
edcappsrhat7 dhcpd: DHCPACK on 10.xxx.xxx.xxx to 00:14:c2:3c:a9:d2 via
eth0 Oct 7 20:10:28
edcappsrhat7 in.tftpd[9102]: RRQ from 10.xxx.xxx.xxx filename
pxelinux.0 Oct 7 20:10:28
edcappsrhat7 in.tftpd[9102]: tftp: client does not accept
options Oct 7 20:10:28
edcappsrhat7 in.tftpd[9103]: RRQ from 10.xxx.xxx.xxx filename
pxelinux.0 Oct 7 20:10:28
edcappsrhat7 in.tftpd[9104]: RRQ from 10.xxx.xxx.xxx filename
pxelinux.cfg/01-00-14-c2-3c-a9-d2 Oct 7 20:10:28
edcappsrhat7 in.tftpd[9104]: sending NAK (1, File not found) to
10.xxx.xxx.xxx Oct 7 20:10:28
edcappsrhat7 in.tftpd[9105]: RRQ from 10.xxx.xxx.xxx filename
pxelinux.cfg/0xxxxxx Oct 7 20:12:03
edcappsrhat7 in.tftpd[9224]: RRQ from 10.xxx.xxx.xxx filename
vmlinuz Oct 7 20:12:03
edcappsrhat7 in.tftpd[9225]: RRQ from 10.xxx.xxx.xxx filename
initrd.img Then it starts the
process and dies with the message I posted earlier. It just hangs at
the: Welcome to Red Hat
Configure TCP/IP
screen Thanks. Liz
Brosch TSH System
Services office: (215)
386-0100 x1144 cell: (267)
784-9166 From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]
On Behalf Of Shabazian,
Chip Do you get an address
when you boot from disk 1 or the boot.iso? From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]
On Behalf Of
Elizabeth.Brosch@xxxxxxxxxxx Thanks for the reply
Chip but it didn’t work. I received the same
error. Liz From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]
On Behalf Of Shabazian,
Chip Will this server get a
dhcp address if you boot from the boot.iso (or disk 1 with askmethod) and select
http, ftp or nfs as your install path? If so, you are probably
running into a switch timing issue that I have to deal with every day. Try
adding an ethtool option to the end of your command
line: if 100MB Full
Duplex: ksdevice=eth0
eth0_ethtool="autoneg=off speed=100 duplex=full" If 1000MB
Full: ksdevice=eth0
eth0_ethtool="autoneg=on speed=1000 duplex=full" Chip From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]
On Behalf Of
Elizabeth.Brosch@xxxxxxxxxxx I have been trying to get kickstart
working but have had no success. Here are the last few lines of the
kickstart process before it dies: *getting kickstart
file *sending dhcp request through device
eth0 *waiting for
link * 5
seconds * running dhcp for
eth0 * pump told us: No DHCP reply
received * eth0 isn’t a wireless
adaptor I have checked every possible
configuration with regards to dhcp, pxe, tftp, but cannot find anything
wrong. Has anyone else seen this type of
behavior? Thanks in
advance. Liz
Brosch TSH System
Services office: (215) 386-0100
x1144 cell: (267)
784-9166 |
