BIRD Masters, BIRD 1.2.5 I recently updated my route server configuration to include a new set of BGP export filters when one peer wants to exclude routes to another peer. The filter is only applied to those selecting to exclude one another. When I pushed the new config with only two BGP sessions having the added filers, the rest untouched, and two new pipes were added, BIRD restarted all PIPE/BGP sessions after a 'configure soft'. Is this the expected behavior? Without export filter: protocol bgp RXXXXX { local as myas; neighbor xx.xx.xx.xx as XXXXX; import filter bgp_in_ASXXXXX; export all; route limit 500; table TXXXXX; rs client; start delay time 30; } With export filter: protocol bgp RYYYY { debug { filters }; local as myas; neighbor yy.yy.yy.yy as YYYY; import filter bgp_in_ASYYYY; export filter bgp_out_ASYYYY; route limit 1000; table TYYYY; rs client; start delay time 30; } Much Appreciated, Stephen
Additionally this preceded the restarts: 28-07-2011 12:28:07 <WARN> Reconfiguration of BGP listening socket not implemented, please restart BIRD. No changes were made to the listen IP/Port. -Stephen From: owner-bird-users@atrey.karlin.mff.cuni.cz [mailto:owner-bird-users@atrey.karlin.mff.cuni.cz] On Behalf Of Stephen Holmes Sent: Thursday, July 28, 2011 12:48 PM To: bird-users@network.cz Subject: All protocols restarting on configure soft BIRD Masters, BIRD 1.2.5 I recently updated my route server configuration to include a new set of BGP export filters when one peer wants to exclude routes to another peer. The filter is only applied to those selecting to exclude one another. When I pushed the new config with only two BGP sessions having the added filers, the rest untouched, and two new pipes were added, BIRD restarted all PIPE/BGP sessions after a 'configure soft'. Is this the expected behavior? Without export filter: protocol bgp RXXXXX { local as myas; neighbor xx.xx.xx.xx as XXXXX; import filter bgp_in_ASXXXXX; export all; route limit 500; table TXXXXX; rs client; start delay time 30; } With export filter: protocol bgp RYYYY { debug { filters }; local as myas; neighbor yy.yy.yy.yy as YYYY; import filter bgp_in_ASYYYY; export filter bgp_out_ASYYYY; route limit 1000; table TYYYY; rs client; start delay time 30; } Much Appreciated, Stephen ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________
No response needed. I pushed the same config to my redundant route server and it didn't restart all the protocols. Maybe I did something I am not aware of to cause the restarts... Thanks, Stephen From: owner-bird-users@atrey.karlin.mff.cuni.cz [mailto:owner-bird-users@atrey.karlin.mff.cuni.cz] On Behalf Of Stephen Holmes Sent: Thursday, July 28, 2011 1:06 PM To: bird-users@network.cz Subject: RE: All protocols restarting on configure soft Additionally this preceded the restarts: 28-07-2011 12:28:07 <WARN> Reconfiguration of BGP listening socket not implemented, please restart BIRD. No changes were made to the listen IP/Port. -Stephen From: owner-bird-users@atrey.karlin.mff.cuni.cz [mailto:owner-bird-users@atrey.karlin.mff.cuni.cz] On Behalf Of Stephen Holmes Sent: Thursday, July 28, 2011 12:48 PM To: bird-users@network.cz Subject: All protocols restarting on configure soft BIRD Masters, BIRD 1.2.5 I recently updated my route server configuration to include a new set of BGP export filters when one peer wants to exclude routes to another peer. The filter is only applied to those selecting to exclude one another. When I pushed the new config with only two BGP sessions having the added filers, the rest untouched, and two new pipes were added, BIRD restarted all PIPE/BGP sessions after a 'configure soft'. Is this the expected behavior? Without export filter: protocol bgp RXXXXX { local as myas; neighbor xx.xx.xx.xx as XXXXX; import filter bgp_in_ASXXXXX; export all; route limit 500; table TXXXXX; rs client; start delay time 30; } With export filter: protocol bgp RYYYY { debug { filters }; local as myas; neighbor yy.yy.yy.yy as YYYY; import filter bgp_in_ASYYYY; export filter bgp_out_ASYYYY; route limit 1000; table TYYYY; rs client; start delay time 30; } Much Appreciated, Stephen ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________
participants (1)
-
Stephen Holmes