Example Of Ethernet Oam Connectivity Fault Management Configuration - Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual

Complete Software Guide for Junos
Related
Documentation

Example of Ethernet OAM Connectivity Fault Management Configuration

4078
®
OS for EX Series Ethernet Switches, Release 10.4
In a CFM maintenance domain, each service instance is called a maintenance association.
A maintenance association can be thought of as a full mesh of maintenance association
endpoints (MEPs) having similar characteristics. MEPs are active CFM entities generating
and responding to CFM protocol messages. There is also a maintenance intermediate
point (MIP), which is a CFM entity similar to the MEP, but more passive (MIPs only respond
to CFM messages).
Each maintenance domain is associated with a maintenance domain level from 0 through
7. Level allocation is based on the network hierarchy, where outer domains are assigned
a higher level than the inner domains. Configure customer end points to have the highest
maintenance domain level. The maintenance domain level is a mandatory parameter
that indicates the nesting relationships between various maintenance domains. The level
is embedded in each CFM frame. CFM messages within a given level are processed by
MEPs at that same level.
To enable CFM on an Ethernet interface, you must configure maintenance domains,
maintenance associations, and maintenance association end points (MEPs). Figure 97
on page 4078 shows the relationships among maintenance domains, maintenance
association end points (MEPs), and maintenance intermediate points (MIPs) configured
on a switch.
Figure 97: Relationship Among MEPs, MIPs, and Maintenance Domain
Levels
Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure) on page 4082
Junos OS Network Interfaces Configuration Guide
Example: Configuring Ethernet OAM Connectivity Fault Management on EX Series
Switches on page 4079
Copyright © 2010, Juniper Networks, Inc.