•
Business and service policies have been established.
•
EVC associated with CFM domain must be configured with the L2VFI interface command
◦
Before configuring CFM over L2VFI ensure EVC and Bridge Domain are configured.
◦
Bridge-domain under L2VFI must be configured prior to configuring CFM MEP
Information About Configuring Ethernet CFM
Ethernet CFM
IEEE CFM is an end-to-end per-service Ethernet layer OAM protocol that includes proactive connectivity
monitoring, fault verification, and fault isolation. End to end can be provider edge to provider edge (PE to
PE) or customer edge to customer edge (CE to CE).
Ethernet CFM is distinct from other metro-Ethernet OAM protocols by being an end-to-end technology. For
example, Multiprotocol Label Switching (MPLS), ATM, and SONET OAM help in debugging Ethernet wires
but are not always end to end. 802.3ah OAM is a single-hop and per-physical-wire protocol. It is not end to
end or service aware. Ethernet Local Management Interface (E-LMI) is confined between the user-end provider
edge (uPE) and CE and relies on CFM for reporting status of the metro-Ethernet network to the CE.
The benefits of Ethernet CFM are:
•
End-to-end service-level OAM technology
•
Reduced operating expense for service provider Ethernet networks
•
Competitive advantage for service providers
Benefits of Ethernet CFM
•
End-to-end service-level OAM technology
•
Reduced operating expense for service provider Ethernet networks
•
Competitive advantage for service providers
Maintenance Associations
An MA identifies a service that can be uniquely identified within a maintenance domain. There can be many
MAs within a domain. The MA direction is specified when the MA is configured. The short MA name must
be configured on a domain before MEPs can be configured.
The CFM protocol runs for a specific MA.
Carrier Ethernet Configuration Guide (Cisco ASR 920 Series)
248
Configuring Ethernet CFM
Information About Configuring Ethernet CFM
To Next Page
Loading...
Need help?
General
