Bugs item #1029243, was opened at 2004-09-16 07:53
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1029243&group_id=259
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: systemimager-client
Group: v3.2.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: A Baggarley (abaggnc)
Assigned to: Nobody/Anonymous (nobody)
Summary: PXE clients do not seem to find files
Initial Comment:
The clients get an IP address then they seem to locate
the TFTP server but never start pulling files....
Here is what I see .... or think I see because it scrolls
so quickly
UNDI data segment at : 0097ZC0
UNDI data segment size: 58D0
UNDI code segment at: 009CB90
UNDI code segment size: 2470
PXE entry point founf (we hope) at 9CB9:00CC
My IP adress seems to be 0A14E6C8 10.20.230.200
IP
10.20.230.200:10.20.230.132:10.20.230.1:255.255.255.0
TFTP prefix:
Trying to load prelinux.cfg/0A14E6C8
Booting form local disk:
opening: prelinux.cfg/0A14E6C8
opening: prelinux.cfg/0A14E6C
opening: prelinux.cfg/0A14E6
opening: prelinux.cfg/0A14E
opening: prelinux.cfg/0A14
opening: prelinux.cfg/0A
opening: prelinux.cfg/0
opening: prelinux.cfg
then there is a line or two more but they go by so
quickly I can not get a pause...
Does anyone have any idea what I am or am not doing
right .... I need to image about 4000 machines and was
hoping to use flamethrower with a PXE boot since the
devices do not have a floppy controller onboard and
mkautoinstalldiskette only associates the floppy drive
with fd0-fd7, not my usb /sda
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-01-15 06:46
Message:
Logged In: NO
Hi,
same problem with me i have successfully run mkclientnetboot command after
that is not working.
Thnx
Neeraj Dwivedi
System admin
India
----------------------------------------------------------------------
Comment By: Jerry DeLapp (jerrygd)
Date: 2005-01-04 22:24
Message:
Logged In: YES
user_id=512778
I think... which means I haven't verified this...
The default pxe config in recent versions of systemimager
presumes that you have already imaged and that you
"really" wish to boot from your hard drive.
You need to run mkclientnetboot for the clients in
question to reconfig your tftp server to send the
"systemimager netboot" config to the client. The
following option is from the mkclientnetboot man page:
--clients "HOST1 HOST2 ..."
A space seperated list of host names
and/or dotted quad IP
addresses. This server (assuming it is a
boot server) will be
told to let these clients net boot from
this server, at least
until they?ve completed a successful
SystemImager autoinstall.
End of excerpt from manpage
Similarly, once you've successfully netbooted, you can run
mkclientnetboot to "switch back" to the local disk pxe
config. Read the man page for more details
HTH
J
----------------------------------------------------------------------
Comment By: Peter Sturdza (sturdza)
Date: 2005-01-04 20:40
Message:
Logged In: YES
user_id=542857
I have been having the same problem with SystemImager 3.2.3.
My only workaround is using a second server to run tftp
that is set up with the tools from SystemImager 3.0.1
(mkbootserver). Then, in the image server that runs 3.2.3,
the next-server line in the dhcpd.conf file points to the
second server. I copied the boot kernel and image file from
the 3.2.3 server to the /tftpboot directory of the second
server.
I don't understand why this fails under 3.2.3 since both
servers are running the same version of tftp and the same
operating systems (old RedHat 8.0).
SI 3.2.3 fails in the same way when run on Suse 9.1. I'm
using Intel PRO/1000 MT gigabit cards.
----------------------------------------------------------------------
Comment By: A Baggarley (abaggnc)
Date: 2004-10-20 10:03
Message:
Logged In: YES
user_id=1122913
You are correct it actually says pxelinux not prelinux.cfg.
Have not been able to test the tftp yet for the box
continually reboots once it fials to find the files.
And yes mkdhcpserver has been run
----------------------------------------------------------------------
Comment By: Brian Elliott Finley (brianfinley)
Date: 2004-10-18 21:27
Message:
Logged In: YES
user_id=140
Just noticed your bit about what you "think" you see. I was
wondering if some new kind of firmware was out. Heh.
Anywho, if you pause it, or capture the output from a serial
console, can you see if it actually says "pxelinux.cfg"?
Can you still try the tftp test I mention, only try to grab
the following file, which may be the last one scrolling off
your screen:
pxelinux.cfg/default
One other question: have you run "mkdhcpserver"?
----------------------------------------------------------------------
Comment By: Brian Elliott Finley (brianfinley)
Date: 2004-10-18 21:05
Message:
Logged In: YES
user_id=140
First, I would have expected it to say "pxelinux.cfg/"
instead of "prelinux.cfg". So, assuming that the only
difference in this firmware is filenames (which may be a bad
assumption) what you can do is the following, and it will
probably work:
cd /tftpboot
mv pxelinux.cfg prelinux.cfg
ln -s prelinux.cfg pxelinux.cfg # there may be some SI
things that look for this
cp prelinux.cfg/default prelinux.cfg/0
Then test your tftp configuration manually, to see if you
can retrieve the default config file (now named "0"):
cd /tmp/
tftp servername
tftp> get prelinux.cfg/0
Received 173 bytes in 0.2 seconds
tftp>
Cheers!
-Brian
----------------------------------------------------------------------
Comment By: Ray Van dolson (rayvd)
Date: 2004-10-18 17:19
Message:
Logged In: YES
user_id=31335
This exact thing happens on our HP DL140 server as well.
These boxes have Broadcom BCM5704 gigabit cards in them. I
get nearly the same output as above, except that it makes an
attempt to read prelinux.cfg/default and then tries to boot
from the hard disk (which of course fails).
Maybe this is just an issue with my NIC. It seems HP has a
PXE patch of some sort out for these systems, but as they
only seem to come in .rpm format, they aren't too useful as
far as applying to a virgin system. :-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1029243&group_id=259
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
