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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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/L3V_TRAP_MID_EXCEED_active

L3VPN/4/L3V_TRAP_MID_EXCEED_active

Message

L3VPN/4/L3V_TRAP_MID_EXCEED_active: The number of prefixes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MidThresholdValue=[MidThresholdValue])

Description

The number of route prefixes in the VPN instance exceeded the middle threshold set by using the prefix limit number alert-percent [ route-unchanged ] command.

Parameters

Parameter Name Parameter Meaning

VpnInstanceName

VPN instance name

VpnInstanceRouteCount

Number of route prefixes in the VPN instance

MidThresholdValue

Middle threshold of the route prefixes in the VPN instance

Possible Causes

Cause: The number of prefixes contained by the specified VPN exceeds the threshold as configured by prefix limit command.

Procedure

  1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of route prefixes in the VPN instance exceeds the upper limit.
  2. Run the display ip routing-table vpn-instance vpn-instance-name statistics command to check whether the number of existing routes or prefixes in the VPN instance meets the requirements.

    • If there are redundant route prefixes, go to Step 3.
    • If there are no redundant route prefixes, go to Step 4.

  3. Delete the redundant route prefixes from the VPN instance and then check whether the alarm persists.

    • If the alarm persists, go to Step 4.
    • If the alarm is cleared, no more action needs to be taken.

  4. Run the display this command in the VPN instance view to check whether the alarm threshold is higher than the number of route prefixes in the VPN instance.

    • If the alarm threshold is higher, go to Step 5.
    • If the alarm threshold is not higher than the number of route prefixes in the VPN instance, it is a normal case that the alarm is generated. To clear the alarm, run the prefix limit number {alert-percent| simply-alert} command to configure a new alarm threshold.

  5. Contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115757

Downloads: 85

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