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

S9300, S9300E, and S9300X V200R010C00

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).
RM/4/PFXNUM_EXCD_WARN6

RM/4/PFXNUM_EXCD_WARN6

Message

RM/4/PFXNUM_EXCD_WARN6:The number of prefixes in IPv6 [vpn-instance-name] was [current-number], which exceeded the alarm threshold [threshold-value]. (InstanceId=[ULONG], MaxPrefixLimit=[ULONG])

Description

The number of prefixes for the specified IPv6 private network instance exceeded the trap threshold.

Parameters

Parameter Name Parameter Meaning
[vpn-instance-name] Indicates the name of an IPv6 VPN instance.
[current-number] Indicates the current number of prefixes.
[threshold-value] Indicates the value of the alarm threshold.
InstanceId Indicates the ID of an IPv6 VPN instance.
MaxPrefixLimit Indicates the maximum number of prefixes.

Possible Causes

The number of prefixes for the specified IPv6 private network instance exceeded the trap threshold.

Procedure

  1. Run the display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics command to check the total number of prefixes in this IPv6 VPN instance.
  2. Analyze the source of each prefix and check whether the number of current prefixes in the IPv6 VPN instance meets the requirement.

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

  3. Delete unnecessary private routes, and then check whether the number of prefixes still reaches or exceeds the alarm threshold.

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

  4. Enter the IPv6 VPN instance view and run the display this command to check the configuration of prefix limit to check whether the set alarm threshold of private prefixes is proper.

    • If so, go to Step 5.
    • If not, run the prefix limit number { alert-percent | simply-alert } command to reconfigure a proper alarm threshold. Then, go to Step 6.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142069

Views: 578446

Downloads: 37

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