net boot problem

2007-12-25 8:25:00

I had written:

> Can someone please suggest where to look for the cause of a diskless boot

> failure (4/65 booting brom a 6/690) where the complaint is

>

> receive failed (file not found)

>

> It appears that the client is not receiving its ip address back

> from the rarp process on the server, as the error occurs before

> the "using ip address" (which never appears)

> and etherfind shows no sign of packets with that ip.

>

> THe hardware is good, as is the network connection as the client machine is

> actually a healthy diskful machine that is only being booted remote to do a

> full install from a remote cd.

Many responses, most pointing to probable problems in the /tftpboot

symbolic links to the boot file, which I was so sure were OK that I hadn't even

checked them except to make sure that the [ip-address].SUN4C link pointed

to the correct file. DUMB DUMB DUMB...I had used the ip address of the

machine in its diskful incarnation, not the generic name and address set

up specifically for diskless boots while upgrading!!!

It turns out, contrary to my post, that the rarp was OK -- thanks to

Bill Hunter who reminded me to kill rarpd and rpc.bootparamd and run then

in a command window with "-d" flags for debugging. THat's what showed

that the rarp was working.

Thanks to:

 eckhard@ts.go.dlr.de (Eckhard Rueggeberg)

 bill@hobbes.access.com ( Bill Hunter [Instructor / Tech Support])

 Manish Bhatia <manish@prentice.COM>

Matt_Mauss_-T@hqdev.3mail.3com.com

 kovert@cs.UMD.EDU

 fallan@baobab.awadi.com.AU

strombrg@hydra.acs.uci.edu

 poffen@sj.ate.slb.com (Russ Poffenberger)

  Jeff Fookson jeff@cns.nyu.edu

  Center for Neural Science, New York University

Comments

Got something to say?

You must be logged in to post a comment.