EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.46 hwDot1agCfmRDI

Trap Buffer Description

MEP received a CCM with RDI flag set. (MdIndex=[MdIndex], MaIndex=[MaIndex], MdName=[MdName], MaName=[MaName], MepId=[MepId], RmepId=[RmepId])

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

Trap Attributes

Trap Attribute Description

Alarm or Event

Alarm

Trap Severity

Error

Mnemonic Code

RDI

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.46

MIB

HUAWEI-ETHOAM-MIB

Alarm ID

0x09ac000e

Alarm Name

RDI

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.47 hwDot1agCfmRDICleared

Trap Buffer Parameters

Parameter Description

MdName

Name of an MD

MaName

Name of an MA

MepId

ID of a MEP

RmepId

ID of an RMEP

MdIndex

Index of an MD table

MaIndex

Index of an MA table

VB Parameters

VB OID VB Name VB Index

1.3.6.1.4.1.2011.5.25.136.1.1.3.2.1.3

hwDot1agCfmMdName

hwDot1agCfmMdIndex

1.3.6.1.4.1.2011.5.25.136.1.1.4.2.1.2

hwDot1agCfmMaName

hwDot1agCfmMdIndex

hwDot1agCfmMaIndex

1.3.6.1.4.1.2011.5.25.136.1.1.5.1.1.1

hwDot1agCfmMepIdentifier

hwDot1agCfmMdIndex

hwDot1agCfmMaIndex

hwDot1agCfmMepIdentifier

1.3.6.1.4.1.2011.5.25.136.1.1.6.1.1.1

hwDot1agCfmRMepIdentifier

hwDot1agCfmMdIndex

hwDot1agCfmMaIndex

hwDot1agCfmRMepIdentifier

Impact on the System

System performance will not be affected.

Possible Causes

MEP received a CCM with RDI flag set.

Procedure

1. 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.

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.3.6.1.4.1.2011.5.25.136.1.6.42 hwDot1agCfmLOC to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.
  • If the value of the Alarm Status field is unexpectedMAC, follow the troubleshooting procedure described in EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40 hwDot1agCfmUnexpectedMAC to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.
  • If the value of the Alarm Status field is unexpectedPeriod, follow the troubleshooting procedure described in EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38 hwDot1agCfmUnexpectedPeriod to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.
  • If the value of the Alarm Status field is unexpectedMEP, follow the troubleshooting procedure described in EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36 hwDot1agCfmUnexpectedMEP to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.
  • If the value of the Alarm Status field is mismerge, follow the troubleshooting procedure described in EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.34 hwDot1agCfmMismerge to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.
  • If the value of the Alarm Status field is unexpectedMEGLevel, follow the troubleshooting procedure described in EOAM-1AG_1.3.6.1.4.1.2011.5.25.136.1.6.32 hwDot1agCfmUnexpectedMEGLevel to rectify the fault. Check whether the trap is cleared. If the trap persists, go to Step 3.

3. Perform the following steps on the RMEP:

  • a. Run the oam-mgr command to enter the MGR view.
  • b. 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.
  • c. 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 trap is cleared. If the trap persists, go to Step 4.

4. Collect alarm information and configuration information, and then contact technical support personnel.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >