[c-nsp] ignoring bgp learned route?

[matthew zeier]

So I learned about the backdoor command (http://tinyurl.com/y67nfg) and that 
did exactly what I wanted.

router bgp 1234
  network 10.10.223.0 mask 255.255.255.0 backdoor

Uses the IGP learned route unless it's not there.

- mz



Shakeel Ahmad wrote:
> Let the route come but use higher administratice distance for BGP 
> session which will overrule your OSPF AD. (I am supposing you might need 
> it incase local route goes away) or you can always use filter-lists to 
> drop a specific prefix.
>  
>  
> SA
> 
>  
> On 12/23/06, *matthew zeier* <mrz at velvet.org <mailto:mrz at velvet.org>> 
> wrote:
> 
>     I'm trying to anycast 10.10.223.0/24 <http://10.10.223.0/24> from
>     two sites.  One site (SJ) also
>     announces the aggregate 10.10.208.0/20
>     <http://10.10.208.0/20>.  Each site is behind a seperate AS.
> 
>     In SJ, the /24 is statically routed on the core routers to a connected
>     interface.  All OSPF speakers see that route correctly.
> 
>     The border routers see the BGP learned from from the other site and
>     not the
>     OSPF learned route.  I want these routers to ignore the BGP learned
>     route and
>     announce it on their own and use what they hear from OSPF.
> 
>     What's the best way to accomplish this?  prefix-list/filter-list on
>     each ebgp
>     neighbor denying that route?
> 
>     _______________________________________________
>     cisco-nsp mailing list   cisco-nsp at puck.nether.net
>     <mailto:cisco-nsp at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-nsp
>     archive at http://puck.nether.net/pipermail/cisco-nsp/
>     <http://puck.nether.net/pipermail/cisco-nsp/>
> 
>