- 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
Example: Configure Ethernet CFM on Bridge Connections
In this example, both the customer and service provider are running Ethernet CFM over a simple bridge network. The network is shown in Figure 1. The customer has configured Ethernet CFM on MX Series routers L2-CE1 and L2-CE2. The service provider has configured Ethernet CFM on MX Series routers PE1 and PE2.
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.
The service provider is using CFM level 3 for the link between PE1 and PE2 and level 5 from one CE facing port to the other. The customer is using CFM level 7. The boundaries are marked with “up mep” and “down mep” CFM terminology in the figure.

Here are the configurations of CFM on the customer routers.
CFM on L2-CE1
[edit interfaces] ge-0/2/9 { vlan-tagging; unit 0 { vlan-id 2000; } } [edit protocols oam ethernet] connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 700 { interface ge-0/2/9.0; direction down; auto-discovery; } } } }
CFM on L2-CE2
[edit interfaces] ge-1/0/7 { vlan-tagging; unit 0 { vlan-id 2000; } } [edit protocols oam ethernet] connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site2 { continuity-check { interval 1s; } mep 800 { interface ge-1/0/7.0; direction down; auto-discovery; } } } }
Here are the configurations of CFM on the provider routers.
CFM on PE1
[edit interfaces] ge-5/0/9 { vlan-tagging; encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } ge-5/1/7 { vlan-tagging; encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } [edit bridge-domains] bridge-vlan2000 { domain-type bridge; vlan-id 2000; interface ge-5/0/9.0; interface ge-5/1/7.0; } [edit protocols oam ethernet connectivity-fault-management] maintenance-domain provider-outer { level 5; maintenance-association provider-outer-site1 { continuity-check { interval 1s; } mep 200 { interface ge-5/0/9.0; direction up; auto-discovery; } } } maintenance-domain provider-inner { level 3; maintenance-association provider-inner-site1 { continuity-check { interval 1s; } mep 200 { interface ge-5/1/7.0; direction down; auto-discovery; } } }
CFM on PE2
[edit interfaces] ge-5/1/7 { vlan-tagging; encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } ge-5/2/3 { vlan-tagging; encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } [edit bridge-domains] bridge-vlan2000 { domain-type bridge; interface ge-5/2/3.0; interface ge-5/1/7.0; } [edit protocols oam ethernet connectivity-fault-management] maintenance-domain provider-outer { level 5; maintenance-association provider-outer-site1 { continuity-check { interval 1s; } mep 100 { interface ge-5/2/3.0; direction up; auto-discovery; } } } maintenance-domain provider-inner { level 3; maintenance-association provider-inner-site1 { continuity-check { interval 1s; } mep 100 { interface ge-5/1/7.0; direction down; auto-discovery; } } }