Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
L3VPN/2/hwL3vpnIpv6RouteExceed_active
Message
L3VPN/2/hwL3vpnIpv6RouteExceed_active: The number of IPv6 routes in the VPN instance exceeded the maximum value.(VPN instance name=[], number of existing routes=[], maximum value=[])
Description
The number of IPv6 routes in the VPN instance exceeded the limit on the maximum number of routes allowable in the VPN instance, which was set using the routing-table limit command.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
VpnName |
Name of the VPN instance |
Current |
Number of IPv6 routes in the current VPN instance |
Max |
Maximum number of IPv6 routes allowable in a VPN instance |
Possible Causes
Cause: The number of routes to be added to the routing table of the VPN instance exceeded the limit on the maximum number of routes allowable in the VPN instance, which was set using the routing-table limit command.
Procedure
- Run the display ipv6 routing-table limit command to check the configured limit on the maximum number of routes allowable in the VPN instance and the current total number of routes.
- Run the display
ipv6 routing-table statistics command to check whether
redundant VPN routes exist in the VPN instance.
- If so, go to Step 3.
- If not, go to Step 4.
- Delete the redundant VPN routes and then check whether
the alarm persists.
- If so, go to Step 4.
- If not, go to Step 6.
- Run the display this command in the VPN instance view to
check the routing-table
limit configuration. Check whether the number of
routes in the VPN instance reaches the upper threshold.
- If yes, the alarm is informational only, and no action is required. To clear the alarm, run the routing-table limit number { alert-percent | simply-alert } command to reconfigure a proper upper threshold. Then go to Step 6.
- If not, go to Step 5.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
