Table of Contents
Advertisement
Step
10. Apply a routing policy to
routes advertised to or
received from the peer or
peer group.
11. Enable route target filtering
for received BGP VPNv6
routes.
12. Configure the local PE as the
RR and specify the peer as
the client.
13. Specify the maximum
number of routes BGP can
receive from a peer or peer
group.
14. Enable route reflection
between clients.
15. Configure a cluster ID for the
RR.
16. Configure filtering of
reflected routes.
17. Configure the SoO attribute
for a BGP peer for peer
group.
Configuring inter-AS IPv6 VPN
If the MPLS backbone spans multiple ASs, you must configure inter-AS IPv6 VPN.
There are three inter-AS VPN solutions (for more information, see
MPLS L3VPN supports only inter-AS VPN option A and option C.
Before configuring inter-AS IPv6 VPN, perform these tasks:
•
Configure an IGP for the MPLS backbone in each AS to ensure IP connectivity.
•
Configure basic MPLS for the MPLS backbone of each AS.
•
Configure MPLS LDP for the MPLS backbones so that LDP LSPs can be established.
The following sections describe inter-AS IPv6 VPN option A and option C. Select one according to
your network scenario.
Command
peer { group-name | ip-address
[ mask-length ] } route-policy
route-policy-name { export |
import }
policy vpn-target
peer { group-name | ip-address
[ mask-length ] } reflect-client
peer { group-name | ip-address
[ mask-length ] } route-limit
prefix-number [ { alert-only |
discard | reconnect
reconnect-time } |
percentage-value ] *
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
rr-filter
extended-community-number
peer { group-name | ip-address
[ mask-length ] } soo site-of-origin
342
Remarks
By default, no routing policy is
applied for a peer.
By default, route target filtering is
enabled.
By default, no RR or client is
configured.
By default, the number of routes
that BGP can receive from a peer
or peer group is not limited.
By default, route reflection
between clients is enabled.
By default, an RR uses its own
router ID as the cluster ID.
If more than one RR exists in a
cluster, use this command to
configure the same cluster ID for
all RRs in the cluster to avoid
routing loops.
By default, an RR does not filter
reflected routes.
Only IBGP routes whose
extended community attribute
matches the specified community
list are reflected.
By configuring different filtering
policies on RRs, you can
implement load balancing among
the RRs.
By default, the SoO attribute is not
configured.
"Configuring MPLS
L3VPN"). IPv6
Advertisement
Table of Contents
