RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed
Description
RM/2/PUBLIC_IPV6_PREFIX_EXCEED:OID [oid] The number of public IPv6 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv6 public route prefixes exceeded that supported by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.2.1 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv6 public route prefixes in the routing table. |
MaxValue |
Indicates the maximum number of IPv6 public route prefixes supported by the device. |
Impact on the System
New IPv6 public route prefixes cannot be added to the routing table. Services will be affected if the number of IPv6 route prefixes keeps increasing.
Possible Causes
Cause 1:
A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.
Cause 2:
The maximum number of IPv6 public route prefixes supported by the system was decreased.
Procedure
- Run the display ipv6 routing-table statistics command
to check the number of IPv6 public route prefixes and the number of
routes of each protocol that are added to the routing table. Run the display ipv6 routing-table limit command to check
the number of IPv6 public route prefixes supported by the system.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.
- Adjust the configurations to delete unneeded
routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is not generated, go to 3.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is generated, go to 4.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
