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

OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02

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

MPLS_TUNNEL_MISMATCH

Description

The MPLS_TUNNEL_MISMATCH alarm indicates trail termination source identifiers (TTSIs) mismatch. This alarm is reported if no CV/FFD packet with a correct TTSI is received in three consecutive CV/FFD periods.

Attribute

Alarm Severity Alarm Type

Major

Communication alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1

LSRID/MEGID: Indicates the source of the packet.

Impact on the System

Services may be interrupted or packets from other tunnels may be received.

Possible Causes

Possible causes of the MPLS_TUNNEL_MISMATCH alarm are as follows:

  • Cause 1: The physical link is incorrectly connected.
  • Cause 2: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at both ends of the tunnel.

Procedure

  1. Check whether an optical fiber or a cable is incorrectly connected between both ends. If yes, rectify the fiber/cable connection.
  2. Then, check whether the alarm is cleared. If the alarm persists, go to 3.
  3. On the U2000, check whether the LSR IDs or tunnel IDs are consistent at both ends of a tunnel.
    1. If the source NE is an ingress node, the value of Sink Node is the LSR ID of the sink node. If the sink NE is an egress node, the value of Source Node is the LSR ID of the source NE. For details about how to query the LSR ID of the source/sink NE, see the Configuration Guide.
    2. The tunnel IDs configured on the source NE and sink NE of one tunnel should be the same. For details about how to query tunnel IDs, see the Configuration Guide.
  4. If the tunnel IDs on both ends of a tunnel mismatch, change the tunnel IDs and ensure that the tunnel IDs on both ends of a tunnel match.

Related Information

None.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 76416

Downloads: 138

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