Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

close
keyboard_arrow_left
Network Management and Monitoring Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Introduction to OAM Link Fault Management (LFM)

date_range 19-Dec-24

This section describes the Operation, Administration, and Management (OAM) of link fault management (LFM).

Use Feature Explorer to confirm platform and release support for specific features.

Review the Platform-Specific OAM LFM Behavior section for notes related to your platform.

Configure Ethernet 802.3ah OAM

The IEEE 802.3ah standard for Operation, Administration, and Management (OAM) provides a specification for Ethernet in the first mile (EFM) connectivity. EFM defines how Ethernet can be transmitted over new media types using new Ethernet physical layer (PHY) interfaces. You can configure IEEE 802.3ah OAM on Ethernet point-to-point direct links or links across Ethernet repeaters. The IEEE 802.3ah OAM standard meets the requirement for OAM capabilities as Ethernet moves from being solely an enterprise technology to being a WAN and access technology, as well as being backward-compatible with existing Ethernet technology.

For Ethernet interfaces capable of running at 100 Mbps or faster, the IEEE 802.3ah OAM standard is supported on numerous Juniper Networks routers and switches. This topic describes configuration support for IEEE 802.3ah OAM features on routers.

To configure 802.3ah OAM support for Ethernet interfaces, include the oam statement at the [edit protocols] hierarchy level:

content_copy zoom_out_map
oam {
    ethernet {
        link-fault-management {
            interfaces {
                interface-name {
                    pdu-interval interval;
                    link-discovery (active | passive);
                    pdu-threshold count;
                }
            }
        }
    }
}

You can configure threshold values for fault events that trigger the sending of link event TLVs when the values exceed the threshold. To set threshold values for fault events on an interface, include the event-thresholds statement at the [edit protocols oam ethernet link-fault-management interface] hierarchy level.

You can also configure OAM threshold values within an action profile and apply the action profile to multiple interfaces. To create an action profile, include the action-profile statement at the [edit protocols oam ethernet link-fault-management] hierarchy level.

You can configure Ethernet OAM either on an aggregate interface or on each of its member links. However, we recommend that you configure Ethernet OAM on the aggregate interface, and this will internally enable Ethernet OAM on the member links.

To view OAM statistics, use the show oam ethernet link-fault-management operational mode command. To clear OAM statistics, use the clear oam ethernet link-fault-management statistics operational mode command. To clear link-fault management state information and restart the link discovery process on Ethernet interfaces, use the clear oam ethernet link-fault-management state operational mode command. For more information about these commands, see the CLI Explorer.

To enable IEEE 802.3ah OAM support, include the interface statement at the [edit protocols oam ethernet link-fault-management] hierarchy level:

content_copy zoom_out_map
[edit protocols oam ethernet link-fault-management interface interface-name]

When you enable IEEE 802.3ah OAM on a physical interface, the discovery process is automatically triggered.

Platform-Specific OAM LFM Behavior

Use Feature Explorer to confirm platform and release support for specific features.

Use the following table to review platform-specific behaviors for your platform.

Platform Difference

ACX Series

  • ACX Series routers that support LFM have the following limitations:

    • ACX5096 and ACX5048 routers do not support Dying-gasp.

    • ACX Series routers support the receipt of dying-gasp packets, but cannot generate them.

MX Series

  • MX Series routers that support LFM have the following limitations:

    • OAM configurations do not support Ethernet running on top of a Layer 2 protocol, such as Ethernet over ATM.

    • The 10-Gigabit Ethernet LAN/WAN PIC with SFP+ doesn't support remote loopback.

PTX Series

  • PTX Series routers that support LFM have the following limitations:

    • OAM configurations do not support Ethernet running on top of a Layer 2 protocol, such as Ethernet over ATM.

    • The 10-Gigabit Ethernet LAN/WAN PIC with SFP+ doesn't support remote loopback.

  • PTX Series routers support the following IEEE 802.3ah OAM features at the physical interface level:

    • Discovery and link monitoring

    • Fault signaling and detection

    • Periodic packet management (PPM) processing

    • Action profile support

    • Graceful Routing Engine switchover (GRES)

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
17.3R1
Starting in Junos OS Release 17.3R1, the Ethernet link fault management daemon (lfmd) runs on the backup Routing Engine when graceful Routing Engine switchover (GRES) is configured.
external-footer-nav