Network booting diskless computer

I'm trying to boot a diskless machine(2 scsi disks detached) but
facing many problems.
Please read the following and help me find problems.
I'll show you a few file and command outputs.


RH 9.0 with kernel 2.4.22 Diskless machine
------------------------- ----------------
DHCP Server Intel Boot Agent GE V1.2.11
NFS Server Client to be booted
TFTP Server
eth0 10.243.3.19/24 eth0 (not cabled)
eth1 192.168.1.1 <===========> eth1 (to be)192.168.1.11 (by
dhcpd.conf)

Two machines are directely connected, and both have 2 NICs.
Server has the other NIC for public networking.
I've configured dhcp server with dhcpd-0.3pl1-23.
Here's the dhcpd.conf

ddns-update-style interim;
default-lease-time 21500;
max-lease-time 43200;

option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;

shared-network platform2
{
subnet 10.243.3.19 netmask 255.255.255.0
{
}

subnet 192.168.1.0 netmask 255.255.255.0
{
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.1.11 192.168.1.100; #
not dynamic!
default-lease-time 21600;
max-lease-time 43200;
}
}

group
{
use-host-decl-names on;
option log-servers 192.168.1.1;

host spider2
{
hardware ethernet 00:03:47:f1:44:75;
fixed-address 192.168.1.11;
option root-path "192.168.1.1:/tftpboot/";
filename "vmlinuz";
}
}

-----------------------------------------------------------------------
This is the /etc/xinetd.d/tftp
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/tftpd
server_args = -s /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}


tftpd has come to be used(from src rpm) while trying to this job
instead of in.tftpd
provided by rh dist. for default.

and this is the output of ifconfig
[SERVER]
eth0 Link encap:Ethernet HWaddr 00:03:47:30:C0:E6
inet addr:10.243.3.195 Bcast:10.243.3.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:393331 errors:0 dropped:0 overruns:0 frame:0
TX packets:20441 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:108707310 (103.6 Mb) TX bytes:2235592 (2.1 Mb)
Interrupt:58 Base address:0x4040 Memory:feac0000-feae0000

eth1 Link encap:Ethernet HWaddr 00:03:47:30:C0:E7
inet addr:192.168.1.1 Bcast:192.168.1.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2923 errors:0 dropped:0 overruns:0 frame:0
TX packets:1467 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:746657 (729.1 Kb) TX bytes:1383045 (1.3 Mb)
Interrupt:59 Base address:0x4000 Memory:feae0000-feb00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2934 errors:0 dropped:0 overruns:0 frame:0
TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:839507 (819.8 Kb) TX bytes:839507 (819.8 Kb)


When client machine powers on, it shows,

Intel(R) Boot Agent GE v1.2.11
copyright (C) 1997-2003, Intel coorporation

CLIENT MAC ADDR: 00 03 47 F1 44 75 GUID: xxxxxxxxx xxxx xxxxxx
xxxxxxxxxxxxxxxxx
CLIENT IP : 192.168.1.1 MASK: 255.255.255.0 DHCP IP : 192.168.1.1
GATEWAY IP : 192.168.1.1

-> This changes to
PXE-E53: No boot filename received

PXE-M0F: Exiting Intel Boot Agent.
.....



I thought there's something wrong with tftp server but tftp server
itself is not to be blamed
as it works fine when i test put/get files from other networked hosts.

These are dumped from 'tcpdump -i eth1' and 'tail -f
/var/log/messages'
------------------------------- tcpdump -i eth1
--------------------------
18:51:00.325615 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x48f14474 secs:4 flags:0x8000 file ""[|bootp]
18:51:00.325955 arp who-has 192.168.1.100 tell 192.168.1.1
18:51:01.009093 192.168.1.1.bootps > 255.255.255.255.bootpc:
xid:0x48f14474 secs:4 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
18:51:01.318905 arp who-has 192.168.1.100 tell 192.168.1.1
18:51:02.311311 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x49f14474 secs:6 flags:0x8000 file ""[|bootp]
18:51:02.311687 192.168.1.1.bootps > 255.255.255.255.bootpc:
xid:0x49f14474 secs:6 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
18:51:02.318889 arp who-has 192.168.1.100 tell 192.168.1.1
18:51:06.320692 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4af14474 secs:10 flags:0x8000 file ""[|bootp]
18:51:06.320990 192.168.1.1.bootps > 255.255.255.255.bootpc:
xid:0x4af14474 secs:10 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
18:51:14.339700 0.0.0.0.bootpc > 255.255.255.255.bootps:
xid:0x4bf14474 secs:18 flags:0x8000 file ""[|bootp]
18:51:14.339996 192.168.1.1.bootps > 255.255.255.255.bootpc:
xid:0x4bf14474 secs:18 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
---------------------------- /var/log/messages
---------------------------
Oct 1 18:51:00 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
eth1
Oct 1 18:51:01 newton dhcpd: DHCPOFFER on 192.168.1.100 to
00:03:47:f1:44:74 via eth1
Oct 1 18:51:02 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
eth1
Oct 1 18:51:02 newton dhcpd: DHCPOFFER on 192.168.1.100 to
00:03:47:f1:44:74 via eth1
Oct 1 18:51:06 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
eth1
Oct 1 18:51:06 newton dhcpd: DHCPOFFER on 192.168.1.100 to
00:03:47:f1:44:74 via eth1
Oct 1 18:51:14 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
eth1
Oct 1 18:51:14 newton dhcpd: DHCPOFFER on 192.168.1.100 to
00:03:47:f1:44:74 via eth1
--------------------------------------------------------------------------

I can't figure out what is wrong, maybe the whole things i've done are
useless.
Any advice appreciated.

The MAC address that you reserve in dhcpd.conf is one off from the MAC
address in the tcpdumps (last byte 75 instead of 74).


--

wcardwell at nc dot rr dot com


"newton" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I'm trying to boot a diskless machine(2 scsi disks detached) but
> facing many problems.
> Please read the following and help me find problems.
> I'll show you a few file and command outputs.
>
>
> RH 9.0 with kernel 2.4.22 Diskless machine
> ------------------------- ----------------
> DHCP Server Intel Boot Agent GE V1.2.11
> NFS Server Client to be booted
> TFTP Server
> eth0 10.243.3.19/24 eth0 (not cabled)
> eth1 192.168.1.1 <===========> eth1 (to be)192.168.1.11 (by
> dhcpd.conf)
>
> Two machines are directely connected, and both have 2 NICs.
> Server has the other NIC for public networking.
> I've configured dhcp server with dhcpd-0.3pl1-23.
> Here's the dhcpd.conf
>
> ddns-update-style interim;
> default-lease-time 21500;
> max-lease-time 43200;
>
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> option routers 192.168.1.1;
>
> shared-network platform2
> {
> subnet 10.243.3.19 netmask 255.255.255.0
> {
> }
>
> subnet 192.168.1.0 netmask 255.255.255.0
> {
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
> range dynamic-bootp 192.168.1.11 192.168.1.100; #
> not dynamic!
> default-lease-time 21600;
> max-lease-time 43200;
> }
> }
>
> group
> {
> use-host-decl-names on;
> option log-servers 192.168.1.1;
>
> host spider2
> {
> hardware ethernet 00:03:47:f1:44:75;
> fixed-address 192.168.1.11;
> option root-path "192.168.1.1:/tftpboot/";
> filename "vmlinuz";
> }
> }
>
> -----------------------------------------------------------------------
> This is the /etc/xinetd.d/tftp
> service tftp
> {
> disable = no
> socket_type = dgram
> protocol = udp
> wait = yes
> user = root
> server = /usr/sbin/tftpd
> server_args = -s /tftpboot
> per_source = 11
> cps = 100 2
> flags = IPv4
> }
>
>
> tftpd has come to be used(from src rpm) while trying to this job
> instead of in.tftpd
> provided by rh dist. for default.
>
> and this is the output of ifconfig
> [SERVER]
> eth0 Link encap:Ethernet HWaddr 00:03:47:30:C0:E6
> inet addr:10.243.3.195 Bcast:10.243.3.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:393331 errors:0 dropped:0 overruns:0 frame:0
> TX packets:20441 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:108707310 (103.6 Mb) TX bytes:2235592 (2.1 Mb)
> Interrupt:58 Base address:0x4040 Memory:feac0000-feae0000
>
> eth1 Link encap:Ethernet HWaddr 00:03:47:30:C0:E7
> inet addr:192.168.1.1 Bcast:192.168.1.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2923 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1467 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:746657 (729.1 Kb) TX bytes:1383045 (1.3 Mb)
> Interrupt:59 Base address:0x4000 Memory:feae0000-feb00000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:2934 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:839507 (819.8 Kb) TX bytes:839507 (819.8 Kb)
>
>
> When client machine powers on, it shows,
>
> Intel(R) Boot Agent GE v1.2.11
> copyright (C) 1997-2003, Intel coorporation
>
> CLIENT MAC ADDR: 00 03 47 F1 44 75 GUID: xxxxxxxxx xxxx xxxxxx
> xxxxxxxxxxxxxxxxx
> CLIENT IP : 192.168.1.1 MASK: 255.255.255.0 DHCP IP : 192.168.1.1
> GATEWAY IP : 192.168.1.1
>
> -> This changes to
> PXE-E53: No boot filename received
>
> PXE-M0F: Exiting Intel Boot Agent.
> ....
>
>
>
> I thought there's something wrong with tftp server but tftp server
> itself is not to be blamed
> as it works fine when i test put/get files from other networked hosts.
>
> These are dumped from 'tcpdump -i eth1' and 'tail -f
> /var/log/messages'
> ------------------------------- tcpdump -i eth1
> --------------------------
> 18:51:00.325615 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x48f14474 secs:4 flags:0x8000 file ""[|bootp]
> 18:51:00.325955 arp who-has 192.168.1.100 tell 192.168.1.1
> 18:51:01.009093 192.168.1.1.bootps > 255.255.255.255.bootpc:
> xid:0x48f14474 secs:4 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> 18:51:01.318905 arp who-has 192.168.1.100 tell 192.168.1.1
> 18:51:02.311311 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x49f14474 secs:6 flags:0x8000 file ""[|bootp]
> 18:51:02.311687 192.168.1.1.bootps > 255.255.255.255.bootpc:
> xid:0x49f14474 secs:6 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> 18:51:02.318889 arp who-has 192.168.1.100 tell 192.168.1.1
> 18:51:06.320692 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x4af14474 secs:10 flags:0x8000 file ""[|bootp]
> 18:51:06.320990 192.168.1.1.bootps > 255.255.255.255.bootpc:
> xid:0x4af14474 secs:10 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> 18:51:14.339700 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x4bf14474 secs:18 flags:0x8000 file ""[|bootp]
> 18:51:14.339996 192.168.1.1.bootps > 255.255.255.255.bootpc:
> xid:0x4bf14474 secs:18 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> ---------------------------- /var/log/messages
> ---------------------------
> Oct 1 18:51:00 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> eth1
> Oct 1 18:51:01 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> 00:03:47:f1:44:74 via eth1
> Oct 1 18:51:02 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> eth1
> Oct 1 18:51:02 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> 00:03:47:f1:44:74 via eth1
> Oct 1 18:51:06 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> eth1
> Oct 1 18:51:06 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> 00:03:47:f1:44:74 via eth1
> Oct 1 18:51:14 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> eth1
> Oct 1 18:51:14 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> 00:03:47:f1:44:74 via eth1
> --------------------------------------------------------------------------
>
> I can't figure out what is wrong, maybe the whole things i've done are
> useless.
> Any advice appreciated.

Client machine also has 2 nic ports and it was my mistyping.
Anyway, i'm thinking of using pxe server for this job. but i'm not
sure whether
I could boot the target and nfs mount root fs but not
network-installation as I don't
need to install new o/s.
Is this possible?



"W Cardwell" <(E-Mail Removed)> wrote in message news:<nMzeb.15806$(E-Mail Removed) m>...
> The MAC address that you reserve in dhcpd.conf is one off from the MAC
> address in the tcpdumps (last byte 75 instead of 74).
>
>
> --
>
> wcardwell at nc dot rr dot com
>
>
> "newton" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > I'm trying to boot a diskless machine(2 scsi disks detached) but
> > facing many problems.
> > Please read the following and help me find problems.
> > I'll show you a few file and command outputs.
> >
> >
> > RH 9.0 with kernel 2.4.22 Diskless machine
> > ------------------------- ----------------
> > DHCP Server Intel Boot Agent GE V1.2.11
> > NFS Server Client to be booted
> > TFTP Server
> > eth0 10.243.3.19/24 eth0 (not cabled)
> > eth1 192.168.1.1 <===========> eth1 (to be)192.168.1.11 (by
> > dhcpd.conf)
> >
> > Two machines are directely connected, and both have 2 NICs.
> > Server has the other NIC for public networking.
> > I've configured dhcp server with dhcpd-0.3pl1-23.
> > Here's the dhcpd.conf
> >
> > ddns-update-style interim;
> > default-lease-time 21500;
> > max-lease-time 43200;
> >
> > option subnet-mask 255.255.255.0;
> > option broadcast-address 192.168.1.255;
> > option routers 192.168.1.1;
> >
> > shared-network platform2
> > {
> > subnet 10.243.3.19 netmask 255.255.255.0
> > {
> > }
> >
> > subnet 192.168.1.0 netmask 255.255.255.0
> > {
> > option routers 192.168.1.1;
> > option subnet-mask 255.255.255.0;
> > range dynamic-bootp 192.168.1.11 192.168.1.100; #
> > not dynamic!
> > default-lease-time 21600;
> > max-lease-time 43200;
> > }
> > }
> >
> > group
> > {
> > use-host-decl-names on;
> > option log-servers 192.168.1.1;
> >
> > host spider2
> > {
> > hardware ethernet 00:03:47:f1:44:75;
> > fixed-address 192.168.1.11;
> > option root-path "192.168.1.1:/tftpboot/";
> > filename "vmlinuz";
> > }
> > }
> >
> > -----------------------------------------------------------------------
> > This is the /etc/xinetd.d/tftp
> > service tftp
> > {
> > disable = no
> > socket_type = dgram
> > protocol = udp
> > wait = yes
> > user = root
> > server = /usr/sbin/tftpd
> > server_args = -s /tftpboot
> > per_source = 11
> > cps = 100 2
> > flags = IPv4
> > }
> >
> >
> > tftpd has come to be used(from src rpm) while trying to this job
> > instead of in.tftpd
> > provided by rh dist. for default.
> >
> > and this is the output of ifconfig
> > [SERVER]
> > eth0 Link encap:Ethernet HWaddr 00:03:47:30:C0:E6
> > inet addr:10.243.3.195 Bcast:10.243.3.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:393331 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:20441 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:108707310 (103.6 Mb) TX bytes:2235592 (2.1 Mb)
> > Interrupt:58 Base address:0x4040 Memory:feac0000-feae0000
> >
> > eth1 Link encap:Ethernet HWaddr 00:03:47:30:C0:E7
> > inet addr:192.168.1.1 Bcast:192.168.1.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2923 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1467 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:746657 (729.1 Kb) TX bytes:1383045 (1.3 Mb)
> > Interrupt:59 Base address:0x4000 Memory:feae0000-feb00000
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:2934 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:839507 (819.8 Kb) TX bytes:839507 (819.8 Kb)
> >
> >
> > When client machine powers on, it shows,
> >
> > Intel(R) Boot Agent GE v1.2.11
> > copyright (C) 1997-2003, Intel coorporation
> >
> > CLIENT MAC ADDR: 00 03 47 F1 44 75 GUID: xxxxxxxxx xxxx xxxxxx
> > xxxxxxxxxxxxxxxxx
> > CLIENT IP : 192.168.1.1 MASK: 255.255.255.0 DHCP IP : 192.168.1.1
> > GATEWAY IP : 192.168.1.1
> >
> > -> This changes to
> > PXE-E53: No boot filename received
> >
> > PXE-M0F: Exiting Intel Boot Agent.
> > ....
> >
> >
> >
> > I thought there's something wrong with tftp server but tftp server
> > itself is not to be blamed
> > as it works fine when i test put/get files from other networked hosts.
> >
> > These are dumped from 'tcpdump -i eth1' and 'tail -f
> > /var/log/messages'
> > ------------------------------- tcpdump -i eth1
> > --------------------------
> > 18:51:00.325615 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > xid:0x48f14474 secs:4 flags:0x8000 file ""[|bootp]
> > 18:51:00.325955 arp who-has 192.168.1.100 tell 192.168.1.1
> > 18:51:01.009093 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > xid:0x48f14474 secs:4 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> > 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > 18:51:01.318905 arp who-has 192.168.1.100 tell 192.168.1.1
> > 18:51:02.311311 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > xid:0x49f14474 secs:6 flags:0x8000 file ""[|bootp]
> > 18:51:02.311687 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > xid:0x49f14474 secs:6 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> > 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > 18:51:02.318889 arp who-has 192.168.1.100 tell 192.168.1.1
> > 18:51:06.320692 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > xid:0x4af14474 secs:10 flags:0x8000 file ""[|bootp]
> > 18:51:06.320990 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > xid:0x4af14474 secs:10 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> > ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > 18:51:14.339700 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > xid:0x4bf14474 secs:18 flags:0x8000 file ""[|bootp]
> > 18:51:14.339996 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > xid:0x4bf14474 secs:18 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> > ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > ---------------------------- /var/log/messages
> > ---------------------------
> > Oct 1 18:51:00 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > eth1
> > Oct 1 18:51:01 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > 00:03:47:f1:44:74 via eth1
> > Oct 1 18:51:02 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > eth1
> > Oct 1 18:51:02 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > 00:03:47:f1:44:74 via eth1
> > Oct 1 18:51:06 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > eth1
> > Oct 1 18:51:06 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > 00:03:47:f1:44:74 via eth1
> > Oct 1 18:51:14 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > eth1
> > Oct 1 18:51:14 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > 00:03:47:f1:44:74 via eth1
> > --------------------------------------------------------------------------
> >
> > I can't figure out what is wrong, maybe the whole things i've done are
> > useless.
> > Any advice appreciated.

Yes. A couple of good docs are at http://syslinux.zytor.com/pxe.php and
http://www.tldp.org/HOWTO/NFS-Root.html.

--

wcardwell at nc dot rr dot com


"newton" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Client machine also has 2 nic ports and it was my mistyping.
> Anyway, i'm thinking of using pxe server for this job. but i'm not
> sure whether
> I could boot the target and nfs mount root fs but not
> network-installation as I don't
> need to install new o/s.
> Is this possible?
>
>
>
> "W Cardwell" <(E-Mail Removed)> wrote in message
news:<nMzeb.15806$(E-Mail Removed) m>...
> > The MAC address that you reserve in dhcpd.conf is one off from the MAC
> > address in the tcpdumps (last byte 75 instead of 74).
> >
> >
> > --
> >
> > wcardwell at nc dot rr dot com
> >
> >
> > "newton" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) om...
> > > I'm trying to boot a diskless machine(2 scsi disks detached) but
> > > facing many problems.
> > > Please read the following and help me find problems.
> > > I'll show you a few file and command outputs.
> > >
> > >
> > > RH 9.0 with kernel 2.4.22 Diskless machine
> > > ------------------------- ----------------
> > > DHCP Server Intel Boot Agent GE V1.2.11
> > > NFS Server Client to be booted
> > > TFTP Server
> > > eth0 10.243.3.19/24 eth0 (not cabled)
> > > eth1 192.168.1.1 <===========> eth1 (to be)192.168.1.11 (by
> > > dhcpd.conf)
> > >
> > > Two machines are directely connected, and both have 2 NICs.
> > > Server has the other NIC for public networking.
> > > I've configured dhcp server with dhcpd-0.3pl1-23.
> > > Here's the dhcpd.conf
> > >
> > > ddns-update-style interim;
> > > default-lease-time 21500;
> > > max-lease-time 43200;
> > >
> > > option subnet-mask 255.255.255.0;
> > > option broadcast-address 192.168.1.255;
> > > option routers 192.168.1.1;
> > >
> > > shared-network platform2
> > > {
> > > subnet 10.243.3.19 netmask 255.255.255.0
> > > {
> > > }
> > >
> > > subnet 192.168.1.0 netmask 255.255.255.0
> > > {
> > > option routers 192.168.1.1;
> > > option subnet-mask 255.255.255.0;
> > > range dynamic-bootp 192.168.1.11 192.168.1.100; #
> > > not dynamic!
> > > default-lease-time 21600;
> > > max-lease-time 43200;
> > > }
> > > }
> > >
> > > group
> > > {
> > > use-host-decl-names on;
> > > option log-servers 192.168.1.1;
> > >
> > > host spider2
> > > {
> > > hardware ethernet 00:03:47:f1:44:75;
> > > fixed-address 192.168.1.11;
> > > option root-path "192.168.1.1:/tftpboot/";
> > > filename "vmlinuz";
> > > }
> > > }
> > >
> >
> -----------------------------------------------------------------------
> > > This is the /etc/xinetd.d/tftp
> > > service tftp
> > > {
> > > disable = no
> > > socket_type = dgram
> > > protocol = udp
> > > wait = yes
> > > user = root
> > > server = /usr/sbin/tftpd
> > > server_args = -s /tftpboot
> > > per_source = 11
> > > cps = 100 2
> > > flags = IPv4
> > > }
> > >
> > >
> > > tftpd has come to be used(from src rpm) while trying to this job
> > > instead of in.tftpd
> > > provided by rh dist. for default.
> > >
> > > and this is the output of ifconfig
> > > [SERVER]
> > > eth0 Link encap:Ethernet HWaddr 00:03:47:30:C0:E6
> > > inet addr:10.243.3.195 Bcast:10.243.3.255
> > > Mask:255.255.255.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:393331 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:20441 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:100
> > > RX bytes:108707310 (103.6 Mb) TX bytes:2235592 (2.1 Mb)
> > > Interrupt:58 Base address:0x4040 Memory:feac0000-feae0000
> > >
> > > eth1 Link encap:Ethernet HWaddr 00:03:47:30:C0:E7
> > > inet addr:192.168.1.1 Bcast:192.168.1.255
> > > Mask:255.255.255.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:2923 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:1467 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:100
> > > RX bytes:746657 (729.1 Kb) TX bytes:1383045 (1.3 Mb)
> > > Interrupt:59 Base address:0x4000 Memory:feae0000-feb00000
> > >
> > > lo Link encap:Local Loopback
> > > inet addr:127.0.0.1 Mask:255.0.0.0
> > > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > > RX packets:2934 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:839507 (819.8 Kb) TX bytes:839507 (819.8 Kb)
> > >
> > >
> > > When client machine powers on, it shows,
> > >
> > > Intel(R) Boot Agent GE v1.2.11
> > > copyright (C) 1997-2003, Intel coorporation
> > >
> > > CLIENT MAC ADDR: 00 03 47 F1 44 75 GUID: xxxxxxxxx xxxx xxxxxx
> > > xxxxxxxxxxxxxxxxx
> > > CLIENT IP : 192.168.1.1 MASK: 255.255.255.0 DHCP IP : 192.168.1.1
> > > GATEWAY IP : 192.168.1.1
> > >
> > > -> This changes to
> > > PXE-E53: No boot filename received
> > >
> > > PXE-M0F: Exiting Intel Boot Agent.
> > > ....
> > >
> > >
> > >
> > > I thought there's something wrong with tftp server but tftp server
> > > itself is not to be blamed
> > > as it works fine when i test put/get files from other networked hosts.
> > >
> > > These are dumped from 'tcpdump -i eth1' and 'tail -f
> > > /var/log/messages'
> > > ------------------------------- tcpdump -i eth1
> > > --------------------------
> > > 18:51:00.325615 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > > xid:0x48f14474 secs:4 flags:0x8000 file ""[|bootp]
> > > 18:51:00.325955 arp who-has 192.168.1.100 tell 192.168.1.1
> > > 18:51:01.009093 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > > xid:0x48f14474 secs:4 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> > > 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > > 18:51:01.318905 arp who-has 192.168.1.100 tell 192.168.1.1
> > > 18:51:02.311311 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > > xid:0x49f14474 secs:6 flags:0x8000 file ""[|bootp]
> > > 18:51:02.311687 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > > xid:0x49f14474 secs:6 flags:0x8000 Y:192.168.1.100 S:192.168.1.1 ether
> > > 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > > 18:51:02.318889 arp who-has 192.168.1.100 tell 192.168.1.1
> > > 18:51:06.320692 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > > xid:0x4af14474 secs:10 flags:0x8000 file ""[|bootp]
> > > 18:51:06.320990 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > > xid:0x4af14474 secs:10 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> > > ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > > 18:51:14.339700 0.0.0.0.bootpc > 255.255.255.255.bootps:
> > > xid:0x4bf14474 secs:18 flags:0x8000 file ""[|bootp]
> > > 18:51:14.339996 192.168.1.1.bootps > 255.255.255.255.bootpc:
> > > xid:0x4bf14474 secs:18 flags:0x8000 Y:192.168.1.100 S:192.168.1.1
> > > ether 0:3:47:f1:44:74 file ""[|bootp] [tos 0x10]
> > > ---------------------------- /var/log/messages
> > > ---------------------------
> > > Oct 1 18:51:00 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > > eth1
> > > Oct 1 18:51:01 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > > 00:03:47:f1:44:74 via eth1
> > > Oct 1 18:51:02 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > > eth1
> > > Oct 1 18:51:02 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > > 00:03:47:f1:44:74 via eth1
> > > Oct 1 18:51:06 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > > eth1
> > > Oct 1 18:51:06 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > > 00:03:47:f1:44:74 via eth1
> > > Oct 1 18:51:14 newton dhcpd: DHCPDISCOVER from 00:03:47:f1:44:74 via
> > > eth1
> > > Oct 1 18:51:14 newton dhcpd: DHCPOFFER on 192.168.1.100 to
> > > 00:03:47:f1:44:74 via eth1
> >
> --------------------------------------------------------------------------
> > >
> > > I can't figure out what is wrong, maybe the whole things i've done are
> > > useless.
> > > Any advice appreciated.