[j-nsp] Family route-target filtering - filtering the default advertiseme nt

[Damon Pegg]

No, all devices are supporting RTF and show that the family route-target
capability has been negotiated in the traceoptions.

> -----Original Message-----
> From: Cliff DeGuzman [mailto:cliff at juniper.net]
> Sent: 22 October 2004 15:47
> To: Damon Pegg; juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] Family route-target filtering - filtering the
> defaultadvertiseme nt 
> 
> 
> Damon,
> 
> Do you have a PE in the mesh that does not support RTF?  If 
> so, then it
> is normal for the PE router(s) to automatically generate a default
> route-target route and advertise it to all its peers.
> 
> The "advertise-default" option tells the router to advertise a default
> route-target route and suppress any specifics, so what you 
> are seeing is
> the correct behavior.
> 
> Regards,
> Cliff
> 
> > -----Original Message-----
> > From: juniper-nsp-bounces at puck.nether.net 
> > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Damon Pegg
> > Sent: Friday, October 22, 2004 4:45 AM
> > To: 'juniper-nsp at puck.nether.net'
> > Subject: [j-nsp] Family route-target filtering - filtering 
> > the defaultadvertiseme nt 
> > 
> > 
> > Quick pop quiz:
> > 
> > running 6.4 and my PEs seem to be advertising both the 
> > specific nlri and the default, and thus I have no filtering!
> > 
> > If I turn on 'protocol bgp group x family route-target 
> > advertise-default' it suppresses the more specifics but I get 
> > both without that command.
> > 
> > Any ideas?
> > 
> > damon. 
> > 
> > 
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net 
> > http://puck.nether.net/mailman/listinfo/junipe> r-nsp
> > 
>