Example: Configuring Two-Way Ethernet Frame Delay Measurements With Single-Tagged Interfaces - Juniper JUNOS OS 10.4 Manual

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide
Related
Documentation
Example: Configuring Two-Way Ethernet Frame Delay Measurements with
Single-Tagged Interfaces
130
2 357
3 344
4 332
5 319
6 306
7 294
8 281
9 269
10 255
Average one-way delay
Average one-way delay variation: 11 usec
Best case one-way delay
NOTE: When two systems are close to each other, their one-way delay values
are very high compared to their two-way delay values. This is because
one-way delay measurement requires the timing for the two systems to be
synchronized at a very granular level and MX Series routers do not support
this granular synchronization. However, two-way delay measurement does
not require synchronized timing, making two-way delay measurements more
accurate.
Ethernet OAM
Ethernet Frame Delay Measurements on page 119
Configuring MEP Interfaces to Support ETH-DM on page 122
Triggering an ETH-DM Session on page 123
Viewing ETH-DM Statistics on page 124
Configuring Two-Way ETH-DM with Single-Tagged Interfaces on page 130
Configuring ETH-DM with Untagged Interfaces on page 134
This example uses two MX routers:
down MEP session on a VLAN-tagged logical interface connecting the two (
Router and
MX-1 ge-0/2/5
NOTE: These are not complete router configurations.
Configuration on Router
MX-1
[edit]
interfaces {
ge-5/2/9 {
vlan-tagging;
unit 0 {
vlan-id 512;
: 312 usec
: 255 usec
and . The configuration creates a CFM
MX-1 MX-2
on Router ).
MX-2
:
ge-5/2/9
Copyright © 2012, Juniper Networks, Inc.
on