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


To have a better experience, please upgrade your IE browser.


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



The MPLS_PW_UNEXPMEP is an alarm indicating that the PW does not receive the expected PEP ID. The sink NE reports this alarm upon receiving an OAM packet with an unexpected MEP ID.

  1. The source NE adds a PW outgoing label to the OAM packet that contains the CCM information and sends the packet to the sink NE. CCM information includes the MEG level, MEG ID, and MEP ID of the source 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 and MEG IDs are consistent but MEP IDs are inconsistent, the sink NE reports the MPLS_PW_UNEXPMEP alarm.


Alarm Severity Alarm Type


Communication alarm


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.

OptiX OSN 580 has no alarm parameters.

Impact on the System

When this alarm occurs, services are interrupted.

Possible Causes

The possible cause of the MPLS_PW_UNEXPMEP alarm is as follows:

Cause: MEP IDs are inconsistent on NEs at both ends of a PW.

As shown in Figure 4-17, NE2 is the sink end for NE1 and the MEP ID is 1 for both NEs in the network plan.

However, the MEP 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 CCM packet that contains incorrect MEP ID from NE1.

Figure 4-17  MPLS_PW_UNEXPMEP alarm detection


  1. As shown in Figure 4-17, check whether PW configurations are consistent on the source and sink NEs. MEP IDs must be set to the same value for NEs at both ends of a PW service.
  2. Check whether service-related alarms are reported by NEs at both ends of the PW. For example, MPLS_PW_LOCV. If any of these alarms are reported, clear them before you proceed.
  3. On the NMS, check whether tunnel-related alarms are reported by NEs at both ends of the PW. For example, MPLS_TUNNEL_OAMFAIL. If any of these alarms are reported, clear them before you proceed.
  4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support engineers for a solution.

Related Information


Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75835

Downloads: 138

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