[c-nsp] Change BGP default-originate to IGP?

[Christian Meutes]

The best way is here really to inject the defaults via ISIS.

On 27.09.2012, at 04:04, Tom Lanyon <tom+c-nsp at oneshoeco.com> wrote:

> 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  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/