RM/4/PFXNUM_EXCD_WARN6
Message
RM/4/PFXNUM_EXCD_WARN6:The number of prefixes in IPv6 [vpn-instance-name] was [current-number], which exceeded the alarm threshold [threshold-value]. (InstanceId=[ULONG], MaxPrefixLimit=[ULONG])
Description
The number of prefixes for the specified IPv6 private network instance exceeded the trap threshold.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance-name] | Indicates the name of an IPv6 VPN instance. |
[current-number] | Indicates the current number of prefixes. |
[threshold-value] | Indicates the value of the alarm threshold. |
InstanceId | Indicates the ID of an IPv6 VPN instance. |
MaxPrefixLimit | Indicates the maximum number of prefixes. |
Possible Causes
The number of prefixes for the specified IPv6 private network instance exceeded the trap threshold.
Procedure
- Run the display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics command to check the total number of prefixes in this IPv6 VPN instance.
- Analyze the source of each prefix and check whether the
number of current prefixes in the IPv6 VPN instance meets the requirement.
- If so, go to Step 4.
- If not, go to Step 3.
- Delete unnecessary private routes, and then check whether
the number of prefixes still reaches or exceeds the alarm threshold.
- If so, go to Step 5.
- If not, go to Step 6.
- Enter the IPv6 VPN instance view and run the display
this command to check the configuration of prefix limit to check whether the set alarm threshold of private prefixes is
proper.
- If so, go to Step 5.
- If not, run the prefix limit number { alert-percent | simply-alert } command to reconfigure a proper alarm threshold. Then, go to Step 6.
- Collect log information and configuration information, and then contact technical support personnel.
- End.