The MPLS label is allocated based on the VPN instance, which ensures that all the routes in a
VPN instance use the same MPLS label.
Step 6
(Optional) Run:
routing-table limit
number
{
alert-percent
|
simply-alert
}
The maximum number of routes of the VPN instance is configured.
Step 7
(Optional) Run:
prefix limit
number
{
alert-percent
[
route-unchanged
] |
simply-alert
}
The maximum number of prefixes of the VPN instance is configured.
Step 8
(Optional) Run:
limit-log-interval
interval
The frequency of displaying logs when the number of routes exceeds the threshold is configured.
Step 9
(Optional) Run:
import route-policy
policy-name
The import routing policy of the VPN instance is configured.
Step 10
(Optional) Run:
export route-policy
policy-name
The export routing policy of the VPN instance is configured.
----End
3.7.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 used
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 IPv4 VPN routes with the same next hop and outgoing
label. Compared with allocating a label for each IPv4 VPN route, next-hop-based label allocation
greatly saves the label resources.
Do as follows on the ASBR:
Procedure
Step 1
Run:
system-view
The system view is displayed.
Step 2
Run:
bgp
as-number
The BGP view is displayed.
Quidway S7700 Smart Routing Switch
Configuration Guide - VPN
3 BGP MPLS IP VPN Configuration
Issue 01 (2011-07-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
133
