[j-nsp] BGP advertisements not making it

Diogo Montagner diogo.montagner at gmail.com
Sat Jul 31 00:23:42 EDT 2010


Yes. This is your case. The best route is OSPF. As Richard said, if
you don't have the advertise-inactive then the BGP route
64.187.209.0/24 will not be advertised by BGP.

HTH
./diogo -montagner



On Sat, Jul 31, 2010 at 11:55 AM, Richard A Steenbergen
<ras at e-gerbil.net> wrote:
> On Fri, Jul 30, 2010 at 08:47:25PM -0700, Jim Devane wrote:
>> RAS,
>>
>> Thanks. I just replied to Diogo. I think it may simply be a case of
>> not being the best route and not advertised. I am going to track down
>> where the other route is coming from and find out why it is missing
>> the pass community and I am thinking at that point it will pass.
>
> Ah, well that would do it too. If your other route is non-BGP (for
> example, a static or IGP route) you can work around this by configuring
> "advertise-inactive" in BGP to make it advertise the best BGP route. If
> the wrong BGP route is active, you probably just need to tweak your
> localprefs. :)
>
> All my policy evaluation bugs are REALLY obscure, for example subroutine
> policies which will randomly not apply any actions in any term that
> doesn't contain a "then accept". I've never seen a problem with a
> configuration as simple as yours.
>
> --
> Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



More information about the juniper-nsp mailing list