Ethernet Cfm; Figure 67: Relationship Of Meps, Mips, And Maintenance Domain Levels - Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

JUNOS 10.1 Network Interfaces Configuration Guide
These capabilities allow operators to offer binding service-level agreements (SLAs)
and generate new revenues from rate- and performance-guaranteed service packages
that are tailored to the specific needs of their customers.

Ethernet CFM

The IEEE 802.1ag standard for connectivity fault management (CFM) defines
mechanisms to provide for end-to-end Ethernet service assurance over any path,
whether a single link or multiple links spanning networks composed of multiple
LANs.
For Ethernet interfaces on M320, MX Series, and T Series routers, JUNOS Software
supports the following key elements of the Ethernet CFM standard:
In a CFM environment, network entities such as network operators, service providers,
and customers may be part of different administrative domains. Each administrative
domain is mapped into one maintenance domain. Maintenance domains are
configured with different level values to keep them separate. Each domain provides
enough information for the entities to perform their own management and end-to-end
monitoring, and still avoid security breaches.
Figure 67 on page 740 shows the relationships among the customer, provider, and
operator Ethernet bridges, maintenance domains, maintenance association end
points (MEPs), and maintenance intermediate points (MIPs).

Figure 67: Relationship of MEPs, MIPs, and Maintenance Domain Levels

740
Ethernet Frame Delay Measurements Overview
Fault monitoring using the IEEE 802.1ag Ethernet OAM Continuity Check protocol
Path discovery and fault verification using the IEEE 802.1ag Ethernet OAM
Linktrace protocol
Fault isolation using the IEEE 802.1ag Ethernet OAM Loopback protocol