[j-nsp] MBGP automatic filtering?

[michael.firth at bt.com]

It is simply an option for testing and debugging - to make sure that a new PE's got a good connection to the RR that can import L3VPN routes before any VRFs are configured.

It sounds like the 'keep-all' knob may allow that. 

In operation, I am more than happy with the default behaviour - it will extend the time that low memory REs can stay in service.

Michael

> -----Original Message-----
> From: Doug Marschke [mailto:Doug at ietraining.net] 
> Sent: 25 June 2008 08:08
> To: Firth,MJC,Michael,DMJ R; juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] MBGP automatic filtering?
> 
> Yes, JUNOS only keeps routes that have a matching route target.
> 
> You could configure the keep-all knob under BGP to see all routes on
> your PE.
> 
> I guess I ask the question, why you want to see all that 
> garbage?  These
> is a very good reason for that automatic filtering :)
> 
> 
> 
> Doug Marschke 
> Principal Technologist 
> Strategic Networks Training 
> JNCIE-ER #3, JNCIE-M/T #41, JNCIS-FW, JNCI 
> www.ietraining.net 
> (415)902-5702 
> 
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> michael.firth at bt.com
> Sent: Tuesday, June 24, 2008 8:52 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] MBGP automatic filtering?
> 
> A (hopefully) simple question for someone on here.
> 
> When connecting a PE router to a route reflector, there seems 
> to be some
> form of automatic filtering going on with the bgp.l3vpn.0 table.
> 
> On the RR I see the following for a 'show bgp neighbor <pe-address>':
> ...
>   Table bgp.l3vpn.0 Bit: 20017
>     RIB State: BGP restart is complete
>     RIB State: VPN restart is complete
>     Send state: in sync
>     Active prefixes:              9
>     Received prefixes:            9
>     Suppressed due to damping:    0
>     Advertised prefixes:          1156
> ...
> 
> While on the PE, for a 'show bgp neighbor <rr-address>' I get:
> ...
>   Table bgp.l3vpn.0
>     RIB State: BGP restart is complete
>     RIB State: VPN restart is complete
>     Send state: not advertising
>     Active prefixes:              9
>     Received prefixes:            9
>     Suppressed due to damping:    0
> ...
> 
> The PE seems to be doing some form of automatic filtering on the
> received prefixes from the RR, to only include those that are required
> for routing-instances it has configured.
> 
> Is there any command that can override this, and show the full list of
> prefixes received from the RR?
> 
> Thanks
> 
> Michael
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>