Example: Configure Ethernet OAM Connectivity Fault Management on EX Series Switches
Ethernet interfaces on EX Series switches and 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 example describes how to enable and configure OAM CFM on a Gigabit Ethernet interface:
Requirements
This example uses the following hardware and software components:
Junos OS Release 10.2 or later for EX Series switches
Two EX Series switches connected by a point-to-point Gigabit Ethernet link
Overview and Topology
CFM can be used to monitor the physical link between two switches. In the following example, two switches are connected by a point-to-point Gigabit Ethernet link. The link between these two switches is monitored using CFM.
Configuring Ethernet OAM Connectivity Fault Management on Switch 1
CLI Quick Configuration
To quickly configure Ethernet OAM CFM, copy the following commands and paste them into the switch terminal window:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain] set name-format character-string set maintenance-domain private level 0 set maintenance-association private-ma set continuity-check hold-interval 1s
Procedure
Step-by-Step Procedure
To enable and configure OAM CFM on switch 1:
Specify the maintenance domain name format:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain] user@switch1# set name-format character-string
Specify the maintenance domain name and the maintenance domain level:
[edit protocols oam ethernet connectivity-fault-management] user@switch1# set maintenance-domain private level 0
Create a maintenance association:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private] user@switch1# set maintenance-association private-ma
Enable the continuity check protocol and specify the continuity check hold interval:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private maintenance-association private-ma] user@switch1# set continuity-check hold-interval 1s
Configure the maintenance association end point (MEP):
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private maintenance-association private-ma] user@switch1# set mep 100 interface ge-1/0/1 auto-discovery direction down
Results
Check the results of the configuration.
[edit] user@switch1 > show
protocols {
oam {
ethernet {
connectivity-fault-management {
maintenance-domain private {
level 0;
maintenance-association private-ma {
continuity-check {
interval 1s;
}
mep 100 {
interface ge-1/0/1;
auto-discovery;
direction down;
}
}
}
}
}
Configuring Ethernet OAM Connectivity Fault Management on Switch 2
CLI Quick Configuration
To quickly configure Ethernet OAM CFM, copy the following commands and paste them into the switch terminal window:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain] set name-format character-string set maintenance-domain private level 0 set maintenance-association private-ma set continuity-check hold-interval 1s
Procedure
Step-by-Step Procedure
The configuration on switch 2 mirrors that on switch 2.
Specify the maintenance domain name format:
[edit protocols oam ethernet connectivity-fault-management] user@switch2# set name-format character-string
Specify the maintenance domain name and the maintenance domain level:
[edit protocols oam ethernet connectivity-fault-management] user@switch2# set maintenance-domain private level 0
Create a maintenance association:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private] user@switch2# set maintenance-association private-ma
Enable the continuity check protocol and specify the continuity check hold interval:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private maintenance-association private-ma] user@switch2# set continuity-check hold-interval 1s
Configure the maintenance association end point (MEP)
[edit protocols oam ethernet connectivity-fault-management maintenance-domain private maintenance-association private-ma] user@switch2# set mep 200 interface ge-0/2/5 auto-discovery direction down
Results
Check the results of the configuration.
[edit] user@switch2 > show
protocols {
oam {
ethernet {
connectivity-fault-management {
maintenance-domain private {
level 0;
maintenance-association private-ma {
continuity-check {
interval 1s;
}
mep 200 {
interface ge-0/2/5;
auto-discovery;
direction down;
}
}
}
}
}
Verification
To confirm that the configuration is working properly, perform these tasks:
Verifying That OAM CFM Has Been Configured Properly
Purpose
Verify that OAM CFM has been configured properly.
Action
Use the show oam ethernet connectivity-fault-management
interfaces detail command:
user@switch1# No link title detailSample Output
command-name
Interface name: ge-1/0/1.0, Interface status: Active, Link status: Up
Maintenance domain name: private, Format: string, Level: 0
Maintenance association name: private-ma, Format: string
Continuity-check status: enabled, Interval: 1ms, Loss-threshold: 3 frames
MEP identifier: 100, Direction: down, MAC address: 00:90:69:0b:4b:94
MEP status: running
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : yes
Cross-connect CCM received : no
RDI sent by some MEP : yes
Statistics:
CCMs sent : 76
CCMs received out of sequence : 0
LBMs sent : 0
Valid in-order LBRs received : 0
Valid out-of-order LBRs received : 0
LBRs received with corrupted data : 0
LBRs sent : 0
LTMs sent : 0
LTMs received : 0
LTRs sent : 0
LTRs received : 0
Sequence number of next LTM request : 0
Remote MEP count: 2
Identifier MAC address State Interface
2001 00:90:69:0b:7f:71 ok ge-0/2/5.0
Meaning
When the output displays that continuity-check status
is enabled and displays details of
the remote MEP, it means that connectivity fault management (CFM)
has been configured properly.