EVPN Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

EVPN Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

CFM on EVPN

Updated: June 10, 2026

Want to summarize with AI?

Introduces CFM functionality on EVPN, detailing feature highlights, supported offload types and timer values, deployment restrictions, and supported services, including configuration and operation for E-LAN and E-Line single-homing topologies.

An Ethernet Connectivity Fault Management (CFM) is an Ethernet layer operation, administration, and management (OAM) protocol that

operates end-to-end per service instance
provides proactive connectivity monitoring and fault verification, and
enables fault isolation in large networks.

Table 1. Feature History Table
Feature Name	Release Information	Feature Description
Extended Hardware offload of Connectivity Check Messages (CCM) timers	Release 26.2.1	Introduced in this release on: Modular Systems (8800 [LC ASIC: K100])(select variants only); This feature is supported on Cisco 88-LC1-48Y8H-EM line cards.
CFM on EVPN	Release 26.2.1	Introduced in this release on: Modular Systems (8800 [LC ASIC: K100])(select variants only); This feature is supported on Cisco 88-LC1-48Y8H-EM line cards.
CFM on EVPN	Release 25.4.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only) This feature is now supported on: 8011-32Y8L2H2FH 8011-12G12X4Y-A 8011-12G12X4Y-D
CFM on EVPN	Release 25.1.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100]) (select variants only) This feature is now supported on the Cisco 8011-4G24Y4H-I routers.
CFM on EVPN	Release 24.4.1	Introduced in this release on: Fixed Systems (8700 [ASIC: K100]) (select variants only) The CFM on EVPN functionality is now extended to the Cisco 8712-MOD-M routers.
CFM on EVPN	Release 24.3.1	Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100])(select variants only); Modular Systems (8800 [LC ASIC: P100])(select variants only) * The CFM on EVPN functionality is now extended to: 8212-48FH-M 8711-32FH-M 88-LC1-52Y8H-EM 88-LC1-12TH24FH-E
CFM on EVPN	Release 24.2.11	Introduced in this release on: Modular Systems (8800 [LC ASIC: Q200, P100]) (select variants only) You can now proactively monitor connectivity and verify faults and isolate them for EVPN services. This is because Ethernet Connectivity Fault Management (CFM) is now available for EVPN and provides end-to-end service level OAM (Operations, Administration, and Maintenance) for EVPN services. This feature is supported only on routers with Q200 and 88-LC1-36EH line cards.

CFM on EVPN feature highlights and benefits

CFM on EVPN provides essential capabilities to monitor and maintain the health and connectivity of EVPN services. The key highlights and benefits include:

Fault detection and isolation—enables rapid detection of connectivity faults within EVPN domains, helping to isolate and pinpoint issues quickly to minimize service disruption.
Proactive monitoring—supports continuous monitoring of EVPN service health through periodic continuity checks, ensuring early identification of potential problems.
Service assurance—verifies the operational status of EVPN instances, CFM helps maintain high service availability and reliability.
Standardized protocols—uses IEEE 802.1ag and ITU-T Y.1731 standards, ensuring interoperability across multi-vendor environments.
Scalability—designed to scale with large EVPN deployments, supporting multiple maintenance domains and endpoints.
Simplified troubleshooting—provides detailed fault management tools such as loopback and linktrace messages, which assist network operators in diagnosing and resolving issues efficiently.
Integration with EVPN— is tightly integrated with EVPN control plane mechanisms, enabling seamless operation and management within EVPN architectures.

Supported offload types and timer values

Continuity Check Messages (CCMs) are heartbeat messages exchanged periodically among all Maintenance End Points (MEPs) within a service. Each MEP sends multicast CCMs and receives CCMs from all other MEPs, enabling peer discovery and connectivity verification. The offload type is determined by where CCMs are processed.

Currently, only the Non-offload type is supported, where CCMs are generated and processed by the CPU. For a CFM session on a bundle interface or similar, CCM timers must be set to one second or greater.

CCM timers define the intervals at which CCMs are sent and received. If CCMs are not received within the configured interval, the CFM MEP is considered down. The supported CCM timer values for the Non-offload type are:

This table details the supported CCM times values for non-offload and hardware offload types:


Offload type	CCM timer value
Non-offload	1 second
	10 seconds
	1 minute
	10 minutes
1 second, applicable to these routers: Cisco 8011-4G24Y4H-I Cisco 8011-32Y8L2H2FH

Restrictions for CFM on EVPN

To ensure accurate CFM operation on EVPN, observe these restrictions:

Loopback and linktrace results may show artifacts such as multiple or varying responses for the same instance.
Do not configure CFM on interfaces with untagged encapsulation for EVPN pseudowire, as this is unsupported by Cisco IOS XR software.

Supported services for CFM on EVPN

CFM on EVPN support these service types:

EVPN E-LAN—CFM plays a crucial role in EVPN E-LAN services by enabling service providers and enterprises to maintain high availability and ensure the reliability of their distributed Ethernet services.
EVPN E-Line—CFM facilitates monitoring and maintaining the health of point-to-point Ethernet services over packet-switched networks, which is essential for service providers managing EVPN E-Line services.

Note

CFM on EVPN is supported only on single-homed devices.

CFM on EVPN E-LAN single-homing

CFM on EVPN E-LAN single-homing is a network monitoring feature that

operates on networks running E-LAN services with single-homed devices
monitors the health and performance of E-LAN services, and
provides high-speed Layer 2 services with enhanced resiliency.

How CFM on EVPN E-LAN single-homing works

Summary

The key components involved in the CFM on EVPN E-LAN single-homing process are:

Single-homed device: Connects to the EVPN E-LAN service and participates in connectivity monitoring.
CFM: Monitors and verifies connectivity within the EVPN E-LAN domain.
EVPN E-LAN domain: The network environment where devices communicate and connectivity is managed.

The CFM on EVPN E-LAN single-homing process enables continuous connectivity monitoring by the single-homed device within the EVPN E-LAN domain, and detects faults through continuity checks and alerts administrators to ensure network stability and simplify troubleshooting.

Workflow

These stages describe how CFM on EVPN E-LAN single-homing works.

The single-homed device connects to the EVPN E-LAN service.
CFM is enabled on the device to monitor connectivity within the EVPN E-LAN domain.
CFM initiates continuity checks between the single-homed device and other devices in the EVPN E-LAN.
CFM detects any connectivity faults and generates alarms or notifications.
Network administrators use CFM results to troubleshoot and resolve connectivity issues.

Result

This process ensures continuous monitoring and fault detection in single-homed EVPN E-LAN environments, improving network stability and simplifying troubleshooting.

Configure CFM on EVPN E-LAN full mesh topology

Enable and verify CFM on EVPN E-LAN full mesh topology to monitor network continuity and detect faults.

Use this task to configure CFM continuity checks, MEP cross-checks, and interface settings on Cisco routers participating in an EVPN E-LAN full mesh topology.

Procedure

	1.	Enable Ethernet CFM and configure the domain and service. Example: `Router# ethernet cfm Router(config-cfm# domain bd-domain level 1 id null Router(config-cfm-dmn)# service bd-domain bridge group bg-elan bridge-domain bd-elan id icc-based MC MCMC Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	2.	Configure MEP cross-checks. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-dmn-svc)# mep-id 1112 Router(config-cfm-dmn-svc)# mep-id 1113 Router(config-cfm-dmn-svc)# commit`
	3.	Repeat steps 1 and 2 on nodes 2 and 3, adjusting MEP IDs accordingly. For node 2, configure MEP cross-check with respective mep-id values of node 1 and node 3 (1111 and 1113 respectively, in this example). For node 3, configure MEP cross-check with respective mep-id values of node 1 and node 2 (1111 and 1112 respectively, in this example).
	4.	Enable CFM on the interface. Example: `Router(config)# interface TenGigE 0/0/0/2.100 l2transport Router(config-subif)# description bg-elan Router(config-subif)# encapsulation dot1q 100 Router(config-subif)# rewrite ingress tag pop 1 symmetric Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain bd-domain service bd-service mep-id 1111 Router(config-if-cfm-mep)# commit`
	5.	Repeat step 4 on nodes 2 and 3 with their respective MEP IDs. You must repeat the above configurations for node 2 and node 3, with the respective mep-id values (that is, 1112 for node 2 and 1113 for node 3, in this example).
	6.	Running configuration of CFM on EVPN E-LAN full mesh topology. Example: `ethernet cfm domain bd-domain level 1 id null service bd-domain bridge group bg-elan bridge-domain bd-elan id icc-based MC MCMC continuity-check interval 10s mep crosscheck mep-id 1112 mep-id 1113 ! ! ! ! interface TenGigE 0/0/0/2.100 l2transport description bg-elan encapsulation dot1q 100 rewrite ingress tag pop 1 symmetric ethernet cfm mep domain bd-domain service bd-service mep-id 1111 !`

CFM is enabled on all nodes in the EVPN E-LAN full mesh topology, providing continuous connectivity monitoring and fault detection.

Configure CFM on EVPN E-LAN hub and spoke topology

Configure CFM on an EVPN E-LAN hub and spoke topology with SLA profiles to monitor connectivity between the hub and spoke nodes.

This task extends the full mesh CFM configuration by adding SLA operation profiles on the hub node to ensure continuous network service monitoring.

Before you begin

Complete the full mesh CFM configuration steps on all nodes.

Procedure

Enable Ethernet CFM with the MEP domain, service, and MEP ID, and configure SLA profiles for spoke nodes’ MEP IDs.

The CFM configuration for the hub and spoke topology remains the same as that of full mesh topology mentioned above, except for these additional steps for SLA profile configuration to be done under the interface. You must configure the SLA profile between the hub and the spokes to ensure continuous network services.

In this example, 1112 and 1113 are the mep-id values of node 2 and node 3.

Example:

Router(config)#interface TenGigE 0/0/0/2.100 l2transport
Router(config-subif)# ethernet cfm
Router(config-if-cfm)# mep domain bd-domain service bd-service mep-id 1111
Router(config-if-cfm-mep)# sla operation profile test-profile1 target mep-id 1112
Router(config-if-cfm-mep)# sla operation profile test-profile2 target mep-id 1112
Router(config-if-cfm-mep)# sla operation profile test-profile1 target mep-id 1113
Router(config-if-cfm-mep)# sla operation profile test-profile2 target mep-id 1113
Router(config-if-cfm-mep)# commit

Running configuration of CFM on EVPN E-LAN hub and spoke topology.

Example:


interface TenGigE 0/0/0/2.100 l2transport
 description bg-elan
 encapsulation dot1q 100
 rewrite ingress tag pop 1 symmetric
 ethernet cfm
  mep domain bd-domain service bd-service mep-id 1111
   sla operation profile test-profile1 target mep-id 1112
   sla operation profile test-profile2 target mep-id 1112
   sla operation profile test-profile1 target mep-id 1113
   sla operation profile test-profile2 target mep-id 1113
 !

SLA profiles are configured on the hub node, enabling continuous service-level monitoring between the hub and spoke nodes.

Configure CFM for different domain types and bridge domains

Configure Ethernet CFM continuity checks and MEP cross-checks for various domain levels, multiple MEPs, and multiple services across different EVPN bridge domains.

Use these examples to configure CFM in complex EVPN environments with multiple bridge domains, domain levels, and services.

Before you begin

Ensure you have the necessary domain, service, bridge group, and bridge domain information.

Procedure

Follow these steps for each of these scenarios.

Scenario 1: Up MEPs with the same domain and level

Procedure

	1.	Enable Ethernet CFM continuity check. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain BD-DOMAIN level 4 id null Router(config-cfm-dmn)# service BD-SERVICE bridge group ELAN_FUNC_3 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	2.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 5 Router(config-cfm-xcheck)# mep-id 1101 Router(config-cfm-xcheck)# mep-id 1103`
	3.	Configure the bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group ELAN_FUNC_3 Router(config-l2vpn-bg)# bridge-domain FUNC_3 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/0.1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/1.2 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 101`
	4.	Enable CFM on interfaces with respective MEP IDs. Example: `Router(config)# interface TenGigE0/0/0/0.1 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain BD-DOMAIN service BD-SERVICE mep-id 1103 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/1.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain BD-DOMAIN service BD-SERVICE mep-id 5`
	5.	Running configuration of scenario 1. Example: ethernet cfm domain BD-DOMAIN level 4 id null service BD-SERVICE bridge group ELAN_FUNC_3 bridge-domain FUNC_3 id number 100 continuity-check interval 10s mep crosscheck mep-id 5 mep-id 1101 mep-id 1103 l2vpn bridge group ELAN_FUNC_3 bridge-domain FUNC_3 interface TenGigE0/0/0/0.1 ! interface TenGigE0/0/0/1.2 ! evi 101 interface TenGigE0/0/0/0.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain BD-DOMAIN service BD-SERVICE mep-id 1103 interface TenGigE0/0/0/1.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain BD-DOMAIN service BD-SERVICE mep-id 5

Scenario 2: Multiple Up MEPs on AC interfaces in the same bridge domain

Procedure

	1.	Enable Ethernet CFM continuity check. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain BD-DOMAIN level 4 id null Router(config-cfm-dmn)# service BD-SERVICE bridge group ELAN_FUNC_3 bridge-domain FUNC_3 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	2.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 1 Router(config-cfm-xcheck)# mep-id 2 Router(config-cfm-xcheck)# mep-id 21 Router(config-cfm-xcheck)# mep-id 22`
	3.	Enable Ethernet CFM continuity check for another domain level. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain BD-DOMAIN1 level 3 id null Router(config-cfm-dmn)# service BD-SERVICE1 bridge group ELAN_FUNC_3 bridge-domain FUNC_3 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	4.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 1001 Router(config-cfm-xcheck)# mep-id 1021 Router(config-cfm-xcheck)# mep-id 2001 Router(config-cfm-xcheck)# mep-id 2021`
	5.	Configure the bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group ELAN_FUNC_3 Router(config-l2vpn-bg)# bridge-domain FUNC_3 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/0 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 101`
	6.	Enable CFM on interfaces with multiple MEPs for both domains. Example: Router(config)# interface TenGigE0/0/0/0.1 l2transport Router(config-subif)# encapsulation dot1q 1 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain BD-DOMAIN service BD-SERVICE mep-id 21 Router(config-if-cfm-mep)# exit Router(config-if-cfm)# mep domain BD-DOMAIN1 service BD-SERVICE1 mep-id 1021 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/1.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain BD-DOMAIN service BD-SERVICE mep-id 22 Router(config-if-cfm-mep)# exit Router(config-if-cfm)#mep domain BD-DOMAIN1 service BD-SERVICE1 mep-id 2021
	7.	Running configuration of scenario 2. Example: ethernet cfm domain BD-DOMAIN level 4 id null service BD-SERVICE bridge group ELAN_FUNC_3 bridge-domain FUNC_3 id number 100 continuity-check interval 10s mep crosscheck mep-id 1 mep-id 2 mep-id 21 mep-id 22 domain BD-DOMAIN1 level 3 id null service BD-SERVICE1 bridge group ELAN_FUNC_3 bridge-domain FUNC_3 continuity-check interval 10s mep crosscheck mep-id 1001 mep-id 1021 mep-id 2001 mep-id 2021 l2vpn bridge group ELAN_FUNC_3 bridge-domain FUNC_3 interface TenGigE0/0/0/0 interface TenGigE0/0/0/1 Interface TenGigE0/0/0/2 evi 101 interface TenGigE0/0/0/0.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain BD-DOMAIN service BD-SERVICE mep-id 21 mep domain BD-DOMAIN1 service BD-SERVICE1 mep-id 1021 interface TenGigE0/0/0/1.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain BD-DOMAIN service BD-SERVICE mep-id 22 mep domain BD-DOMAIN1 service BD-SERVICE1 mep-id 2021

Scenario 3: Multiple services for different EVPN bridge domains

Procedure

	1.	Enable Ethernet CFM continuity check. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain evpn-bd level 4 id null Router(config-cfm-dmn)# service evpn-bd1 bridge group BG1 bridge-domain BD1 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	2.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 5 Router(config-cfm-xcheck)# mep-id 6 Router(config-cfm-xcheck)# mep-id 1101 Router(config-cfm-xcheck)# mep-id 1103`
	3.	Enable Ethernet CFM continuity check for another service. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain evpn-bd level 4 id null Router(config-cfm-dmn)# service evpn-bd2 bridge group BG2 bridge-domain BD2 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	4.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 11 Router(config-cfm-xcheck)# mep-id 21 Router(config-cfm-xcheck)# mep-id 101`
	5.	Configure the bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group BG1 Router(config-l2vpn-bg)# bridge-domain BD1 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/0.1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/1.2 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 101`
	6.	Configure another bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group BG2 Router(config-l2vpn-bg)# bridge-domain BD2 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/2.1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/5.2 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 201`
	7.	Enable CFM on interfaces with corresponding domain, service, and MEP IDs. Example: Router(config)# interface TenGigE0/0/0/0.1 l2transport Router(config-subif)# encapsulation dot1q 1 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd1 mep-id 1103 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/1.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd1 mep-id 5 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/2.1 l2transport Router(config-subif)# encapsulation dot1q 1 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd2 mep-id 101 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/5.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd2 mep-id 11
	8.	Running configuration of scenario 3. Example: ethernet cfm domain evpn-bd level 4 id null service evpn-bd1 bridge group BG1 bridge-domain BD1 continuity-check interval 10s mep crosscheck mep-id 5 mep-id 6 mep-id 1101 mep-id 1103 service evpn-bd2 bridge group BG2 bridge-domain BD2 continuity-check interval 10s mep crosscheck mep-id 11 mep-id 21 mep-id 101 l2vpn bridge group BG1 bridge-domain BD1 interface TenGigE0/0/0/0.1 interface TenGigE0/0/0/1.2 evi 101 bridge group BG2 bridge-domain BD2 interface TenGigE0/0/0/2.1 interface TenGigE0/0/0/5.2 evi 201 interface TenGigE0/0/0/0.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain evpn-bd service evpn-bd1 mep-id 1103 interface TenGigE0/0/0/1.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain evpn-bd service evpn-bd1 mep-id 5 interface TenGigE0/0/0/2.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain evpn-bd service evpn-bd2 mep-id 101 interface TenGigE0/0/0/5.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain evpn-bd service evpn-bd2 mep-id 11

Scenario 4: Different EVPN bridge domains on different domain levels

Procedure

	1.	Enable Ethernet CFM continuity check. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain evpn-bd level 4 id null Router(config-cfm-dmn)# service evpn-bd1 bridge group BG1 bridge-domain BD1 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	2.	Configure MEP cross-check. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 5 Router(config-cfm-xcheck)# mep-id 6 Router(config-cfm-xcheck)# mep-id 1101 Router(config-cfm-xcheck)# mep-id 1103`
	3.	Enable Ethernet CFM continuity check for another domain and service. Example: `Router(config)# ethernet cfm Router(config-cfm)# domain evpn-bd2 level 3 id null Router(config-cfm-dmn)# service evpn-bd2 bridge group BG2 bridge-domain BD2 $ Router(config-cfm-dmn-svc)# continuity-check interval 10s`
	4.	Configure MEP cross-check for antoher domain. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-xcheck)# mep-id 11 Router(config-cfm-xcheck)# mep-id 21 Router(config-cfm-xcheck)# mep-id 101 Router(config-cfm-xcheck)# mep-id 201`
	5.	Configure the bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group BG1 Router(config-l2vpn-bg)# bridge-domain BD1 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/0.1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/1.2 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 101`
	6.	Configure another bridge domain and assign interfaces to the bridge domain. Example: `Router(config)# l2vpn Router(config-l2vpn)# bridge group BG2 Router(config-l2vpn-bg)# bridge-domain BD2 Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/2.1 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# interface TenGigE0/0/0/5.2 Router(config-l2vpn-bg-bd-ac)# exit Router(config-l2vpn-bg-bd)# evi 201`
	7.	Enable CFM on interfaces with corresponding domain, service, and MEP IDs. Example: Router(config)# interface TenGigE0/0/0/0.1 l2transport Router(config-subif)# encapsulation dot1q 1 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd1 mep-id 1103 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/1.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd service evpn-bd1 mep-id 5 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/2.1 l2transport Router(config-subif)# encapsulation dot1q 1 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd2 service evpn-bd2 mep-id 101 Router(config-if-cfm)# root Router(config)# interface TenGigE0/0/0/5.2 l2transport Router(config-subif)# encapsulation dot1q 2 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain evpn-bd2 service evpn-bd2 mep-id 11
	8.	Running configuration of scenario 4. Example: ethernet cfm domain evpn-bd level 4 id null service evpn-bd1 bridge group BG1 bridge-domain BD1 continuity-check interval 10s mep crosscheck mep-id 5 mep-id 6 mep-id 1101 mep-id 1103 ! ! ! domain evpn-bd2 level 3 id null service evpn-bd2 bridge group BG2 bridge-domain BD2 continuity-check interval 10s mep crosscheck mep-id 11 mep-id 21 mep-id 101 mep-id 201 ! ! ! ! l2vpn bridge group BG1 bridge-domain BD1 interface TenGigE0/0/0/0.1 ! interface TenGigE0/0/0/1.2 ! evi 101 ! ! ! bridge group BG2 bridge-domain BD2 interface TenGigE0/0/0/2.1 ! interface TenGigE0/0/0/5.2 ! evi 201 ! ! ! ! interface TenGigE0/0/0/0.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain evpn-bd service evpn-bd1 mep-id 1103 ! ! ! interface TenGigE0/0/0/1.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain evpn-bd service evpn-bd1 mep-id 5 ! ! ! interface TenGigE0/0/0/2.1 l2transport encapsulation dot1q 1 ethernet cfm mep domain evpn-bd2 service evpn-bd2 mep-id 101 ! ! ! interface TenGigE0/0/0/5.2 l2transport encapsulation dot1q 2 ethernet cfm mep domain evpn-bd2 service evpn-bd2 mep-id 11 ! ! !

CFM on EVPN E-Line single-homing

A CFM on EVPN E-Line single-homing is a network monitoring solution that

operates on networks using EVPN E-Line single-homed devices
monitors E-Line services providing high-speed Layer 2 connectivity, and
ensures high resiliency for the Layer 2 services.

CFM up MEP is supported only on single-homing Layer 2 main and subinterfaces.

How CFM on EVPN E-Line single-homing works

Summary

The key components involved in the CFM on EVPN E-Line single-homing process are:

Cisco routers (Nodes 1, 2, and 3): These routers form the network topology and are interconnected.
CFM: Provides fault detection and monitoring capabilities within the EVPN E-Line service.
EVPN E-Line service: A point-to-point Ethernet VPN service that supports single-homing configurations.

CFM on EVPN E-Line single-homing enables routers to exchange monitoring messages over a full mesh to detect faults and ensure continuous service integrity. This process supports rapid fault detection and high availability in single-homed EVPN E-Line deployments.

Workflow

These stages describe how CFM on EVPN E-Line single-homing works.

Cisco routers (Nodes 1, 2, and 3) establish full mesh connectivity to support CFM operations within the EVPN E-Line topology.
CFM messages are exchanged between the routers to monitor connectivity and detect faults.
Faults detected by CFM trigger notifications and enable rapid troubleshooting within the EVPN E-Line single-homing environment.
Routers maintain continuous monitoring to ensure service integrity and performance.

Result

This process enables robust fault management and monitoring for EVPN E-Line single-homing deployments, ensuring high availability and rapid fault detection in the network.

Configure CFM on EVPN E-Line single-homing

Enable and validate CFM to monitor service continuity and endpoint liveliness for EVPN E-Line service.

Use this task to configure CFM service continuity checks, Maintenance End Point (MEP) cross-checks, and enable CFM on interfaces for EVPN E-Line single-homing deployments.

Procedure

	1.	Enable CFM continuity check. Example: `Router# ethernet cfm Router(config-cfm# domain xcup1 level 7 id null Router(config-cfm-dmn)# service xcup1 xconnect group evpn_vpws_Bundle_ether203 p2p evpn_vpws-100 id number 4001 Router(config-cfm-dmn-svc)# continuity-check interval 1s`
	2.	Configure MEP cross-check to validate remote MEPs. Example: `Router(config-cfm-dmn-svc)# mep crosscheck Router(config-cfm-dmn-svc)# mep-id 4001 Router(config-cfm-dmn-svc)# commit` Repeat the above configurations for node 2 and node 3, with the respective mep-id values. For node 2, configure MEP cross-check with respective mep-id values of node 1 and node 3 (2001 and 3001 respectively, in this example). For node 3, configure MEP cross-check with respective mep-id values of node 1 and node 2 (4001 and 2001 respectively, in this example).
	3.	Enable CFM on the interface. Example: `Router# configure Router(config)# interface Bundle-Ether203.2001 l2transport Router(config-subif)# encapsulation dot1q 2001 Router(config-subif)# ethernet cfm Router(config-if-cfm)# mep domain xcup1 service xcup1 mep-id 2001 Router(config-if-cfm-mep)# commit` You must repeat the above configurations for node 2 and node 3, with the respective mep-id values.
	4.	Running configuration of CFM on EVPN E-Line. Example: `ethernet cfm domain xcup1 level 7 id null service xcup1 xconnect group evpn_vpws_Bundle_ether203 p2p evpn_vpws-100 id number 4001 continuity-check interval 1s mep crosscheck mep-id 4001 ! ! ! ! interface Bundle-Ether203.2001 l2transport encapsulation dot1q 2001 ethernet cfm mep domain xcup1 service xcup1 mep-id 2001 !`
	5.	Use the show ethernet cfm services command to verify CFM on EVPN E-Line. Example: `Router# show ethernet cfm services Summary for Domain xcup1 (level 7), Service xcup1 ============================================================================= Domain MIB index: 1, Service MIB index: 1 Domain ID: NULL, Service ID: UINT: 4001 Service configured on P2P cross-connect evpn_vpws-100 in group evpn_vpws_Bundle_ether CCM interval: 1s Local MEPs: 1 total Peer MEPs: 2 total MIPs: 0, MIP creation rule: always`

CFM is configured on EVPN E-Line, providing continuous service monitoring and fault detection through MEP cross-checks and continuity checks, ensuring network reliability and rapid troubleshooting.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.