Web Management Guide-R04

Table Of Contents
Chapter 13
| Basic Administration Protocols
Connectivity Fault Management
– 525 –
Figure 339: Configuring Interfaces for CFM
Configuring CFM
Maintenance Domains
Use the Administration > CFM (Configure MD) pages to create and configure a
Maintenance Domain (MD) which defines a portion of the network for which
connectivity faults can be managed. Domain access points are set up on the
boundary of a domain to provide end-to-end connectivity fault detection, analysis,
and recovery. Domains can be configured in a hierarchy to provide management
access to the same basic network resources for different user levels.
Command Usage
Configuring General Settings
Where domains are nested, an upper-level hierarchical domain must have a
higher maintenance level than the ones it encompasses. The higher to lower
level domain types commonly include entities such as customer, service
provider, and operator.
More than one domain can be configured at the same maintenance level, but a
single domain can only be configured with one maintenance level.
If MEPs (see "Configuring Maintenance End Points") or MAs (see "Configuring
CFM Maintenance Associations") are configured for a domain, they must first be
removed before you can remove the domain.
Maintenance domains are designed to provide a transparent method of
verifying and resolving connectivity problems for end-to-end connections. By
default, these connections run between the domain service access points
(DSAPs) within each MA defined for a domain, and are manually configured
(see "Configuring Maintenance End Points").
In contrast, MIPs are interconnection points that make up all possible paths
between the DSAPs within an MA. MIPs are automatically generated by the
CFM protocol when the MIP Creation Type is set to “Default” or “Explicit,” and
the MIP creation state machine is invoked (as defined in IEEE 802.1ag). The
default option allows MIPs to be created for all interconnection points within an
MA, regardless of the domains level in the maintenance hierarchy (e.g.,
customer, provider, or operator). While the explicit option only generates MIPs
within an MA if its associated domain is not at the bottom of the maintenance