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

Robert Armstrong bob at jfcl.com
Sun Aug 16 18:18:27 PDT 2020


>i've never had any line in my config in relation to debug or informational
logs - 

>just the log file definition on the daemon startup script.

 

  I have a whole yaml file for logging, which is mostly taken verbatim from
Paul's example.  I get tons of logged events - starting circuits, starting
datalinks, nodes up, areas up, routers discovered, etc.  It doesn't seem
like it's changed with this release.  You might try that.

 

  For example, an hour ago I just got

 

2020-08-16 17:06:07.775: A2RTR: Event type 4.7, Circuit down, circuit fault

  From node 2.1023 (A2RTR), occurred 16-Aug-2020 17:06:07.775

  Circuit = MUL-35

    Reason = Circuit synchronization lost

    Adjacent node = 35.1023 (A35RTR)

2020-08-16 17:06:28.432: A2RTR: Event type 4.10, Circuit up

  From node 2.1023 (A2RTR), occurred 16-Aug-2020 17:06:28.432

  Circuit = MUL-35

    Adjacent node = 35.1023 (A35RTR)

 

Bob

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20200816/6f5b4106/attachment.html>


More information about the Hecnet-list mailing list