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.4 hwL3vpnIpv4RouteThresholdExceedClear

L3VPN_1.3.6.1.4.1.2011.5.25.145.33.4 hwL3vpnIpv4RouteThresholdExceedClear

Description

The number of IPv4 routes in the VPN instance fell below the maximum number. (VPNInstanceName=[VpnName], NumberOfExistingRoutes=[Current], AlarmThreshold=[MidThreshold])

The number of IPv4 routes in the VPN instance fell below the middle threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwL3vpnIpv4RouteThresholdExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.33.4

Alarm ID

0x00F1022a

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

L3VPN_1.3.6.1.4.1.2011.5.25.145.33.3 hwL3vpnIpv4RouteThresholdExceed

Parameters

Parameter Description

VpnName

Name of the VPN instance

Current

Number of IPv4 routes in the current VPN instance

MidThreshold

Middle threshold

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

Services will not be affected.

Possible Causes

Cause 1: Routes were deleted by a specific protocol.

Cause 2: Configuration of the routing-table limit command was deleted or modified to increase the middle threshold so that the number of the VPN IPv4 routes was lower than the middle threshold.

Procedure

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

Document ID: EDOC1100039527

Views: 87861

Downloads: 21

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