This section illustrates how to enable BGP route target filtering on the route reflector for this example.
Configure the routing options on the route reflector as follows:
- [edit]
- routing-options {
- route-distinguisher-id 10.255.14.174;
- autonomous-system 200;
- }
Configure the BGP protocol on the route reflector as follows:
- [edit]
- protocols {
-
- bgp {
-
- group rr-group {
- type internal;
- local-address 10.255.14.174;
- cluster 10.255.14.174;
- peer-as 200;
-
- neighbor 10.255.14.182 {
- description to_PE1_vpn12;
-
- family inet-vpn {
- unicast;
- }
- family route-target;
- }
-
- neighbor 10.255.14.176 {
- description to_PE2_vpn06;
-
- family inet-vpn {
- unicast;
- }
- family route-target;
- }
-
- neighbor 10.255.14.178 {
- description to_PE3_vpn08;
-
- family inet-vpn {
- unicast;
- }
- family route-target;
- }
- }
- }
- }
Once you have configured the route reflector in this manner, you should see the following when you issue the show route table bgp.rtarget.0 command:
user@host> show route table bgp.rtarget.0
bgp.rtarget.0: 4 destinations, 8 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
200:200:101/96
*[BGP/170] 00:29:03, localpref 100, from
10.255.14.176
AS path: I
> via t1-0/2/0.0
[BGP/170] 00:29:03, localpref 100, from
10.255.14.178
AS path: I
> via t3-0/1/1.0
[BGP/170] 00:29:03, localpref 100, from
10.255.14.182
AS path: I
> via t3-0/1/3.0
200:200:102/96
*[BGP/170] 00:29:03, localpref 100, from
10.255.14.176
AS path: I
> via t1-0/2/0.0
[BGP/170] 00:29:03, localpref 100, from
10.255.14.182
AS path: I
> via t3-0/1/3.0
200:200:103/96
*[BGP/170] 00:29:03, localpref 100, from
10.255.14.176
AS path: I
> via t1-0/2/0.0
[BGP/170] 00:29:03, localpref 100, from
10.255.14.178
AS path: I
> via t3-0/1/1.0
200:200:104/96
*[BGP/170] 00:29:03, localpref 100, from
10.255.14.178
AS path: I
> via t3-0/1/1.0