RM_1.3.6.1.4.1.2011.5.25.145.19.1.3 hwPublicIpv4PrefixThresholdExceed
Description
RM/4/PUBLIC_IPV4_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of public IPv4 prefixes exceeded the threshold. (PrefixCount=[Integer], Threshold=[Integer])
The number of IPv4 public route prefixes exceeded the alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.1.3 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv4 public route prefixes in the routing table. |
Threshold |
Indicates the threshold of the number of IPv4 public route prefixes. |
Impact on the System
The number of IPv4 public route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv4 public route prefixes keeps increasing.
Possible Causes
Cause 1:
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.
Cause 2:
The threshold of the number of IPv4 public route prefixes was decreased.
Procedure
- Run the display current-configuration command to check whether the threshold value specified in the ip prefix-limit command is too small.
- Rerun the ip prefix-limit number alert-percent command to increase number and alert-percent.
-
Run the display ip routing-table statistics command
to check the number of IPv4 public 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, replace the license or contact technical support personnel for specification expansion.
-
Adjust the configurations to delete unneeded routes, and check
whether the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is not generated, go to 5.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is generated, go to 6.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
