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 12800 and 12800E V200R005C00

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.4.1.2011.5.25.145.33.1 hwL3vpnIpv4RouteExceed

L3VPN_1.3.6.1.4.1.2011.5.25.145.33.1 hwL3vpnIpv4RouteExceed

Description

The number of IPv4 routes in the VPN instance exceeded the maximum value.(VPNInstanceName=[VpnName], NumberOfExistingRoutes=[Current], MaximumValue=[Max])

The number of IPv4 routes in the VPN instance exceeded the maximum number that is allowed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwL3vpnIpv4RouteExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.33.1

Alarm ID

0x00F1021c

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.4.1.2011.5.25.145.33.2_hwIpv4RouteExceedClear

Parameters

Parameter Description

VpnName

Name of the VPN instance

Current

Number of IPv4 routes in the current VPN instance

Max

Maximum number of IPv4 routes allowable in a VPN instance

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.31.1

hwCurIpv4RouteNum

N/A

1.3.6.1.4.1.2011.5.25.145.31.2

hwIpv4RouteLimitValue

N/A

1.3.6.1.4.1.2011.5.25.145.31.3

hwIpv4RouteLimitVpnName

N/A

Impact on the System

If the number of VPN IPv4 routes exceeds the upper threshold, the excessive routes cannot be added to the VPN instance's routing table, causing these routes to be lost and some traffic to be interrupted.

Possible Causes

Cause 1: The number of VPN IPv4 routes to be added to the routing table exceeded the upper threshold of the VPN instance.

Cause 2: The routing-table limit command was run, or the existing configuration of this command was modified to reduce the limit on the maximum number of routes allowable in the IP address family of the VPN instance.

Procedure

  1. Run the display ip routing-table limit command to check the configured limit on the maximum number of routes allowable in the VPN instance and the current total number of routes.
  2. Run the display ip routing-table statistics command to check whether redundant VPN routes exist in the VPN instance.

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

  3. Delete the redundant VPN routes and then check whether the alarm persists.

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

  4. Run the display this command in the VPN instance view to check the routing-table limit configuration. Check whether the number of routes in the VPN instance reaches the upper threshold.

    • If so, the alarm is informational only, and no action is required. To clear the alarm, run the routing-table limit number { alert-percent | simply-alert } command to reconfigure a proper limit on the maximum number of routes. Then go to Step 6.
    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 68043

Downloads: 21

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