You know, I had wondered why APOLLO had dropped offline...
!i dec
?Local DECNET node: VENTI2.? Nodes reachable: 6.
?Accessible DECNET nodes are:??? A2RTR??? APOLLO??? LEGATO TOMMYT???
VENTI2??? ZITI
!opr.EXE.1
OPR>ent nc
NCP>shoW adJACENT NODES
NCP>
21:58:41 ??? NCP
Request # 183; Show Adjacent Nodes Summary Completed
????? Node?????? State?????? Active? Delay? Circuit?????? Next node
???????????????????????????? links
? 2.520 (TOMMYT) Reachable????? 0?????? 1?? NI-0-0?????? 2.520 (TOMMYT)
?2.1023 (A2RTR)? Reachable????????????????? NI-0-0????? 2.1023 (A2RTR)
NCP>telL a2rtr:: shoW exECUTOR
NCP>
22:01:15 ??? NCP
??? ??? Request # 184 Accepted
22:01:16 ??? NCP
Request # 184; Show Executor Node Summary Completed
Executor Node = 2.1023 (A2RTR)
? State = On
? Identification = DECnet/Python Area 2 Router
I needed to use SETNOD to define A2RTR to see it, but other than that I
haven't noticed anything.
On 2/25/20 8:13 PM, Robert Armstrong wrote:
? I have switched from using LEGATO as the area 2 router to using
Paul?s pyDECnet router instead.? I?m very impressed ? it doesn?t run
under VMS, but other than that pyDECnet does pretty much everything
you could want to do with DECnet or HECnet all in a single package.?
It only took me a couple of hours to get it all set up, and it can
manage all the Multinet links and the one ?Bilquist Bridge? link that
were formerly attached to LEGATO.
? The new router for area 2 is (what else?) A2RTR, 2.1023.? Johnny,
please add this node name to your database.
? LEGATO is still there, but it?s been demoted to an L1 router and it
doesn?t do anything now except route between HECnet and the real,
physical, machines in my house.
? For the people who were/are connected to LEGATO there should be no
real difference except that you?ll now see A2RTR on the other end of
the link instead. Everything else should work as before.? Let me know
if you find some problem.
? And a special thanks to Paul and Supratim for answering my silly
questions and helping me set it up.
Bob