Configuring Inter-As Ipv6 Vpn; Configuring Inter-As Ipv6 Vpn Option A - HP HSR6800 Configuration Manual

Step
19. Configure a cluster ID for the
route reflector.
20. Create an RR reflection
policy.
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 must configure
inter-AS IPv6 VPN.
There are three inter-AS VPN solutions (for more information, see "Configuring MPLS L3VPN").
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
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.
To configure inter-AS IPv6 option A:
•
Perform basic IPv6 MPLS L3VPN configuration on each AS.
•
Configure each ASBR, taking the peer ASBR PE as its CE. In other words, configure VPN
instances on both PEs and ASBR PEs. The VPN instances on PEs allow CEs to access the
network, while 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.
Command
reflector cluster-id { cluster-id |
ip-address }
rr-filter
extended-community-number
392
Remarks
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.
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.