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

Alarm Handling

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document provides the explanations, causes, and recommended actions of alarms 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_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Description

The number of prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])

The number of public network route prefixes exceeded the maximum limit specified using the ip prefix-limit command.

The number of VPN route prefixes in the VPN instance exceeded the maximum limit specified using the prefix limit command.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

L3VPN_MIB_TRAP_THRESH_EXCEED

Trap OID

1.3.6.1.2.1.10.166.11.0.4

Alarm ID

0x09110001

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

Parameters

Name Meaning

VpnInstanceName

Indicates the name of a VPN instance.

NOTE:

If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds the maximum limit.

VpnInstanceRouteCount

Indicates the number of existing route prefixes.

MaxValue

Indicates that the maximum number of route prefixes allowed.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.3.1.1.3

mplsL3VpnVrfPerfCurrNumRoutes

N/A

1.3.6.1.2.1.10.166.11.1.2.2.1.10

mplsL3VpnVrfConfHighRteThresh

mplsL3VpnVrfName;

Impact on the System

If the number of public network route prefixes exceeds the maximum limit:

No public network route prefixes can be added. As a result, some public network routes will be discarded and some traffic cannot be forwarded.

If the number of VPN route prefixes in the VPN instance exceeds the maximum limit:

No more VPN route prefixes can be added. As a result, some VPN routes will be discarded and some traffic cannot be forwarded.

Possible Causes

1. The number of public network route prefixes in the public network routing table exceeded the maximum limit specified using the ip prefix-limit command.

2. The number of VPN route prefixes in the VPN instance exceeded the maximum limit specified in the license or specified using the prefix limit command.

Procedure

  • Cause 1: The number of public network route prefixes in the public network routing table exceeded the maximum limit.

    1. Run the display ip routing-table limit command to check the maximum limit for public network route prefixes.

    2. Run the display ip routing-table statistics command to check whether the number of existing public network route prefixes exceeds the maximum limit.

      • If so, go to Step 4.

      • If not, go to Step 3.

    3. Check whether the number of public network route prefixes exceeds the maximum limit after excess public network routes are deleted.

      • If so, go to Step 5.

      • If not, go to Step 6.

    4. In the system view, run the display this command to check whether the ip prefix-limit command configuration is appropriate.

      • If so, go to Step 5.

      • If not, run the ip prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to set an appropriate maximum limit for public network route prefixes. Then, go to Step 6.

    5. Collect the trap information, log information, and configuration information, and contact technical personnel.

    6. End.

  • Cause 2: The number of VPN route prefixes in the VPN instance exceeded the maximum limit.

    1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of VPN 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 VPN route prefixes in the VPN instance meets the requirements.

      • If so, go to Step 4.

      • If not, go to Step 3.

    3. Check whether the number of VPN route prefixes still exceeds the maximum limit after excess VPN routes are deleted.

      • 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 the prefix limit command. Check whether the maximum limit for VPN route prefixes is appropriate.

      • If so, go to Step 5.

      • If not, run the prefix limit number { alert-percent | simply-alert } command to set an appropriate maximum limit for VPN route prefixes. Then, go to Step 6.

    5. Collect the trap information, log information, and configuration information, and contact technical personnel.

    6. End.

Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17538

Downloads: 25

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