I have done this from a SIMH instance that is set as a routing node. My own
user mode router does not implement these events.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf
Of Paul Koning
Sent: 16 August 2020 18:37
To: hecnet at Update.UU.SE
Subject: [HECnet] Re: HECnet mapper -- request to backbone node operators
A clarification: I'm looking for an event source for each area. Even if
your
area
only has a single connection to other areas, it's
useful to have an event
source
there. The reason is that change of node reachability
is visible only to
routers
in the area, and this is one of the events I'm
looking for.
paul
On Aug 15, 2020, at 2:42 PM, Paul Koning
<paulkoning at comcast.net> wrote:
Gentlepeople,
I've added a new feature to the HECnet mapper
(
http://akdesign.dyndns.org:8080/map/) to listen for topology change
events
and do incremental updates of the map as these happen.
You can see this
in
the current mapper display, which will show "Last
incremental change" in
the
map title block if there has been any incremental
change since the last
full
update.
>
> For this to be most effective, the mapper needs to be sent these events
from
at least one router in each area. A good choice would
be the main
backbone
area router in each area; better still all the
backbone area routers if
there are
several.
>
> So if you have one of these and are interested in participating, please
do
the
equivalent of this NCP command:
>
> NCP>set logging monitor events 4.7-10,14-15,18-19 sink node 28nh
>
> and of course the equivalent permanent command ("define" instead of
"set",
and perhaps in a different utility at least for the
case of RSX).
>
> If you're running PyDECnet, you need to upgrade to the current version,
rev
524. Then add this line to the config file:
>
> logging monitor --sink-node 28nh --events 4.7-10,14-15,18-19
>
> When you set up a router for this, please drop me an email so I know
which
nodes are currently participating.
>
> Thanks much,
> paul
>