[HECnet] Multinet Tunnel Links defined - area 13
Johnny Billquist
bqt at softjar.se
Thu Dec 22 02:18:31 PST 2011
On 2011-12-22 10:22, hvlems at zonnet.nl wrote:
As everybody here knows, Decservers don't use decnet but needed an entry in the ncp database for MOM to figure
out where the software was to be found. Later on LANCP was introduced for that purpose.
Actually not really true. Or maybe that is true for VMS then. It is not true for RSX. RSX boots DECservers happily without any information in the nodename database.
And you can also connect to the admin serial port with MOP without having an entry in the nodename database.
Since we're not exactly short of areas, let alone node addresses there's no reason why we cannot reserve an area
for them. OTOH I doubt we'll boot a decserver across the bridges (perhaps Sampsa will try that). So I'll keep my
DS100 in area 44, it is 44.8 (ASTAAT, At).
We're not short on either, but we are definitely much closer to running out of areas than node numbers. At the moment, we are standing at 28 allocated areas, soon to be atleast 29. That is close to 50%.
But I'll leave area 13 alone for now, to make you happy. :-)
And for your information, MIM regularly boots DECservers over the bridge... Mine and Updates, but occasionally also others. And RSX normally starts booting a DECserver before VMS have even started thinking about the request. :-)
To quote a piece of the RSX kernel:
;+
; If we cannot process a clock interrupt within 10 seconds, we are
; no longer processing in real time, and we may as well become
; a VAX ... Call an end to this ... NOW!
;-
BGCK$A BF.SAN,BE.IDC,<FATAL> ;;; System massively confused
:-)
Johnny
-----Original Message-----
From: Johnny Billquist<bqt at softjar.se>
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 22 Dec 2011 04:11:10
To:<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Multinet Tunnel Links defined
On 2011-12-22 04:04, Steve Davidson wrote:
Two things:
First I would like to continue to reserve area 13. All the
documentation about DECserver management refers to it.
Could you point me to some of that documentation? I've not seen any of
it, and I don't really at all understand the point of even setting up
information in the nodename database for DECservers, which don't even
speak DECnet to begin with. (And I do have DECservers up and running, as
well as manuals...)
I know that, from a convenience point of view, you can use the name as a
short cut for specifying the MAC address and circuit, but having an area
reserved for such a simple detail seems excessive.
Second SG1 is a VS4000/30 (VLC). It is small, quiet, and cheap to run -
all very important features. If I remember correctly, LEGATO is the
same platform for the exact purpose. The only difference between my
Multnet "gateway" is that it can accommodate dynamic-DNS at the other
end.
Cool. I guess that platform should be enough to handle normal HECnet
traffic even if we grow some more.
How do you deal with dynamic IP addresses?
PS One more network is in the wings. You should be getting email about
it soon enough if you have not already.
Nothing yet.
Johnny
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, December 21, 2011 9:58 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Multinet Tunnel Links defined
Current list as of right now:
.ncp sho act are
Active areas summary as of 22-DEC-11 03:53:33
Next
Area State Circuit Node
1 Reachable 1.13 (MIM)
2 Reachable UNA-0 19.41 (SG1)
3 Reachable UNA-0 19.41 (SG1)
4 Reachable UNA-0 4.249 (SLAVE)
6 Reachable UNA-0 6.1 (STAR69)
8 Reachable UNA-0 19.41 (SG1)
11 Reachable UNA-0 11.2 (MAISA)
19 Reachable UNA-0 19.41 (SG1)
20 Reachable UNA-0 19.41 (SG1)
33 Reachable UNA-0 19.41 (SG1)
42 Reachable UNA-0 42.1 (CANADA)
44 Reachable UNA-0 44.21 (NIKKEL)
54 Reachable UNA-0 19.41 (SG1)
59 Reachable UNA-0 19.41 (SG1)
.
That is 14 areas, and I'm talking to one more guy who wants a new area,
which would bring us to 15.
Anyone object to me giving him area 13? It was asked to be reserved for
DECserver management, but I don't really see the point of having an area
for that purpose. But if you can convince me... :-)
Also, SG1:: is quite a hub from the bridge point of view. Lots of
connections coming through there. Nice. :-) What type of machine is it?
Johnny
On 2011-12-21 18:29, Steve Davidson wrote:
At the moment 13 areas are up and running - this list only show 10.
Hopefully sometime today we will be at 14. We're working on it! :-)
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Tuesday, December 20, 2011 5:44 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Multinet Tunnel Links defined
On 2011-12-20 22:34, Steve Davidson wrote:
I have defined (or redefined) tunnels for areas 3 and 6 for both
GORVAX:: and SG1::. These are effective immediately. Enjoy!
Cool. Area 3 is up according to MIM. Pretty...
.ncp sho act are
Active areas summary as of 20-DEC-11 23:42:41
Next
Area State Circuit Node
1 Reachable 1.13 (MIM)
3 Reachable UNA-0 19.41 (SG1)
4 Reachable UNA-0 4.249 (SLAVE)
6 Reachable UNA-0 19.41 (SG1)
8 Reachable UNA-0 19.41 (SG1)
11 Reachable UNA-0 11.2 (MAISA)
19 Reachable UNA-0 19.41 (SG1)
20 Reachable UNA-0 19.41 (SG1)
33 Reachable UNA-0 19.41 (SG1)
42 Reachable UNA-0 42.1 (CANADA)
.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
More information about the Hecnet-list
mailing list