cpw%sneezy@LANL.GOV (C. Philip Wood) (08/26/87)
Excuse if you already know about this problem. But, a recent release of software for the Celerity OS caused a big headache here at LANL. The symptom was Suns and Symbolics machines could not boot or communicate because they could not find out their internet addresses via RARP. Or, rather, they found out a wrong address, namely 0.0.0.0. This tidbit of information was provided by the Celerity RARP handler. I give credit to Celerity for finding out about the problem and fixing it. However, it took some sluthing with etherfind to figure out who the culprit was on our part. And, then finding the offending piece of hardware, and then finding someone who would take responsibility for it, and then calling up Celerity support. Once we got that far the fix was easy. Run ifconfig with the -arp option, and wait for the patch tapes in the mail. The came the next day. Phil Wood (cpw@lanl.gov)
DCP@QUABBIN.SCRC.Symbolics.COM (David C. Plummer) (08/27/87)
Date: Wed, 26 Aug 87 12:08:16 MDT
From: cpw%sneezy@LANL.GOV (C. Philip Wood)
Excuse if you already know about this problem. But,
a recent release of software for the Celerity OS caused
a big headache here at LANL. The symptom was Suns and
Symbolics machines could not boot or communicate because
they could not find out their internet addresses via RARP.
Point of information: The released Symbolics system does not use RARP at
all. (It normally gets it's Internet address from the namespace object
for the host, which it finds from the chaos address, which is specified
in the boot file.) I suspect the Symbolics systems couldn't boot for
some other reason, such as failing to get valid ARP responses from the
servers.
Or, rather, they found out a wrong address, namely 0.0.0.0.
This tidbit of information was provided by the Celerity RARP
handler.
I give credit to Celerity for finding out about the problem and
fixing it. However, it took some sluthing with etherfind to figure
out who the culprit was on our part. And, then finding the offending
piece of hardware, and then finding someone who would take responsibility
for it, and then calling up Celerity support. Once we got that far
the fix was easy. Run ifconfig with the -arp option, and wait for
the patch tapes in the mail. The came the next day.
Phil Wood (cpw@lanl.gov)