close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
play_arrow Operation, Administration, and Management Features
- play_arrow Ethernet OAM and Connectivity Fault Management for Routers
- play_arrow Link Fault Management for Routers
- play_arrow Ethernet OAM Link Fault Management for Switches
- play_arrow Ethernet OAM Connectivity Fault Management for Switches
- play_arrow Ethernet Frame Delay
- play_arrow Ethernet Service OAM (ITU-TY.1731) for Routers
play_arrow Network Monitoring by using SNMP
play_arrow Remote Network Monitoring (RMON) with SNMP Alarms and Events
play_arrow Accounting Options
- Accounting Options Overview
- Configure Accounting Options, Source Class Usage and Destination Class Usage Options
play_arrow Monitoring Options
- play_arrow Interface Alarms
  - Alarm Overview
  - Example: Configure Interface Alarms
- play_arrow IP Monitoring
- play_arrow sFlow Monitoring Technology
- play_arrow Adaptive Sampling for Routers and Switches
  - Adaptive Sampling Overview
- play_arrow Packet Flow Accelerator Diagnostics Software
play_arrow Monitoring Common Security Features
play_arrow Performance Management
- Network Analytics
- Configure Hardware Resource Threshold Monitoring for Capacity Planning
play_arrow Port Mirroring
- play_arrow Port Mirroring and Analyzers
play_arrow System Log Messages
play_arrow Network Management and Troubleshooting
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)

date_range 15-Dec-23

arrow_backward

arrow_forward

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).

Note:

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:

Specify a name for the maintenance domain:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management]
user@switch# set maintenance-domain domain-name

Specify a format for the maintenance domain name. If you specify none, no name is configured:
- A plain ASCII character string
- A domain name service (DNS) format
- A media access control (MAC) address plus a two-octet identifier in the range 0 through 65,535
- none
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name]
user@switch# set name-format format
```
For example, to specify the name format as MAC address plus a two-octet identifier:
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name]
user@switch# set name-format mac+2oct
```
Configure the maintenance domain level, which is used to indicate the nesting relationship between this domain and other domains. Use a value from 0 through 7:
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name]
user@switch# set level level
```
Note:
The configuration display entries in the CFM maintenance domain list are "ordered by system" rather than "ordered by user."

Configuring the Maintenance Domain MIP Half Function

Note:

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:

content_copy zoom_out_map
[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:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name]
user@switch# set maintenance-association ma-name

Note:

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:

Enable the continuity check protocol:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name]
user@switch# set continuity-check

Specify the continuity check hold interval. The hold interval is the number of minutes to wait before flushing the MEP database if no updates occur. The default value is 10 minutes.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name continuity-check]
user@switch# set hold-interval number
```
Specify the CCM interval. The interval is the time between the transmission of CCMs. You can specify 10 minutes (10m), 1 minute (1m), 10 seconds (10s), 1 second (1s), 100 milliseconds (100ms), or 10 milliseconds (10ms).
Note:
On EX4600, QFX5200, and QFX5210 switches, CCM interval of less than 1 second is not supported.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name continuity-check]
user@switch# set interval number
```
Specify the number of CCMs (that is, protocol data units) that can be lost before the MEP is marked as down. The default number of protocol data units (PDUs) is 3.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name continuity-check]
user@switch# set loss-threshold number
```

Configuring a Maintenance Association End Point

To configure a maintenance association end point:

Specify an ID for the MEP. The value can be from 1 through 8191.

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name]
user@switch# set mep mep-id]

Enable maintenance endpoint automatic discovery if you want to have the MEP accept continuity check messages (CCMs) from all remote MEPs of the same maintenance association:
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id 
user@switch# set auto-discovery
```
You can specify that CFM packets (CCMs) be transmitted only in one direction for the MEP, that is, the direction be set as down so that CCMs are transmitted only out of (not into) the interface configured on this MEP.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id]
user@switch# set direction down
```
Specify the logical interface to which the MEP is attached. It can be either an access interface or a trunk interface. If you specify a trunk interface, the VLAN associated with that interface must have a VLAN ID.
Note:
You cannot associate an access interface that belongs to multiple VLANs with the MEP.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id]
user@switch# set interface interface-name
```
You can configure a remote MEP from which CCMs are expected. If autodiscovery is not enabled, the remote MEP must be configured under the mep statement. If the remote MEP is not configured under the mep statement, the CCMs from the remote MEP are treated as errors.
```
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id]
user@switch# set remote-mep mep-id
```

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:

Specify a name for an action profile:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management]
user@switch# set action-profile profile-name

Configure the action of the action profile:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name]
user@switch# set action interface-down

Configure one or more events under the action profile, the occurrence of which will trigger the corresponding action to be taken:
```
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name]
user@switch# set event event
```
See Junos OS Network Interfaces Configuration Guide

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:

Configure the linktrace path age timer. If no response to a linktrace request is received, the request and response entries are deleted after the age timer expires:
```
[edit protocols oam ethernet connectivity-fault-management]
user@switch# set linktrace age time
```

Configure the number of linktrace reply entries to be stored per linktrace request:

content_copy zoom_out_map
[edit protocols oam ethernet connectivity-fault-management]
user@switch# set linktrace path-database-size path-database-size

arrow_backward PREVIOUS Understand Ethernet OAM Connectivity Fault Management for Switches

NEXT arrow_forward Example: Configure Ethernet OAM Connectivity Fault Management on EX Series Switches

Network Management and Monitoring Guide

ON THIS PAGE

Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)

Creating the Maintenance Domain

Configuring the Maintenance Domain MIP Half Function

Creating a Maintenance Association

Configuring the Continuity Check Protocol

Configuring a Maintenance Association End Point

Configuring a Connectivity Fault Management Action Profile

Configuring the Linktrace Protocol

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Network Management and Monitoring Guide

ON THIS PAGE

Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)

Creating the Maintenance Domain

Configuring the Maintenance Domain MIP Half Function

Creating a Maintenance Association

Configuring the Continuity Check Protocol

Configuring a Maintenance Association End Point

Configuring a Connectivity Fault Management Action Profile

Configuring the Linktrace Protocol

Related Documentation

Stay in touch