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 8800, 7800, 6800, and 5800 V200R005C10

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).
RM_1.3.6.1.4.1.2011.5.25.145.11.3 hwIpv6PrefixThresholdExceed

RM_1.3.6.1.4.1.2011.5.25.145.11.3 hwIpv6PrefixThresholdExceed

Description

The number of IPv6 prefixes exceeded the threshold. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv6 route prefixes exceeded the alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv6PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.3

Alarm ID

0x08390007

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear

Parameters

Parameter Description

PrefixCount

Indicates the number of IPv6 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 route prefixes supported by the device.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

Impact on the System

The number of IPv6 route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv6 route prefixes keeps increasing.

Possible Causes

The number of IPv6 prefixes exceeded the threshold of the routing table.

Procedure

  1. Run the display current-configurationcommand to check whether the threshold value specified in the ipv6 prefix-limit system threshold-alarm command is too small.

    • If the threshold value is too small, go to 2.
    • If the threshold value is in a proper range, go to 3.

  2. Run the ipv6 prefix-limit system threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to increase the value of upper-limit-value.
  3. Run the display ipv6 routing-table statistics and display ipv6 routing-table all-vpn-instance statistics commands to check the numbers of IPv6 public and private route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 4.

    • If services need these routes, go to 5.

  4. Adjust the configurations to delete unneeded routes and ensure that the number of IPv6 route prefixes falls below the lower-limit-value configured using the ipv6 prefix-limit system threshold-alarm command, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated.

  5. Reset a proper maximum number of IPv6 route prefixes supported by the device, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated.

  6. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  7. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 24559

Downloads: 31

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