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

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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.3 mplsL3VpnVrfRouteMidThreshExceeded

L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

Description

L3VPN/4/L3V_TRAP_MID_EXCEED:OID [oid] The number of routes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[octet], VpnInstanceRouteCount=[gauge], MidThresholdValue=[gauge])

The number of routes contained by the specified VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of a VPN instance.

VpnInstanceRouteCount

Indicates the number of existing routes or prefixes.

MidThresholdValue

Indicates that the alarm threshold of routes or prefixes.

Impact on the System

When the total number of VPN routes or prefixes exceeds the alarm threshold, routes can still be installed to the routing table. That is, the routes are not discarded and traffic is not interrupted for the moment.

Possible Causes

1. The total number of the VPN routes in the VPN routing table exceeds the alarm threshold of VPN routes specified in the routing-table limit command, and is smaller than the maximum number of routes.

2. The total number of the VPN route prefixes in the VPN routing table exceeds the alarm threshold of VPN route prefixes specified in the prefix limit command, and is smaller than the maximum number of route prefixes.

Procedure

  1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of routes or prefixes in the VPN instance exceeds the upper limit.
  2. Analyze the source of each route and check whether the number of existing routes or 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 routes or prefixes still exceeds the alarm threshold after redundant 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 view the configuration of the routing-table limit command and the prefix limit command. Then, check whether the set alarm threshold of VPN routes is proper.

    • If so, go to Step 5.

    • If not, run the routing-table limit number { alert-percent | simply-alert } or prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of routes or prefixes. Then, go to Step 6.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None.

Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 130720

Downloads: 40

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