<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: L3VPN VPNv4 NLRI - Route Reflector Scaling</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>>On Wednesday 02 April 2008, David Freedman wrote:<BR>
> We have dedicated VPNv4 route reflectors, they work well<BR>
> for us.<BR>
>An inevitable end as the number of routes grows.<BR>
<BR>
In our case we use the cisco "rr-group" directive<BR>
(<A HREF="http://www.cisco.com/en/US/docs/ios/12_3/iproute/command/reference/ip2_a1g.html#wp1040902">http://www.cisco.com/en/US/docs/ios/12_3/iproute/command/reference/ip2_a1g.html#wp1040902</A>)<BR>
to limit RR clusters to the prefixes we actually want them to reflect, filtered by extcommunity.<BR>
<BR>
The downside to this of course is that the RRs spend time discarding prefixes when update time comes around for the PEs.<BR>
<BR>
Dave.</FONT>
</P>
</BODY>
</HTML>