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_PW_UNEXPMEG

MPLS_PW_UNEXPMEG

Description

The MPLS_PW_UNEXPMEG is an alarm indicating an error in the CCM information of the PW OAM packet. The sink NE reports the MPLS_PW_UNEXPMEG alarm upon receiving the OAM CCM packet with an unexpected MEG ID.

  1. The source NE adds a PW outgoing label to the OAM packet containing CCM information (including MEG level, MEG ID, and MEP ID) and transmits them to the sink NE.
  2. The sink 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 sink NE reports the MPLS_PW_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 sink NE receives OAM CCM packets of other PW services.

Possible Causes

The possible causes of the MPLS_PW_UNEXPMEG alarm are as follows:

  • Cause 1: The PW is configured incorrectly. Different PWs use the same labels.

    As shown in Figure 4-14, NE1 is the source NE, and NE2 is the sink NE. The PW incoming label for NE2 is 1, indicating that it is supposed to receive packets from PW1 only.

    On the live network, NE1 configures a PW outgoing label whose value is 1 to both PW1 and PW2. Therefore, after receiving CCM packets from PW2, NE2 detects different MEG IDs and reports the MPLS_PW_UNEXPMEG alarm.

    Figure 4-14  MPLS_PW_UNEXPMEG alarm detection (1)

  • Cause 2: MEG IDs configured on NEs at both ends of the PW are different.

    As shown in Figure 4-15, on the link from NE1 to NE2, the MEG ID is 1.

    In practice, the MEG ID for NE1 is 1 and MEG ID for NE2 is 2. Then, NE2 receives CCM packets containing different MEG ID and reports the MPLS_PW_UNEXPMEG alarm.

    Figure 4-15  MPLS_PW_UNEXPMEG alarm detection (2)

  • Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label are connected to the same sink NE.

    As shown in Figure 4-16, a fiber between NE1 and NE2 is correctly connected. On the link from NE1 to NE2, the PW outgoing label is 1, and the MEG ID is 1. On the link from NE3 to NE4, the PW outgoing label is 1, and the MEG ID is 2.

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

    Figure 4-16  MPLS_PW_UNEXPMEG alarm detection (3)

Procedure

  1. Cause 1: The PW is configured incorrectly. Different PWs use the same labels.
    1. As shown in Figure 4-14, check whether the PW label is configured correctly. If multiple PWs use the same labels, reconfigure the PW label.
    2. Check whether the alarm is cleared. If the alarm persists, go to 2.
  2. Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
    1. As shown in Figure 4-15, check whether the PW configurations on NEs at both ends of the PW are consistent. PW IDs on NEs at both ends of a PW must be set to the same value.
    2. Check whether the alarm is cleared. If the alarm persists, go to 3.
  3. Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label are connected to the same sink NE.
    1. As shown in Figure 4-16, check whether the fiber or cable is correctly connected between ports at both ends. If the fiber or cable is connected incorrectly, connect it correctly.
    2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers for a solution.

Related Information

None.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75080

Downloads: 138

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