32-2
Cisco ME 3800X and 3600X Switch Software Configuration Guide
OL-23400-01
Chapter 32 Configuring Ethernet OAM, CFM, and E-LMI
Understanding Ethernet CFM
The switch does not support:
•
CFM transparency in VPLS or EoMPLS pseudowires
•
Provider-edge E-LMI
•
CFM on bridge domains (supported on switchports only)
These sections contain conceptual information about Ethernet CFM:
•
CFM Domain, page 32-2
•
Maintenance Associations and Maintenance Points, page 32-3
•
CFM Messages, page 32-4
•
Crosscheck Function and Static Remote MEPs, page 32-5
•
SNMP Traps and Fault Alarms, page 32-5
•
Configuration Error List, page 32-5
•
IP SLAs Support for CFM, page 32-6
•
IP SLAs Support for CFM, page 32-6
CFM Domain
A CFM maintenance domain is a management space on a network that is owned and operated by a single
entity and defined by a set of ports internal to it, but at its boundary. You assign a unique maintenance
level (from 0 to 7) to define the hierarchical relationship between domains. The larger the domain, the
higher the level. For example, as shown in
Figure 32-1
, a service-provider domain would be larger than
an operator domain and might have a maintenance level of 6, while the operator domain maintenance
level is 3 or 4.
As shown in
Figure 32-2
, domains cannot intersect or overlap because that would require management
by more than one entity, which is not allowed. Domains can touch or nest (if the outer domain has a
higher maintenance level than the nested domain). Nesting domains is useful when a service provider
contracts with one or more operators to provide Ethernet service. Each operator has its own maintenance
domain and the service provider domain is a superset of the operator domains. Maintenance levels of
nesting domains should be communicated among the administrating organizations. CFM exchanges
messages and performs operations on a per-domain basis.
