No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Log Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).



L3VPN/4/ROUTE_MAX_EXCEEDED:The total number of routes in VPN instance [vpn-instance] was [route-number], which exceeded the maximum value [maximum-value].


The number of added routes exceeded the upper limit.


Parameter Name Parameter Meaning
[vpn-instance] Indicates the name of the VPN instance.
[route-number] Indicates the number of the current routes.
[maximum-value] Indicates the maximum of the routes.

Possible Causes

After the number of routes in the routing table reached the upper limit, new routes continued to be added.


  1. Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to check the total number and types of routes in this VPN instance.
  2. Analyze the source of each route and check whether the number of current routes in the VPN instance meets the actual requirement.

    • If so, go to Step 4.
    • If not, go to Step 3.

  3. Delete unnecessary private routes, and then check whether the number of routes still reaches or exceeds the alarm threshold.

    • If so, go to Step 5.
    • If not, go to Step 6.

  4. Enter the VPN instance view and run the display this command to check the configuration of routing-table limit to check whether the set alarm threshold of private routes is proper.

    • If so, go to Step 5.
    • If not, run the routing-table limit number { alert-percent | simply-alert } command to re-configure a proper alarm threshold. Then, go to Step 6.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. End.
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 83943

Downloads: 181

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next