14.12.2012 Views

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - 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.

Table 50: show oam ethernet connectivity-fault-management mep-database Output<br />

Fields (continued)<br />

Field Name<br />

Out of sync 1DMs<br />

received<br />

DMMs sent<br />

Valid DMMs received<br />

Invalid DMMs received<br />

DMRs sent<br />

Valid DMRs received<br />

Invalid DMRs received<br />

Valid out-of-order LBRs<br />

received<br />

LBRs received with<br />

corrupted data<br />

LBRs sent<br />

LTMs sent<br />

LTMs received<br />

LTRs sent<br />

LTRs received<br />

Sequence number of<br />

next LTM request<br />

LMM sent<br />

Field Description<br />

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

If the MEP is a receiver for a one-way ETH-DM session: Number of out-of-sync one-way delay<br />

measurement request packets received.<br />

If the MEP is an initiator for a two-way ETH-DM session: Number of Delay Measurement Message<br />

(DMM) PDU frames sent to the peer MEP in this session.<br />

For all other cases, this field displays 0.<br />

If the MEP is an initiator for a two-way ETH-DM session: Number of valid two-way delay measurement<br />

packets received.<br />

If the MEP is an initiator for a two-way ETH-DM session: Number of invalid two-way delay measurement<br />

packets received.<br />

If the MEP is a responder for a ETH-DM session: Number of Delay Measurement Reply (DMR) frames<br />

sent.<br />

For all other cases, this field displays 0.<br />

If the MEP is an initiator for a two-way ETH-DM session: Number of valid DMRs received.<br />

For all other cases, this field displays 0.<br />

If the MEP is an initiator for a two-way ETH-DM session: Number of invalid DMRs received.<br />

For all other cases, this field displays 0.<br />

Number of LBRs received that were valid messages and not in sequence.<br />

Number of LBRs received that were corrupted.<br />

Number of LBRs transmitted.<br />

Linktrace messages (LTMs) transmitted.<br />

Linktrace messages received.<br />

Linktrace responses (LTRs) transmitted.<br />

Linktrace responses received.<br />

Chapter 4: Ethernet Interface Operational Mode <strong>Command</strong>s<br />

Sequence number of the next linktrace message request to be transmitted.<br />

If the interface is attached to an initiator MEP for a ETH-LM session: Number of loss measurement<br />

message (LMM) PDU frames sent to the peer MEP in this session.<br />

321

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

Saved successfully!

Ooh no, something went wrong!