Generating CCM Errors

This article describes the generation of CCM errors. Interface P2 of CUST3 is made down to raise a defect/fault in the sample topology.

CLI Configurations

At CUST3

• Make interface P2 down.
  your product(config)# interface gigabitethernet 0/2
  your product(config-if)# shutdown

• Wait for 5 seconds and verify any link failure (error/fault/defect)

At CUST1

• Display the logged CFM continuity check error conditions
  your product# show ethernet cfm errors

MEP-ID :  10
Level VLAN RMEP-ID   Current defect type
----- ---- -------   -------------------
5     2    30        ccm life time expired

At CUST2

• Display the logged CFM continuity check error conditions
  your product# show ethernet cfm errors
  Shows no error as MIP cannot detect any link failure (error/fault/defect).

At CUST3

• Display the logged CFM continuity check error conditions
  your product# show ethernet cfm errors

MEP-ID :  30
Level VLAN RMEP-ID   Current defect type
----- ---- -------   -------------------
5     2    10        ccm life time expired

SNMP Configurations

At CUST3

• Make interface P2 as down. [Index: Interface Number = 2]
  % snmp0 set {{ifMainAdminStatus.2 down }}

• Wait for 5 seconds and verify any link failure (error/fault/defect)

At CUST1

• Display the logged CFM continuity check error conditions. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
  % snmp0 get {fsMIEcfmExtMepDefects.0.1.1.10 }

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.0.1.1.10 {OCTET STRING} 20}

At CUST3

• Display the logged CFM continuity check error conditions. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 30]
  % snmp0 get {fsMIEcfmExtMepDefects.0.1.1.30 }

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.0.1.1.30 {OCTET STRING} 20}