21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Two-Way ETH-DM Frame Counts<br />

Each router counts the number of two-way ETH-DM frames sent and received:<br />

• For an initiator MEP, the router counts the number DMM frames transmitted, the number<br />

of valid DMR frames received, and the number of invalid DMR frames received.<br />

• For a responder MEP, the router counts the number of DMR frames sent.<br />

Each router stores ETH-DM frame counts in the CFM database. The CFM database stores<br />

CFM session statistics and, for interfaces that support ETH-DM, any ETH-DM frame<br />

counts. You can access the frame counts at any time by displaying CFM database<br />

information for <strong>Ethernet</strong> interfaces assigned to MEPs or for MEPs in CFM sessions.<br />

NOTE: For a given two-way <strong>Ethernet</strong> frame delay measurement, frame delay<br />

and frame delay variation values are available only at the router that contains<br />

the initiator MEP.<br />

Choosing Between One-Way and Two-Way ETH-DM<br />

One-way frame delay measurement requires that the system clocks at the initiator MEP<br />

and receiver MEP are closely synchronized. Two-way frame delay measurement does<br />

not require synchronization of the two systems. If it is not practical for the clocks to be<br />

synchronized, two-way frame delay measurements are more accurate.<br />

When two systems are physically close to each other, their one-way delay values are<br />

very high compared to their two-way delay values. One-way delay measurement requires<br />

that the timing for the two systems be synchronized at a very granular level, and MX<br />

Series routers currently do not support this granular synchronization.<br />

Restrictions for <strong>Ethernet</strong> Frame Delay Measurement<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

The following restrictions apply to the <strong>Ethernet</strong> frame delay measurement feature:<br />

• The ETH-DM feature is not supported on aggregated <strong>Ethernet</strong> interfaces or<br />

label-switched interface. (LSI) pseudowires.<br />

• Hardware-assisted timestamping for ETH-DM frames in the reception path is only<br />

supported for MEP interfaces on Enhanced DPCs and Enhanced Queuing DPCs in MX<br />

Series routers. For information about hardware-assisted timestamping, see “Guidelines<br />

for Configuring Routers to Support an ETH-DM Session” on page 253 and “Enabling the<br />

Hardware-Assisted Timestamping Option” on page 263.<br />

• <strong>Ethernet</strong> frame delay measurements can be triggered only when the distributed periodic<br />

packet management daemon (ppm) is enabled. For more information about this<br />

limitation, see “Guidelines for Configuring Routers to Support an ETH-DM Session” on<br />

page 253 and “Ensuring That Distributed ppm Is Not Disabled” on page 261.<br />

• You can monitor only one session at a time to the same remote MEP or MAC address.<br />

For more information about starting an ETH-DM session, see “Starting an ETH-DM<br />

Session” on page 264.<br />

Chapter 14: Configuring ITU-T Y.1731 <strong>Ethernet</strong> Service OAM<br />

243

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!