Technical Specification

MEF 48

Carrier Ethernet Service Activation Testing

(SAT)

October 2014

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
Disclaimer

The information in this publication is freely available for reproduction and use by any recipient
and is believed to be accurate as of its publication date. Such information is subject to change
without notice and the Metro Ethernet Forum (MEF) is not responsible for any errors. The MEF
does not assume responsibility to update or correct any information in this publication. No rep-
resentation or warranty, expressed or implied, is made by the MEF concerning the completeness,
accuracy, or applicability of any information contained herein and no liability of any kind shall
be assumed by the MEF as a result of reliance upon such information.

The information contained herein is intended to be used without modification by the recipient or
user of this document. The MEF is not responsible or liable for any modifications to this docu-
ment made by any other party.

The receipt or any use of this document or its contents does not in any way create, by implication
or otherwise:

a) any express or implied license or right to or under any patent, copyright, trademark or
trade secret rights held or claimed by any MEF member company which are or may be
associated with the ideas, techniques, concepts or expressions contained herein; nor

b) any warranty or representation that any MEF member companies will announce any
product(s) and/or service(s) related thereto, or if such announcements are made, that
such announced product(s) and/or service(s) embody any or all of the ideas, technolo-
gies, or concepts contained herein; nor

c) any form of relationship between any MEF member companies and the recipient or
user of this document.

Implementation or use of specific Metro Ethernet standards or recommendations and MEF speci-
fications will be voluntary, and no company shall be obliged to implement them by virtue of par-
ticipation in the Metro Ethernet Forum. The MEF is a non-profit international organization ac-
celerating industry cooperation on Metro Ethernet technology. The MEF does not, expressly or
otherwise, endorse or promote any specific products or services.

© The Metro Ethernet Forum 2014. All Rights Reserved.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Table of Contents
1 List of Contributing Members ........................................................................................... 1
2 Abstract ................................................................................................................................ 1
3 Terminology and Acronyms............................................................................................... 1
4 Scope..................................................................................................................................... 9
5 Compliance Levels ............................................................................................................ 10
6 Numerical Prefix Conventions ......................................................................................... 11
7 Introduction ....................................................................................................................... 11
7.1 Terminology and SAT Use Case ..................................................................................... 13
7.2 Aspect of Service Testing Framework ............................................................................ 15
8 Service Measurement Points and Functions................................................................... 16
8.1 Service Activation Measurement Point Location ............................................................ 16
8.1.1 Service Activation Measurement Point Locations and Use Cases ........................................ 17
8.1.2 Loopback Considerations ...................................................................................................... 21
9 Service Attributes.............................................................................................................. 22
9.1 E-Access Service Attributes ............................................................................................ 22
9.1.1 UNI Service Attributes .......................................................................................................... 22
9.1.2 OVC per UNI Service Attributes .......................................................................................... 23
9.1.3 OVC Service Attributes ........................................................................................................ 24
9.1.4 OVC End Point per ENNI Service Attributes ....................................................................... 24
9.1.5 ENNI Service Attributes ....................................................................................................... 25
9.2 Performance Service Attributes ....................................................................................... 26
9.3 Ingress Bandwidth Profile Parameters ............................................................................ 27
10 Service Activation Testing Methodology ........................................................................ 28
10.1 Common Test Methodology Requirements ..................................................................... 29
10.1.1 Common Ethernet Test Equipment Requirement ................................................................. 29
10.1.2 Test Frame Format and Size.................................................................................................. 30
10.1.3 One-way vs two-way Performance Measurement................................................................. 31
10.2 Service Acceptance Criteria Limits ................................................................................. 32
10.3 Service Configuration Tests ............................................................................................ 33
10.3.1 OVC MTU Size Test ............................................................................................................. 36
10.3.2 CE-VLAN ID Preservation Test ........................................................................................... 37
10.3.3 CE VLAN CoS ID Preservation Test .................................................................................... 40
10.3.4 Broadcast, Unicast, Multicast Frame Delivery Test.............................................................. 42
10.3.5 Ingress Bandwidth Profile per OVC End Point Tests ........................................................... 48
10.4 Service Performance Tests .............................................................................................. 60
10.4.1 Service Performance Tests Duration ..................................................................................... 65
11 Results ................................................................................................................................ 65
11.1 Monitoring Test ............................................................................................................... 66
11.1.1 Determine Test Status ........................................................................................................... 66
11.1.2 Determine Test Result ........................................................................................................... 67

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page i
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
11.1.3 Test Report ............................................................................................................................ 68
12 Terminology Alignment.................................................................................................... 68
12.1 ITU-T Y.1563 .................................................................................................................. 68
13 References .......................................................................................................................... 69
Appendix A Special Use Cases when performing SAT on MEF Services (Informative) .. 70
A.1 E-Access Use Cases......................................................................................................... 70
A.1.1 Cooperative Service Activation Testing by Service and Access Providers .......................... 70
A.1.2 Service Activation Testing with an existing EVC at the UNI ............................................... 71
Appendix B SAT Record example (Informative) .................................................................. 73
B.1 Access Provider SAT Record .......................................................................................... 73
B.1.1 UNI Service Attributes Record ............................................................................................. 73
B.1.2 OVC per UNI Service Attributes Record .............................................................................. 73
B.1.3 OVC Service Attributes Record ............................................................................................ 74
B.1.4 OVC End Point per ENNI Service Attributes Record .......................................................... 74
B.1.5 ENNI Service Attributes Record ........................................................................................... 74
B.1.6 Access EPL Service Definition Record................................................................................. 74
B.1.7 Service Acceptance Criteria Record ..................................................................................... 75
B.1.8 EMIX Frame Size Configuration Test Record ...................................................................... 75
B.1.9 OVC MTU Size Test Record ................................................................................................ 75
B.1.10 CE-VLAN ID Preservation Test Record – Access EPL ....................................................... 76
B.1.11 CE-VLAN CoS ID Preservation Test Record ....................................................................... 77
B.1.12 Broadcast Delivery Test Record ........................................................................................... 79
B.1.13 Unicast Delivery Test Record ............................................................................................... 80
B.1.14 Multicast Delivery Test Record ............................................................................................ 81
B.1.15 Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test Record .............. 81
B.1.16 Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test Record .............. 82
B.1.17 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test Record ................... 83
B.1.18 Service Performance Tests Record – Access EPL ................................................................ 84
B.2 Service Provider Service Activation Testing Record ...................................................... 85
B.2.1 UNI Service Attributes Record ............................................................................................. 85
B.2.2 OVC per UNI Service Attributes Record .............................................................................. 85
B.2.3 OVC Service Attributes Record ............................................................................................ 85
B.2.4 OVC End Point per ENNI Service Attributes Record .......................................................... 85
B.2.5 ENNI Service Attributes Record ........................................................................................... 86
B.2.6 Access EPL Service Definition Record................................................................................. 86
B.2.7 Service Acceptance Criteria Record ..................................................................................... 86
B.2.8 EMIX Frame Size Configuration Test Record ...................................................................... 86
B.2.9 OVC MTU Size Test Configuration Record ......................................................................... 86
B.2.10 CE-VLAN ID Preservation Test Record – Access EPL ....................................................... 86
B.2.11 CE-VLAN CoS ID Preservation Test Record – Access EPL ............................................... 86
B.2.12 Broadcast Delivery Test Record ........................................................................................... 86
B.2.13 Unicast Delivery Test Record ............................................................................................... 86
B.2.14 Multicast Delivery Test Record ............................................................................................ 86
B.2.15 Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test Record .............. 87
B.2.16 Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test Record .............. 87
B.2.17 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test Record ................... 87
B.2.18 Service Performance Tests Record – Access EPL ................................................................ 87

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page ii
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

List of Figures
Figure 1 – E-Access Service View for SAT ................................................................................. 10
Figure 2 – Example of SAT Use Case for E-Access Service ....................................................... 14
Figure 3 – Service Testing Venn Diagram ................................................................................... 15
Figure 4 – Service Measurement Point Specialization ................................................................. 16
Figure 5 – SAMP Location at the Service Provider’s ENNI ........................................................ 17
Figure 6 – SAMP Location at the Access Provider’s ENNI ......................................................... 18
Figure 7 – SAMP Location at the Access Provider’s UNI ........................................................... 18
Figure 8 – Service Activation Measurement Points Use Cases A & B ........................................ 20
Figure 9 – Service Activation Measurement Points Use Cases C & D ........................................ 21
Figure 10 – Service Activation Test Methodology ....................................................................... 29
Figure 11 – Service Configuration Test Process for Access Providers ........................................ 33
Figure 12 – Service Configuration Test Process for Service Providers........................................ 34
Figure 13 – Service Configuration Test – Ingress Bandwidth Profile per OVC End Point Test . 49
Figure 14 – Service Performance Tests Process – Access EPL.................................................... 61
Figure 15 – Service Performance Tests Process – Access EVPL................................................. 62
Figure 16 – Test Results Use Case (Push Model)......................................................................... 66
Figure 17 – SAT performed “cooperatively” by Service & Access Providers ............................. 71
Figure 18 – Congestion Due to SAT using Latching Loopback (LL) .......................................... 72
Figure 19 – Congestion Due to SAT using Ethernet Test Equipment-Application ...................... 72

List of Tables
Table 1 – Terminology and Acronyms ........................................................................................... 9
Table 2 – Numerical Prefix Conventions...................................................................................... 11
Table 3 – UNI Service Attributes ................................................................................................. 23
Table 4 – OVC per UNI Service Attributes .................................................................................. 23
Table 5 – OVC Service Attributes ................................................................................................ 24
Table 6 – OVC End Point per ENNI Service Attributes .............................................................. 25
Table 7 – ENNI Service Attributes ............................................................................................... 26
Table 8 – Performance Service Attributes .................................................................................... 27
Table 9 – Parameters for Bandwidth Profile Service Attributes................................................... 28
Table 10 – Ethernet Test Frame Sizes and Size Designations ...................................................... 31
Table 11 – SAT Methodology – Common Test Requirements for Access EPL Services ............ 35
Table 12 – SAT Methodology – Common Test Requirements for Access EVPL Services ......... 36
Table 13 – SAT Methodology – OVC MTU Size Test ................................................................ 37
Table 14 – SAT Methodology – CE-VLAN ID Preservation Test for Access EPL Services ...... 38
Table 15 – SAT Methodology – CE-VLAN ID Preservation Test for Access EVPL Services ... 39
Table 16 – SAT Methodology – CE-VLAN CoS ID Preservation Test for Access EPL Services
............................................................................................................................................... 41
Table 17 – SAT Methodology – CE-VLAN CoS ID Preservation Test for Access EVPL Services
............................................................................................................................................... 42
Table 18 – SAT Methodology – Broadcast Delivery Test for Access EPL Services ................... 43
Table 19 – SAT Methodology – Broadcast Delivery Test for Access EVPL Services ................ 44
Table 20 – SAT Methodology – Unicast Delivery Test for Access EPL Services....................... 45
Table 21 – SAT Methodology – Unicast Delivery Test for Access EVPL Services .................... 46
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page iii
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Table 22 – SAT Methodology – Multicast Delivery Test for Access EPL Services .................... 47
Table 23 – SAT Methodology – Multicast Delivery Test for Access EVPL Services ................. 47
Table 24 – SAT Methodology –CIR Configuration Test (Color-aware) ...................................... 51
Table 25 – SAT Methodology –CIR Configuration Test (Color-blind) ....................................... 52
Table 26 – SAT Methodology – EIR Configuration Test (Color-aware) ..................................... 54
Table 27 – SAT Methodology – EIR Configuration Test (Color-blind) ...................................... 56
Table 28 – SAT Methodology – Traffic Policing Configuration Test (Color-aware) .................. 58
Table 29 – SAT Methodology – Traffic Policing Configuration Test (Color-blind) ................... 60
Table 30 – SAT Methodology – Service Performance Tests – Single Service ............................ 63
Table 31 – SAT Methodology – Service Performance Tests – Multiple Services ....................... 65
Table 32 – UNI Service Attributes Record Example.................................................................... 73
Table 33 – OVC per UNI Service Attributes Record Example .................................................... 73
Table 34 – OVC Service Attributes Record Example .................................................................. 74
Table 35 – OVC End Point per ENNI Service Attribute Record Example .................................. 74
Table 36 –ENNI Service Attribute Record Example .................................................................... 74
Table 37 – Access EPL Service Definition Record Example ....................................................... 75
Table 38 – Service Acceptance Criteria Record Example ............................................................ 75
Table 39 – EMIX Frame Size Configuration Record Example .................................................... 75
Table 40 – OVC MTU Size Test Record Example....................................................................... 76
Table 41 – CE-VLAN ID Preservation Test Record – Access EPL ............................................. 77
Table 42 – CE-VLAN CoS ID Preservation Test Record ......................................................... 79
Table 43 – Broadcast Delivery Test Record Example .............................................................. 80
Table 44 – Unicast Delivery Test Record Example .................................................................. 80
Table 45 – Multicast Delivery Test Record Example ............................................................... 81
Table 46 – Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test (Color-
blind) Record Example ......................................................................................................... 82
Table 47 – Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test (Color-
aware) Record Example ........................................................................................................ 83
Table 48 – Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test (Color-
aware) Record Example ........................................................................................................ 84
Table 49 – Service Performance Tests Record – Access EPL Example .................................. 84
Table 50 – UNI Service Attribute Record Example ................................................................ 85
Table 51 – OVC per UNI Service Attribute Record Example ................................................. 85
Table 52 – OVC Service Attribute Record Example ............................................................... 85

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page iv
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

1 List of Contributing Members

The following members of the MEF participated in the development of this document and have
requested to be included in this list.

ADVA Optical Networking LTD JDSU

Albis Technologies Omnitron Systems Technology, Inc.
Alcatel-Lucent PLDT Corp. Business Solutions
Allstream Pulse Communications (Pulsecom)
Cable Television Labs RAD Data Communications
Ciena Corporation Microsemi (Symmetricom)
Cisco Systems Tata Communications
Cogeco Cable Inc. Telecom New Zealand
Comcast Time Warner Cable
EXFO Inc. Transition Networks
IOMETRIX Verizon

2 Abstract

This document specifies the requirements and use cases for Carrier Ethernet Service Activation
Testing (SAT) for E-Access services (Access Ethernet Private Line (Access EPL) and Access
Ethernet Virtual Private Line (Access EVPL)) as defined in MEF 33 [20]. Service Activation
Testing encompasses those business processes for testing MEF services to ensure that the service
is configured as specified and meets the defined Service Acceptance Criteria (SAC). Service Ac-
tivation Testing occurs after the Operator Virtual Connection (OVC) for an E-Access service
[20] has been provisioned and before the service is deployed to the customer.

3 Terminology and Acronyms

This section defines the terms used in this document. In many cases, the normative definitions to
terms are found in other documents. In these cases, the third column is used to provide the refer-
ence that is controlling, in other MEF or external documents.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 1
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Access EPL Access Ethernet Private Line MEF 33 [20]
Access EVPL Access Ethernet Virtual Private Line MEF 33 [20]
AP Access Provider MEF 33 [20]
Bandwidth Profile A Bandwidth Profile is a characterization of the MEF 10.3 [13]
lengths and arrival times for Service Frames at a ref-
erence point.
BWP Bandwidth Profile MEF 10.3 [13]
Carrier Ethernet Net- A network from a Service Provider or Network Op- MEF 12.2 [14]
work erator supporting the MEF service and architecture
models.
CBS Committed Burst Size MEF 10.3 [13]
CEN Carrier Ethernet Network MEF 12.2 [14]
CF Coupling Flag MEF 10.3 [13]
CIR Committed Information Rate MEF 10.3 [13]
CM Color Mode MEF 10.3 [13]
Collector Test Func- A logical function for collecting Ethernet test meas- This document
tion urements.
Color Mode CM is a Bandwidth Profile parameter. The Color MEF 10.3 [13]
Mode parameter indicates whether the color-aware
or color-blind property is employed by the Band-
width Profile. It takes a value of “color-blind” or
“color-aware” only.
Color-aware A Bandwidth Profile property where a pre- MEF 10.3 [13]
determined level of Bandwidth Profile compliance
for each Service Frame is taken into account when
determining the level of compliance for each Service
Frame.
Color-blind A Bandwidth Profile property where a pre- MEF 10.3 [13]
determined level of Bandwidth Profile compliance
for each Service Frame, if present, is ignored when
determining the level of compliance for each Service
Frame.
Committed Burst Size CBS is a Bandwidth Profile parameter. It limits the MEF 10.3 [13]
maximum number of bytes available for a burst of
Service Frames sent at the UNI speed to remain
CIR-conformant.
Committed Infor- CIR is a Bandwidth Profile parameter. It defines the MEF 10.3 [13]
mation Rate average rate in bits/s of Service Frames up to which
the network delivers Service Frames and meets the
performance objectives defined the CoS Service At-
tribute.
CoS Class of Service or Classes of Service MEF 23.1 [17]
CoS Performance Performance objective specified for a CoS Label or MEF 23.1 [17]
Objective CoS Name.
CTF Collector Test Function This document
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 2
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Coupling Flag CF is a Bandwidth Profile parameter. The Coupling MEF 10.3 [13]
Flag allows the choice between two modes of opera-
tion of the rate enforcement algorithm. It takes a val-
ue of 0 or 1 only.
CPO CoS Performance Objective MEF 23.1 [17]
Double-tagged IEEE 802.1ad Ethernet frames with two tags. The MEF 37 [22]
Frames outer tag is an S-Tag, the inner tag is a C-Tag.
Dual-Ended A type of process where a MEP sends measurement MEF 35 [21]
information to a peer MEP that will perform the cal-
culations.
E-Access Ethernet Access MEF 33 [20]
EBS Excess Burst Size MEF 10.3 [13]
EFD ETH Flow Domain MEF 12.2 [14]
Egress Bandwidth A service attribute that specifies the length and arri- MEF 10.3 [13]
Profile val time characteristics of egress Service Frames at
the egress UNI.
EIR Excess Information Rate MEF 10.3 [13]
EMIX Ethernet Mix ITU-T Y.1564
[11]
ENNI External Network Network Interface MEF 4 [12]
ENNI Frame The first bit of the Destination Address to the last bit MEF 26.1 [18]
of the Frame Check Sequence of the Ethernet frame
transmitted across the ENNI.
EPCF ETH Provider Conditioning Function MEF 12.2 [14]
ESCF ETH Subscriber Conditioning Function MEF 12.2 [14]
ETE Ethernet Test Equipment MEF 46 [23]
ETE-A Ethernet Test Equipment-Application MEF 46 [23]
ETE-I Ethernet Test Equipment-Instrument MEF 46 [23]
ETE-TH Ethernet Test Equipment-Test Head MEF 46 [23]
ETH Ethernet Layer or Ethernet Services Layer MEF 4 [12]
ETH Flow Domain An ETH Flow Domain (EFD) is a topological com- MEF 12.2 [14]
ponent of the ETH Layer formally defined by the set
of ETH flow points, including termination flow
points, made available for the purpose of transferring
information within a given administrative portion of
the ETH Layer network.
ETH Provider Condi- The ETH Provider Conditioning Function (EPCF) is MEF 12.2 [14]
tioning Function the processing entity of the ETH Layer responsible
for classification, filtering, metering, marking, polic-
ing, scheduling, shaping and, in general, condition-
ing flow(s) between two CENs.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 3
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

ETH Subscriber The ETH Subscriber Conditioning Function (ESCF) MEF 12.2 [14]
Conditioning Function is the processing entity of the ETH Layer responsible
for classification, filtering, metering, marking, polic-
ing, scheduling, shaping and, in general, condition-
ing the subscriber flow into and out of a Service
Provider EFD at a UNI-N.
Ethernet Equipment A Network Element or Ethernet Test Equipment, MEF 46 [23]
with ETH functions, installed or used in a CEN.
Ethernet Mix An Ethernet traffic pattern consisting of a preset ITU-T Y.1564
mixture of Ethernet test frame sizes used to emulate [11]
real-world traffic scenarios in a testing environment.
Ethernet Services The Ethernet Services Layer, also referred to as the MEF 4 [12]
Layer ETH Layer, is responsible for the instantiation of
Ethernet MAC oriented connectivity services and the
delivery of Ethernet service frames presented across
well-defined internal and external interfaces and as-
sociated reference points. The ETH layer is also re-
sponsible for all service-aware aspects associated
with Ethernet MAC flows including operations, ad-
ministration, maintenance and provisioning capabili-
ties required to support such Ethernet connectivity
services.
Ethernet Test Equip- A general term to include an Ethernet Test Equip- MEF 46 [23]
ment ment-Application, Ethernet Test Equipment-Test
Head and/or Ethernet Test Equipment-Instrument.
Ethernet Test Equip- Functionality resident in a Network Element, which MEF 46 [23]
ment-Application may include a Generator Test Function, a Collector
Test Function, and/or Latching Loopback Function
that enables the Network Element to perform Service
Activation Testing and activate/deactivate loopback
devices.
Ethernet Test Equip- A portable, external Ethernet testing equipment not MEF 46 [23]
ment-Instrument permanently installed in the network, which may in-
clude a Generator Test Function, a Collector Test
Function, and/or Latching Loopback Function that
enables the ETE to perform Service Activation Test-
ing and activate/deactivate loopback devices.
Ethernet Test Equip- An external Ethernet testing equipment permanently MEF 46 [23]
ment-Test Head installed in the network, which may include a Gen-
erator Test Function, a Collector Test Function,
and/or Latching Loopback Function that enables the
ETE to perform Service Activation Testing and acti-
vate/deactivate loopback devices. It is not involved
in the forwarding path of services.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 4
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Ethernet Test Support A function that coordinates test activity at Ethernet MEF 46 [23]
System Test Equipment or Network Elements.
Ethernet Virtual Con- An association of two or more UNIs that limits the MEF 10.3 [13]
nection exchange of Service Frames to UNIs in the Ethernet
Virtual Connection.
ETSS Ethernet Test Support System This document
EVC Ethernet Virtual Connection MEF 10.3 [13]
Excess Burst Size EBS is a Bandwidth Profile parameter. It limits the MEF 10.3 [13]
maximum number of bytes available for a burst of
Service Frames sent at the UNI speed to remain EIR-
conformant.
Excess Information EIR is a Bandwidth Profile parameter. It defines the MEF 10.3 [13]
Rate average rate in bits/s of Service Frames up to which
the network may deliver Service Frames but without
any performance objectives.
External Network A reference point representing the boundary between MEF 4 [12]
Network Interface two Operator MENs that are operated as separate
administrative domains.
FD Frame Delay MEF 10.3 [13]
FDR Frame Delay Range MEF 10.3 [13]
FLR Frame Loss Ratio MEF 10.3 [13]
Frame Delay The time required to transmit a Service Frame from MEF 10.3 [13]
ingress UNI to egress UNI.
Frame Delay Perfor- A measure of the delays experienced by different MEF 10.3 [13]
mance Service Frames belonging to the same CoS instance.
Frame Delay Range The difference between the Frame Delay Perfor- MEF 10.3 [13]
mance values corresponding to two different percen-
tiles.
Generator Test Func- A logical function for generating and transmitting This document
tion Ethernet Frames which can include test frames.
GTF Generator Test Function This document
IFDV Inter-Frame Delay Variation MEF 10.3 [13]
IMIX Internet Mix RFC 6985 [8]
Information Rate The average bit rate of Frames at the measurement ITU-T Y.1564
point starting with the first MAC address bit and [11]
ending with the last FCS bit. Note: Frames can be
Service Frames [13] or ENNI Frames [18].
Inter-Frame Delay The difference in delay of two Service Frames be- MEF 10.3 [13]
Variation longing to the same CoS instance.
Ingress Bandwidth A characterization of ingress Service Frame arrival MEF 10.3 [13]
Profile times and lengths at the ingress UNI and a specifica-
tion of disposition of each Service Frame based on
its level of compliance with the characterization.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 5
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Internet MIX A traffic pattern consisting of a preset mixture of IP- RFC 6985 [8]
Layer packet sizes used to emulate real-world traffic
scenarios in a testing environment.
IR Information Rate ITU-T Y.1564
[11]
IRSC Information Rate Service Configuration This document
L2CP Layer 2 Control Protocol MEF L2CP [24]
Latching Loopback A configured function within an Ethernet Equipment MEF 46 [23]
where frames are returned to the entity which sent
them.
Layer 2 Control Proto- A Service Frame that is used for Layer 2 control, e.g., MEF 10.3 [13]
col Service Frame Spanning Tree Protocol.
Layer 2 Control Proto- The process by which a Layer 2 Control Protocol Ser- MEF 10.3 [13]
col Tunneling vice Frame is passed through the Service Provider
network without being processed and is delivered un-
changed to the proper UNI(s).
LL Latching Loopback MEF 46 [23]
LLF Latching Loopback Function MEF 46 [23]
MAC Media Access Control IEEE 802.3 [2]
MAC DA Media Access Control Destination Address IEEE 802.3 [2]
MAC SA Media Access Control Source Address IEEE 802.3 [2]
Maintenance Entity A Maintenance Entity Group (MEG) consists of the MEF 17 [16]
Group Maintenance Entities that belong to the same service
inside a common OAM domain.
Mean Frame Delay The arithmetic mean or average of delays experi- MEF 33 [20]
enced by different Service or ENNI Frames belong-
ing to the same CoS Frame Set.
ME-NE Metro Ethernet Network Element MEF 15 [15]
MEF Service Activa- A business process for testing MEF services to en- This document
tion Testing Process sure that the service is configured according to the
specification and will work to agreed performance
levels (e.g., SLAs). This process occurs before the
service is deployed to the customer.
MEG Maintenance Entity Group MEF 17 [16]
MEG End Point A MEG End Point (MEP) is a provisioned OAM MEF 17 [16]
reference point which can initiate and terminate pro-
active OAM frames. A MEP can also initiate and
react to diagnostic OAM frames.
MEG Intermediate MEG Intermediate Point (MIP) is a provisioned MEF 17 [16]
Point OAM reference point which is capable to react to
diagnostic OAM frames initiated by MEPs. A MIP
does not initiate proactive or diagnostic OAM
frames.
MEP MEG End Point MEF 17 [16]

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 6
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Metro Ethernet Net- A Network Element supporting Metro Ethernet ser- MEF 15 [15]
work Element vices.
MFD Mean Frame Delay MEF 33 [20]
MIP MEG Intermediate Point MEF 17 [16]
MTU Maximum Transmission Unit MEF 10.3 [13]
N/A Not Applicable This document
N/D Not Defined This document
One-way A measurement performed in the Forward or Back- MEF 35 [21]
ward direction. For example from MEP A to MEP B
or from MEP B to MEP A.
Operator Virtual Con- Operator Virtual Connection, an association of OVC MEF 26.1 [18]
nection End Points.
OVC End Point An association of an OVC with a specific External MEF 26.1 [18]
Interface i.e., UNI, ENNI
OVC Operator Virtual Connection MEF 26.1 [18]
OVC EP OVC End Point MEF 26.1 [18]
SAC Service Acceptance Criteria ITU-T Y.1564
[11]
SAMP Service Activation Measurement Point This document
SAT Service Activation Testing MEF 46 [23]
Service Acceptance A set of criteria used to ensure that a service meets ITU-T Y.1564
Criteria its functionality and quality requirement and that the [11]
service is ready to operate when it has been de-
ployed.
Service Activation A Service Activation Measurement Point is a refer- This document
Measurement Point ence point in the network, placed at the ingress of an
ETH Subscriber/Provider Conditioning Function in
the case of a Generator Test Function or at the egress
of an ETH Subscriber/Provider Conditioning Func-
tion in the case of a Collector Test Function, at
which performance reference events can be observed
and measured during the Service Activation Testing
process.
Service Activation The process of executing a collection of test proce- This document
Testing dures to be applied to a given traffic entity (e.g.,
EVC, OVC, etc.) in order to collect behavioral in-
formation about the traffic and compare this with
predefined expectations.
Service Activation A methodology for performing Ethernet Service ITU-T Y.1564
Test Methodology turn-up testing using defined benchmark tests while [11]
measuring various performance parameters.
Service Activation A report of test results for a new Ethernet Service. This document
Test Record The results show if the service met the applicable
performance objectives or Service Acceptance Crite-
ria.
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 7
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Service Configuration A high level business process which encompasses TMF GB921 [27]
and Activation operational processes for the allocation, implementa-
tion, configuration, activation and testing of specific
services to meet customer requirements.
Service Frame An Ethernet frame transmitted across the UNI to- MEF 10.3 [13]
ward the Service Provider or an Ethernet frame
transmitted across the UNI toward the Subscriber.
Service Level Agree- The contract between the Subscriber or Operator and MEF 10.3 [13]
ment Service Provider specifying the agreed to service
level commitments and related business agreements.
Service Level Specifi- The technical specification of the service level being MEF 10.3 [13]
cation offered by the Service Provider to the Subscriber.
Service Measurement A Service Measurement Point is a well-defined point This document
Point in the network at which performance reference
events can be observed and measured.
SLA Service Level Agreement MEF 10.3 [13]
SLS Service Level Specification MEF 10.3 [13]
SMP Service Measurement Point This document
SP Service Provider MEF 10.3 [13]
TAF Transport Adaptation Function MEF 4 [12]
ToD Time-of-Day MEF 35 [21]
Test Head Connection A Test Head Connection Point is a reference point in This document
Point a ME-NE, placed at the location of a ENNI ETE-A
SAMP providing the test connectivity to an ETE-TH
or ETE-I.
THCP Test Head Connection Point This document
Traffic Conditioning A Traffic Conditioning Point corresponds to an MEF 17 [16]
Point ESCF.
TrCP Traffic Conditioning Point MEF 17 [16]
Two-way A measurement of the performance of frames that MEF 35 [21]
flow from the Controller MEP to Responder MEP
and back again.
ULR Utilized Line Rate ITU-T Y.1564
[11]
UML Unified Modeling Language OMG UML [26]
UNI User Network Interface MEF 10.3 [13]
UNI-C User Network Interface-Client MEF 4 [12]
UNI-Client The UNI-C is a compound architectural component MEF 4 [12]
of a CEN that represents all of the functions required
to connect a subscriber to a CEN.
UNI-N User Network Interface-Network MEF 4 [12]
UNI-Network The UNI-N is a compound architectural component MEF 4 [12]
of a CEN that represents all of the functions required
to connect a CEN to a CEN subscriber.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 8
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Term Definition Reference

Unified Modeling The Unified Modeling Language (UML) is a unified OMG UML [26]
Language model for object oriented analysis and design.
Use Case In the UML, a use case represents one particular type OMG UML [25]
of a system’s behavior based on stimuli from an ex-
ternal source (i.e., an actor). A system may have
several use cases which define all its behavior.
User Network Inter- The physical demarcation point between the respon- MEF 10.3 [13]
face sibility of the Service Provider and the responsibility
of the Subscriber.
Utilized Line Rate The average bit rate of the Ethernet line at the meas- ITU-T Y.1564
urement point, including the bits a) allocable to the [11]
minimum-duration period of each Inter-Packet gap
(but not the number of bits allocable to the part of
each Inter-Packet gap longer than the minimum), b)
in the preamble, c) in the start of frame delimiter and
d) in the Ethernet Service Frame starting with the
first MAC address bit and ending with the last FCS
bit.
Table 1 – Terminology and Acronyms

4 Scope

This document defines the requirements and use cases for out-of-service testing performed on
MEF 33 services [20], also known as E-Access services, prior to the services being delivered to
customers and placed in-service. Use cases include testing an Access Provider’s (AP) OVC by
the AP as well as by the Service Provider (SP), as illustrated in the MEF service view in Figure
1. The document is based on E-Access services [20] definitions, which uses service attributes
and parameters defined in MEF 26.1 [18] and MEF 10.3 [13]. This document also references
International Telecommunication Union - Telecommunication Standardization Sector (ITU-T)
Recommendation Y.1564 [11] for the basic Service Activation Testing methodology and test
procedures to be used for Service Configuration and Service Performance testing, while extend-
ing these test procedures for E-Access service attributes and parameters [20]. With the proce-
dures defined in this document, Service Providers and Access Providers can work together in a
standardized fashion to activate configured services.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 9
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 1 – E-Access Service View for SAT

5 Compliance Levels

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [5]. All key words must be in upper
case, bold text.

Items that are REQUIRED (contain the words MUST or MUST NOT) are labeled as [Rx] for
required. Items that are RECOMMENDED (contain the words SHOULD or SHOULD NOT)
are labeled as [Dx] for desirable. Items that are OPTIONAL (contain the words MAY or OP-
TIONAL) are labeled as [Ox] for optional.

A paragraph preceded by [CRa]< specifies a conditional mandatory requirement that MUST be

followed if the condition(s) following the “<” have been met. For example, “[CR1]<[D38]” in-
dicates that Conditional Mandatory Requirement 1 must be followed if Desirable Requirement
38 has been met. A paragraph preceded by [CDb]< specifies a Conditional Desirable Require-
ment that SHOULD be followed if the condition(s) following the “<” have been met. A para-
graph preceded by [COc]< specifies a Conditional Optional Requirement that MAY be followed
if the condition(s) following the “<” have been met.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 10
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

6 Numerical Prefix Conventions

This document uses the prefix notation to indicate multiplier values as shown in Table 2.

Decimal Binary
Symbol Value Symbol Value
k 103 Ki 210
M 106 Mi 220
G 109 Gi 230
12
T 10 Ti 240
P 1015 Pi 250
18
E 10 Ei 260
Z 1021 Zi 270
Y 1024 Yi 280
Table 2 – Numerical Prefix Conventions

7 Introduction

When a Service Provider contracts with an Access Provider to connect to a customer location,
testing should be performed to verify that the E-Access service [20] meets the Service Provider
and customer expectations. This testing, across the multi-Carrier Ethernet Network (CEN) envi-
ronment, ensures that the allocated network resources have been configured properly (e.g., con-
nectivity is established and the configurable service parameters are correct) and that the service
meets the applicable Service Acceptance Criteria (SAC). The SAT Record created as a result of
the test would be used as a birth certificate for the service. It can be referred to in the future if
there is ever a question about the level of performance that was attained, or if it can be helpful in
troubleshooting a subsequent performance problem.

The following definition is provided in MEF 15 [15] from a resource management perspective
(e.g., resources participating in providing the Ethernet service):

“Once the equipment has been installed and the software and initial installation configuration
data has been loaded, Service Activation must be performed. Service Activation ensures that the
Metro Ethernet Network Element (ME-NE) receives the data necessary in order to use resources
to provide the intended network service.”

The TeleManagement Forum defines several business processes related to Service Activation
Testing. They define two phases to Service Activation Testing:

 Configuration Verification

 Performance Verification

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 11
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Configuration Verification testing is of short duration and ideal for connectivity, Committed In-
formation Rate (CIR) and Excess Information Rate (EIR) configuration and Service Acceptance
Criteria (SAC) evaluation prior to Performance Verification. This type of testing could be per-
formed by a technician who is onsite installing and configuring a User Network Interface (UNI)
Ethernet demarcation device, but is not limited to this scenario.

Performance Verification testing requires longer duration, on the order of 15 minutes to 1 day, to
ensure that all the elements of the network as well as existing active services have had sufficient
time to show any problems that could occur. Performance Verification focuses on measuring at-
tributes such as Frame Delay (FD), Frame Loss Ratio (FLR), Inter-Frame Delay Variation
(IFDV), and Information Rate (IR), and characterizing each service while simultaneously run-
ning all services at once.

Service Configuration tests and Service Performance tests pass or fail on the basis of whether or
not the service meets its SAC during each test. These criteria are allowable limits for each of the
measured parameters in the test, and are carefully selected to give the Service Provider and Ac-
cess Provider confidence that a service that passes its Service Activation Testing according to the
established SAC will be a satisfactory service that will meet its Class of Service Performance
Objectives (CPOs). Some differences may exist between the Service Acceptance Criteria and the
Class of Service Performance Objectives. For instance, the measurement definitions and meas-
ured parameters may be slightly different at Service Activation than they are for performance
monitoring, so it may be impossible to select exactly equal limits. Second, an SP and an AP may
wish to choose SAC that are slightly more stringent than the CPOs, to help ensure a low likeli-
hood of performance problems occurring for the activated service.

Test results and data from both the Configuration Verification testing and the Performance Veri-
fication testing are inputs into the creation of the SAT Record. Creating a concise performance
report as a baseline facilitates future performance comparisons.

This document uses and extends test processes and procedures based on an Ethernet test method-
ology defined by ITU-T Y.1564 [11]. However, it should be clarified that this document is spe-
cific to MEF services, service attributes and parameters and defines specific requirements, use
cases, test procedures, measurement points, and test topologies relevant to the services defined in
MEF 33 [20].

Prior to ITU-T Y.1564 [11], the only methodology widely used to assess the performance of
Ethernet-based network services was Internet Engineering Task Force’s (IETF) "Benchmarking
Methodology for Network Interconnect Devices", also known as RFC 2544 [6]. RFC 2544 [6]
was created to evaluate the performance characteristics of network devices in the lab. It was
widely adapted to provide performance metrics of Ethernet-based network services as there was
no other methodology available to measure the attributes defined in RFC 1242 [4].

With its capability to measure throughput, latency, frame loss, and burstability (back-to-back
test), RFC 2544 [6] could arguably be used to provide performance metrics. However, to do so
would be to use RFC 2544 [6] beyond its intended scope. The IETF as also issued an applicabil-
ity statement for the use of RFC 2544 [7] as a methodology for Ethernet service activation test-
ing. The statement can be found in RFC 6815 [7].

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 12
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ITU-T Y.1564 [11] fills the methodological gap for measurement of operational Ethernet net-
work services. Also, Ethernet-based services have evolved to include more features and com-
plexities than those covered by the RFC 2544 [6] scope. The RFC 2544 [6] benchmarking meth-
odology is not applicable to Ethernet service activation testing because:

 IETF RFC 2544 [6] does not consider multiple time durations for tests, as are often per-
formed in operational networks with time-varying impairments. Its procedures find the
absolute performance limit of a network element in a laboratory environment rather than
verify that a service is delivered to the agreed level.

 Latency is measured in a limited way, on only one frame every two minutes, and only at
maximum transmitted load with no loss rate, which is very likely much higher than the
agreed upon committed information rate.

 It does not provide for the verification of configuration and performance of CIR and EIR,
all important components of the Bandwidth Profile.

 Finally, important Ethernet service attributes, such as frame delay variation, are not part
of the methodology.

For these reasons, ITU-T Y.1564 [11] was chosen as the base for this technical specification.

7.1 Terminology and SAT Use Case

This section highlights the Service Activation Testing (SAT) use case based on the E-Access
service type [20]. This section also provides terminology definitions of the different components
defined within this document, which may be used in SAT topologies, requirements and process-
es. A fundamental understanding of the terms and concepts will be necessary for later sections
of the document.

An Ethernet Test Equipment-Instrument (ETE-I) is a portable, external Ethernet testing device

not permanently installed in the network that may include a Generator Test Function (GTF) and
Collector Test Function (CTF) and/or Latching Loopback function (LLF) that enables the ETE-I
to perform Service Activation Testing and activate/deactivate loopback devices. The Ethernet
Test Equipment-Instrument may be remotely connected to a UNI-N, and includes the necessary
logical and physical test functions to perform Service Activation Testing at that UNI-N.

An Ethernet Test Equipment-Application (ETE-A) includes functionality resident in a Network

Element that may include a Generator Test Function and a Collector Test Function and/or Latch-
ing Loopback function that enables the Network Element to perform Service Activation Testing
and activate/deactivate loopback devices. For example, the Ethernet Test Equipment-Application
may reside at an External Network Network Interface - Network (ENNI-N) or UNI-N. In the
scenario presented in Figure 2, a technician at the AP’s UNI is not necessary since the logical
testing functions reside in the ME-NE.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 13
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

An Ethernet Test Equipment-Test Head (ETE-TH) is an Ethernet Test Equipment (ETE) in-
stalled in the network for performing Service Activation Testing that includes a Generator Test
Function, Collector Test Function and/or Latching Loopback function that enables the ETE-TH
to perform Service Activation Testing and activate/deactivate loopback devices.

ETE is a general term to include an Ethernet Test Equipment-Application, Ethernet Test Equip-
ment-Test Head and/or Ethernet Test Equipment-Instrument.

Figure 2 illustrates a SAT use case where a Service Provider A is using an Ethernet Test Equip-
ment-Test Head placed within its network. The ETE-TH is not involved in the forwarding path
of services. In this scenario, Service Provider A wishes to test the E-Access service [20] from the
ENNI-N of Service Provider A to the UNI-N of Access Provider B and use the Ethernet Test
Support System to control the fixed Ethernet Test Equipment-Test Head, which is dedicated for
Ethernet testing. An Ethernet Test Support System in Service Provider A’s back office (e.g., Ser-
vice Provider A is offering the end-to-end MEF service) may control the testing, with direct ac-
cess to the Ethernet Test Equipment-Test Head at Service Activation Measurement Point
(SAMP) A, via in-band management access to the Ethernet Test Equipment-Application at
SAMP B. The in-band management access definitions to the ETE-A at the remote end is beyond
the scope of this specification.

An Ethernet Test Support System is a back office or Operational Support System (OSS) that co-
ordinates test activity at Ethernet Test Equipment-Test Heads or Network Elements, and includes
storage of SAT Records. However, since this Service Provider has no out-of-band management
access to the UNI-N Network Element located at SAMP B, it may invoke an in-band Latching
Loopback (LL) to facilitate the testing process by looping all test traffic within that Network El-
ement.

SAMP C in Figure 2 is located at the Access Providers ENNI-N and would be used to connect an
ETE-TH and test the E-Access service [20] from an Access Provider’s perspective.

Figure 2 – Example of SAT Use Case for E-Access Service

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 14
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

7.2 Aspect of Service Testing Framework

Service Activation Testing, Service Monitoring, and Service Troubleshooting business processes
contribute to an overall Service Testing framework as the Venn diagram in Figure 3 highlights.
The process comparisons are discussed below.

Figure 3 – Service Testing Venn Diagram

Service Activation Testing, as part of the Service Testing framework, can be viewed as a process
to validate that the Access EPL or Access EVPL service [20] is behaving as per the Service Def-
inition. The SAT methodology will verify the configuration, validate the performance of the dif-
ferent service attributes and provide a SAT Record (also known as birth certificate). Service Ac-
tivation Testing is performed as the Access EPL or Access EVPL service [20] is provision and
before releasing to the Service Provider.

Service Monitoring can be viewed as a process within Service Testing and separate from Service
Activation Testing. This includes the Fault Management and Performance Monitoring use cases
defined in MEF 30.1 [19] and MEF 35 [21] where an Ethernet service is deployed to a customer
and the service is “in-service” and carrying customer traffic. Service Monitoring encompasses
those 24x7 business processes measuring Service Level Agreement (SLA) conformance and ser-
vice health on an ongoing proactive basis. Service Monitoring also has to be sensitive to custom-
er traffic loads to avoid disrupting customer bandwidth needs. Service Monitoring employs
Maintenance Entity Groups (MEGs), MEG Intermediate Points (MIPs) and MEG End Points
(MEPs) as defined in MEF 17 [16].

Service Troubleshooting can be viewed as an on-demand process, encompassing both Service

Monitoring processes as well as Service Activation Testing processes, to diagnose and correct
faults in the service (due to service outages or service degradation). If Service Monitoring detects
network or service error/fault conditions, Service Activation Testing can be performed (as part of
troubleshooting the service problems with the affected customer) while the problematic service is
taken out-of-service and the customer traffic is halted.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 15
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

8 Service Measurement Points and Functions

This section defines the functions, architecture, requirements and use cases for the Service Acti-
vation Measurement Points in performing Service Activation Testing for E-Access services [20].

A Service Measurement Point (SMP) is a well-defined point in the network at which perfor-
mance reference events can be observed and measured. Different types of Service Measurement
Points may exist, through specialization defined in OMG UML [26], as shown in Figure 4 and
described with examples in the paragraphs below.

Figure 4 – Service Measurement Point Specialization

A Generator Test Function is a logical function for generating and transmitting Ethernet frames,
which can include synthetic test frames. Similarly, a Collector Test Function is a logical function
for collecting Ethernet test frames that are being used to perform measurements. A SAMP, which
is a specialization of a Service Measurement Point, is a reference point in the network. A SAMP
enables SAT to perform measurements on the service under test.

Other types of measurement points may exist outside of the context of SAT and these are denot-
ed in Figure 4 as Service<x>Measurement Point.

8.1 Service Activation Measurement Point Location

The figures found in this section represent some of the different test topologies that can be used
to perform SAT within the CEN architecture. Depending on whether the ETE is an Instrument,
Test Head or Application (inside an ME-NE) performing the test functions, the SAMP will be at
a physical point in the network or at a logical point inside of the ME-NE.

Refer to Figure 5, Figure 6 and Figure 7 in the following section for an illustration of the loca-
tions of SAMPs for SAT. The Access Provider and Service Provider (depending on the use case)
will need to associate the SAMPs so that there is connectivity between the ETEs testing the ser-
vice.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 16
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
8.1.1 Service Activation Measurement Point Locations and Use Cases

This section illustrates the use cases of the SAMP at different locations for the E-Access service
type [20] in a single or multi-CEN environment. Figure 5, Figure 6 and Figure 7 illustrate the
location of a SAMP or Test Head Connection Point (THCP) within a ME-NE. Figure 8 and Fig-
ure 9 represent four use cases with the internal and external logical functions and SAMP as ref-
erences.

Figure 5 – SAMP Location at the Service Provider’s ENNI

Figure 5 demonstrates the location of a SAMP (or THCP) within an SP’s ENNI-N. This SAMP
would be downward facing to test with an upward SAMP located at the AP’s UNI-N. Figure 6
shows the location of a SAMP (or THCP) within an AP’s ENNI-N. This SAMP would be up-
ward facing to test to an upward SAMP located at the AP’s UNI-N. Finally, Figure 7 illustrates
the location of a SAMP within an AP’s UNI-N. This SAMP would be upward facing to test to a
SAMP located at the ENNI-N.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 17
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 6 – SAMP Location at the Access Provider’s ENNI

Figure 7 – SAMP Location at the Access Provider’s UNI

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 18
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

As shown in Figure 5, Figure 6 and Figure 7, the location of SAMPs (up and down) is in an ETE
in relation to the ETH Layer Functional Elements [14]. An up SAMP, in a ME-NE, generates
and collects traffic that crosses the ETH Ethernet Virtual Connection (EVC) Adaptation and/or
Termination Functions [14]. A down SAMP, in a ME-NE, generates and collects traffic that
crosses the ETH Adaptation and/or Termination Functions [14]. An ETE-TH and ETE-I need to
only supports down SAMPs, i.e., send/receive test traffic out of the port on the ETE-TH or ETE-
I. On the other hand, an ETE-A can support up or down SAMPs.

[R1] When using an ETE-A at a SP's ENNI-N, the down SAMP for GTF and CTF
MUST behave as if located between the ETH Provider Conditioning Function
(EPCF) and Transport Adaptation Function (TAF).

[R2] When using an ETE-A at an AP's ENNI-N, the up SAMP for GTF and CTF
MUST behave as if located between the EPCF and TAF.

[R3] When using an ETE-TH or ETE-I, the Test Head Connection Points for the E-
Access service [20] under test at the ENNI-N MUST behave as if located be-
tween the EPCF and TAF.

[R4] When using an ETE-A at the AP's UNI-N the up SAMP for GTF and CTF
MUST be located between the ETH Subscriber Conditioning Function (ESCF)
and TAF.

[R5] When using an ETE-TH or ETE-I at the AP's UNI-N the down SAMP for GTF
and CTF MUST be associated with the OVC End Point for the E-Access service
[20] under test.

Use Case A in Figure 8 provides an example of an internal Service Activation Measurement

Point using an Ethernet Test Equipment-Application at the ENNI-N of the Access Provider's
CEN and at the Access Provider’s UNI-N to perform Service Activation Testing.

Use Case B in Figure 8 provides an example of an external Service Activation Measurement

Point using an Ethernet Test Equipment-Test Head within the Service Provider’s CEN and an
internal Service Activation Measurement Point using an Ethernet Test Equipment-Application at
the Access Provider’s UNI-N to perform Service Activation Testing. In this use case, the exter-
nal SAMP on the ETE-TH is connected to the Test Head Connection Point in the ENNI-N.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 19
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 8 – Service Activation Measurement Points Use Cases A & B

Use Case C in Figure 9 provides an example of an internal Service Activation Measurement

Point using an Ethernet Test Equipment-Application at the ENNI-N of the Access Provider's
CEN and an Ethernet Test Equipment-Instrument at the Access Provider’s UNI-N to perform
Service Activation Testing. Use Case C in Figure 9 shows the use of an Ethernet Test Equip-
ment-Instrument at the UNI-C while the customer equipment is unplugged. In this case the Ser-
vice Activation Measurement Point becomes the UNI-C itself, and the service is measured exact-
ly as it is delivered to the customer. This choice of measurement point, however, temporarily
takes the UNI and any services configured on the UNI out-of-service for the customer while the
tests are made.

Use Case D in Figure 9 provides an example of an external Service Activation Measurement

Point using an Ethernet Test Equipment-Test Head within the Access Provider’s CEN and a
UNI-N which has a Latching Loopback Function to loop back test traffic. Use case D in Figure
9 has a Latching Loopback Function (LLF) at the AP’s UNI-N to loop back test traffic. An AP’s
ETE-TH supporting a GTF is used to transmit test traffic. At the AP’s UNI-N, the test traffic is
looped back towards the CTF in the ETE-TH. As there is no GTF or CTF required where the
LLF is located, there is no SAMP at the UNI-N associated with the loopback.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 20
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 9 – Service Activation Measurement Points Use Cases C & D

8.1.2 Loopback Considerations

Operators who consider using loopback topologies should be advised that the use of loopback is
not appropriate when testing for configuration of ingress Bandwidth Profile (BWP) either at the
ENNI or at the UNI of the AP. The test traffic may not have adequate Information Rate to test
for proper configuration when testing to a LLF. Additionally, significant measurement degrada-
tion could take place due to frames transmitted at the CIR experiencing large IFDV. Burst test
procedures are generally only meaningful at the ESCF when directly connected to a GTF through
a SAMP. See Appendix A for more information on this subject.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 21
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

9 Service Attributes

This section lists the relevant service attributes that an SP and AP can verify using the proce-
dures specified in this document for Service Activation Testing of an E-Access service [20]. The
attributes are as specified in MEF 10.3 [13] and MEF 26.1 [18]. See Section 8 in this document
for test topologies.

The SAT by an SP assumes that an AP has configured the values for the attributes of the specific
Access EPL or Access EVPL [20] service per the service agreement. When doing SAT, it is as-
sumed that the SP can use the AP to help test the E-Access Service [20]. These attributes are per
UNI, per OVC End Point (OVC EP) at UNI, per OVC, per OVC EP at ENNI and per ENNI, as
specified in MEF 33 [20]. The AP performs SAT to verify that E-Access service [20] (Access
EPL or Access EVPL) behavior is conformant to the service agreement.

9.1 E-Access Service Attributes

This section lists, in different tables, the services attributes as found in MEF 33 [20]. Each table
found below lists service attributes by category and provides information on how this service at-
tribute is handled during SAT. This shown for both SP and AP. A service attribute can be tested
and its result reported in the SAT Record (Test), the configuration value of the service attribute
can be reported in the SAT Record (Report) or the service attribute is neither tested nor reported
during SAT (N/A).

Each table also provides information on whom of the SP and/or AP is responsible to test or re-
port on the service attributes and if it is mandatory or optional to test this service attribute.

A column entitled “Test Procedure” references the procedure used to test the different service
attributes.
9.1.1 UNI Service Attributes

Table 3 provides a list of the E-Access UNI service attributes [20].

[R6] The Service Provider MUST report UNI service attributes as specified in Table
3.

[R7] The Access Provider MUST report UNI service attributes as specified in Table
3.

Service Provider Access Provider

Test
Report/ Report/ Comments
UNI Service Attribute SP Req AP Req Procedure
Test Test
UNI Identifier Report Mandatory Report Mandatory - -
Physical Medium N/A - Report Mandatory - -
Speed N/A - Report Mandatory - -
Auto-Negotiation N/A - Report Mandatory - See Note 1

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 22
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Mode N/A - Report Mandatory - -

MAC Layer N/A - N/A - - See Note 2
UNI MTU Size N/A - Report Mandatory - See Note 3
CE-VLAN ID for untagged and priori-
N/A - N/A - - -
ty tagged Frames
Maximum number of OVCs per UNI N/A - N/A - - -
Maximum number of CE-VLAN IDs
N/A - N/A - - -
per OVC (Access EVPL only)
Ingress Bandwidth Profile per UNI N/A - N/A - - -
Egress Bandwidth Profile per UNI N/A - N/A - - -
Note 1: Auto-Negotiation is not a UNI service attribute defined in MEF 33 [20] but important to Service Providers.
Note 2: MAC Layer is defined in MEF 33 [20] but not directly tested in SAT. Requirement [R26] defines the test
traffic to be IEEE 802.3 [2] compliant.
Note 3: The SP and AP will be testing the OVC Maximum Transmission Unit (MTU) Size.

Table 3 – UNI Service Attributes

9.1.2 OVC per UNI Service Attributes

Table 4 provides a list of the E-Access OVC per UNI service attributes [20].

[R8] The Service Provider MUST test and/or report OVC per UNI service attributes
as specified in Table 4.

[R9] The Access Provider MUST test and/or report OVC per UNI service attributes
as specified in Table 4.

Service Provider Access Provider

Test
Report/ Report/ Comments
OVC per UNI Service Attribute SP Req AP Req Procedure
Test Test
UNI OVC Identifier Report Mandatory Report Mandatory - -
OVC End Point Map Report Mandatory Report Mandatory - See Note 1
Class of Service Identifier for Service
Test Mandatory Test Mandatory 10.3.3 See Note 2
Frames
Ingress Bandwidth Profile per OVC
Test Mandatory Test Mandatory 10.3.5 -
End Point at a UNI
Ingress Bandwidth Profile per Class of
N/A - N/A - - -
Service Identifier at a UNI
Egress Bandwidth Profile per OVC
N/A - N/A - - -
End Point at a UNI
Egress Bandwidth Profile per Class of
N/A - N/A - - -
Service Identifier at a UNI
Note 1: OVC End Point Map attribute reporting is only valid for Access EVPL.
Note 2: Class of Service Identifier for Service Frame is tested as part of CE-VLAN CoS ID Value preservation.

Table 4 – OVC per UNI Service Attributes

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 23
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
9.1.3 OVC Service Attributes

Table 5 provides a list of the E-Access OVC service attributes [20].

[R10] The Service Provider MUST test and/or report the Mandatory OVC service at-
tributes as specified in Table 5.

[O1] The Service Provider MAY test and report the Optional OVC service attributes
as specified in Table 5.

[R11] The Access Provider MUST test and/or report OVC service attributes as speci-
fied in Table 5.

Service Provider Access Provider

Test
Report/ Report/ Comments
OVC Service Attribute SP Req AP Req Procedure
Test Test
OVC Identifier Report Mandatory Report Mandatory - -
OVC Type N/A - N/A - - -
OVC End Point List N/A - N/A - - -
Maximum Number of UNI OVC End
N/A - N/A - - -
Points
Maximum Number ENNI OVC End
N/A - N/A - - -
Points
OVC Maximum Transmission Unit
Test Mandatory Test Mandatory 10.3.1 -
Size
CE-VLAN ID Preservation N/A Mandatory Test Mandatory 10.3.2 -
CE-VLAN CoS ID Value Preservation N/A Mandatory Test Mandatory 10.3.3 -
S-VLAN ID Preservation N/A - N/A - - -
S-VLAN CoS ID Value Preservation N/A - N/A - - -
Color Forwarding N/A - Report Mandatory - See Note 1
Service Level Specification N/A - N/A - - See Note 2
Unicast Frame Delivery Test Optional Test Mandatory 10.3.4 -
Multicast Frame Delivery Test Optional Test Mandatory 10.3.4 -
Broadcast Frame Delivery Test Optional Test Mandatory 10.3.4 -
Note 1: Color Forwarding is a reportable OVC service attribute. A Color Forwarding test methodology is for fur-
ther study.
Note 2: Service Level Specification will not be tested, SAC to be used as a mean to determine valid performance
attributes.

Table 5 – OVC Service Attributes

9.1.4 OVC End Point per ENNI Service Attributes

Table 6 provides a list of the E-Access OVC End Point per ENNI service attributes [20].

[R12] The Service Provider MUST test and/or report the OVC End Point per ENNI
service attributes as specified in Table 6.
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 24
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

[R13] The Access Provider MUST test and report OVC End Point per ENNI service
attributes as specified in Table 6.

Service Provider Access Provider

Test
OVC End Point per ENNI Report/ Report/ Comments
SP Req AP Req Procedure
Service Attribute Test Test
OVC End Point Identifier N/A - Report Mandatory - See Note 1
Class of Service Identifier for
Test Mandatory Test Mandatory 10.3.3 -
ENNI Frames
Ingress Bandwidth Profile per
Test Mandatory Test Mandatory 10.3.5 See Note 2
OVC End Point
Ingress Bandwidth Profile per
ENNI Class of Service Identi- N/A - N/A - - -
fier
Egress Bandwidth Profile per
N/A - N/A - - -
End Point
Egress Bandwidth Profile per
ENNI Class of Service Identi- N/A - N/A - - -
fier
Note 1: OVC End Point Identifier is specific to an AP network, and is therefore not relevant to an SP.
Note 2: The ingress CIR for an OVC at the ENNI should be greater than the corresponding ingress CIR at the UNI
due to the presence of the added S-VLAN tag (4 bytes) at the ENNI. As an example, if the average frame size was
200 bytes, the CIR should be increased by 2%.

Table 6 – OVC End Point per ENNI Service Attributes

9.1.5 ENNI Service Attributes

There are no ENNI service attributes to be configured for a SAT since it is assumed that the
ENNI is already supporting other services. The SP and AP have to ensure that ENNI Frames
have the appropriate S-tag value as specified for the E-Access service [20] being tested during
SAT. Table 7 provides a list of the E-Access ENNI service attributes [20].

[R14] The Service Provider MUST report ENNI service attributes as specified in Table
7.

[R15] The Access Provider MUST report ENNI service attributes as specified in Table
7.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 25
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Provider Access Provider

Test
Report/ Report/ Comments
ENNI Service Attribute SP Req AP Req Procedure
Test Test
Operator ENNI Identifier N/A Report Mandatory - -
Physical Layer N/A N/A - -
Frame Format N/A N/A - -
Number of Links N/A N/A - -
Protection Mechanism N/A N/A - -
ENNI Maximum Transmission Unit
N/A N/A - -
Size
End Point Map Report Mandatory Report Mandatory - -
Maximum Number of OVCs N/A N/A - -
Maximum Number of OVC End Points
N/A N/A - -
per OVC

Table 7 – ENNI Service Attributes

9.2 Performance Service Attributes

This section defines the MEF performance service attributes that are tested and reported by an
SP or an AP during Service Activation Testing (e.g., Frame Delay Performance, Frame Loss Ra-
tio Performance, etc.). These performance service attributes are listed in Table 8.

[R16] The Service Provider MUST test and report the performance service attributes
as specified in Table 8.

[R17] The Access Provider MUST test and report the performance service attributes as
specified in Table 8.

[R18] The Service Provider and Access Provider MUST agree on testing and re-
porting Frame Delay Performance or Mean Frame Delay Performance.

[R19] The Service Provider and Access Provider MUST agree on testing and reporting
Frame Delay Range Performance or Inter-Frame Delay Variation Performance.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 26
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Provider Access Provider

Test
Report/ Report/ Comments
Performance Service Attribute SP Req AP Req Procedure
Test Test
Frame Delay Performance Test Mandatory Test Mandatory - See Note 1
Frame Delay Range Performance Test Mandatory Test Mandatory - See Note 2
Mean Frame Delay Performance Test Mandatory Test Mandatory - See Note 1
Inter-Frame Delay Variation Per-
Test Mandatory Test Mandatory - See Note 2
formance
Frame Loss Ratio Performance Test Mandatory Test Mandatory - -
Note 1: Frame Delay (FD) Performance and Mean Frame Delay (MFD) Performance form a pair for which this
Technical Specification requires support for at least one. Additional information can be found in Section 6.7 of
MEF 23.1 [17].
Note 2: Frame Delay Range Performance and Inter-Frame Delay Variation Performance form a pair for which this
Technical Specification requires support for at least one. Additional information can be found in Section 6.7 of
MEF 23.1 [17].

Table 8 – Performance Service Attributes

9.3 Ingress Bandwidth Profile Parameters

This section defines the MEF ingress Bandwidth Profile that might be tested and reported by an
SP or an AP during Service Activation Testing (e.g., CIR, EIR, etc.). These parameters are listed
in Table 9. Table 9 also lists the test procedure or reference used to test the ingress Bandwidth
Profile.

As there is currently no standardized test methodology to measure the Committed Burst Size
(CBS) and Excess Burst Size (EBS) as part of Service Activation Testing, these tests are deemed
optional and are left to the Service Provider and Access Provider to decide if they are required.

As noted in Table 9, the test methodologies found in this document are defined for a Coupling
Flag equal to the value “0”. A test methodology for Coupling Flag (CF) value of “1” is not de-
fined in this document and is for further study.

[R20] The Service Provider MUST test and report the Mandatory Bandwidth Profile
service attributes as specified in Table 9.

[O2] The Service Provider MAY test and report the Optional OVC service attributes
as specified in Table 9.

[R21] The Access Provider MUST test and report the Mandatory Bandwidth Profile
service attributes as specified in Table 9.

[O3] The Access Provider MAY test and report the Optional OVC service attributes
as specified in Table 9.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 27
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Provider Access Provider

Test
Bandwidth Profile Service Report/ Report/ Comments
SP Req AP Req Procedure
Attribute Test Test
Committed Information Rate
Test Mandatory Test Mandatory 10.3.5 -
(CIR)
Committed Burst Size (CBS) Test Optional Test Optional N/D See Note 1
Excess Information Rate (EIR) Test Mandatory Test Mandatory 10.3.5 -
Excess Burst Size (EBS) Test Optional Test Optional N/D See Note 1
Coupling Flag (CF) N/A - N/A - - See Note 2
See See
Color Mode (CM) - - -
Note 3 Note 3
Note 1: CBS and EBS testing are optional as per [O11].
Note 2: The test methodologies found in this document are defined for CF = 0.
Note 3: The test methodologies found in this document address color-blind (CM=0) and color-aware (CM=1) val-
ues.

Table 9 – Parameters for Bandwidth Profile Service Attributes

10 Service Activation Testing Methodology

The goal of the testing methodology during Service Activation Testing is to validate the Service
Configuration (UNI and/or OVC) and to verify the Service Performance. The validation is per-
formed by sending predefined test traffic and verifying that the behavior is according to the Ser-
vice Definition. The following sections provide the methodology to perform this validation. To
remove complexity from this technical specification, the test methodology presented in this sec-
tion is for testing between two ETEs. Although testing from an ETE to an LLF is a valid use
case, it is a subset of the methodology.

Figure 10 below provides a summary view of the SAT methodology. The figure does not pro-
vide the description of the methodology in case of test failures and errors. The detailed method-
ology involving test failures and errors will be addressed in later figures, when appropriate.

The methodology described in Figure 10 is comprised of processes and apply to both Service
Providers and Access Providers.

The first step of the process is to set up the test architecture by ensuring connectivity between the
two ETEs. Section 8.1 of this document provides a view of the different use cases for Service
Activation Testing.

The next sets of processes for Service Activation Testing are the Service Configuration (Section
10.3) and Service Performance (Section 10.4) tests. A technician or automated testing applica-
tion in the back office ought to have the granularity and flexibility to run individual tests identi-
fied in this section, or run the full set of tests in sequence. For example, a single test from the set
of Service Configuration tests could be run for the service under test.

The last sets of processes are used to return the service to the pre-test state and to complete the
test report.
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 28
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service
SAT Methodology - Setup Test
Configuration
Start Architecture
Tests

Service
Performance
Tests

SAT Methodology - Complete Report Return Service to

Completed pre-Test State

Figure 10 – Service Activation Test Methodology

10.1 Common Test Methodology Requirements

This section captures the common testing parameters and requirements applicable to Service
Configuration tests and Service Performance tests. Section 10.1.1 provides the common ETE
requirements related to the attributes that need to be tested and the different parameters that are
configured.

Section 10.1.2 provides the requirements related to the Ethernet frames used in SAT. Finally,
Section 10.1.3 offers a description of one-way versus two-way performance measurement in the
context of SAT.
10.1.1 Common Ethernet Test Equipment Requirement

This section provides the common Ethernet Test Equipment requirement to perform SAT. The
following requirements relate to the measurement and calculation of E-Access performance ser-
vice attributes [20].

[R22] The Ethernet Test Equipment MUST measure the FD, FLR and IR.

[O4] The Ethernet Test Equipment MAY use Utilized Line Rate (ULR) in replace-
ment of IR.

[R23] The Ethernet Test Equipment MUST calculate the MFD, Frame Delay Range
(FDR) and IFDV.

[R24] The Ethernet Test Equipment MUST measure/calculate the E-Access service at-
tributes [20] for color-blind and color-aware mode when applicable.

The MEF 10.3 [13] performance metrics of FD, FDR, and IFDV are all defined in terms of the p-
Percentile of Frame Delay or Inter-Frame Delay Variation. Direct computation of percentiles
would be resource intensive, requiring significant storage and computation. The Appendix C of

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 29
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

MEF 35 [21] describes a method for determining whether performance objectives are met using
bins for FD and IFDV. The methodology to measure and calculate the E-Access performance
service attributes [20] is beyond the scope of this specification.

The goal for SAT is to reproduce Service and ENNI Frame behavior to ensure that the E-Access
service [20] performs as per the Service Level Specification (SLS). For this reason, test traffic
should be sent in both directions (ETE1 to ETE2 and ETE2 to ETE1) as per the test configuration
schematic presented in Table 11 and Table 12.

[R25] SAT MUST be performed in both directions simultaneously.

10.1.2 Test Frame Format and Size

The test frame format and size is an important part of SAT as test frames need to reproduce the
behavior of Service and ENNI Frames. This section will list the requirements for the format and
size of test frames.

[R26] The ETE MUST use IEEE 802.3 framing to perform SAT on the E-Access ser-
vices [20].

[R27] The ETE MUST generate and process CE-VLAN ID, CE-VLAN CoS ID, S-
VLAN ID and S-VLAN CoS ID as specified for C-TAG and S-TAG in IEEE
Std 802.1QTM-2011 sections 9.5 and 9.6 [3].

[R28] The ETE MUST generate or process frames such that ENNI Frames have a col-
or indication as specified in MEF 23.1 [17].

[R29] The ETE MUST generate or process frames such that ENNI Frame Format is as
specified in MEF 26.1 [18].

The frame size used for the Service Configuration and Service Performance tests can be constant
or a distribution of multiple frame sizes.

[R30] The ETE MUST support the capability to send a single constant test frame size.

[R31] The ETE MUST support the capability to configure the test frame size.

This default frame size refers to the total size in octets including the MAC DA through the FCS
of an untagged service frame at UNI and excludes the preamble and IPG. A tagged service
frame will have 4 more bytes than an untagged Service Frame. Also, the ENNI Frame will have
4 more bytes than an untagged/tagged Service Frame at UNI.

A predefined distribution of multiple frames sizes is referred to as Ethernet Mix (EMIX). This
name is similar to the name applied to the variable size patterns assigned in IP-layer testing by
different vendors, Internet Mix (IMIX). The EMIX definition found in this technical specifica-
tion draws upon ITU-T Y.1564 [11] and section 4 of RFC 6985 [8]. EMIX is used to emulate
real-world traffic scenarios in a testing environment.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 30
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

The EMIX pattern is specified in the following format:

EMIX – 123456… x

where each number is replaced by the letter corresponding to the size of the test frame at that po-
sition in the sequence. Table 10 gives the letter encoding for standard frame size [6] (64, 128,
256, 512, 1024, 1280, and 1518 bytes), UNI MTU and User defined test frame sizes.

a b c d e f g h u
64 128 256 512 1024 1280 1518 MTU User
defined

Table 10 – Ethernet Test Frame Sizes and Size Designations

EMIX patterns are to be specified by the size designator for each frame in the repeating pattern
from Table 10. For example, an eight-frame repeating pattern can be specified as follows:

EMIX – abcdefgh = 64, 128, 256, 512, 1024, 1280, 1518, MTU

[D1] EMIX variable test frame size pattern SHOULD be used as part of the Service
Configuration and Service Performance tests.

[CR1]<[D1]If an EMIX variable test frame size pattern is used, the repeating sequence of
sizes MUST support at least 8 frame sizes.

[CD1]<[D1]If an EMIX variable test frame size pattern is used, the repeating sequence of
sizes SHOULD support at least 32 frame sizes.

[CR2]<[D1] The variable frame size pattern MUST be repeated as long as necessary dur-
ing the test procedure from the first to last frame sizes starting at the beginning of
each test procedure.

[CD2]<[D1] The EMIX default pattern SHOULD be the sequence of sizes: EMIX –
abcdefgh.

10.1.3 One-way vs two-way Performance Measurement

The SAT definitions of one-way and two-way performance measurement are based on the MEF
35 [21] definitions, with adjustments for SAT to change the reference point from a MEP to an
ETE connected to a SAMP.

One-way performance measurement, in the context of SAT, is defined as a measurement per-

formed in the Forward or Backward direction. For example, using Figure 2, the Forward direc-
tion is presented from SAMP A located at the ENNI-N to SAMP B at the UNI-N. Using the
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 31
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

same Figure 2, the Backward direction is from SAMP B to SAMP A. A one-way measurement
provides a measurement in a single direction only.

Two-way measurement, in the context of SAT, is defined as a measurement performed in the

Forward direction and then in the Backward direction. As an example, using Figure 2, a two-
way measurement is from SAMP A located at the ENNI-N to SAMP B at the UNI-N and back to
SAMP A. A two-way measurement provides a round-trip measurement.

Wherever possible, one-way performance measurement is performed by the ETEs. The test is
considered passed if both directions meet the pass/fail limits (SAC), or failed if either direction
fails the SAC. One-way delay is difficult to measure and therefore one-way delay may be ap-
proximated from two-way measurements. However these techniques are beyond the scope of
this document.

[D2] The ETE SHOULD perform one-way performance measurement.

[R32] The ETE MUST perform two-way performance measurement.

MEF 26.1 [18] defines performance as one-way metrics for the OVC. These metrics are most
accurately measured using one-way measurements. In case one-way measurements cannot be
executed, the performance could be approximated using two-way measurements, and reported as
approximations of the one-way objective. Under no conditions should one-way metrics derived
from two–way measurements be reported as one-way metrics.

[R33] The method of measuring the metric (e.g., one-way, two-way) MUST be re-
ported with the measurements.

10.2 Service Acceptance Criteria Limits

As described in Section 7, the Service Acceptance Criteria apply to the Service Configuration
and Service Performance tests and provide pass or fail criteria on the basis of whether or not the
service meets it’s SAC during each test, and this per service attribute and per direction. These
criteria are allowable limits for each of the measured service attributes in the test, and are care-
fully selected to give the Service Provider and Access Provider confidence that a service that
passes its Service Activation Testing, according to the established SAC, will be a satisfactory
service that will meet its Class of Service Performance Objectives (CPOs) for the customer. As
already stated in this document, some differences may exist between the Service Acceptance Cri-
teria and the Class of Service Performance Objectives.

SAT Service Acceptance Criteria (SAC) are not equivalent to CPOs. CPOs are based on per-
formance of in-service OVCs over a 30-day time period; while SAC values are based on measur-
ing test frames transmitted for a limited time period, e.g., normally < 24 hours, before an OVC is
placed in-service. Due to this difference, the values contained in MEF 23.1 [17] for CPOs are
not directly applicable to SAC for an OVC1.

1
SP and AP can choose to use CPOs as defined in MEF 23.1 [17] for SAC. If they choose to make them more
stringent (which they should), they are not going against SAT. SAC as defined in SAT are just configurable
pass/fail criteria. The values for SAC are beyond the scope of this document.
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 32
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

[R34] The Service Acceptance Criteria (SAC) MUST be agreed upon by the Service
Provider and the Access Provider.

10.3 Service Configuration Tests

The objectives of the Service Configuration tests are to validate that the service is configured as
defined and consistent with E-Access services [20]. Figure 11 and Figure 12 provide a summary
view of the Service Configuration Testing process for the AP (Figure 11) and SP (Figure 12).

The Service Configuration tests for the AP are composed of 5 sub-processes that are designed to
ensure that the service is configured and documented correctly. These sub-processes are OVC
MTU size test, CE-VLAN ID Preservation test, CE VLAN CoS ID Preservation test, Broad-
cast/Unicast/Multicast Frame Delivery tests and Bandwidth Profile (BWP) tests. Each of these
sub-processes will be explained in details below.

The Service Configuration tests for the SP are composed of 5 sub-processes. These sub-
processes are OVC MTU size test, CE-VLAN ID Preservation test, CE VLAN CoS ID Preserva-
tion test, Broadcast/Unicast/Multicast Frame Delivery tests and Bandwidth Profile (BWP) tests.
The main difference between the SP and AP processes is the Frame Delivery tests that are op-
tional in the case of the SP processes.

Each sub-section below provides information on which service attributes are tested and reported,
or only reported, for SPs and APs, as described in Section 9.

Setup Test OVC MTU Pass CE VLAN ID Pass

Service Configuration Tests Preservation Test
Architecture Size Test

Fail Fail

Fail Fail

Frame
Troubleshoot CE VLAN CoS
Delivery
service ID Preservation
Pass Tests Pass Test

To
Complete Service
Pass Service
BWP Tests Performance
Configuration Tests
Test Report
Fail

Figure 11 – Service Configuration Test Process for Access Providers

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 33
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Setup Test OVC MTU Pass CE VLAN ID Pass

Service Configuration Tests Preservation Test
Architecture Size Test

Fail Fail

Fail Fail

Frame
Troubleshoot CE VLAN CoS
Delivery
service ID Preservation
Pass Tests Pass Test

To
Complete Service
Pass Service
BWP Tests Performance
Configuration Tests
Test Report
Fail

Optional Test

Figure 12 – Service Configuration Test Process for Service Providers

For each sub-section, a series of tables are added to clarify the methodology used to test each
service attribute. The following two tables provide a high level view of the common test re-
quirements for Access EPL (Table 11) and Access EVPL (Table 12) services [20].

Service Activation Test Methodology – Common Test Requirements – Access EPL

An OVC associating one OVC EP at the UNI and one OVC EP at the ENNI is configured as per the Service
Test Configu-
Definition. All CE-VLAN ID values are mapped to the OVC EP at the UNI and a specific S-VLAN ID is
ration
mapped to the OVC EP at the ENNI.
Access Provider Test Configuration:

Service Provider Test Configuration:

Test Configu-
ration Sche-
matic

Note 1: The ETE1 or ETE2 shown in the Test Configuration Schematic could be replaced by an LLF as an
alternative configuration. An example of such configuration can be found in Figure 9 D). Refer for section
8.1.2 for additional considerations.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 34
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Map at UNI
CE-VLAN ID OVC End Point
1,2…4095 OVC EP1
End Point
Maps Map at ENNI
S-VLAN ID OVC End Point
As per Service Definition OVC EP2

Ingress Bandwidth Profile per OVC EP at UNI

OVC End Point Parameters
OVC EP1 CIR1 CBS1 EIR1 EBS1 CF1 CM1
Note 1: CIR1 CBS1 EIR1 EBS1 CF1 CM1 as per Service Definition
Bandwidth
Profile Ingress Bandwidth Profile per OVC EP at ENNI
OVC End Point Parameters
OVC EP2 CIR2 CBS2 EIR2 EBS2 CF2 CM2
Note 1: CIR2 CBS2 EIR2 EBS2 CF2 CM2 as per Service Definition

Table 11 – SAT Methodology – Common Test Requirements for Access EPL Services

Service Activation Test Methodology – Common Test Requirements – Access EVPL

An OVC associating one OVC EP at the UNI and one OVC EP at the ENNI is configured as per the Service
Test Configu-
Definition. One or more CE-VLAN ID is mapped to the OVC EP at the UNI and a specific S-VLAN ID is
ration
mapped to the OVC EP at the ENNI.
Access Provider Test Configuration:

Service Provider Test Configuration:

Test Configu-
ration Sche-
matic

Note 1: The ETE1 or ETE2 shown in the Test Configuration Schematic could be replaced by an LLF as an
alternative configuration. An example of such configuration can be found in Figure 9 D). Refer for section
8.1.2 for additional considerations.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 35
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Map at UNI
CE-VLAN ID OVC End Point
As per Service Definition OVC EP1
End Point
Maps Map at ENNI
S-VLAN ID OVC End Point
As per Service Definition OVC EP2

Ingress Bandwidth Profile per OVC EP at UNI

OVC End Point Parameters
OVC EP1 CIR1 CBS1 EIR1 EBS1 CF1 CM1
Note 1: CIR1 CBS1 EIR1 EBS1 CF1 CM1 as per Service Definition
Bandwidth
Profile Ingress Bandwidth Profile per OVC EP at ENNI
OVC End Point Parameters
OVC EP2 CIR2 CBS2 EIR2 EBS2 CF2 CM2
Note 1: CIR2 CBS2 EIR2 EBS2 CF2 CM2 as per Service Definition

Table 12 – SAT Methodology – Common Test Requirements for Access EVPL Services
For the Service Configuration tests (excluding the BWP tests of section 10.3.5), a time duration
for a test is defined as TSC (Time Service Configuration).

[R35] The TSC MUST be configurable from at least 1 second up to 60 seconds.

10.3.1 OVC MTU Size Test

The Maximum Transmission Unit (MTU) size specifies the maximum frame length in bytes al-
lowed at an External Interface. The MTU is part of several attribute specifications. For example,
the OVC (defined in MEF 26.1 section 7.2.10 [18]) has an MTU attribute which needs to be val-
idated.

[R36] The Access Provider MUST test the OVC MTU size as per the methodology de-
fined in Table 13.

[R37] The Service Provider MUST test the OVC MTU size as per the methodology
defined in Table 13.

Table 13 below defines the test methodology to perform OVC MTU size test. This methodology
explains how the OVC MTU size test is used to test an Access EPL and Access EVPL services
[20].

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 36
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name OVC Maximum Transmission Unit size test

Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that for an Access EPL or Access EVPL service, the OVC Maximum Transmission Unit size is an
Test Object
integer number of bytes ≥ 1526.

Access EPL Service:

 ETE1 offers C-tagged Service Frames with CE-VLAN ID equal to 65 and frame size equal to the
OVC1 MTU size at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Access
Provider and Service Provider.
 ETE2 verifies that the Service Frames offered at the UNI are received double-tagged with S-VLAN
ID equal to the S-VLAN ID as defined in the Service Definition at the ENNI configured in OVC1
and validates the received OVC MTU size. Frame loss is acceptable up to FLRSAC, where FLRSAC is
the SAC for Frame Loss Ratio.
 Simultaneously, ETE2 offers double-tagged ENNI frames with CE-VLAN ID equal to 65 and S-
VLAN ID equal to the S-VLAN ID defined in the Service Definition and frame size equal to the
OVC1 MTU size at ENNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Ac-
cess Provider and Service Provider.
 ETE1 verifies that the ENNI Frames with S-VLAN ID equal to the S-VLAN ID defined in the Ser-
vice Definition offered at ENNI configured in OVC1 are received C-tagged with CE-VLAN ID
equal to 65 at UNI and validates the received OVC MTU size. Frame loss is acceptable up to FLR-
Test Proce-
SAC.
dure
Access EVPL Service:
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per Service Definition and frame size
equal to the OVC1 MTU size at UNI configured in OVC1 at a rate IRSC and for a time TSC defined
by the Access Provider and Service Provider.
 ETE2 verifies that the Service Frames offered at the UNI are received double-tagged with S-VLAN
ID equal to the S-VLAN ID as defined in the Service Definition at the ENNI configured in OVC1.
Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss Ratio.
 Simultaneously, ETE2 offers double-tagged ENNI frames with CE-VLAN ID as per Service Defi-
nition and S-VLAN ID equal to the S-VLAN ID defined in the Service Definition and frame size
equal to the OVC1 MTU size at ENNI configured in OVC1 at a rate IRSC and for a time TSC defined
by the Access Provider and Service Provider.
 ETE1 verifies that the ENNI Frames with S-VLAN ID equal to the S-VLAN ID as per Service Def-
inition offered at ENNI configured in OVC1 are received C-tagged with CE-VLAN ID equal to the
value in the Service Definition at the UNI. Frame loss is acceptable up to FLRSAC.

Units Number of valid frames received at the external interfaces

Variables OVC MTU size, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Note 1: OVC MTU size of the E-Access Service [20] under test is to be provided by the Access Provider.
Remarks Note 2: The OVC MTU size has to be ≤ to the MTU size of each External Interface where an OVC EP exists
that is associated by the OVC.

Table 13 – SAT Methodology – OVC MTU Size Test

10.3.2 CE-VLAN ID Preservation Test

CE-VLAN ID Preservation describes a relationship between the format and certain field values
of the frame at one External Interface and the format and certain field values of the correspond-
ing frame at another External Interface that allows the CE-VLAN ID value of the UNI Service

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 37
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Frame to be derived from the ENNI Frame and vice versa. MEF 26.1 Section 7.2.11 [18] pro-
vides a detailed explanation of CE-VLAN ID Preservation.

[R38] The Access Provider MUST test the CE-VLAN ID Preservation as per the
methodology defined in Table 14 for Access EPL or Table 15 for Access EVPL.

[R39] The Service Provider MUST test the CE-VLAN ID Preservation as per the
methodology defined in Table 14 for Access EPL or Table 15 for Access EVPL.

Table 14 and Table 15 below define the test methodology to perform CE-VLAN ID Preservation
test. This methodology explains how the CE-VLAN ID Preservation test is used to test Access
EPL and Access EVPL services [20]. For Access EVPL services [20], there are two test proce-
dures described, one for maximum number of CE-VLAN IDs per OVC equal to 1 (mandatory as
part of Access EVPL service definition [20]) and one procedure for CE-VLAN IDs per OVC
greater than 1 (optional as part of Access EVPL service definition [20]).

Service Activation Test Methodology

Test Name CE-VLAN ID Preservation test for Access EPL Services

Test Type Service Activation
Service Type Access EPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that for an Access EPL service, CE-VLAN IDs mapped to the OVC are preserved.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN IDs as per test definition at UNI configured
in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider and Service Provider.
(See Note 1)
 ETE2 verifies that the C-tagged Service Frames offered at UNI are delivered double-tagged with
CE-VLAN IDs as per test definition and S-VLAN ID as per Service Definition at the ENNI con-
Test Proce- figured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss
dure Ratio.
 Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN IDs as per test defini-
tion and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for a
time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the ENNI Frames offered at ENNI double-tagged with CE-VLAN IDs as per test
definition and S-VLAN ID as per Service Definition are received C-tagged at UNI configured in
OVC1 with CE-VLAN IDs as per Service Definition. Frame loss is acceptable up to FLRSAC.

Units CE-VLAN ID and S-VLAN ID values

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Note 1: For Access EPL testing, the test definition is for 4 VLAN IDs values to be tested: for example, one
at the beginning of the VLAN range (value = 1), 2 in the middle of the range (Value = 1024 and 2048) and 1
at the top end (Value = 4094). The values of the VLAN IDs are to be determined by the Access and Service
Remarks
Providers.
Note 2: CE-VLAN and S-VLAN formats are as specified for the C-TAG and S-TAG in IEEE Std 802.1QTM-
2011 sections 9.5 and 9.6 [3].

Table 14 – SAT Methodology – CE-VLAN ID Preservation Test for Access EPL Services

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 38
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name CE-VLAN ID Preservation test for Access EVPL Services

Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that for an Access EVPL service, the CE-VLAN ID mapped to the OVC is preserved.

For maximum number of CE-VLAN IDs per OVC = 1

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per service definition at UNI config-
ured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider and Service Provid-
er.
 ETE2 verifies that the C-tagged Service Frames offered at UNI are delivered double-tagged with
CE-VLAN ID as per service definition and S-VLAN ID as per Service Definition at the ENNI con-
figured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss
Ratio.
 Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN IDs as per service defi-
nition and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for
a time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the ENNI Frames offered at ENNI double-tagged with CE-VLAN IDs as per
service definition and S-VLAN ID as per Service Definition are received C-tagged at UNI config-
ured in OVC1 with CE-VLAN IDs as per Service Definition. Frame loss is acceptable up to FLR-
SAC.
Test Proce-
dure
For maximum number of CE-VLAN IDs per OVC > 1
 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN IDs as per test definition at UNI configured
in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider and Service Provider.
(See Note 1)
 ETE2 verifies that the C-tagged Service Frames offered at UNI are delivered double-tagged with
CE-VLAN IDs as per test definition and S-VLAN ID as per Service Definition at the ENNI con-
figured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss
Ratio.
 Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN IDs as per test defini-
tion and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for a
time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the ENNI Frames offered at ENNI double-tagged with CE-VLAN IDs as per test
definition and S-VLAN ID as per Service Definition are received C-tagged at UNI configured in
OVC1 with CE-VLAN IDs as per Service Definition. Frame loss is acceptable up to FLRSAC.
 The test procedure is repeated for each CE-VLAN ID to be tested.

Units CE-VLAN ID and S-VLAN ID values

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Note 1: For Access EVPL testing with maximum number of CE-VLAN IDs per OVC > 1, the values of the
CE-VLAN IDs are to be determined by the Access and Service Providers.
Remarks
Note 2: CE-VLAN and S-VLAN formats are as specified for the C-TAG and S-TAG in IEEE Std 802.1QTM-
2011 sections 9.5 and 9.6 [3].

Table 15 – SAT Methodology – CE-VLAN ID Preservation Test for Access EVPL Services

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 39
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
10.3.3 CE VLAN CoS ID Preservation Test

CE-VLAN CoS ID Preservation describes a relationship between the format and certain field
values of the frame at one External Interface and the format and certain field values of the corre-
sponding frame at another External Interface that allows the CE-VLAN CoS ID value of the UNI
Service Frame to be derived from the ENNI Frame and vice versa. MEF 26.1 Section 7.2.12
[18] provides a detailed explanation of CE-VLAN CoS ID Preservation.

[R40] The Access Provider MUST test the CE-VLAN CoS ID Preservation as per the
methodology defined in Table 16 for Access EPL or Table 17 for Access EVPL.

[R41] The Service Provider MUST test the CE-VLAN CoS ID Preservation as per the
methodology defined in Table 16 for Access EPL or Table 17 for Access EVPL.

As part of the CE-VLAN CoS ID Preservation test, the Class of Service Identifier for Service
Frames and the Class of Service Identifier for ENNI Frames are assessed. When a Service
Frame is mapped to an OVC end point, it is according to its CE-VLAN ID. When testing CE-
VLAN CoS ID Preservation, the mapping process of the Service Frame is tested. For this rea-
son, Class of Service IDs are by default tested as part of this test methodology.

Table 16 and Table 17 below define the test methodology to perform CE-VLAN CoS ID Preser-
vation test. This methodology explains how the CE-VLAN CoS ID Preservation test is used to
test an Access EPL and Access EVPL services.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 40
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name CE-VLAN CoS ID Preservation test for Access EPL Services
Test Type Service Activation
Service Type Access EPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that for an Access EPL service, all CE-VLAN CoS IDs mapped to the OVC are preserved.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID equal to 65 and CE-VLAN CoS ID equal
to 0 at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider
and Service Provider.
 ETE2 verifies that the C-tagged Service Frames offered at UNI are delivered double-tagged with
CE-VLAN ID equal to 65 and CE-VLAN CoS ID equal to 0 and S-VLAN ID as per Service Defi-
nition at the ENNI configured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is
the SAC for Frame Loss Ratio.
Test Proce-
 Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN ID equal to 65 and CE-
dure
VLAN CoS ID equal to 0 and S-VLAN ID as per Service Definition at ENNI configured in OVC1
at a rate IRSC and for a time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the ENNI Frames offered at ENNI double-tagged with CE-VLAN ID equal to 65
and CE-VLAN CoS ID equal to 0 and S-VLAN ID as per Service Definition are received C-tagged
at UNI configured in OVC1 with CE-VLAN ID equal to 65 and CE-VLAN CoS ID equal to 0.
Frame loss is acceptable up to FLRSAC.
 The test procedure is repeated by incrementing the CE-VLAN CoS ID by one until all CoS IDs are
tested.

Units CE-VLAN ID, CE-VLAN CoS ID and S-VLAN ID values

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
CE-VLAN and S-VLAN formats are as specified for the C-TAG and S-TAG in IEEE Std 802.1QTM-2011
Remark
sections 9.5 and 9.6 [3].

Table 16 – SAT Methodology – CE-VLAN CoS ID Preservation Test for Access EPL Ser-
vices

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 41
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name CE-VLAN CoS ID Preservation test for Access EVPL Services
Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that for an Access EVPL service, the CE-VLAN CoS IDs are preserved.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per Service Definition and CE-VLAN
CoS ID equal to 0 at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Ac-
cess Provider and Service Provider.
 ETE2 verifies that the C-tagged Service Frames offered at UNI are delivered double-tagged with
CE-VLAN ID as per Service Definition and CE-VLAN CoS ID equal to 0 and S-VLAN ID as per
Service Definition at the ENNI configured in OVC1. Frame loss is acceptable up to FLRSAC, where
FLRSAC is the SAC for Frame Loss Ratio.
Test Proce-  Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN ID as per Service Defi-
dure nition and CE-VLAN CoS ID equal to 0 and S-VLAN ID as per Service Definition at ENNI con-
figured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider and Service Pro-
vider.
 ETE1 verifies that the ENNI Frames offered at ENNI double-tagged with CE-VLAN ID as per Ser-
vice Definition and CE-VLAN CoS ID equal to 0 and S-VLAN ID as per Service Definition are re-
ceived C-tagged at UNI configured in OVC1 with CE-VLAN ID as per Service Definition and CE-
VLAN CoS ID equal to 0. Frame loss is acceptable up to FLR SAC.
 The test procedure is repeated by incrementing the CE-VLAN CoS ID by one until all CoS IDs are
tested (see note 1).

Units CE-VLAN ID, CE-VLAN CoS ID and S-VLAN ID values

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Note 1: For Access EVPL testing with maximum number of CE-VLAN IDs per OVC > 1, the test procedure
must be repeated for each value of the CE-VLAN IDs as determined by the Access and Service Providers.
Remarks
Note 2: CE-VLAN and S-VLAN formats are as specified for the C-TAG and S-TAG in IEEE Std 802.1QTM-
2011 sections 9.5 and 9.6 [3].

Table 17 – SAT Methodology – CE-VLAN CoS ID Preservation Test for Access EVPL Ser-
vices
10.3.4 Broadcast, Unicast, Multicast Frame Delivery Test

The goal of this test is to validate Broadcast, Unicast, and Multicast Service Frame Delivery
from UNI to ENNI and ENNI to UNI with parameters of Deliver Unconditionally. An ETE of-
fers Service Frames with IEEE 802.3 [2] frame formats at the UNI supporting the OVC to be
tested and verified.

[R42] OVC Data Service Frame Delivery tests MUST be performed during the Service
Configuration test.

The methodology to test the Broadcast, Unicast and Multicast Data Service Frame Delivery is
detailed in the following sub-sections.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 42
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

10.3.4.1 Broadcast Data Service Frame Delivery Test

The Broadcast Data Service Delivery attribute describes how ingress frames mapped to an OVC
End Point at an External Interface with the Broadcast destination MAC address are delivered to
the other End Points associated by the OVC. MEF 26.1 Section 7.2.19 [18] provides a detailed
explanation of the Broadcast Data Service Delivery attribute.

[R43] The Access Provider MUST test the Broadcast Data Service Delivery as per the
methodology defined in Table 18 for Access EPL or Table 19 for Access EVPL.

[O5] The Service Provider MAY test the Broadcast Data Service Delivery as per the
methodology defined in Table 18 for Access EPL or Table 19 for Access EVPL.

Table 18 and Table 19 below define the test methodology to perform Broadcast Data Service De-
livery test. This methodology explains how the Broadcast Data Service Delivery test is used to
test Access EPL and Access EVPL services [20].

The methodology presented below is defined for the Unconditional Delivery of Broadcast
Frames. If Delivered Conditionally, the Access Provider and Service Provider have to negotiate
the conditions for the delivery and the methodology to test. Conditional Delivery is beyond the
scope of this specification.

Service Activation Test Methodology

Test Name Broadcast Unconditional Frame Delivery Test for Access EPL Services
Test Type Service Activation
Service Type Access EPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EPL service, the Broadcast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID equal to 65 with Broadcast destination
address at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider
and Service Provider. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame
Loss Ratio.
 ETE2 verifies that the Broadcast C-tagged Service Frames offered at UNI are delivered double-
Test Proce- tagged with CE-VLAN ID equal to 65 and S-VLAN ID as per Service Definition at the ENNI con-
dure figured in OVC1.
 Simultaneously, ETE2 offers Broadcast double-tagged ENNI Frames with CE-VLAN ID equal to
65 and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for a
time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Broadcast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition are received C-tagged at UNI configured in
OVC1 with CE-VLAN ID equal to 65. Frame loss is acceptable up to FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark None

Table 18 – SAT Methodology – Broadcast Delivery Test for Access EPL Services

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 43
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name Broadcast Unconditional Frame Delivery Test for Access EVPL Services
Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EVPL service, the Broadcast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per Service Definition with Broadcast
destination address at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Ac-
cess Provider and Service Provider.
 ETE2 verifies that the Broadcast C-tagged Service Frames offered at UNI are delivered double-
tagged with CE-VLAN ID as per Service Definition and S-VLAN ID as per Service Definition at
the ENNI configured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC
Test Procedure for Frame Loss Ratio.
 Simultaneously, ETE2 offers Broadcast double-tagged ENNI Frames with CE-VLAN ID as per
Service Definition and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate
IRSC and for a time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Broadcast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID
as per Service Definition and S-VLAN ID as per Service Definition are received C-tagged at UNI
configured in OVC1 with CE-VLAN ID as per Service Definition. Frame loss is acceptable up to
FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark None

Table 19 – SAT Methodology – Broadcast Delivery Test for Access EVPL Services
10.3.4.2 Unicast Data Service Frame Delivery Test

The Unicast Data Service Delivery attribute describes how ingress frames mapped to an OVC
End Point at an External Interface with a Unicast destination MAC address of the remote ETE
are delivered to the other End Points associated by the OVC. MEF 26.1 Section 7.2.17 [18] pro-
vides a detailed explanation of the Unicast Data Service Delivery attribute.

[R44] The Access Provider MUST test the Unicast Data Service Delivery as per the
methodology defined in Table 20 for Access EPL or Table 21 for Access EVPL.

[O6] The Service Provider MAY test the Unicast Data Service Delivery as per the
methodology defined in Table 20 for Access EPL or Table 21 for Access EVPL.

Table 20 and Table 21 below define the test methodology to perform Unicast Data Service De-
livery test. This methodology explains how the Unicast Data Service Delivery test is used to test
an Access EPL and Access EVPL Services [20].

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 44
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

The methodology presented below is defined for the Unconditional Delivery of Unicast frames.
If Delivered Conditionally, the Access Provider and Service Provider have to negotiate the con-
ditions for the delivery and the methodology to test. Conditional Delivery is beyond the scope of
this specification.

Service Activation Test Methodology

Test Name Unicast Unconditional Frame Delivery Test for Access EPL Services
Test Type Service Activation
Service Type Access EPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EPL service, the Unicast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID equal to 65 with Unicast destination ad-
dress at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider
and Service Provider.
 ETE2 verifies that the Unicast C-tagged Service Frames offered at UNI are delivered double-tagged
with CE-VLAN ID equal to 65 and S-VLAN ID as per Service Definition at the ENNI configured
Test Proce-
in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss Ratio.
dure
 Simultaneously, ETE2 offers Unicast double-tagged ENNI Frames with CE-VLAN ID equal to 65
and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for a
time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Unicast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition are received C-tagged at UNI configured in
OVC1 with CE-VLAN ID equal to 65. Frame loss is acceptable up to FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark None

Table 20 – SAT Methodology – Unicast Delivery Test for Access EPL Services

Service Activation Test Methodology

Test Name Unicast Unconditional Frame Delivery Test for Access EVPL Services
Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EVPL service, the Unicast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per Service Definition with Unicast
destination address at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Ac-
Test Procedure cess Provider and Service Provider.
 ETE2 verifies that the Unicast C-tagged Service Frames offered at UNI are delivered double-tagged
with CE-VLAN ID as per Service Definition and S-VLAN ID as per Service Definition at the EN-
NI configured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for
Frame Loss Ratio.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 45
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
 Simultaneously, ETE2 offers Unicast double-tagged ENNI Frames with CE-VLAN ID as per Ser-
vice Definition and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate
IRSC and for a time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Unicast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID as
per Service Definition and S-VLAN ID as per Service Definition are received C-tagged at UNI
configured in OVC1 with CE-VLAN ID as per Service Definition. Frame loss is acceptable up to
FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark None

Table 21 – SAT Methodology – Unicast Delivery Test for Access EVPL Services
10.3.4.3 Multicast Data Service Frame Delivery Test

Multicast Data Service Delivery attribute describes how ingress frames mapped to an OVC End
Point at an External Interface with a Multicast destination MAC address (provided by the SP or
AP) are delivered to the other End Points associated by the OVC. MEF 26.1 Section 7.2.18 [18]
provides a detailed explanation of the Multicast Data Service Delivery attribute.

[R45] The Access Provider MUST test the Multicast Data Service Delivery as per the
methodology defined in Table 22 for Access EPL or Table 23 for Access EVPL.

[O7] The Service Provider MAY test the Multicast Data Service Delivery as per the
methodology defined in Table 22 for Access EPL or Table 23 for Access EVPL.

Table 22 and Table 23 below define the test methodology to perform Multicast Data Service De-
livery Test. This methodology explains how the Multicast Data Service Delivery Test is used to
test an Access EPL and Access EVPL Services [20].

The methodology presented below is defined for the Unconditional delivery of Multicast Frames.
If Delivered Conditionally, the Access Provider and Service Provider have to negotiate the con-
ditions for the delivery and the methodology to test. Conditional Delivery is beyond the scope of
this specification.

Service Activation Test Methodology

Test Name Multicast Unconditional Frame Delivery Test for Access EPL Services
Test Type Service Activation
Service Type Access EPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EPL service, the Multicast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
Test Proce-  ETE1 offers C-tagged Service Frames with CE-VLAN ID equal to 65 with Multicast destination
dure address at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Access Provider
and Service Provider.
 ETE2 verifies that the Multicast C-tagged Service Frames offered at UNI are delivered double-

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 46
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
tagged with CE-VLAN ID equal to 65 and S-VLAN ID as per Service Definition at the ENNI con-
figured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC for Frame Loss
Ratio.
 Simultaneously, ETE2 offers Multicast double-tagged ENNI Frames with CE-VLAN ID equal to 65
and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate IRSC and for a
time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Multicast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition are received C-tagged at UNI configured in
OVC1 with CE-VLAN ID equal to 65. Frame loss is acceptable up to FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark The Multicast frames are not to be Layer 2 Control Protocol (L2CP) Frames. See MEF L2CP [24] Table 2.

Table 22 – SAT Methodology – Multicast Delivery Test for Access EPL Services

Service Activation Test Methodology

Test Name Multicast Unconditional Frame Delivery Test for Access EVPL Services
Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Optional for Service Provider
Test Object Verify that for an Access EVPL service, the Multicast frames are Delivered Unconditionally.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames with CE-VLAN ID as per Service Definition with Multicast
destination address at UNI configured in OVC1 at a rate IRSC and for a time TSC defined by the Ac-
cess Provider and Service Provider.
 ETE2 verifies that the Multicast C-tagged Service Frames offered at UNI are delivered double-
tagged with CE-VLAN ID as per Service Definition and S-VLAN ID as per Service Definition at
the ENNI configured in OVC1. Frame loss is acceptable up to FLRSAC, where FLRSAC is the SAC
Test Procedure for Frame Loss Ratio.
 Simultaneously, ETE2 offers Multicast double-tagged ENNI Frames with CE-VLAN ID as per
Service Definition and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a rate
IRSC and for a time TSC defined by the Access Provider and Service Provider.
 ETE1 verifies that the Multicast ENNI Frames offered at ENNI double-tagged with CE-VLAN ID
as per Service Definition and S-VLAN ID as per Service Definition are received C-tagged at UNI
configured in OVC1 with CE-VLAN ID as per Service Definition. Frame loss is acceptable up to
FLRSAC.

Units Number of valid frames received at the external interfaces

Variables Service and ENNI Frame sizes, IRSC, test duration TSC and FLRSAC
Results Pass or fail
Remark The Multicast frames are not to be Layer 2 Control Protocol Frames. See MEF L2CP [24] Table 2.

Table 23 – SAT Methodology – Multicast Delivery Test for Access EVPL Services

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 47
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
10.3.5 Ingress Bandwidth Profile per OVC End Point Tests

The ingress Bandwidth Profile per OVC End Point describes ingress policing by the Operator
CEN on all ingress Service Frames or ENNI Frames mapped to a given OVC End Point. MEF
26.1 Section 7.5.4 (UNI) and MEF 26.1 Section 7.3.4 (ENNI) [18] provide a detailed explanation
of the ingress Bandwidth Profile per OVC End Point.

The goal of the ingress Bandwidth Profile per OVC End Point tests are to validate that the ser-
vice Bandwidth Profiles are configured as intended. The SAT methodology is derived from
ITU-T Recommendation Y.1564 [11].

The first step is to validate the CIR configuration of the E-Access service [20]. By offering Ser-
vice and ENNI Frames at the respective ingress Bandwidth Profiles at a rate of CIR and by ob-
serving the Frame Loss Ratio, it is possible to determine the Information Rate of the service. As
Service and ENNI Frames are being transmitted across the service, it will also be possible to
measure/calculate the performance service attributes as found in Table 8. Validating the perfor-
mance service attributes during the Service Configuration tests ensure that the tested service can
potentially pass the Service Performance tests as defined in Section 10.4.

The next step of the ingress Bandwidth Profile per OVC End Point tests is to validate the config-
uration of the EIR (if required by the Service Definition). During this step of the tests, Service
and ENNI Frames are offered at the External Interface at a rate of CIR + EIR. The goal of this
step is to validate that CIR + EIR can be carried by the service.

Finally, a Traffic Policing test will be performed to validate that the service is limited in band-
width as per the Service Definition.

An example of these steps is demonstrated in Figure 13. For the CIR step, the Information Rate,
FD/MFD, FDR/IFDV and FLR are measured/calculated.

After the EIR and traffic policing tests are performed, an optional burst size configuration test
can be executed. An example of a CBS and EBS configuration test is illustrated in Y.1564 Ap-
pendix I [11]. A normative methodology for CBS and EBS is for further study.

The burst configuration is verified first for the CBS, and then for the CBS and EBS together.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 48
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 13 – Service Configuration Test – Ingress Bandwidth Profile per OVC End Point
Test
Note 1 – The test steps demonstrated in Figure 13 represents the transmission rate as would be seen at the output of
the Ethernet Test Equipment.
Note 2 – Caution should be exercised when configuring the test time for the bandwidth profile test to make sure the
traffic policer has enough time to be exercised. Low Information Rate combined with high burst sizes require more
time for the traffic policing to take effect. Guidance on test time is for further study.
Note 3 – When testing CIR (or EIR) configuration with a large token bucket size for CBS (or EBS) and a low In-
formation Rate for the test traffic the token bucket might not go empty so as to verify the policing action. Addition-
ally, when testing token bucket size for CBS (or EBS) configuration sufficient idle time might be needed between
bursts to allow the token bucket to fill.

The Test Step Duration as presented in Figure 13 is defined as TBWD (Time BWD).

[R46] The Ethernet Test Equipment MUST have the possibility of configuring TBWD as
illustrated in Figure 13.

[R47] TBWD for each test step size MUST be configurable from at least 1 second up to
60 seconds as illustrated in Figure 13.

From MEF 10.3 [13], the Coupling Flag CF is set to either 0 or 1. The choice of the value for CF
has the effect of controlling the volume of the Service Frames that are declared Yellow. When
CF is set to 0, the long-term average bit rate of Service Frames that are declared Yellow is
bounded by EIR. When CF is set to 1, the long-term average bit rate of Service Frames that are
declared Yellow is bounded by CIR + EIR depending on volume of the offered Service Frames
that are declared Green. In both cases the burst size of the Service Frames that are declared Yel-
low is bounded by EBS. As per the Table 9 in Section 9.3, CF has a value of 0 or 1. Procedures
are available for 0 in this document. Procedures for 1 are left for further study.

The following steps provide the test procedure for verifying proper network configuration of the
ingress Bandwidth Profile per OVC End Point before proceeding to the Service Performance
tests.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 49
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

[O8] Utilized Line Rate (ULR) and Information Rate MAY be used to define and re-
port Bandwidth Profiles test parameters, results or information.

To simplify this procedure, only Information Rate will be used in the following sections.

The following sections list the test methodology to be used to test the Bandwidth Profile as per
the Service Definition.

[R48] Each of the tests listed in section 10.3.5 MUST be run separately when applica-
ble as per the Service Definition.

10.3.5.1 Ingress Bandwidth Profile per OVC End Point - CIR Configuration Test (Color-
aware)

The CIR Configuration test as part of the ingress Bandwidth Profile per OVC End Point Test val-
idates that the CIR Bandwidth Profile parameter is configured as per Service Definition. The
CIR test is valid for a Service Definition that is color-aware.

Table 24 provides the methodology to test the CIR configuration of the ingress Bandwidth Pro-
file per OVC End Point at the UNI and the ENNI.

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – CIR Test Color-aware
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI and the ENNI. The Bandwidth Profile is applied to all ingress Service and ENNI
Test Object
Frames that are mapped to the given OVC EP and the amount of Green traffic delivered at the OVC EP is
within SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers Green C-tagged Service Frames at a constant rate equal to CIR for a time TBWD. The
CE-VLAN ID is equal to 65 for Access EPL. For Access EVPL services, the CE-VLAN ID is as
per the Service Definition.
 ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, FLRMEAS-G,
the Frame Loss Ratio for Green frames, and FDMEAS/MFDMEAS-G, the Frame Delay/Mean Delay
for Green-colored frames. ETE2 also calculate IFDV/FDR from FDMEAS-G, the Inter-Frame Delay
Variation/Frame Delay Range for Green-colored frames.
 Simultaneously, ETE2 offers Green double-tagged ENNI Frames with CE-VLAN ID equal to 65
Test Proce-
and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant rate equal to
dure
CIR for a time TBWD. For Access EVPL services, the CE-VLAN ID is as per the Service Definition.
 ETE1 measures the received IRMEAS-G, the Information Rate of Green-colored frames, FLRMEAS-G,
the Frame Loss Ratio for Green frames and FDMEAS/MFDMEAS-G, the Frame Delay/Mean Delay for
Green-colored frames. ETE1 also calculate IFDV/FDR from FDMEAS-G, the Inter-Frame Delay Var-
iation/Frame Delay Range for Green-colored frames.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 If the IRMEAS-G, FLRMEAS-G, FDMEAS/MFDMEAS-G and IFDVMEAS/ FDRMEAS-G are all within the
limits specified by the SAC for ETE1 and ETE2, then the result is PASS. Proceed to the EIR con-
figuration test (10.3.5.3).

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 50
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
Results
ETE2 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G

Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green Color Identifiers defined in MEF 23.1 Table 4 [17].
Remarks
Note 3: The length of the time TBWD must be such that the number of bytes in CBS is negligible compared to
the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.

Table 24 – SAT Methodology –CIR Configuration Test (Color-aware)

10.3.5.2 Ingress Bandwidth Profile per OVC End Point - CIR Configuration Test (Color-
blind)

The CIR Configuration test as part of the ingress Bandwidth Profile per OVC End Point Test val-
idates that the CIR Bandwidth Profile parameter is configured as per Service Definition. The
CIR test is valid for a Service Definition that is color-blind.

Table 25 provides the methodology to test the CIR configuration of the ingress Bandwidth Pro-
file per OVC End Point at the UNI and the ENNI.

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – CIR Test Color-blind
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI and the ENNI. The Bandwidth Profile is applied to all ingress Service and ENNI
Test Object
Frames that are mapped to the given OVC EP and the amount of Green traffic delivered at the OVC EP is
within SAC.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 51
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames at a constant rate equal to CIR for a time TBWD. The CE-
VLAN ID is equal to 65 for Access EPL. For Access EVPL services, the CE-VLAN ID is as per
the Service Definition.
 ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, FLRMEAS-G,
the Frame Loss Ratio for Green frames, and FDMEAS/MFDMEAS-G, the Frame Delay/Mean Delay
for Green-colored frames. ETE2 also calculate IFDV/FDR from FDMEAS-G, the Inter-Frame Delay
Variation/Frame Delay Range for Green-colored frames.
Test Proce-
 Simultaneously, ETE2 offers Green double-tagged ENNI Frames with CE-VLAN ID equal to 65
dure
and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant rate equal to
CIR for a time TBWD. For Access EVPL services, the CE-VLAN ID is as per the Service Definition.
 ETE1 measures the received IRMEAS, FLRMEAS and FDMEAS/MFDMEAS. ETE1 also calculate
IFDV/FDR from FDMEAS.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 If the IRMEAS, FLRMEAS, FDMEAS/MFDMEAS and IFDVMEAS/ FDRMEAS for ETE1 and IRMEAS-G,
FLRMEAS-G, FDMEAS/MFDMEAS-G and IFDVMEAS/ FDRMEAS-G for ETE2 are all within the limits
specified by the SAC, then the result is PASS. Proceed to the EIR configuration test (10.3.5.4).

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR
FD or MFD
IFDV or FDR
FLR

Results ETE2 Results:

Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G

Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green Color Identifiers defined in MEF 23.1 Table 4 [17].
Remarks
Note 3: The length of the time TBWD must be such that the number of bytes in CBS is negligible compared to
the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.

Table 25 – SAT Methodology –CIR Configuration Test (Color-blind)

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 52
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

10.3.5.3 Ingress Bandwidth Profile per OVC End Point - EIR Configuration Test (Color-
aware)

The EIR Configuration test for a color-aware UNI as part of the ingress Bandwidth Profile per
OVC End Point Test validates that the EIR Bandwidth Profile Parameter is configured as per
Service Definition. The EIR test is valid for a Service Definition that is color-aware and the EIR
> 0 and EBS > 0. If the EIR = 0 and EBS = 0, proceed to Traffic Policing test (Section 10.3.5.5).
If the UNI is color-blind, proceed to Section 10.3.5.4.

Table 26 provides the methodology to test the EIR configuration of the ingress Bandwidth Pro-
file per OVC End Point at the UNI (color-aware) and the ENNI.

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test – Color-aware
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an Ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI (color-aware) and the ENNI. The Bandwidth Profile is applied to all ingress Ser-
Test Object
vice and ENNI Frames that are mapped to the given OVC EP and the amount of Green/Yellow traffic deliv-
ered at the OVC EP is within SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2
 ETE1 offers Green and Yellow C-tagged Service Frames at a constant rate equal to CIR for Green
frames and EIR for Yellow frames for a time TBWD. The CE-VLAN ID is equal to 65 for Access
EPL. For Access EVPL services, the CE-VLAN ID is as per the Service Definition.
 ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored frames,
FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.
 ETE2 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Green-colored frames, and IFDVMEAS-Y, the frame delay variation for Yellow-colored frames.
 Simultaneously, ETE2 offers Green and Yellow double-tagged ENNI Frames with CE-VLAN ID
Test Proce- equal to 65 and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant
dure rate equal to CIR for Green frames and EIR for Yellow frames for a time TBWD. For Access EVPL
services, the CE-VLAN ID is as per the Service Definition.
 ETE1 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored frames,
FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.
 ETE1 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Green-colored frames, and IFDVMEAS-Y, the frame delay variation for Yellow-colored frames.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 If IRMEAS-G, FD/MFDMEAS-G, IFDV/FDRMEAS-G and FLRMEAS-G are all within the limits speci-
fied by SAC for ETE1 and ETE2, then the result is PASS; proceed to the traffic policing test
(10.3.5.5).

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 53
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A N/A

Results
ETE2 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A N/A

Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green/Yellow Color Identifiers defined in MEF 23.1 Table 4 [17].
Note 3: The length of the time TBWD must be such that the number of bytes in CBS is negligible compared to
Remarks
the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.
Note 5: All the parameters associated with the Yellow-colored frames can be reported for reference purposes
only, because the SAC does not apply to Yellow-colored frames.

Table 26 – SAT Methodology – EIR Configuration Test (Color-aware)

10.3.5.4 Ingress Bandwidth Profile per OVC End Point - EIR Configuration Test (Color-
blind)

The EIR test for a color-blind UNI as part of the ingress Bandwidth Profile per OVC End Point
Test validates that the EIR Bandwidth Profile parameter is configured as per Service Definition.
The EIR test is valid for a Service Definition that is color-blind and the EIR > 0 and EBS > 0. If
the EIR = 0 and EBS = 0, proceed to Traffic Policing test (Section 10.3.5.5).

Table 27 provides the methodology to test the EIR configuration of the ingress Bandwidth Pro-
file per OVC End Point at the UNI (color-blind) and the ENNI.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 54
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test – Color-blind
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an Ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI (color-blind) and the ENNI. The Bandwidth Profile is applied to all ingress Ser-
Test Object
vice and ENNI Frames that are mapped to the given OVC EP and the amount of Green/Yellow traffic deliv-
ered at the OVC EP is within SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames at a constant rate equal to CIR+EIR for a time TBWD. The
CE-VLAN ID is equal to 65 for Access EPL. For Access EVPL services, the CE-VLAN ID is as
per the Service Definition.
 ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored frames,
FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.
 ETE2 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Test Proce- Green-colored frames, and IFDV/FDRMEAS-Y, the Inter-Frame Delay Variation/Frame Delay
dure Range for Yellow-colored frames.
 Simultaneously, ETE2 offers Green and Yellow double-tagged ENNI Frames with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant
rate equal to CIR for Green frames and EIR for Yellow frames for a time TBWD. For Access EVPL
services, the CE-VLAN ID is as per the Service Definition.
 ETE1 measures the received IRMEAS and FLRMEAS.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 For ETE1: If CIR*(1 – FLRSAC) ≤ IRMEAS ≤ CIR+EIR, then the result is PASS; proceed to the traf-
fic policing test (10.3.5.5).
 For ETE2: If CIR*(1 – FLRSAC) ≤ IRMEAS-T ≤ CIR+EIR, then the result is PASS; proceed to the
traffic policing test (10.3.5.5).

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR
FLR

ETE2 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
Results FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 55
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green/Yellow Color Identifiers defined in MEF 23.1 Table 4[17].
Note 3: The length of the time TBWD must be such that the number of bytes in CBS is negligible compared to
the total volume of traffic received over the duration of the test.
Remarks
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.
Note 5: All the parameters associated with the Yellow-colored frames can be reported for reference purposes
only, because the SAC does not apply to Yellow-colored frames.
Note 6: FD/MFDSAC and IFDV/FDRSAC are Not Applicable in a color-blind scenario as there is no method to
determine the color of the measured frame for ETE1.

Table 27 – SAT Methodology – EIR Configuration Test (Color-blind)

10.3.5.5 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test (Color-aware)

The Traffic Policing test for a color-aware UNI as part of the ingress Bandwidth Profile per OVC
End Point Test validates that the CIR and EIR Bandwidth Profile parameter are configured as per
Service Definition. The Traffic Policing test is valid for a Service Definition that is color-aware
and the CIR > 0 and EIR > 0 and CBS > 0 and EBS > 0.

[O9] The Traffic Policing test MAY be performed by the SP and the AP.

The Traffic Policing test is deemed optional so that there will be no overloading of the network
that would impact active services.

Table 28 provides the methodology to test the Traffic Policing configuration of the ingress
Bandwidth Profile per OVC End Point at the UNI (color-aware) and the ENNI.

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – Traffic Policing – Color-aware
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an Ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI (color-aware) and the ENNI. The Bandwidth Profile is applied to all ingress Ser-
Test Object
vice and ENNI Frames that are mapped to the given OVC EP and the amount of Green/Yellow traffic deliv-
ered at the OVC EP is within SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers Green and Yellow C-tagged Service Frames at a constant rate equal to CIR for Green
frames and 125% EIR for Yellow frames for a time TBWD. The CE-VLAN ID is equal to 65 for Ac-
cess EPL. For Access EVPL services, the CE-VLAN ID is as per the Service Definition. (See Note
7)
Test Proce-
 ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
dure
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Frame Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored
frames, FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.
 ETE2 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Green-colored frames, and IFDV/FDRMEAS-Y, the frame delay variation for Yellow-colored

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 56
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
frames.
 Simultaneously, ETE2 offers Green and Yellow double-tagged ENNI Frames with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant
rate equal to CIR for Green frames and 125% EIR for Yellow frames for a time TBWD. For Access
EVPL services, the CE-VLAN ID is as per the Service Definition. (See Note 7)
 ETE1 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored frames,
FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.
 ETE1 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Green-colored frames, and IFDV/FDRMEAS-Y, the frame delay variation for Yellow-colored
frames.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 If FLRMEAS-G, FDMEAS/MFDMEAS -G, IFDV/FDR MEAS -G, are all within the SAC limits, and if IR-
T ≤ CIR+EIR+M (see Note 6), then the result is PASS.

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A
Results
ETE2 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 57
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green/Yellow Color Identifiers defined in MEF 23.1 Table 4 [17].
Note 3: The length of the time TBWD must be such that the number of bytes in CBS is negligible compared to
the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.
Remarks
Note 5: Note that all the Yellow-colored parameters can be reported for reference purposes only, because the
SAC does not apply to Yellow-colored frames.
Note 6: The M factor is added to allow for the effect of the traffic policer's CBS and EBS settings, and test
time. Experience will determine the values for M. Additional guidance on M is for further study.
Note 7: Note that if EIR < 20%*CIR, then the transmitted frames would be 100%*CIR Green-marked frames
plus 25%*CIR Yellow-marked frames plus 100%*EIR Yellow-marked frames. This step was created to send
an adequate number of test frames to test the traffic policer. This test is only valid if the CIR + EIR ULR is
smaller than the interface ULR.

Table 28 – SAT Methodology – Traffic Policing Configuration Test (Color-aware)

10.3.5.6 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test (Color-blind)

The Traffic Policing Test for a color-blind UNI as part of the ingress Bandwidth Profile per OVC
End Point Test validates that the CIR and EIR Bandwidth Profile parameter are configured as per
Service Definition. The Traffic Policing test is valid for a Service Definition where the CIR > 0
and EIR > 0 and CBS > 0 and EBS>0.

[O10] The Traffic Policing test MAY be performed by the SP and the AP.

The Traffic Policing test is deemed optional so that there will be no overloading of the network
that would impact active services.

Table 29 provides the methodology to test the Traffic Policing configuration of the ingress
Bandwidth Profile per OVC End Point at the UNI (color-blind) and the ENNI.

Service Activation Test Methodology

Test Name Ingress Bandwidth Profile per OVC End Point – Traffic Policing – Color-blind
Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Verify that an Ingress Bandwidth Profile per OVC EP with BWP parameters defined in the Service Defini-
tion is in force at the UNI (color-blind) and the ENNI. The Bandwidth Profile is applied to all ingress Ser-
Test Object
vice and ENNI Frames that are mapped to the given OVC EP and the amount of Green/Yellow traffic deliv-
ered at the OVC EP is within SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames at a constant rate equal to CIR + 125% EIR for a time TBWD.
The CE-VLAN ID is equal to 65 for Access EPL. For Access EVPL services, the CE-VLAN ID is
Test Proce- as per the Service Definition. (See Note 4)
dure  ETE2 measures the received IRMEAS-G, the Information Rate of Green-colored frames, IRMEAS-Y,
the Information Rate of Yellow-colored frames, IRMEAS-T, the total combined Information Rate,
FLRMEAS-G, the Frame Loss Ratio for Green frames, FDMEAS/MFDMEAS -G, the Frame Delay/Mean
Delay for Green-colored frames, FLRMEAS-Y, the frame loss ratio for Yellow-colored frames,
FDMEAS/MFDMEAS -Y, the frame delay for Yellow-colored frames.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 58
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
 ETE2 also calculate IFDV/FDR MEAS-G, the Inter-Frame Delay Variation/Frame Delay Range for
Green-colored frames, and IFDV/FDRMEAS-Y, the frame delay variation for Yellow-colored
frames.
 Simultaneously, ETE2 offers Green and Yellow double-tagged ENNI Frames with CE-VLAN ID
equal to 65 and S-VLAN ID as per Service Definition at ENNI configured in OVC1 at a constant
rate equal to CIR for Green frames and 125% EIR for Yellow frames for a time TBWD. For Access
EVPL services, the CE-VLAN ID is as per the Service Definition. (See Note 8)
 ETE1 measures the received IRMEAS and FLRMEAS.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 For ETE1: If CIR*(1 – FLRSAC) ≤ IRMEAS ≤ CIR+EIR+M (see Note 7), then the result is PASS.
 For ETE2: If CIR*(1 – FLRSAC) ≤ IRMEAS-T ≤ CIR+EIR+M (see Note 7), then the result is PASS.

Units Information Rate: Mbit/s, Delay: ms

Service and ENNI Frame sizes, test step duration TBWD, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLR-
Variables
SAC

ETE1 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR
FLR

ETE2 Results:
Attribute Tested Measured/Calculated SAC value Pass/Fail
IR-G
Results FD-G or MFD-G
IFDV-G or FDR-
G
FLR-G
IR-Y N/A N/A
FD-Y or MFD-Y N/A N/A
IFDV-Y or FDR-
N/A N/A
Y
FLR-Y N/A N/A
IR-T N/A

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 59
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green/Yellow Color Identifiers defined in MEF 23.1 Table 4 [17].
Note 3: The length of the time TBWD is such that the number of bytes in CBS is negligible compared to the
total volume of traffic received over the duration of the test.
Note 4: If EIR < 20%*CIR, then the transmitted IR or ULR would be 125%*CIR + EIR. This step was creat-
ed to send an adequate number of test frames to test the traffic policer. This test is only valid if the CIR + EIR
ULR is smaller than the interface ULR.
Remarks Note 5: Note that all the Yellow-colored parameters can be reported for reference purposes only, because the
SAC does not apply to Yellow-colored frames.
Note 6: FD/MFDSAC and IFDV/FDRSAC are Not Applicable in a color-blind scenario as there is no method to
determine the color of the measured frame for ETE1.
Note 7: The M factor is added to allow for the effect of the traffic policer's CBS and EBS settings, and test
time. Experience will determine the values for M. Additional guidance on M is for further study.
Note 8: Note that if EIR < 20%*CIR, then the transmitted frames would be 100%*CIR Green-marked frames
plus 25%*CIR Yellow marked frames plus 100%*EIR Yellow-marked frames. This step was created to send
an adequate number of test frames to test the traffic policer. This test is only valid if the CIR + EIR ULR is
smaller than the interface ULR.

Table 29 – SAT Methodology – Traffic Policing Configuration Test (Color-blind)

10.3.5.7 Ingress Bandwidth Profile per OVC End Point –CBS/EBS Test

The goal of the CBS/EBS test is to validate the configuration of the CBS and EBS service attrib-
utes. The CBS/EBS test is optional and this testing is still considered experimental. The test
methodology for CBS and EBS testing is still for further study.

[O11] The SP and the AP MAY perform CBS and EBS testing based on an agreed up-
on methodology.

10.4 Service Performance Tests

As the Service Configuration tests were completed prior to this sub-process, the network is con-
figured correctly to deliver Ethernet-based services. The objective of the Service Performance
tests is to validate the quality of the service over time. In this phase of the test methodology, the
service attributes and all Ethernet performance parameters are measured simultaneously. This
means that the IR, FD/MFD, IFDV/FDR, and FLR are monitored for the service simultaneously.
In the case of multiple new Access EVPL services delivered between a single UNI and single
ENNI (as per Figure 5 of MEF 33 [20], all new services and their performance attributes would
be measured simultaneously. Figure 14 provides a graphical view of the Service Performance
tests for an Access EPL service [20]. Figure 15 provides a graphical view of the Service Perfor-
mance tests to test multiple Access EVPL services [20] simultaneously. Should there be a single
Access EVPL service [20] to test, the Service Performance tests process would be the same as an
Access EPL service [20], demonstrated in Figure 14.

This phase of the test methodology has a medium to long time duration. As the test duration has
implications on the performance parameters measured, certain durations are to be respected. The
test duration is detailed in section 10.4.1.

As part of the Service Performance tests, Service Providers can test the performance of the
transmission of Broadcast, Unicast and Multicast Service Frames if there are different service
configurations for these frame types.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 60
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service
Service Perfornance Tests Setup Test
Performance
Access EPL Architecture
Tests

Measure Calculate Generate

Measure FLR Measure IR
FD/MFD FDR/IFDV Test Traffic

No
Complete
Troubleshoot Fail Service meet Pass Test Service
service SAC? Completed? Performance
Yes
Tests Report

Return to
Service
Service Return
Activation Test
Configuration Service to
Completed
Tests pre-Test state

Figure 14 – Service Performance Tests Process – Access EPL

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 61
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service
Service Perfornance Tests Setup Test
Performance
Access EPL Architecture
Tests

Measure Calculate Generate

Measure FLR Measure IR
FD/MFD FDR/IFDV Test Traffic
Service #1 Service #1
Service #1 Service #1 Service #1

Measure Calculate Generate

Measure FLR Measure IR
FD/MFD FDR/IFDV Test Traffic
Service #n Service #n
Service #n Service #n Service #n

No
Complete
Troubleshoot Fail Services meet Pass Test Service
service SAC? Completed? Performance
Yes
Tests Report

Return to
Service
Service Return
Activation Test
Configuration Services to
Completed
Tests pre-Test state

Figure 15 – Service Performance Tests Process – Access EVPL

[R49] The Service Performance tests MUST be performed by the Access Provider.

[R50] The Service Performance tests MUST be performed by the Service Provider.

[D3] The Service Performance tests SHOULD incorporate one-way measurement of

the OVC performance service attributes as defined in MEF 26.1 [18].

Table 30 below provides a detailed methodology to test the performance attributes for single E-
Access service [20].

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 62
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Activation Test Methodology

Test Name Service Performance Tests – Single Service

Test Type Service Activation
Service Type Access EPL and Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that the Access EPL or Access EVPL service performs as per the Service Definition and meets SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames at a constant rate equal to CIR for a time TSP. The CE-
VLAN ID is equal to 65 for Access EPL. For Access EVPL services, the CE-VLAN ID is as per
the Service Definition.
 ETE2 measures the received IRMEAS, FLRMEAS and FDMEAS/MFDMEAS. ETE2 also calculate
IFDV/FDR from FDMEAS.
Test Proce-  Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN ID equal to 65 and S-
dure VLAN ID as per Service Definition at the ENNI configured in OVC1 at a constant rate equal to
CIR for a time TSP. For Access EVPL services, the CE-VLAN ID is as per the Service Definition.
 ETE1 measures the received IRMEAS, FLRMEAS and FDMEAS/MFDMEAS. ETE1 also calculate
IFDV/FDR from FDMEAS.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC.
 If the IRMEAS, FLRMEAS, FDMEAS/MFDMEAS and IFDVMEAS/ FDRMEAS are all within the limits speci-
fied by the SAC for ETE1 and ETE2, then the result is PASS.

Units Information Rate: Mbit/s, Delay: ms

Variables Service and ENNI Frame sizes, test duration TSP, IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC

ETE1 Results:
SAC value
Attribute Tested Measured/Calculated Pass/Fail
(See note 6)
IR
FD or MFD
IFDV or FDR
FLR
Results
ETE2 Results:
SAC value
Attribute Tested Measured/Calculated Pass/Fail
(See note 6)
IR
FD or MFD
IFDV or FDR
FLR

Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green Color Identifiers defined in MEF 23.1 Table 4 [17].
Note 3: The length of the time TSP has to be such that the number of bytes in CBS is negligible compared to
Remarks the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.
Note 5: Frames can be transmitted in units of IR bits per second, although transmission rate measured in Uti-
lized Line Rate (ULR) bits per second is also acceptable.
Note 6: Refer to Section 10.2 for guidance on SAC values.

Table 30 – SAT Methodology – Service Performance Tests – Single Service

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 63
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Table 31 below provides a detailed methodology to test the performance attributes for multiple
Access EVPL services [20] as described in Figure 5 of MEF 33 [20].

Service Activation Test Methodology

Test Name Service Performance Tests – Multiple Services

Test Type Service Activation
Service Type Access EVPL
Test Status Mandatory for Access Provider and Service Provider
Test Object Verify that the Access EVPL services perform as per the Service Definition and meets SAC.

 The frame size to be used for testing can be a single frame size or an EMIX as per Section 10.1.2.
 ETE1 offers C-tagged Service Frames at a constant rate equal to CIR for a time TSP with the CE-
VLAN ID as per the Service Definition and this for each service concurrently.
 ETE2 measures the received IRMEAS, FLRMEAS and FDMEAS/MFDMEAS. ETE2 also calculate
IFDV/FDR from FDMEAS for each service (i=service identifier, value of i = 1..n, where n is the
number of service to test).
 Simultaneously, ETE2 offers double-tagged ENNI Frames with CE-VLAN ID and S-VLAN ID as
Test Proce-
per Service Definition at the ENNI configured in OVC1 at a constant rate equal to CIR for a time
dure
interval T, and this for each service concurrently.
 ETE1 measures the received IRMEAS, FLRMEAS and FDMEAS/MFDMEAS. ETE1 also calculate
IFDV/FDR from FDMEAS for each service.
 IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC are the limits as specified as the SAC. SAC
are to be defined for each service.
 If the IRMEAS, FLRMEAS, FDMEAS/MFDMEAS and IFDVMEAS/ FDRMEAS are all within the limits speci-
fied by the SAC for ETE1 and ETE2 and for each service, then the result is PASS.

Units Information Rate: Mbit/s, Delay: ms

Variables Service and ENNI Frame sizes, test duration TSP IRSAC, FDSAC/MFDSAC, IFDVSAC/FDRSAC and FLRSAC

ETE1 Results:
Service #i
SAC value
Attribute Tested Measured/Calculated Pass/Fail
(See note 6)
IR
FD or MFD
IFDV or FDR
FLR

Results
ETE2 Results:
Service #i
SAC value
Attribute Tested Measured/Calculated Pass/Fail
(See note 6)
IR
FD or MFD
IFDV or FDR
FLR

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 64
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
Note 1: Bandwidth Profile is measured in terms of Service or ENNI Frame traffic where the Service or ENNI
Frame consists of the first bit of the destination MAC Address through the last bit of the Frame Check Se-
quence.
Note 2: Green Color Identifiers defined in MEF 23.1 Table 4 [17].
Note 3: The length of the time TSP has to be such that the number of bytes in CBS is negligible compared to
Remarks the total volume of traffic received over the duration of the test.
Note 4: Frames would be transmitted at constant intervals, e.g., without burstiness or interval variation. If
interval variation is present, it would be proportional to the size variation in the EMIX.
Note 5: Frames can be transmitted in units of IR bits per second, although transmission rate measured in Uti-
lized Line Rate (ULR) bits per second is also acceptable.
Note 6: Refer to Section 10.2 for guidance on SAC values.

Table 31 – SAT Methodology – Service Performance Tests – Multiple Services

10.4.1 Service Performance Tests Duration

The Service Performance tests duration is defined as TSP (Time Service Performance).

[R51] TSP MUST be negotiated between the Service Provider and Access Provider be-
fore SAT.

[R52] TSP MUST be reported.

[R53] The ETE MUST support TSP of Test15m (15 minutes), Test2h (2 hours) and
Test24h (24 hours).

There are four test durations defined in ITU-T M.2110 [9]. The continuity test is beyond the
scope of this document as the service under test has already been tested with the service configu-
ration tests. The applicable test durations are therefore Test15m, Test2h and Test24h. For exam-
ple, a Service Provider can test services for 15 minutes if the services are provided over a net-
work already carrying working traffic in a metro application. 2-hour test durations can be used
for services running over a multi Service Provider long-haul network. Finally, a 24-hour test du-
ration can be used for services which are being carried internationally over multiple Operator
networks.

11 Results

This section provides the requirements to create the SAT Record. SAT Records can be used for
SLA verification and validation prior to deploying the service under test to the customer.

Figure 16 provides a high level use case for the Service Activation Testing results process using
an automated Ethernet Test Support System (ETSS). SAT can also be performed without an au-
tomated ETSS; in this case, the user of the ETE used to test the service can enter the information
required to generate a SAT Record.

It is assumed that for the example use case SAT is actively running. Figure 16 represents a use
case where the ETE-TH ‘pushes’ the status up to the ETSS autonomously. When a test com-
pletes, the ETE-TH automatically notifies the ETSS that the specified test has finished. At this
point the ETSS can trigger querying the ETE-TH for the test results for the specified test. Once

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 65
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

the test results are obtained, they can be stored within a back office database and the SAT Record
can be generated.

Figure 16 – Test Results Use Case (Push Model)

11.1 Monitoring Test

This use case encompasses several scenarios that are applicable when SAT is actively running or
scheduled to run at a future point in time. A test result status is linked to a requested test.

A Service Provider can query, via an ETSS as shown in Figure 16, an ETE-TH and/or ETE-A to
determine the current test status. The management interface used to perform this query might be
SNMP or NETCONF, for example.

Autonomous events could be used to convey certain test status state changes as illustrated in
Figure 16. For example, a device might send an SNMP or NETCONF Notification to indicate a
test (with a given Test ID) has been completed. Similarly, an ETSS might show a visual indicator
that a test has completed execution.

An ETE-I might convey certain test status information via visual indicators such as LEDs or lo-
cal on-screen display information.
11.1.1 Determine Test Status

ETE-THs and ETE-As can support the following test statuses:

None This state correlates to the testing state where a test has never been run since the de-
vice or service was brought online from an initialization state.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 66
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Completed The requested test execution succeeded.

In Progress The requested test execution is still in progress.
Not Supported The requested test is not supported by the system and/or device.
Unable To The requested test cannot be executed. For example, a device has not met the pre-
Run conditions to execute the test (e.g., taken out-of-service).
Aborted A test was aborted, either manually by an Operator or automatically by a device due
to problems or error conditions. Results are not deemed acceptable. Within this
state, an Operator might be interested to determine if the test was aborted due to
manual intervention or due to device intervention. This might include the scenario
where a test timed out due to a control path communication error.
Failed The requested test execution has failed since the expected criteria, outcome and be-
havior was not met. For example, a measurement did not meet the expected criteria.
Unknown This state indicates the test result state is currently unknown.

Test status is key information included in the test reports, along with other correlational data.

ETE-THs and ETE-As might support autonomous events (e.g., SNMP Traps, NETCONF asyn-
chronous messages, etc.) to convey test status state changes.
11.1.2 Determine Test Result

The final test results can be reported for each test or suite of tests as defined in Section 10. Test-
ing results need to follow POSIX [1] test result ratings (such as PASS, FAIL, UNRESOLVED)
and multiple results can be rolled into a final test disposition. For example, a test that timed out
with a test execution failure would report a result of UNRESOLVED.

Test results are key information included in the test reports, along with other correlational data.

[R54] An Ethernet Test Support System MUST support reporting test results in the fol-
lowing POSIX [1] test result assertion codes:

 PASS

 FAIL

 UNTESTED

 UNSUPPORTED

 NOT_APPLICABLE

 NOT_TESTABLE

 UNRESOLVED

 NOT_INITIATED

[D4] An Ethernet Test Equipment SHOULD support reporting test results in the
POSIX [1] test result assertion codes.
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 67
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
11.1.3 Test Report

This section provides the requirements that are to be used for the creation of the SAT Records.
Section 9 identifies the MEF service attributes which are to be included as part of the SAT Rec-
ord. Other information will also be necessary in the SAT Record such as a record name, start
time, end time, etc.

Test automation being a goal for Service Providers, an XML Service Activation Test Report is to
be generated for back office applications to be able to parse and understand the reports and be
able to generate reports in other formats such as PDF, Word, Excel, etc. By providing a stand-
ardized SAT Record format in XML, many different applications and processes can parse and
utilize the information contained with-in the report.

As the example use case in this section highlights, the ETE might provide test result and status
data to an Ethernet Test Support System (ETSS) or Element Management System (EMS) using
other management protocols, including SNMP, NETCONF, XML or vendor proprietary meth-
ods. These ETSS and EMS applications, in turn, will aggregate the test result and status infor-
mation and generate the SAT Record in XML. If an automated ETSS is not used, the user of the
ETE will need to input manually the parameters to be able to create the Service Activation Test
Records.

[R55] The SAT Record MUST support test report generation based on XML.

[O12] SAT Record MAY support test report generation based on other reporting for-
mats as agreed to by the two involved parties.

A detailed definition of the SAT Record in XML is for further study. An example of a Service
Activation Test Record is presented in a table format in Appendix B.

12 Terminology Alignment
12.1 ITU-T Y.1563

ITU-T Recommendation Y.1563 [10] defines the parameters that may be used in specifying and
assessing the performance of speed, accuracy, dependability and availability of Ethernet frame
transfer of an Ethernet communication service.

ITU-T Y.1563 [10] defines a Measurement Point (MP) as a boundary between a bridge and an
adjacent link at which performance reference events can be observed and measured. A section or
a combination of sections is measurable if it is bounded by a set of MPs.

This definition differs from this specification as the SAMP definition is more precise as it locates
the measurement point with regards to the ESCF/EPCF. The SAMP location is presented in Sec-
tion 8.1.1 of this specification.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 68
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

13 References

[1] IEEE Std 1003.3-1991, IEEE Standard for Information Technology-Test Methods for
Measuring Conformance to POSIX, 1991.

[2] IEEE Std 802.3TM – 2012, IEEE Standard for Ethernet, December 2012.

[3] IEEE Std 802.1QTM – 2011, Media Access Control (MAC) Bridges and Virtual Bridge
Local Area Networks

[4] IETF RFC 1242, Benchmarking Terminology for Network Interconnection Devices, Ju-
ly 1991.

[5] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March
1997.

[6] IETF RFC 2544, Benchmarking Methodology for Network Interconnect Devices,
March 1999.

[7] IETF RFC 6815, Applicability Statement for RFC 2544: Use on Production Networks
Considered Harmful, November 2012.

[8] IETF RFC 6985, IMIX Genome: Specification of Variable Packet Sizes for Additional
Testing, July 2013.

[9] ITU-T Recommendation M.2110, Bringing into service international multi-operator

paths, sections and transmission systems, July 2002.

[10] ITU-T Recommendation Y.1563 (2009), Ethernet frame transfer and availability per-
formance, plus Amendment 1 (2009).

[11] ITU-T Recommendation Y.1564, Ethernet service activation test methodology, March
2011.

[12] MEF 4, Metro Ethernet Network Architecture Framework - Part 1: Generic Framework,
May 2004.

[13] MEF 10.3, Ethernet Services Attributes Phase 3, October 2013.

[14] MEF 12.2, Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services
Layer, April 2014.

[15] MEF 15, Requirements for Management of Metro Ethernet Phase 1 Network Elements,
November 2005.

[16] MEF 17, Service OAM Requirements & Framework – Phase 1, April 2007.

[17] MEF 23.1, Carrier Ethernet Class of Service – Phase 2, January 2012.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 69
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

[18] MEF 26.1, External Network Network Interface (ENNI) -- Phase 2, January 2012.

[19] MEF 30.1, Service OAM Fault Management Implementation Agreement: Phase 2,
April 2013.

[20] MEF 33, Ethernet Access Services Definition, January 2012.

[21] MEF 35, Service OAM Performance Monitoring Implementation Agreement, April
2012.

[22] MEF 37, Abstract Test Suite for ENNI, January 2012

[23] MEF 46, Latching Loopback Protocol and Functionality, July 2014

[24] MEF L2CP, Multi-CEN L2CP, July 2014

[25] OMG Unified Modeling Language™ (OMG UML), Superstructure, Version 2.3, May
2010, http://www.omg.org/spec/UML/2.3/Superstructure.

[26] OMG Unified Modeling Language™ (OMG UML), Infrastructure, Version 2.3, May
2010, http://www.omg.org/spec/UML/2.3/Infrastructure.

[27] Business Process Framework (eTOM), Addendum DX: Extended Process Decomposi-
tions and Descriptions, GB921 Addendum DX, Version 12.3, TM Forum, April 2012.

Appendix A Special Use Cases when performing SAT on MEF Ser-

vices (Informative)
A.1 E-Access Use Cases

This section identifies E-Access [20] use cases. They are specific to testing a new Access EPL
or Access EVPL service [20] being activated on an existing ENNI that a Service Provider has
with an Access Provider.

These use cases also assume that there is only an Access Provider NID at the customer premise,
although the addition of a Service Provider NID would not substantially change the use cases.

A.1.1 Cooperative Service Activation Testing by Service and Access Providers

The use case shown in Figure 17 assumes that the final joint OVC testing session is coordinated
between the Service Provider and Access Provider, requiring joint planning of resources needed
for the test at both locations. In addition to personnel and schedule coordination, the SP and AP
need to have compatible (interoperable) ETEs if they are to source and sink traffic in each direc-
tion. In addition to compatible ETEs, if one-way delay measurements are to be made the ETEs
will need to have access to Time-of-Day (ToD) clock sources to synchronize time stamping at
the source and sink ETEs. The Service Provider needs to be able to source and sink test traffic
on a single OVC on an ENNI without disturbing any of the in-service traffic on that interface.
The Access Provider ETE is beyond their NID so that test traffic flows past the Traffic Condi-
tioning Point (TrCP) and properly measures behavior of the customer circuit. In this use case, the
MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 70
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Service Provider initiates and controls the testing from the ETE-TH. The ETE-I at the Access
Provider’s UNI could also be replaced with an ETE-A at the UNI-N to support the one-way co-
ordinated testing.

Figure 17 – SAT performed “cooperatively” by Service & Access Providers

A.1.2 Service Activation Testing with an existing EVC at the UNI

SAT for an OVC might need to be performed differently when there is an existing EVC at a UNI
(Access EVPL service [20]). This is due to the desire to not adversely impact the existing in-
service EVC. If an ETE-I is used to perform the testing at the UNI that has existing customer
traffic, the ETE-I is connected to the UNI-N, which likely breaks the connection between the
UNI-N and the UNI-C. This, of course, affects any EVC that already exist on a UNI. To avoid
the impact of using an ETE-I at a UNI-N that already has in-service EVCs, a different method is
recommended such as a Latching Loopback (LL) or an ETE-A.

Even when an ETE-I is not used, the existing EVC can be impacted by testing of a new OVC
being activated. This is due to the customer sending frames from the UNI-C at the same time
that frames are either being generated by the ETE-A or looped back at the UNI-N. Since the
customer’s equipment is not aware of the test frames, they may continue to send frames up to the
CBS of their existing services while SAT is underway. If SAT is concurrently sending bursts of
frames, the customer may experience additional delay or frame loss on the existing EVC and the
SAT may experience additional delay that could cause SAT to fail. Figure 18 provides an exam-
ple of this use case where one EVC is in-service and one OVC is being activated. Each EVC and
OVC have a CIR of 40 Mb/s and a CBS of 40 KB. All physical interfaces in this example are
100 Mb/s.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 71
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Figure 18 – Congestion Due to SAT using Latching Loopback (LL)

As can be seen in the use case above, a full BWP test run while a customer is sending Service
Frames at line rate causes congestion since the egress port can support only 100 Mb/s. A similar
issue exists if an ETE-A is used versus a LL. Service Frames and test traffic will contend for the
same upstream bandwidth and additional Frame Delay or Inter-Frame Delay Variation may be
experienced. An example of this is shown in Figure 19.

Figure 19 – Congestion Due to SAT using Ethernet Test Equipment-Application

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 72
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Appendix B SAT Record example (Informative)

This appendix presents a table view of a SAT Record. The test record includes the test infor-
mation (date, time, etc…), reportable service attributes that are not tested and results from testing
the service attributes. These records are to be included for Service Configuration and Service
Performance Tests.

B.1 Access Provider SAT Record

This part of the appendix covers SAT Record from an Access Provider’s perspective. Each part
of the AP’s SAT Record is covered in a sub-section. The complete AP SAT Record would
merge all the different tables into a single record. Each sub-section provides an example of a
record for each reportable service attribute or test configuration and results. Differences between
different E-Access services [20] tested will be explained in each sub-section, when necessary,
without having a table for each possible use case.

B.1.1 UNI Service Attributes Record

Table 32 below provides an example of the UNI service attributes record for an AP.

UNI Service Attribute Value

UNI Identifier MTRL333-Node3-Slot2-Port1

Physical Medium 1000BASE-SX
Speed 1 Gb/s
Auto-Negotiation Auto
Mode Full Duplex
UNI MTU Size (byte) 1522

Table 32 – UNI Service Attributes Record Example

B.1.2 OVC per UNI Service Attributes Record

Table 33 below provides an example of the OVC per UNI service attributes record for an AP.

OVC per UNI Service Attribute Value

UNI OVC Identifier MTRL333-Node3-Slot2-Port1-OVC-0001965-ACME-MEGAMART

CE VLAN ID OVC EP
OVC End Point Map
All 1

Table 33 – OVC per UNI Service Attributes Record Example

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 73
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
B.1.3 OVC Service Attributes Record

Table 34 below provides an example of the OVC service attributes record for an AP.

OVC Service Attributes Value

OVC Identifier OVC-0001965-ACME-MEGAMART

Color Forwarding Yes

Table 34 – OVC Service Attributes Record Example

B.1.4 OVC End Point per ENNI Service Attributes Record

Table 35 below provides an example of the OVC per ENNI service attributes record for an AP.

OVC End Point per ENNI Service

Value
Attribute
OVC End Point Identifier MMART1965

Table 35 – OVC End Point per ENNI Service Attribute Record Example

B.1.5 ENNI Service Attributes Record

Table 36 below provides an example of the ENNI service attributes record for an AP.

OVC End Point per ENNI Service

Value
Attribute
Operator ENNI Identifier ENNI-MTRL Central Exchange_14-0624

Table 36 –ENNI Service Attribute Record Example

B.1.6 Access EPL Service Definition Record

Table 37 below provides an example of an Access EPL Service Definition record for an AP.

Access EPL Service Definition Value

OVC End Point Map at UNI

CE-VLAN ID OVC End Point
All 1
End Points Map
OVC End Point Map at ENNI
S-VLAN ID OVC End Point
65 50
Ingress Bandwidth Profile per OVC CIR 100 Mb/s

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 74
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
EP at UNI CBS 12 KB
EIR 50 Mb/s
EBS 6 KB
CF Yes
CM Blind
CIR 100 Mb/s
CBS 12 KB
Ingress Bandwidth Profile per OVC EIR 50 Mb/s
EP at ENNI EBS 6 KB
CF Yes
CM Aware

Table 37 – Access EPL Service Definition Record Example

B.1.7 Service Acceptance Criteria Record

Table 38 below provides an example of the Service Acceptance Criteria for an AP.

Service Acceptance Criteria Value

Information Rate (IRSAC) 100 Mb/s

Mean Frame Delay (MFDSAC) 25 ms
Inter-Frame Delay Variation
10 ms
(IFDVSAC)
Frame Loss Ratio (FLRSAC) 10-4

Table 38 – Service Acceptance Criteria Record Example

B.1.8 EMIX Frame Size Configuration Test Record

Table 39 below provides an example of the EMIX Frame Size configuration test record for an
AP.

EMIX Frame Size Configuration Value

EMIX Definition a b c d e f g h u
EMIX size (byte) 64 128 256 512 1024 1280 1518 1526 576

Table 39 – EMIX Frame Size Configuration Record Example

B.1.9 OVC MTU Size Test Record

Table 40 below provides an example of the OVC MTU Size test record for an AP.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 75
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

OVC MTU Size Test Configuration

Value
Parameters
Test Frame Size (byte) 1526
Test Frame Type Unicast
Test Information Rate (IRSC) 50 Mb/s
Test Duration (TSC) 1 sec
Frame Loss Ratio (FLRSAC) 10-4
OVC MTU Size Test Results Results
Verdict
ETE1 TX Service Frames 4095 -
ETE1 RX Service Frames 4095 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 4095 -
ETE2 RX Service Frames 4095 -
ETE2 – ETE1 One-way FLR 0 PASS
OVC MTU Size Test Verdict PASS

Table 40 – OVC MTU Size Test Record Example

B.1.10 CE-VLAN ID Preservation Test Record – Access EPL

Table 41 below provides an example of the CE-VLAN ID Preservation test record for an Access
EPL service for an AP.

In the case of an Access EVPL service [20], Table 41 would only list the CE-VLAN ID tested
(CE-VLAN IDs per OVC = 1 or CE-VLAN IDs per OVC > 1).

CE-VLAN ID Preservation Test

Value
Configuration Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Information Rate (IRSC) 50 Mb/s
Test Duration (TSC) 1 sec
Frame Loss Ratio (FLRSAC) 10-4
CE-VLAN ID Preservation Results Results
CE VLAN ID 1
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 76
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE2 RX Service Frames 7926 -

ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN ID 1024
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN ID 2048
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN ID 4094
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE-VLAN ID Preservation Test Ver-
PASS
dict

Table 41 – CE-VLAN ID Preservation Test Record – Access EPL

B.1.11 CE-VLAN CoS ID Preservation Test Record

Table 42 below provides an example of the CE-VLAN CoS ID Preservation test record for an
AP.

CE-VLAN CoS ID Preservation

Value
Test Configuration Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Information Rate (IRSC) 50 Mb/s

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 77
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Test Duration (TSC) 1 sec

Frame Loss Ratio (FLRSAC) 10-4
CE-VLAN CoS ID Preservation
Results
Results
CE VLAN CoS ID 0
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 1
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 2
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 3
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 4
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 78
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE2 TX Service Frames 7926 -

ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 5
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 6
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE VLAN CoS ID 7
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
CE-VLAN CoS ID Preservation Test
PASS
Verdict

Table 42 – CE-VLAN CoS ID Preservation Test Record

B.1.12 Broadcast Delivery Test Record

Table 43 below provides an example of the Broadcast Delivery test record for an AP.

Broadcast Unconditional Delivery

Value
Test Configuration Parameters
Test Frame Size (byte) EMIX
Test Frame Type Broadcast
EMIX abcdefgh
Test Information Rate (IRSC) 31.5 Kb/s

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 79
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

Test Duration (TSC) 1 sec

Frame Loss Ratio (FLRSAC) 10-4
Broadcast Unconditional Delivery
Results
Test Configuration Results
Verdict
ETE1 TX Service Frames 5 -
ETE1 RX Service Frames 5 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 5 -
ETE2 RX Service Frames 5 -
ETE2 – ETE1 One-way FLR 0 PASS
Broadcast Unconditional Delivery
PASS
Test Verdict

Table 43 – Broadcast Delivery Test Record Example

B.1.13 Unicast Delivery Test Record

Table 44 below provides an example of the Unicast Delivery test record for an AP.

Unicast Unconditional Delivery Test

Value
Configuration Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Information Rate (IRSC) 50 Mb/s
Test Duration (TSC) 1 sec
Frame Loss Ratio (FLRSAC) 10-4
Unicast Unconditional Delivery Test
Results
Configuration Results
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
Unicast Unconditional Delivery Test
PASS
Verdict

Table 44 – Unicast Delivery Test Record Example

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 80
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
B.1.14 Multicast Delivery Test Record

Table 45 below provides an example of the Multicast Delivery test record for an AP.

Multicast Unconditional Delivery

Value
Test Configuration Parameters
Test Frame Size (byte) EMIX
Test Frame Type Multicast
EMIX abcdefgh
Test Information Rate (IRSC) 50 Mb/s
Test Duration (TSC) 1 sec
Frame Loss Ratio (FLRSAC) 10-4
Multicast Unconditional Delivery
Results
Test Configuration Results
Verdict
ETE1 TX Service Frames 7926 -
ETE1 RX Service Frames 7926 -
ETE1 – ETE2 One-way FLR 0 PASS
ETE2 TX Service Frames 7926 -
ETE2 RX Service Frames 7926 -
ETE2 – ETE1 One-way FLR 0 PASS
Multicast Unconditional Delivery Test
PASS
Verdict

Table 45 – Multicast Delivery Test Record Example

B.1.15 Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test Record

Table 46 below provides an example of the ingress Bandwidth Profile per OVC End Point – CIR
Configuration Test (Color-blind) record for an AP.

Ingress Bandwidth Profile per OVC

End Point – CIR Configuration Test Value
Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Step Duration (TBWD) 10 sec
Ingress Bandwidth Profile per OVC
End Point – CIR Configuration Test Results
Result
Verdict
ETE1 One-way IRMEAS 100 Mb/s PASS
ETE1 One-way MFDMEAS 18 PASS

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 81
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE1 One-Way IFDVMEAS 6 PASS

ETE1 One-way FLRMEAS 0 PASS
ETE2 One-way IRMEAS-G 100 Mb/s PASS
ETE2 One-way MFDMEAS-G 19 PASS
ETE2 One-way IFDVMEAS-G 7 PASS
ETE2 One-Way FLRMEAS-G 0 PASS
Ingress Bandwidth Profile per OVC
End Point – CIR Configuration Test - PASS
Verdict

Table 46 – Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test (Col-
or-blind) Record Example

B.1.16 Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test Record

Table 47 below provides an example of the ingress Bandwidth Profile per OVC End Point – EIR
Configuration Test (Color-aware) record for an AP.

In the case of the color-blind EIR Configuration Test presented in Table 27, the ETE1 would on-
ly list the different results without color (IRMEAS and FLRMEAS).

Ingress Bandwidth Profile per OVC

End Point – EIR Configuration Test Value
(Color-aware) Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Step Duration (TBWD) 10 sec
Ingress Bandwidth Profile per OVC
End Point – EIR Configuration Test Results
(Color-aware) Result
Verdict
ETE1 One-way IRMEAS-G 100 Mb/s PASS
ETE1 One-way IRMEAS-Y 32 Mb/s N/A
ETE1 One-way IRMEAS-T 132 Mb/s PASS
ETE1 One-way MFDMEAS-G 18 PASS
ETE1 One-way MFDMEAS-Y 22 N/A
ETE1 One-way IFDVMEAS-G 6 PASS
ETE1 One-way IFDVMEAS-Y 9 N/A
ETE1 One-Way FLRMEAS-G 0 PASS
-1
ETE1 One-Way FLRMEAS-Y 5.625 x 10 N/A
ETE2 One-way IRMEAS-G 100 Mb/s PASS
ETE2 One-way IRMEAS-Y 16 Mb/s N/A
ETE2 One-way IRMEAS-T 116 Mb/s PASS

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 82
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE2 One-way MFDMEAS-G 19 PASS

ETE2 One-way MFDMEAS-Y 25 N/A
ETE2 One-way IFDVMEAS-G 7 PASS
ETE2 One-way IFDVMEAS-Y 10 N/A
ETE2 One-Way FLRMEAS-G 0 PASS
-1
ETE2 One-Way FLRMEAS-Y 6.8 x 10 N/A
Ingress Bandwidth Profile per OVC
End Point – EIR Configuration Test - PASS
Verdict

Table 47 – Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test (Col-
or-aware) Record Example

B.1.17 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test Record

Table 48 below provides an example of the ingress Bandwidth Profile per OVC End Point –
Traffic Policing Test (color-aware) test record for an AP.

In the case of the color-blind Traffic Policing Test presented in Table 29, the ETE1 would only
list the different results without color (IRMEAS and FLRMEAS).

Ingress Bandwidth Profile per OVC

End Point – Traffic Policing Test Value
(Color-aware) Parameters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Step Duration (TBWD) 10 sec
Ingress Bandwidth Profile per OVC
End Point – Traffic Policing Test Results
(Color-aware) Result
Verdict
ETE1 One-way IRMEAS-G 100 Mb/s PASS
ETE1 One-way IRMEAS-Y 32 Mb/s N/A
ETE1 One-way IRMEAS-T 132 Mb/s PASS
ETE1 One-way MFDMEAS-G 18 PASS
ETE1 One-way MFDMEAS-Y 22 N/A
ETE1 One-way IFDVMEAS-G 6 PASS
ETE1 One-way IFDVMEAS-Y 9 N/A
ETE1 One-Way FLRMEAS-G 0 PASS
-1
ETE1 One-Way FLRMEAS-Y 5.625 x 10 N/A
ETE2 One-way IRMEAS-G 100 Mb/s PASS
ETE2 One-way IRMEAS-Y 16 Mb/s N/A
ETE2 One-way IRMEAS-T 116 Mb/s PASS

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 83
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

ETE2 One-way MFDMEAS-G 0 PASS

-1
ETE2 One-way MFDMEAS-Y 6.8 x 10 N/A
ETE2 One-way IFDVMEAS-G 19 PASS
ETE2 One-way IFDVMEAS-Y 25 N/A
ETE2 One-Way MFDMEAS-G 7 PASS
ETE2 One-Way MFDMEAS-Y 10 N/A
Ingress Bandwidth Profile per OVC
End Point – Traffic Policing Test - PASS
(Color-aware) Verdict

Table 48 – Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test (Color-
aware) Record Example

B.1.18 Service Performance Tests Record – Access EPL

Table 49 below provides an example of the Service Performance test record for an AP.

In the case of the Access EVPL with multiple services presented in Table 31, the results would
be listed for Service #1 to Service #i.

Service Performance Tests Parame-

Value
ters
Test Frame Size (byte) EMIX
Test Frame Type Unicast
EMIX abcdefgh
Test Duration (TSP) 15 min.
Service Performance Tests Result Results
Service #1 Verdict
ETE1 One-way IRMEAS 100 Mb/s PASS
ETE1 One-way MFDMEAS 18 PASS
ETE1 One-way IFDVMEAS 6 PASS
ETE1 One-Way FLRMEAS 0 PASS
ETE2 One-way IRMEAS 100 Mb/s PASS
ETE2 One-way MFDMEAS 19 PASS
ETE2 One-way IFDVMEAS 7 PASS
ETE2 One-Way FLRMEAS 0 PASS
Service Performance Tests Verdict - PASS

Table 49 – Service Performance Tests Record – Access EPL Example

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 84
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)

B.2 Service Provider Service Activation Testing Record

This part of the appendix covers SAT Record from a Service Provider’s perspective. The com-
plete SP SAT Record would merge all the different tables into a single record. Each sub-section
provides an example of a record for each reportable service attribute or test configuration and
results. Differences between different E-Access services [20] tested or from the AP SAT Record
will be explained in each sub-section, when necessary, without having a table for each possible
use case.

B.2.1 UNI Service Attributes Record

Table 50 below provides an example of the UNI service attributes record for an SP.

UNI Service Attribute Value

UNI Identifier MTRL333-Node3-Slot2-Port1

Table 50 – UNI Service Attribute Record Example

B.2.2 OVC per UNI Service Attributes Record

Table 51 below provides an example of the OVC per UNI service attributes record for an SP.

OVC per UNI Service Attribute Value

UNI OVC Identifier MTRL333-Node3-Slot2-Port1-OVC-0001965-ACME-MEGAMART

CE VLAN ID OVC EP
OVC End Point Map
All 1

Table 51 – OVC per UNI Service Attribute Record Example

B.2.3 OVC Service Attributes Record

Table 52 below provides an example of the OVC service attributes record for an SP.

OVC Service Attribute Value

OVC Identifier OVC-0001965-ACME-MEGAMART

Table 52 – OVC Service Attribute Record Example

B.2.4 OVC End Point per ENNI Service Attributes Record

There is no OVC End Point per ENNI service attribute record for Service Providers.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 85
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
B.2.5 ENNI Service Attributes Record

There is no ENNI service attribute record for Service Providers.

B.2.6 Access EPL Service Definition Record

The example presented in section B.1.6 for the AP Access EPL Service Definition record applies
for the SP.

B.2.7 Service Acceptance Criteria Record

The example presented in section B.1.7 for the AP Service Acceptance Criteria record applies for
the SP.

B.2.8 EMIX Frame Size Configuration Test Record

The example presented in section B.1.8 for the AP EMIX Frame Size configuration test record
applies for the SP.

B.2.9 OVC MTU Size Test Configuration Record

The example presented in section B.1.9 for the AP OVC MTU Size test record applies for the
SP.

B.2.10 CE-VLAN ID Preservation Test Record – Access EPL

The example and differences presented in section B.1.10 for the AP CE-VLAN ID Preservation
test record applies for the SP.

B.2.11 CE-VLAN CoS ID Preservation Test Record – Access EPL

The example presented in section B.1.11 for the AP CE-VLAN CoS ID Preservation test record
applies for the SP.

B.2.12 Broadcast Delivery Test Record

The example presented in section B.1.12 for the AP Broadcast Delivery test record applies for
the SP.

B.2.13 Unicast Delivery Test Record

The example presented in section B.1.13 for the AP Unicast Delivery test record applies for the
SP.

B.2.14 Multicast Delivery Test Record

The example presented in section B.1.14 for the AP Multicast Delivery test record applies for the
SP.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 86
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.
 Carrier Ethernet Service Activation Testing (SAT)
B.2.15 Ingress Bandwidth Profile per OVC End Point – CIR Configuration Test Record

The example presented in section B.1.15 for the AP ingress Bandwidth Profile per OVC End
Point – CIR Configuration test record applies for the SP.

B.2.16 Ingress Bandwidth Profile per OVC End Point – EIR Configuration Test Record

The example and differences presented in section B.1.16 for the AP ingress Bandwidth Profile
per OVC End Point – EIR Configuration Test (color-aware) record applies for the SP.

B.2.17 Ingress Bandwidth Profile per OVC End Point – Traffic Policing Test Record

The example and differences presented in section B.1.17 for the AP ingress Bandwidth Profile
per OVC End Point – Traffic Policing Test (color-aware) record applies for the SP.

B.2.18 Service Performance Tests Record – Access EPL

The example and differences presented in section B.1.18 for the AP Service Performance Test
record applies for the SP.

MEF 48 © The Metro Ethernet Forum 2014. Any reproduction of this document, or any portion thereof, shall contain the Page 87
following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is
authorized to modify any of the information contained herein.