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

ETH_EFM_DF

Description

The ETH_EFM_DF alarm indicates that negotiation of the P2P OAM protocol fails at a port.

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

Indicates the cause of the failure.

  • 0x01: The connection at the local end fails.
  • 0x02: No OAM packet is received at the local end within a specified period.
  • 0x03: The OAM settings at the opposite end are inconsistent with those at the local end.
  • 0x04: The OAM settings at the local end are inconsistent with those at the opposite end.
  • 0x05 - 0xff: Reserved.

Impact on the System

Services may be interrupted.

Possible Causes

Possible causes of the ETH_EFM_DF alarm are as follows:

  • Hardware equipment on the local end, such as the optical module, boards, or physical link, is faulty.
  • No OAM packet is received at the local end within a specified period.
  • The OAM settings at one end do not meet the requirements at the other end.

Procedure

  1. On the U2000, check whether there are hardware-related alarms at the local end, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms. Then, check whether the ETH_EFM_DF alarm is cleared.
  2. If the alarm persists, check whether an optical fiber or a cable between the local NE and the opposite NE is damaged. If yes, replace the faulty optical fiber or cable. Check whether the alarm is cleared.
  3. If the alarm persists, go to the next step.
  4. On the U2000, check whether the OAM protocol is enabled on the opposite NE. If not, enable the OAM protocol. Check whether the alarm is cleared.
  5. If the alarm persists, check whether the OAM modes are passive at both ends. For two interconnected systems, the OAM mode of one system must be active. If yes, make the setting of the OAM mode active at one end or two ends based on the actual situations. Then, check whether the alarm is cleared.
  6. 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.

Related Information

None.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75577

Downloads: 138

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