ON THIS PAGE
Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)
Ethernet interfaces on Juniper Networks EX Series Ethernet Switches and Juniper Networks Junos OS for EX Series switches support the IEEE 802.1ag standard for Operation, Administration, and Management (OAM). The IEEE 802.1ag specification provides for Ethernet connectivity fault management (CFM).
This feature is not supported on EX4300 switches on aggregated Ethernet (LAG) interfaces.
This topic describes these tasks:
Creating the Maintenance Domain
A maintenance domain comprises network entities such as operators, providers, and customers. To enable connectivity fault management (CFM) on an Ethernet interface, you must create a maintenance domains, maintenance associations, and MEPs.
To create a maintenance domain:
Configuring the Maintenance Domain MIP Half Function
MIP Half Function (MHF) is not supported on EX4600, QFX5200, and QFX5210 switches.
MIP Half Function (MHF) divides the maintenance association intermediate point (MIP) functionality into two unidirectional segments, improves visibility with minimal configuration, and improves network coverage by increasing the number of points that can be monitored. MHF extends monitoring capability by responding to loop-back and link-trace messages to help isolate faults. Whenever a MIP is configured, the MIP half function value for all maintenance domains and maintenance associations must be the same.
To configure the MIP half function:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] user@switch# set mip-half-function (none | default | explicit)
Creating a Maintenance Association
In a CFM maintenance domain, each service instance is called a maintenance association.
To create a maintenance association:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] user@switch# set maintenance-association ma-name
The configuration display entries in the CFM maintenance domain list are "ordered by system" rather than "ordered by user."
Configuring the Continuity Check Protocol
The continuity check protocol is used for fault detection by a maintenance association end point (MEP) within a maintenance association. The MEP periodically sends continuity check multicast messages. The receiving MEPs use the continuity check messages (CCMs) to build a MEP database of all MEPs in the maintenance association.
To configure the continuity check protocol:
Configuring a Maintenance Association End Point
To configure a maintenance association end point:
Configuring a Connectivity Fault Management Action Profile
You can configure an action profile and specify the action to be taken when any of the configured events occur. Alternatively, you can configure an action profile and specify default actions when connectivity to a remote MEP fails.
To configure an action profile:
Configuring the Linktrace Protocol
The linktrace protocol is used for path discovery between a
pair of maintenance points. Linktrace messages are triggered by an
administrator using the traceroute
command to verify the
path between a pair of MEPs under the same maintenance association.
Linktrace messages can also be used to verify the path between a MEP
and a MIP under the same maintenance domain.
To configure the linktrace protocol: