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

RSVP

RSVP/6/DISABLE_MPLS

Message

RSVP/6/DISABLE_MPLS:RSVP was disabled successfully in the MPLS view.

Description

Succeeded in disabling RSVP in the MPLS view.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

Succeeded in disabling RSVP in the MPLS view.

Procedure

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

RSVP/6/ENABLE_INTF

Message

RSVP/6/ENABLE_INTF:RSVP TE was enabled successfully on interface [InterfaceName].

Description

Succeeded in enabling RSVP in the interface view.

Parameters

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

Possible Causes

Succeeded in enabling RSVP in the interface view.

Procedure

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

RSVP/6/ENABLE_MPLS

Message

RSVP/6/ENABLE_MPLS:RSVP was enabled successfully in the MPLS view.

Description

Succeeded in enabling RSVP in the MPLS view.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

Succeeded in enabling RSVP in the MPLS view.

Procedure

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

RSVP/6/FUNC_SPEC_AVAIL

Message

RSVP/6/FUNC_SPEC_AVAIL:RSVP function was enabled.

Description

The RSVP function was enabled.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The RSVP function was enabled.

Procedure

  1. This log message is informational only. RSVP specifications are controlled using a license file.

RSVP/6/FUNC_SPEC_UNAVAIL

Message

RSVP/6/FUNC_SPEC_UNAVAIL:RSVP function was disabled.

Description

The RSVP function was disabled.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The RSVP function was disabled.

Procedure

  1. This log message is informational only. RSVP specifications are controlled using a license file.

RSVP/6/GET_MPLS_MTU_FAIL

Message

RSVP/6/GET_MPLS_MTU_FAIL:Cannot obtain MPLS MTU for interface index [InterfaceIndex].

Description

Failed to obtain the MPLS MTU.

Parameters

Parameter Name Parameter Meaning
[InterfaceIndex] Indicates the interface index.

Possible Causes

Failed to obtain the MPLS MTU during the creation of interface entries.

Procedure

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

RSVP/7/GLOBAL_OVER_FAIL

Message

RSVP/7/GLOBAL_OVER_FAIL: Failed to send global backup end event to HA.

Description

Failed to send a global backup end event to the HA module.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The system works abnormally.

Procedure

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

RSVP/6/GR_AGING_TIMER_END

Message

RSVP/6/GR_AGING_TIMER_END:The GR aging timer expired. (InterfaceName=[STRING], InterfaceAddress=[STRING], NeighborAddress=[STRING])

Description

The GR Aging timer expired.

Parameters

Parameter Name Parameter Meaning
InterfaceName Indicates the interface name.
InterfaceAddress Indicates the interface address.
NeighborAddress Indicates the neighbor address.

Possible Causes

When the local node helped the neighbor to perform GR, the GR Aging timer expired.

Procedure

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

RSVP/6/GR_AGING_TIMER_START

Message

RSVP/6/GR_AGING_TIMER_START:The GR aging timer of neighbor [NeighborAddress] was started.

Description

The GR Aging timer was started.

Parameters

Parameter Name Parameter Meaning
[NeighborAddress] Indicates the neighbor address.

Possible Causes

When the local node helped the neighbor to perform GR and GR ended, the GR Aging timer was started.

Procedure

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

RSVP/6/GR_RES_NBR_ENDTONOR

Message

RSVP/6/GR_RES_NBR_ENDTONOR:RSVP GR neighbour state changed from end to normal on the restarting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP restarting node changed from end to normal.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

After the local router finished GR, the status of the neighbor changed from end to normal.

Procedure

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

RSVP/6/GR_RES_NBR_NORTOEND

Message

RSVP/6/GR_RES_NBR_NORTOEND:RSVP GR neighbour state changed from normal to end on the restarting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP restarting node changed from normal to end.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

The neighbor no longer helped the local node to perform GR, and the status of the local node changed to end.

Procedure

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

RSVP/6/GR_RES_NBR_NORTOSUP

Message

RSVP/6/GR_RES_NBR_NORTOSUP:RSVP GR neighbour state changed from normal to supporting on the restarting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP restarting node changed from normal to supporting.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

When the local node performed GR and received the Support message from the neighbor, the local node changed the neighbor status from normal to supporting.

Procedure

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

RSVP/6/GR_RES_NBR_SUPTOEND

Message

RSVP/6/GR_RES_NBR_SUPTOEND:RSVP GR neighbour state changed from supporting to end on the restarting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP restarting node changed from supporting to end.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

After the local node finished GR, the status of the neighbor changed from supporting to end.

Procedure

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

RSVP/6/GR_RES_NBR_SUPTONOR

Message

RSVP/6/GR_RES_NBR_SUPTONOR:RSVP GR neighbour state changed from supporting to normal on the restarting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP restarting node changed from supporting to normal.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

When the neighbor helped the local node to perform GR and the local node finished GR, the local node changed the neighbor status from supporting to normal.

Procedure

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

RSVP/6/GR_RES_NORTORES

Message

RSVP/6/GR_RES_NORTORES:RSVP GR state changed from normal to restarting on the restarting node.

Description

The GR status on the RSVP restarting node changed from normal to restarting.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The active/standby switchover occurred.

Procedure

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

RSVP/6/GR_RES_RECTONOR

Message

RSVP/6/GR_RES_RECTONOR:RSVP GR state changed from recovering to normal on the restarting node.

Description

The GR status on the RSVP restarting node changed from recovering to normal.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

GR normally ended.

Procedure

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

RSVP/6/GR_RES_RESTONOR

Message

RSVP/6/GR_RES_RESTONOR:RSVP GR state changed from restarting to normal on the restarting node.

Description

The GR status on the RSVP restarting node changed from restarting to normal.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

When the local node was performing GR, no neighbor helped the local node to perform GR.

Procedure

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

RSVP/6/GR_RES_RESTOREC

Message

RSVP/6/GR_RES_RESTOREC:RSVP GR state changed from restarting to recovering on the restarting node.

Description

The GR status on the RSVP restarting node changed from restarting to recovering.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The Restart timer ended during GR.

Procedure

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

RSVP/6/GR_SUP_NBR_MRESTONOR

Message

RSVP/6/GR_SUP_NBR_MRESTONOR:RSVP GR neighbour state changed from maybe-restarting to normal on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from maybe-normal to normal.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

Before the timer expired, the local node did not receive the Hello message sent from the neighbor, and thus the local node judged that the neighbor was performing GR. After receiving the Hello message sent from the neighbor, the local node changed the neighbor status.

Procedure

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

RSVP/6/GR_SUP_NBR_MRESTORES

Message

RSVP/6/GR_SUP_NBR_MRESTORES:RSVP GR neighbour state changed from maybe-restarting to restarting on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from maybe-restarting to restarting.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

The local node received the GR message of the neighbor and judged that the neighbor was performing GR, and then the status of the supporting node changed.

Procedure

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

RSVP/6/GR_SUP_NBR_NORTOMRES

Message

RSVP/6/GR_SUP_NBR_NORTOMRES:RSVP GR neighbour state changed from normal to maybe-restarting on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from normal to maybe-restarting.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

When the local node supported GR and Hello detection with the neighbor expired, the local node judged that the neighbor might be performing GR and set the flag bit.

Procedure

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

RSVP/6/GR_SUP_NBR_NORTORES

Message

RSVP/6/GR_SUP_NBR_NORTORES:RSVP GR neighbour state changed from normal to restarting on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from normal to restarting.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

The local node received the Hello message from the neighbor and found the neighbor performing GR.

Procedure

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

RSVP/6/GR_SUP_NBR_RESTOMRES

Message

RSVP/6/GR_SUP_NBR_RESTOMRES:RSVP GR neighbour state changed from restarting to maybe-restarting on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from restarting to maybe-restarting.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

When the neighbor was performing GR, the Hello message between the local node and the neighbor expired again.

Procedure

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

RSVP/6/GR_SUP_NBR_RESTONOR

Message

RSVP/6/GR_SUP_NBR_RESTONOR:RSVP GR neighbour state changed from restarting to normal on the supporting node. (NeighbourAddress=[IPADDR])

Description

The GR status on the RSVP supporting node changed from restarting to normal.

Parameters

Parameter Name Parameter Meaning
NeighbourAddress Indicates the address of the restarting neighbor.

Possible Causes

The neighbor finished GR, and the local node changed from restarting to normal.

Procedure

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

RSVP/6/INC_INTF

Message

RSVP/6/INC_INTF:Cannot obtain interface from RSVP message. (IncomingInterfaceIndex=[ULONG], InterfaceName=[STRING])

Description

Failed to read interface information.

Parameters

Parameter Name Parameter Meaning
IncomingInterfaceIndex Indicates the incoming interface index.
InterfaceName Indicates the interface name.

Possible Causes

Failed to resolve the RSVP message.

Procedure

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

RSVP/6/INTF_SEQ_RCH_MAX

Message

RSVP/6/INTF_SEQ_RCH_MAX:Authentication send: Interface sequence number reached the greatest value.

Description

The sequence number of the interface reached the upper limit.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

When the authentication sequence number of the interface reached the upper limit, the sequence number was reset, and the sequence flag bit increased by 1.

Procedure

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

RSVP/3/LOOP_PATH

Message

RSVP/3/LOOP_PATH:A loop existed in path message (IngressLsrId=[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR]), the IP address [LoopAddress] conflicted with other router.

Description

A loop occurred in the Path message.

Parameters

Parameter Name Parameter Meaning
IngressLsrId Indicates the LSR ID of the ingress in the Path message.
TunnelId Indicates the tunnel ID.
EgressLsrId Indicates the LSR ID of the egress in the Path message.
[LoopAddress] Indicates the address that causes the loop.

Possible Causes

An incorrect configuration caused a loop. For example, a device on a TE tunnel is configured with an IP address that is the same as the IP address of an interface along the TE tunnel.

Procedure

  1. Run the display ip interface brief command on the involved device to check IP addresses of all interfaces and find the interfaces whose IP addresses are the same as that displayed in the LoopAddr field.
  2. Log in to the ingress based on the LSR ID displayed in the IngressLsrId field. Then run the display mpls te tunnel path command on the ingress to check nodes along the TE tunnel.
  3. Run the display ip interface brief command on each node to check the IP address and find the IP address the same as that displayed in the LoopAddr field.
  4. Change either of two identical IP addresses to be a different one.
  5. Collect log information and configuration information, and then contact technical support personnel.

RSVP/3/LOOP_RESV

Message

RSVP/3/LOOP_RESV:There is a loop in resv message (IngressLsrId=[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR]), the IP address [LoopAddress] conflicted with other router.

Description

A loop was found during the RSVP loop detection.

Parameters

Parameter Name Parameter Meaning
IngressLsrId Indicates the LSR ID of the ingress in the Resv message.
TunnelId Indicates the tunnel ID.
EgressLsrId Indicates the LSR ID of the egress in the Resv message.
[LoopAddress] Indicates the address that causes the loop.

Possible Causes

A loop was found during the RSVP loop detection because of incorrect configuration.

Procedure

  1. Run the display ip interface brief command on the involved device to check IP addresses of all interfaces and find the interfaces whose IP addresses are the same as that displayed in the LoopAddr field.
  2. Log in to the ingress based on the LSR ID displayed in the IngressLsrId field. Then run the display mpls te tunnel path command on the ingress to check nodes along the TE tunnel.
  3. Run the display ip interface brief command on each node to check the IP address and find the IP address the same as that displayed in the LoopAddr field.
  4. Change either of two identical IP addresses to be a different one.
  5. Collect log information and configuration information, and then contact technical support personnel.

RSVP/3/LSP_DOESNOT_EXIST

Message

RSVP/3/LSP_DOESNOT_EXIST:LSP did not exist. (EgressAddress=[STRING], SessionId=[USHORT], IngressAddress=[STRING], LspId=[USHORT])

Description

The LSP did not exist.

Parameters

Parameter Name Parameter Meaning
EgressAddress Indicates the egress address.
SessionId Indicates the session discriminator.
IngressAddress Indicates the ingress address.
LspId Indicates the LSP ID.

Possible Causes

During the active/standby switchover, the LSP was not backed up to the SMB after GR.

Procedure

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

RSVP/3/LSP_EXCEED_PAF_LIC

Message

RSVP/3/LSP_EXCEED_PAF_LIC:Number of LSPs to be recovered given by LSPM exceeded actual PAF licence number. (GivenNumber=[ULONG])

Description

The number of LSPs to be restored reached the maximum value specified in the License.

Parameters

Parameter Name Parameter Meaning

GivenNumber

The number of LSPs to be restored.

Possible Causes

The local node was configured with self-GR. During the active/standby switchover and GR, the number of LSPs in the License was modified to a value smaller than the number of current LSPs in the SMB.

Procedure

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

RSVP/3/LSRID_GET_FAIL

Message

RSVP/3/LSRID_GET_FAIL:Cannot obtain LSR ID from both RRO and CSPF. (IngressLsrId=[STRING], SessionId=[USHORT], IngressAddress=[STRING], LspId=[USHORT])

Description

Failed to obtain the LSR ID.

Parameters

Parameter Name Parameter Meaning
IngressLsrId Indicates the ingress LSR ID.
SessionId Indicates the session ID.
IngressAddress Indicates the ingress address.
LspId Indicates the LSP ID.

Possible Causes

Failed to obtain the LSR ID from RRO and CSPF during the processing of the Path message.

Procedure

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

RSVP/6/MAX_NBR_REACH

Message

RSVP/6/MAX_NBR_REACH:The number of the neighbours on the interface [interfacename] reached the maximum value [maximum]. (CurrentNumber=[ULONG])

Description

The number of neighbors on the interface reached the maximum.

Parameters

Parameter Name Parameter Meaning
[interfacename] Indicates the interface name.
[maximum] Indicates the maximum number of neighbors permitted on the interface.
CurrentNumber Indicates the number of current neighbors.

Possible Causes

The interface corresponded to too many neighbors.

Procedure

  1. Check the specification and increase the configured number of neighbors.

RSVP/6/MAX_SESSION_REACH

Message

RSVP/6/MAX_SESSION_REACH:Reached the maximum value of session [maximum].

Description

The number of sessions reached the maximum.

Parameters

Parameter Name Parameter Meaning
[maximum] Indicates the maximum number of sessions.

Possible Causes

The number of sessions reached the maximum during the creation of sessions.

Procedure

  1. Run the display mpls rsvp-te session ingress-lsr-id tunnel-id egress-lsr-id command to check for unwanted sessions. If some sessions are unwanted, delete them. If all sessions are needed, contact technical support personnel for expansion.

RSVP/3/NBR_NO_GR_PATH

Message

RSVP/3/NBR_NO_GR_PATH:Received a path message from neighbor [neighbor-address], but the neighbor was not enabled GR.

Description

A Recovery Path message received from the neighbor that was not enabled with GR.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

The local node could help the downstream neighboring node to perform GR. When the downstream neighboring node was performing GR, the GR supporting capability or Hello detection was disabled on the local node.

Procedure

  1. Check whether the neighbor needs to be enabled with the RSVP GR supporting capability.

RSVP/3/NBR_NO_GR_REC_PATH

Message

RSVP/3/NBR_NO_GR_REC_PATH:Received a recovery-path message from neighbor [neighbor-address], but the neighbor was not enabled GR.

Description

A neighbor without the GR capability received a Recovery Path message.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

The local node could help the upstream neighboring node to perform GR. When the upstream neighboring node was performing GR, the GR supporting capability or Hello detection was disabled on the local node.

Procedure

  1. Check whether the neighbor needs to be enabled with the RSVP GR supporting capability.

RSVP/6/NOTIFY_LSPM_GR_END

Message

RSVP/6/NOTIFY_LSPM_GR_END:RSVP GR ends.

Description

RSVP notified LSPM that RSVP GR ended.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

1. Before the active/standby switchover, the GR capability was not configured on the device.

2. No LSP existed on the device.

3. The neighboring node did not have the RSVP GR supporting capability.

4. GR was complete.

Procedure

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

RSVP/6/NOTIFY_LSPM_GR_START

Message

RSVP/6/NOTIFY_LSPM_GR_START:RSVP GR starts.

Description

RSVP notified LSPM that RSVP GR started.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

1. RSVP GR was configured, but the undo mpls rsvp-te command was run immediately, and then the LSP was not deleted.

2. Before the active/standby switchover, the router already had the RSVP GR capability.

Procedure

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

RSVP/6/PSB_CLEAN_TIMEOUT

Message

RSVP/6/PSB_CLEAN_TIMEOUT:The cleanup timer of PSB expired. (IngressLsrId=[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR], LspId=[USHORT], LastRecRefreshTime [ULONG]:[ULONG]:[ULONG](Hour:Minute:Second), CleanupTime=[ULONG](Second))

Description

The timer of PSB expired.

Parameters

Parameter Name Parameter Meaning
IngressLsrId Indicates the LSR ID of the ingress.
TunnelId Indicates the ID of a tunnel.
EgressLsrId Indicates the LSR ID of the egress in the Path message.
LspId Indicates the local LSP ID.
LastRecRefreshTime Indicates the last time when receiving a Resv Refresh message.
CleanupTime Indicates the timeout period of the PSB cleanup timer

Possible Causes

The PSB failed to be updated, causing the clean timer to expire. Between two directly-connected devices, if one directly-connected interface of a device fails, the device cannot send a Path Refresh message. As failing to receiving the Path Refresh message, the other device deletes the TE tunnel after the PSB cleanup timer expires.

Procedure

  1. Check whether there is an operation that shuts down the interface or interrupts services.
  2. Collect log information and configuration information, and then contact technical support personnel.

RSVP/3/REACH_LIC_LIMIT

Message

RSVP/3/REACH_LIC_LIMIT:The number of CR-LSPs reached the upper limit of Paf/License.

Description

The number of CR-LSPs reached the maximum value specified in the Paf/License.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The number of CR-LSPs created by the local device reached the maximum.

Procedure

  1. This log message is informational only. To create more CR-LSPs, modify the License.

RSVP/4/REACH_LIST_MAXLEGTH

Message

RSVP/4/REACH_LIST_MAXLEGTH:The length of the RSVP message list reached the maximum. (MaxLength=[ULONG])

Description

The length of the RSVP message list reached the maximum value.

Parameters

Parameter Name Parameter Meaning
MaxLength Indicates the maximum length of the RSVP message list.

Possible Causes

RSVP messages were not processed in time, and thus the length of the RSVP message list reached the maximum value.

Procedure

  1. Run the display memory-usage command to view the status of the memory usage.
  2. If it is necessary and possible, run the reset mpls rsvp-te command in the user view to clear the list. Note that this command may result in the reestablishment of all LSPs related to RSVP, so use it with caution.
  3. Contact technical personnel to locate which module occupies too much CPU, which slows down packet processing and causes the message list to be full.

RSVP/3/REACH_PSB_MAXNUM

Message

RSVP/3/REACH_PSB_MAXNUM:Reached the maximum of PSBs. (MaxNumber=[ULONG])

Description

During the creation of PSBs, the number of PSBs reached the maximum.

Parameters

Parameter Name Parameter Meaning
MaxNumber Indicates the maximum number of PW LSPs.

Possible Causes

The number of PSBs reached the maximum value specified in the License.

Procedure

  1. Check whether the number of TE tunnels reached the maximum value specified in the License.

RSVP/3/RECONSTRUCT_LSP_FAIL

Message

RSVP/3/RECONSTRUCT_LSP_FAIL:Cannot reconstruct RSVP states for LSP. (EgressAddress=[STRING], SessionId=[USHORT], IngressAddress=[STRING], LspId=[USHORT])

Description

Failed to restore the LSP.

Parameters

Parameter Name Parameter Meaning
EgressAddress Indicates the egress address.
SessionId Indicates the session ID.
IngressAddress Indicates the ingress address.
LspId Indicates the LSP ID.

Possible Causes

Failed to use the received GR message to reestablish PSB or RSB. Possible causes are as follows:

1. The system had insufficient memory.

2. Routing information on the SMB was lost.

3. The TTL value was smaller than 1.

4. The system detected a loop.

Procedure

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

RSVP/6/RECOVERY_TIMER_END

Message

RSVP/6/RECOVERY_TIMER_END:The recovery timer of neighbor [neighbor-address] expired.

Description

The Recovery timer expired.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

When the local node or the GR supporting node was performing GR, the Recovery timer expired.

Procedure

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

RSVP/6/RECOVERY_TIMER_START

Message

RSVP/6/RECOVERY_TIMER_START:The recovery timer of neighbor [neighbor-address] was started.

Description

The Recovery timer was started.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

When the local node or the GR supporting node was performing GR, the Recovery timer was started.

Procedure

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

RSVP/6/RESTART_TIMER_END

Message

RSVP/6/RESTART_TIMER_END:The restart timer of neighbor [neighbor-address] expired.

Description

The Restart timer expired.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

When the local node or the GR supporting node was performing GR, the Restart timer expired.

Procedure

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

RSVP/6/RESTART_TIMER_START

Message

RSVP/6/RESTART_TIMER_START:The restart timer of neighbor [neighbor-address] was started.

Description

The Restart timer was started.

Parameters

Parameter Name Parameter Meaning
[neighbor-address] Indicates the neighbor address.

Possible Causes

When the local node or the GR supporting node was performing GR, the Restart timer was started.

Procedure

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

RSVP/6/RSB_CLEAN_TIMEOUT

Message

RSVP/6/RSB_CLEAN_TIMEOUT:The cleanup timer of RSB expired. (IngressLsrId=[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR], LspId=[USHORT], LastRecRefreshTime [ULONG]:[ULONG]:[ULONG](Hour:Minute:Second), CleanupTime=[ULONG](Second))

Description

The RSB's cleanup timer expired.

Parameters

Parameter Name Parameter Meaning
IngressLsrId Indicates the LSR ID of the ingress in the Resv message.
TunnelId Indicates the ID of a tunnel.
EgressLsrId Indicates the LSR ID of the egress in the Resv message.
LspId Indicates the LSP ID.
LastRecRefreshTime Indicates the last time when receiving a Resv Refresh message.
CleanupTime Indicates the timeout period of the RSB cleanup timer

Possible Causes

The RSB failed to be updated, causing its cleanup timer to expire. For example, between two directly-connected devices, if one directly-connected interface of a device fails, the device cannot send a Resv Refresh message. As failing to receiving the Resv Refresh message, the other device deletes the TE tunnel after the RSB cleanup timer expires.

Procedure

  1. Check whether there is an operation that shuts down the interface or interrupts services.
  2. Collect log information and configuration information, and then contact technical support personnel.

RSVP/7/SD_HA_BACK_OVER_FAIL

Message

RSVP/7/SD_HA_BACK_OVER_FAIL:Failed to sent batch backup end event to HA.

Description

Failed to send the event that batch backup ended to the HA module.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

Failed to inform the slave board that batch backup ended.

Procedure

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

Document ID: EDOC1100065665

Views: 5617

Downloads: 15

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