Information Technology Reference
In-Depth Information
Example 10-41 shows a standard extended community list that permits VPNv4 routes that
have RTs 100:1 and 100:2. This is an exact match, meaning that both RTs must exist for a
prefix to be accepted.
Example 10-41
Example of a Standard Extended Community List
ip extcommunity-list 1 permit rt 100:1 rt 100:2
Figure 10-31 shows an RR design using RR groups, where two RTs designate two RR groups.
The first group has two redundant RRs, which accepts only routes with an RT of 100:101.
In the second group, two redundant RRs accept only routes with an RT of 100:102.
Figure 10-31
Partitioning RRs with RR Groups
RT=100:101
RT=100:101
RR1
PE1
RR2
RT=100:102
PE2
RR3
PE3
RT=100:102
RT=100:101
RT=100:102
RR4
All PEs peer with all RRs to simplify configuration and management. In addition to existing
RTs, PE1 also exports an RT of 100:101 (RR group 1). Thus, RR group 1 accepts routes
from PE1. The additional RT exported by PE2 is 100:102; thus, RR group 2 accepts the
routes from PE2. Routes from PE3 are accepted by both RR groups as both RTs are
exported. From an RR perspective, RR1 and RR2 reflect routes from PE1 and PE3; RR3
and RR4 reflect routes from PE2 and PE3. Note that there is no full-mesh requirement
between RRs of the different RR groups.
NOTE
The grouping of RRs with RTs does not necessarily coincide with RR clusters.
