Step 3
Run
route-distinguisher
route-distinguisher
The RD is configured for the IPv6 VPN instance.
Step 4
Run
vpn-target
vpn-target
&<1-8>
import-extcommunity
The VPN target extended community for the IPv6 VPN instance is created.
For the same VPN in the inter-AS VPN-Option B mode, the VPN targets of the ASBR and the
PE in an AS should match with each other.
The VPN targets of the PE in different Ass must match with each other likewise.
Step 5
(Optional) Run
routing-table limit
number
{
alert-percent
|
simply-alert
}
The maximum number of routes is configured for the IPv6 VPN instance.
Step 6
(Optional) Run:
prefix limit
number
{
alert-percent
[
route-unchanged
] |
simply-alert
}
The maximum number of prefixes of the IPv6 VPN instance is configured.
Step 7
(Optional) Run:
limit-log-interval
interval
The frequency of displaying logs when the number of routes exceeds the threshold is configured.
Step 8
(Optional) Run:
import route-policy
policy-name
An import routing policy is created for the IPv6 VPN instance.
Step 9
(Optional) Run:
export route-policy
policy-name
An export routing policy is created for the IPv6 VPN instance.
----End
4.8.6 (Optional) Enabling Next-Hop-based Label Allocation on the
ASBR
To save label resources on an ASBR, you can enable next-hop-based label allocation on the
ASBR. Note that next-hop-based label allocation and one label per instance need to be enabled
together on the ASBR.
Context
In a VPN Option B scenario, after next-hop-based label allocation is enabled on the ASBR, the
ASBR allocates only one label for the IPv6 VPN routes with the same next hop and outgoing
label. Compared with allocating a label for each IPv6 VPN route, next-hop-based label allocation
greatly saves the label resources.
Do as follows on the ASBR:
Quidway S7700 Smart Routing Switch
Configuration Guide - VPN
4 BGP MPLS IPv6 VPN Configuration
Issue 01 (2011-07-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
358
