Juniper EX9200 Features Manual page 25

Related
Documentation
Copyright © 2016, Juniper Networks, Inc.
}
protocol-down;
}
}
NOTE: Whenever link-fault management (LFM) with an action profile is
configured to mark the interface as down (by including the link-down
statement at the [edit protocols oam ethernet link-fault-management]
hierarchy level), the port is placed in the blocked state (STP state). In such
a state of the interface, data traffic is not transmitted out on that interface.
Because the connectivity-fault management (CFM) downstream
maintenance MEPs come up on blocked ports, the CFM sessions come up
properly. However, the interface is down and the interface status TLV does
not contain the correct status. Only if you configure the port status TLV, the
actual status of the port is reflected. The interface status TLV does not carry
the actual state of the port.
action-profile on page 47
IEEE 802.3ah OAM Link-Fault Management Overview on page 3
Configuring IEEE 802.3ah OAM Link-Fault Management on page 5
Enabling IEEE 802.3ah OAM Support on page 6
Configuring Link Discovery on page 16
Configuring the OAM PDU Interval on page 6
Configuring the OAM PDU Threshold on page 7
Configuring Threshold Values for Local Fault Events on an Interface on page 17
Disabling the Sending of Link Event TLVs on page 18
Detecting Remote Faults on page 18
Specifying the Actions to Be Taken for Link-Fault Management Events on page 19
Monitoring the Loss of Link Adjacency on page 12
Monitoring Protocol Status on page 13
Configuring Threshold Values for Fault Events in an Action Profile on page 10
Applying an Action Profile on page 10
Setting a Remote Interface into Loopback Mode on page 11
Enabling Remote Loopback Support on the Local Interface on page 15
Example: Configuring IEEE 802.3ah OAM Support on an Interface on page 21
Ethernet Interfaces Feature Guide for Routing Devices
Chapter 1: Configuring Ethernet OAM Link Fault Management
9