Abstract Test Suite for UNI Type 1

Abstract Test Suite for UNI Type 1
Abstract Test Suite for UNI Type 1
Technical Specification
MEF 19
Abstract Test Suite
for
UNI Type 1
April, 2007
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
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
representation 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
document 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,
technologies, 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
specifications will be voluntary, and no company shall be obliged to implement them by virtue of
participation in the Metro Ethernet Forum. The MEF is a non-profit international organization
accelerating 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 2007. All Rights Reserved.
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
Table of Contents
1. ABSTRACT ......................................................................................................................................................... 5
2. TERMINOLOGY ................................................................................................................................................. 5
3. SCOPE ................................................................................................................................................................. 9
4. COMPLIANCE LEVELS .................................................................................................................................... 9
5. INTRODUCTION................................................................................................................................................. 9
6. TEST CONFIGURATION .................................................................................................................................10
7. TEMPLATE FOR ABSTRACT TEST CASES FOR UNI TYPE 1 ..............................................................11
8. ABSTRACT TEST CASES FOR UNI TYPE 1 COMMON CHARACTERISTICS ...................................12
TEST CASE 1: Type 1 UNI-N Ethernet Physical Medium ........................................................................................ 13
TEST CASE 2: Type 1 UNI-N Ethernet Frame Format - Tagged, Untagged and Priority Tagged ..................... 14
TEST CASE 3: Type 1 UNI-N Minimum and Maximum Ethernet Frame Size ....................................................... 15
9. ABSTRACT TEST CASES FOR UNI TYPE 1.1 SPECIFIC CHARACTERISTICS ................................16
TEST CASE 4: Type 1.1 UNI-N CE-VLAN ID - Single EVC ..................................................................................... 17
TEST CASE 5: Type 1.1 UNI-N Configurable CE-VLAN ID/EVC Map - No CE-VLAN ID.................................... 18
TEST CASE 6: Type 1.1 UNI-N Bandwidth Profile per Ingress UNI ....................................................................... 19
TEST CASE 7: Type 1.1 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR = 0 ................................ 20
TEST CASE 8: Type 1.1 UNI-N Mandatory CIR Configuration Granularity ........................................................... 21
TEST CASE 9: Type 1.1 UNI-N Optional CIR Configuration Granularity ............................................................... 22
TEST CASE 10: Type 1.1 UNI-N CBS Configuration ................................................................................................ 23
TEST CASE 11: Type 1.1 UNI-N Mandatory Layer 2 Control Protocol Processing .............................................. 24
TEST CASE 12: Type 1.1 UNI-N Optional Layer 2 Control Protocol Processing .................................................. 25
TEST CASE 13: Type 1.1 UNI-N Optional Layer 2 Control Protocol Discard ........................................................ 26
TEST CASE 14: Type 1.1 UNI-N Point-to-Point EVC................................................................................................ 27
TEST CASE 15: Type 1.1 UNI-N CE-VLAN ID Preservation ................................................................................... 28
TEST CASE 16: Type 1.1 UNI-N CE-VLAN CoS Preservation................................................................................ 29
TEST CASE 17: Type 1.1 UNI-N Service Frame Unconditional Delivery ............................................................... 30
10. ABSTRACT TEST CASES FOR UNI TYPE 1.2 SPECIFIC CHARACTERISTICS ................................31
TEST CASE 18:
TEST CASE 19:
TEST CASE 20:
TEST CASE 21:
TEST CASE 22:
TEST CASE 23:
TEST CASE 24:
TEST CASE 25:
TEST CASE 26:
TEST CASE 27:
TEST CASE 28:
TEST CASE 29:
TEST CASE 30:
TEST CASE 31:
TEST CASE 32:
TEST CASE 33:
TEST CASE 34:
TEST CASE 35:
TEST CASE 36:
MEF 19
Type 1.2 UNI-N Service Multiplexing.............................................................................................. 32
Type 1.2 UNI-N Service Multiplexing - Minimum Number of EVCs ........................................... 33
Type 1.2 UNI-N Minimum Number of CE-VLAN IDs .................................................................... 34
Type 1.2 UNI-N CE-VLAN ID Range .............................................................................................. 35
Type 1.2 UNI-N Configurable CE-VLAN ID/EVC Map ................................................................. 36
Type 1.2 UNI-N CE-VLAN ID/EVC Map Service Frame Discard ............................................... 37
Type 1.2 UNI-N All-to-One Bundling............................................................................................... 38
Type 1.2 UNI-N Bandwidth Profile per Ingress UNI ..................................................................... 39
Type 1.2 UNI-N Bandwidth Profile per EVC .................................................................................. 40
Type 1.2 UNI-N Bandwidth Profile per Class of Service.............................................................. 41
Type 1.2 UNI-N Multiple Bandwidth Profiles ................................................................................. 42
Type 1.2 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR = 0 .............................. 43
Type 1.2 UNI-N BW Profile Rate Enforcement when CIR = 0 and EIR > 0 .............................. 44
Type 1.2 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR > 0 .............................. 45
Type 1.2 UNI-N Mandatory CIR Configuration Granularity ......................................................... 46
Type 1.2 UNI-N Mandatory EIR Configuration Granularity ......................................................... 47
Type 1.2 UNI-N Optional CIR Configuration Granularity ............................................................. 48
Type 1.2 UNI-N Optional EIR Configuration Granularity ............................................................. 49
Type 1.2 UNI-N CBS Configuration ................................................................................................ 51
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 37:
TEST CASE 38:
TEST CASE 39:
TEST CASE 40:
TEST CASE 41:
TEST CASE 42:
TEST CASE 43:
TEST CASE 44:
Type 1.2 UNI-N EBS Configuration ................................................................................................ 52
Type 1.2 UNI-N Optional Layer 2 Control Protocol Discard ........................................................ 53
Type 1.2 UNI-N Optional Layer 2 Control Protocol Generation .................................................. 54
Type 1.2 UNI-N Concurrent Point-to-Point and Multipoint EVCs ............................................... 55
Type 1.2 UNI-N CE-VLAN ID Preservation ................................................................................... 56
Type 1.2 UNI-N CE-VLAN CoS Preservation................................................................................ 57
Type 1.2 UNI-N Broadcast & Multicast Service Frame Unconditional Delivery ....................... 58
Type 1.2 UNI-N Unicast Service Frame Unconditional Delivery ................................................ 59
11. REFERENCES ...................................................................................................................................................60
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
1. Abstract
This document defines test procedures based on the requirements for the User to Network Interface
(UNI) Type 1 mode or manual configuration mode. The UNI Type 1 mode provides data-plane
connectivity services without control-plane or management-plane capabilities.
2. Terminology
All to One Bundling
A UNI attribute in which all CE-VLAN IDs are associated with a single EVC
Bandwidth Profile
A characterization of ingress Service Frame arrival times and lengths at a
reference point and a specification of the disposition of each Service Frame
based on its level of compliance with the Bandwidth Profile. In this document
the reference point is the UNI
Broadcast Service Frame
A Service Frame that has the broadcast destination MAC address
Bundling
A UNI attribute in which more than one CE-VLAN ID can be associated with
an EVC
CBS
Committed Burst Size
CE
Customer Edge
CE-VLAN CoS
Customer Edge VLAN CoS
CE-VLAN ID
Customer Edge VLAN ID
CE-VLAN ID Preservation
An EVC attribute in which the CE-VLAN ID of an egress Service Frame is
identical in value to the CE-VLAN ID of the corresponding ingress Service
Frame
CE-VLAN ID/EVC Map
An association of CE-VLAN IDs with EVCs at a UNI
CE-VLAN Tag
Customer Edge VLAN Tag
CF
Coupling Flag
CIR
Committed Information Rate
Class of Service
A set of Service Frames that have a commitment from the Service Provider
to receive a particular level of performance
Class of Service Identifier
Information derivable from a) the EVC to which the Service Frame is
mapped or b) the combination of the EVC to which the Service Frame is
mapped and a set of one or more CE-VLAN CoS values
CM
Color Mode
Color Mode
CM is a Bandwidth Profile parameter. The Color Mode parameter indicates
whether the color-aware or color-blind property is employed by the
Bandwidth Profile. It takes a value of “color-blind” or “color-aware” only
Color-aware
A Bandwidth Profile property where a pre-determined level of Bandwidth
Profile compliance for each Service Frame is taken into account when
determining the level of compliance for each Service Frame
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
Color-blind
A Bandwidth Profile property where a pre-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 maximum number of
bytes available for a burst of ingress Service Frames sent at the UNI speed
to remain CIR-conformant
Committed Information Rate
CIR is a Bandwidth Profile parameter. It defines the average rate in bits/s of
ingress Service Frames up to which the network delivers Service Frames
and meets the performance objectives defined by the CoS Service Attribute
Coupling Flag
CF is a Bandwidth Profile parameter. The Coupling Flag allows the choice
between two modes of operations of the rate enforcement algorithm. It takes
a value of 0 or 1 only
Customer Edge
Equipment on the Subscriber side of the UNI
Customer Edge VLAN CoS
The user priority bits in the IEEE 802.1Q Tag in a Service Frame that is
either tagged or priority tagged
Customer Edge VLAN ID
The identifier derivable from the content of a Service Frame that allows the
Service Frame to be associated with an EVC at the UNI
Customer Edge VLAN Tag
The IEEE 802.1Q Tag in a tagged Service Frame
EBS
Excess Burst Size
Egress Service Frame
A Service Frame sent from the Service Provider network to the CE
EIR
Excess Information Rate
E-LAN Service
Ethernet LAN Service
E-Line Service
Ethernet Line Service
Ethernet LAN Service
An Ethernet Service Type distinguished by its use of a Multipoint-toMultipoint EVC
Ethernet Line Service
An Ethernet Service Type distinguished by its use of a Point-to-Point EVC
Ethernet Virtual Connection
An association of two or more UNIs that limits the exchange of Service
Frames to UNIs in the Ethernet Virtual Connection
EVC
Ethernet Virtual Connection
Excess Burst Size
EBS is a Bandwidth Profile parameter. It limits the maximum number of
bytes available for a burst of ingress Service Frames sent at the UNI speed
to remain EIR-conformant
Excess Information Rate
EIR is a Bandwidth Profile parameter. It defines the average rate in bits/s of
ingress Service Frames up to which the network may deliver Service
Frames without any performance objectives
FD
Frame Delay
FDV
Frame Delay Variation
FLR
Frame Loss Ratio
Frame
Short for Ethernet frame
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
Frame Delay
The time required to transmit a Service Frame from source to destination
across the metro Ethernet network
Frame Delay Performance
A measure of the delays experienced by Service Frames belonging to the
same CoS instance
Frame Delay Variation
The difference in delay of two Service Frames
Frame Delay Variation
Performance
A measure of the variation in the delays experienced by Service Frames
belonging to the same CoS instance
Frame Loss Ratio
Performance
Frame Loss Ratio is a measure of the number of lost frames inside the
MEN. Frame Loss Ratio is expressed as a percentage
Ingress Service Frame
A Service Frame sent from the CE into the Service Provider network
Layer 2 Control Protocol
Service Frame
A Service Frame that is used for Layer 2 control, e.g., Spanning Tree
Protocol
Layer 2 Control Protocol
Tunneling
The process by which a Layer 2 Control Protocol Service Frame is passed
through the Service Provider network without being processed and is
delivered unchanged to the proper UNI(s)
Multicast Service Frame
A Service Frame that has a multicast destination MAC address
Multipoint-to-Multipoint EVC
An EVC with two or more UNIs. A Multipoint-to-Multipoint EVC with two
UNIs is different from a Point-to-Point EVC because one or more additional
UNIs can be added to it
Point-to-Point EVC
An EVC with exactly 2 UNIs
Service Frame
An Ethernet frame transmitted across the UNI toward the Service Provider
or an Ethernet frame transmitted across the UNI toward the Subscriber
Service Level Agreement
The contract between the Subscriber and Service Provider specifying the
agreed to service level commitments and related business agreements
Service Level Specification
The technical specification of the service level being offered by the Service
Provider to the Subscriber
Service Multiplexing
A UNI service attribute in which the UNI can be in more than one EVC
instance
Service Provider
The organization providing Ethernet Service(s)
SLA
Service Level Agreement
SLS
Service Level Specification
Subscriber
The organization purchasing and/or using Ethernet Services
UNI
User Network Interface
UNI-C
Compound architectural component on the Subscriber side of the UNI that
represents all the functions required to connect a subscriber to a MEN
UNI-N
Compound architectural component on the Service Provider side of the UNI
that represents all the functions required to connect a MEN to a MEN
subscriber
Unicast Service Frame
A Service Frame that has a unicast destination MAC address
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
User Network Interface
The physical demarcation point between the responsibility of the Service
Provider and the responsibility of the Subscriber
WG
W G is the amount of traffic accepted as Green over the time interval T that
should be delivered to the egress UNI
WY
W Y is the amount of traffic accepted as Yellow over the time interval T that
may be delivered to the egress UNI
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
3. Scope
The Abstract Test Suite for UNI Type 1 describes the test procedures based on the requirements for
the User to Network Interface (UNI) Type 1 mode or manual configuration mode. Test Cases in this Test
Specification are only defined for the UNI-N and each different physical interface MUST be tested
independently.
The UNI Type 1 requirements are described in sections 5, 6.1 and 6.2 of MEF 13 User Network Interface
(UNI) Type 1 Implementation Agreement.
Section 5 of MEF 13 defines the common characteristics of a UNI Type 1 such as the supported physical
media and Ethernet frame formats.
Section 6.1 of MEF 13 defines the specific characteristics of a UNI Type 1.1 which is a subset of the UNI
Type 1 and which is not meant to support service multiplexing.
Section 6.2 of MEF 13 defines the specific characteristics of a UNI Type 1.2 which is also a subset of the
UNI Type 1 but which is meant to support service multiplexing.
UNI Type 2 mode (Service Management) and UNI Type 3 mode (Dynamic Connection Setup) are out of
the scope of this document.
This document may be updated in the future to reflect new work done in the MEF Technical Committee.
4. 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. All key words MUST be use upper case, bold text.
5. Introduction
This document supplements the existing MEF test specifications MEF 9 Abstract Test Suite for Ethernet
Services at the UNI and MEF 14 Abstract Test Suite for Traffic Management Phase 1, by adding test
procedures based on the requirements for the User to Network Interface (UNI) Type 1 mode (manual
configuration) defined in MEF 13 User Network Interface (UNI) Type 1 implementation agreement.
As with MEF 9 and MEF 14, vendors can refer to the requirements and test procedures defined in this
specification in the development and commercial cycles of their products and carriers can use them to
ensure that the network elements they deploy or add to their existing network will have the ability to
deliver Ethernet Services based on the MEF technical specifications.
The requirements, framework and functional model on how the UNI reference point operates in a Metro
Ethernet Network is defined on the Metro Ethernet Forum technical specification MEF 11 User to Network
Interface Requirements and Framework.
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
6. Test Configuration
Although some Test Cases may require very specific test configurations, most Test Cases defined in this
document are to be executed by attaching the Ethernet interface of a tester to the Ethernet User Network
Interface (UNI).
Tester
Metro
Ethernet Network
(MEN)
UNI
connection
termination
UNI-N
UNI
connection
termination
UNI-N
Tester
EVC
•Testers are physically attached to the MEN at the UNIs
•Multiple testers may be generating, receiving and monitoring frames at the UNIs
Test Configuration for UNI Type 1
·
·
·
·
MEF 19
In each Test Case, the Test Configuration section describes the number of EVCs associating the
number of UNIs and the number of CE-VLAN IDs mapped to the EVCs
Testers are attached to all UNIs in the configured EVCs
CE-VLAN ID/EVC Maps are given for each Test Case
Applicable Bandwidth Profile and Service Performance parameters are provided when necessary
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
7. Template for Abstract Test Cases for UNI Type 1
The following template is adopted for the definition of Abstract Test Cases for UNI Type 1:
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Name derived from reference document
A punctuated alphanumeric string assigned to each defined requirement and test procedure couple using the
following convention: ‘one to three letter abbreviated source document name’. ‘section number’ - ‘specific
requirement number in the section from which requirement is derived’. This number always figures as the last
number of an ID. UNI Type 1 = U1; Ethernet Services Definitions = S; etc. Example: U1.5.1-1
Reference document (and section and paragraph when useful for clarity)
Functional, Conformance, Interoperability or Performance
Mandatory, Optional
Brief description of the service requirement that MUST or SHOULD be satisfied
Succinct description of test purpose
Succinct description of test bed configuration
A sample CE-VLAN ID/EVC Map is suggested. Variables augment it.
CE-VLAN ID/EVC
Map
INGRESS UNI ‘A’
CE-VLAN ID
EVC
10
EVC 1
EGRESS UNI ‘B’
CE-VLAN ID
EVC
10
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
A sample Bandwidth Profile table is suggested. Variables augment it.
Per Ingress UNI
Bandwidth Profile
UNI
UNI A
Bandwidth Profile Parameters
CIR A
CBS A
EIR A
EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)
A sample EVC Performance Objectives table is suggested. Variables augment it.
Service
Performance
CoS
Identifier
1
Test Procedure
Units
Variables
Results
Remarks
MEF 19
EVC Performance Service Attributes
Frame Delay (FD) Performance
Frame Delay Variation (FDV) Performance
Frame Loss Ratio (FLR) Performance
Performance
Objectives
FD 1
FDV 1
FLR 1
Succinct description of the test procedure
Units can be time units, rates and counts in integers such as milliseconds, frames per second and numbers of valid
frames. For the most part units used are defined in RFCs 2285, 2544, 2889
Variables such as number of UNIs, EVCs and CE-VLAN IDs and frame formats and lengths MUST be described
Description of the textual, numerical and/or graphical format in which to display test results. Results can be Pass or
Fail
Description of any particular observations that might effect the test result
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
8. Abstract Test Cases for UNI Type 1 Common
Characteristics
In this section we assume familiarity with MEF 13 User Network Interface (UNI) Type 1 Implementation
Agreement and, in particular, its section 5 which defines the common characteristics of the UNI Type 1.
Three Abstract Test Cases based on the common characteristics of the UNI Type 1 are defined in this
section.
Abstract Test Cases for UNI-N Type 1 Common Characteristics
Test Case 1: Type 1 UNI-N Ethernet Physical Medium
Test Case 2: Type 1 UNI-N Ethernet Frame Format - Tagged, Untagged and Priority Tagged
Test Case 3: Type 1 UNI-N Minimum and Maximum Ethernet Frame Size
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 1: Type 1 UNI-N Ethernet Physical Medium
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1 UNI-N Ethernet Physical Medium
U1.5.1-2
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1 UNI-N MUST support at least one of the following IEEE 802.3 Ethernet PHYs:
Requirement
Description
·
·
·
·
10BASE-T in Full-duplex mode
100BASE-T including 100BASE-TX and 100BASE-FX in Full-duplex mode
1000BASE-X including 1000BASE-SX, 1000BASE-LX, and 1000BASE-T in Full-duplex mode
10GBASE-SR, 10GBASE-LX4, 10GBASE-LR, 10GBASE-ER, 10GBASE-SW, 10GBASE-LW, and 10GBASEEW in Full-duplex mode
Test Object
Verify that a Type 1 UNI-N supports at least one of the IEEE 802.3 Ethernet PHYs listed in the requirement
description section above
Test
Configuration
One EVC associating two Type 1 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames bidirectionally at each UNI configured in the EVC and verifies that the corresponding
Service Frames are successfully delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 2: Type 1 UNI-N Ethernet Frame Format - Tagged, Untagged and Priority Tagged
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Type 1 UNI-N Ethernet Frame Format - Tagged, Untagged and Priority Tagged
U1.5.2-4
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1 UNI-N MUST support the transmission and reception of untagged, VLAN-tagged and priority-tagged
Ethernet frames according to IEEE 802.3-2002
Test Object
Verify that a Type 1 UNI-N supports the transmission and reception of untagged, VLAN-tagged and priority-tagged
Ethernet frames according to IEEE 802.3-2002
Test
Configuration
One EVC associating two Type 1 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged, untagged and priority tagged Service Frames bidirectionally at each UNI configured in the EVC
and verifies that the corresponding Service Frames are received at the associated UNI. The VLAN ID of the tagged
Service Frames must be the one configured in the CE-VLAN ID/EVC map
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 3: Type 1 UNI-N Minimum and Maximum Ethernet Frame Size
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Type 1 UNI-N Minimum and Maximum Ethernet Frame Size
U1.5.2-6
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1 UNI-N MUST support the transmission and reception of minimum and maximum size Ethernet frames as
specified in IEEE 802.3-2002
Test Object
Verify that a Type 1 UNI-N supports the transmission and reception of minimum and maximum size Ethernet frames
as specified in IEEE 802.3-2002
Test
Configuration
One EVC associating two Type 1 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers minimum and maximum size Service Frames, as specified in IEEE 802.3-2002, bidirectionally at each
UNI configured in the EVC and verifies that the corresponding Service Frames are delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
9. Abstract Test Cases for UNI Type 1.1 Specific
Characteristics
In this section we assume familiarity with MEF 13 User Network Interface (UNI) Type 1 Implementation
Agreement and, in particular, its section 6.1 which defines the specific characteristics of the UNI Type 1.1.
Fourteen Abstract Test Cases based on the specific characteristics of the UNI Type 1.1 are defined in this
section.
Abstract Test Cases for UNI-N Type 1.1 Specific Characteristics
Test Case 4: Type 1.1 UNI-N CE-VLAN ID - Single EVC
Test Case 5: Type 1.1 UNI-N Configurable CE-VLAN ID/EVC Map - No CE-VLAN ID
Test Case 6: Type 1.1 UNI-N Bandwidth Profile per Ingress UNI
Test Case 7: Type 1.1 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
Test Case 8: Type 1.1 UNI-N Mandatory CIR Configuration Granularity
Test Case 9: Type 1.1 UNI-N Optional CIR Configuration Granularity
Test Case 10: Type 1.1 UNI-N CBS Configuration
Test Case 11: Type 1.1 UNI-N Mandatory Layer 2 Control Protocol Processing
Test Case 12: Type 1.1 UNI-N Optional Layer 2 Control Protocol Processing
Test Case 13: Type 1.1 UNI-N Optional Layer 2 Control Protocol Discard
Test Case 14: Type 1.1 UNI-N Point-to-Point EVC
Test Case 15: Type 1.1 UNI-N CE-VLAN ID Preservation
Test Case 16: Type 1.1 UNI-N CE-VLAN CoS Preservation
Test Case 17: Type 1.1 UNI-N Service Frame Unconditional Delivery
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 4: Type 1.1 UNI-N CE-VLAN ID - Single EVC
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.1 UNI-N CE-VLAN ID - Single EVC
Test Definition ID
Reference
Document
U1.6.1.1-7, 8
Test Type
Conformance
Test Status
Requirement
Description
Test Object
Test
Configuration
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Mandatory
A Type 1.1 UNI-N MUST be able to support a single EVC and to accept any CE-VLAN ID received from the UNI-C
Verify that a Type 1.1 UNI-N can support a single EVC and accept any CE-VLAN ID received from the UNI-C
One EVC associating at least two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the
EVC. A per Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI
are attached to all UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID
CE-VLAN ID/EVC
Map
All possible values
allowed at the
UNI-C
UNI ‘B’
EVC
CE-VLAN ID
EVC
EVC 1
All possible values
allowed at the
UNI-C
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with VLAN IDs = 1, …, 4095, untagged Service Frames and priority tagged
Service Frames bidirectionally at each UNI configured in the EVC and verifies that the corresponding Service
Frames are delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 5: Type 1.1 UNI-N Configurable CE-VLAN ID/EVC Map - No CE-VLAN ID
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Configurable CE-VLAN ID/EVC Map - No CE-VLAN IDs
U1.6.1.2-9
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be configurable to map no CE-VLAN ID to an EVC. (Temporary disconnection without
tearing down the EVC)
Verify that a Type 1.1 UNI-N can be configured to map no CE-VLAN ID to an EVC
One EVC associating two Type 1.1 UNIs is configured and no CE-VLAN ID is mapped to the EVC. A per Ingress
UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached to both
UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
None
EVC 1
None
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with VLAN IDs = 1, …4095, untagged Service Frames and priority tagged
Service Frames bidirectionally at each UNI configured in the EVC and verifies that the corresponding Service
Frames are not delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 6: Type 1.1 UNI-N Bandwidth Profile per Ingress UNI
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Bandwidth Profile per Ingress UNI
U1.6.1.3-10
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to support a per Ingress UNI bandwidth profile based on MEF 10
Verify that a Type 1.1 UNI-N can support a per Ingress UNI bandwidth profile based on MEF 10
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Not Specified
Tester offers tagged Service Frames with VLAN IDs = 1, …4095, untagged Service Frames and priority tagged
Service Frames of length λ into the configured EVC at the ingress UNI and verifies that over a time interval T at least
one Service Frame of each CE-VLAN ID is delivered at the associated egress UNI. Service Frames are offered at
equal average rates into the configured EVC, at an aggregate average rate greater than CIR A. Tester also verifies
that the amount of traffic delivered at the egress UNI falls within the range X ≤ W G ≤ Z where:
·
·
Units
Variables
Results
W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI.
X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 7: Type 1.1 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR = 0
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
U1.6.1.3-12
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to support color-blind bandwidth profile where EIR=EBS=0 and CIR and CBS are
non-zero
Verify that a Type 1.1 UNI-N can support color-blind bandwidth profile where EIR=EBS=0 and CIR and CBS are nonzero
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. One
Bandwidth Profile where EIR=EBS=0 and CIR and CBS are non-zero is applied at the ingress UNI. Testers with
proper PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames of length λ at an average rate greater than CIR A to the ingress UNI during a time
interval T and measures the number of Service Frames delivered at the associated egress UNI. The amount of
traffic delivered at the associated egress UNI must fall within the range X ≤ W G ≤ Z where:
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI.
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 8: Type 1.1 UNI-N Mandatory CIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.1 UNI-N Mandatory CIR Configuration Granularity
Test Definition ID
Reference
Document
Test Type
U1.6.1.3-13
Test Status
Mandatory
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
A Type 1.1 UNI-N MUST allow configuration to modify CIR in the following granularities
Requirement
Description
Test Object
Test
Configuration
·
·
·
·
1 Mbps steps up to 10 Mbps [CIR range 1]
5 Mbps steps beyond 10 Mbps and up to 100 Mbps [CIR range 2]
50 Mbps steps beyond 100 Mbps and up to 1 Gbps [CIR range 3]
500 Mbps steps beyond 1 Gbps [CIR range 4]
Verify that a Type 1.1 UNI-N allows configuration to modify CIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.1 UNIs is configured. All possible CE-VLAN IDs are mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Not Specified
Tester offers Service Frames of length λ at an average rate greater than CIR A to the ingress UNI during a time
interval T and measures the number of Service Frames delivered at the associated egress UNI. The amount of
traffic delivered at the egress UNI must fall within the range X ≤ W G ≤ Z where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI.
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Begin the test with CIR A set to the minimum value (i.e. 1 Mbps) and increment CIR A by the step value defined for the
CIR range.
Repeat the test for each CIR A value until CIR A has been incremented to the UNI speed
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 9: Type 1.1 UNI-N Optional CIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Optional CIR Configuration Granularity
U1.6.1.3-14
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.1 UNI-N SHOULD allow configuration to modify CIR in the following granularities:
· 64 Kbps (DS0 rate) steps up to 1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) [CIR range 1]
· 1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) steps up to 50 Mbps [CIR range 2]
· 43.008 Mbps (VC3 rate) steps beyond 50 Mbps and up to 150 Mbps [CIR range 3]
· 133.12 Mbps (VC4 rate) steps beyond 150 Mbps [CIR range 4]
Verify that a Type 1.1 UNI-N allows configuration to modify CIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.1 UNIs is configured. All possible CE-VLAN IDs are mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Not Specified
Tester offers Service Frames of length λ at an average rate greater than CIR A to the ingress UNI during a time
interval T and measures the number of Service Frames delivered at the associated egress UNI. The amount of
traffic delivered at the egress UNI must fall within the range X ≤ W G ≤ Z where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI.
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Begin the test with CIR A set to the minimum value (i.e. 64 Kbps) and increment CIR A by the step value defined for
the CIR range.
Repeat the test for each CIR A value until CIR A has been incremented to the UNI speed
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 10: Type 1.1 UNI-N CBS Configuration
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N CBS Configuration
U1.6.1.3-15
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to at least support CBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
Verify that a Type 1.1 UNI-N can at least support CBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
One EVC associating two Type 1.1 UNIs is configured. All possible CE-VLAN IDs are mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ 12176 bytes)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames of length λ at an average rate equal to CIR A to the ingress UNI during a time interval T.
At time T/2 tester injects a burst of ingress Service Frames greater than CBS A . Tester measures the number of
Service Frames delivered at the associated egress UNIs. The amount of traffic delivered at each egress UNI must
fall within the range X ≤ W G ≤ Z where:
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass, fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 11: Type 1.1 UNI-N Mandatory Layer 2 Control Protocol Processing
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Mandatory Layer 2 Control Protocol Processing
U1.6.1.4-16
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to pass the following L2 Control Protocols to the EVC:
·
Spanning Tree Protocol (STP),
·
Rapid Spanning Tree Protocol (RSTP),
·
Multiple Spanning Tree Protocol (MSTP)
·
All LANs Bridge Management Group Block of Protocol
·
Generic Attribute Registration Protocol (GARP)
Verify that a Type 1.1 UNI-N can pass each L2 Control Protocol described in the requirement description section
above to the EVC
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A
per Ingress UNI bandwidth profile is applied at the UNI. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames carrying Layer 2 Control protocols described in the requirement description section
above at the ingress UNI and verifies that the corresponding Service Frames are delivered at the associated egress
UNI. The L2CPs Destination Address and Ethertype/Length fields must be defined as per the IEEE standards
Number of valid Service Frames carrying the L2CPs
L2CP, Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 12: Type 1.1 UNI-N Optional Layer 2 Control Protocol Processing
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Type 1.1 UNI-N Optional Layer 2 Control Protocol Processing
U1.6.1.4-17
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.1 UNI-N SHOULD be able to pass the following L2 Control Protocols to the EVC:
·
Link Aggregation Control Protocol (LACP)
·
Marker Protocol
·
Authentication (802.1x)
Test Object
Verify that a Type 1.1 UNI-N can pass each L2 Control Protocols described in the requirement description section
above to the EVC
Test
Configuration
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at the UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames carrying Layer 2 Control protocols described in the requirement description section
above at the ingress UNI and verifies that the corresponding Service Frames are delivered at the associated egress
UNI. The L2CPs Destination Address and Ethertype/Length fields must be defined as per the IEEE standards
Number of valid Service Frames carrying the L2CPs
L2CP, Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 13: Type 1.1 UNI-N Optional Layer 2 Control Protocol Discard
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Optional Layer 2 Control Protocol Discard
U1.6.1.4-18
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.1 UNI-N SHOULD be able to discard 802.3x PAUSE frames
Verify that a Type 1.1 UNI-N can discard 802.3x PAUSE frames
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at the UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers 802.3x PAUSE frames at the ingress UNI and verifies that they are not delivered at the associated
egress UNI.. The L2CPs Destination Address and Ethertype/Length fields must be defined as per the IEEE
standards
Number of valid Service Frames carrying the L2CPs
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 14: Type 1.1 UNI-N Point-to-Point EVC
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N Point-to-Point EVC
U1.6.1.5-19
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to support point-to-point EVC
Verify that a Type 1.1 UNI-N can support point-to-point EVC
One point-to-point EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to
the EVC. A per Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each
UNI are attached to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames bidirectionally at each UNI configured in the EVC and verifies that the corresponding
Service Frames are delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 15: Type 1.1 UNI-N CE-VLAN ID Preservation
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N CE-VLAN ID Preservation
U1.6.1.6-20
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to support CE-VLAN ID preservation
Verify that a Type 1.1 UNI-N can support CE-VLAN ID preservation
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with VLAN IDs = 1,…, 4095, untagged Service Frames and priority tagged
Service Frames bidirectionally at each UNI configured in the EVC and verifies that the corresponding Service
Frames are delivered at the associated UNI with CE-VLAN ID preservation
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 16: Type 1.1 UNI-N CE-VLAN CoS Preservation
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.1 UNI-N CE-VLAN CoS Preservation
U1.6.1.7-21
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to support CE-VLAN CoS preservation
Verify that a Type 1.1 UNI-N can support CE-VLAN CoS preservation
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with all possible CoS values bidirectionally at each UNI configured in the EVC
and verifies that the corresponding Service Frames are delivered at the associated UNI with CE-VLAN CoS
preservation
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 17: Type 1.1 UNI-N Service Frame Unconditional Delivery
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Type 1.1 UNI-N Service Frame Unconditional Delivery
U1.6.1.8-22
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.1 UNI-N MUST be able to deliver unicast, multicast and broadcast Service Frames, except 802.3x PAUSE
frames unconditionally
Test Object
Verify that a Type 1.1 UNI-N can deliver unicast, multicast and broadcast Service Frames, except 802.3x PAUSE
frames unconditionally
Test
Configuration
One EVC associating two Type 1.1 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A
per Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers unicast, multicast and broadcast Service Frames bidirectionally at each UNI configured in the EVC and
verifies that the corresponding Service Frames are delivered at the associated UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
10. Abstract Test Cases for UNI Type 1.2 Specific
Characteristics
In this section we assume familiarity with MEF 13 User Network Interface (UNI) Type 1 Implementation
Agreement and, in particular, its section 6.2 which defines the specific characteristics of the UNI Type 1.2.
Twenty-seven Abstract Test Cases based on the specific characteristics of the UNI Type 1.2 are defined in
this section.
Abstract Test Cases for UNI-N Type 1.2 Specific Characteristics
Test Case 18: Type 1.2 UNI-N Service Multiplexing
Test Case 19: Type 1.2 UNI-N Service Multiplexing - Minimum Number of EVCs
Test Case 20: Type 1.2 UNI-N Minimum Number of CE-VLAN IDs
Test Case 21: Type 1.2 UNI-N CE-VLAN ID Range
Test Case 22: Type 1.2 UNI-N Configurable CE-VLAN ID/EVC Map
Test Case 23: Type 1.2 UNI-N CE-VLAN ID/EVC Map Service Frame Discard
Test Case 24: Type 1.2 UNI-N All-to-One Bundling
Test Case 25: Type 1.2 UNI-N Bandwidth Profile per Ingress UNI
Test Case 26: Type 1.2 UNI-N Bandwidth Profile per EVC
Test Case 27: Type 1.2 UNI-N Bandwidth Profile per Class of Service
Test Case 28: Type 1.2 UNI-N Multiple Bandwidth Profiles
Test Case 29: Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
Test Case 30: Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0
Test Case 31: Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0
Test Case 32: Type 1.2 UNI-N Mandatory CIR Configuration Granularity
Test Case 33: Type 1.2 UNI-N Mandatory EIR Configuration Granularity
Test Case 34: Type 1.2 UNI-N Optional CIR Configuration Granularity
Test Case 35: Type 1.2 UNI-N Optional EIR Configuration Granularity
Test Case 36: Type 1.2 UNI-N CBS Configuration
Test Case 37: Type 1.2 UNI-N EBS Configuration
Test Case 38: Type 1.2 UNI-N Optional Layer 2 Control Protocol Discard
Test Case 39: Type 1.2 UNI-N Optional Layer 2 Control Protocol Generation
Test Case 40: Type 1.2 UNI-N Concurrent Point-to-Point and Multipoint EVCs
Test Case 41: Type 1.2 UNI-N CE-VLAN ID Preservation
Test Case 42: Type 1.2 UNI-N CE-VLAN CoS Preservation
Test Case 43: Type 1.2 UNI-N Broadcast & Multicast Service Frame Unconditional Delivery
Test Case 44: Type 1.2 UNI-N Unicast Service Frame Unconditional Delivery
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 18: Type 1.2 UNI-N Service Multiplexing
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N Service Multiplexing
U1.6.2.1-23
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support Service Multiplexing as defined in MEF 10
Verify that a Type 1.2 UNI-N can support Service Multiplexing as defined in MEF 10
At least two EVCs, each one associating a given Type 1.2 ingress UNI and at least one other Type 1.2 UNI are
configured and at least one CE-VLAN ID is mapped per EVC. Per EVC bandwidth profiles are applied at all UNIs.
Testers with proper PHY that matches each UNI are attached to all UNIs in the configured EVCs
UNI ‘A’
UNI ‘B’
CE-VLAN ID
EVC
11*
EVC 1
12
EVC 2
CE-VLAN ID/EVC
Map
UNI ‘C’
CE-VLAN ID
EVC
12
CE-VLAN ID
EVC
11*
EVC 1
EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs conforms to MEF
10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at both ingress and
egress UNIs
PER EVC
Bandwidth Profile
EVC
Bandwidth Profile Parameters
EVC 1
CIR 1
CBS 1
EIR 1
EBS 1
EVC 2
CIR 2
CBS 2
EIR 2
EBS 2
Note 1: (0 < CIR 1,2 < Ingress UNI Speed), (CBS 1,2 ≥ maximum Service Frame size)
Note 2: (Σ Ingress CIRs ≤ Egress UNI Speed)
Note 3: (EIR 1,2 = 0) and (EBS 1,2 = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVCs and
verifies that the corresponding Service Frames are successfully delivered on the proper EVC at the associated UNIs.
Number of valid Service Frames
Number of UNIs, number of EVCs per UNI, Bandwidth Profile Parameters CIR 1, CBS 1 , CIR 2 , CBS 2 , UNIs interface
speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 19: Type 1.2 UNI-N Service Multiplexing - Minimum Number of EVCs
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N Service Multiplexing - Minimum Number of EVCs
U1.6.2.1-24
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD at least be able to support a minimum number of EVCs as described in the following
table
Link Speed
10/100 Mbps
1 Gbps
10 Gbps
Minimum Number of EVCs
8
64
512
Verify that a Type 1.2 UNI-N can support a minimum number of EVCs as described in the requirement description
table above
At least eight EVCs, each one associating a given Type 1.2 ingress UNI and at least one other Type 1.2 UNI are
configured and at least one CE-VLAN ID is mapped per EVC. Per EVC bandwidth profiles are applied at all UNIs.
Testers with proper PHY that matches each UNI are attached to all UNIs in the configured EVCs
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
1
2
3
4
5
6
7
8
EVC 1
EVC 2
EVC 3
EVC 4
EVC 5
EVC 6
EVC 7
EVC 8
UNI ‘C’
CE-VLAN ID
EVC
5
6
7
8
CE-VLAN ID
EVC
1
2
3
4
EVC 1
EVC 2
EVC 3
EVC 4
EVC 5
EVC 6
EVC 7
EVC 8
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs conforms to MEF
10 [Ethernet Services Attributes Phase 1], Section 7.5.1
This mapping applies for 10/100 Mbps UNI speeds. The same mapping principles should be applied for
the 1Gbps and 10Gbps UNI speeds but with respectively 64 and 512 EVCs
PER EVC
EVC
EVC 1
EVC 2
Bandwidth Profile
Bandwidth Profile Parameters
CIR 1 CBS 1 EIR 1 EBS 1
CIR 2 CBS 2 EIR 2 EBS 2
.
.
.
.
.
.
EVC 8
CIR 8
.
.
.
CBS 8
.
.
.
EIR 8
.
.
.
EBS 8
Note 1: (0 < CIR 1,2,3,4,5,6,7,8 < Ingress UNI Speed), (CBS 1,2,3,4,5,6,7,8 ≥ maximum Service Frame size)
Note 2: (Σ Ingress CIRs ≤ Egress UNI Speed)
Note 3: (EIR 1,2,3,4,5,6,7,8 = 0) and (EBS 1,2,3,4,5,6,7,8 = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Remarks
MEF 19
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVCs and
verifies that the corresponding Service Frames are delivered at the associated UNIs
Number of valid Service Frames
UNIs interface speed, number of UNIs, number of EVCs per UNI, Bandwidth Profile Parameters CIR 1, CBS 1 , CIR 2 ,
CBS 2, CIR 3, CBS 3 , CIR 4 , CBS 4, CIR 5, CBS 5 , CIR 6 , CBS 6, CIR 7, CBS 7 , CIR 8 , CBS 8
Pass or fail
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 20: Type 1.2 UNI-N Minimum Number of CE-VLAN IDs
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.2 UNI-N Minimum Number of CE-VLAN Ids
Test Definition ID
Reference
Document
U1.6.2.2-25.1
Test Type
Conformance
Test Status
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Optional
A Type 1.2 UNI-N SHOULD be able to support at least a minimum number of CE-VLAN IDs as described in the
following table
Requirement
Description
Test Object
Test
Configuration
Link Speed
10/100 Mbps
1 Gbps
10 Gbps
Minimum Number of
CE-VLAN IDs
8
64
512
Verify that a Type 1.2 UNI-N can at least support a minimum number of CE-VLAN IDs as described in the
requirement description table above
One EVC associating two Type 1.2 UNIs is configured and at least eight CE-VLAN IDs are mapped to the EVC. A
per Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID
11, 12, 13, 14, 15,
16, 17, 18
CE-VLAN ID/EVC
Map
UNI ‘B’
EVC
CE-VLAN ID
EVC
EVC 1
11, 12, 13, 14, 15,
16, 17, 18
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
This mapping applies for 10/100 Mbps UNI speeds. The same mapping principles should
be applied for the 1Gbps and 10Gbps UNI speeds but with respectively 64 and 512 CEVLAN IDs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVC and
verifies that the corresponding Service Frames are delivered at the associated UNI
Number of valid Service Frames
UNIs interface speed, number of mapped CE-VLAN IDs, Bandwidth Profile Parameters CIR , CBS
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 21: Type 1.2 UNI-N CE-VLAN ID Range
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.2 UNI-N CE-VLAN ID Range
Test Definition ID
Reference
Document
U1.6.2.2-25.2
Test Type
Conformance
Test Status
Requirement
Description
Test Object
Test
Configuration
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Optional
A Type 1.2 UNI-N should be able to support a minimum number of CE-VLAN IDs that SHOULD be configurable in
the range of 1-4095
Verify that a Type 1.2 UNI-N can at support a minimum number of CE-VLAN IDs configurable in the range of 1-4095
One EVC associating two Type 1.2 UNIs is configured and at least eight CE-VLAN IDs are mapped to the EVC. A
per Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID
1, 56, 212, 1087, 1460,
2228, 3999, 4095
CE-VLAN ID/EVC
Map
UNI ‘B’
EVC
CE-VLAN ID
EVC
EVC 1
1, 56, 212, 1087, 1460,
2228, 3999, 4095
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
This mapping applies for 10/100 Mbps UNI speeds. The same mapping principles should
be applied for the 1Gbps and 10Gbps UNI speeds but with respectively 64 and 512 CEVLAN IDs, including VLAN IDs 1 and 4095
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVC and
verifies that the corresponding Service Frames are delivered at the associated UNI
Number of valid Service Frames
UNIs interface speed, number of mapped CE-VLAN IDs, Bandwidth Profile Parameters CIR , CBS
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 22: Type 1.2 UNI-N Configurable CE-VLAN ID/EVC Map
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Type 1.2 UNI-N Configurable CE-VLAN ID/EVC Map
U1.6.1.3-26
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Test Status
Requirement
Description
Test Object
Mandatory
Test
Configuration
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped per EVC. At least
two different mapping configurations are required. A per Ingress UNI bandwidth profile is applied at both UNIs.
Testers with proper PHY that matches each UNI are attached to both UNIs in the configured EVC
A Type 1.2 UNI-N MUST have a configurable CE-VLAN ID/EVC mapping table
Verify that a Type 1.2 UNI-N can have a configurable CE-VLAN ID/EVC mapping table
UNI ‘A’
CE-VLAN ID/EVC
Map
Configuration 1
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
UNI ‘A’
CE-VLAN ID/EVC
Map
Configuration 2
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
12
EVC 1
12
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped and unmapped CE-VLAN IDs bidirectionally at each UNI configured in
the EVC as per the CE-VLAN ID/EVC map 1 and verifies that the Service Frames with the mapped CE-VLAN IDs
are delivered and the ones with the unmapped CE-VLAN IDs are not delivered at the associated UNI.
Change the configuration to the CE-VLAN ID/EVC map 2.
Tester offers Service Frames with mapped and unmapped CE-VLAN IDs bidirectionally at each UNI configured in
the EVC as per the CE-VLAN ID/EVC map 2 and verifies that the Service Frames with the mapped CE-VLAN IDs
are delivered and the ones with the unmapped CE-VLAN IDs are not delivered at the associated egress UNI
Number of valid Service Frames
CE-VLAN ID/EVC maps, Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 23: Type 1.2 UNI-N CE-VLAN ID/EVC Map Service Frame Discard
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N CE-VLAN ID/EVC Map Service Frame Discard
U1.6.1.3-27
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to drop the frames if a match in the CE-VLAN ID/EVC map table cannot be found
Verify that a Type 1.2 UNI-N can drop the frames if a match in the CE-VLAN ID/EVC map table cannot be found
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped per EVC. A per
Ingress UNI bandwidth profile is applied at the UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped and unmapped CE-VLAN IDs at the ingress UNI configured in the EVC
and verifies that the Service Frames with the mapped CE-VLAN IDs are delivered and the ones with the unmapped
CE-VLAN IDs are not delivered at the associated egress UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 24: Type 1.2 UNI-N All-to-One Bundling
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N All-to-One Bundling
U1.6.2.4-28
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support All-to-one bundling
Verify that a Type 1.2 UNI-N can support All-to-one bundling
One EVC associating two Type 1.2 UNIs is configured and all possible CE-VLAN IDs are mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
All possible values
EVC 1
All possible values
EVC 1
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with VLAN IDs= 1, …, 4095, untagged Service Frames and priority tagged
Service bidirectionally at each UNI configured in the EVC and verifies that the corresponding Service Frames are
delivered at the associated UNI with CE-VLAN ID preservation
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 25: Type 1.2 UNI-N Bandwidth Profile per Ingress UNI
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N Bandwidth Profile per Ingress UNI
U1.6.2.5-29
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support a per Ingress UNI bandwidth profile based on MEF 10
Verify that a Type 1.2 UNI-N can support a per Ingress UNI bandwidth profile based on MEF 10
Two EVCs associating two Type 1.2 UNIs are configured and at least one CE-VLAN ID is mapped per EVC. A per
Ingress UNI bandwidth profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVCs
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11
EVC 1
11
EVC 1
12
EVC 2
12
EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ into the configured EVCs at the ingress UNI and
verifies that over a time interval T at least one Service Frame of each CE-VLAN ID is delivered at the associated
egress UNI. Service Frames are offered at equal average rates into the configured EVCs at the ingress UNI, at an
aggregate average rate greater than CIR A. Tester also verifies that the amount of traffic delivered at the egress UNI
falls within the range X ≤ (W G + W Y ) ≤ Z where:
·
W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
·
W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI
·
X A = ((CIR A + EIR A )*T + CBS A + EBS A - F) and Z A = ((CIR A + EIR A )*T + CBS A + EBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, EIR A, EBS A , UNIs interface speed, time interval T, tolerated variance F,
number and length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 26: Type 1.2 UNI-N Bandwidth Profile per EVC
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N Bandwidth Profile per EVC
U1.6.2.5-30
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support a per EVC bandwidth profile based on MEF 10
Verify that a Type 1.2 UNI-N can support a per EVC bandwidth profile based on MEF 10
Two EVCs associating two Type 1.2 UNIs are configured and at least one CE-VLAN ID is mapped per EVC. Per
EVC bandwidth profiles are applied at the ingress UNI. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVCs
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11
EVC 1
11
EVC 1
12
EVC 2
12
EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
PER EVC
Bandwidth Profile
EVC
Bandwidth Profile Parameters
EVC 1
CIR 1
CBS 1
EIR 1
EBS 1
EVC 2
CIR 2
CBS 2
EIR 2
EBS 2
Note 1: (CIR 1 = 0), (CBS 1 = 0) and (EIR 1 = 0) and (EBS 1 = 0)
Note 2: (0 < CIR 2 < Ingress UNI Speed), (CBS 2 ≥ maximum Service Frame size)
Note 3: (Σ Ingress CIRs ≤ Egress UNI Speed)
Service
Performance
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ into the configured EVCs at the ingress UNI
during a time interval T, at an aggregate average rate in excess of the sum of the CIRs of all the configured EVCs
and measures the number of Service Frames delivered at the associated egress UNI. For each EVC the amount of
traffic delivered at the associated egress UNI must fall within the range X ≤ (W G + W Y ) ≤ Z where:
Test Procedure
·
·
·
·
Units
Variables
Results
W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI
X 1 = ((CIR 1 + EIR 1 )*T + CBS 1 + EBS 1 - F) and Z 1 = ((CIR 1 + EIR 1 )*T + CBS 1 + EBS 1 + F)
X 2 = ((CIR 2 + EIR 2 )*T + CBS 2 + EBS 2 - F) and Z 2 = ((CIR 2 + EIR 2 )*T + CBS 2 + EBS 2 + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR 2, CBS 2, EIR 2, EBS 2 , UNIs interface speed, time interval T, tolerated variance F,
number and length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 27: Type 1.2 UNI-N Bandwidth Profile per Class of Service
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test
Configuration
Type 1.2 UNI-N Bandwidth Profile per Class of Service
U1.6.2.5-31.1
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD be able to support a per CoS bandwidth profile based on MEF 10
Verify that a Type 1.2 UNI-N can support a per CoS bandwidth profile based on MEF 10
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped per EVC. Per Class
of Service bandwidth profiles are applied at the ingress UNI. Two CoS Identifiers are used to identify the Class of
Service applicable to the Service Frames offered at the UNI. Testers with proper PHY that matches each UNI are
attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER CLASS OF SERVICE
EVC
Bandwidth Profile
EVC 1
CoS
Identifier
CE-VLAN
CoS
1
1
CIR 11 CBS 11 EIR 11 EBS 11
2
7
CIR 12 CBS 12 EIR 12 EBS 12
Bandwidth Profile Parameters
Note 1: (CIR 11 = 0), (CBS 11 = 0) and (EIR 11 = 0) and (EBS 11 = 0)
Note 2: (0 < CIR 12 < Ingress UNI Speed), (CBS 12 ≥ maximum Service Frame size)
Note 3: (Σ Ingress CIRs ≤ Egress UNI Speed)
Service
Performance
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ into the configured EVC at the ingress UNI
during a time interval T, at an aggregate average rate in excess of the sum of the CIRs of the configured CoS IDs
and measures the number of Service Frames delivered at the associated egress UNI. For each CoS ID, the amount
of traffic delivered at the associated egress UNI must fall within the range X ≤ (W G + W Y ) ≤ Z where:
Test Procedure
·
·
·
·
Units
Variables
Results
W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI
X 11 = ((CIR 11 + EIR 11 )*T + CBS 11 + EBS 11 - F) and Z 11 = ((CIR 11 + EIR 11 )*T + CBS 11 + EBS 11 + F)
X 12 = ((CIR 12 + EIR 12 )*T + CBS 12 + EBS 12 - F) and Z 12 = ((CIR 12 + EIR 12 )*T + CBS 12 + EBS 12 + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR 12, CBS 12, EIR 12, EBS 12 , time interval T, tolerated variance F, number and length λ
of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 28: Type 1.2 UNI-N Multiple Bandwidth Profiles
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N Multiple Bandwidth Profiles
U1.6.2.5-31.2
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
Multiple models of bandwidth profile MAY exist at a UNI-N Type 1.2.
Verify that a Type 1.2 UNI-N can support multiple models of bandwidth profile
Two EVCs associating two Type 1.2 UNIs are configured and at least one CE-VLAN ID is mapped per EVC. A per
EVC bandwidth profile and a per Class of Service bandwidth profile are applied at the ingress UNI. Testers with
proper PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID
EVC
11
EVC 1
12
EVC 2
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
11
EVC 1
12
EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
PER EVC
EVC
Bandwidth Profile Parameters
EVC 1
CIR 1
CBS 1
EIR 1
EBS 1
Note 1: (0 < CIR 1 < ingress UNI Speed), (CBS 1 ≥ maximum Service Frame size)
PER CLASS OF SERVICE
CoS
CE-VLAN
EVC
Bandwidth Profile Parameters
Identifier
CoS
1
1
CIR 21 CBS 21 EIR 21 EBS 21
EVC 2
2
7
CIR 22 CBS 22 EIR 22 EBS 22
Note 2: (CIR 21 = 0), (CBS 21 = 0) and (EIR 21 = 0) and (EBS 21 = 0)
Note 3: (0 < CIR 22 < ingress UNI Speed), (CBS 22 ≥ maximum Service Frame size)
Note 4: (∑ Ingress CIRs < Ingress UNI Speed)
Note 5: (Σ Ingress CIRs ≤ Egress UNI Speed)
Bandwidth Profile
Service
Performance
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ into the configured EVCs at the ingress UNI
during a time interval T, at an aggregate average rate in excess of the sum of the CIRs of all the configured EVCs
and CoS IDs and measures the number of Service Frames delivered at the associated egress UNI. For EVC 1 and
for each CoS ID of EVC 2 , the amount of traffic delivered at the associated egress UNI must fall within the range
X ≤ (W G + W Y ) ≤ Z where:
Test Procedure
·
·
·
·
·
Units
Variables
Results
Remarks
MEF 19
W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI
X 1 = ((CIR 1 + EIR 1 )*T + CBS 1 + EBS 1 - F) and Z 1 = ((CIR 1 + EIR 1 )*T + CBS 1 + EBS 1 + F)
X 21 = ((CIR 21 + EIR 21 )*T + CBS 21 + EBS 21 - F) and Z 21 = ((CIR 21 + EIR 21 )*T + CBS 21 + EBS 11 + F)
X 22 = ((CIR 22 + EIR 22 )*T + CBS 22 + EBS 22 - F) and Z 22 = ((CIR 22 + EIR 22 )*T + CBS 22 + EBS 22 + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR 1, CBS 1, EIR 1, EBS 1, CIR 22, CBS 22, EIR 22, EBS 22, UNIs interface Speed, time
interval T, tolerated variance F, number and length λ of the offered Service Frames
Pass or fail
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 29: Type 1.2 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR = 0
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
Test Definition ID
Reference
Document
U1.6.2.5-33.1
Test Type
Conformance
Test Status
Requirement
Description
Test Object
Test Configuration
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Mandatory
A Type 1.2 UNI-N MUST be able to support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS
Verify that a Type 1.2 UNI-N can support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS when
CIR > 0 and EIR = 0
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. One
Bandwidth Profile where EIR=EBS=0 and CIR and CBS are non-zero is applied at the ingress UNI. Testers with
proper PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Test Procedure
Units
Variables
Results
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than CIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤W G ≤ Z where:
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 30: Type 1.2 UNI-N BW Profile Rate Enforcement when CIR = 0 and EIR > 0
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0
Test Definition ID
Reference
Document
U1.6.2.5-33.2
Test Type
Conformance
Test Status
Requirement
Description
Test Object
Test Configuration
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Mandatory
A Type 1.2 UNI-N MUST be able to support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS
Verify that a Type 1.2 UNI-N can support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS when
CIR = 0 and EIR > 0
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. One
Bandwidth Profile where CIR=CBS=0 and EIR and EBS are non-zero is applied at the ingress UNI. Testers with
proper PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
Bandwidth Profile
Service
Performance
Test Procedure
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (CIR A = 0) and (CBS A = 0)
Note 2: (0 < EIR A < Ingress UNI Speed), (EBS A ≥ maximum Service Frame size)
Note 3: (Ingress EIR A ≤ Egress UNI Speed)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than EIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤W Y ≤ Z where:
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI
· X A = (EIR A *T + EBS A - F) and Z A = (EIR A *T + EBS A + F)
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters EIR A, EBS A , UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 31: Type 1.2 UNI-N BW Profile Rate Enforcement when CIR > 0 and EIR > 0
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Type 1.2 UNI-N Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0
Test Definition ID
Reference
Document
U1.6.2.5-33.3
Test Type
Conformance
Test Status
Requirement
Description
Test Object
Test Configuration
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Mandatory
A Type 1.2 UNI-N MUST be able to support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS
Verify that a Type 1.2 UNI-N can support color-blind bandwidth profiling to enforce CIR, CBS, EIR and EBS when
CIR > 0 and EIR > 0
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. One
Bandwidth Profile where CIR, CBS, EIR and EBS are non-zero is applied at the ingress UNI. Testers with proper
PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (0 < EIR A < Ingress UNI Speed), (EBS A ≥ maximum Service Frame size)
Note 3: (CIR A + EIR A < Ingress UNI Speed)
Note 4: (Σ Ingress CIRs + EIRs ≤ Egress UNI Speed)
Bandwidth Profile
Service
Performance
Test Procedure
Units
Variables
Results
Bandwidth Profile Parameters
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than CIR A + EIR A to
the ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated
egress UNI. The amount of traffic delivered at the associated egress UNI must fall within the range
X ≤ (W G + W Y ) ≤ Z where:
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI
· X A = ((CIR A + EIR A )*T + CBS A + EBS A - F) and Z A = ((CIR A + EIR A )*T + CBS A + EBS A + F)
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, EIR A, EBS A , UNIs interface speed, time interval T, tolerated variance F,
number and length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 32: Type 1.2 UNI-N Mandatory CIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Mandatory CIR Configuration Granularity
U1.6.2.5-34.1
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST allow configuration to modify CIR in the following granularities
Requirement
Description
Test Object
Test Configuration
·
·
·
·
1 Mbps steps up to 10 Mbps [CIR range 1]
5 Mbps steps beyond 10 Mbps and up to 100 Mbps [CIR range 2]
50 Mbps steps beyond 100 Mbps and up to 1 Gbps [CIR range 3]
500 Mbps steps beyond 1 Gbps [CIR range 4]
Verify that a Type 1.2 UNI-N allows configuration to modify CIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than CIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤W G ≤ Z where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Begin the test with CIR A set to the minimum value (i.e. 1 Mbps) and increment CIR A by the step value defined for the
CIR range.
Repeat the test for each CIR A value until CIR A has been incremented to the UNI speed
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 33: Type 1.2 UNI-N Mandatory EIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Mandatory EIR Configuration Granularity
U1.6.2.5-34.2
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST allow configuration to modify EIR in the following granularities
Requirement
Description
Test Object
Test Configuration
·
·
·
·
1 Mbps steps up to 10 Mbps [EIR range 1]
5 Mbps steps beyond 10 Mbps and up to 100 Mbps [EIR range 2]
50 Mbps steps beyond 100 Mbps and up to 1 Gbps [EIR range 3]
500 Mbps steps beyond 1 Gbps [EIR range 4]
Verify that a Type 1.2 UNI-N allows configuration to modify EIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (CIR A = 0) and (CBS A = 0)
Note 2: (0 < EIR A < Ingress UNI Speed), (EBS A ≥ maximum Service Frame size)
Note 3: (Ingress EIR A ≤ Egress UNI Speed)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than EIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤W Y ≤ Z where:
Test Procedure
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI
· X A = (EIR A *T + EBS A - F) and Z A = (EIR A *T + EBS A + F)
Begin the test with EIR A set to the minimum value (i.e. 1 Mbps) and increment EIR A by the step value defined for the
EIR range.
Repeat the test for each EIR A value until EIR A has been incremented to the UNI speed
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters EIR A, EBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 34: Type 1.2 UNI-N Optional CIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Optional CIR Configuration Granularity
U1.6.2.5-35.1
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD allow configuration to modify CIR in the following granularities
Requirement
Description
Test Object
Test Configuration
·
·
·
·
64 Kbps (DS0 rate) steps up to 1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) [CIR range 1]
1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) steps up to 50 Mbps [CIR range 2]
43.008 Mbps (VC3 rate) steps beyond 50 Mbps and up to 150 Mbps [CIR range 3]
133.12 Mbps (VC4 rate) steps beyond 150 Mbps [CIR range 4]
Verify that a Type 1.2 UNI-N allows configuration to modify CIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1 : (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2 : (Ingress CIR A ≤ Egress UNI Speed)
Note 3 : (EIR A = 0) and (EBS A = 0)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than CIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤W G ≤ Z where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Begin the test with CIR A set to the minimum value (i.e. 64 Kbps) and increment CIR A by the step value defined for
the CIR range.
Repeat the test for each CIR A value until CIR A has been incremented to the UNI speed
Units
Variables
Results
MEF 19
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, number and length λ of the offered
Service Frames, amount of traffic X and amount of traffic Z
Pass or fail
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
Remarks
TEST CASE 35: Type 1.2 UNI-N Optional EIR Configuration Granularity
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Optional EIR Configuration Granularity
U1.6.2.5-35.2
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD allow configuration to modify EIR in the following granularities
Requirement
Description
Test Object
Test Configuration
·
·
·
·
64 Kbps (DS0 rate) steps up to 1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) [EIR range 1]
1.422 Mbps (VC11 rate) or 1.932 Mbps (VC12 rate) steps up to 50 Mbps [EIR range 2]
43.008 Mbps (VC3 rate) steps beyond 50 Mbps and up to 150 Mbps [EIR range 3]
133.12 Mbps (VC4 rate) steps beyond 150 Mbps [EIR range 4]
Verify that a Type 1.2 UNI-N allows configuration to modify EIR in the granularities described in the requirement
description section above
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (CIR A = 0) and (CBS A = 0)
Note 2: (0 < EIR A < Ingress UNI Speed), (EBS A ≥ maximum Service Frame size)
Note 3: (Ingress EIR A ≤ Egress UNI Speed)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate greater than EIR A to the
ingress UNI during a time interval T and measures the number of Service Frames delivered at the associated egress
UNI. The amount of traffic delivered at the associated egress UNI must fall within the range X ≤ W Y ≤ Z where:
Test Procedure
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI
· X A = (EIR A *T + EBS A - F) and Z A = (EIR A *T + EBS A + F)
Begin the test with EIR A set to the minimum value (i.e. 64 Kbps) and increment EIR A by the step value defined for
the EIR range.
Repeat the test for each EIR A value until EIR A has been incremented to the UNI speed
Units
Variables
MEF 19
Number of valid Service Frames
Bandwidth Profile Parameters EIR A, EBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
Results
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 36: Type 1.2 UNI-N CBS Configuration
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N CBS Configuration
U1.6.2.5-36.1
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to at least support CBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
Verify that a Type 1.2 UNI-N can at least support CBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Test Procedure
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ 12176 bytes)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
EIR A
EBS A
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate equal to CIR A to the ingress
UNI during a time interval T. At time T/2 tester injects a burst of ingress Service Frames greater than CBS A . Tester
measures the number of Service Frames delivered at the associated egress UNI. The amount of traffic delivered at
the associated egress UNI must fall within the range X ≤ W G ≤ Z where:
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
· X A = (CIR A *T + CBS A - F) and Z A = (CIR A *T + CBS A + F)
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames, burst size
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 37: Type 1.2 UNI-N EBS Configuration
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N EBS Configuration
U1.6.2.5-36.2
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to at least support EBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
Verify that a Type 1.2 UNI-N can at least support EBS values that are equal to or greater than 8 x MTU =
8 x 1522 bytes = 12176 bytes
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Test Procedure
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
Note 1: (CIR A = 0) and (CBS A = 0)
Note 2: (0 < EIR A < Ingress UNI Speed), (EBS A ≥ 12176 bytes)
Note 3: (Ingress EIR A ≤ Egress UNI Speed)
EIR A
EBS A
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs of length λ at an average rate equal to EIR A to the ingress
UNI during a time interval T. At time T/2 tester injects a burst of ingress Service Frames greater than EBS A . Tester
measures the number of Service Frames delivered at the associated egress UNI. . The amount of traffic delivered
at the associated egress UNI must fall within the range X ≤ W Y ≤ Z where:
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI
· X A = (EIR A *T + EBS A - F) and Z A = (EIR A *T + EBS A + F)
Units
Variables
Results
Number of valid Service Frames
Bandwidth Profile Parameters EIR A, EBS A, UNIs interface speed, time interval T, tolerated variance F, number and
length λ of the offered Service Frames, burst size
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 38: Type 1.2 UNI-N Optional Layer 2 Control Protocol Discard
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Optional Layer 2 Control Protocol Discard
U1.6.2.6-37
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD be able to discard the following L2 Control Protocols
Requirement
Description
·
·
·
·
·
·
·
·
·
Spanning Tree Protocol (STP),
Rapid Spanning Tree Protocol (RSTP),
Multiple Spanning Tree Protocol (MSTP)
All LANs Bridge Management Group Block of Protocol
Generic Attribute Registration Protocol (GARP)
Link Aggregation Control Protocol (LACP)
Marker Protocol
Authentication (802.1x)
802.3x (PAUSE) frames
Test Object
Verify that a Type 1.2 UNI-N can discard each L2 Control Protocol described in the requirement description section
above
Test Configuration
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at the UNI. Testers with proper PHY that matches each UNI are attached to
both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2: (Ingress CIR A ≤ Egress UNI Speed)
Note 3: (EIR A = 0) and (EBS A = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames carrying Layer 2 Control protocols described in the requirement description section
above at the ingress UNI and verifies that the corresponding Service Frames are not delivered at the associated
egress UNI. The L2CPs Destination Address and Ethertype/Length fields must be defined as per the IEEE
standards
Number of valid Service Frames carrying the L2CPs
L2CP, Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 39: Type 1.2 UNI-N Optional Layer 2 Control Protocol Generation
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N Optional Layer 2 Control Protocol Generation
U1.6.2.6-38
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Optional
A Type 1.2 UNI-N SHOULD NOT generate 802.3x PAUSE frames
Verify that a Type 1.2 UNI-N does not generate 802.3x PAUSE frames
One EVC associating two Type 1.2 UNIs is configured. At least one CE-VLAN ID is mapped to the EVC and one
Bandwidth Profile is applied at the ingress UNI. A per Ingress UNI bandwidth profile is applied at the UNI. Testers
with proper PHY that matches each UNI are attached to both UNIs in the configured EVC
INGRESS UNI ‘A’
CE-VLAN ID/EVC
Map
EGRESS UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
Service
Performance
Test Procedure
Units
Variables
Results
Bandwidth Profile Parameters
UNI A
CIR A
CBS A
EIR A
EBS A
Note 1: (0 < CIR A < Ingress UNI Speed/2), (CBS A ≥ maximum Service Frame size)
Note 2: (EIR A = 0) and (EBS A = 0)
Note 3: (Ingress CIR A ≤ Egress UNI Speed)
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs at the ingress UNI, at an average rate equal to the UNI
speed and verifies that no 802.3x PAUSE frames are sent back to its test interfaces
Number of valid Service Frames carrying he L2CPs
Bandwidth Profile Parameters CIR A, CBS A, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 40: Type 1.2 UNI-N Concurrent Point-to-Point and Multipoint EVCs
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N Concurrent Point-to-Point and Multipoint EVCs
U1.6.2.7-40
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support Point-to-Point and Multipoint EVCs concurrently
Verify that a Type 1.2 UNI-N can support Point-to-Point and Multipoint EVCs concurrently
One Multipoint and one Point-to-Point EVCs associating one Type 1.2 ingress UNI and two Type 1.2 egress UNIs
are configured and at least one CE-VLAN ID is mapped per EVC. Per EVC bandwidth profiles are applied at all
UNIs. Testers with proper PHY that matches each UNI are attached to all UNIs in the configured EVCs
UNI ‘A’
UNI ‘B’
UNI ‘C’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
11*
EVC 1
12
EVC 2
12
EVC 2
CE-VLAN ID/EVC
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs conforms to MEF
10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at both ingress and
egress UNIs
PER EVC
Bandwidth Profile
EVC
Bandwidth Profile Parameters
EVC 1
CIR 1
CBS 1
EIR 1
EBS 1
EVC 2
CIR 2
CBS 2
EIR 2
EBS 2
Note 1: (0 < CIR 1,2 < Ingress UNI Speed), (CBS 1,2 ≥ maximum Service Frame size)
Note 2: (Σ Ingress CIRs ≤ Egress UNI Speed)
Note 3: (EIR 1,2 = 0) and (EBS 1,2 = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVCs and
verifies that the corresponding Service Frames are successfully delivered on the proper EVC at the associated UNIs.
Number of valid Service Frames
Bandwidth Profile Parameters CIR 1, CBS 1 , CIR 2, CBS 2, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 41: Type 1.2 UNI-N CE-VLAN ID Preservation
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N CE-VLAN ID Preservation
U1.6.2.8-41
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support CE-VLAN ID preservation
Verify that a Type 1.2 UNI-N can support CE-VLAN ID preservation
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers Service Frames with mapped CE-VLAN IDs bidirectionally at each UNI configured in the EVC and
verifies that the corresponding Service Frames are delivered at the associated UNI with CE-VLAN ID preservation
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 42: Type 1.2 UNI-N CE-VLAN CoS Preservation
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N CE-VLAN CoS Preservation
U1.6.2.9-42
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to support CE-VLAN CoS preservation
Verify that a Type 1.2 UNI-N can support CE-VLAN CoS preservation
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers tagged Service Frames with mapped CE-VLAN ID with all possible CoS values bidirectionally at each
UNI configured in the EVC and verifies that the corresponding Service Frames are delivered at the associated UNI
with CE-VLAN CoS preservation
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 43: Type 1.2 UNI-N Broadcast & Multicast Service Frame Unconditional Delivery
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Type 1.2 UNI-N Broadcast & Multicast Service Frame Unconditional Delivery
U1.6.2.10-43
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to deliver multicast and broadcast Service Frames unconditionally, except:
Requirement
Description
·
·
·
·
·
·
·
·
·
Spanning Tree Protocol (STP),
Rapid Spanning Tree Protocol (RSTP),
Multiple Spanning Tree Protocol (MSTP)
All LANs Bridge Management Group Block of Protocol
Generic Attribute Registration Protocol (GARP)
Link Aggregation Control Protocol (LACP)
Marker Protocol
Authentication (802.1x)
802.3x (PAUSE) frames
Test Object
Verify that a Type 1.2 UNI-N can deliver multicast and broadcast Service Frames unconditionally, except the L2CPs
listed in the requirement description above
Test Configuration
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVC
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers multicast and broadcast Service Frames (except the L2CPs listed in the requirement description above)
bidirectionally at each UNI configured in the EVC and verifies that the corresponding Service Frames are delivered at
the associated UNI
Number of valid Service Frames
Frame Format (broadcast, multicast), Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
TEST CASE 44: Type 1.2 UNI-N Unicast Service Frame Unconditional Delivery
ABSTRACT TEST SUITE FOR UNI TYPE 1
Test Name
Test Definition ID
Reference
Document
Test Type
Test Status
Requirement
Description
Test Object
Test Configuration
Type 1.2 UNI-N Unicast Service Frame Unconditional Delivery
U1.6.1.8-44
MEF 13 [User Network Interface (UNI) Type 1 Implementation Agreement]
Conformance
Mandatory
A Type 1.2 UNI-N MUST be able to deliver all unicast Service Frames unconditionally
Verify that a Type 1.2 UNI-N can deliver all unicast Service Frame unconditionally
One EVC associating two Type 1.2 UNIs is configured and at least one CE-VLAN ID is mapped to the EVC. A per
Ingress UNI bandwidth profile is applied at both UNIs. Testers with proper PHY that matches each UNI are attached
to both UNIs in the configured EVCs
UNI ‘A’
CE-VLAN ID/EVC
Map
UNI ‘B’
CE-VLAN ID
EVC
CE-VLAN ID
EVC
11*
EVC 1
11*
EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1
The CE-VLAN ID for untagged and priority tagged Service Frames is configured to 11 at
both ingress and egress UNIs
PER INGRESS UNI
UNI
Bandwidth Profile
UNI
Bandwidth Profile Parameters
CIR
CBS
EIR
EBS
Note 1: (0 < CIR < Ingress UNI Speed), (CBS ≥ maximum Service Frame size)
Note 2: (Ingress CIR ≤ Egress UNI Speed)
Note 3: (EIR = 0) and (EBS = 0)
Service
Performance
Test Procedure
Units
Variables
Results
Not Specified
Tester offers unicast Service Frames with mapped CE-VLAN IDs with varying destination addresses bidirectionally at
each UNI configured in the EVC and verifies that the corresponding Service Frames are delivered at the associated
UNI
Number of valid Service Frames
Bandwidth Profile Parameters CIR , CBS, UNIs interface speed
Pass or fail
Remarks
MEF 19
© The Metro Ethernet Forum 2007. 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.
Abstract Test Suite for UNI Type 1
11. References
References
Details
IEEE 802.3
IEEE P 802.3 – 2002, Information technology – Telecommunications and information exchange
between systems – Local and metropolitan area networks – Specific requirements – Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) access method and physical
layer specifications, 8 March 2002. (Normative)
IEEE 802.3ae
IEEE 802.3ae-2002Information Technology - Local & Metropolitan Area Networks - Part 3:
Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and
Physical Layer Specifications - Media Access Control Parameters, Physical Layers and
Management Parameters for 10 Gb/s Operation
IEEE 802.1Q
IEEE 802.1Q, 2003 Edition, IEEE Standards for Local and metropolitan area networks—Virtual
Bridged Local Area Networks
MEF 4
Metro Ethernet Network Architecture Framework - Part 1: Generic Framework
MEF 6
Ethernet Services Definitions
MEF 10
Ethernet Services Attributes Phase 1
MEF 11
User Network Interface (UNI) Requirements and Framework
MEF 13
User Network Interface (UNI) Implementation Agreement
RFC 2119
RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner,
http://www.ietf.org/rfc/rfc2119.txt (Normative)
RFC 2285
RFC 2285, “Benchmarking Terminology for LAN Switching Devices”, R. Mandeville,
http://www.ietf.org/rfc/rfc2285.txt
RFC 2544
RFC 2544, “Benchmarking Methodology for Network Interconnect Devices”, S. Bradner, J.
McQuaid, http://www.ietf.org/rfc/rfc2544.txt
RFC 2889
RFC 2889, “Benchmarking Methodology for LAN Switching Devices”, R. Mandeville, J. Perser,
http://www.ietf.org/rfc/rfc2889.txt
MEF 19
© The Metro Ethernet Forum 2007. 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.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising