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

ODUk_PM_TIM

Description

The ODUk_PM_TIM alarm indicates ODUk PM trace identifier mismatch. This alarm is reported if the trace identifier mismatch (TIM) detection function is enabled and the trace identifier at the local end and that at the peer end do not match during control processing.

k indicates the level of rate, its value is 0, 1, 2, 3, or flex.

Attribute

Alarm Severity Alarm Type

Minor

Communication alarm

Parameters

None

Impact on the System

Quality of the services carried by the optical port deteriorates, and the services may be unavailable.

Possible Causes

  • Cause 1: The configured TIM detection mode is not applicable to the networking topology.
  • Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI received at the local end.
  • Cause 3: Fiber connections are incorrect.
  • Cause 4: Cross-connections are incorrectly configured.

Procedure

  1. Cause 1: The configured TIM detection mode is not applicable to the networking topology.
    1. On the NMS, query the TIM detection mode of the local NE. If the TIM detection mode is not applicable to the networking topology, rectify the configurations.

      • For the point-to-point topology, only the SAPI (Source Access Point Identifier) is compared for the sink of trail termination.
      • For the point-to-multipoint topology, only the SAPI is compared for the sink of trail termination.
      • For the multipoint-to-multipoint topology, only the DAPI (Destination Access Point Identifier) is compared for the sink of trail termination.

    2. Check whether the alarm is cleared. If the alarm persists, go to 2.
  2. Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI received at the local end.
    1. On the NMS, query whether the TTI sent by the peer end and that received at the local end are the same. If the two TTIs are different, query the TTI received by the local NE on the NMS. Re-configure the SAPI and the DAPI of the TTI for the local NE to ensure that the two TTIs are the same.
    2. Check whether the alarm is cleared. If the alarm persists, go to 3.
  3. Cause 3: Fiber connections are incorrect.
    1. Check whether the fiber connections between the local optical port and peer optical port are correct. If the fiber connections are incorrect, connect the fibers correctly.
    2. Check whether the alarm is cleared. If the alarm persists, go to 4.
  4. Cause 4: Cross-connections are incorrectly configured.
    1. Check whether the cross-connections are correctly configured. If the configurations are incorrect, rectify the configurations.
    2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle the alarm.

Related Information

None

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75621

Downloads: 138

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