9 Dec
2021
9 Dec
'21
7:06 p.m.
On Dec 9, 2021, at 11:58 AM, Peter Lothberg <roll
at stupi.com> wrote:
Idea:
Put the lat/long of the node in the DECnet executor identification,
something like this.. (just an example)
set exECUTOR idENTIFICATION "DECnet-10 Version 4.0 *59.22222,18.88888*"
Then anyone can pull it with:
NCP>sh exec char
Executor Node = 59.1 (ODEN)
Identification = DECnet-10 Version 4.0 *59.22222,18.88888*
Nice idea. A couple of limitations: the ident string max length is fairly low, though
some implementations ignore the specified limit. And this only works if the node is (a)
up and (b) allow NICE connections. While updating Johnny's database requires some
manual action, it has the benefit that it applies to any node, up or down, Cisco or
otherwise.
The mapper queries it once a day (the top line on the map display shows the most recent
"database update").
paul