[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bird-users
Subject:    Re: BGP syslog
From:       Jimmy Halim <jhalim () ap ! equinix ! com>
Date:       2013-03-13 6:35:02
Message-ID: CD663AB5.41685%jhalim () ap ! equinix ! com
[Download RAW message or body]

Hi Santiago,

We are getting it now after we set the syslog severity to debug. Just
wondering, is it possible for you guys to include the BGP up and down
event under "info" severity? If not I guess the syslog will be flooded
with those unwanted debugging events.

Mar 13 14:14:35 Birdy bird6: Testing_601: Down
Mar 13 14:04:20 Birdy bird6: Testing_601: State changed to up

Thanks,

Jimmy




On 13/3/13 12:41 AM, "Ondrej Zajicek" <santiago@crfreenet.org> wrote:

>On Wed, Mar 13, 2013 at 12:01:23AM +0800, Jimmy Halim wrote:
>> Hi Santiago,
>> 
>> This is what I have:
>> 
>> Global:
>> log syslog {debug, trace, info, remote, warning, error, auth, fatal,
>>bug};
>> 
>> Each BGP neighbor:
>> debug { states, events };
>> 
>> 
>> It should be enough right? In syslog I cannot see BGP up "established"
>>and
>> BGP "down" messages :(
>
>Yes this is OK, you should see:
>
>  BGP session established
>
>  BGP session closed
>
>You could try log "filename" instead of log debug. If you would see that
>in direct file log and not in syslog-based log, then probably it is an
>issue in your syslog config.
>
>BTW, you can also use 'log syslog all' instead of 'log syslog { ... }'.
>
>-- 
>Elen sila lumenn' omentielvo
>
>Ondrej 'SanTiago' Zajicek (email: santiago@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."

[prev in list] [next in list] [prev in thread] [next in thread]