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

Alarm Handling

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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).
EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34 hwDot1agCfmMismerge

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34 hwDot1agCfmMismerge

Description

EOAM1AG/1/MISMERGE: OID [oid] MEP received a CCM with unexpected MEG ID. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

An MD or MA name carried in a CCM sent by the RMEP was different from that specified on the MEP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.34 Critical communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

MdIndex

Index of an MD table

MaIndex

Index of an MA table

MdName

Name of an MD

MaName

Name of an MA

MepId

ID of a MEP

Impact on the System

CFM will fail.

Possible Causes

An MD or MA name carried in a CCM sent by the RMEP was different from that specified on the MEP when the MEP and RMEP had the same MD level and service type in a MEG.

Procedure

  1. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to view the value of the MD Name field on the MEP and RMEP that have the same service type and MD level. Check whether the MD names are the same.

    • If they are the same, go to Step 2.

    • If they are different, go to Step 3.

  2. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to view the value of the MA Name field on the MEP and RMEP that have the same service type, MD level, and MD name. Check whether the MA names are the same.

    • If they are the same, go to Step 5.

    • If they are different, go to Step 4.

  3. Perform the following steps on the MEP:
    1. Run the undo cfm md name md-name command to delete existing MD configurations.
    2. Run the cfm md md-name level level command to reconfigure an MD the same as that on the RMEP.
    3. Run the display alarm active command to check whether the alarm is cleared. If the alarm is cleared, go to Step 6. If the alarm is not cleared, go to Step 5.
  4. Perform the following steps on the MEP:
    1. Run the undo ma ma-name command to delete existing MA configurations.
    2. Run the ma ma-name command to reconfigure an MA the same as that on the RMEP.
    3. Run the display alarm active command to check whether the alarm is cleared. If the alarm is cleared, go to Step 6. If the alarm is not cleared, go to Step 5.
  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 150176

Downloads: 42

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