Configuring Inter-As Ipv6 Vpn - HP FlexNetwork HSR6600 Configuration Manual

Comware 7 mpls
Hide thumbs Also See for FlexNetwork HSR6600:
Table of Contents

Advertisement

Step
15. Set the maximum number of
routes BGP can receive from
a peer or peer group.
16. Enable route reflection
between clients.
17. Configure a cluster ID for the
RR.
18. Configure filtering of
reflected routes.
19. 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
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.
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, perform the following tasks:
Configure basic IPv6 MPLS L3VPN on each AS.
Configure VPN instances on both PEs and ASBRs. The VPN instances on PEs allow CEs to
access the network, and those on ASBRs are for access of the peer ASBRs.
Command
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
334
Remarks
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.
"Inter-AS
VPN"). IPv6 MPLS

Advertisement

Table of Contents
loading

Table of Contents