RM/4/hwIpv4PrefixThresholdExceed_active

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 step 2. - If the threshold value is in a proper range, go to step 3. 2. Rerun 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 step 4. - If services need these routes, go to step 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. - If the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is not generated, go to step 5. - If theRM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated, go to step 6. 5. Collect alarm information and configuration information, and then contact technical support personnel. 6. End.