I would say first modify import and export policy to influence the routing such that upstream and downstream nodes view the BGP speaker as less preferred. Give it some time for BGP tables to settle down and nodes to converge on new more preferable paths, then simply deactivated BGP.
Of course all of this hinges on having multiple routers as exit points in your network. Sorry for the top post. Stefan Fouant GPG Key ID: 0xB4C956EC Sent from my HTC EVO. ----- Reply message ----- From: "Matthias Brumm" <matth...@brumm.net> Date: Tue, Jul 19, 2011 6:29 am Subject: [j-nsp] best way to shut down BGP session To: "Juniper-NSP" <juniper-nsp@puck.nether.net> Hi! What are you using to shut down a BGP session in the most smoothly way for maintenance purposes? At this time I have used an import/export statement with a reject action in it. But perhaps you have a better way, so that the routes on the connected routers are reroutes very smoothly, so that the customers are nearly unaffected? Regards, Matthias _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
