L3VPN/4/L3V_TRAP_MID_EXCEED_active

Message

L3VPN/4/L3V_TRAP_MID_EXCEED_active: The number of prefixes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MidThresholdValue=[MidThresholdValue])

Description

The number of public network route prefixes exceeded the middle threshold, or the number of route prefixes contained by the specified VRF exceeded the middle threshold.

Parameters

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 or is about to exceed the maximum limit.
VpnInstanceRouteCount	Indicates the number of existing route prefixes.
MidThresholdValue	Indicates that the alarm threshold of route prefixes.

Possible Causes

Cause 1: The number of received public network route prefixes exceeded the upper threshold multiplied by the maximum number allowed but was less than the maximum number allowed.

Cause 2: The number of received VPN route prefixes exceeded the upper threshold multiplied by the maximum number allowed but was less than the maximum number allowed.

Procedure

Cause 1: The total number of public network route prefixes exceeds the alarm threshold of public route prefixes specified in the ip prefix-limit command, and is smaller than the maximum number of route prefixes.

1. Run the display ip routing-table limit command to check whether the number of public network route prefixes exceeds the upper limit.

2. Run the display ip routing-table statistics command to check whether the number of existing public network route prefixes meets the requirements.

If so, go to Step 4.
If not, go to Step 3.

3. Check whether the number of route prefixes still exceeds the alarm threshold after redundant public routes are deleted.

If so, go to Step 5.
If not, go to Step 6.

4. In the system view and run the display this command to view the configuration of the ip prefix-limit command. Then, check whether the set alarm threshold of public routes is proper.

If so, go to Step 5.
If not, run the prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of route prefixes. Then, go to Step 6.

5. Collect alarm information and configuration information, and then contact technical support personnel.

6. End.

Cause 2: The total number of the VPN route prefixes in the VPN routing table exceeds the alarm threshold of VPN route prefixes specified in the prefix limit command, and is smaller than the maximum number of route prefixes.

1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of 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 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 route prefixes still exceeds the alarm threshold after redundant VPN routes are deleted.

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 view the configuration of the prefix limit command. Then, check whether the set alarm threshold of VPN routes is proper.

If so, go to Step 5.
If not, run the prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of route prefixes. Then, go to Step 6.

5. Collect alarm information and configuration information, and then contact technical support personnel.

6. End.