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 12800 and 12800E V200R005C00

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.1 hwIpv6PrefixExceed

RM_1.3.6.1.4.1.2011.5.25.145.11.1 hwIpv6PrefixExceed

Description

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

The number of IPv6 prefixes exceeded the maximum value.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIpv6PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.1

Alarm ID

0x08390005

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.2 hwIpv6PrefixExceedClear

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

If more IPv6 routes are added, they will be discarded. As a result, traffic may be interrupted.

Possible Causes

The number of IPv6 prefixes exceeded the maximum value configured using the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command.

Procedure

  1. Run the display ipv6 routing-table statistics command to check the number of IPv6 public route prefixes and the display ipv6 routing-table all-vpn-instance statistics command to check the number of IPv6 VPN route prefixes.
  2. Check whether the number of route prefixes of each protocol is within the normal range.

    • If the number of route prefixes of each protocol is within the normal range, go to 4.
    • If the number of route prefixes of each protocol is not within the normal range, go to 3.

  3. Delete unneeded IPv6 routes and then check whether the alarm persists.

    • If the alarm persists, go to 4.
    • If the alarm is cleared, go to 6.

  4. Run the display virtual-system [ name vs-name ] resource command to check whether the configured maximum number of IPv6 prefixes is greater than the actual number.

    • If the configured maximum number of IPv6 prefixes is greater than or equal to the actual number, go to 5.
    • If the configured maximum number of IPv6 prefixes is less than the actual number, run the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to reconfigure the maximum number and go to 6.

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

Document ID: EDOC1100039527

Views: 68141

Downloads: 21

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