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_UNEXPMEG

MPLS_TUNNEL_UNEXPMEG

Description

The MPLS_TUNNEL_UNEXPMEG is an alarm indicating an error of the tunnel OAM CCM information. The sink NE reports this alarm upon receiving an OAM packet with an unexpected MEG ID.

  1. The ingress NE adds a tunnel outgoing label to the OAM packet that contains the CCM information and sends the packet to the egress NE. CCM information includes the MEG level, MEG ID, and MEP ID of the ingress NE.
  2. The egress NE receives the OAM packet based on its incoming label and compares the CCM information in the packet with that configured on itself. If MEG levels are consistent but MEG IDs are inconsistent, the egress NE reports the MPLS_TUNNEL_UNEXPMEG alarm.

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

(OptiX OSN 500/550)LSRID/MEGID: Indicates the source of the packet.

NOTE:
OptiX OSN 580 has no alarm parameters.

Impact on the System

When this alarm occurs, the egress NE receives OAM packets (containing CCM information) of other tunnels.

Possible Causes

The possible causes of the MPLS_TUNNEL_UNEXPMEG alarm are as follows:

  • Cause 1: There are multiple tunnels with the same label between the source and sink NEs.

    An example is provided as follows: As shown in Figure 4-21, there are two links in the network plan that are connected to NE2: tunnel 1 between NE1 and NE2, and tunnel 2 between NE3 and NE2. The label of tunnel 1 is 1 and tunnel 2 is 2.

    However, in actual configuration, outgoing labels of both tunnel 1 and tunnel 2 are set to 1. NE2 receives an OAM packet (containing CCM information) that contains incorrect MEG ID from NE3. As a result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.

    Figure 4-21  MPLS_TUNNEL_UNEXPMEG alarm detection (1)

  • Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.

    An example is provided as follows: As shown in Figure 4-22, NE2 is the source end for NE1 and the MEG ID on both NEs is 1 in the network plan.

    However, the MEG ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore, NE2 reports the MPLS_PW_UNEXPMEP alarm upon receiving the OAM packet (containing CCM information) with an incorrect MEG ID from NE1.

    Figure 4-22  MPLS_TUNNEL_UNEXPMEG alarm detection (2)

  • Cause 3: Physical links are connected improperly. Multiple tunnels with the same label are connected to the same sink NE.

    As shown in Figure 4-23, a fiber between NE1 and NE2 is connected correctly. The tunnel between NE1 and NE2 has an outgoing label (label 1) and the MEG ID is 1. The tunnel between NE3 and NE4 has an outgoing label (label 1) and the MEG ID is 2.

    In practice, if NE1 is mistakenly connected to NE4, the outgoing label of a tunnel on NE1 is the same as that of the tunnel from NE3 to NE4, and the incoming label of a tunnel on NE2 is the same as the outgoing label of a tunnel from NE3 to NE4. As a result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.

    Figure 4-23  MPLS_TUNNEL_UNEXPMEG alarm detection (3)

Procedure

  1. Cause 1: There are multiple tunnels with the same label between the source and sink NEs.
    1. As shown in Figure 4-21, check whether there are multiple tunnels with the same label on the source and sink NEs. If yes, reconfigure labels for tunnels.
    2. Check whether the alarm is cleared. If the alarm persists, go to 2.
  2. Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.
    1. As shown in Figure 4-22, check whether tunnel configurations are consistent on the source and sink NEs. MEG IDs must be set to the same value on NEs at both ends of a tunnel service.
    2. Check whether the alarm is cleared. If the alarm persists, go to 3.
  3. Cause 3: Physical links are connected improperly. Multiple tunnels with the same label are connected to the same sink NE.
    1. As shown in Figure 4-23, check whether the fiber or cable correctly connects ports on both source and sink NEs. If the fiber or cable connection is incorrect, connect it correctly.
    2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support engineers for a solution.

Related Information

None.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 83208

Downloads: 154

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