If you are running RSX, another tool that can be used to quickly determine your routing node’s connectivity to other areas is NTD. NTD is a bit like RMD in that normally it is a live screen that updates every second with new info. Also, like the NCP TELL node command NTD node displays info for a remote node. It has several screens that can be displayed showing various types of info like what tasks are connected to DECnet. The one I’d like to point out is the Area display page. To get a copy of the screen for pasting into an email ( with out the escape sequences for VT100 graphics ) I set the terminal type to a LA120 hard copy:
>SET /LA120=TI:
>NTD CBVRP3,/PAGE=A
10-SEP-2022 10:06:49 Node: CBVRP3(30.15) CBVRP3 RASPBERRYPI RSX11M+ V4.6
RSX-11M-Plus, Area Routing Node, DECnet V4.6
Area Circuit Hop/Cst Next Node Area Circuit Hop/Cst Next Node
1 IP-0-2 1/6 ANKE ( 1.1023)
2 IP-0-3 2/13 PYRTR (31.3)
5 IP-0-2 2/11 ANKE ( 1.1023)
9 IP-0-4 3/17 PYTHON(41.1)
12 IP-0-4 4/20 PYTHON(41.1)
24 IP-0-2 2/9 ANKE ( 1.1023)
27 IP-0-4 2/12 PYTHON(41.1)
29 IP-0-2 2/10 ANKE ( 1.1023)
31 IP-0-3 1/6 PYRTR (31.3)
33 IP-0-3 2/11 PYRTR (31.3)
34 IP-0-4 3/18 PYTHON(41.1)
35 IP-0-4 3/24 PYTHON(41.1)
38 IP-0-2 4/19 ANKE ( 1.1023)
39 IP-0-3 2/10 PYRTR (31.3)
41 IP-0-4 1/6 PYTHON(41.1)
42 IP-0-4 3/16 PYTHON(41.1)
59 IP-0-4 3/13 PYTHON(41.1)
61 IP-0-4 3/15 PYTHON(41.1)
62 IP-0-2 3/16 ANKE ( 1.1023)
- Total areas: 19-
So from my connections to HECnet the largest number of hops to an area was 4 with a max cost of 20.
Best Regards,
Mark
On Sep 10, 2022, at 9:50 AM, Tomas Prybil <tomas@prybil.se> wrote:
Hey
I'm the guy running A34 in Båtbyggartorp in the suburbs of Stockholm, SWEDEN
Since I went the route of not running a bridged setup to Uppsala and went into the dark area of cisco routes I don't have a direct route to A1 anymore. However I have routes to A12, A27, A31, A59 and A61 (A22 fell off some time ago) They are all weighted in accordance to Johnnys ping--to-cost per links.
The specific example of inefficient route between A1 and A34 should be looked into I agree. Could be a hiccup since the relocation from Uppsala to Stockholm. I don't know.
Paul has a fantastic tool that describes routes between Areas around the globe. It's a great visualization of all the nerds that like to keep ancient software up and running. If we could find a way to incorporate the dark routes of gre tunnels between cisco/ios boxes that would very much help to show where we could be more efficient in routing.
Any ideas on how to move that thread forward?
BR
/t
Den 2022-09-10 15:38 skrev "Johnny Billquist" <bqt@softjar.se> följande:
I thought I'd share an example of a non-optimal setup for people, so
that you can understand a little better what we currently have.
This is from area 1 to area 34. More specifically ANKE to area 34.
Now, physically, ANKE is in Stockholm, Sweden, while A34RTR is in
Båtbyggartorp, Sweden. They are actually not that far from each other,
physically, if you look on a map. Maybe 40 kilometers at the most.
However, in HECnet, it is 3 hops, and a cost of 20.
Now, when ANKE wants to talk to area 34, the next hops are:
PYTHON - New Boston, NH, USA (cost 8)
IMPRTR - Washington DC, USA (cost 4)
and then I *think* it must be A34RTR, since that should be the final
hop, but since both IMPRTR and A34RTR are Cisco boxes, I can't see.
And a guess that the cost of that last hop would be 8.
But clearly, such a roundabout way to talk to such a close node is
kindof silly. :-) We should have reasonable links, in reasonable
directions, and with appropriate costs, so that we don't have things
like this. No good reason to. It's not like we need to pay money to have
physical cables installed between places.
(This must have been such a fun work back in the day when you needed to
actually pay for the physical cables...)
If the link to PYTHON went down, the alternative route would be through
A39RTR(9), PYRTR(2), IMPRTR(4) and then A34RTR. The costs in
parenthesis. (A cost of 2 between A39RTR and PYRTR seems rather cheap,
but what do I know?)
A few suggestions on how to look at things:
If you have a machine that talks NICE, you can examine for both VMS, RSX
and PyDECnet, what the next hop towards an area is. Giving examples on MIM:
.ncp tell anke sho area 34 stat
Area status as of 10-SEP-22 15:34:49
Next
Area State Cost Hops Circuit Node
34 Reachable 20 3 DMC-15 41.1 (PYTHON)
.ncp tell anke sho cir dmc-15 cha
Circuit characteristics as of 10-SEP-22 15:36:02
Circuit = DMC-15
Level one cost = 8
Hello timer = 60, Listen timer = 630
This can then be repeated for node PYTHON and so on. But as noted, when
you get to a Cisco box, you can't do this. Cisco boxes do not speak NICE.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se