On Mon, Oct 24, 2011 at 04:38:32PM +0200, Ruben Laban wrote:
On Monday 24 October 2011 at 16:18 (CET), Ondrej Zajicek wrote:
Real 'sledgehammer' is restart command. Configure command tries to be gentle, but restart the protocol if necessary (like if BGP import filter is changed and the neighbor does not support route refresh).
Ok, clear. But aren't route refreshes a fundamental part of BGP? Or am I missing/misunderstanding something here?
No, they are an extension (RFC 2918), but widely implemented.
What I don't understand though, when I was just altering null-routes and export filters, a configure did result in a hard clear according to my peer. Are there any other scenarios where configure could lead to a hard clear and not a soft clear? One thing that comes to mind is that I enabled 'next hop self' as well, though I don't see why that'd warrant a hard clear either?
Proper reconfiguration of BGP sessions is not implemented in BIRD, so changing other parameters (than import/export) of BGP (like 'next hop self') will lead to session restart. -- 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."