- play_arrow Overview
- play_arrow Network Monitoring by using SNMP
- SNMP Architecture and SNMP MIBs Overview
- Understand SNMP Implementation in Junos OS
- Configure SNMP in Junos OS
- Configure Options on Managed Devices for Better SNMP Response Time
- Enterprise Specific Utility MIB to Enhance SNMP Coverage
- Optimize the Network Management System Configuration for the Best Results
- Interfaces to Accept SNMP Requests
- Configure SNMP for Routing Instances
- Configure SNMP Remote Operations
- SNMP Traps
- SNMP Traps Supported by Junos OS
- Trace SNMP Activity
- Access Privileges for an SNMP Group
- Configure Local Engine ID on SNMPv3
- Configure SNMPv3
- Configure SNMPv3 Authentication Type and Encryption Type
- SNMPv3 Traps
- SNMPv3 Informs
- SNMP Communities
- MIB Views
- SNMP MIBs Supported by Junos OS and Junos OS Evolved
- Junos OS SNMP FAQs
- play_arrow Remote Network Monitoring (RMON) with SNMP Alarms and Events
- play_arrow Accounting Options
- play_arrow Monitoring Options
- play_arrow Interface Alarms
- play_arrow IP Monitoring
- play_arrow sFlow Monitoring Technology
- play_arrow Adaptive Sampling for Routers and Switches
- play_arrow Packet Flow Accelerator Diagnostics Software
-
- play_arrow Monitoring Common Security Features
- play_arrow Performance Management
- play_arrow Port Mirroring
- play_arrow Port Mirroring and Analyzers
- Port Mirroring and Analyzers
- Configuring Port Mirroring and Analyzers
- Configuring Port Mirroring Instances
- Configuring Port Mirroring on Physical Interfaces
- Configuring Port Mirroring on Logical Interfaces
- Configuring Port Mirroring for Multiple Destinations
- Configuring Port Mirroring for Remote Destinations
- Configuring Port Mirroring Local and Remote Analysis
- 1:N Port Mirroring to Multiple Destinations on Switches
- Example: Configure Port Mirroring with Family any and a Firewall Filter
- Monitoring Port Mirroring
- Configure Packet Mirroring with Layer 2 Headers for Layer 3 Forwarded Traffic
- Troubleshooting Port Mirroring
-
- play_arrow System Log Messages
- play_arrow Network Management and Troubleshooting
- Compressing Troubleshooting Logs from /var/logs to Send to Juniper Networks Technical Support
- Monitoring and Troubleshooting
- Troubleshooting System Performance with Resource Monitoring Methodology
- Configuring Data Path Debugging and Trace Options
- Using MPLS to Diagnose LSPs, VPNs, and Layer 2 Circuits
- Using Packet Capture to Analyze Network Traffic
- On-Box Packet Sniffer Overview
- Troubleshooting Security Devices
- play_arrow Configuration Statements and Operational Commands
Remote Loopback for Link Fault Management
Use this topic to understand what happens when you set a remote interfaces in loopback mode and how to enable remote loopback. You can also learn how to enable nonstop routing for LFM.
Set a Remote Interface into Loopback Mode
You can configure the software to set the remote DTE into loopback mode on the following interfaces:
IQ2 and IQ2-E Gigabit Ethernet interfaces
Ethernet interfaces on the MX Series routers or EX Series switches
Junos OS can place a remote DTE into loopback mode (if remote-loopback mode is supported by the remote DTE). When you place a remote DTE into loopback mode, the interface receives the remote-loopback request and puts the interface into remote-loopback mode. When the interface is in remote-loopback mode, all frames except OAM PDUs are looped back without any changes made to the frames. OAM PDUs continue to be sent to the management plane and processed.
To configure remote loopback, include the remote-loopback
statement at the [edit protocol oam ethernet link-fault-management
interface interface-name]
hierarchy level:
[edit protocol oam ethernet link-fault-management interface interface-name] remote-loopback;
To take the remote DTE out of loopback mode, remove the remote-loopback
statement from the configuration.
See Also
Enable Remote Loopback Support on the Local Interface
You can allow a remote DTE to set a local interface into remote loopback mode on IQ2 and IQ2-E Gigabit Ethernet interfaces and all Ethernet interfaces on the MX Series routers and EX Series switches. When a remote-loopback request is sent by a remote DTE, the Junos OS places the local interface into loopback mode. When an interface is in loopback mode, all frames except OAM PDUs are looped back without any changes to the frames. OAM PDUs continue to be sent to the management plane and processed. By default, the remote loopback feature is not enabled.
To enable remote loopback, include the allow-remote-loopback
statement at the [edit protocol oam ethernet link-fault-management
interface interface-name negotiation-options]
hierarchy level:
[edit protocol oam ethernet link-fault-management interface interface-name negotiation-options] allow-remote-loopback;
Activation of OAM remote loopback may result in data frame loss.
See Also
Enable Nonstop Routing for Ethernet Link Fault Management on Backup Routers
Starting in Junos OS Release 17.3R1, the Ethernet link fault management daemon (lfmd) runs on the backup Routing Engine as well when graceful Routing Engine switchover (GRES) is configured. When the lfmd daemon runs on the backup Routing Engine as well, the link fault management states are kept in sync and so minimal effort is required by the lfmd daemon post switch over.
To enable Nonstop routing for Ethernet LFM on backup routers:
See Also
Example: Configure Ethernet LFM with Loopback Support
In this example, LFM is configured between provider edge (PE) router and the customer edge (CE) router. The PE router can put the CE router in remote loopback mode. This allows the PE to have all the traffic sent to the CE router looped back for diagnostics purposes, as shown in Figure 1.

To configure LFM between a PE router and a CE router:
Configure LFM loopback on the PE router:
content_copy zoom_out_map[edit] interfaces ge-1/0/0 { unit 0 { family inet { address 11.11.11.1/24; } } } protocols { oam { ethernet { link-fault-management { interface ge-1/0/0 { pdu-interval 1000; pdu-threshold 5; remote-loopback; } } } } }
Configure LFM loopback on the CE router:
content_copy zoom_out_map[edit] interfaces ge-1/1/0 { unit 0 { family inet { address 11.11.11.2/24; } } } protocols { oam { ethernet { link-fault-management { interface ge-1/1/0 { pdu-interval 1000; pdu-threshold 5; negotiation-options { allow-remote-loopback; } } } } } }
Note:If the
negotiation options allow-remote-loopback
statement on the CE router is deleted before removing the CE router from remote loopback mode, traffic flow between the PE router and CE router is affected. Hence, delete theremote-loopback
statement on the PE router before deleting thenegotiation-options allow-remote-loopback
statement on the CE router.
See Also
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.