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.19.2.3 hwPublicIpv6PrefixThresholdExceed

RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed

Description

The number of public IPv6 prefixes exceeded the threshold. (PrefixCount=[hwCurIpv6PrefixNum], Threshold=[hwIpv6PrefixLimitValue])

The number of IPv6 public route prefixes exceeded the value calculated using the formula (Maximum number x Threshold/100).

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwPublicIpv6PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.2.3

Alarm ID

0x70122011

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear

Parameters

Parameter Description

PrefixCount

Number of IPv6 public route prefixes in the routing table

Threshold

Threshold of the number of IPv6 public route prefixes

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 public route prefixes exceeded the value calculated using the formula (Maximum number x Threshold/100), and services may be affected if the number of IPv6 public route prefixes keeps increasing.

Possible Causes

Cause 1:

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

Cause 2:

The threshold of the number of IPv6 public route prefixes was decreased.

Procedure

  1. Run the display ipv6 routing-table statistics command to check the total number of IPv6 public route prefixes and the number of routes of each routing protocol that are added to the IPv6 routing table. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 public route prefixes exceeds the value calculated using the formula (Maximum number x Threshold/100).

    • If the number of IPv6 public route prefixes exceeds the value, go to 2.

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

  2. Delete unneeded IPv6 public 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-02

Document ID: EDOC1100074754

Views: 21742

Downloads: 30

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