15 Sep
2022
15 Sep
'22
8:49 p.m.
On Sep 15, 2022, at 2:34 PM, Johnny Billquist
<bqt(a)softjar.se> wrote:
For directly connected nodes (point-to-point or ethernet), I usually get a log
notification whenever a node comes or goes. That is pretty much standard DECnet logging.
And it's event 4.15 for adjacency up, and 4.18 for adjacency down.
Johnny
The mapper is interested in a number of events: node/area reachability change, and
circuit/adjacency up/down/fault, events 4.7-10,14-15,18-19. The reachability change
events will report nodes coming and going even if they are not adjacent, but a circuit
change where there are redundant circuits would not be accompanied by a reachablity change
so it's only seen if the reporting node is adjacent. The node up/down case are more
critical in the sense that this is directly visible to anyone who tries to reach the node
in question.
Right now I have a number of event senders in some of the HECnet areas; other areas
don't yet have coverage. So loss of an area will be seen right away, some L2 circuit
loss will be, but changes within areas might not be. The list of reporting nodes is at
the bottom of the NSP status page of the mapper, since that shows the open connections to
the event listener. http://akdesign.dyndns.org:8080/nsp/status?system=28NH -- Hm, curious
that right now there are two connections from 2.99...
paul