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


To have a better experience, please upgrade your IE browser.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

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. hwIpv4PrefixExceed

RM_1. hwIpv4PrefixExceed


RM/2/IPV4_PREFIX_EXCEED:OID [oid] The number of IPv4 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 route prefixes exceeded that supported by the device.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


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


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

Impact on the System

New IPv4 route prefixes cannot be added to the routing table. Services will be affected if the number of IPv4 route prefixes keeps increasing.

Possible Causes

A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, direct routes, or UNR routes were added to the routing table.


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

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  2. Adjust the configurations to delete unneeded routes, and check whether the RM_1. hwIpv4PrefixExceedClear alarm is generated.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 101799

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next