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

List:       quagga-users
Subject:    [quagga-users 9037] Re: SLOW COMMAND with clear ip bgp * soft,
From:       paul () clubi ! ie
Date:       2007-10-26 12:59:40
Message-ID: alpine.LFD.0.9999.0710261357050.6106 () localhost ! localdomain
[Download RAW message or body]

On Fri, 26 Oct 2007, Tore Anderson wrote:

> 2007/10/26 11:04:19 BGP: SLOW COMMAND: command took 17308ms (cpu time 16930ms): clear ip bgp * soft
> 2007/10/26 11:04:19 BGP: SLOW THREAD: task vtysh_read (2aaf0cbc3a76) ran for 17308ms (cpu time 16930ms)
>
> Out of 10 BGP active BGP sessions, only one survived.  The rest of 
> them was put in state  «Clearing », after which they were 
> automatically re-established.  I've seen this happen before, too.

Hmm, what kind of hold-time parameters are you using?

bgpd took 17s to do your clear, that's well within the default 
hold-time.

> Isn't the  «soft » parameter supposed to make sure the sessions are 
> NOT reset?

Yes, and the command wouldn't have reset your peers. Rather your 
peers did, presumably because the command took too long.

> Is there any other way to safely reload BGP peers without risking 
> tearing down the sessions?

Yes, use route-refresh (clear .... in) - it doesn't need a table 
walk.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Reading is to the mind what exercise is to the body.

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users


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