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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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).
EOAM-1AG/3/RDI_active

EOAM-1AG/3/RDI_active

Message

EOAM-1AG/3/RDI_active:MEP received a CCM with RDI flag set. (MdIndex=[MdIndex], MaIndex=[MaIndex], MdName=[MdName], MaName=[MaName], MepId=[MepId], RmepId=[RmepId])

Description

The RMEP sent a CCM carrying the RDI flag with the value of 1 to the MEP.

Parameters

Parameter Name Parameter Meaning
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
RmepId ID of an RMEP

Possible Causes

Cause 1: If an RMEP received a non-RDI log, the RMEP set the RDI flag to 1 in a CCM and sent the CCM to the MEP.

Cause 2: If CFM association was enabled and an associated interface or protocol notified the RMEP of a detected fault, the RMEP set the RDI flag to 1 in a CCM and sent the CCM to the MEP.

Procedure

  • Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command on the RMEP to view the value of the Alarm Status field.

    • If the value of the Alarm Status field is none, go to Step 3.

    • If the value of the Alarm Status field is not none, go to Step 2.

  • Perform the following steps on the RMEP:

    • If the value of the Alarm Status field is LOC, follow the troubleshooting procedure described in EOAM-1AG/1/LOC_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

    • If the value of the Alarm Status field is unexpectedMAC, follow the troubleshooting procedure described in EOAM-1AG/3/UNEXPECTEDMAC_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

    • If the value of the Alarm Status field is unexpectedPeriod, follow the troubleshooting procedure described in EOAM-1AG/3/UNEXPECTEDPERIOD_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

    • If the value of the Alarm Status field is unexpectedMEP, follow the troubleshooting procedure described in EOAM-1AG/3/UNEXPECTEDMEP_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

    • If the value of the Alarm Status field is mismerge, follow the troubleshooting procedure described in EOAM-1AG/1/MISMERGE_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

    • If the value of the Alarm Status field is unexpectedMEGLevel, follow the troubleshooting procedure described in EOAM-1AG/1/UnexpectedMEGLevel_active to rectify the fault. Check whether the log is cleared. If the log persists, go to Step 3.

  • Perform the following steps on the RMEP:
    1. Run the oam-mgr command to enter the MGR view.
    2. Run the display this command. Check whether CFM is associated with an interface or a protocol. If there is no association configuration, go to Step 4.
    3. If CFM is associated with an interface or a protocol, check whether the associated interface or protocol fails. If the associated interface or protocol works properly, go to Step 4. If the associated interface or protocol fails, rectify the fault. Check whether the log is cleared. If the log persists, go to Step 4.
  • Collect configuration, trap messages, and log messages, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115773

Downloads: 85

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