RgSalisbury
2007-May-28 05:07 UTC
[syslinux] Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.
Hi ALL Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned. Is there a Protocol communication problem ???????? Are there alternative tftp-severs that work for the RHEL5.. It seems: the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm) But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm) Client very SLOWLY displays thus: Trying to load: pxelinux.cfg/AC1000FD Trying to load: pxelinux.cfg/AC1000F Trying to load: pxelinux.cfg/AC1000 Trying to load: pxelinux.cfg/AC100 Trying to load: pxelinux.cfg/AC10 Trying to load: pxelinux.cfg/AC1 Trying to load: pxelinux.cfg/AC Trying to load: pxelinux.cfg/A Trying to load: pxelinux.cfg/default Message log : #################################################################### dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b via eth1 dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1 xinetd[3173]: START: tftp pid=3238 from=172.16.0.253 in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0 in.tftpd[3239]: tftp: client does not accept options in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0 *** AND STOPS here ** #################################################################### the "tftp: client does not accept options" doesn't seem to be a problem as it is generated on RHEL4 servers & the pxe booting still WORKS. Enviroment details: OS: RHEL5 KERNEL: Kernel 2.6.18-8.el5 SERVER: tftp-server-0.42-3.1.i386.rpm NIC: INTEL 82801BA/CA # server THanks in advance Roger
RgSalisbury
2007-May-28 05:15 UTC
[syslinux] Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.
Hi ALL Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned. Is there a Protocol communication problem ???????? Are there alternative tftp-severs that work for the RHEL5.. It seems: the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm) But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm) Client very SLOWLY displays thus: Trying to load: pxelinux.cfg/AC1000FD Trying to load: pxelinux.cfg/AC1000F Trying to load: pxelinux.cfg/AC1000 Trying to load: pxelinux.cfg/AC100 Trying to load: pxelinux.cfg/AC10 Trying to load: pxelinux.cfg/AC1 Trying to load: pxelinux.cfg/AC Trying to load: pxelinux.cfg/A Trying to load: pxelinux.cfg/default Message log : #################################################################### dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b via eth1 dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1 xinetd[3173]: START: tftp pid=3238 from=172.16.0.253 in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0 in.tftpd[3239]: tftp: client does not accept options in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0 *** AND STOPS here ** #################################################################### the "tftp: client does not accept options" doesn't seem to be a problem as it is generated on RHEL4 servers & the pxe booting still WORKS. Enviroment details: OS: RHEL5 KERNEL: Kernel 2.6.18-8.el5 SERVER: tftp-server-0.42-3.1.i386.rpm NIC: INTEL 82801BA/CA # server THanks in advance Roger
H. Peter Anvin
2007-May-28 05:38 UTC
[syslinux] Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.
RgSalisbury wrote:> > the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir > > RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm) > > But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm) >*TO THE SAME CLIENT*???? What you're describing is a common problem, but I have NEVER seen it be a server problem. The one thing that might be an issue is if you have a funny firewall setup on your server. -hpa
RgSalisbury
2007-May-28 05:39 UTC
[syslinux] Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.
sorry --1st message was html correcting now! Hi ALL Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned. Is there a Protocol communication problem ???????? Are there alternative tftp-severs that work for the RHEL5.. It seems: the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm) But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm) Client very SLOWLY displays thus: Trying to load: pxelinux.cfg/AC1000FD Trying to load: pxelinux.cfg/AC1000F Trying to load: pxelinux.cfg/AC1000 Trying to load: pxelinux.cfg/AC100 Trying to load: pxelinux.cfg/AC10 Trying to load: pxelinux.cfg/AC1 Trying to load: pxelinux.cfg/AC Trying to load: pxelinux.cfg/A Trying to load: pxelinux.cfg/default Message log : #################################################################### dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b via eth1 dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1 xinetd[3173]: START: tftp pid=3238 from=172.16.0.253 in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0 in.tftpd[3239]: tftp: client does not accept options in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0 *** AND STOPS here ** #################################################################### the "tftp: client does not accept options" doesn't seem to be a problem as it is generated on RHEL4 servers & the pxe booting still WORKS. Enviroment details: OS: RHEL5 KERNEL: Kernel 2.6.18-8.el5 SERVER: tftp-server-0.42-3.1.i386.rpm NIC: INTEL 82801BA/CA # server THanks in advance Roger
Dyks, Axel (XL)
2007-May-28 15:47 UTC
[syslinux] Has anyone any insight as to why RedHatEnterprise Level 5 is broken as far as PXE booting is concerned.
RgSalisbury wrote:>> Could you produce a wireshark trace of the traffic? >> > A little more with verbosity turned up & no arp messages > ############################################################################# > > 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none], proto: > UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ > "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks >Did you set "next-server" in "dhcpd.conf"? Seems to me that the client tries to TFTP from 0.0.0.0, after retrieving "pxelinux.0". RHEL 5 might have a newer version "dhcpd" which no longer sets "next-server" to "boot/dhcp server" when missing in "dhcpd.conf". Axel
RgSalisbury
2007-May-29 01:10 UTC
[syslinux] Has anyone any insight as to why RedHatEnterprise Level 5 is broken as far as PXE booting is concerned.
OK
Different symptons
I have now tried on a RHEL different machine with a different nic.(Intel
ethernet pro 100)
But same client & a different client
Client messages are:
##################
PXE-T02 Only absolute filenames allowed
PXE-E3C TFTP ERROR - Access Violation
PXE-M0F: Exiting Broadcom PXE ROM.
##################
##################
PXE-T02 Only absolute filenames allowed
PXE-E3C TFTP ERROR - Access Violation
PXE-M0F: Exiting Intel PXE ROM.
##################
Added
next-server
to My minimal dhcpd.conf & looks thus:
##################
ddns-update-style interim;
ignore client-updates;
subnet 172.16.0.0 netmask 255.255.255.0 {
option routers 172.16.0.254;
option subnet-mask 255.255.255.0;
host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
filename "pxelinux.0";
allow booting;
allow bootp;
range dynamic-bootp 172.16.0.128 172.16.0.254;
default-lease-time 21600;
max-lease-time 43200;
host ns {
next-server 172.16.0.254;
hardware ethernet 00:02:B3:99:05:A0;
# 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
fixed-address 172.16.0.254;
}
}
##################
> RgSalisbury wrote:
>>> Could you produce a wireshark trace of the traffic?
>>>
>> A little more with verbosity turned up & no arp messages
>>
#############################################################################
>>
>> 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none],
>> proto:
>> UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
>> "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
>>
>
> Did you set "next-server" in "dhcpd.conf"?
>
> Seems to me that the client tries to TFTP from 0.0.0.0, after retrieving
> "pxelinux.0".
>
> RHEL 5 might have a newer version "dhcpd" which no longer sets
> "next-server"
> to "boot/dhcp server" when missing in "dhcpd.conf".
>
> Axel
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date: 5/24/2007
> 4:01 PM
>
>