HP MSR2000/3000/4000 Router Series MPLS Configuration Guide

229
Ste
p
Command
Remarks
14. Configure a cluster ID for the
route reflector.
reflector cluster-id { cluster-id |
ip-address }
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.
15. Configure filtering of reflected
routes.
rr-filter
extended-community-list-number
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.
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 "Configuring MPLS L3VPN"). IPv6
MPLS L3VPN supports only inter-AS VPN option A and option C.
Before configuring inter-AS IPv6 VPN, complete 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.
Configuring inter-AS IPv6 VPN option A
Inter-AS IPv6 VPN option A applies to scenarios where the number of VPNs and that of VPN routes on
the PEs are relatively small.
To configure inter-AS IPv6 option A:
Configure basic IPv6 MPLS L3VPN on each AS.
Configure VPN instances on both PEs and ASBR PEs. The VPN instances on PEs allow CEs to access
the network, and those on ASBR PEs are for access of the peer ASBR PEs.
For more configuration information, see "Configuring MPLS L3VPN."
In the inter-AS IPv6 VPN option A solution, for the same IPv6 VPN, the route targets configured on the PEs
must match those configured on the ASBR-PEs in the same AS to make sure VPN routes sent by the PEs (or
ASBR-PEs) can be received by the ASBR-PEs (or PEs). Route targets configured on the PEs in different ASs
do not have such requirements.