Article View: comp.sys.sequent
Article #41Re: Sequent/Sun connection prob.
From: James S. Vera
Date: Fri, 07 Aug 1992 22:32
Date: Fri, 07 Aug 1992 22:32
22 lines
1395 bytes
1395 bytes
We had this problem when we first got some Sparc 2s. Seems whats
happening is that the Sparc 2s are so fast that they answer the
Sequent's arp request before the Sequent is ready to head it. The
solution was to make the arp entries for our 2s permanent on the
Sequent. This was done by putting the following in our rc.local
# make permanent arp entries for machines that respond to arp requests
if [ -f /etc/arp.init ]; then
/usr/etc/arp -f /etc/arp.init && \
echo 'local arp entries.' >/dev/console
and then creating the file /etc/arp.init which contained all of our
2's ethernet address, e.g.,
fanaraaken 8:0:20:10:94:10
...
That fixed things completely.
James S. Vera | Internet |Standard Disclaimers
Stanford University| vera@anna.stanford.edu |Blah Blah Blah Blah
+1.415.723.1089 | FAX +1.415.725.7398 |
Technical Details
Message-ID:
<vera.713226741@fanaraaken.Stanford.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!leland.Stanford.EDU!fanaraaken.Stanford.EDU!veraReferences:
<1992Aug6.100749.3276@aston.ac.uk>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.sequent Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!leland.Stanford.EDU!fanaraaken.Stanford.EDU!vera From: vera@fanaraaken.Stanford.EDU (James S. Vera) Subject: Re: Sequent/Sun connection prob. Message-ID: <vera.713226741@fanaraaken.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: Program Analysis and Verification Group, Stanford University References: <1992Aug6.100749.3276@aston.ac.uk> Date: 7 Aug 92 22:32:21 GMT Lines: 23