RM/4/RT6_NUM_EXCD_WARN
Message
RM/4/RT6_NUM_EXCD_WARN:The number of routes in IPv6 [vpn-instance-name] was [current-number], which exceeded the alarm threshold [threshold-value]. (InstanceId=[ULONG], MaximumRouteLimit=[ULONG])
Description
The number of routes for the specified IPv6 private network instance exceeded the upper limit of the trap threshold.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance-name] | Indicates the name of an IPv6 VPN instance. |
[threshold-value] | Indicates the value of the trap threshold. |
InstanceId | Indicates the ID of an IPv6 VPN instance. |
MaximumRouteLimit | Indicates the maximum number of routes. |
[current-number] |
Indicates the actual number of routes. |
Possible Causes
The number of routes for the specified IPv6 private network instance exceeded the upper limit of the trap threshold.
Procedure
- Run the display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics command to check the total number and types of routes in this IPv6 VPN instance.
- Analyze the source of each route and check whether the number of current routes 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 routes 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 routing-table limit to check whether the set alarm threshold of private routes is proper.
- If so, go to Step 5.
- If not, run the routing-table 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.