[HECnet] HECnet mapper -- request to backbone node operators

[Johnny Billquist]

On 2020-08-16 05:20, Mark Matlock wrote:
> Paul,
>     I look forward to seeing your HECnet mapper respond to topology changes.
>   
>     I just set up CBVRP3 the primary router for area 30 to forward events to 28NH. Let me know if there are any issues.
> 
>     Your NCP syntax below worked perfectly for me in RSX once I defined the node 28NH. I just put it also at the end of my network start-up command files to make it permanent.

Paul was also thinking about/referring to how to set it up in the 
permanent DECnet configuration. In RSX, the tool for that is CFE. 
However, CFE cannot set that up fully (I was a bit surprised when I 
realized this). So the best is to just do what you have done, Mark. Turn 
it on in NCP at boot time.

CFE can turn on the monitoring sink as such, but you cannot point that 
to a node in CFE.

   Johnny

> 
> Thanks and Best Regards,
> Mark
> 
>> On Aug 15, 2020, at 1: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
>>
> 

-- 
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