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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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/4/hwL3vpnIpv6PrefixThresholdExceed

L3VPN/4/hwL3vpnIpv6PrefixThresholdExceed

Message

L3VPN/4/hwL3vpnIpv6PrefixThresholdExceed:The number of IPv6 prefixes in the VPN instance exceeded the threshold. (VpnInstanceName=[VpnInstanceName], PrefixCount=[PrefixCount], Threshold=[Threshold])

Description

The number of IPv6 route prefixes in a VPN instance exceeded the value calculated using the formula.

Parameters

Parameter Name Parameter Meaning

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

Possible Causes

Cause 1:

A large number of IPv6 routes were added to the routing table in the VPN instance.

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 IPv6 route prefixes in the VPN instance and the number of routes of each routing protocol that are added to the IPv6 routing table in the VPN instance. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance exceeds the value calculated using the formula.

    • If the number of IPv6 route prefixes in the VPN instance exceeds the value, go to 2.

    • If the number of IPv6 route prefixes in the VPN instance is less than the value, go to 3.

  2. Delete unneeded IPv6 VPN routes or run the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to increase alert-percent. Then, check whether the alarm persists.

    • If the alarm persists, go to 3.

    • If the alarm is cleared, go to 4.

  3. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  4. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 122424

Downloads: 90

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