limitation includes the iterator support for other measurement types such as loss,
statistical frame loss, and two-way delay. A new iterator type, SLM, is added to support
ETH-SLM. The total number of SLA iterators that you can configure in the system is
equal to the total number of iterations supported in the system.
•
For on-demand SLM, the minimum period between two SLM requests is 100
milliseconds.
•
For proactive SLM, the minimum period between two SLM requests is 10 milliseconds
for distributed mode and 100 milliseconds for non-distributed mode.
•
ETH-SLM frames are always marked as drop-ineligible in compliance with the ITU-T
Y.1731 standard.
Related
Documentation
Ethernet Synthetic Loss Measurement Overview on page 1140•
• Transmission of ETH-SLM Messages on page 1141
• Format of ETH-SLM Messages on page 1144
• Scenarios for Configuration of ETH-SLM on page 1147
• Managing ETH-SLM Statistics and ETH-SLM Frame Counts on page 1148
• Starting a Proactive ETH-SLM Session on page 1153
• Starting an On-Demand ETH-SLM Session on page 1156
• Troubleshooting Failures with ETH-SLM
• Ethernet Interfaces Feature Guide for Routing Devices
Scenarios for Configuration of ETH-SLM
ETH-SLM measures near-end and far-end frame loss between two MEPs that are part
of the same MEG level. You can configure ETH-SLM to measure synthetic loss for both
upward-facing or upstream MEP and downward-facing or downstreamMEP. This section
describes the following scenarios for the operation of ETH-SLM:
Upstream MEP in MPLS Tunnels
Consider a scenario in which a MEP is configured between the user network interfaces
(UNIs) of two MX Series routers, MX1 and MX2, in the upstream direction. MX1 and MX2
are connected over an MPLS core network. ETH-SLM measurements are performed
between the upstream MEP in the path linking the two routers. Both MX1 and MX2 can
initiate on-demand or proactive ETH-SLM, which can measure both far-end and near-end
loss at MX1 and MX2, respectively. The two UNIs are connected using MPLS-based Layer
2 VPN virtual private wire service (VPWS).
Downstream MEP in Ethernet Networks
Consider a scenario in which a MEP is configured between two MX Series routers, MX1
and MX2, on the Ethernet interfaces in the downstream direction. MX1 and MX2 are
connected in an Ethernet topology and downstream MEP is configured toward the
1147Copyright © 2017, Juniper Networks, Inc.
Chapter 34: Configuring Operations, Administration, and Management (OAM)