Y.1731 and CFM Over VXLAN ELINE Single Home
Overview
The Single Home VxLAN ELINE Y.1731 CFM over Sub-interface feature enables the monitoring and management of Virtual Extensible LAN (VxLAN) E-Line 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-Line 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-Line 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 ELINE architecture, enabling efficient service delivery and management.
• Implements VxLAN ELINE 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 ELINE configuration.
Verify that the devices are running compatible software versions that include support for these features.
Configuration
Configure Single Home EVPN ELINE Y.1731 CFM over Sub-interface for enhanced fault management in EVPN networks.
Topology
The topology consists of two Customer Edge devices (CE1 and CE2) connected to Provider Edge devices (PE1 and PE2) 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 ELINE Over Sub-interface-Single Home
Perform the following configurations to configure Single Home VxLAN ELINE Y.1731 CFM over Sub-interface:
1. On Customer Edge (CE) Nodes (CE1, and CE2), configure the interface xe1 and set load interval of (30 seconds):
CE1(config)#interface xe11
CE1(config-if)#load-interval 30
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.10)adding the VLAN:
CE1(config)#interface xe11.10 switchport
CE1(config-if)#encapsulation dot1q 20
CE1(config-if)#commit
CE1(config-if)#exit
CE1(config)#interface xe43.10 switchport
CE1(config-if)#encapsulation dot1q 10
CE1(config-if)#commit
CE1(config-if#exit
3. Set up a cross-connect named (SH10), specifying in and out interfaces:
CE1(config)#cross-connect SH10
CE1(config-xc)#interface xe11.10
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 and 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)# address-family l2vpn evpn
PE1(config-router-af)# neighbor 2.2.2.2 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 vrf10
PE1(config-vrf)# rd 1.1.1.1:10
PE1(config-vrf)# route-target both 10:10
PE1(config-vrf)#commit
PE1(config-vrf)#exit
8. Map the VxLAN instance and VRF, specifying the VxLAN ID:
PE1(config)# nvo vxlan id 10 xconnect target-vxlan-id 100
PE1(config-nvo)# vxlan host-reachability-protocol evpn-bgp vrf20
PE1(config-nvo)#vni-name SH10
PE1(config-nvo)#commit
9. Configure VxLAN access interface on PE1:
PE1(config)# interface xe10.10 switchport
PE1(config-if)# encapsulation dot1q 10
PE1(config-if)# access-if-evpn
PE1(config-acc-if-evpn)#map vpn-id 10
PE1(config-acc-if-evpn)# commit
10. Configure CFM UP MEP on PE1, define the CFM domain (SH001), create MA, configure UP MEP, and configure Remote MEP Auto-discovery enable, 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 ma10
PE1(config-ether-cfm-ma)#ethernet cfm mep up mpid 110 active true xe3.10 vlan 10
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, set the measurement type to LMM, set the measurement interval to 1 second, specify the number of intervals stored as 3:
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
Configuration Snapshot:
CE1:
interface xe11
load-interval 30
!
interface xe43
switchport
load-interval 30
!
interface xe11.10 switchport
encapsulation dot1q 10
!
interface xe43.10 switchport
encapsulation dot1q 10
cross-connect SH10
interface xe43.10
interface xe11.10
CE2:
interface ce23
load-interval 30
!
interface ce49
switchport
load-interval 30
!
interface ce23.10 switchport
encapsulation dot1q 10
!
interface ce49.10 switchport
encapsulation dot1q 10
cross-connect SH10
interface ce23.10
interface ce49.10
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
address-family l2vpn evpn
neighbor 2.2.2.2 activate
exit-address-family
VxLAN configuration:
nvo vxlan enable
!
evpn vxlan multihoming enable
!
nvo vxlan vtep-ip-global 1.1.1.1
!
mac vrf vrf10
rd 1.1.1.1:10
route-target both 10:10
!
nvo vxlan id 10 xconnect target-vxlan-id 100
vxlan host-reachability-protocol evpn-bgp vrf10
vni-name SH10
interface xe10.10 switchport
encapsulation dot1q 10
load-interval 30
access-if-evpn
map vpn-id 10
!
CFM Configurations:
ethernet cfm domain-type character-string domain-name SH001 level
6 mip-creation default
service ma-type string ma-name ma10
ethernet cfm mep up mpid 110 active true xe10.10 vlan 10
cc multicast state enable
exit-ether-ma-mep-mode
rmep auto-discovery enable
cc interval 3ms
exit-ether-ma-mode
P1 Configurations:
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
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
PE2:
Interface configuration:
interface lo
ip address 127.0.0.1/8
ip address 22.22.22.22/32 secondary
interface xe14
speed 10g
load-interval 30
ip address 192.168.20.2/24
mtu 9216
interface xe2
speed 10g
load-interval 30
ip address 192.168.40.1/24
mtu 9216
OSPF configuration:
router ospf 100
ospf router-id 22.22.22.22
network 22.22.22.22/32 area 0.0.0.0
network 192.168.20.0/24 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
PE2:
Interface configuration:
interface lo
ip address 127.0.0.1/8
ip address 2.2.2.2/32 secondary
interface xe1
speed 10g
load-interval 30
ip address 192.168.40.1/24
mtu 9216
interface xe3
speed 10g
load-interval 30
ip address 192.168.30.1/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.40.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
address-family l2vpn evpn
neighbor 1.1.1.1 activate
exit-address-family
!
VxLAN configuration:
nvo vxlan enable
!
evpn vxlan multihoming enable
!
nvo vxlan vtep-ip-global 2.2.2.2
!
mac vrf vrf10
rd 2.2.2.2:10
route-target both 10:10
!
nvo vxlan id 100 xconnect target-vxlan-id 10
vxlan host-reachability-protocol evpn-bgp vrf10
vni-name SH10
interface ce23.10 switchport
encapsulation dot1q 10
load-interval 30
access-if-evpn
map vpn-id 100
!
CFM Configurations:
ethernet cfm domain-type character-string domain-name SH001 level
6 mip-creation default
service ma-type string ma-name ma10
ethernet cfm mep up mpid 210 active true ce23.10 vlan 10
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 xconnect status:
PE1#show nvo vxlan xconnect id 10
EVPN Xconnect Info
========================
AC-AC: Local-Cross-connect
AC-NW: Cross-connect to Network
AC-UP: Access-port is up
AC-DN: Access-port is down
NW-UP: Network is up
NW-DN: Network is down
NW-SET: Network and AC both are up
Local Remote Connection-Details
================================ ============ ===============================================================================================
VPN-ID EVI-Name MTU VPN-ID Source vlan-info Destination PE-IP MTU Type NW-Status
outer,inner
================================ ============ ===============================================================================================
10 SH10 1500 100 xe3.10 ----,---- --- Single Homed Port --- 2.2.2.2 1500 AC-NW NW-SET
Total number of entries are 1
Verify the CFM Errors:
PE1#show ethernet cfm errors domain SH001
Domain Name MA Name Level VLAN InnerVLAN MEPID Defects
-----------------------------------------------------------------------
SH001 ma10 6 10 NA 110 ....
Verify the ethernet cfm ma status domain is active or not:
PE1#show ethernet cfm ma status domain SH001 ma-name ma10
MA NAME STATUS
-------------------------------
ma10 Active
Verify the local MEP is installed or not:
PE1#show ethernet cfm maintenance-points local mep domain SH001 ma-name ma10
MPID Dir Lvl VLAN CC-Stat HW-Status CC-Intvl MAC-Address Def Port MD Name
--------------------------------------------------------------------------------
110 Up 6 10 Enable Installed 3 ms e8c5.7afe.fae9 F xe3.10 SH001
Verify the RMEP is learned or not:
PE1#show ethernet cfm maintenance-points remote domain SH001 ma-name ma10
MA_NAME MEPID RMEPID LEVEL Rx CCM RDI PEER-MAC TYPE
------------------------------------------------------------------------------
ma10 110 210 6 Yes False 5c07.5851.cfad Learnt
Verify the Ping:
PE1#ping ethernet mac 5c07.5851.cfad unicast source 110 domain SH001 ma ma10
success rate is 100 (5/5)
Verify the traceroute:
PE1#traceroute ethernet 5c07.5851.cfad mepid 110 domain SH001 ma ma10
MP Mac Hops Relay-action Ingress/Egress Ingress/Egress action
5c07.5851.cfad 1 RlyHit Ingress IngOK
Verify the Delay-measurement:
PE1#delay-measurement type proactive profile-name DM rmep 210 mep 110 domain SH001 ma ma10
PE1#2024 Oct 02 02:07:58.409 : PE1 : ONMD : INFO : [CFM_PM_SESSION_INFO_5]: CFM Frame Delay Measurement session started for MEP Id 110 and RMEP Id 210
PE1#
PE1#show ethernet cfm delay-measurement
mep profile
PE1#show ethernet cfm delay-measurement mep 110 domain SH001 ma-name ma10
MD : SH001
MA : ma10
MEP : 110
VLAN ID : 10
Interface : xe3.10
Peer MAC Address : 5c07.5851.cfad
CURRENT:
======================
RMEP ID : 210
Measurement ID : 1
Measurement Type : DMM
Elapsed time(sec) : 12
Start Time : 2024 Oct 02 02:07:58
Suspect Flag : FALSE
Min Frame Delay(usec) : 20
Max Frame Delay(usec) : 21
Avg Frame Delay(usec) : 20
Min Inter FD Variation(usec): 0
Max Inter FD Variation(usec): 1
Avg Inter FD Variation(usec): 0
FRAME DELAY BINS
Bin Number Bin Threshold(usec) Bin Counter
========================================================
1 0 - < 4999 12
2 5000 - < 9999 0
3 10000 - < 4294967295 0
INTER-FRAME DELAY BINS
Bin Number Bin Threshold(usec) Bin Counter
========================================================
1 0 - < 4999 11
2 5000 - < 4294967295 0
Verify the Loss Measurement:.
PE1#loss-measurement type proactive profile-name LM rmep 210 mep 110 domain SH001 ma ma10
PE1#2024 Oct 02 02:09:24.850 : PE1 : ONMD : INFO : [CFM_DEFECT_INFO_5]: CFM Frame Loss Measurement started for MEP:110 MA:ma10 MD:SH001
PE1#show ethernet cfm loss-measurement mep 1100 domain SH001 ma-name ma10
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 : lmm
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 ELINE 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 ELINE 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 VLANs or other criteria. In this context, sub-interfaces are employed to establish distinct connections within the VxLAN ELINE SH topology. |
EVPN | Ethernet Virtual Private Network (VPN) is a technology that enables the creation of virtual private networks over an Ethernet-based infrastructure. It provides multi-tenancy and allows for the segmentation of traffic in service provider networks. |
ELINE | ELINE is a type of VxLAN service that provides point-to-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. |