[rbak-nsp] bgp debug to external log server

[Sridhar]

Hi Marcin,
I'm not sure if you can redirect debug bgp ouput to an external log
server, but you can log the debug output to a file on /md and retrieve
the file later. But you need to do this carefully (ie. choose the
right debugs ) because this can fill up /md quickly.

[local]Redback#conf
[local]Redback(config)#cont local
[local]Redback(config-ctx)#logging file ?
  WORD  Local file name prefix; default directory /md
  text  Save the log in clear text
[local]Redback(config-ctx)#logging file text /md/bgpdebug.txt
[local]Redbackl(config-ctx)#end
[local]Redback#
[local]Redback# debug bgp neighbor 172.30.45.110 update
[local]Redback#

sridhar

On Mon, Jul 27, 2009 at 9:27 AM, Marcin Kuczera<marcin at leon.pl> wrote:
> David Freedman wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Marcin Kuczera wrote:
>>>
>>> David Freedman wrote:
>>> What happens? neighbourship collapses?  do you get NOTIFCATION? if so,
>>> what is code?
>>>
>>>> It's more complicate.
>>
>> <snip>
>>
>> This is the PLiX RS right?
>
> yes, PLIX
>
>> How many participants are using this? have any of these had a similar
>> problem? have you raised this with them? what bgpd are they using?
>
> about 100 members using RS.
> I have no info about others seeing the same as we do...
> RSes are based on OpenBGPd as I was told, members - usually cisco/juniper.
> I'll try to investigate if anyone else had this problem.
>
>> Would be extremely odd if suddenly SEOS started using the origin as
>> next-hop!
>
> It is odd...
>
> Regards,
> Marcin
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>