CFM Tac Toi1

802.
1AG – Ethernet Service

OAM and
ITU-T Y.1731 TAC TOI
Praveen Bhat
Anuj Agrawal
Sumitha Govindrajan
Loganathan Nehru
Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1
Agenda
1. IEEE 802.1ag Overview

2. Cisco IOS IEEE 802.1ag Implementation
Configuration model ( w/ various Topologies)
1. D1 -> D8
2. ITU-T Y.1731 ETH-AIS/ETH-LCK/ETH-RDI
3. CFM interworking with E-LMI, Link OAM,
Y.1731
4. CFM Troubleshooting
5. Caveats
6. References
Technical Overview
CFM Overview
 Family of protocols that provides capabilities to detect,
verify, isolate and report end-to-end ethernet connectivity
faults
 Employs regular Ethernet frames that travel in-band with
the customer traffic
Devices that cannot interpret CFM Messages forward them as
normal data frames
 CFM frames are distinguishable by Ether-Type 89-02

(and MAC Address for multicast messages)
 Standardized by IEEE (P802.1ag) in late 2007
IEEE std. 802.1ag-2007
CFM Overview (cont.)
 Key CFM mechanisms include:
– Nested Maintenance Domains (MDs) that break up
the responsibilities for network administration of a
given end-to-end service
– Maintenance Associations (MAs) that monitor
service instances under a given MD
– Maintenance Points (MPs) that generate and
respond to CFM PDUs
– Protocols (Continuity Check, Loopback and
Linktrace) used for Fault Management activities
CFM Concepts
Maintenance Domain (MD)
CE CE
Operator A Operator B
Service Provider
Customer
 Defined by Operational/Contractual Boundaries

e.g. Customer / Service Provider / Operator
 MD may nest and touch, but never intersect
 Up to 8 levels of “nesting”: MD Level (0..7)
The higher the level, the broader its reach
CFM Concepts
Maintenance Association (MA)
CE Operator A Operator B CE
 Monitors connectivity of a particular service instance in a given MD

(e.g. 1 service traversing 4 MDs = 4 MAs)
 Defined by a set of Maintenance End Points (MEP) at the edge of
a domain
 Identified by MAID == “Short MA” Name + MD ID
CFM Concepts
Maintenance Point (MP)—MEP
MEP MEP
MEP MEP
MEP MEP MEP MEP
 Maintenance Association End Point (MEP)

 Define the boundaries of a MD
 Support the detection of connectivity failures between any pair
of MEPs in an MA
 Associated per MA and identified by a MEPID (1-8191)
 Can initiate and respond to CFM PDUs
CFM Concepts
MAs and UP/DOWN MEPs
 Applicability of UP/DOWN DOWN MEP
MEPs in switches: Bridge 1 Bridge 2

Bridge Bridge Bridge Bridge
DOWN MEPs are typically
used for MAs spanning a Port
Relay
Port Port
Relay
Port
single link Entity Entity
UP MEPs are commonly Monitored area

used for MAs with a wider
reach (e.g. end-to-end,
beyond a single link) UP MEP
Bridge 1 Bridge 2
Bridge Bridge Bridge Bridge
Port Port Port Port

Relay Relay
Entity Entity
Monitored area
CFM Concepts
Maintenance Point (MP)—MIP
MEP MIP MIP MEP

Customer
MEP MIP MIP MEP
Service Provider
MEP MIP MIP MEP MEP MIP MIP MIP MIP MEP
Operator A Operator B
MIP MIP MIP MIP
 Maintenance Domain Intermediate Point (MIP)

 Support the discovery of paths among MEPs and location of faults along
those paths
 Can add, check and respond to received CFM PDUs
CFM Protocols
There are three (3) protocols defined by CFM
 Continuity Check Protocol
Fault Detection
Fault Notification
 Loopback Protocol
Fault Verification
 Linktrace Protocol
Fault Isolation
CFM Protocols
Continuity Check Protocol
Catalogue and
Catalogue Catalogue Terminate
MEP MIP MIP MEP
1 2 3
Continuity Check Message
X
(CCM)
 Used for Fault Detection and Notification

 Per-Maintenance Association multicast “heart-beat” messages
Carries status of port on which MEP is configured
Uni-directional (no response required)
Transmitted at a configurable periodic interval by MEPs
 Catalogued by MIPs at the same MD-Level and service,
Terminated by remote MEPs in the same MA
CFM Protocols
Loopback Protocol
S D
MEP MIP MIP MEP
1 1 1. Loopback Message (LBM)

2 2 2. Loopback Reply (LBR)
 Used for Fault Verification—Ethernet Ping

 MEP can transmit a unicast LBM to a MEP or MIP in the same MA
 Receiving MP responds by transforming the LBM into a unicast
LBR sent back to the originating MEP
 MEP can transmit a multicast LBM for Y.1731, and only MEPs in
the same MA respond
CFM Protocols
Linktrace Protocol
6
S 4 D
2
MEP MIP MIP MEP
1 3 5 1, 3, 5
X Linktrace Message (LTM)
Y 2, 4, 6
Linktrace Reply (LTR)
 Used for Path Discovery and Fault Isolation—Ethernet Traceroute

 MEP can transmit a multicast message (LTM) in order to discover
the MPs and path to a MIP or MEP in the same MA
 Each MIP along the path and the terminating MP return a unicast
LTR to originating MEP
CFM Protocols
CFM PDU Summary
 Summary of CFM PDUs defined per protocol and type

of frame used
CFM Destination
CFM PDU
Protocol MAC address
Continuity Check
Continuity Check Multicast
Message (CCM)
Loopback Message Unicast
(LBM) Multicast – Y.1731
Loopback
Loopback Reply
Unicast
(LBR)
Multicast (w/unicast
Linktrace Message
destination address
(LTM)
Linktrace as payload)
Linktrace Reply
Unicast
(LTR)
CFM Protocols
Putting Everything Together
1. Run Connectivity Check to proactively detect a

soft or hard failure
2. Upon a failure detection, use Loopback to
verify it
3. Upon verification, run Traceroute to isolate it;
multiple segment LBMs can also be used to
isolate the fault
Cisco IOS
IEEE 802.1ag
Implementation
CFM Shared MP address model
“bridge-brain” model
 MEP
Up MEP uses the same “bridge-brain” MAC address
*Down MEP and Port MEP use port MAC address
 MIP uses “bridge-brain” MAC address
*: The only exception being the L2vfi case wherein down MEP’s use
bridge-brain address.
Notes :
CFM unicast MAC : Bridge-brain Mac
CFM multicast MAC : 0180.c200.003x
D1 CFM Multicast MAC : 0100.0ccc.cccx
X : 4 bits representing the level
CFM frames are distinguishable by Ether-Type 89-02 (and MAC
Address for multicast messages)
CFM – Match register requirements
CFM needs a minimum of 2 Match registers ( a 44-bit and a 48-bit match
register) to be available on the LC.
1. 44-bit Register : CFM Multicast MAC
2. 48-bit Register : CFM Unicast MAC
When spanning-tree mode is PVST, one match register is occupied by the
PVST MAC. Hence in all scenarios where we have only 2 match registers
available, PVST and CFM cannot co-exist.
When Spanning-tree mode is PVST on the box and when you try to enable
CFM globally, even if one of the LC doesnt have the required match
register free, cfm will be de-activated. This doesn’t apply to the Supervisor
cards ,which have only 2 Match registers. in this scenario CFM will be
automatically disabled on the SUP ports and enabled on rest of the LC’s.
On Metro Cards like ES20 and ES+,
1. The bridge-brain MAC ( unicast MAC) is programmed in a 44-bit match
register. This enables us to use the range of Bridge-brain addresses for
Port-channel use. We support 15 portchannels with the bridge-brain
model.
2. Port-MAC’s are also programmed in a 44-bit Match register.
CFM Network Provisioning
Network Provisioning
802.3ah (Provider)
CFM (Global Attributes)

3. Configure CFM Domains
on Devices
802.3ah (UNI)
Service Provisioning
1. Enable CFM globally
Define CFM Domains in
network 4. Define MIPs policy (auto-
CFM
create(Service Attributes)
or manually configured)
2. Define global CFM parameters 5. Service Provisioning

E-LMI
(cache sizes, hold timers)
CFM Service Provisioning
CFM Service Provisioning
1. Define Service 6. Configure MIPs 8. Enable CFM SNMP
(Type, UNIs, VLANs etc.) policies (or manually Traps

on
UNIs and NNI hand-
802.3ah (Provider) offs)
9. Enable Crosscheck
2. Provision Service 7. Configure MEPs on or Static Rmep Check
UNIs and NNI hand-
CFM (Global Attributes) offs
3. Configure CFM 802.3ah (UNI)

Maintenance Associations
Service Provisioning
CFM (Service Attributes)
4. Enable CC
E-LMI
5. Tweak CC Timers and
Thresholds per SLA
Cisco CFM Implementation
Verify CFM Operation
 Show Local Maintenance Points
Router# show ethernet cfm maintenance-points local
Router#show ethernet cfm runtime lmep (PRIV INTERNAL command)
 Show Remote Maintenance Points - MEP CCDB
Router# show ethernet cfm maintenance-points remote
 Show Remote Maintenance Points - MIP CCDB
Router# show ethernet cfm mpdb
 Show CFM Errors DB
Router# show ethernet cfm errors
 Show CFM configuration errors
Router# show ethernet cfm errors configuration
 Show CFM Domains
Router# show ethernet cfm domain
 Show Traceroute Information
Router# show ethernet cfm traceroute-cache
Troubleshooting
 Loopback
Router# ping ethernet {mac-address | mpid id | multicast}
domain domain-name { vlan vlan-id | port | evc evc-name }
 Traceroute
Router# traceroute ethernet {mac-address | mpid id } domain
domain-name { vlan vlan-id | port | evc evc-name }
CFM Network and Service Provisioning Example
MEP MIP
GE2/7 GE2/1
2. MEP
interface GigabitEthernet2/7 3. MIP
ethernet cfm mep domain Provider_Domain mpid 1500 vlan 500 interface GigabitEthernet2/1
ethernet cfm mip level 4 vlan 500
1. Global Configuration MIP

MEP
ethernet cfm global
ethernet cfm domain Provider_Domain level 4 MD and MD Level
service customer_500_provider vlan 500
continuity-check MA
!
ethernet cfm traceroute cache
!
snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
CFM Network and Service Provisioning Example (Cont.)
MIP MIP
GE2/1 GE2/2
Global Configuration
!
ethernet cfm global
ethernet cfm mip auto-creation level 4 vlan 500
!
MIPs
MIPs are created on all interfaces that VLAN 500 is allowed, and VLAN 500 is not associated with a Domain/Service
CFM Network and Service Provisioning Example (Cont.)
MIP MEP
GE3/2 GE3/1
2. MEP
interface GigabitEthernet3/1
ethernet cfm mep domain Provider_Domain mpid 1510 vlan 500
3. MIP 1. Global Configuration

MIPs are created on all ethernet cfm global
interfaces where VLAN 500 is ethernet cfm domain Provider_Domain level 4
allowed at level 4 service customer_500_provider vlan 500
continuity-check
mip auto-create
!
ethernet cfm traceroute cache
!
snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
 HotICE compliance
 Rollback for 1AG to 1AG configuration commands, but does not rollback from
1AG to D1 configuration commands
 HA/ISSU/SSO capable
CFM SNMP Instrumentation
Cisco SNMP Traps
 Cisco-defined MIB (CISCO-ETHER-CFM-MIB)

 CCM traps generated by MEPs
Trap Type Object
cEtherCfmCcMepUp
cEtherCfmCcMepDown
CCM cEtherCfmCcCrossconnect
cEtherCfmCcLoop
cEtherCfmCcConfigError
Cisco SNMP Traps (cont.)
 Cisco-defined MIB (CISCO-ETHER-CFM-MIB)

 Crosschecks traps generated by MEPs
Trap Type Object
cEtherCfmXCheckServiceUp
cEtherCfmXCheckMissing
Cross-Check
cEtherCfmXCheckUnknown
Continuity Check Protocol - Fault Detection
CCM-based detectable Faults Notification (SNMP Trap)
MEP Down (code:

Inability to receive consecutive CCMs from a remote MEP in the same MA
timeout)
MEP Up (code:
Remote port failure
portState)
Reception of its own CCM Loop
Reception of a CCM with a Lifetime of zero (Last Gasp CCM – due to remote MEP MEP Down (code:
removed or disabled only from D1 device) lastGasp)
Reception of a CCM with an incorrect MPID (i.e. duplicate value) Configuration Error
Reception of a CCM from a remote MEP assigned to another service - The reception of a
Crossconnect
CCM with an incorrect MA
Continuity Check Protocol - Fault Detection (cont.)
CCM-based detectable Events
Notification
(SNMP Trap)
Discovery of a remote MEP for the first time

MEP Up (code:
new)
MEP Up (code:
Re-discovery of a previously expired remote MEP
returning)
CFM support in SRE
CFM Support in SRE
As part of the D8.1 implementation , we support the following in SRE

 CFM over EVC BD (Both MEP and MIP)
 CFM over Switchport (Both MEP and MIP)
 CFM over EVC Xconnect (Both MEP and MIP)
 CFM over Routed ports ( sub-interfaces) (Both MEP and MIP)
 CFM over L2VFI (Down MEP only)
 Port MEP
 CFM over port-channel (with first 3 interface types as given above)
Port Mep is supported only on member links not on the PC.
CFM over Bridge-
Domain
CFM over BD
Highlights
 CFM IEEE 802.1ag is supported over BD Infrastructure
 Compatible and Interoperable with CFM over Switchport / VLAN
 Extends support for “double tagged” and “untagged” CFM frames
 CFM MEPs/MIPs provisioned under EFP
EFP MUST be associated to an EVC
EFP MUST be mapped to a Bridge Domain
 OAM IW support
CFM (over BD) to E-LMI IW
Link OAM to CFM (over BD) IW
 IP SLA support
IP SLA with CFM (over BD) integration supported
CFM over BD
Highlights continued…
 Encapsulation of locally sourced CFM traffic is the SAME as the

encapsulation configured on the egress EFP
 If egress EFP encapsulation includes vlan range/lists; one can
explicitly configure the encapsulation to be used for locally sourced
CFM traffic
 By default (if not explicitly given) for CFM encapsulation, first vlan
is used from the efp encapsulation vlan range/list
CFM over BD
Highlights (cont.)
 In case of UP MEP,
Encapsulation of locally sourced dot1q 20
CFM traffic is the SAME as the BD 100
encapsulation configured on the CCM, 20 Rewrite pop 1 sym
EFP itself.
 EVC BD replication happens on
the LC, rewrites should be dot1q 30
configured appropriately on the dot1q 10 BD 100
evc’s BD 100
Rewrite pop 1 CCM
Rewrite pop 1
sym
sym
 If switchport and evc bd in the
same broadcast domain, evc bd
should push tags in egress as
appropriate. CCM, 30
 Same BD , if tag mismatch ,
packets will be dropped in
egress. ( this used to work in D1) dot1q 40
BD 100
CCM, 40 Rewrite pop 1
sym
CCM – Continuity Check Message

CFM over BD
Configuration Anatomy
MD ethernet cfm domain <name> level <level>

Global
MA service <name/num/id> evc <evc-name> [direction down ]

EVC ethernet evc <evc-name>
EVC Name is
required for CFM to
be configured on
EFP service instance <efp-id> ethernet <evc-name> EFP
EFP Encapsulation encapsulation …

Interface
BD is required to be
configured for CFM
option to be available
BD bridge-domain <id>
MEP cfm mep domain <domain-name> mpid <id>
MIP cfm mip level <level>
CFM Encapsulation cfm encapsulation {dot1ad/dot1q
<vlan-id>} [dot1q/second-dot1q
Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential
<vlan-id>] [cos <vlaue>] 38
CFM over BD
Configuration Anatomy (cont.)

Global

EVC name is locally
significant
EFP service instance <efp-id> ethernet <evc-name>

Interface
CFM Encapsulation cfm encapsulation …
CFM over BD

Global

MA name must be the
same E2E for a given
service

Interface
CFM over BD
MD ethernet cfm domain <domain-name> level <domain-level>

Global
MA service <name/num/id> evc <evc-name>

EVC ethernet evc <evc-name> 2 different domains with same evc name is
blocked if they are at the same level
(similar to vlan case to avoid domain
overlap).
Outward services with same evc name is
allowed in 2 domains at same level.

Interface
CFM over
ScEOMPLs
CFM over ScEOMPLs
 Ability to monitor end-to-end Ethernet connectivity faults over

ScEOMPLs pseudowires.( evc xconnect pw’s)
 Complete support of CFM transparent case if CFM is globally
enabled.
 Supports UP MEP, Down MEP and MIP’s
 Tightly coupled to the evc state. If the VC is down, evc is down and
CFM functionality on the access side also is affected.
 Support upto 8K IFM’s and OFM’s.
 Support AIS, RDI and LCK. ( Y.17131 features)
CFM over ScEOMPLs
(UNI)
(UNI) 2.2.2.2
1.1.1.1
MPLS Cloud
CE PE PE CE
802.1ag
CFM
EVC Xconnect -
EVC Xconnect -
Service instance 1 eth evc10 Service instance 1 eth evc10
Encap dot1q 100 Encap dot1q 100
Xconnect 1.1.1.1 1 encap mpls Xconnect 2.2.2.2 1 encap mpls
Cfm mep domain provider mid 100 Cfm mep domain provider mid 101
Cfm mip lev 7 Cfm mip lev 7
CFM over Evc Xconnect
Configuration Anatomy

Global

EVC ethernet evc <evc-name> No vlan required
EVC Name is
required for CFM to
be configured on
EFP service instance <efp-id> ethernet <evc-name> EFP
xconnect is required
EFP Encapsulation encapsulation … to be configured for
Interface
CFM option to be
available
Xconnect [Remote peer] [vc id] encap [type]

<vlan-id>} [dot1q/second-dot1q
Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential
<vlan-id>] [cos <vlaue>] 45
Configuration 1.1.1.1 2.2.2.2
Global: MPL
Ethernet cfm global CE1 PE1 S

Clou
PE2 CE2
EVC1 d
Ethernet cfm enable EVC1
Ethernet cfm domain Provider level 6

Service xconn evc xconn
Continuity-check
Ethernet evc xconn
UPE2:
UPE1:
Int gi 2/0/0
Int gi 1/0/0
Service instance 1 Ethernet xconn Service instance 1 Ethernet xconn
Encap dot1q 100
Encap dot1q 100
Xconnect 1.1.1.1 1 encap mpls
Xconnect 2.2.2.2 1 encap mpls
Cfm mep domain provider mpid 101
Cfm mep domain provider mpid 100
Cfm mip lev 7
Cfm mip lev 7
Notes: Cfm is supported over encap default and untagged evc’s

cfm encap has to be configured appropriately on these Evc’s
CFM over L2VFI
CFMoL2VFI: Technical Overview
Physical
Interface
Emulated LAN
Interface
Bridge VPLS Core

Forwarde
Access r Pseudowires
Pseudowires
L2 VFI
CFM Outward-facing MEP
 L2VFI Forwarder is a combination of fully-meshed core. The bundle of

core VCs is treated as one virtual port.
 In Software, Access PWs ≡ Spoke VCs and Core PWs ≡ Hub VCs
 Service providers mostly care about the state of Core VCs.
 Supports ONLY Down MEP over VFI Core pseudowires (that is, ability to
monitor hub VCs only)
 MIPs are not supported
 Complete support of CFM transparent case if CFM is globally enabled.
 No Support of D1 over VFI Pseudowires
CFMoL2VFI: What’s Supported
CE PE PE CE
CORE VC
Down MEP
MEP MEP MEP

Down MEP on CE through VC
MEP UP MEPon PE though VC
Down MEPon PE though VC MEP
 CORE VC between PEs may be

transparent.
Down MEP for VFI
 Interfaces connecting Access side PE-CE maybe
EVC-BD
Switchport
Spoke-VC (VPLS hub-Spoke Model)
CFMoL2VFI: Configuration Anatomy
MD ethernet cfm domain <domain-name> level <level>
MA service <name/num/id> evc <evc-name> vlan <vlan-id> direction down
EVC Name is
EVC ethernet evc <evc-name> required for CFM to
be configured on
l2vfi
EVC Association l2 vfi <vfi-name> evc <evc-name>

VPN vpn id <vpn-id> BD association is
Global
required for CFM

option to be available
BD Association bridge-domain <vlan-id> vlan
VC neighbor <peer-ip> <vc-id> encapsulation <pw-class> [no-split-horizon]
MEP cfm mep domain <domain-name> mpid <mep-id>

<vlan-id>} [dot 1q/second-dot1q
<vlan-id>] [cos <vlaue>]
SVI Interface Vlan <vlan-id>
VFI Association xconnect vfi <vfi-name>
CFMoVFI configuration
 VFI MEPs are implemented via EVC-BD association. ethernet evc new_vfi_evc
 SVI hwidbs are not used to identify Core VC. l2 vfi try manual new_vfi_evc
vpn id 81
 l2 vfi try manual new_vfi_evc This command does VFI to
EVC association. bridge-domain 81 vlan
neighbor 10.30.30.16 encapsulation mpls
 bridge-domain 81 vlan This makes BD to VFI
association. Without this CFM MEP cli is not enabled. cfm mep domain ofm_vfi mpid 8112
CFMoL2VFI: Netdr
Dump
------- dump of outgoing inband packet -------

interface Vl81, routine draco2_ibc_soutput, timestamp 00:00:00
dbus info: src_vlan 0x51(81), src_indx 0x452E0(283360), len 0x3F54(16212)
bpdu 1, index_dir 1, flood 1, dont_lrn 1, dest_indx 0x4051(16465)
52E0023F 5051E9E4 52E0023F 54ABE9E4 52E0023F 54ABE9E4 00000008 40510000
mistral hdr: req_token 0x0(0), src_index 0x840(2112), rx_offset 0x51(81)
requeue 0, obl_pkt 0, vlan 0x0(0)
destmac 01.80.C2.00.00.34, srcmac 00.14.1C.39.6B.10, protocol 8842
layer 3 data: 32E45650 91888902 80010546 28F97832 1FB10407 6F666D5F
76666902 0B6F666D 5F766669 5F63666D 00000000 00000000
00000000 00000000 00000051 00000380 00084051 081A
CFMoL2VFI: Complex topology
3 3
CE CE
HUB-VC PE
4
PE
1
Spoke VC HUB-VC
PE 1
1
4
PE Spoke VC
2 HUB-VC PE Spoke PE
2
CFMoL2VFI: Sample Topology and
Configurations
l2 vfi vfi100 manual e100
vpn id 1
bridge-domain 100 vlan
4 4
neighbor 2.2.2.2 12 encapsulation mpls
l2 vfi vfi100 manual e100 neighbor 3.3.3.3 13 encapsulation mpls
vpn id 1 CE CE
cfm mep domain D1 mpid 1
bridge-domain 100 vlan l2 vfi vfi100 manual e100
vpn id 1mpls
neighbor 3.3.3.3 312 encapsulation Interface gigabitEthernet 2/0/0
cfm mep domain D3 mpid 1 bridge-domain 100 vlan switchport
neighbor 1.1.1.1 13 encapsulation
switchport
mpls
mode trunk
Int gi3/0/0 neighbor 2.2.2.2 23 encapsulation mpls
switchport neighbor 11.11.11.11 311 encapsulation mpls no-split-horizon
switchport mode tru neighbor 12.12.12.12 312 encapsulation mpls no-split-horizon
ethernet cfm mep domain D2cfm
mpid mep
201domain D1 mpid 3
nPE
uPE Hub VC 1.1.1.1
1
11.11.11.11 3
Spoke VC Interface gi1/0/0
nPE service Hub
instance
VC 1 ethernet e100
1
encapsulation dot1q 100
Spoke VC 3.3.3.3 neighbor 2.2.2.2 213 encapsulation mpls
3 l2 vfi vfi100 manual e100 1 Spoke VC

vpn id 1 nPE
uPE bridge-domain 100 vlan
Hub VC
uPE
12.12.12.12 neighbor 3.3.3.3 311 encapsulation mpls
2.2.2.2 13.13.13.13
2 2
l2 vfi vfi100 manual
Interface gigabitEthernet 3/0/0e100
vpn id11ethernet e100
service instance
bridge-domain
encapsulation dot1q 100 100 vlan
neighbor
bridge-domain 100 1.1.1.1 12 encapsulation mpls
neighbor 3.3.3.3 23 encapsulation mpls
neighbor 13.13.13.13 213 encapsulation mpls no-split-horizon
CFM on Port-
Channel
CFM on Port-Channel
 Supported with Etherchannel in LACP or PAGP mode

( cfm on FEC mode isn’t supported)
 UP/DOWN MEPs are supported on the Etherchannel;
not on the physical members of the Etherchannel
 Port MEPs are supported on the physical members of
the Etherchannel; not supported on the Etherchannel
 CFM on PC EVC BD, EVC Xconnect supported
D1 to D8.1
CLI differences
 There are quite a lot of changes in the CLI to configure

CFM.
 Please refer to the configuration guide.
Port MEP
 A “Port MEP” is not associated with a VLAN tag and is different
than a VLAN MEP.
 When the PI code detects that CC messages are not being
received on a Port MEP, PI will declare that the port is MAC
Operationally Down.
 Platform (PD) must block all messages except the CFM and
OAM messages when MAC Operationally Down.
 PI will monitor CFM incoming messages and when PI detects
incoming CC messages resuming and determines that the Port
Error condition has been removed, PI will notify MAC
Operationally Up.
 Ping and traceroute on trunk ports for Port-MEP's and down
MEP's configured on native vlan is supported only on ES20 and
ES40 line cards.
Autocreate MIP
 MIP can be created automatically using the below

command.
router(config)#ethernet cfm mip auto-create level ?
<0-7> maintenance level number
 MIP created either manually or automatically does the

same function.
MIP contd…
 IEEE 802.1ag specification no longer enforces MIP filtering levels
 MIP Filtering option is a Cisco value add feature carried forward
from D1
 If enabled, MIP filtering will:
–Drop all CFM packets at a lower level from both the wire side as well
as from the relay function side
–Catalog (as necessary) and pass thru CFM packets at the same level
–Transparently pass thru CFM packets at a higher level
 Global configuration parameter and is enabled “per box” on all
CFM interfaces.
 The default is off
Behavior with STP Blocked Ports
 Up MEPs – if MEP configured on STP blocked port, MEP can still

transmit or receive CFM messages via the relay function. But not
through other STP blocked ports.
 Down MEPs – if MEP configured on STP blocked port, MEP can still
transmit and receive CFM messages via the wire.
 MIPs – if MIP configured on STP blocked port, still able to receive and
respond to CFM messages from both relay and wire side, but cannot
forward any CFM messages.
 Transparent Ports – ports with no MEP or MIP configured; on STP
blocked ports CFM frames will be dropped on ingress or egress on
that port.
 You can ping or traceroute to a MEP where Continuity Check (CC) is
disabled. However, you cannot use ping and traceroute for an down
MEP on a STP blocked port configured on either a supervisor port or
a LAN port.
PVST and CFM co-existence
 PVST and CFM can co-exist in the system only if there

are enough MAC match registers to get both of them
programmed.
 If there are no MAC match registers available, run MST
before enabling CFM.
 The MAC registers can be verified using
‘show platform mrm info’ command on SP console.
Migration utility
 Migration utility running in IOS will help in changing the
configuration from D1 to D8.1.
 The user has to just reload the box with SRE image. The
migration utility will run during bootup to convert the
configuration. However startup-configuration will be still
D1.
Migration utility
 Limitation with EVC BD case
If there is evc-only service configured under domain in D1, it will fail while migrating to
D8.1.
To avoid this, configure both vlan-only and evc-only under domain in D1.
Example D1 configuration by which issue will be seen during migration
ethernet cfm domain 2OUT493 level 2 direction outward

service 1 evc 493
Configuration to avoid this issue
ethernet cfm domain 2OUT493 level 2 direction outward

service 1 evc 493
service 1 vlan 493
ITU-T Y.1731
ETH-AIS/ETH-LCK/ETH-RDI
AGENDA
 ITU-T Y.1731 Introduction

 Alarm Indication Signal (ETH-AIS)
 Remote Defect Indication (ETH-RDI)
 Locked Signal (ETH-LCK)
 ITU-T Y.1731 IOS Implementation
ITU-T Y.1731 Overview
 ITU-T recommendation that provides mechanisms for

user-plane OAM functionality in Ethernet networks.
Covers:
Fault Management mechanisms
Performance Management mechanisms
 Standardized by ITU-T SG 13 in May 2006

A new pre-published version dated Feb. 2008 after IEEE
802.1ag standardization
 Frames format (Multicast Address, Ethertype, and

common OAM PDU fields ) and base functionality are
generally agreed across IEEE 802.1ag and Y.1731
ITU-T Y.1731 Terminology
Comparison with IEEE 802.1ag
IEEE 802.1ag ITU-T Y.1731

ME Maintenance Entity ME Maintenance Entity
Maintenance
MA Association
MEG ME Group
MAID MA Identifier MEGID MEG Identifier

No such construct
MD Maintenance Domain --- available
MD MEG
MD Level MEG Level
Level Level
MEP MA End Point MEP MEG End Point
MIP MD Intermediate Point MIP MEG Intermediate Point
No such construct Server

--- available
Server MEP
MEP
ITU-T Y.1731 Overview
 OAM Functions for Fault Management ( FM )
Ethernet Continuity Check (ETH-CC) (Y.1731 adds unicast CCM)
Ethernet Loopback (ETH-LB) (Y.1731 adds multicast LBM)
Covered by
IEEE 802.1ag Ethernet Linktrace (ETH-LT)
Ethernet Remote Defect Indication (ETH-RDI)
Ethernet Alarm Indication Signal (ETH-AIS) Focus of this
presentation
Ethernet Locked Signal (ETH-LCK)
 OAM Functions for Performance Management

(PM)
Frame Loss Measurement (ETH-LM)
Frame Delay Measurement (ETH-DM)
PM functionality is not supported on 122SRE (Eagle).
Alarm Indication Signal
(ETH-AIS)
Alarm Indication Signal (AIS)
 Ethernet Alarm Indication function (ETH-AIS)
defined by ITU-T Y.1731
 Serves two purposes:
Loss of Continuity (LOC) Alarm Suppression so that
an NMS does not receive and excessive number of
redundant alarms for a particular fault
Informs clients of a transport path failure
ITU-T Y.1731 - ETH-AIS
Alarms Without AIS
SNMP Server
Northbound Link
LOC Traps Failure
Customer Operator A Operator B Customer
Equipment Bridges Bridges Equipment
MEP(7)
MIP(7)
MEP(5)
MIP(5)
MEP(3) MEP(2)
MIP(3) MIP(2)
SMEP
802.3ah/link status
Alarms With AIS
SNMP Server
Northbound LOC Traps Link
suppressed Failure
MEP(7)
MIP(7)
MEP(5)
MIP(5)
MEP(3) MEP(2)
MIP(3) MIP(2)
SMEP
802.3ah/link status
AIS
Transport Path Failure propagation
NMS
AIS Defect Link
Northbound Failure
Syslogs
MEP(7)
MIP(7)
MEP(5)
MIP(5)
MEP(3) MEP(2)
MIP(3) MIP(2)
SMEP/link-status
AIS
AIS Transmission
 Who can send AIS frames?
CFM Maintenance End Points (MEP)
AIS
 When are AIS frames sent by a MEP? 5
Upon detecting CC failures; such as: 4 AIS
Loss of Continuity (LOC), Loop,
Configuration Error (duplicate mpid), AIS
3 3
Cross-connect (different service)
Upon detecting AIS or LCK condition
(due to incoming AIS or LCK frames)
 A MEP, upon detecting a defect
condition, can transmit AIS frames in a AIS
direction opposite to its peer MEP(s) 5
 The first AIS frame must always be 4 AIS
transmitted immediately following the
detection of a defect condition 3 3
 AIS PDUs sent periodically at a

configured MD level until defect CCM (identical) Loop Error
condition is removed CCM (duplicate mpid) – Config Error
CCM (different MAID) - CrossConnect
No CCM – Timeout (Loss of Continuity)
AIS Transmission (cont.)
 Who can also send AIS

frames?
Server MEP
AIS AIS
 What is Server MEP?
Not to be confused with CFM
3 3
X
Server
MEPs MEP
In IOS, Link OAM and

Interface/Line Protocol State
act as Server MEPs AIS vid 100 vid 100
 When are AIS frames sent by AIS vid 200 vid 200
a Server MEP? AIS vid 300 vid 300
Upon detection of any signal AIS vid 400 vid 400
fail condition
AIS PDU per VLAN/EVC
3 3
X
Server
 See next slide for implemented MEP
behaviors in IOS
AIS Transmission (cont.)
AIS AIS
3 3
X
Server
MEP:
Interface State
Link Errors
AIS AIS
3 3
Link Monitoring Threshold exceeded
Server Action: port Error Disable
MEP:
Link OAM
802.3ah RFI
AIS AIS
3 3 Link Failure (unidirectional operation)
Server Dying Gasp
MEP: Critical Event
Link OAM
AIS Reception
 Who can react to AIS frames?
CFM Maintenance End Points (MEP)
 Upon receiving a frame with ETH-AIS information a

MEP detects AIS condition and may suppress loss of
continuity alarms associated with all its peer MEPs
 A MEP resumes loss of continuity alarm generation
upon detecting loss of continuity defect conditions in
the absence of AIS condition
Remote Defect
Indication (ETH-RDI)
Remote Defect Indication (RDI)
 Ethernet Remote Defect Indication (RDI) is defined by

IEEE 802.1ag and ITU Y.1731
 Used by a MEP to communicate to its peer MEPs that a
defect condition has been encountered
 ETH-RDI has the following two applications:
Single-ended fault management - The absence of received
ETH-RDI information in a single MEP indicates the absence of
defects in the entire MEG
Contribution to far-end performance monitoring - It reflects that
there was a defect condition in the far-end which is used as an
input to the performance monitoring process
ITU-T Y.1731
Remote Defect Indicator (ETH-RDI) (Cont.)
NMS
Link
Failure

CCM (RDI ON)
MEP(7)
AIS AIS
MIP(7) CCM (RDI ON)
MEP(5) AIS
MIP(5) CCM (RDI ON)
MEP(3) MEP(2)
MIP(3)
AIS MIP(2)
SMEP/link-status
AIS
ITU-T Y.1731
Remote Defect Indicator (ETH-RDI) (Cont.)
Customer Operator A CFM duplicate Operator B

mpid Customer
100
Equipment Bridges mpid detected Bridges Equipment
CFM duplicate CCM

mpid detected
(RDI ON)
mpid
MEP(7) mpid
100
200
MIP(7) CCM (RDI ON) CCM (RDI OFF)
MEP(5)
MIP(5)
MEP(3) MEP(2)
MIP(3) MIP(2)
SMEP
802.3ah/link status
CCM with RDI Transmission
 Who can send CCM with RDI frames?

MEP
 ETH-RDI is used only when ETH-CC transmission is enabled
 When are CCM with RDI frames sent by a MEP?
Upon detecting CC failures; such as: Loop, Configuration Error
(duplicate mpid), Cross-connect (different service)
Upon detecting AIS or LCK condition (due to incoming AIS or LCK
frames)
 A MEP, upon detecting a defect condition, can:
Sets the RDI field in the CCM frames for the duration of the defect
condition
Transmit CCM frames with RDI set in the direction towards its peer
MEP(s)
 When the defect condition clears, the MEP clears the RDI field in
the CCM frames in subsequent transmissions.
CCM with RDI Transmission
AIS AIS
5 5
AIS RDI
AIS RDI 4
4
CCM (identical) – Loop Error 3 3 AIS
3 3 CCM (duplicate mpid) – Config Error
RDI CCM (different MAID) - CrossConnect RDI
AIS
5 5
AIS CCM with
4 RDI 4 Port State
DOWN
3 3 No CCM 3 3
Timeout (Loss of Continuity) RDI
CCM with RDI Reception
 For a point-to-point ETH connection, a MEP can clear

the RDI condition when it receives the first CCM frame
from its peer MEP with the RDI field cleared
 For multipoint ETH connectivity, a MEP can clear the
RDI condition when it receives the CCM frames from its
entire list of peer MEP with the RDI field cleared.
Ethernet Locked Signal
(LCK)
ITU Y.1731
Ethernet Locked Signal (ETH-LCK)
 Main Applications
Inform immediate MD/MEG Level of a maintenance/
admin condition with interruption of data traffic
Useful when performing “intrusive” OAM service tests
 LCK Transmission
Upon starting “intrusive” test, the MP starts transmitting
periodic frames with ETH-LCK at a configured MD level
until test is stopped
 LCK Reception
Upon receiving a LCK frame, a MEP enters AIS defect
state and suppresses loss of continuity alarms
associated with all its peer MEPs
ITU Y.1731
Ethernet Locked Signal (ETH-LCK) (Cont.)

AIS AIS
MEP(7)
MIP(7) LCK LCK
MEP(5)
MIP(5)
MEP(3) Start Start MEP(2)
LCK LCK
MIP(3) LBM / LBR MIP(2)
SMEP
802.3ah/link status
AIS Objective:
LCK Intrusive per-service OAM loopback
LBM / LBR (drop Tx / Rx data traffic)
IOS ITU-T Y.1731 Fault
Management
Implementation
Cisco IOS Y.1731 Implementation
 Cisco IOS supports the following Y.1731 fault

management functions:
Alarm Indication Signal (ETH-AIS)
Remote Defect Indication (ETH-RDI)
Locked Signal (ETH-LCK)
Multicast Loopback
 Link OAM and Interface/Line Protocol State act as

Server MEPs (SMEPs)
AIS Configuration—Server MEP
 Default AIS configuration for Server MEP

Enabled
Transmission Period is 60 seconds
Transmission level (Immediate client MEG/MA level)
 Configuration to disable AIS for Server MEP
Global configuration for disabling generation of AIS by all Server MEPs
Router(config)#ethernet cfm ais link-status global
Router(config-ais-link-cfm)#disable
Interface level configuration for disabling generation of AIS by Server
MEP
Router(config-if)#no ethernet cfm ais link-status
AIS Configuration—Server MEP (Cont.)
 Configuration to Change Transmission period for Server MEP

Global configuration for changing Transmission period for all Server MEP
Router(config-ais-link-cfm)#period <1|60>
Interface level configuration for changing Transmission period for Server MEP
Router(config-if)#ethernet cfm ais link-status period <1|60>
 Configuration to change AIS Transmission Level for Server MEP

Global configuration for changing Transmission Level for all Server MEP
Router(config-ais-link-cfm)#level <0-7>
Interface level configuration for changing Transmission Level for Server MEP
Router(config-if)#ethernet cfm ais link-status level <0-7>
AIS Configuration—MEP
 Default AIS configuration for MEP

Enabled
Transmission period 60 seconds
Expiry Threshold (3.5)
Suppressing Loss of Continuity (LOC) Alarms is Enabled
 Configuration to disable AIS generation for MEP

Router(config-ecfm-srv)#no ais
 Configuration to change AIS transmission period for MEP

Router(config-ecfm-srv)#ais period <1|60>
 Configuration to change Transmission level

Router(config-ecfm-srv)#ais level <0-7>
 Configuration to change expiry threshold

Router(config-ecfm-srv)#ais expiry-threshold <2-255>
 Configuration to change alarm suppression

Router(config-ecfm-srv)#no ais suppress-alarms
LCK Configuration—Server MEP
 Default LCK configuration for Server MEP

Enabled
Transmission Period is 60 seconds
 Configuration to disable LCK for Server MEP

Global configuration for disabling generation of LCK by all Server MEPs
Router(config)#ethernet cfm lck link-status global
Router(config-lck-link-cfm)#disable
Interface level configuration for disabling generation of LCK by Server MEP
Router(config-if)#no ethernet cfm lck link-status
LCK Configuration—Server MEP (Cont.)
 Configuration to Change Transmission period for Server MEP

Global configuration for changing Transmission period for all Server MEP
Router(config-lck-link-cfm)#period <1|60>
Interface level configuration for changing Transmission period for Server MEP
Router(config-if)#ethernet cfm lck link-status period <1|60>
 Configuration to change LCK Transmission Level for Server MEP
Global configuration for changing Transmission Level for all Server MEP
Router(config-lck-link-cfm)#level <0-7>
Interface level configuration for changing Transmission Level for Server MEP
Router(config-if)#ethernet cfm lck link-status level <0-7>
 Syslog for AIS/LCK are generated right away due to asynchronous nature
whereas LOC took time to pop-up.
LCK Configuration—MEP
 Default LCK configuration for MEP

Enabled
Transmission period 60 seconds
Expiry Threshold (3.5)
 Configuration to disable LCK generation for MEP

Router(config-ecfm-srv)#no lck
 Configuration to change LCK transmission period for MEP

Router(config-ecfm-srv)#lck period <1|60>
 Configuration to change Transmission level

Router(config-ecfm-srv)#lck level <0-7>
 Configuration to change expiry threshold

Router(config-ecfm-srv)#lck expiry-threshold <2-255>
AIS/LCK Show/Exec Commands
 Server MEP specific display

Router#show ethernet cfm smep [interface <name>]
 MEP specific display for AIS/LCK

Router#show ethernet cfm main local detail
 Remote MEP specific display for RDI

Router#show ethernet cfm error
Router#show ethernet cfm maintenance-point remote detail
 Start/Stop Interface or MEP LCK

Router#ethernet cfm lck [start | stop] [interface <id> direction
[up | down] | mpid <id> domain <name> [vlan <id> | evc
<name>]] {drop l2-pdu}
Data Blocking (not supported)
 ITU-T Y.1731 recommends that MEP can decide

whether it blocks data frames when it detects AIS
defect condition.
 Data Blocking is recommended for Mismerge,
UnexpectedMEP detection, and UnexpectedMEGLevel
detection condition.
 Currently we don’t support data blocking for AIS.
Caveats
 Y1731 AIS/RDI is supported on all line cards.

 Loss-threshold value should be high (than default value) if SSO is
done with administrative LCK.
 LCK cannot be used with sub-second CC interval because of the
platform limitation.
 Drop-l2bpdu option is not supported in LCK.
 LT packets will be dropped in LCK condition on intermediate
routers, because it’s treated as data packets.
CFM interworking
with E-LMI, Link
OAM, Y.1731
CFM Interworking
(UNI)
(UNI)
MEN
(Provider/Operator)
CE PE PE CE
802.3ah 802.3ah
802.1ag
E-LMI CFM E-LMI
E-LMI : Ethernet Provisioning and Management entity across UNI (CE-PE)

802.1ag : Ethernet Service Layer Monitoring entity across MEN (PE-PE)
802.3ah : Link Layer Monitoring
Inter-working Scenarios: CFM to E-LMI
Customer Service Provider
CE
Ethernet Ethernet
Access Access
CE 1 uPE B nPE B nPE A uPE A CE 2

Service Layer
OAM
CFM to E-LMI I/W
E-LMI Network Layer
OAM
Provider Level CFM

CFM @ Provider Level acts as MEN OAM: provides EVC Status and Remote UNI Status/Name to E-LMI
– Port State TLV of CC Messages carry remote UNI status
– MEP Name TLV of CC Messages carry remote UNI name
– Status of remote MEP in CCDB indicates EVC State
Inter-working Scenarios: 802.3ah to CFM
Customer Service Provider
CE
Ethernet MPLS
Access Access
CE 1 uPE B PE-Agg B nPE B nPE A uPE A CE 2

Service Layer
OAM
AIS AIS CC
Transport
Layer OAM
802.3ah 802.3ah to CFM I/W 802.3ah
 Link Layer Defects detected by 802.3ah, relayed to CFM on same device.

 CFM notifies remote devices of localized fault.
 Two variants:
CC based (802.3ah on edge of domain)
AIS based (802.3ah within domain)
Interworking Configuration
BD configuration SVLAN configuration
ethernet cfm domain aaa level 5 ethernet cfm domain aaa level 5
service custA evc EVC_P2P service custA vlan 2
continuity-check continuity-check
service custA vlan 2 !
continuity-check ethernet evc EVC_P2P
! oam protocol cfm svlan 2 domain aaa
ethernet evc EVC_P2P !
oam protocol cfm domain aaa interface Ethernet0/0
! ethernet cfm mip level 7 vlan 1-4094
interface Ethernet0/0 ethernet cfm mep domain aaa mpid 1502 vlan 2
ethernet cfm mip level 7 vlan 1-4094 ethernet lmi interface
ethernet lmi interface ethernet uni id PE1:CE1
ethernet uni id PE1:CE1 service instance 101 ethernet EVC_P2P
service instance 5 ethernet EVC_P2P ethernet lmi ce-vlan map 2
encapsulation dot1q 2 !
ethernet lmi ce-vlan map 2
bridge-domain 2
cfm mep domain aaa mpid 20
!
!
SLA/CFM
Interworking
SLA/CFM Interworking
 IP SLA configuration is unchanged between CFM versions
 SLA utilize CFM to measure performance at the Ethernet Level.
 SLA is used measure response time, latency, packet loss and
other statistics.
 IP SLA Echo will interoperate with any CFM compliant
implementation.
 IP SLA Jitter will not interoperate with other vendors.
 Interworking for SLA/CFM is available for both Vlan and BD case.
 There is currently no IP SLA support for PORT MEP.
 SLA is a software based and has accuracy limitation.
 SLA entry will only be sent for active MEP entries.
Cisco IP SLA’s & CFM Integration Highlights
 In-band Performance Management Tool for Ethernet

Use native Ethernet frames
IP not required
 Built on CFM principles
Use Ethernet CFM frames to collect statistics
Probes performed in context of a VLAN and a CFM
Maintenance Domain
CFM MEPs define probe endpoints
 Automatic Discovery of Probe Endpoints
Rely on CFM Continuity Check Database (CCDB) to
automatically discover Probe Endpoints
EVC and Maintenance Domain based
Support ‘static’ probes and exclusions
IP SLA configuration
ip sla 1
ethernet echo mpid 333 domain aaa vlan 40
ip sla schedule 1 start-time now
ip sla 2
ethernet echo mpid 33 domain aaa evc evc_5
ip sla 3
ethernet jitter mpid 333 domain aaa vlan 40
ip sla 4
ethernet jitter mpid 33 domain aaa evc evc_5
Troubleshooting
Verify CFM Operation
 Show Local Maintenance Points
Router# show ethernet cfm maintenance-points local
Router#show ethernet cfm runtime lmep (PRIV INTERNAL command)
 Show Remote Maintenance Points - MEP CCDB
Router# show ethernet cfm maintenance-points remote
 Show Remote Maintenance Points - MIP CCDB
Router# show ethernet cfm mpdb
 Show CFM Errors DB
Router# show ethernet cfm errors
 Show CFM configuration errors
Router# show ethernet cfm errors configuration
 Show CFM Domains
Router# show ethernet cfm domain
 Show Traceroute Information
Router# show ethernet cfm traceroute-cache
Troubleshooting
 Loopback
Router# ping ethernet {mac-address | mpid id | multicast}
domain domain-name { vlan vlan-id | port | evc evc-name }
 Traceroute
Router# traceroute ethernet {mac-address | mpid id } domain
domain-name { vlan vlan-id | port | evc evc-name }
Debug commands
 Different types of CFM debug commands exist to assist in

trouble shooting
Router1# debug ethernet cfm ?

all Ethernet CFM errors, events, packets
diagnostic Ethernet CFM diagnostic information
error Ethernet CFM errors
events Ethernet CFM events
ha Ethernet CFM ha
packets Ethernet CFM packet-related information
 Can be used in conjunction with the show commands to

gather CFM information.
Debug commands (cont.)
 The events and packets allow conditional per service
filtering options.
 Diagnostic, error and HA do not have conditional per service
filtering options.
• Error – displays information about invalid information in
received CFM messages, internal errors or action errors
• HA – displays information about High Availability events
• Diagnostic – more detailed debug information for all
occurrences; able to set additional filtering (e.g. message
type filtering).
 ‘All’ option turns on debug events, packets, diagnostic
events, diagnostic packets, errors, and HA.
Debug commands Examples
 The all, events, and packets will do “conditional” debugging
for levels, domains and services in the configuration. Allows
user to determine granularity of specific debug information:
Router1# debug ethernet cfm events domain abc vlan 9
Ethernet CFM level 3 domain abc vlan 9 event debugging is on
Router1# debug ethernet cfm events vlan 9

Ethernet CFM level 7 domain abc7 vlan 9 event debugging is on
Ethernet CFM level 3 domain abc vlan 9 event debugging is on
Ethernet CFM level 2 domain abc-l2 vlan 9 event debugging is on
 Debug conditional parameters
Router1# debug ethernet cfm all ?
domain Domain Name
evc Specify EVC
port DOWN service direction with no vlan association
vlan Service Vlan
<cr>
Router1# debug ether cfm events ?
domain Domain Name
evc Specify EVC
vlan Service Vlan
<cr>
Router1# debug ether cfm packets ?
domain Domain Name
evc Specify EVC
vlan Service Vlan
<cr>
 Diagnostic debugs – gather more detailed, non-service
specific information
Router1# debug ether cfm diagnostic ?
ais Ethernet CFM diagnostic ais information
events Ethernet CFM diagnostic event information
lck Ethernet CFM diagnostic lck information
mip-autocreate Ethernet CFM diagnostic MIP auto create information
packets Ethernet CFM diagnostic packet information
<cr>
 Can filter on “type” of packet – may be dependent on platform

implementations
Router1# debug ether cfm diagnostic packets ?
ais Ethernet CFM diagnostic packet ais information
cc Ethernet CFM diagnostic packet cc information
lb Ethernet CFM diagnostic packet lb information
lck Ethernet CFM diagnostic packet lck information
lt Ethernet CFM diagnostic packet lt information
<cr>
CFM Errors
1. Configuration Error
 Reception of a CCM with an incorrect MPID (i.e. duplicate value)
 Execute “show ethernet cfm error” command to check for Configuration errors
Sample Configuration and

“show ethernet cfm error” output included below
Topology - CE and PE routers connected back to back

CE PE
Configuration Error (Continued)
Sample configuration on CE and PE
PE#sh run int TenGigabitEthernet 8/0/0

CE#sh run int TenGigabitEthernet 3/0/1
Building configuration...
Building configuration... Current configuration : 123 bytes
Current configuration : 123 bytes !
! interface TenGigabitEthernet8/0/0
interface TenGigabitEthernet3/0/1 no ip address
no ip address mls qos trust dscp
mls qos trust dscp ethernet cfm mep domain r6 mpid 2000 vlan 100
ethernet cfm mep domain r6 mpid 2000 vlan 100 end
end
CE#sh ethernet cfm error

-------------------------------------------------------------------------------
MPID Domain Id Mac Address Type Id Lvl
MAName Reason Age
--------------------------------------------------------------------------------
2000 r6 001f.6c99.6ac0 BD-V 100 6 s6 Configuration Error 4s
PE#sh ethernet cfm error

--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
2000 r6 001a.a106.95c1 BD-V 100 6
s6 Configuration Error 1s
Configuration Error (Continued)
Here same mpid “2000” is configured on R1 and R2

Once mpid on R2 is corrected to 2500, cfm error should get cleared on R1 and MEP should come up fine
CE#sh ethernet cfm maintenance-points remote
--------------------------------------------------------------------------------
MPID Domain Name MacAddress IfSt PtSt
Lvl Domain ID Ingress
RDI MA Name Type Id SrvcInst
EVC Name Age
--------------------------------------------------------------------------------
2500 r6 001f.6c99.6ac0 Up Up
6 r6 Te3/0/1.100
- s6 BD-V 100 N/A
evc6 6s
Total Remote MEPs: 1

CE#
Cross-connect Error
 Reception of a CCM from a remote MEP with an incorrect MA

 Execute “show ethernet cfm error” command to check for cross-connect errors
Sample configuration, ‘show ethernet cfm error’ output included

below.
CE#sh running-config | b ethernet cfm domain r6 PE#sh running-config | b ethernet cfm domain r6
ethernet cfm domain r6 level 6 ethernet cfm domain r6 level 6
service s6 evc evc6 vlan 100 direction down service s5 evc evc6 vlan 100 direction down
continuity-check continuity-check
continuity-check interval 1m continuity-check interval 1m
! !
! PE#sh run int TeNGigabitEthernet 8/0/0
interface TenGigabitEthernet3/0/1 Building configuration...
no ip address Current configuration : 123 bytes
mls qos trust dscp !
ethernet cfm mep domain r6 mpid 2000 vlan 100 interface TenGigabitEthernet8/0/0
end no ip address
mls qos trust dscp
ethernet cfm mep domain r6 mpid 2500 vlan 100
end
Cross-Connect Error (Continued)
CE#sh ethernet cfm maintenance-points remote

CE#
--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
2500 r6 001f.6c99.6ac0 BD-V 100 6 s5 Crossconnect Error 22s

--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
2000 r6 001a.a106.95c1 BD-V 100 6 s6 Crossconnect Error 20s
PE#sh ethernet cfm maintenance-points remote
PE#
AIS Error
 AIS messages are generated to notify other cfm devices of the existence of the fault.
 Execute “show ethernet cfm error” command to check for AIS errors.
Shut PE interface
CE – AIS received on CE ad PE
--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
- r6 001a.a106.95c1 BD-V 100 6
s6 Receive AIS 5s

--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
- r6 001f.6c99.6ac0 BD-V 100 6
s6 Receive AIS 30s
RDI Error
 Reception of a CCM containing an RDI Flag bit set

 Execute “show ethernet cfm maintenance-points remote” output to check if RDI flag is set
Ex:
CE and PE routers connected back to back with parallel paths (one port is forwarding and the
other port is STP blocked)
Remote MEP Port State is displayed as blocked "Blck" on the Remote MEPs learnt on PE1 device and RDI
is set for the Remote MEPs learnt on CE1 device
CE1#sh ethernet cfm maintenance-points remote

--------------------------------------------------------------------------------
EVC Name Age
--------------------------------------------------------------------------------
7534 lev6 000a.8b3f.7812 Up Up
6 lev6 Po12
RDI sss3584 BD-V 3584 3584
3584 10s
RDI Error (Continued)
PE1#sh ethernet cfm maintenance-points remote

--------------------------------------------------------------------------------
EVC Name Age
--------------------------------------------------------------------------------
2998 lev6 00d0.013b.2c12 Up Blck
6 lev6 Po12
- sss2048 BD-V 2048 2048
2048 11s
Loop Trap Error
 Reception of its own CCM

 Execute “show ethernet cfm error” command to check for Loop Trap errors
In the case below, Loop Trap Error is generated as cc messages are received with same mpid and mac
address.
CE(config-if)#do sh ethernet cfm err

-------------------------------------------------------------------------------
Level Vlan MPID Remote MAC Reason Service ID
-------------------------------------------------------------------------------
5 711 550 1001.1001.1001 Loop Trap Error OUT
PE#sh ethernet cfm err
-------------------------------------------------------------------------------
Level Vlan MPID Remote MAC Reason Service ID
-------------------------------------------------------------------------------
5 711 550 1001.1001.1001 Loop Trap Error OUT
Caveats / Limitations
Caveats / Limitations
1.CFM D8.1 QinQ configuration on sub interface is not Supported
2.You can ping or traceroute to a MEP where Continuity Check (CC) is disabled.
However, you cannot use ping and traceroute for an down MEP on a STP
blocked port configured on either a supervisor port or a LAN port.
3.With lower CC intervals, CC packets would be transmitted in bursts. Mls rate

limiters should be configured appropriately to avoid flapping of remote MEPs
4.Port-mep Ping / Traceroute for native vlan on trunk port fails for LAN Cards.
5.802.3ah E-OAM - The remote-loopback TEST status not retained across

switchovers. Works with longer OAM timeout value greater than 10 secs
Caveats / Limitations (Continued)
6.Hardware EoMPLS is not supported
7.In order for CFM and PVST to work, Line cards and Supervisor cards need to
support 3 match registers
8.When 4K Xconnect sessions are coming up/going down its expected that data traffic
gets punted to RP during adjacency changes. We need to rate limit these packets
that are getting punted to RP. Please enable "mls rate-limit unicast ip icmp
unreachable no-route <>" to resolve this.
9.On 7600 we do not handle chassis_reload and single sup reloads in HA, we handle
only the component type reload, which is HA compliant. So in a HA its always
assumed that switchover is going to take place if the active rp goes down. Dying
gasp is not sent in a HA system on reload.
CFM D8.1 Scalability Supported numbers
 100 MEP at 100msec CC interval
 1000 MEP at 1 sec CC interval
 6K Up MEP per box at 10 sec CC interval
 8K Down MEP per box at 10 sec CC interval
 2K MEPs per box for CFMoVFI
 8k MEP’s supported on EVC Xconnect
References
References
 Ethernet cfm D8.1 PI TOI - EDCS 702785

 TSG: http://zed.cisco.com/confluence/display/TSG/CFM
 PRD : CFM D8.1 , EDCS – 634612
 Aliases: c7600-cfm-dev
c7600-cfm-devtest
7600-cfm-queries
 CFM 802.1ag Project Webpage
http://wwwin-
eng.cisco.com/Eng/IOS/NSETC/WWW/802.1ag_Draft_8.1_CFM/
Q&A
Backup slides
LOC Alarm Suppression
 Without AIS, a MEP would report Loss of Continuity (LOC) for each of its
remote MEPs upon timer expiration
 With AIS, if a MEP receives AIS from the network, it suppresses LOC
alarms from peer MEPs
LOC 1
LOC 3 Network outage
LOC 4 2 AIS defect 2
LOC 1
LOC 2 AIS
mpid = 1 LOC 4 mpid = 1 AIS defect
LOC 2
X 3
AIS
X AIS
3
LOC 3 AIS
LOC 4 AIS defect
4 LOC 1 4
LOC 2
LOC 3 AIS defect
WITHOUT AIS WITH AIS

Timer-driven Event-driven
LOC notification AIS notification
Enable CFM
Router(config)# ethernet cfm global
CFM Domain Level X
UNI UNI
Configure Global parameters/attributes (optional)

Router(config)# ethernet cfm traceroute cache [size entries | max-hold-time minutes]
Router(config)# alarm notification { all | mac-remote-error-xcon | remote-error-xcon
| error-xcon | xcon | none }
CFM Domain Level X
UNI UNI
Configure Global default MIP auto-creation policy (optional)

Router(config)# ethernet cfm mip auto-create level level-id {vlan <vlan | vlan-range> |
evc evc-name }
CFM Domain Level X
UNI UNI
Service Provisioning (cont.)
Configure Maintenance Association

Router(config-ecfm)# service { short-ma-name | number MA-number | vlan-id
primary-vlan-id | vpn-id vpn-id } {vlan vlan-id | port | evc evc-name }
CFM Domain Level X
UNI UNI
Configure per-service parameters

Router(config-ecfm-srv)# continuity-check
Router(config-ecfm-srv)# continuity-check interval CC-interval (optional)
Router(config-ecfm-srv)# continuity-check loss-threshold threshold (optional)
Router(config-ecfm-srv)# maximum meps value (optional)
CFM Domain Level X
UNI
UNI
Network Provisioning (cont.)
Configure CFM Domains
Router(config)# ethernet cfm domain domain-name level level-id
CFM Domain Level X
UNI UNI
Configure per-Domain parameters (optional)

Router(config-ecfm)# id [ null | dns DNS-name | mac-address domain-number ]
Router(config-ecfm)# mep archive-hold-time minutes
Router(config-ecfm)# mip auto-create [ lower-mep-only ]
Router(config-ecfm)# sender-id chassis
CFM Domain Level X
UNI UNI
Configure and Enable Static Remote MEP Check – 1AG (optional)
Router(config-ecfm-srv)# continuity-check static rmep
Router(config-ecfm-srv)# mep mpid mpid
Router(config-ecfm-srv)# …
CFM Domain Level X
UNI UNI
Configure and Enable Crosscheck – D1 functionality (optional)

Router(config)# ethernet cfm mep crosscheck start-delay delay
Router(config-ecfm-srv)# mep mpid id
Router(config-ecfm-srv)# …
Router# ethernet cfm mep crosscheck {enable | disable} domain domain-name
{vlan {vlan-id | any | vlan-id-vlan-id [,vlan-id-vlan-id] } | port | evc evc-name }
CFM Domain Level X
UNI UNI
Configure MEPs
Router(config-if)# ethernet cfm mep domain domain-name mpid id vlan
vlan-id
CFM Domain Level X
UNI UNI
Configure per-MEP parameters (optional)

Router(config-if-ecfm-mep)# cos cos-value
Router(config-if-ecfm-mep)# alarm notification { all | mac-remote-
error-xcon | remote-error-xcon | error-xcon | xcon | none }
CFM Domain Level X
UNI UNI
Configure manual MIP for vlan (optional)

Router(config-if)# ethernet cfm mip level level-id [vlan vlan-range]
CFM Domain Level X
UNI UNI
Configure manual MIP for evc (optional)

Router(config-if-srv)# cfm mip level level-id
CFM Domain Level X
UNI UNI
Enable Cisco SNMP Traps – D1 (optional)

Router(config)# snmp-server enable traps ethernet cfm cc [mep-up | mep-
down | config | loop | cross-connect]
Router(config)# snmp-server enable traps ethernet cfm crosscheck [ mep-
unknown | mep-missing | service-up]
CFM Domain Level X
UNI UNI
CFMPAL – Behavior with STP Blocked Ports
CC messages - Up MEP with STP on same port
MEP Level M
B B
A C A C
X X
CC Level L CC Level N
X
X X
On Port A On Port A
L < M STP Filter N < M Drop
L = M STP Filter N = M Cataloged and terminate
L > M STP Filter N > M STP Filter
CC messages - Up MEP with STP on remote port
MEP Level M
B B
A C A C
X X
X X
X X
On Port A On Port C
L < M Drop N < M STP Filter
L = M Drop N = M STP Filter
L > M Pass thru transparently N > M STP Filter
On Port C
L > M STP Filter
CC message - Down MEP with STP on same port
MEP Level M
B B
A C A C
X X
X
X X
On Port A On Port A
L = M Cataloged & terminate N = M STP Filter
CC message - Down MEP with STP on remote port
MEP Level M
B B
A C A C
X X
X
X X
On Port A On Port C
L= M Cataloged & terminate N = M STP Filter
L > M Pass thru transparently N > M STP Filter
On Port C
L > M STP Filter
CC message - MIP with STP on same port and MIP
filtering enabled
MIP Level M
B B
A C A C
X X
X X
X X
On Port A On Port A
L < M Drop N < M Drop
L = M Cataloged & STP Filter N = M Cataloged & STP Filter
Deploying Carrier Ethernet OAM
Y.1731 AIS/RDI Operational Scenario
CE Access Aggregation Aggregation Access CE
CFM
OAM protocol positioning
Y.1731 AIS/RDI Operational Scenario (Cont.)
Failure scenario: Network failure
CE Access Aggregation Aggregation Access CE
X
Interface
Failure
SMEPs enter AIS

defect state
SMEP AIS syslog
AIS AIS
AIS transmission in
opposite direction
Local MEPs enter

AIS defect state
MEP AIS syslog
CCM CCM
Local MEPs:
suppress LOC alarms (if configured)
send CCMs with RDI ON
CE 11 uPE 11 AGG 11 Eth0/1 AGG 31 uPE 31 CE 31
X
AGG11(config)#int ethernet0/1
AGG11(config-if)#shutdown
Interface
enters AIS AGG11#
defect
*May 2 00:15:43.872: %E_CFM-6-ENTER_AIS_INT: Interface Ethernet0/1 enters AIS
state defect condition for Down direction
*May 2 00:15:45.888: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to
administratively down
*May 2 00:15:46.988 : %LINEPROTO-5-UPDOWN: Line protocol on Interface
Ethernet0/1, changed state to down
AGG11#show ethernet cfm smep interface ethernet0/1

SMEP Settings:
--------------
Interface: Ethernet0/1
LCK-Status: Enabled
LCK Period: 60000 (ms)
Level to transmit LCK: Default
AIS-Status: Enabled
AIS Period: 60000 (ms)
Level to transmit AIS: Default
Defect Condition: AIS
X
Local MEP
enters AIS
defect UPE11#
state *May 2 00:15:44.164: %E_CFM-6-ENTER_AIS: local mep with mpid 1100 level 4
id 100 dir U Interface Ethernet0/0 enters AIS defect condition
UPE11#show ethernet cfm error

--------------------------------------------------------------------------------
MAName Reason Age
--------------------------------------------------------------------------------
3100 PROVIDER_DOMAIN aabb.cc00.0599 BD-V 100 4
customer_100_provider Lifetime Timer Expired 348s
- PROVIDER_DOMAIN aabb.cc00.0399 BD-V 100 4
customer_100_provider Receive AIS 51s
Error DB: CFM MAC

- Rmep timeout address of
- Incoming AIS AGG11
X
Upon arrival
of AIS, local
MEP: UPE11#show ethernet cfm maintenance-points local detail domain PROVIDER_DOMAIN
Local MEPs:
----------
MPID: 1100
DomainName: PROVIDER_DOMAIN
Level: 4
- sets RDI on Direction: Up
outgoing Vlan: 100
Interface: Et0/0
CCMs CC-Status: Enabled
CC Loss Threshold: 2
MAC: aabb.cc00.0299
(snip)
Defect Condition: AIS
presentRDI: TRUE
- suppresses AIS-Status: Enabled
AIS Period: 60000(ms)
LOC alarms AIS Expiry Threshold: 3.5
Level to transmit AIS: Default
for rMEPs Suppress Alarm configuration: Enabled
Suppressing Alarms: Yes
(snip)
AGG11(config-if)#no shutdown
Upon
interface AGG11#
recovery, *May 2 00:41:39.803: %LINK-3-UPDOWN: Interface Ethernet0/1, changed state
to up
interface and
MEP exit AIS *May 2 00:41:40.815: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Ethernet0/1, changed state to up
defect state
*May 2 00:41:40.815: %E_CFM-6-EXIT_AIS_INT: Interface Ethernet0/1 exited
AIS defect condition for Down direction
UPE11#
*May 2 00:41:38.163: %E_CFM-6-EXIT_AIS: local mep with mpid 1100 level 4
id 100 dir U Interface Ethernet0/0 exited AIS defect condition
*May 2 00:41:38.163: %E_CFM-6-REMOTE_MEP_UP: Continuity Check message is

received from a remote MEP with mpid 3100 evc customer_100_provider@100
vlan 100 MA name customer_100_provider domain PROVIDER_DOMAIN interface
status Up event code Returning.
Deploying AIS
Network Redundancy considerations
No Redundancy Redundancy No Redundancy
1st Failure: primary path

CE/NID/Access CE/NID/Access
X
X MEN X
UNI failure X UNI failure
2nd Failure: backup path
MEN cloud that includes

portions with L2 network redundancy
(e.g. using STP, REP, RPR)
Deploying AIS
Network Redundancy considerations (cont.)
CE/NID/Access AIS AIS

CE/NID/Access
X MEN
UNI failure
UNI Recommendation: CE/NID Recommendation:

Enable AIS-Tx on UNI links Disable AIS LOC alarm
suppression on MEPs
(opt. for mp services)
Deploying AIS
1st Failure:
primary path
CE/NID/Access CE/NID/Access
AIS
X AIS
MEN
X
2nd Failure: CE/NID Recommendation:
CE/NID Recommendation: backup path Disable AIS LOC alarm
Disable AIS LOC alarm suppression on MEPs
suppression on MEPs (opt. for mp services)
(opt. for mp services) MEN Recommendation:
Disable AIS-Tx on NNI links
Enable AIS-Tx on MEPs
Deploying AIS
 MEN Recommendation - or portions of the network

where there is redundancy
 Disable AIS-transmission on interfaces in the MEN
where redundancy is present
 Enable AIS-transmission on MEPs configured on UNIs
(or interfaces with no redundancy)
 This option allows the MEPs to generate AIS PDUs
towards Access/NID/CE device in case of CC-detected
error conditions
Deploying AIS
 UNI Recommendation - or portions of the network

where there is no redundancy
 Enable AIS-transmission on UNI interfaces
 Allows for an event-driven mechanism to signal UNI
(link) failures to remote MEPs
Unambiguous and ideal for P2P services
Ambiguous for MP services. Incoming AIS at NID/CPE can be
used to trigger automatic ping to all the remote MEPs (in order
to isolate the problem) at the Access/NID/CE device
Deploying AIS
 CE / NID Recommendation
 Goal is to minimize AIS ambiguity (either due to
Multipoint service scenarios or Network Redundancy)
 For P2P services:
Incoming AIS is an unambiguous signal that the service is
broken (either due to MEN or remote UNI failure)
 For MP services:
Incoming AIS is ambiguous for both MEN or remote UNI failures
Disable AIS LOC alarm suppression on MEP
Incoming AIS can be used to trigger automatic
Loopback/Linktrace to all the remote MEPs (in order to isolate
the problem)
Deploying AIS
Ambiguity considerations for MP services
 ETH-AIS Ambiguity for Multipoint services

Upon reception of a frame with ETH-AIS information, the MEP
will suppress alarms for all peer MEPs whether there is still
connectivity or not. For multipoint ETH connectivity a MEP
cannot determine the associated subset of its peer MEPs for
which it should suppress alarms since the received AIS PDU
does not contain that information
 ETH-AIS for Point-to-point services

For a point-to-point ETH connection, a MEP has only a single
peer MEP. Therefore, there is no ambiguity regarding the peer
MEP for which it should suppress alarms when it receives the
ETH-AIS information
Deploying AIS
Ambiguity considerations due to Network Redundancy
 Excerpt from ITU Y.1731:

“(…) Due to independent restoration capabilities provided within
the Spanning Tree Protocol (STP) environments, ETH-AIS is
not expected to be applied in the STP environments (…)”
 The problem is that AIS generation at an smep is

independent (and unaware) of protection mechanisms
 For most cases, we can assume that Layer 2
convergence is faster that CCM timeout (e.g. when
using CCM = 1 or 10 sec, timeout = 3.5 or 35 sec)
CFMoL2VFI: Datapath Concepts
 Imposition and disposition is done on line card
=> core-facing line card should be an intelligent one
 CFM messages follow L2VFI forwarding rules:
- packet ingress from core does not go back to core
- packet ingress from spoke goes to core and other spokes
- packet ingress on a VC never goes back on the same VC
 SP is unaware of VFI
=> CFM DB for l2 vfi is not populated on SP
 In egress path, when RP sends out a packet (to linecards), it
encapsulates the packet with a special shim header (ethertype 0x8842)
to indicate how to forward a packet
 Parameters of interest:
- PAK_L3_VPLS_SPLIT_HORIZON flag (set if packet came from core)
- shim.direction (send only to core VCs or all VCs)
- shim.sub_feature = L2VFI
- dbus.dont_forward = 1 (prevents flooding to LAN port ASICs)
- dbus.flood = 1 (flood on vlan, prevents EARL lookup)
- dbus.src_index (prevents to go back on VC it ingressed from)

CFM Tac Toi1

Uploaded by

Copyright:

Available Formats

CFM Tac Toi1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CFM Tac Toi1

Uploaded by

Copyright:

Available Formats

What are maintenance domains and how are they used?

What are maintenance domains and how are they used?

What are maintenance associations and how do they monitor connectivity?

What are maintenance associations and how do they monitor connectivity?

802.

1AG – Ethernet Service

1. IEEE 802.1ag Overview

 CFM frames are distinguishable by Ether-Type 89-02

 Defined by Operational/Contractual Boundaries

 Monitors connectivity of a particular service instance in a given MD

MEP MEP MEP MEP

 Maintenance Association End Point (MEP)

 Applicability of UP/DOWN DOWN MEP

MEPs in switches: Bridge 1 Bridge 2

UP MEPs are commonly Monitored area

Port Port Port Port

MEP MIP MIP MEP

 Maintenance Domain Intermediate Point (MIP)

MEP MIP MIP MEP

 Used for Fault Detection and Notification

1 1 1. Loopback Message (LBM)

 Used for Fault Verification—Ethernet Ping

 Used for Path Discovery and Fault Isolation—Ethernet Traceroute

 Summary of CFM PDUs defined per protocol and type

1. Run Connectivity Check to proactively detect a

CFM (Global Attributes)

2. Define global CFM parameters 5. Service Provisioning

(Type, UNIs, VLANs etc.) policies (or manually Traps

3. Configure CFM 802.3ah (UNI)

1. Global Configuration MIP

3. MIP 1. Global Configuration

 Cisco-defined MIB (CISCO-ETHER-CFM-MIB)

Trap Type Object

 Cisco-defined MIB (CISCO-ETHER-CFM-MIB)

Trap Type Object

MEP Down (code:

Reception of its own CCM Loop

Discovery of a remote MEP for the first time

As part of the D8.1 implementation , we support the following in SRE

 Encapsulation of locally sourced CFM traffic is the SAME as the

CCM – Continuity Check Message

MD ethernet cfm domain <name> level <level>

MA service <name/num/id> evc <evc-name> [direction down ]

EFP Encapsulation encapsulation …

MD ethernet cfm domain <name> level <level>

MA service <name/num/id> evc <evc-name> [direction down ]

EVC ethernet evc <evc-name>

EFP Encapsulation encapsulation …

MD ethernet cfm domain <name> level <level>

MA service <name/num/id> evc <evc-name> [direction down ]

EFP Encapsulation encapsulation …

CFM Encapsulation cfm encapsulation …

MD ethernet cfm domain <domain-name> level <domain-level>

MA service <name/num/id> evc <evc-name>

EFP service instance <efp-id> ethernet <evc-name>

EFP Encapsulation encapsulation …

CFM Encapsulation cfm encapsulation …

 Ability to monitor end-to-end Ethernet connectivity faults over

MD ethernet cfm domain <name> level <level>