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

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms 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).
EOAM1AG

EOAM1AG

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.32 hwDot1agCfmUnexpectedMEGLevel

Description

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

The MD level 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.32 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

The MD level carried in a CCM sent by the RMEP was different from that specified on the MEP.

Procedure

  1. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command on both the MEP and RMEP to view the value of the Level field. Check whether the MD levels are the same.

    • If the MD levels are different, go to Step 2.

    • If the MD levels are the same, go to Step 3.

  2. 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 view the trap. Check whether the trap is cleared. If the trap persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.33 hwDot1agCfmUnexpectedMEGLevelCleared

Description

EOAM1AG/1/UNEXPECTEDMEGLEVELCLEARED: OID [oid] MEP did not receive any CCM with unexpected MEG level before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The trap about inconsistency between the MD level carried in a CCM sent by the RMEP and that specified on the MEP was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.136.1.6.33

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

System performance will not be affected.

Possible Causes

The MEP received a CCM carrying the MD level the same as that specified on the MEP.

Procedure

  • This trap message is informational only, and no action is required.

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.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.35 hwDot1agCfmMismergeCleared

Description

EOAM1AG/1/MISMERGECLEARED: OID [oid] MEP did not receive any CCM with unexpected MEG ID before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The trap about inconsistency between the MD or MA name carried in a CCM sent by the RMEP and that specified on the MEP was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.35 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

System performance will not be affected.

Possible Causes

The MEP received a CCM carrying an MD or MA name the same as that specified on the MEP.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.36 hwDot1agCfmUnexpectedMEP

Description

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

The MEP ID carried in a CCM sent by the RMEP was not listed in the RMEP list of the MEP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.36 Minor 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

The MEP ID carried in a received CCM was not listed in the RMEP list of the MEP when the MEP and RMEP have the same MD level and MA ID.

Procedure

  1. Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command on the MEP to view the value of the RMEP ID field. Check whether the RMEP ID is displayed in the command output.

    • If the RMEP ID is displayed and the fault persists, go to Step 3.

    • If the RMEP ID is not displayed, go to Step 2.

  2. Perform the following steps on the MEP:
    1. Run the remote-mep mep-id mep-id [ mac mac-address ] command to specify a correct RMEP.
    2. Run the display alarm active command to view the trap. Check whether the trap is cleared. If the trap persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.37 hwDot1agCfmUnexpectedMEPCleared

Description

EOAM1AG/3/UNEXPECTEDMEPCLEARED: OID [oid] MEP did not receive any CCM with unexpected MEP before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER])

The trap about the event that a MEP ID in a CCM sent by the RMEP was not listed in the RMEP list of the MEP was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.37 Minor 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

System performance will not be affected.

Possible Causes

The MEP received a CCM carrying a MEP ID that was listed in the local RMEP list under the following conditions:
  • The MEP and RMEP had the same MD level.

  • The MEP and RMEP had the same MA ID.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.38 hwDot1agCfmUnexpectedPeriod

Description

EOAM1AG/3/UNEXPECTEDPERIOD: OID [oid] MEP received a CCM with unexpected period. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The CCM interval 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.38 Minor 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

RmepId

ID of an RMEP

Impact on the System

CFM will fail.

Possible Causes

The CCM interval carried in a CCM sent by the RMEP was different from that specified on the MEP in the scenario where the MEP and RMEP had the same MD level and MA ID, and the MEP was enabled to receive CCMs carrying the specified RMEP ID.

Procedure

  1. Run the display cfm ma [ md md-name [ ma ma-name ] ] command to view the value of the Interval field on the MEP and RMEP. Check whether the intervals configured on the MEP and RMEP are the same.

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

    • If they are different, go to Step 2.

  2. Perform the following steps on the MEP:
    1. Run the cfm md md-name command to enter the MD view.
    2. Run the display this command. Check whether the mep ccm-send enable command has been run to enable the MEP to send CCMs and the remote-mep ccm-receive enable command has been run to enable the MEP to receive CCMs.
    3. If the mep ccm-send enable command has been run, run the undo mep ccm-send enable command to disable the MEP from sending CCMs.
    4. If the remote-mep ccm-receive enable command has been run, run the undo remote-mep ccm-receive enable command to disable the MEP from receiving CCMs.
    5. Run the ccm-interval interval command to configure the interval between CCMs the same as the interval configured on the RMEP. Then run the remote-mep ccm-receive enable command to enable the MEP to receive CCMs and the mep ccm-send enable command to enable the MEP to send CCMs.
    6. Run the mep ccm-send enable command to enable the MEP to send CCMs.
    7. Run the remote-mep ccm-receive enable command to enable the MEP to receive CCMs.
    8. Run the display alarm active command to view the trap. Check whether the trap is cleared. If the trap persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.39 hwDot1agCfmUnexpectedPeriodCleared

Description

EOAM1AG/3/UNEXPECTEDPERIODCLEARED: OID [oid] MEP did not receive any CCM with unexpected period before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The trap about inconsistency between the CCM interval specified on the MEP and that carried in a CCM sent by the RMEP was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.39 Minor 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

The MEP received a CCM sent by the RMEP within a specified period of time and the interval carried in the CCM and that specified on the MEP were the same under the following conditions:
  • The MEP and RMEP had the same MD level.

  • The MEP and RMEP had the same MA ID.

  • The MEP ID carried in the received CCMs was listed in the RMEP list on the MEP.

  • The MEP was enabled to receive CCMs.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.40 hwDot1agCfmUnexpectedMAC

Description

EOAM1AG/3/UNEXPECTEDMAC: OID [oid] MEP received a CCM with unexpected MAC address. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The source MAC address carried in a CCM sent by the RMEP was different from the RMEP's MAC address specified on the MEP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.40 Minor 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

RmepId

ID of an RMEP

Impact on the System

CFM will fail.

Possible Causes

The source MAC address carried in a CCM sent by the RMEP was different from the RMEP's MAC address specified on the MEP under the following conditions:
  • The MEP and RMEP had the same MD level.

  • The MEP and RMEP had the same MA ID.

  • The MEP ID carried in the received CCMs was listed in the RMEP list on the MEP.

  • The MEP was enabled to receive CCMs.

  • The MEP and RMEP had the same interval at which CCMs were sent.

Procedure

  1. Perform the following steps:

    1. Run the cfm md md-name command on the MEP to enter the MD view.

    2. Run the display this command on the MEP to view the RMEP's MAC address.

    3. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command on the RMEP to view the value of the MAC field.

    4. Check whether the value of the MAC field on the RMEP is the same as the RMEP's MAC address on the MEP.
      • If they are the same, go to Step 3.

      • If they are different, go to Step 2.

  2. Perform the following steps on the MEP:
    1. Run the undo remote-mep mep-id mep-id command to delete the existing RMEP configuration.
    2. Run the remote-mep mep-id mep-id mac mac-address command to specify the correct MAC address of the RMEP.
    3. Run the display alarm active command to view the trap. Check whether the trap is cleared. If the trap persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.41 hwDot1agCfmUnexpectedMACCleared

Description

EOAM1AG/3/UNEXPECTEDMACCLEARED: OID [oid] MEP did not receive any CCM with unexpected MAC address before timeout. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The trap about inconsistency between the source MAC address carried in a CCM sent by the RMEP and the RMEP's MAC address specified on the MEP was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.41 Minor 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

The MEP received a CCM carrying the source MAC address the same as the RMEP's MAC address specified on the MEP under the following conditions:
  • The MEP and RMEP had the same MD level.

  • The MEP and RMEP had the same MA ID.

  • The MEP ID carried in the received CCMs was listed in the RMEP list on the MEP.

  • The MEP was enabled to receive CCMs.

  • The MEP and RMEP had the same interval at which CCMs were sent.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.42 hwDot1agCfmLOC

Description

EOAM1AG/1/LOC: OID [oid] MEP is disconnected with the remote MEP. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The MEP received no CCM in a period of time 3.5 times the interval at which CCMs were sent.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.42 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

RmepId

ID of an RMEP

Impact on the System

If this alarm is displayed, the link CC check fails, CCM configuration is incorrect, or a physical link fails.

Possible Causes

The MEP received no CCM in a period of time 3.5 times the interval at which CCMs were sent.

Procedure

  1. Perform the following operations to check the network operating status on the MEP:

    1. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to view the value of the Interface Name field. Obtain the interface type and number.

    2. Run the display interface interface-type interface-num command with the obtained interface type and number specified. View the value of the current state field.

      • If the value of the current state field is Up, go to Step 2.

      • If the value of the current state field is not Up, the interface connection fails. For the troubleshooting procedure, see "Physical Interconnection Troubleshooting."

  2. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command to view the value of the CCM Send field on the RMEP. Check whether the RMEP is enabled to send CCMs.

    • If the value of the CCM Send field is enabled, go to Step 4.

    • If the value of the CCM Send field is disabled, go to Step 3.

  3. Perform the following steps on the RMEP:
    1. Run the cfm md md-name command to enter the MD view.
    2. Run the ma ma-name command to enter the MA view.
    3. Run the mep ccm-send enable command to enable the RMEP to send CCMs. Check whether the trap is cleared. If the trap persists, go to Step 4.
  4. Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id ] command to view the value of the CCM Receive field on the MEP.

    • If the value of the CCM Receive field is enabled, go to Step 6.

    • If the value of the CCM Receive field is disabled, go to Step 5.

  5. Perform the following steps on the MEP:
    1. Run the cfm md md-name command to enter the MD view.
    2. Run the ma ma-name command to enter the MA view.
    3. Run the remote-mep ccm-receive enable command to enable the MEP to receive CCMs. Check whether the trap is cleared. If the trap persists, go to Step 6.
  6. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.43 hwDot1agCfmLOCCleared

Description

EOAM1AG/1/LOCCLEARED: OID [oid] MEP is reconnected with the remote MEP. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

The MEP received a CCM within a period of time 3.5 times the interval at which CCMs were sent.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.43 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

The MEP received a CCM within a period of time 3.5 times the interval at which CCMs were sent, and CFM was successful.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.44 hwDot1agCfmExceptionalMACStatus

Description

EOAM1AG/2/EXCEPTIONALMACSTATUS: OID [oid] MEP received a CCM with the Port Status TLV or Interface Status TLV reporting an error status. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

TLV information carried in a CCM sent by the RMEP within a specified interval showed that the interface connecting the RMEP to the MEP became abnormal.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.44 Major 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

TLV information carried in a CCM sent by the RMEP within a specified interval showed that the interface connecting the RMEP to the MEP became abnormal.

Procedure

  1. Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command on the RMEP to view the values of the Interface Name and Direction fields. Obtain the interface type and number and check the value of the Direction field.

    • If the value of the Direction field is inward, go to Step 2.

    • If the value of the Direction field is outward, go to Step 4.

  2. Perform the following steps on the RMEP:

    • Run the interface interface-type interface-number command with the obtained interface type and number specified to enter the interface view.

    • Run the display this interface command to view the value of the current state field.
      • If the value of the current state field is Up, go to Step 5.

      • If the value of the current state field is not Up, go to Step 3.

  3. Run the display interface interface-type interface-number command to view the value of the current state field on the RMEP.

    • If the value of the current state field is Administratively DOWN, go to Step 4.

    • If the value of the current state field is not Administratively DOWN, go to Step 6.

  4. Perform the following steps on the RMEP:

    • Run the interface interface-type interface-number command to enter the interface view.

    • Run the undo shutdown command to restart the interface. Check whether the trap is cleared. If the trap persists, go to Step 5.

  5. Run the display stp brief command to view the value of the STP State field. The STP State field is related to the Interface Name field that shows the same interface type and number as those obtained in step 1.

    • If the value of the STP State field is DISCARDING, check whether the port is blocked due to incorrect MSTP configuration. If the MSTP configuration is incorrect, adjust the MSTP configuration.
    • If the value of the STP State field is FORWARDING, go to Step 6.

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

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.45 hwDot1agCfmExceptionalMACStatusCleared

Description

EOAM1AG/2/EXCEPTIONALMACSTATUSCLEARED: OID [oid] MEP received a CCM with the Port Status TLV or Interface Status TLV reporting an error status cleared. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

TLV information carried in a CCM sent by the RMEP within a specified interval showed that the interface connecting the RMEP to the MEP was restored.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.45 Major 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

TLV information carried in a CCM sent by the RMEP showed that the interface connecting the RMEP to the MEP was restored.

Procedure

  • This trap message is informational only, and no action is required.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.46 hwDot1agCfmRDI

Description

EOAM1AG/3/RDI: OID [oid] MEP received a CCM with RDI flag set. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.46 Minor 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

Cause 1: If an RMEP received a non-RDI trap, 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

  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:

  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 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 trap is cleared. If the trap persists, go to Step 4.
  4. Collect alarm information and configuration information, and then contact technical support personnel.

EOAM1AG_1.3.6.1.4.1.2011.5.25.136.1.6.47 hwDot1agCfmRDICleared

Description

EOAM1AG/3/RDICLEARED: OID [oid] MEP received a CCM with RDI flag cleared. (MdIndex=[GAUGE], MaIndex=[GAUGE], MdName=[STRING], MaName=[STRING], MepId=[INTEGER], RmepId=[INTEGER])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.47 Minor 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

RmepId

ID of an RMEP

Impact on the System

System performance will not be affected.

Possible Causes

The MEP received a CCM carrying the RDI flag with the value of 0.

Procedure

  • This trap message is informational only, and no action is required.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 4405

Downloads: 6

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