On Thu, Mar 09, 2017 at 04:30:55PM +0200, Lennert Buytenhek wrote:
If we are using the secondary remote AS mechanism, we don't necessarily need to restart an already established BGP connection if the remote AS for a BGP session changes, as long as the AS number that the peer is currently connected with is still in the list of AS numbers that we accept from the peer.
This commit will avoid reconfiguring a BGP protocol if there is a corresponding connection in OpenConfirm or Established state and the only change to the protocol configuration was related to remote AS numbers and the AS number that the peer is currently connected with is still a permitted remote AS number. This allows adding a secondary remote AS number to a BGP protocol without bouncing an already established BGP session for this protocol.
Well, the simple way to avoid reconfiguration in this case is just to move 'remote_as2' field at the end of bgp_config, like 'check_link' or 'bfd'. -- 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."