[Etherboot-users] DHCP- Etherboot not sending DHCPREQUEST

[David T. P. <phe...@un...>]

Hello,

    I am trying to install Rocks 4.1 Fuji on a 25 node LinuxNewtorx=20
cluster that was donated to my college. Each node has only a power,
 serial console, and network connections. There is no cdrom or floppy =
drive,=20
so PXE booting these nodes is my only method of installing an OS on=20
these machines.

    The nodes have a LinuxBIOS and Etherboot5.0.4eb4.1 burned onto the =
prom.
My problem is that my nodes are not sending a DHCPREQUEST
to the frontend (DHCP) server.

    I have worked with DHCP a number of times but never had this=20
problem. However, this is my first time trying to use PXE booting. Here =
is the output of `tail /var/log/messages` when I power on the first =
node:

Nov  7 12:36:41 manganese dhcpd: DHCPDISCOVER from 00:30:48:22:b7:3f via =

eth0
Nov  7 12:36:41 manganese dhcpd: DHCPOFFER on 192.168.1.253 to=20
00:30:48:22:b7:3f via eth0
Nov  7 12:36:41 manganese dhcpd: DHCPDISCOVER from 00:30:48:22:b7:3f via =

eth0
Nov  7 12:36:41 manganese dhcpd: DHCPOFFER on 192.168.1.253 to=20
00:30:48:22:b7:3f via eth0

The node itself shows:

=FCROM segment 0xc800 length 0x4000 reloc 0x9400
Etherboot 5.0.4eb4.1 (GPL) Tagged ELF (Multiboot) for [EEPRO100]
Boot from (N)etwork or from (L)ocal? N
Found Intel EtherExpressPro100 at 0XC000, ROM address 0X0000
Probing...[EEPRO100]Ethernet addr: 00:30:48:22:B7:3F
Searching for server (DHCP)...
....................No Server found
<abort>
Boot from (N)etwork or from (L)ocal?

    The cluster is on its own network, with a single HP ProCurve 4108GL=20
switch. I searched the Rocks mailinglist archives to see if this problem =

has occurred before, and came across a thread relating my
troubles to the Spanning Tree settings of a SMC switch. I have reset my=20
switch to factory default, re-configured it and made sure the Spanning=20
Tree Edge was set to 'Yes'. When that didn't work, I tried a 12 port=20
unmanaged switch and still had my DHCP problem.
If I connect a laptop to the network, it receives a DHCP address=20
correctly, as does the DHCP client of the switch (for connecting to it=20
and managing it). So, I KNOW dhcp works. I just can't figure out why=20
certain clients will have a successful DHCP transaction and my nodes =
won't.

Any ideas?

Thank you in advance,

--David

--=20



****************************
****************************
**  David T. Pheasant     **
**  Computer Engineering  **
**  Union College 2006    **
**                        **
**  phe...@un...    **
****************************
****************************