Juniper Networks JUNOS OS 10.4 - Manual (Page 156)

2 357
3 344
4 332
5 319
6 306
7 294
8 281
9 269
10 255
Average one-way delay : 312 usec
Average one-way delay variation: 11 usec
Best case one-way delay : 255 usec
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.
Related
Documentation
Ethernet OAM •
• Ethernet Frame Delay Measurements on page 125
• Configuring MEP Interfaces to Support ETH-DM on page 128
• Triggering an ETH-DM Session on page 129
• Viewing ETH-DM Statistics on page 130
• Configuring Two-Way ETH-DM with Single-Tagged Interfaces on page 136
• Configuring ETH-DM with Untagged Interfaces on page 140
Example: Configuring Two-Way Ethernet Frame Delay Measurements with
Single-Tagged Interfaces
This example uses two MX Series routers: MX-1 and MX-2 . The configuration creates a
CFM down MEP session on a VLAN-tagged logical interface connecting the two ( ge-5/2/9
on Router MX-1 and ge-0/2/5 on Router MX-2 ).
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;
Copyright © 2013, Juniper Networks, Inc. 136
Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide