H3C Technologies H3C S10500 Series Switches - Manual (Page 362)

351
To do… Use the command… Remarks
Configure a cluster ID for the route
reflector reflector cluster-id { cluster-id |
ip-address }
Optional
By default, each RR in a cluster 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 rout
loops.
Create an RR reflection policy
rr-filter
extended-community-list-number
Optional
By default, an RR does not filter the
reflected routes.
With an RR reflection policy, only
iBGP routes whose Extended
Communities attribute matches the
specified one are reflected.
By configuring different RR
reflection policies on different RRs,
you can implement load balancing
among the RRs.
NOTE:
For information about IPv6 BGP routing features, see Layer 3—IP Routing Configuration Guide.
Configuring inter-AS IPv6 VPN
If the MPLS backbone that carries the IPv6 VPN routes spans multiple ASs, you need to configure inter-AS
IPv6 VPN.
There are three inter-AS VPN solutions (see the chapter “MPLS L3VPN configuration” for more
information). Currently, IPv6 MPLS L3VPN supports only inter-AS VPN option A and option C.
Configuration prerequisites
Before configuring inter-AS IPv6 VPN, complete these tasks:
• Configuring an IGP for the MPLS backbone in each AS to ensure IP connectivity
• Configuring basic MPLS for the MPLS backbone of each AS
• Configuring MPLS LDP for the MPLS backbones so that LDP LSPs can be established
NOTE:
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. It is easy to implement.