- 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
ON THIS PAGE
Example: Configure Ethernet CFM on Physical Interfaces
This example shows the configuration of Ethernet connectivity fault management (CFM) on physical interfaces.
Requirements
This example uses the following hardware and software components:
Junos OS Release 9.3 or later.
Overview
CFM can be used to monitor the physical link between two routers. This functionality is similar to that supported by the IEEE 802.3ah LFM protocol.
In Junos OS Release 9.3 and later, CFM also supports aggregated Ethernet interfaces. On interfaces configured on Modular Port Concentrators (MPCs) and Modular Interface Cards (MICs) on MX Series routers, CFM is not supported on untagged aggregated Ethernet member links. MPCs and MICs do support CFM on untagged and tagged aggregated Ethernet logical interfaces.
The configurations in this example are only partial examples of complete and functional router configurations. Do not copy these configurations and use them directly on an actual system.
Configuration
In the following example, two routers (Router 1 and Router 2) are connected by a point-to-point Gigabit Ethernet link. The link between these two routers is monitored using CFM. This is shown in Figure 1. The single boundary is a “down mep” in CFM terminology.

To configure Ethernet CFM on physical interfaces, perform these tasks:
CLI Quick Configuration
Router 1
Configure the interface and CFM:
[edit] interfaces ge-1/0/1 { unit 0 { family inet; } } 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; direction down; auto-discovery; } } } } } } }
The configuration on Router 2 mirrors that on Router 1, with the exception of the mep-id.
Router 2
Configure the interface and CFM:
[edit] interfaces ge-0/2/5 { unit 0 { family inet; } } 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; direction down; auto-discovery; } } } } } } }
To verify that the physical interface is configured correctly
for CFM, use the show interface
command. To verify the
CFM configuration, use one or more of the show oam ethernet connectivity-fault-management
commands listed in the CLI Explorer.