OSPFv3 and logging (debug)

[Ondrej Zajicek]

On Fri, Dec 06, 2013 at 02:04:17PM +0400, Alexander V. Chernikov wrote:
> On 05.12.2013 09:14, Dmitry S. Nikolaev wrote:
> > Hello.
> > 
> > Thus it is impossible to understand exactly what neighbor (over what
> > tunnel) change it`s state because there is no iface name in log.
> > So monitoring system can say that some neighbor down/up but can`t say
> > over what tunnel this neighbor was working :(
> > 
> > Who faced with the same task ? How to solve?

> Please try an attached patch.

Hello

Although adding an iface scope to link-local addresses helps a bit,
link-local addresses are still confusing when there are many neighbors
on one iface.

I am thinking about replacing IPs with router IDs as a primary neighbor
description in most OSPF log messages. Any comments/opinions to such
change?


BTW, you can use '%J' as a shorthand for %iface
(see e.g. bgp_start_locked() in proto/bgp/bgp.c).

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20131206/e6cbb2e8/attachment-0001.asc>