L3VPN
L3VPN/3/L3V_STATICLABEL_FAIL
Message
L3VPN/3/L3V_STATICLABEL_FAIL:Failed to allocate static label [label-value] to VPN instance [vpn-instance]. The static label configuration was deleted.
Description
A VPN instance failed to obtain a static label and static label configurations were deleted.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[label-value] | Value of the static label configured for a VPN instance. |
[vpn-instance] | Name of a VPN instance |
L3VPN/6/L3V_UNDOFRRNO
Message
L3VPN/6/L3V_UNDOFRRNO:When deciding whether to delete [configuration] configuration, the user chose NO.
Description
After a user entered the undo ip frr all command to delete the IP FRR configuration or the undo vpn frr all command to delete the VPN FRR configuration, the user entered No to cancel the operation.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[configuration] | Name of the FRR configuration to be deleted. The
value can be:
|
L3VPN/6/L3V_UNDOFRRTIMEOUT
Message
L3VPN/6/L3V_UNDOFRRTIMEOUT:When a user did not input any word in [time]s, the system exited from the operation automatically.
Description
After a user entered the undo ip frr all command to delete the IP FRR configuration or the undo vpn frr all command to delete the VPN FRR configuration, the system displayed a confirmation message. The user did not confirm the operation within a specified period of time and the system canceled the operation.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[time] | Waiting period for a user to confirm an operation. The default value is 30s. |
Possible Causes
After a user enters the undo ip frr all command to delete the IP FRR configuration or the undo vpn frr all command to delete the VPN FRR configuration, the system displays a confirmation message. If the user does not confirm the operation within the specified time, the system cancels the operation and generates the described log.
L3VPN/6/L3V_UNDOFRRYES
Message
L3VPN/6/L3V_UNDOFRRYES:When deciding whether to delete [configuration] configuration, the user chose YES.
Description
After a user entered the undo ip frr all command to delete the IP FRR configuration or the undo vpn frr all command to delete the VPN FRR configuration, the system displayed a confirmation message. The user entered Yes to continue the operation.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[configuration] | Name of the FRR configuration to be deleted. The
value can be:
|
L3VPN/4/PREFIX_MAX_CLEARED
Message
L3VPN/4/PREFIX_MAX_CLEARED:The number of route prefixes in VPN instance [vpn-instance] reduced to [prefixes-number], which was below the maximum value [max-value].
L3VPN/4/PREFIX_MAX_EXCEEDED
Message
L3VPN/4/PREFIX_MAX_EXCEEDED:The number of route prefixes in VPN instance [vpn-instance] was [prefixes-number], which exceeded the maximum value [max-value].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance] | Indicates the name of the VPN instance. |
[prefixes-number] | Indicates the number of the current route prefixes. |
[max-value] | the upper limit for the number of route prefixes. |
Possible Causes
After the number of route prefixes in the routing table reached the upper limit, new routes continued to be added.
Procedure
- Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to check the total number and types of routes in this VPN instance.
- Analyze the sources of routes and check whether the number
of current private prefixes in the VPN instance meets the requirement.
- If so, go to Step 4.
- If not, go to Step 3.
- Delete unnecessary private prefixes, 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 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 re-configure a proper alarm threshold. Then, go to Step 6.
- Collect log information and configuration information, and then contact technical support personnel.
- End.
L3VPN/4/PREFIX_MID_EXCEEDED
Message
L3VPN/4/PREFIX_MID_EXCEEDED:The number of route prefixes in VPN instance [vpn-instance] was [prefixes-number], which exceeded the [threshold-value].
Description
The number of added route prefixes exceeded the alarm threshold for the number of route prefixes.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance] | Indicates the name of the VPN instance. |
[prefixes-number] | Indicates the number of the current route prefixes. |
[threshold-value] | the upper limit for the number of route prefixes. |
Possible Causes
After the number of route prefixes in the routing table reached the alarm threshold, new route prefixes continued to be added.
Procedure
- Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to check the total number and types of routes in this VPN instance.
- Analyze the sources of routes and check whether the number
of current private prefixes in the VPN instance meets the requirement.
- If so, go to Step 4.
- If not, go to Step 3.
- Delete unnecessary private prefixes, 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 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 re-configure a proper alarm threshold. Then, go to Step 6.
- Collect log information and configuration information, and then contact technical support personnel.
- End.
L3VPN/4/ROUTE_MAX_CLEARED
Message
L3VPN/4/ROUTE_MAX_CLEARED:The total number of routes in VPN instance [vpn-instance] reduced to [route-number], which was below the maximum value [maximum-value].
L3VPN/4/ROUTE_MAX_EXCEEDED
Message
L3VPN/4/ROUTE_MAX_EXCEEDED:The total number of routes in VPN instance [vpn-instance] was [route-number], which exceeded the maximum value [maximum-value].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance] | Indicates the name of the VPN instance. |
[route-number] | Indicates the number of the current routes. |
[maximum-value] | Indicates the maximum of the routes. |
Possible Causes
After the number of routes in the routing table reached the upper limit, new routes continued to be added.
Procedure
- Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to check the total number and types of routes in this VPN instance.
- Analyze the source of each route and check whether the number of current routes in the VPN instance meets the actual 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 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 re-configure a proper alarm threshold. Then, go to Step 6.
- Collect log information and configuration information, and then contact technical support personnel.
- End.
L3VPN/4/ROUTE_MID_EXCEEDED
Message
L3VPN/4/ROUTE_MID_EXCEEDED:The total number of routes in VPN instance [vpn-instance] was [route-number], which exceeded the alarm threshold [threshold-value].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[vpn-instance] | Indicates the name of the VPN instance. |
[route-number] | Indicates the number of the current routes. |
[threshold-value] | Indicates the alarm threshold for the number of routes. |
Possible Causes
After the number of routes in the routing table reached the alarm threshold, new routes continued to be added.
Procedure
- Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to check the total number and types of routes in this VPN instance.
- Analyze the source of each route and check whether the number of current routes in the 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 VPN instance view and run the display this command to check the configuration of route 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 re-configure a proper alarm threshold. Then, go to Step 6.
- Collect log information and configuration information, and then contact technical support personnel.
- End.