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_TUNNEL_LOCV alarm indicates loss of tunnel connectivity. This alarm is reported if the expected CV/FFD packet is not received in three consecutive periods. For example, this alarm is reported when the Ethernet port receives the continuity check packet with the correct TTSI within three consecutive periods, but the packet type and period are different from the expected values.


Alarm Severity Alarm Type


Communication alarm



Impact on the System

The services that the faulty tunnel carries may be interrupted.

Possible Causes

Possible causes of the MPLS_TUNNEL_LOCV alarm are as follows:

  • The MPLS OAM settings differ between both ends. For example, the type of packets to be checked or the check period differs between both ends.
  • The network is severely congested.
  • A board fails.
  • The physical link is faulty.


  1. On the U2000, check whether the MPLS OAM settings are the same at both ends.
  2. If they are different, modify them to be the same based on the actual situation. Then, check whether the alarm is cleared.
  3. If the alarm persists, go to 4.
  4. Based on the actual situation, increase the value of the Detection Packet Period parameter appropriately.
  5. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is exhausted. If yes, expand the bandwidth allocated to the tunnel or eliminate the source that transmits a large amount of invalid data. Check whether the alarm is cleared.
  6. If the alarm persists, go to 7.
  7. On the U2000, check whether the COMMUN_FAIL alarm is reported on the opposite NE. If yes, you can infer that the opposite NE is being reset. After the COMMUN_FAIL alarm is cleared, check whether the MPLS_TUNNEL_LOCV alarm is cleared.
  8. On the U2000, check whether the local NE and the opposite NE report alarms that are related to the hardware of optical modules or boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms and check whether the MPLS_TUNNEL_LOCV alarm is cleared.
  9. If the alarm persists, go to 10.
  10. Check whether an optical fiber or a cable between both ends is faulty. If yes, replace the faulty optical fiber or cable.

Related Information


Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75442

Downloads: 138

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