L3VPN/2/L3V_TRAP_THRE_EXCEED_active: The number of prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])
The number of public network route prefixes exceeded the maximum limit, or the number of VPN route prefixes in the VPN instance exceeded the maximum limit.
| Parameter Name | Parameter Meaning |
|---|---|
|
VpnInstanceName |
Indicates the name of a VPN instance. If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds the maximum limit. |
|
VpnInstanceRouteCount |
Indicates the number of existing route prefixes. |
|
MaxValue |
Indicates that the maximum number of route prefixes allowed. |
Cause 1: The number of received public network route prefixes exceeded the maximum number of route prefixes configured for the IPv4 public network routing table.
Cause 2: The number of received VPN route prefixes exceeded the maximum number of VPN route prefixes defined in the license file or that configured for the routing table of the VPN instance.
Cause1: The number of public network route prefixes in the public network routing table exceeded the maximum limit. 1. Run the display ip routing-table limit command to check the maximum limit for public network route prefixes. 2. Run the display ip routing-table statistics command to check whether the number of existing public network route prefixes exceeds the maximum limit. - If so, go to Step 4. - If not, go to Step 3. 3. Check whether the number of public network route prefixes exceeds the maximum limit after deleting excess public network routes. - If so, go to Step 5. - If not, go to Step 6. 4. In the system view, run the display this command to check whether the ip prefix-limit command configuration is appropriate. - If so, go to Step 5. - If not, run the ip prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to set an appropriate maximum limit for public network route prefixes. Then, go to Step 6. 5. Collect alarm information and configuration information, and then contact technical support personnel. 6. End. Cause2: The number of VPN route prefixes in the VPN instance exceeded the maximum limit. 1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of VPN route prefixes in the VPN instance exceeds the upper limit. 2. Run the display ip routing-table vpn-instance vpn-instance-name statistics command to check whether the number of existing VPN route prefixes in the VPN instance meets the requirements. - If so, go to Step 4. - If not, go to Step 3. 3. Check whether the number of VPN route prefixes still exceeds the maximum limit specified in the license or specified using the prefix limit command after deleting excess VPN routes. - If so, go to Step 5. - If not, go to Step 6. 4. Enter the VPN instance view and run the display this command to check the configuration of the prefix limit command. Check whether the maximum limit for VPN route prefixes is appropriate. - If so, go to Step 5. - If not, run the prefix limit number { alert-percent | simply-alert } command to set an appropriate maximum limit for VPN route prefixes. Then, go to Step 6. 5. Collect alarm information and configuration information, and then contact technical support personnel. 6. End.