The NE80E version is V300R002C06B325 and is configured with the VPN route control function. The limit is 100 routes. The current controlled VPU routing table, however, has 145 routes and the number continues to increase.
This case applies to all V300R002 versions.
The VPN route control is configured as follows:
ip vpn-instance ABC
routing-table limit 100 60
vpn-target 100:103 export-extcommunity
vpn-target 100:103 import-extcommunity#
[NE40E] dis ip routing-table vpn-instance ABC statistics
Proto total active added deleted freed
routes routes routes routes routes
DIRECT 1 1 1 0 0
STATIC 0 0 0 0 0
RIP 0 0 0 0 0
OSPF 0 0 0 0 0
IS-IS 0 0 0 0 0
BGP 288 144 736 448 448Total 289 145 737 448 448
1、Reset the MBGP neighbors and learn the routes again. Then, the number of routes in the VPN routing table can be restricted within the limit.2、Keep the status of current routing table. Change the limit value to 145. In this case, new routes are restricted and cannot be added to the routing table.
VPN route control is configured as follows:If the number of current routes exceeds the limit, new routes still can be added without alarms. VPN route control takes effect only when the routes are learned again. If the number of current routes is less than the limit, the configuration takes effect.
The number of VPN routes must be restricted. VPN route control should be configured when you configure VPN instances. Then, configure the related MBGP data. In this case, routes can be added to the VPN routing table and be restricted.