No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.
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

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

Possible Causes

A VPN instance attempted to obtain a static label based on existing static label configurations but failed during MPLS enabling.

Procedure

  1. Collect log information and configuration information, and then contact technical support personnel.

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:
  • all IP FRR
  • all VPN FRR

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, if the user enters No, the described log message is generated.

Procedure

  1. This log message is informational only, and no action is required.

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.

Procedure

  1. This log message is informational only, and no action is required.

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:
  • all IP FRR
  • all VPN FRR

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. If the user enters Yes, the described log message is generated.

Procedure

  1. This log message is informational only, and no action is required.

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].

Description

The number of added route prefixes fell below the upper limit.

Parameters

Parameter Name Parameter Meaning
[vpn-instance] Indicates the name of the VPN instance.
[prefixes-number] Indicates the number of current route prefixes.
[max-value] Indicates the upper limit for the number of route prefixes.

Possible Causes

The number of route prefixes in the routing table fell below the upper limit.

Procedure

  1. This log message is informational only, and no action is required.

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].

Description

The number of added route prefixes exceeded the upper limit.

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

  1. 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.
  2. 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.

  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.

  4. 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.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. 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

  1. 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.
  2. 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.

  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.

  4. 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.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. 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].

Description

The number routes fell below the upper limit.

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

The number of routes in the routing table fell below the upper limit.

Procedure

  1. This log message is informational only, and no action is required.

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].

Description

The number of added routes exceeded the upper limit.

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

  1. 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.
  2. 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.

  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.

  4. 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.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. 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].

Description

The number of routes exceeded the alarm threshold for the number of routes.

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

  1. 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.
  2. 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.

  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.

  4. 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.

  5. Collect log information and configuration information, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5540

Downloads: 15

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next