GROVER@IUBACS.BITNET (05/25/88)
We faced the area numbering problem about a year ago when we wanted to bring onto our local DECnet a Vax already a node in HEPnet. We talked with Phil DeMar also, and ultimately applied the mechanism he describes in the document previously referenced here. It provides a simple and clever solution to the problem, and we have had no difficulties whatsoever since changing numbers. The change itself requires no small amount of coordination, however, especially if many nodes on your net are not under your administrative control. (It's amazing how fast your network grows when you attach to a net with conflicting DECnet area numbers! :-)) Doug Grover Operations Manager Academic Computing Indiana University, Bloomington
GROVER%IUBACS.BITNET%CORNELLC.CCS.CORNELL.EDU%KL.SRI.COM%lbl%sfsu1.hepnet@LBL.GOV (05/28/88)
Received: from KL.SRI.COM by LBL.Gov with INTERNET ;
Fri, 27 May 88 02:04:37 PDT
Received: from CORNELLC.CCS.CORNELL.EDU by KL.SRI.COM with TCP; Wed 25 May 88 11:36:59-PDT
Received: from IUBACS.BITNET by CORNELLC.CCS.CORNELL.EDU ; Wed, 25 May 88 14:16:08 EDT
Date: Wed, 25 May 88 08:08 EST
From: <GROVER%IUBACS.BITNET@CORNELLC.CCS.CORNELL.EDU>
Subject: DECnet area renumbering
To: info-vax@kl.sri.com
X-Original-To: info-vax@kl.sri.com, GROVER
We faced the area numbering problem about a year ago when we wanted to
bring onto our local DECnet a Vax already a node in HEPnet. We talked
with Phil DeMar also, and ultimately applied the mechanism he describes
in the document previously referenced here. It provides a simple and
clever solution to the problem, and we have had no difficulties whatsoever
since changing numbers. The change itself requires no small amount
of coordination, however, especially if many nodes on your net are not
under your administrative control.
(It's amazing how fast your network grows when you attach to a net with
conflicting DECnet area numbers! :-))
Doug Grover
Operations Manager
Academic Computing
Indiana University, Bloomington