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.10.3 hwIpv4PrefixThresholdExceed

RM_1.3.6.1.4.1.2011.5.25.145.10.3 hwIpv4PrefixThresholdExceed

Description

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

The number of IPv4 route prefixes exceeded the alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv4PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.10.3

Alarm ID

0x08390006

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear

Parameters

Parameter Description

PrefixCount

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

MaxValue

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

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.8.1

hwCurIpv4PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.8.2

hwIpv4PrefixLimitValue

N/A

Impact on the System

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

Possible Causes

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

Procedure

  1. Run the display current-configuration command to check whether the threshold value specified in the ip 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 ip 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 ip routing-table statistics and display ip routing-table all-vpn-instance statistics commands to check the numbers of IPv4 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 IPv4 route prefixes falls below the lower-limit-value configured using the ip prefix-limit system threshold-alarm command, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated.

  5. Run the resource u4route upper-limit resource-limit commands to reset a proper maximum number of IPv4 route prefixes supported by the device, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear 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-20

Document ID: EDOC1100039527

Views: 69776

Downloads: 21

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