Configuring Inter-As Ipv6 Vpn - HP FlexNetwork 10500 Series Configuration Manual

Step
14. Enable route target filtering
for received BGP VPNv6
routes.
15. Configure the local PE as the
RR and specify the peer as
the client.
16. Set the maximum number of
routes BGP can receive from
a peer or peer group.
17. Enable route reflection
between clients.
18. Configure a cluster ID for the
RR.
19. Configure filtering of
reflected routes.
20. 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 the following 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
policy vpn-target
peer { group-name | ipv4-address
[ mask-length ] } reflect-client
peer { group-name | ipv4-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 ext-comm-list-number
peer { group-name | ipv4-address
[ mask-length ] } soo site-of-origin
282
Remarks
By default, route target filtering is
enabled for received VPNv6
routes. Only VPNv6 routes whose
export route target attribute
matches local import route target
attribute are added to the routing
table.
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