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

LDP

LDP/6/DATASMTHBEGAN

Message

LDP/6/DATASMTHBEGAN:LDP data smooth began.

Description

LDP data smooth began.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The local entity event was created when the route was started.

Procedure

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

LDP/4/FAILALLOCTOKEN

Message

LDP/4/FAILALLOCTOKEN:Cannot allocate a token to FEC [ip-address]. (NextHop=[ULONG1], ErrorStatus=[ULONG2])

Description

Failed to allocate a token for FEC.

Parameters

Parameter Name Parameter Meaning
[ip-address] Indicates the IP address of FEC.
NextHop Indicates the IP address of the next hop.
ErrorStatus Indicates the returned errored status when allocating a token was failed
1: indicates the LSPM ERR.
  • Failed to allocate a token because obtaining interface information by interface index was failed.

  • Failed to allocate a token because the system resources were insufficient.

Possible Causes

The management module failed to allocate a token for LDP.

Procedure

  1. Run the display tunnel-info statistic command to check whether the tunnel management module has enough tunnels.

LDP/4/FAILEXITMUL

Message

LDP/4/FAILEXITMUL:Cannot exit the UDP multicast group. (ErrorCode=[LONG])

Description

Failed to exit the UDP multicast group.

Parameters

Parameter Name Parameter Meaning
ErrorCode Indicates the error code, such as -107, 0, -105, -108, -106, -22.

Possible Causes

Failed to exit the UDP multicast group.

Procedure

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

LDP/4/FAILJOINMUL

Message

LDP/4/FAILJOINMUL:Cannot join the UDP multicast group. (ErrorCode=[LONG])

Description

Failed to add to the UDP multicast group.

Parameters

Parameter Name Parameter Meaning
ErrorCode Indicates the error code, such as -107, 0, -105, -108, -106, -22.

Possible Causes

Failed to add to the UDP multicast group.

Procedure

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

LDP/4/FAILSENDMSG

Message

LDP/4/FAILSENDMSG:Cannot send TCP message. (PeerIP=[STRING], MessageLength=[ULONG], SocketId=[ULONG], ErrorSocketStatus=[LONG])

Description

Failed to send the TCP message.

Parameters

Parameter Name Parameter Meaning
PeerIP Indicates the IP address of the peer.
MessageLength Indicates the message length.
SocketId Indicates the socket ID.
ErrorSocketStatus Indicates the error socket state, such as -107, 0, -105, -108, -106, -22.

Possible Causes

Failed to send the TCP packet with the following attributes.

Procedure

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

LDP/6/GRCRTFORWDTMR

Message

LDP/6/GRCRTFORWDTMR:LDP System-level GR timer interval was set to [interval] seconds.

Description

The LDP system-level GR timer interval was set to required seconds.

Parameters

Parameter Name Parameter Meaning
[interval] Indicates the system-level timer interval.

Possible Causes

LDP created a timer for MPLS GR.

Procedure

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

LDP/6/GREND

Message

LDP/6/GREND:LDP GR was complete.

Description

LDP GR was complete.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

LDP GR was complete.

Procedure

  1. This log message indicates a normal situation, and no action is required.

LDP/4/HOLDTMREXP

Message

LDP/4/HOLDTMREXP:Sessions were deleted because the hello hold timer expired. (PeerId=[STRING], SessionState=[STRING])

Description

Sessions were deleted because the neighbor hold timer expired.

Parameters

Parameter Name Parameter Meaning
PeerId Indicates the LSR ID of the peer.
SessionState Indicates the session status.

Possible Causes

Sessions were deleted because the Hello hold timer expired.

Procedure

  1. Run the display ip routing-table command to check whether the peer system is stable and the network status is normal.

LDP/4/IFJIONFAIL

Message

LDP/4/IFJIONFAIL:The interface [interface-name] cannot join the multicast group. Retry times exceeded the maximum retries [times].

Description

The interface failed to add to the multicast group. Retry times exceeded the maximum retries.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.
[times] Indicates the maximum retry times, 60 times.

Possible Causes

1: The configuration of the interface that applied for adding to the multicast group was incorrect.

2: The ID of the instance that applied for adding to the multicast group was invalid.

Procedure

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

LDP/4/IFJIONSUCC

Message

LDP/4/IFJIONSUCC:The interface [interface-name] succeeded in joining the multicast group after retrying [times] times.

Description

The interface succeeded in adding to the multicast group after retrying multiple times.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.
[times] Indicates the maximum retry times, 60 times.

Possible Causes

The interface succeeded in adding to the multicast group.

Procedure

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

LDP/4/IMPMSGLISTEXCEED

Message

LDP/4/IMPMSGLISTEXCEED:The length of the LDP important message list reached the alarm threshold [threshold].

Description

The length of the LDP important message list reached the alarm threshold.

Parameters

Parameter Name Parameter Meaning
[threshold] Indicates the alarm threshold of the LDP message list.

Possible Causes

After a large number of LDP messages were received, these messages were not processed in time, causing the queue length to the alarm threshold.

Procedure

  1. Run the display memory-usage command to check memory usage.
  2. If necessary and allowed, run the reset mpls ldp command in the user view to clean the linked list. Exercise caution when running this command because all LDP sessions will be reset.
  3. Collect log information and configuration information, and then contact technical support personnel.

LDP/4/INSTAIDINVALID

Message

LDP/4/INSTAIDINVALID:The interface [interface-name] cannot join the multicast group because the private network ID was invalid.

Description

Failed to add to the multicast group because the private network ID was invalid.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.

Possible Causes

Failed to add to the multicast group.

Procedure

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

LDP/4/JIONRETRYFAIL

Message

LDP/4/JIONRETRYFAIL:The interface [interface-name] cannot join the multicast group after retrying [times] times.

Description

The number of times that the interface failed to add to the multicast group.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.
[times] Indicates the maximum retry times, 60 times.

Possible Causes

LDP instance failed to add to the multicast group because of timeout.

Procedure

  1. Check whether the configuration of the interface that applies for adding to the multicast group is correct.
  2. Check whether the number of instances that apply for adding to the multicast group is too large.

LDP/6/NOENABLELDP

Message

LDP/6/NOENABLELDP:LDP System-level GR processing was complete because LDP is not enabled globally.

Description

LDP System-level GR processing was complete because LDP is not enabled globally.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

LDP was not enabled globally.

Procedure

  1. Run the display current-configuration command to check whether the MPLS LDP is enabled globally.

LDP/6/NOTIGRSTART

Message

LDP/6/NOTIGRSTART:The system notified L2VPN and other features that LDP system-level GR processing started after LDP GR was enabled.

Description

The system notified L2VPN and other features that LDP system-level GR processing started after LDP GR was enabled.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

LDP notified the GR event to the L2VPN.

Procedure

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

LDP/4/OPENRETRYTMR

Message

LDP/4/OPENRETRYTMR:When the interface [interface-name] cannot join the multicast group, the retry timer was opened.

Description

When the interface failed to add to the multicast group, the reconnection timer was restarted.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.

Possible Causes

1: Incorrect configurations of the interface that applies for adding to the multicast group resulted in failing to add to the multicast group. Restarted the timer that added to the multicast group. The precondition was that the interval of the timer did not exceed the maximum interval.

2: The invalid ID of the instance that applies for adding to the multicast group resulted in failing to add to the multicast group. Restarted the timer that added to the multicast group. The precondition was that the interval of the timer did not exceed the maximum interval.

Procedure

  1. Run the display current-configuration command to check the configuration of the interface that applies for adding to multicast is correct.
  2. Check whether the number of instances that apply for adding to the multicast group is too large.
  3. Collect log information and configuration information, and then contact technical support personnel.

LDP/6/PEERCLS

Message

LDP/6/PEERCLS:The message that the peer closed was received from TCP Socket ID [socket-id].

Description

The message that the peer closed was received from the TCP socket ID

Parameters

Parameter Name Parameter Meaning
[socket-id] Indicates the socket ID.

Possible Causes

LDP received the event that the peer closed from the TCP.

Procedure

  1. Run the display interface command to check whether the link status is stable.

LDP/6/PEERRESTART

Message

LDP/6/PEERRESTART:The peer LSR [peer-id] was restarting.

Description

The peer LSR was being restarted.

Parameters

Parameter Name Parameter Meaning
[peer-id] Indicates the peer LSR ID.

Possible Causes

The local end set up the session with the peer end when the neighboring device was restarted or the session flapped. The precondition was that the LDP GR was configured before the LSR connection was established.

Procedure

  1. If the peer is restarted, this log message indicates a normal situation, and no action is required.
  2. If the session flaps, run the display interface command to check whether links between the two devices are normal and run the display tcp status command to check whether TCP connections are normal.

LDP/6/RCVFTMSG

Message

LDP/6/RCVFTMSG:Received FT message from peer [peer-id].

Description

The message that the peer enabled graceful restart was received from the peer.

Parameters

Parameter Name Parameter Meaning
[peer-id] Indicates the LSR ID of the peer.

Possible Causes

The initialization message that the peer enabled graceful restart was received.

Procedure

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

LDP/6/RMGREND

Message

LDP/6/RMGREND:The event that GR of the route management (RM) module was complete was received.

Description

The event that GR of the route management module was complete was received.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The relevant module completed GR after the device was restarted, and notified the module.

Procedure

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

LDP/4/SAMADDRESS

Message

LDP/4/SAMADDRESS:Received same address from different sessions. (Address=[STRING], OldPeer=[STRING], NewPeer=[STRING])

Description

The same address from different sessions was received.

Parameters

Parameter Name Parameter Meaning
Address Indicates the LSR ID of the peer.
OldPeer Indicates the LSR ID of the old peer.
NewPeer Indicates the LSR ID of the new peer.

Possible Causes

The same address from different peers was received.

Procedure

  1. Run the display current-configuration command to check whether the same address is configured.
  2. Operators should check whether network attacks exist.

LDP/6/SMTHCOMPL

Message

LDP/6/SMTHCOMPL:LDP data smooth was complete.

Description

LDP data smooth was complete.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

Data smooth backup was complete.

Procedure

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

LDP/6/SMTHREJIONMUL

Message

LDP/6/SMTHREJIONMUL:The interface [interface-name] retried joining the multicast group during data smooth.

Description

The interface retried to add to the multicast group during data smooth.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.

Possible Causes

The switchover between the master board and the slave board was performed.

Procedure

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

LDP/6/SRVREFUSE

Message

LDP/6/SRVREFUSE:The server refused the request of the instance [instance-name]. (PeerIP=[STRING], SocketId=[USHORT])

Description

The server refused the request of the instance [instance-name].

Parameters

Parameter Name Parameter Meaning
[instance-name] Indicates the name of instance.
PeerIP Indicates the IP address of the peer.
SocketId Indicates the socket ID.

Possible Causes

The client establishing the TCP connection did not receive the message for establishing the connection from the peer when sending the connection request.

Procedure

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

LDP/4/SSNHOLDTMREXP

Message

LDP/4/SSNHOLDTMREXP:Sessions were deleted because the session hold timer expired and the notification of the expiry was sent to the peer [peer-id]. (SessionState=[STRING])

Description

The session was deleted because the session hold timer timed out and the notification that the timer timed out was sent to the peer.

Parameters

Parameter Name Parameter Meaning
[peer-id] Indicates the LSR ID of the peer.
SessionState Indicates the session status.

Possible Causes

The session hold timer timed out and the notification that the timer timed out was sent to the peer.

Procedure

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

LDP/6/SYSGRBEGIN

Message

LDP/6/SYSGRBEGIN:LDP System-level GR processing began.

Description

LDP System-level GR processing began.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The slave board was started.

Procedure

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

LDP/6/SYSGREND

Message

LDP/6/SYSGREND:LDP System-level GR processing was complete.

Description

LDP System-level GR processing was complete.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

System-level GR processing was complete.

Procedure

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

LDP/6/SYSGRNOENABLEMPLS

Message

LDP/6/SYSGRNOENABLEMPLS:LDP System-level GR processing was complete because mpls is not enabled globally.

Description

LDP System-level GR processing was complete because mpls is not enabled globally.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

MPLS is not enabled globally.

Procedure

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

LDP/6/SYSGRNOLDPGR

Message

LDP/6/SYSGRNOLDPGR:The system notified other features that LDP system-level GR ended when LDP GR was not enabled.

Description

The system notified other features that LDP system-level GR ended when LDP GR was not enabled.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

LDP GR was not enabled.

Procedure

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

LDP/6/WAITPEERGR

Message

LDP/6/WAITPEERGR:Wait for peer restart, peer session subject to graceful restart. (VRF=[STRING], PeerAddress=[STRING])

Description

The neighbor GR was being restarted and waited GR of the peer to be restarted.

Parameters

Parameter Name Parameter Meaning

VRF

  • For public network, the VRF is public(0).
  • For private network, the VRF isVRF-Name(VRP-Index).

PeerAddress

Indicates the LSR ID of the peer.

Possible Causes

The LDP session was negotiated to be re-established when the peer LSR was enabled with graceful restart.

Procedure

  1. This log message is informational only, and no action is required.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5495

Downloads: 15

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