Ethernet OAM Commands
ethoam two-way-delay
Initiate a two-way-delay measurement to determine the round-trip latency and jitter between two MEPs.
The initiating MEP sends delay measurement message (DMM) frames to the receiving MEP. The receiv-
ing MEP responds with delay measurement reply (DMR) frames.
ethoam two-way-delay {target-endpoint t-mepid | target-macaddress mac_add} source-endpoint s-
mepid domain domain association association [vlan- priority vlan-priority]
Syntax Definitions
t-mepid
mac_add
s-mepid
domain
association
vlan-priority
Defaults
parameter
vlan-priority
Platforms Supported
OmniSwitch 6400, 6850, 6850E, 6855, 9000E
Usage Guidelines
•
Source MEP-ID, MD and MA must be created before initiating a two-way delay measurement.
•
When target-endpoint is specified then entry must be present in the RMEP table, no matter if the
status is RMEP_OK or RMEP_FAILED, before initiating two-way-delay. So target-macaddress can
be used to bypass such a restriction.
•
The CLI console will pause until all DMRs are received or maximum of 3 seconds to ensure that all the
DMRs have been returned. If the operation fails, then the appropriate message is displayed. If the oper-
ation is successful, no message is displayed.
•
If the DMM is initiated by UP MEP with a target-macaddress and the egress port is found for this
MAC address, then DMM frames are transmitted from that port. Otherwise, DMM frames are flooded
in the MEP's VLAN.
•
Two-way delay measurement does not require NTP clock synchronization on the sending and receiv-
ing MEPs.
OmniSwitch CLI Reference Guide
Target MEP-ID. Valid Range 1-8191.
Target MAC-Address.
Source MEP-ID. Vaild Range 1-8191.
The maintenance domain name.
The maintenance association name.
VLAN Priority. Valid Range is 0-7.
default
7
June 2012
page 45-47