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.19.3.1 hwL3vpnIpv6PrefixExceed

RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed

Description

The number of IPv6 prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[VpnInstanceName], PrefixCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])

The number of IPv6 route prefixes in a VPN instance exceeded the maximum number that is allowed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwL3vpnIpv6PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.3.1

Alarm ID

0x70122013

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear

Parameters

Parameter Description

VpnInstanceName

Name of a VPN instance

PrefixCount

Current number of IPv6 route prefixes in the VPN instance

MaxValue

Maximum number of IPv6 route prefixes in the VPN instance

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.3

hwIpv6PrefixLimitVpnName

N/A

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

Cause 1:

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

Cause 2:

The maximum 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. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance exceeds the configured maximum number.

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

    • If the number of IPv6 route prefixes in the VPN instance is less than the configured maximum number, 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 the maximum number. 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: EDOC1100039527

Views: 70410

Downloads: 21

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