Setting the Lowest Priority MEP Defect Alarm

You can set the lowest priority defect that will generate a fault alarm syslog message using the alarm-defect-syslog command in the MEP configuration mode.

You can set the lowest priority defect that will generate a fault alarm trap message using the alarm-defect-trap command in the MEP configuration mode.

The defects reported is based upon the specified level:

  • all-def – Specifies that the DefRDICCM, DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM defects will generate a fault alarm syslog message. See MEP Defect Definitions for defect descriptions.
  • mac-rem-err-xcom – Specifies that the DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM defects will generate a fault alarm syslog message (default).
  • rem-err-xcon – Specifies that the DefRemoteCCM, DefErrorCCM, and DefXconCCM defects will generate a fault alarm syslog message.
  • err-xcon – Specifies that the DefErrorCCM, and DefXconCCM defects will generate a fault alarm syslog message.
  • xcon – Specifies that the DefXconCCM defect will generate a fault alarm syslog message.
  • no-xcon – Specifies that no fault alarm Syslog messages will be generated.
Click to expand in new window

MEP Defect Definitions

Defect Description
DefRDICCM One or more continuity check messages received by this MEP contained the RDI bit. This bit indicates that some other MEP in this MEP‘s MA is transmitting the RDI bit. This defect clears if continuity check messages from all remote MEPs do not have the RDI bit set. Devices set the RDI bit if they have received continuity check messages from a remote MEP that indicates the remote MEP has seen defect notifications from other MEPs in the MA.
DefMACstatus The port status is not indicating “UP” for all remote MEPs on received continuity check messages, or the interface status for any remote MEP on received continuity check messages is not indicating “UP”.
DefRemoteCCM This MEP is not receiving continuity check messages from a MEP in its configured list.
DefErrorCCM This MEP is receiving continuity check messages from a remote MEP that either uses an invalid MEP ID or uses a continuity check interval that does not match the receiving MEP.
DefXconCCM This MEP is receiving continuity check messages from a remote MEP that either uses an MD level lower than the receiving MEP or uses a different MD or MA name than the receiving MEP.

You can set the minimum time a defect must be present before an alarm is generated using the alarm-time command. You can set the minimum amount of time a defect must be absent before and alarm is reset using the reset-time command. Alarm time and reset time values are set in centiseconds between 250 (2.5 seconds) and 1000 (10 seconds). The default value is 2.5 seconds.

This example sets the Syslog defect alarm setting for the myMA1 MEP 1000 to generate a Syslog message if any supported defect is present for at least 3 seconds:

System(rw-config)->cfm md string-name myMD1
System(su-config-cfm-md.1)->ma string-name myMA1
System(su-config-cfm-ma.1)->mep 1000
System(su-config-cfm-mep.1000)->alarm-defect-syslog all-def
System(su-config-cfm-mep.1000)->alarm-time 300
System(su-config-cfm-mep.1000)->reset-time 300
System(su-config-cfm-mep.1000)->enable