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).
GRE

GRE

GRE/6/GRE_CAMP

Message

GRE/6/GRE_CAMP:The specification of the GRE module is compatible, and lossless upgrade is supported.

Description

The module was compatible in specifications and supported the lossless ISSU.

Parameters

Parameter Name Parameter Meaning
None None.

Possible Causes

The GRE module was compatible in specifications.

Procedure

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

GRE/4/GRE_CAMPNUM_UNCAMP

Message

GRE/4/GRE_CAMPNUM_UNCAMP:The compatible number of the GRE module is not compatible.

Description

Data of two versions in the GRE module is not compatible according to the compatible ID check.

Parameters

Parameter Name Parameter Meaning
None None.

Possible Causes

Data of two versions in the GRE module is not compatible according to the compatible ID check.

Procedure

  • Lossy ISSU is performed, and no action is required.

GRE/6/GRE_DOWN_REASON

Message

GRE/6/GRE_DOWN_REASON:The line protocol on the interface [interface] has entered the DOWN state, reason is:[reason].

Description

The link-layer protocol of a GRE tunnel interface went Down.

Parameters

Parameter Name Parameter Meaning
interface Interface name
reason Reason that the link protocol of the GRE tunnel interface went Down

Possible Causes

  • GRE function is disabled: The GRE PAF (PAF_LCS_TUNNEL_SPECS_GRE_FUNC_ENABLED) was disabled.

  • Tunnel interface is shutdown: The GRE tunnel interface was shut down.

  • Source or destination check is incorrect: The source or destination configuration on the GRE tunnel interface was incorrect.

  • Tunnel interface has no ip address: The GRE tunnel interface had no IPv4 or IPv6 address configured.

  • Source interface is deleted: The source interface specified for the GRE tunnel interface did not exist.

  • Tunnel recursion overload: The number of tunnel recursion layers of the source interface for the GRE tunnel interface is greater than two.

  • Tunnel interface has no destination: The GRE tunnel interface did not have a destination address configured.

  • Source interface is not up: The source interface specified for the GRE tunnel interface went Down.

  • TSU board is inactive: The GRE tunnel interface was bound to a false interface board, or the GRE license was disabled.

  • Different VRFs for source and destination: The VPN instance to which the destination IP address of the GRE tunnel interface belongs differs from the VPN instance bound to the source interface.

  • Slot is not up: The interface board on which the GRE tunnel interface resides went Down.

  • Destination IP is same as tunnel IP: The destination IP address of the GRE tunnel interface was the same as the IP address of the GRE tunnel interface itself.

  • Out interface cannot be tunnel interface: The outbound interface of the route destined for the destination IP address of the GRE tunnel interface was the GRE tunnel interface itself.

  • No route to destination: No route was reachable to the destination IP address of the GRE tunnel interface.

  • Keepalive is unreachable: The keepalive detection on the GRE tunnel interface timed out.

  • Tunnel forwarding information is incorrect: The GRE tunnel interface had an incorrect forwarding entry.

  • Out Interface Of Tunnel Is Wrong Under Route-Via Mandatory Mode: The outbound interface strictly specified for the GRE tunnel interface was incorrect.

  • Hybrid Bonding request not Success: The application for a GRE tunnel used for hybrid bonding failed.

  • Both bonding master and backup destination can't make tunnel up: The master and backup destination addresses of the GRE tunnel interface could not make the GRE tunnel go Up.

  • Invalid information: unknown reason.

  • BFD is down: The BFD session went Down.

Procedure

  • GRE function is disabled: Enable the GRE PAF (PAF_LCS_TUNNEL_SPECS_GRE_FUNC_ENABLED).
  • Tunnel interface is shutdown: Run the undo shutdown command in the GRE tunnel interface view.
  • Source or destination check failed: Correct the source or destination configuration on the GRE tunnel interface.
  • Tunnel interface has no ip address: Configure a correct IPv4 or IPv6 address for the GRE tunnel interface.
  • Source interface is deleted: Configure a correct source interface for the GRE tunnel interface.
  • Tunnel recursion overload: Reduce the tunnel recursion layers of the source interface to be less than two.
  • Tunnel interface has no destination: Configure a correct destination IP address for the GRE tunnel interface.
  • Source interface is not up: Specify a correct source interface for the GRE tunnel interface.
  • TSU board is inactive: Bind the GRE tunnel interface to a correct interface board or enable the GRE license.
  • Different VRFs for source and destination: Configure the same VPN instance for the destination IP address of the GRE tunnel interface and for the source interface.
  • Slot is not up: Enable the interface board on which the GRE tunnel interface resides to go Up.
  • Destination IP is same as tunnel IP: Configure a destination IP address different from the IP address of the GRE tunnel interface for the GRE tunnel interface.
  • Out interface cannot be tunnel interface: Set the outbound interface of the route destined for the destination IP address of the GRE tunnel interface to an interface other than the GRE tunnel interface.
  • No route to destination: Ensure that there are routes reachable to the destination IP address of the GRE tunnel interface.
  • Keepalive is unreachable: Ensure that the intermediate link connected to the GRE tunnel interface can be used for communication.
  • Tunnel forwarding information error: Collect log information and configuration information, and then contact technical support personnel.
  • Out Interface Of Tunnel Is Wrong Under Route-Via Mandatory Mode: If an outbound interface is strictly specified, ensure that the specified outbound interface is included in the GRE tunnel outbound interfaces.
  • Hybrid Bonding request not Success: Collect log information and configuration information, and then contact technical support personnel.
  • Both bonding master and backup destination can't make tunnel up: Collect log information and configuration information, and then contact technical support personnel.
  • Invalid information: Collect log information and configuration information, and then contact technical support personnel.
  • BFD is down: Ensure that the GRE tunnel bound to the BFD session works properly.

GRE/4/GRE_MAXNUM_UNCAMP

Message

GRE/4/GRE_MAXNUM_UNCAMP:The number of GRE tunnels [tunnel-number1] configured on the old main control board is greater than the maximum number of GRE tunnels [tunnel-number2] that can be configured on the new main control board.

Description

The number of GRE tunnels on the main control board running the system software of the previous version before the master-slave switchover was larger than the maximum number of GRE tunnels permitted on the main control board running the system software of the new version.

Parameters

Parameter Name Parameter Meaning
[tunnel-number1] Number of the current GRE tunnels on the main control board running the system software of the previous version before the master-slave switchover
[tunnel-number2] Maximum number of configurable GRE tunnels permitted on the main control board running the system software of the new version after the master-slave switchover

Possible Causes

The number of permitted GRE tunnels on the main control board is reduced in the new system software version. As a result, the number of GRE tunnels on the master main control board running the old system software version was larger than the maximum number of GRE tunnels permitted on the main control board running the new system software version.

Procedure

  • Check specifications and configurations and ensure that, after the mater-slave switchover the maximum number of configurable GRE tunnels on the main control board running the system software of the new version is larger than the number of GRE tunnels on the main control board running the system software of the previous version. You can purchase more PAF files/licenses from Huawei to make specifications satisfied. Otherwise, some configurations will be lost.

GRE/4/GRE_UNIDE_SPEC_T

Message

GRE/4/GRE_UNIDE_SPEC_T:Obtain an unknown object type when parsing the GRE tunnel specification. (Type=[ULONG])

Description

An unknown object type was obtained in the process of parsing the specifications of the TLV-encapsulated GRE tunnel.

Parameters

Parameter Name Parameter Meaning
Type Object type

Possible Causes

An incorrect object type was obtained.

Procedure

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

Document ID: EDOC1100065665

Views: 6220

Downloads: 15

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