Booting via PXE/TFTP problem

freeindy · 02-28-2008, 07:15 AM

Hi,

I have the following configuration:

HOST:

Code:

Suse Linux Enterprise Server 10 (i586) with patchlevel 1
TFTP and NFS installed an running (AFAIK)
IP: 172.25.2.88

Target:

Code:

i686 machine that is diskless.
IP: 172.25.2.104

The host and target connected to a local network and they both have NETMASK 255.255.0.0.

On target side, I have set in the bios that it should boot using PXE and I get the following output at bootup:

Code:

Intel(R) Boot Agent FE v4.1.18                                      
Copyright (C) 1997-2005, Intel Corporation                          


Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 084)               
Copyright (C) 1997-2005, Intel Corporation                          


CLIENT MAC ADDR: 00 A0 A5 5D AD 81  GUID: 00020003 0004 0005 0006 000700080009
CLIENT IP: 172.25.2.104  MASK: 255.255.0.0  DHCP IP: 172.21.1.11    
GATEWAY IP: 172.25.0.254                                            


Press F12 for network service boot                                  
PXE-M0F: Exiting Intel Boot Agent.                                  

Retrying boot sequence...

And so it keeps rebooting and getting the ip address.

I have never done nfs booting as such so I really have no idea what the problem is.

Does anyone knows?

Thanks a million.
Indy

paragkalra · 02-28-2008, 08:44 AM

Well I can surely help you on this....I need following inputs......

1.] Start the installation from the host and execute:
#tcpdump -w <any file name>

Open this file with the utility called "ethereal" and see what exactly is happening and where actually is the bottleneck.

2.] Also when you start the installation on the target, from the host paste the output of following command:
#cat /var/log/messages

3.] Can you check if iptables is running on the host, if yes first stop it and then try the installation on the target and let us know how it goes.

freeindy · 02-28-2008, 01:13 PM

Hi paragkalra,

Analysing the ethereal app with tcpdump, there are several logs from the target:

Code:

No Time    Source       Destination   Protocol   Info
xx xxx  172.25.2.104     Broadcast       ARP     Who has 172.25.0.254  Tell 172.25.2.104

It also has the right mac address from the target.

From the /var/log/messages:

Code:

Jun  2 19:17:07 testserver kernel: device eth0 entered promiscuous mode
Jun  2 19:17:07 testserver kernel: audit(1180804627.254:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
Jun  2 19:17:07 testserver kernel: klogd 1.4.1, ---------- state change ----------
Jun  2 19:17:18 testserver kernel: device eth0 left promiscuous mode
Jun  2 19:17:18 testserver kernel: audit(1180804638.491:3): dev=eth0 prom=0 old_prom=256 auid=4294967295
Jun  2 19:17:28 testserver kernel: device eth0 entered promiscuous mode
Jun  2 19:17:28 testserver kernel: audit(1180804648.124:4): dev=eth0 prom=256 old_prom=0 auid=4294967295
Jun  2 19:18:42 testserver kernel: device eth0 left promiscuous mode
Jun  2 19:18:42 testserver kernel: audit(1180804722.564:5): dev=eth0 prom=0 old_prom=256 auid=4294967295
Jun  2 19:26:20 testserver kernel: device eth0 entered promiscuous mode
Jun  2 19:26:20 testserver kernel: audit(1180805180.589:6): dev=eth0 prom=256 old_prom=0 auid=4294967295
Jun  2 19:27:27 testserver kernel: device eth0 left promiscuous mode
Jun  2 19:27:27 testserver kernel: audit(1180805247.977:7): dev=eth0 prom=0 old_prom=256 auid=4294967295

The date is inacurrate but i suppose that it shouldn't be a problem.

Any help?

Indy

paragkalra · 02-29-2008, 05:54 AM

I want to have look at entire "/var/log/messages" and "tcpdump" output from the instant installation starts at host and to the instant it fails at target. I don't know whether it can be uploaded at LQ or not but in any case you can mail me [paragkalra@gmail.com].

Have you checked iptables on the host?

freeindy · 02-29-2008, 07:08 AM

No, iptables is not running. I don't know how to run it :-P.

Is there a special way of setting it?

freeindy · 02-29-2008, 09:49 AM

I sent you the files to your mail.

indy

arno · 02-29-2008, 05:38 PM

Your dhcp configuration is wrong with the current mask the client wont be able to make a connection to the dhcp server

CLIENT IP: 172.25.2.104 MASK: 255.255.0.0 DHCP IP: 172.21.1.11

change the mask in 255.0.0.0 ( which i dont recommend)
or change the dhcp server to 172.25.1.11
or the client to 172.21.2.104

paragkalra · 03-01-2008, 10:02 AM

I guess arno is right......