Why not use selective advertisement of the default based on receiving a specific route from your carrier or an upstream you know to be stable.
http://www.cisco.com/en/US/docs/ios/12_3/iproute/command/reference/ip2_n1g.h tml#wp1037042 David -- http://dcp.dcptech.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tom Lanyon Sent: Wednesday, September 26, 2012 10:04 PM To: cisco-nsp Subject: [c-nsp] Change BGP default-originate to IGP? Hi list, In an enterprise network I have a core of 4900Ms with a few ASR1ks hanging off to handle upstream connectivity. As an example: Upstream1 - [ASR1k]--[4900M]--[4900M]--[ASR1k] - Upstream2 | | | | Servers Workstations, etc The ASRs and 4900Ms are running BGP and ISIS with full tables on the ASRs and mostly just defaults on the 4900Ms. The ASRs are originating defaults via BGP but on reload they are blackholing traffic whilst BGP converges. I've seen that OSPF and ISIS have 'wait-for-bgp' overload bits available and have been questioning whether switching to an IGP-generated default with wait-for-bpg is the correct solution here. Any thoughts? Thanks, Tom _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
