SLR PDU Format
The synthetic loss reply (SLR) PDU format is used by a MEP to transmit SLR information.
The following are the fields in an SLR PDU:
•
MEG Level—A 3-bit field the value of which is copied from the last received SLM PDU.
•
Version—A 5-bit field the value of which is copied from the last received SLM PDU.
•
OpCode—Identifies an OAM PDU type. For SLR, it is set as 54.
•
Flags—A 1-octet field copied from the SLM PDU.
•
TLV Offset—A 1-octet field copied from the SLM PDU.
•
Source MEP ID—A 2-octet field copied from the SLM PDU.
•
Responder MEP ID—A 2-octet field used to identify the MEP transmitting the SLR
frame.
•
Test ID—A 4-octet field copied from the SLM PDU.
•
TxFCf—A 4-octet field copied from the SLM PDU.
•
TxFCb—A 4 octet field. This value represents the number of SLR frames transmitted
for this test ID.
•
Optional TLV—The value is copied from the SLM PDU, if present.
•
End TLV—A 1-octet field copied from the SLM PDU.
Data Iterator TLV Format
The data iterator TLV specifies the data TLV portion of the Y.1731 data frame. The MEP
uses a data TLV when the MEP is configured to measure delay and delay variation for
different frame sizes. The following are the fields in a data TLV:
•
Type—Identifies the TLV type; value for this TLV type is Data (3).
•
Length—Identifies the size, in octets, of the Value field containing the data pattern.
The maximum value of the Length field is 1440.
•
Data pattern—An n-octet (n denotes length) arbitrary bit pattern. The receiver ignores
it.
Related
Documentation
Ethernet Synthetic Loss Measurement Overview on page 1140•
• Transmission of ETH-SLM Messages on page 1141
• Guidelines for Configuring ETH-SLM on page 1146
• Scenarios for Configuration of ETH-SLM on page 1147
• Managing ETH-SLM Statistics and ETH-SLM Frame Counts on page 1148
• Starting a Proactive ETH-SLM Session on page 1153
• Starting an On-Demand ETH-SLM Session on page 1156
1145Copyright © 2017, Juniper Networks, Inc.
Chapter 34: Configuring Operations, Administration, and Management (OAM)