OcNOS SP : Carrier Ethernet Guide : Carrier Ethernet Configuration : Y.1731 and CFM Over VXLAN ELAN Single Home
Y.1731 and CFM Over VXLAN ELAN Single Home
Overview
The Single Home VxLAN ELAN Y.1731 CFM over Sub-interface feature enables the monitoring and management of Virtual Extensible LAN (VxLAN) Ethernet LAN services using the Y.1731 Connectivity Fault Management (CFM) protocol over sub-interfaces. This feature enhances fault detection and performance monitoring capabilities for VxLAN E-LAN services, allowing network operators to ensure high availability and reliability of their networks. By extending Y.1731 CFM functionality to sub-interfaces in single home VxLAN E-LAN deployments, this feature provides comprehensive end-to-end visibility and control, enabling proactive fault detection, isolation, and troubleshooting.
Feature Characteristics
Utilizes sub-interfaces to partition Ethernet traffic within the Single Home VxLAN ELAN architecture, enabling efficient service delivery and management.
Implements VxLAN ELAN architecture with single-homing capabilities, facilitating the creation of Virtual Extensible LAN (VxLAN) with simplified configurations and reduced complexity.
Provides robust fault detection mechanisms to identify connectivity issues, link failures, and service disruptions in Ethernet networks.
Benefits
Provides detailed insights into Ethernet service performance, enabling proactive monitoring and optimization of network resources.
Minimizes service downtime by promptly detecting and resolving faults, ensuring uninterrupted service delivery and customer satisfaction.
Optimizes network resource utilization and bandwidth allocation by identifying and addressing connectivity issues in a timely manner.
Facilitates rapid fault identification and isolation, accelerating troubleshooting processes and reducing mean time to repair (MTTR).
Ensures compliance with Service Level Agreements (SLAs) by maintaining service quality metrics within defined thresholds and objectives.
Prerequisites
Ensure that the network devices (routers, switches) support Y.1731 CFM functionality and Single Home VxLAN ELAN configuration.
Verify that the devices are running compatible software versions that include support for these features.
Configuration
Configure Single Home VxLAN ELAN Y.1731 CFM over Sub-interface for enhanced fault management in VxLAN networks.
Topology
The topology consists of three Customer Edge devices (CE1, CE2, and CE3) connected to Provider Edge devices (PE1,PE2, and PE3) through sub-interfaces. The Provider Edge devices are interconnected through Provider devices (P1 and P2).
Y.1731 functionality is implemented over these sub-interfaces, allowing for fault detection and performance monitoring of Ethernet connectivity between the customer sites.
VXLAN ELAN Over Sub-interface-Single Home
Perform the following configurations to configure Single Home VxLAN ELAN Y.1731 CFM over Sub-interface:
1. On Customer Edge (CE) Nodes (CE1, CE2, and CE3), configure the interface xe1 :
CE1(config)#interface xe11
CE1(config-if)#commit
CE1(config-if)#exit
Note: Similarly follow the same steps to configure xe11(CE1) and xe12(CE2).
2. Create sub-interface (xe11.20)adding the VLAN:
CE1(config)#interface xe11.20
CE1(config-if)#encapsulation dot1q 20
CE1(config-if)#commit
CE1(config-if)#exit
 
CE1(config)#interface xe43.20 switchport
CE1(config-if)#encapsulation dot1q 20
CE1(config-if)#commit
CE1(config-if)#exit
3. Set up a cross-connect named (VC20), specifying in and out interfaces:
CE1(config)#cross-connect VC20
CE1(config-xc)#interface xe11.20
CE1(config-xc)#interface xe43.20
CE1(config-xc)#commit
4. Perform the following on PE1:
1. Configure CFM related hardware profiles:
PE1(config)# hardware-profile filter cfm-domain-name-str enable
PE1(config)# hardware-profile statistics cfm-lm enable
PE1(config)# hardware-profile statistics cfm-ccm enable
PE1(config)#hardware-profile statistics cfm-slm enable
Note: In Q2 devices, hardware-profile filter cfm-domain-name-str enable by default is enabled.
2. Configure the loopback interface with a secondary IP address(1.1.1.1/32):
PE1(config)#interface lo
PE1(config-if)#ip address 1.1.1.1/32 secondary
PE1(config-if)#commit
PE1(config-if)#exit
3. Configure interface xe9 and xe14 with an IP address (192.168.10.1/24 and 192.168.20.1/24):
PE1(config)#interface xe9
PE1(config-if)#load-interval 30
PE1(config-if)#ip address 192.168.10.1/24
PE1(config-if)#label-switching PE1(config-if)#commit
PE1(config-if)#exit
 
PE1(config)#interface xe14
PE1(config-if)#load-interval 30
PE1(config-if)#ip address 192.168.20.1/24
PE1(config-if)#label-switching PE1(config-if)#commit
PE1(config-if)#exit
 
4. Configure OSPF routing, specify the OSPF router ID as (1.1.1.1), enable BFD on all interfaces, define the network (1.1.1.1/32) in area (0.0.0.0), and define the network (192.168.10.0/24 & 192.168.20.0/24) in area (0.0.0.0):
PE1(config)#router ospf 1
PE1(config-router)#ospf router-id 1.1.1.1
PE1(config-router)#bfd all-interfaces
PE1(config-router)#network 1.1.1.1/32 area 0.0.0.0
PE1(config-router)#network 192.168.10.0/24 area 0.0.0.0
PE1(config-router)#network 192.168.20.0/24 area 0.0.0.0
PE1(config-router)#commit
PE1(config-router)#exit
5. Enable VxLAN globally and configure VTEP IP:
PE1(config)# nvo vxlan enable
PE1(config)# nvo vxlan vtep-ip-global 1.1.1.1
PE1(config)# commit
 
6. Configure BGP with the remote PE devices and activate EVPN:
PE1(config)# router bgp 100
PE1(config-router)# neighbor 2.2.2.2 remote-as 100
PE1(config-router)# neighbor 2.2.2.2 update-source lo
PE1(config-router)# neighbor 3.3.3.3 remote-as 100
PE1(config-router)# neighbor 3.3.3.3 update-source lo
PE1(config-router)# address-family l2vpn evpn
PE1(config-router-af)# neighbor 2.2.2.2 activate
PE1(config-router-af)# neighbor 3.3.3.3 activate
PE1(config-router-af)# exit
PE1(config-router)# exit
PE1(config)# commit
7. Configure MAC VRF with the appropriate RD and RT:
PE1(config)#mac vrf vrf20
PE1(config-vrf)# rd 1.1.1.1:20
PE1(config-vrf)# route-target both 20:20
PE1(config-vrf)#commit
PE1(config-vrf)#exit
PE1(config)#exit
8. Map the VXLAN instance and VRF, specifying the EVPN ID:
PE1(config)# nvo vxlan id 20 ingress-replication
PE1(config-nvo)# vxlan host-reachability-protocol evpn-bgp vrf20
PE1(config-nvo)#vni-name SH20
PE1(config-nvo)#commit
9. Configure VXLAN access ports on PE1:
PE1(config)# interface xe10.20 switchport
PE1(config-if)# encapsulation dot1q 20
PE1(config-if)# access-if-evpn
PE1(config-acc-if-evpn)#map vpn-id 20
PE1(config-acc-if-evpn)# commit
10. Configure CFM MEP on PE1, define the FCM domain (SH002), create MA, configure MEP, and configure Remote MEP Auto-discovery,set CC Interval 3ms:
PE1(config)#ethernet cfm domain-type character-string domain-name SH002
level 6 mip-creation default
PE1(config-ether-cfm)#service ma-type string ma-name ma20
PE1(config-ether-cfm-ma)#ethernet cfm mep up mpid 120 active true xe10.20
vlan 20
PE1(config-ether-cfm-ma-mep)#cc multicast state enable
PE1(config-ether-cfm-ma-mep)#exit-ether-ma-mep-mode
PE1(config-ether-cfm-ma)#rmep auto-discovery enable
PE1(config-ether-cfm-ma)#cc interval 3ms
PE1(config-ether-cfm-ma)#exit-ether-ma-mode
PE1(config-ether-cfm)#commit
11. Provide CFM configuration, define a delay measurement profile named DM, set the measurement interval to 1 second, specify the number of intervals stored as 2, configure the message period as 1 second, define a loss measurement profile named LM, set the measurement type to LMM, set the measurement interval to 1 second, specify the number of intervals stored as 3, define a service level measurement profile named SLM, set the measurement type to SLM:
PE1(config)# ethernet cfm delay-measurement profile-name DM
PE1(config-cfm-dm)# measurement-interval 1
PE1(config-cfm-dm)# intervals-stored 2
PE1(config-cfm-dm)# message-period 1s
PE1(config-cfm-dm)# commit
 
PE1(config)# ethernet cfm loss-measurement profile-name LM
PE1(config-cfm-lm)# measurement-type lmm
PE1(config-cfm-lm)# measurement-interval 1
PE1(config-cfm-lm)# intervals-stored 3
PE1(config-cfm-lm)# message-period 1s
PE1(config-cfm-lm)# commit
 
PE1(config)# ethernet cfm loss-measurement profile-name SLM
PE1(config-cfm-lm)# measurement-type slm
PE1(config-cfm-lm)# measurement-interval 1
PE1(config-cfm-lm)# intervals-stored 3
PE1(config-cfm-lm)# message-period 1s
PE1(config-cfm-lm)# commit
Configuration Snapshot:
CE1:
interface xe11
load-interval 30
!
interface xe43
load-interval 30
!
interface xe11.20 switchport
encapsulation dot1q 20
!
interface xe43.20 switchport
encapsulation dot1q 20
 
cross-connect SH20
interface xe43.20
interface xe11.20
 
CE2:
interface ce23
load-interval 30
!
interface ce45
load-interval 30
!
interface ce23.20 switchport
encapsulation dot1q 20
!
interface ce45.20 switchport
encapsulation dot1q 20
 
cross-connect SH20
interface ce23.20
interface ce45.20
CE3:
interface xe7
load-interval 30
!
interface ce48
load-interval 30
!
interface xe7.20 switchport
encapsulation dot1q 20
!
interface ce48.20 switchport
encapsulation dot1q 20
 
cross-connect SH20
interface xe7.20
interface ce48.20
 
PE1:
Interface configuration:
 
interface lo
ip address 127.0.0.1/8
ip address 1.1.1.1/32 secondary
 
interface xe9
speed 10g
load-interval 30
ip address 192.168.10.1/24
mtu 9216
 
interface xe14
speed 10g
load-interval 30
ip address 192.168.20.1/24
mtu 9216
 
OSPF configuration:
router ospf 100
ospf router-id 1.1.1.1
network 1.1.1.1/32 area 0.0.0.0
network 192.168.10.0/24 area 0.0.0.0
network 192.168.20.0/24 area 0.0.0.0
BGP configuration:
router bgp 100
bgp router-id 1.1.1.1
neighbor 2.2.2.2 remote-as 100
neighbor 2.2.2.2 update-source lo
neighbor 3.3.3.3 remote-as 100
neighbor 3.3.3.3 update-source lo
address-family l2vpn evpn
neighbor 2.2.2.2 activate
neighbor 3.3.3.3 activate
exit-address-family
VxLAN configuration:
nvo vxlan enable
!
evpn vxlan multihoming enable
!
nvo vxlan vtep-ip-global 1.1.1.1
!
 
mac vrf vrf20
rd 1.1.1.1:20
route-target both 20:20
!
nvo vxlan id 20 ingress-replication
vxlan host-reachability-protocol evpn-bgp vrf20
vni-name SH20
 
interface xe10.20 switchport
encapsulation dot1q 20
load-interval 30
access-if-evpn
map vpn-id 20
!
 
CFM Configurations:
ethernet cfm domain-type character-string domain-name SH002 level
6 mip-creation default
service ma-type string ma-name ma20
ethernet cfm mep up mpid 120 active true xe10.20 vlan 20
cc multicast state enable
exit-ether-ma-mep-mode
rmep auto-discovery enable
cc interval 3ms
exit-ether-ma-mode
 
P1:
Interface configuration:
 
interface lo
ip address 127.0.0.1/8
ip address 11.11.11.11/32 secondary
 
interface xe9
speed 10g
load-interval 30
ip address 192.168.10.2/24
mtu 9216
 
interface xe11
speed 10g
load-interval 30
ip address 192.168.30.1/24
mtu 9216
 
interface xe20
speed 10g
load-interval 30
ip address 192.168.40.1/24
mtu 9216
 
 
OSPF configuration:
router ospf 100
ospf router-id 11.11.11.11
network 11.11.11.11/32 area 0.0.0.0
network 192.168.10.0/24 area 0.0.0.0
network 192.168.30.0/24 area 0.0.0.0
network 192.168.40.0/24 area 0.0.0.0
 
PE2:
Interface configuration:
 
interface lo
ip address 127.0.0.1/8
ip address 2.2.2.2/32 secondary
 
 
interface xe2
speed 10g
load-interval 30
ip address 192.168.50.2/24
mtu 9216
 
interface xe3
speed 10g
load-interval 30
ip address 192.168.30.2/24
mtu 9216
OSPF configuration:
router ospf 100
ospf router-id 2.2.2.2
network 2.2.2.2/32 area 0.0.0.0
network 192.168.30.0/24 area 0.0.0.0
network 192.168.50.0/24 area 0.0.0.0
BGP configuration:
router bgp 100
bgp router-id 2.2.2.2
neighbor 1.1.1.1 remote-as 100
neighbor 1.1.1.1 update-source lo
neighbor 3.3.3.3 remote-as 100
neighbor 3.3.3.3 update-source lo
address-family l2vpn evpn
neighbor 1.1.1.1 activate
neighbor 3.3.3.3 activate
exit-address-family
VxLAN configuration:
nvo vxlan enable
!
evpn vxlan multihoming enable
!
nvo vxlan vtep-ip-global 2.2.2.2
!
 
mac vrf vrf20
rd 2.2.2.2:20
route-target both 20:20
!
nvo vxlan id 20 ingress-replication
vxlan host-reachability-protocol evpn-bgp vrf20
vni-name SH20
 
interface ce23.20 switchport
encapsulation dot1q 20
load-interval 30
access-if-evpn
map vpn-id 20
!
CFM Configurations:
ethernet cfm domain-type character-string domain-name SH002 level
6 mip-creation default
service ma-type string ma-name ma10
ethernet cfm mep up mpid 220 active true ce23.20 vlan 20
cc multicast state enable
exit-ether-ma-mep-mode
rmep auto-discovery enable
cc interval 3ms
exit-ether-ma-mode
 
 
PE3:
Interface configuration:
 
interface lo
ip address 127.0.0.1/8
ip address 3.3.3.3/32 secondary
 
interface xe20
speed 10g
load-interval 30
ip address 192.168.40.2/24
mtu 9216
 
interface xe27
speed 10g
load-interval 30
ip address 192.168.60.2/24
mtu 9216
 
OSPF configuration:
router ospf 100
ospf router-id 3.3.3.3
network 3.3.3.3/32 area 0.0.0.0
network 192.168.40.0/24 area 0.0.0.0
network 192.168.60.0/24 area 0.0.0.0
 
BGP configuration:
router bgp 100
bgp router-id 3.3.3.3
neighbor 1.1.1.1 remote-as 100
neighbor 1.1.1.1 update-source lo
neighbor 2.2.2.2 remote-as 100
neighbor 2.2.2.2 update-source lo
address-family l2vpn evpn
neighbor 1.1.1.1 activate
neighbor 2.2.2.2 activate
exit-address-family
VxLAN configuration:
 
nvo vxlan enable
!
evpn vxlan multihoming enable
!
nvo vxlan vtep-ip-global 3.3.3.3
!
 
mac vrf vrf20
rd 3.3.3.3:20
route-target both 20:20
!
nvo vxlan id 20 ingress-replication
vxlan host-reachability-protocol evpn-bgp vrf20
vni-name SH20
 
interface xe7.20 switchport
encapsulation dot1q 20
load-interval 30
access-if-evpn
map vpn-id 20
!
CFM Configurations:
ethernet cfm domain-type character-string domain-name SH002 level
6 mip-creation default
service ma-type string ma-name ma10
ethernet cfm mep up mpid 420 active true xe7.20 vlan 20
cc multicast state enable
exit-ether-ma-mep-mode
rmep auto-discovery enable
cc interval 3ms
exit-ether-ma-mode
 
Validation
Verify the nvo vxlan status:
7033-PE1#show nvo vxlan
VXLAN Information
=================
Codes: NW - Network Port
AC - Access Port
(u) - Untagged
 
VNID VNI-Name VNI-Type Type Interface ESI VLAN DF-Status Src-Addr Dst-Addr
_______________________________________________________________________________________________________________________________
20 SH20 L2 NW ---- ---- ---- ---- 1.1.1.1 3.3.3.3
20 SH20 L2 NW ---- ---- ---- ---- 1.1.1.1 2.2.2.2
20 SH20 -- AC xe3.20 --- Single Homed Port --- ---- ---- ---- ----Total number of entries are 4
 
 
Verify the CFM Errors Status:
7033-PE1#show ethernet cfm errors domain SH002
Domain Name MA Name Level VLAN InnerVLAN MEPID Defects
-----------------------------------------------------------------------
SH002 ma20 6 20 NA 120 .....
Verify the CFM MA status:
7033-PE1#show ethernet cfm maintenance-points remote domain SH002 ma-name ma20
MA_NAME MEPID RMEPID LEVEL Rx CCM RDI PEER-MAC TYPE
------------------------------------------------------------------------------
ma20 120 420 6 Yes False e001.a6b8.ed09 Learnt
ma20 120 220 6 Yes False 5c07.5851.cfad Learnt
 
Verify the Ping:
7033-PE1#ping ethernet mac 5c07.5851.cfad unicast source 120 domain SH002 ma ma20
success rate is 100 (5/5)
7033-PE1#ping ethernet mac e001.a6b8.ed09 unicast source 120 domain SH002 ma ma20
success rate is 100 (5/5)
 
Verify the Traceroute:
7033-PE1#traceroute ethernet 5c07.5851.cfad mepid 120 domain SH002 ma ma20
MP Mac Hops Relay-action Ingress/Egress Ingress/Egress action
5c07.5851.cfad 1 RlyHit Ingress IngOK
7033-PE1#traceroute ethernet e001.a6b8.ed09 mepid 120 domain SH002 ma ma20
MP Mac Hops Relay-action Ingress/Egress Ingress/Egress action
e001.a6b8.ed09 1 RlyHit Ingress IngOK
7033-PE1#
 
Verify the Delay-measurement:
7033-PE1#delay-measurement type proactive profile-name DM rmep 220 mep 120 domain SH002 ma ma20
7033-PE1#2024 Oct 04 08:29:40.642 : 7033-PE1 : ONMD : INFO : [CFM_PM_SESSION_INFO_5]: CFM Frame Delay Measurement session started for MEP Id 120 and RMEP Id 220
 
7033-PE1#show ethernet cfm delay-measurement mep 120 domain SH002 ma-name ma20
MD : SH002
MA : ma20
MEP : 120
VLAN ID : 20
Interface : xe3.20
Peer MAC Address : 5c07.5851.cfad
 
CURRENT:
======================
RMEP ID : 220
Measurement ID : 1
Measurement Type : DMM
Elapsed time(sec) : 13
Start Time : 2024 Oct 04 08:29:40
Suspect Flag : FALSE
Min Frame Delay(usec) : 20
Max Frame Delay(usec) : 20
Avg Frame Delay(usec) : 20
Min Inter FD Variation(usec): 0
Max Inter FD Variation(usec): 0
Avg Inter FD Variation(usec): 0
 
FRAME DELAY BINS
Bin Number Bin Threshold(usec) Bin Counter
========================================================
1 0 - < 4999 14
2 5000 - < 9999 0
3 10000 - < 4294967295 0
 
INTER-FRAME DELAY BINS
Bin Number Bin Threshold(usec) Bin Counter
========================================================
1 0 - < 4999 13
2 5000 - < 4294967295 0
 
Verify the Synthetic Loss Measurement:
7033-PE1#loss-measurement type proactive profile-name SLM rmep 220 mep 120 domain SH002 ma ma20
7033-PE1#2024 Oct 04 08:32:02.959 : 7033-PE1 : ONMD : INFO : [CFM_DEFECT_INFO_5]: CFM Frame Loss Measurement started for MEP:120 MA:ma20 MD:SH002
 
7033-PE1#show ethernet cfm loss-measurement mep 120 domain SH002 ma-name ma20
MEP: 120 MA: ma20
CURRENT:
Measurement ID : 2
Suspect : False
Measurement Type : slm
Elapsed time(sec) : 10
Start Time : 2024 Oct 04 08:33:02
Near End loss : 0
Far End loss : 0
Near End accumulated loss : 0
Far End accumulated loss : 0
Near End frame loss ratio : 0
Far End frame loss ratio : 0
 
HISTORY:
 
Measurement ID : 1
Suspect : False
Measurement Type : slm
Elapsed time(sec) : 60
End Time : 2024 Oct 04 08:33:02
Near End loss : 0
Far End loss : 0
Near End accumulated loss : 0
Far End accumulated loss : 0
Near End frame loss ratio : 0
Far End frame loss ratio : 0
Near End frame loss ratio min : 0
Far End frame loss ratio min : 0
Near End frame loss ratio max : 0
Far End frame loss ratio max : 0
Implementation Examples
Enterprise Connectivity Monitoring:
Scenario: A large enterprise operates multiple branch offices connected via Ethernet services provided by a service provider network.
Use Case: Y.1731 CFM over sub-interface using Single Home VxLAN enables the enterprise to monitor theconnectivity and performance of its branch office connections. It facilitates proactive fault detection and management, ensuring reliable and uninterrupted communication between the headquarters and branch offices.
Service Provider Network Operations:
Scenario: A service provider manages a diverse range of Ethernet services for its enterprise customers, including VPNs, Internet access, and cloud connectivity.
Use Case: Y.1731 CFM over sub-interface using Single Home VxLAN empowers the service provider to deliverhigh-quality Ethernet services with enhanced fault management capabilities. It enables the provider to quickly identify and resolve connectivity issues, minimize service downtime, and maintain customer satisfaction.
Glossary
The following provides definitions for key terms or abbreviations and their meanings used throughout this document:
 
Key Terms/Acronym
Description
Y.1731
A standard defined by the International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) that specifies performance monitoring and fault management for
Ethernet-based networks.
Sub-interface
A logical division of a physical interface, typically used to separate traffic based on VLAN or
other criteria. In this context, sub-interfaces are employed to establish distinct connections within
the VxLAN ELAN SH topology.
ELAN
ELAN is a type of VxLAN service that provides point-to-multi point Ethernet connectivity between two sites.
Single Home (SH)
Refers to the configuration where a Customer Edge device (CE) is connected to only one
Provider Edge device (PE) within an VxLAN setup. It contrasts with the multi-homed configuration, where a CE may be connected to multiple PEs.
Maintenance End Point (MEP)
MEP is a CFM entity that resides at the edge of a CFM domain. It is responsible for generating and transmitting CFM protocol packets to detect faults and collect performance data.
Maintenance Domain (MD)
MD is a logical grouping of MEPs within a CFM network. MEPs within the same MD can communicate with each other to perform CFM functions such as fault detection and performance monitoring.
Maintenance Association(MA)
MA is a collection of MEPs associated with a specific service or set of services. It defines the scope of CFM operations within a maintenance domain.
Maintenance Point Identifier (MPID)
MPID is a unique identifier assigned to each MEP within a maintenance association. It is used to distinguish between different MEPs within the same MA.
Service Level Measurement (SLM)
SLM is a CFM function used to measure the loss characteristics of a network path. It collects data on packet loss, delay, and jitter to assess the quality of service provided by the network.
Loopback Message Generation (LMM )
LMM is a CFM function used to test end-to-end connectivity by generating loopback messages. These messages are transmitted from a MEP and looped back to the same MEP to verify bidirectional communication.
Delay Measurement Message (DMM)
DMM is a CFM function used to measure the one-way delay of packets transmitted across a network. It helps assess the performance of the network in terms of packet delivery time.
Continuity Check (CC)
CC is a CFM function used to verify the continuity of a service or network path by periodically sending continuity check messages between MEPs. It helps detect connectivity faults such as link failures or misconfigurations.