- 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 OAM Link Fault Management
Junos OS allows the Ethernet interfaces on these switches to support the IEEE 802.3ah standard for the Operation, Administration, and Maintenance (OAM) of Ethernet in access networks. The standard defines OAM link fault management (LFM). You can configure IEEE 802.3ah OAM LFM on point-to-point Ethernet links that are connected either directly or through Ethernet repeaters.
This example describes how to enable and configure OAM LFM on a Gigabit Ethernet interface:
Requirements
This example uses the following hardware and software components:
Junos OS Release 9.4 or later for EX Series switches
Two EX3200 or EX4200 switches connected directly
Overview and Topology
Junos OS switches allows the Ethernet interfaces on these switches to support the IEEE 802.3ah standard for the Operation, Administration, and Maintenance (OAM) of Ethernet in access networks. The standard defines OAM link fault management (LFM). You can configure IEEE 802.3ah OAM LFM on point-to-point Ethernet links that are connected either directly or through Ethernet repeaters.
Topology
This example uses two EX4200 switches connected directly. Before you begin configuring Ethernet OAM LFM on two switches, connect the two switches directly through a trunk interface.
Configuring Ethernet OAM Link Fault Management on Switch 1
CLI Quick Configuration
To quickly configure Ethernet OAM LFM, copy the following commands and paste them into the switch terminal window:
[edit protocols oam ethernet link-fault-management]
set interface ge-0/0/0
set interface ge-0/0/0 link-discovery active
set interface ge-0/0/0 pdu-interval 800
set interface ge-0/0/0 remote-loopback Procedure
Step-by-Step Procedure
To configure Ethernet OAM LFM on switch 1:
Enable IEEE 802.3ah OAM support on an interface:
content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch1# set interface ge-0/0/0
Specify that the interface initiates the discovery process by configuring the link discovery mode to
active:content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch1# set interface ge-0/0/0 link-discovery active
Set the periodic OAM PDU-sending interval (in milliseconds) to 800 on switch 1:
content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch1# set interface pdu-interval 800
Set a remote interface into loopback mode so that all frames except OAM PDUs are looped back without any changes made to the frames. Ensure that the remote DTE supports remote loopback mode. To set the remote DTE in loopback mode
content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch1# set interface ge-0/0/0.0 remote-loopback
Results
Check the results of the configuration:
[edit] user@switch1# show
protocols {
oam {
ethernet {
link-fault-management {
interface ge-0/0/0 {
pdu-interval 800;
link-discovery active;
remote-loopback;
}
}
}
}
Configuring Ethernet OAM Link Fault Management on Switch 2
CLI Quick Configuration
To quickly configure Ethernet OAM LFM on switch 2, copy the following commands and paste them into the switch terminal window:
[edit protocols oam ethernet link-fault-management ]
set interface ge-0/0/1
set interface ge-0/0/1 negotiation-options allow-remote-loopback
Procedure
Step-by-Step Procedure
To configure Ethernet OAM LFM on switch 2:
Enable OAM on the peer interface on switch 2:
content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch2# set interface ge-0/0/1
Enable remote loopback support for the local interface:
content_copy zoom_out_map[edit protocols oam ethernet link-fault-management] user@switch2# set interface ge-0/0/1 negotiation-options allow-remote-loopback
Results
Check the results of the configuration:
[edit]
user@switch2# show
protocols {
oam {
ethernet {
link-fault-management {
interface ge-0/0/1 {
negotiation-options {
allow-remote-loopback;
}
}
}
}
}
Verification
Verifying That OAM LFM Has Been Configured Properly
Purpose
Verify that OAM LFM has been configured properly.
Action
Use the show oam ethernet link-fault-management command:
user@switch1#
Sample Output
command-name
Interface: ge-0/0/0.0 Status: Running, Discovery state: Send Any Peer address: 00:19:e2:50:3b:e1 Flags:Remote-Stable Remote-State-Valid Local-Stable 0x50 Remote entity information: Remote MUX action: forwarding, Remote parser action: forwarding Discovery mode: active, Unidirectional mode: unsupported Remote loopback mode: supported, Link events: supported Variable requests: unsupported
Meaning
When the output displays the MAC address and the discover
state is Send Any, it means that OAM LFM has been configured
properly.
