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

Reminder

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

upgrade

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/PREFIX_MAX_EXCEEDED

L3VPN/4/PREFIX_MAX_EXCEEDED

Message

L3VPN/4/PREFIX_MAX_EXCEEDED:The number of route prefixes in VPN instance [vpn-instance] was [prefixes-number], which exceeded the maximum value [max-value].

Description

The number of added route prefixes exceeded the upper limit.

Parameters

Parameter Name Parameter Meaning
[vpn-instance] Indicates the name of the VPN instance.
[prefixes-number] Indicates the number of the current route prefixes.
[max-value] the upper limit for the number of route prefixes.

Possible Causes

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

Procedure

  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 sources of routes and check whether the number of current private prefixes in the VPN instance meets the requirement.

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

  3. Delete unnecessary private prefixes, and then check whether the number of prefixes 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 prefix limit to check whether the set alarm threshold of private prefixes is proper.

    • If so, go to Step 5.
    • If not, run the prefix 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.
Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 69663

Downloads: 181

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