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, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

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).
RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed

RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed

Description

RM/4/L3VPN_IPV6_PREFIX_THRESHOLD_EXCEED:OID [OID] The number of IPv6 prefixes in the VPN instance exceeded the threshold. (VpnInstanceName=[octet], PrefixCount=[Integer], Threshold=[Integer])

The number of IPv6 route prefixes in the VPN instance exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.19.3.3 Warning

qualityOfServiceAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Name of a VPN instance

PrefixCount

Current number of IPv6 route prefixes in the VPN instance

Threshold

Alarm threshold for the number of IPv6 route prefixes in the VPN instance

Impact on the System

The number of IPv6 route prefixes in the VPN instance is approaching the maximum number that is allowed, and route prefixes will no longer be accepted if the maximum number is reached, affecting services.

Possible Causes

Cause 1:

A large number of IPv6 VPN dynamic protocol (BGP or an IGP), static, direct, and UNR routes were added to the routing table.

Cause 2:

The alarm threshold for the number of IPv6 route prefixes in the VPN instance was reduced.

Procedure

  1. Run the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of route prefixes and the number of route prefixes of each protocol. Then run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold.

    • If the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold, go to Step 2.

    • If the number of IPv6 route prefixes in the VPN instance has not exceeded the alarm threshold, go to Step 3.

  2. If the configured private network prefix threshold value is too small, run the prefix limit command in the IPv6 address family view of the VPN instance to reconfigure the threshold. Then check whether the fault is rectified.

    • If yes, go to step 4.

    • If no, go to step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 69713

Downloads: 45

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