Bridge Functions Consortium

Similar documents
Bridge Functions Consortium

Bridge Functions Consortium

Bridge Functions Consortium. Bridge Functions Consortium

Bridge Functions Consortium

Ethernet Switching Protocols

Data Center Bridging Consortium

ROUTING CONSORTIUM TEST SUITE

ROUTING CONSORTIUM. Routing Information Protocol Version 2 (RIP) Multi-System Interoperability Test Suite. Technical Document. Revision 2.

ETHERNET TESTING SERVICES

Data Center Bridging Consortium

UNH IOL iscsi CONSORTIUM

ROUTING CONSORTIUM. Virtual Router Redundancy Protocol Version 3 Interoperability Test Suite. Technical Document. Draft Version

University of New Hampshire InterOperability Laboratory Ethernet in the First Mile Consortium

UNH IOL iscsi CONSORTIUM

THE ETHERNET IN THE FIRST MILE CONSORTIUM. Annex 4A MAC Conformance Test Suite Version 1.0 Technical Document

IWARP Consortium. Network Impairments Test Suite. Technical Document. Revision 0.3

ROUTING CONSORTIUM. Open Shortest Path First (OSPF) Multi-System Interoperability Test Suite. Technical Document. Revision 1.6

Fast Ethernet Consortium

UNH-IOL PCIe CONSORTIUM

WLAN The Wireless Local Area Network Consortium

ROUTING CONSORTIUM. Virtual Router Redundancy Protocol Operations Test Suite. Technical Document. Revision 2.5

Chapter 4 Configuring Switching

ROUTING CONSORTIUM. Intermediate System to Intermediate System (IS-IS) Operations Test Suite. Technical Document. Revision 4.6

VLAN - SP6510P8 2013/4. Copyright 2011 Micronet Communications, INC

IPv6 Application Test Service

ROUTING CONSORTIUM TEST SUITE

Technical Specification MEF 27. Abstract Test Suite For. May 20 th, 2010

40 AND 100 GIGABIT ETHERNET TESTING SERVICE

University of New Hampshire InterOperability Laboratory Ethernet Consortia

IPv6 CONSORTIUM TEST SUITE Address Architecture Conformance Test Specification

Bridge Functions Consortium Spanning Tree Protocol Operations Test Suite Version 2.0

IN THE FIRST MILE CONSORTIUM. Clause 65 Test Suite v1.1 Technical Document. Last Updated: March 23, :43pm

Ethernet. Clause 22, 28, and 40 Management Registers Test Suite V4.0. Technical Document. Last Updated: Monday, March 9, :15 PM

Routing Between VLANs Overview

Ethernet. MDIO Auto-Negotiation Registers Test Suite For Twisted-Pair PHYs V1.0. Technical Document. Last Updated: Thursday March 19, :21 AM

WLAN The Wireless Local Area Network Consortium

IP CONSORTIUM TEST SUITE Internet Protocol, Version 6

10 GIGABIT ETHERNET. 10GBASE-T Physical Layer Interoperability Test Suite Version 1.0. Technical Document. Last Updated: October 3, :30 PM

ROUTING CONSORTIUM. Open Shortest Path First (OSPF) NSSA Option Test Suite. Technical Document. Revision 1.9

Powered by Accton. ES Port Gigabit Web-Smart Switch. Management Guide.

University of New Hampshire InterOperability Laboratory Gigabit Ethernet Consortium

AN-135. Introduction. VLAN Overview IEEE 802.1Q VLAN Q Tag Based and Port Based VLAN Function and Setting in KSZ8995M/MA

University of New Hampshire InterOperability Laboratory Ethernet Consortium

Ethernet. Clause 40 Auto-Crossover Test Suite v1.6. Technical Document. Last Updated: December 22, 2005, 11:07 a.m.

Q VLAN User s Guide

Managed Ethernet Switch User s Manual

Fast Ethernet Consortium

NCT240 IP DSLAM with IAC4500 VLAN Tagging Implementation

SERIAL ATTACHED SCSI (SAS) CONSORTIUM

The University of New Hampshire InterOperability Laboratory 10 GIGABIT ETHERNET. Clause 46 10Gb/s RS Test Suite Version 1.1 Technical Document

Hands-On Metro Ethernet Carrier Class Networks

UNH IOL iscsi CONSORTIUM

SWP-0208G, 8+2SFP. 8-Port Gigabit Web Smart Switch. User s Manual

UNH IOL SERIAL ATTACHED SCSI (SAS) CONSORTIUM

Risanuri Hidayat. 13/03/2012 Jurusan Teknik Elektro dan Tekn Informasi UGM

Ethernet. Clause 40 Auto-Crossover Test Suite V2.2. Technical Document. Last Updated: March 24, 2009, 3:15 p.m.

AUTOMOTIVE ETHERNET CONSORTIUM

1. DUT and Test Equipments Functionality Test... 5

Table of Contents 1 VLAN Configuration 1-1

Technical Specification MEF 14. Abstract Test Suite for Traffic Management Phase 1. November, 2005

Sections Describing Standard Software Features

Junos Enterprise Switching

University of New Hampshire InterOperability Laboratory Gigabit Ethernet Consortium

Application Notes for Foundry Networks FastIron Super X Switch with Avaya Communication Manager - Issue 1.0

University of New Hampshire InterOperability Laboratory Ethernet Consortium

10 GIGABIT ETHERNET CONSORTIUM. 10GBASE-R PCS Test Suite V1.0 Technical Document. Last Updated: September 30, :30pm

Routing Between VLANs Overview

UNH-IOL. FC-1 Conformance Test Suite Version 4.3. Technical Document. Last Updated: February 23, 2008

ETHERNET. Clause 28 Auto-Negotiation State Machine Base Page Exchange Test Suite v5.5. Technical Document. Last Updated: July 22, :11PM

WLAN The Wireless Local Area Network Consortium

How to configure the IAC4500 Internet Access Controller for Billing by Volume Application with NCT480 IP DSLAM using port location mapping

Sections Describing Standard Software Features

10 GIGABIT ETHERNET CONSORTIUM. RS Test Suite V1.2a Technical Document. Last Updated: June 7, :30 pm

VLAN. Mario Baldi. Pietro Nicoletti. Politecnico di Torino. Studio Reti

Switched Ethernet Virtual LANs

OPEN TC11 Switch Semiconductor Test Specification Version 1.0

Configuring Access and Trunk Interfaces

University of New Hampshire InterOperability Laboratory Ethernet Consortium

Configuring Port-Based and Client-Based Access Control (802.1X)

Point-to-Multipoint and Multipoint-to-Multipoint Services on PBB-TE System

Comment A: Text for Sequencing sublayer

LLDP-MED Interoperability

GIGABIT ETHERNET CONSORTIUM

Table of Contents 1 LLDP Configuration 1-1

User Manual ES-5808PHG. Gigabit 8-Port 802.3at PoE Web Smart Switch

Voice over IP Consortium

Wireless LAN Consortium

UNH-IOL FIBRE CHANNEL CONSORTIUM

Contents. Configuring LLDP 2

Technical Specification MEF 37. Abstract Test Suite for ENNI. January 2012

RADview-EMS/NGN. Element Management System for NGN Applications ACE-201/ RAD Data Communications Publication 06/07

DSL Consortium. VDSL2 Rate vs. Reach Interoperability Test Suite (V2RR) Version Last Updated: March 24, 2008

Intel IXP400 Software: VLAN and QoS Application Version 1.0

BreezeACCESS VL Security

Configure Virtual LANs in Layer 2 VPNs

UNH-IOL iscsi CONSORTIUM

Wireless LAN Consortium

ETHERNET. Clause 28 Auto-Negotiation Next Page Exchange Test Suite v2.3. Technical Document. Last Updated: Friday, February 03, :22 AM

University of New Hampshire InterOperability Laboratory Ethernet Consortium

Developing Standards for Metro Ethernet Networks

Transcription:

Hardware Rate Limiting Feature Verification Test Suite Version 0.1 Last Updated: 2005-09-05 121 Technology Drive, Suite 2 University of New Hampshire Durham, NH 03824 Phone: (603) 862-0090 www.iol.unh.edu Fax: (603) 862-4181 2006 University of New Hampshire. All Rights Reserved.

TABLE OF CONTENTS The University of New Hampshire TABLE OF CONTENTS... i MODIFICATION RECORD... ii ACKNOWLEDGEMENTS...iii INTRODUCTION... iv REFERENCES... v DEFINITION OF TERMS... vi Abbreviations and Acronyms:... vi Definitions:...vi TEST ORGANIZATION... vii TEST SETUP...viii GROUP 1: Egress Hardware Rate Limiting... 1 Rate.Ver.1.1: Egress Hardware Rate Limiting... 2 Rate.Ver.1.2: Egress Hardware Rate Limiting Granularity Verification... 5 Rate.Ver.1.3: Egress Rate Limiting and Frame Queuing... 7 GROUP 2: Ingress Hardware Rate Limiting... 10 Rate.Ver.2.1: Ingress Rate Limiting... 11 Rate.Ver.2.2: Ingress Hardware Rate Limiting Granularity Verification... 14 Rate.Ver.2.3: Ingress Hardware Rate Limiting and Frame Queuing... 16 GROUP 3: Ingress/Egress Hardware Rate Limiting... 18 Rate.Ver.3.1: Ingress/Egress Rate Limiting... 19 TEST FRAMES... 22 i Jumbo Frame Feature Verification Test Suite

MODIFICATION RECORD The University of New Hampshire Version Date Editor(s) Comments 0.1 2005-09-05 Curtis Knittle Curtis Simonson Initial Draft ii Jumbo Frame Feature Verification Test Suite

ACKNOWLEDGEMENTS The University of New Hampshire The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. Curtis Knittle Curtis Simonson Harmonic, Inc. UNH InterOperability Lab iii Jumbo Frame Feature Verification Test Suite

INTRODUCTION The University of New Hampshire The University of New Hampshire s (UNH-IOL) is an institution designed to improve the interoperability of standards based products by providing an environment where a product can be tested against other implementations of a standard. This suite of tests has been developed to help implementers evaluate the functionality of their Hardware Rate Limiting capable products. Hardware rate limiting enables providers to pinpoint bandwidth control and provision bandwidth dynamically. Although rate limiting can sometimes place a very heavy burden on a router's central processor, thereby reducing system performance, some manufacturers offer rate-enabled line cards to ensure that the system's performance is not degraded. 1 This test suite has been designed based on the set of common accepted practices that pertain to Hardware Rate Limiting. The test suite is designed to help determine whether or not the DUT will behave in accordance with the industry standard practice during normal operation. These tests are not designed as performance tests. The relative performance of Hardware Rate Limiting capable devices (e.g. rate granularity, burst handling, etc.) is beyond the scope of this document. These tests are not designed as conformance tests. Rather, they provide one method to isolate problems within a Hardware Rate Limiting capable device that may affect interoperability. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other Hardware Rate Limiting capable devices. However, combined with satisfactory completion of interoperability testing, these tests provide a reasonable level of confidence that the DUT will function well in most Hardware Rate Limiting capable environments. 1 Dynamic Provisioning: the New Mantra - Technology Information, Andrew Feldman, Telecommunications Magazine Online www.telecommagazine.com iv Jumbo Frame Feature Verification Test Suite

REFERENCES The University of New Hampshire The following documents are referenced in this text: [IEEE Std 802.1D -2004] [IEEE Std 802.1Q -2003] IEEE Computer Society LAN/MAN Standards Committee, Media Access Control (MAC) Bridges IEEE Computer Society LAN/MAN Standards Committee, Virtual Bridged Local Area Networks v Jumbo Frame Feature Verification Test Suite

DEFINITION OF TERMS Abbreviations and Acronyms: The University of New Hampshire DUT Device Under Test DUT.TS Port on the DUT connected to Test Station (ex. DUT.TS1 refers to the Port on the DUT connected to Test Station 1) MTU Maximum Transmission Unit TS Test Station (ex. TS1 refers to Test Station 1) Definitions: Device Under Test Test Station Frame Jumbo Frame Untagged frame Virtual Bridged Local Area Network (LAN) Virtual Local Area Network (VLAN) VLAN-aware VLAN-tagged frame VLAN-unaware The Bridge on which the Rate.ver test suite is being conducted. A tool that supports the analysis and generation of test traffic, i.e. MAC frames. A unit of data transmission on an IEEE 802 LAN MAC that conveys a PDU between MAC Service users. There are three types of frame; untagged, VLAN-tagged, and priority-tagged. An Ethernet frame containing a data size greater than 1500-bytes. An untagged frame is a frame that does not contain a tag header immediately following the Source MAC Address field of the frame [ ]. A Bridged LAN in which the existence of one or more VLAN-aware Bridges allows the definition, creation, and maintenance of VLANs. A subset of the active topology of a Bridged Local Area Network. Associated with each VLAN is a VLAN Identifier (VID). A property of Bridges or end stations that recognize and support VLANtagged frames. A tagged frame whose tag header carries both VLAN identification and priority information. A property of Bridges or end stations that do not recognize VLANtagged frames. vi Jumbo Frame Feature Verification Test Suite

TEST ORGANIZATION The University of New Hampshire This document organizes tests by group based on related test methodology or goals. Each group begins with a brief set of comments pertaining to all tests within that group. This is followed by a series of description blocks; each block describes a single test. The format of the description block is as follows: Test Label: Purpose: References: Resource Requirements: Discussion: Test Layout: Procedure: Observable Results: Possible Problems: The test label and title comprise the first line of the test block. The test label is the concatenation of the short test suite name, group number, and the test number within the group, separated by periods. The test number is the group number and the test number, also separated by a period. So, test label Rate.Ver.1.2 refers to the second test of the first test group in the Hardware Rate Limiting Feature Verification test suite. The test number is 1.2. The Purpose is a short statement describing what the test attempts to achieve. It is usually phrased as a simple assertion of the feature or capability to be tested. The References section lists cross-references to the specifications and documentation that might be helpful in understanding and evaluating the test and results. The Resource Requirements section specifies the software, hardware, and test equipment that will be needed to perform the test. The Discussion is a general discussion of the test and relevant section of the specification, including any assumptions made in the design or implementation of the test as well as known limitations. The Discussion is a general discussion of the test and relevant section of the specification, including any assumptions made in the design or implementation of the test as well as known limitations. This diagram shows how the Test Systems, DUT, and any other Devices used should be connected for this test. Elements of the Procedure may change the Layout. This section of the test description contains the step-by-step instructions for carrying out the test. These steps include such things as enabling interfaces, disconnecting links between devices, and sending MAC frames from a Test Station. The test procedure also cues the tester to make observations, which are interpreted in accordance with the observable results given for that test part. This section lists observable results that can be examined by the tester to verify that the DUT is operating properly. When multiple observable results are possible, this section provides a short discussion on how to interpret them. The determination of a PASS or FAIL for each test is usually based on how the behavior of the DUT compares to the results described in this section. This section contains a description of known issues with the test procedure, which may affect test results in certain situations. vii Jumbo Frame Feature Verification Test Suite

TEST SETUP The University of New Hampshire Default Settings: DUT Port Admin Status Enabled (all ports) Ageing Time 300 seconds Bridge Spanning Tree Admin Status Disabled PVID 1 (all ports) VLAN Membership 1 untagged (all ports) Port Frame Priority 0 QoS/CoS Bridge Admin Status Enabled QoS/CoS Bridge Mode Strict Priority-to-Transmission Queue Mapping DUT Default DUT s Bridge Filtering Database (Content Addressable Memory) No entries* Rate Limiting Bridge Admin Status Enabled Rate Limiting Port Status Enabled Rate Limiting Port Value 100% (full line rate) *This excludes reserved multicast MAC addresses. Example Priority-to-Queue Mapping (four egress queues) Priority Value Egress Queue 0 0 1 0 2 1 3 1 4 2 5 2 6 3 7 3 viii Jumbo Frame Feature Verification Test Suite

GROUP 1: Egress Hardware Rate Limiting Scope Overview To examine the DUT s Egress (transmission) Hardware Rate Limiting functionality. Egress Hardware Rate Limiting is used to limit the egress (transmission) rate of a Bridge Port. Generally the egress rate limit is configured as a percent of total line rate, with a configuration specific granularity. Egress Hardware Rate Limiting may be deployed by Service Providers wishing to limit the download bandwidth of a particular subscriber. This Group of Tests examines the DUT s Egress Hardware Rate Limiting functionality, including rate limit accuracy, configuration granularity and multiple frame types. 1 Jumbo Frame Feature Verification Test Suite

Rate.Ver.1.1: Egress Hardware Rate Limiting Purpose: To examine the DUT s Egress Hardware Rate Limiting functionality. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Egress Hardware Rate Limiting capabilities indicate support for the configuration of egress (transmission) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s egress rate limiting accuracy and the effect of untagged and VLAN-tagged frames on the DUT s Egress Hardware Rate Limiting capabilities. Test Layout: Figure 1 Egress Rate Limiting 2 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Egress Hardware Rate Limiting Granularity and Range 1. Ensure that the default values are configured on the DUT. 2. Record the DUT s Egress Hardware Rate Limiting granularity and range, as configurable through any/all configuration methods. Part B: Egress Hardware Rate Limiting Verification 3. Ensure that the default values are configured on the DUT. 4. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 5. Start capture on TS1, TS2 and TS3. 6. Wait until TS3 captures 1000 frames. 7. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 8. Set DUT.TS3 s Egress Hardware Rate Limit to 75% line rate. 9. Repeat Steps 4 through 7. 10. Set DUT.TS3 s Egress Hardware Rate Limit to 50% line rate. 11. Repeat Steps 4 through 7. 12. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 13. Repeat Steps 4 through 7. 14. Set DUT.TS3 s Egress Hardware Rate Limit to 1% line rate. 15. Repeat Steps 4 through 7. Part C: Egress Hardware Rate Limiting Verification VLAN tagged frames 16. Ensure that the default values are configured on the DUT. 17. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 18. Set all DUT.TSs s PVID to 1. 19. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 20. Start capture on TS1, TS2 and TS3. 21. Wait until TS3 captures 1000 frames. 22. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 23. Set DUT.TS3 s Egress Hardware Rate Limit to 75% line rate. 24. Repeat Steps 19 through 22. 25. Set DUT.TS3 s Egress Hardware Rate Limit to 50% line rate. 26. Repeat Steps 19 through 22. 27. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 28. Repeat Steps 19 through 22. 29. Set DUT.TS3 s Egress Hardware Rate Limit to 1% line rate. 30. Repeat Steps 19 through 22. 3 Jumbo Frame Feature Verification Test Suite

Observable Results: In Part A, during Step 2, record the DUT s Egress Hardware Rate Limiting granularity and range. In Part B, during Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture all frames transmitted by TS1. In Part B, during Step 9, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 75% of the bits transmitted by TS1. In Part B, during Step 11, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 50% of the bits transmitted by TS1. In Part B, during Step 13, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 25% of the bits transmitted by TS1. In Part B, during Step 15, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 1% of the bits transmitted by TS1. In Part C, during Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture all frames transmitted by TS1, tagged for VID 2. In Part C, during Step 24, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 75% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 26, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 50% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 28, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 25% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 30, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 1% of the bits transmitted by TS1, tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: This Test cannot be completed, if the DUT does not support Egress Hardware Rate Limiting. No further Egress Hardware Rate Limiting testing can be performed. In Part B, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. In Part C, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. 4 Jumbo Frame Feature Verification Test Suite

Rate.Ver.1.2: Egress Hardware Rate Limiting Granularity Verification Purpose: To examine the DUT s Egress Hardware Rate Limiting configuration granularity. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Egress Hardware Rate Limiting capabilities indicate support for the configuration of egress (transmission) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s egress rate limit configuration granularity, with both untagged and VLAN-tagged frames. Test Layout: Figure 2 Egress Hardware Rate Limiting Granularity Verification 5 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Egress Hardware Rate Limiting Granularity Verification 1. Ensure that the default values are configured on the DUT. 2. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 3. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 4. Start capture on TS1, TS2 and TS3. 5. Wait until TS3 captures 1000 frames. 6. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 7. Set DUT.TS3 s Egress Hardware Rate Limit to 26% line rate. 8. Repeat Steps 3 through 6. 9. Set DUT.TS3 s Egress Hardware Rate Limit to 27% line rate. 10. Repeat Steps 3 through 6. Part B: Egress Hardware Rate Limiting Granularity Verification VLAN tagged frames 11. Ensure that the default values are configured on the DUT. 12. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 13. Set all DUT.TSs s PVID to 1. 14. Set DUT.TS3 s Egress Hardware Rate Limit to 50% line rate. 15. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 16. Start capture on TS1, TS2 and TS3. 17. Wait until TS3 captures 1000 frames. 18. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 19. Set DUT.TS3 s Egress Hardware Rate Limit to 49% line rate. 20. Repeat Steps 15 through 18. 21. Set DUT.TS3 s Egress Hardware Rate Limit to 48% line rate. 22. Repeat Steps 15 through 18. Observable Results: In Part A, during Step 5, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 25% of the bits transmitted by TS1. In Part A, during Step 8, repetition of Step 5, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 26% of the bits transmitted by TS1. In Part A, during Step 10, repetition of Step 5, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 27% of the bits transmitted by TS1. In Part B, during Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 50% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 20, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 49% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 22, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture all frames transmitted by TS1. TS3 must capture 48% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: In Part A, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. In Part B, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. 6 Jumbo Frame Feature Verification Test Suite

Rate.Ver.1.3: Egress Rate Limiting and Frame Queuing Purpose: To examine the DUT s Egress Rate Limiting and frame queuing mechanisms. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Hardware Egress Rate Limiting capabilities indicate support for the configuration of egress (transmission) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s rate limiting and frame queuing mechanisms, with both untagged and VLAN-tagged frames. Test Layout: Figure 3 Egress Hardware Rate Limiting and Frame Queuing 7 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Egress Hardware Rate Limiting and Frame Queuing 1. Ensure that the default values are configured on the DUT. 2. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 3. Transmit, from TS3, one Src22 frame. 4. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 5. Continuously transmit, from TS2, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 6. Start capture on TS1, TS2 and TS3. 7. Wait until TS3 captures 1000 frames. 8. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 9. Set DUT.TS3 s Egress Hardware Rate Limit to 75% line rate. 10. Repeat Steps 3 through 8. Part B: Egress Hardware Rate Limiting and Frame Queuing VLAN tagged frames 11. Ensure that the default values are configured on the DUT. 12. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 13. Set all DUT.TSs s PVID to 1. 14. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 15. Transmit, from TS3, one Src22_Tag2 frame. 16. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 17. Continuously transmit, from TS2, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 18. Start capture on TS1, TS2 and TS3. 19. Wait until TS3 captures 1000 frames. 20. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 21. Set DUT.TS3 s Hardware Egress Rate Limit to 75% line rate. 22. Repeat Steps 15 through 20. 8 Jumbo Frame Feature Verification Test Suite

Observable Results: In Part A, during Step 7, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture 12.5% of the bits transmitted by TS1. TS3 must capture 12.5% of the bits transmitted by TS2. TS3 must capture 25% of the total bits transmitted by TS1 and TS2. TS3 must capture an evenly distributed sample of frames from TS1 and TS2. In Part A, during Step 10, repetition of Step 7, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture 37.5% of the bits transmitted by TS1. TS3 must capture 37.5% of the bits transmitted by TS2. TS3 must capture 75% of the bits transmitted by TS1 and TS2. TS3 must capture an evenly distributed sample of frames from TS1 and TS2. In Part B, during Step 19, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture 12.5% of the bits transmitted by TS1. TS3 must capture 12.5% of the bits transmitted by TS2. TS3 must capture 25% of the total bits transmitted by TS1 and TS2. TS3 must capture an evenly distributed sample of frames from TS1 and TS2, tagged for VID 2. In Part B, during Step 22, repetition of Step 19, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture 37.5% of the bits transmitted by TS1. TS3 must capture 37.5% of the bits transmitted by TS2. TS3 must capture 75% of the bits transmitted by TS1 and TS2. TS3 must capture an evenly distributed sample of frames from TS1 and TS2, tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: In Part A, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. In Part B, this Test must be modified, if the DUT does not support the specified Egress Hardware Rate Limit values. 9 Jumbo Frame Feature Verification Test Suite

GROUP 2: Ingress Hardware Rate Limiting Scope Overview To examine the DUT s Ingress (reception) Hardware Rate Limiting functionality. Ingress Hardware Rate Limiting is used to limit the ingress (reception) rate of a Bridge Port. Generally the ingress rate limit is configured as a percent of total line rate, with a configuration specific granularity. Ingress Hardware Rate Limiting may be deployed by Service Providers wishing to limit the upload bandwidth of a particular subscriber. This Group of Tests examines the DUT s Ingress Hardware Rate Limiting functionality, including rate limit accuracy, configuration granularity and multiple frame types. 10 Jumbo Frame Feature Verification Test Suite

Rate.Ver.2.1: Ingress Rate Limiting The University of New Hampshire Purpose: To examine the DUT s Ingress Hardware Rate Limiting functionality. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Ingress Hardware Rate Limiting capabilities indicate support for the configuration of ingress (reception) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s ingress rate limiting accuracy and the effect of untagged and VLAN-tagged frames on the DUT s Ingress Hardware Rate Limiting capabilities. Test Layout: Figure 4 Ingress Hardware Rate Limiting 11 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Ingress Hardware Rate Limiting Granularity and Range 1. Ensure that the default values are configured on the DUT. 2. Record the DUT s Ingress Hardware Rate Limiting granularity and range, as configurable through any/all configuration methods. Part B: Ingress Hardware Rate Limiting Verification 3. Ensure that the default values are configured on the DUT. 4. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 5. Start capture on TS1, TS2 and TS3. 6. Wait until TS3 captures 1000 frames. 7. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 8. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 9. Repeat Steps 4 through 7. 10. Set DUT.TS1 s Ingress Hardware Rate Limit to 50% line rate. 11. Repeat Steps 4 through 7. 12. Set DUT.TS1 s Ingress Hardware Rate Limit to 25% line rate. 13. Repeat Steps 4 through 7. 14. Set DUT.TS1 s Ingress Hardware Rate Limit to 1% line rate. 15. Repeat Steps 4 through 7. Part C: Ingress Hardware Rate Limiting Verification VLAN tagged frames 16. Ensure that the default values are configured on the DUT. 17. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 18. Set all DUT.TSs s PVID to 1. 19. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 20. Start capture on TS1, TS2 and TS3. 21. Wait until TS3 captures 1000 frames. 22. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 23. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 24. Repeat Steps 19 through 22. 25. Set DUT.TS1 s Ingress Hardware Rate Limit to 50% line rate. 26. Repeat Steps 19 through 22. 27. Set DUT.TS1 s Ingress Hardware Rate Limit to 25% line rate. 28. Repeat Steps 19 through 22. 29. Set DUT.TS1 s Ingress Hardware Rate Limit to 1% line rate. 30. Repeat Steps 19 through 22. 12 Jumbo Frame Feature Verification Test Suite

Observable Results: In Part A, during Step 2, record the DUT s Ingress Hardware Rate Limiting granularity and range. In Part B, during Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture all frames transmitted by TS1. In Part B, during Step 9, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 75% of the bits transmitted by TS1. In Part B, during Step 11, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 50% of the bits transmitted by TS1. In Part B, during Step 13, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 25% of the bits transmitted by TS1. In Part B, during Step 15, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 1% of the bits transmitted by TS1. In Part C, during Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture all frames transmitted by TS1, tagged for VID 2. In Part C, during Step 24, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 75% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 26, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 50% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 28, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 25% of the bits transmitted by TS1, tagged for VID 2. In Part C, during Step 30, repetition of Step 21, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 1% of the bits transmitted by TS1, tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: This Test cannot be completed, if the DUT does not support Ingress Hardware Rate Limiting. No further Ingress Hardware Rate Limiting testing can be performed. In Part B, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. In Part C, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. 13 Jumbo Frame Feature Verification Test Suite

Rate.Ver.2.2: Ingress Hardware Rate Limiting Granularity Verification Purpose: To examine the DUT s Ingress Hardware Rate Limiting configuration granularity. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Ingress Hardware Rate Limiting capabilities indicate support for the configuration of ingress (reception) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s ingress rate limit configuration granularity, with both untagged and VLAN-tagged frames. Test Layout: Figure 5 Ingress Hardware Rate Limiting Granularity Verification 14 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Ingress Hardware Rate Limiting Granularity Verification 1. Ensure that the default values are configured on the DUT. 2. Set DUT.TS1 s Ingress Hardware Rate Limit to 25% line rate. 3. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 4. Start capture on TS1, TS2 and TS3. 5. Wait until TS3 captures 1000 frames. 6. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 7. Set DUT.TS1 s Ingress Hardware Rate Limit to 26% line rate. 8. Repeat Steps 3 through 6. 9. Set DUT.TS1 s Ingress Hardware Rate Limit to 27% line rate. 10. Repeat Steps 3 through 6. Part B: Ingress Hardware Rate Limiting Granularity Verification VLAN tagged frames 11. Ensure that the default values are configured on the DUT. 12. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 13. Set all DUT.TSs s PVID to 1. 14. Set DUT.TS1 s Ingress Hardware Rate Limit to 50% line rate. 15. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 16. Start capture on TS1, TS2 and TS3. 17. Wait until TS3 captures 1000 frames. 18. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 19. Set DUT.TS1 s Ingress Hardware Rate Limit to 49% line rate. 20. Repeat Steps 15 through 18. 21. Set DUT.TS1 s Ingress Hardware Rate Limit to 48% line rate. 22. Repeat Steps 15 through 18. Observable Results: In Part A, during Step 5, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 25% of the bits transmitted by TS1. In Part A, during Step 8, repetition of Step 5, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 26% of the bits transmitted by TS1. In Part A, during Step 10, repetition of Step 5, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 27% of the bits transmitted by TS1. In Part B, during Step 17, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 50% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 20, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 49% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 22, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 and TS3 must capture 48% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: In Part A, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. In Part B, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. 15 Jumbo Frame Feature Verification Test Suite

Rate.Ver.2.3: Ingress Hardware Rate Limiting and Frame Queuing Purpose: To examine the DUT s Ingress Hardware Rate Limiting and frame queuing mechanisms. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Ingress Hardware Rate Limiting capabilities indicate support for the configuration of ingress (reception) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s ingress rate limiting and frame queuing mechanisms, with both untagged and VLAN-tagged frames. Test Layout: Figure 6 Ingress Hardware Rate Limiting and Frame Queuing 16 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Ingress Hardware Rate Limiting and Frame Queuing 1. Ensure that the default values are configured on the DUT. 2. Set DUT.TS1 s Ingress Hardware Rate Limit to 25% line rate. 3. Transmit, from TS3, one Src22 frame. 4. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 5. Continuously transmit, from TS2, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 6. Start capture on TS1, TS2 and TS3. 7. Wait until TS3 captures 1000 frames. 8. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 9. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 10. Repeat Steps 3 through 8. Part B: Ingress Rate Limiting and Frame Queuing VLAN tagged frames 11. Ensure that the default values are configured on the DUT. 12. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 13. Set all DUT.TSs s PVID to 1. 14. Set DUT.TS1 s Ingress Hardware Rate Limit to 25% line rate. 15. Transmit, from TS3, one Src22_Tag2 frame. 16. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 17. Continuously transmit, from TS2, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 18. Start capture on TS1, TS2 and TS3. 19. Wait until TS3 captures 1000 frames. 20. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 21. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 22. Repeat Steps 15 through 20. Observable Results: In Part A, during Step 7, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture a sample of frames from TS1 and TS2, such that TS3 captures more frames from TS2 than TS1. In Part A, during Step 10, repetition of Step 7, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture a sample of frames from TS1 and TS2, such that TS3 captures more frames from TS2 than TS1. In Part B, during Step 19, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture a sample of frames from TS1 and TS2, such that TS3 captures more frames from TS2 than TS1, tagged for VID 2. In Part B, during Step 22, repetition of Step 19, TS1 and TS2 must not capture any frames transmitted by TS1 or TS2. TS3 must capture a sample of frames from TS1 and TS2, such that TS3 captures more frames from TS2 than TS1, tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: In Part A, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. In Part B, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. 17 Jumbo Frame Feature Verification Test Suite

GROUP 3: Ingress/Egress Hardware Rate Limiting Scope Overview To examine the DUT s Ingress and Egress (reception) Hardware Rate Limiting functionality simultaneously. Ingress Hardware Rate Limiting is used to limit the ingress (reception) rate of a Bridge Port. Egress Hardware Rate Limiting is used to limit the egress (transmission) rate of a Bridge Port. Generally the ingress and egress rate limits are configured as a percent of total line rate, with a configuration specific granularity. This Group of Tests examines the DUT s Ingress and Egress Hardware Rate Limiting interaction, by configuring the DUT to simultaneously limit ingress and egress on separate Bridge Ports. 18 Jumbo Frame Feature Verification Test Suite

Rate.Ver.3.1: Ingress/Egress Rate Limiting The University of New Hampshire Purpose: To examine the DUT s Ingress and Egress Hardware Rate Limiting functionality simultaneously. References: IEEE Std 802.3-2002 IEEE Std 802.1D-2004 IEEE Std 802.1Q-2003 Resource Requirements: 3 Test Stations Discussion: Ethernet devices claiming Ingress Hardware Rate Limiting capabilities indicate support for the configuration of ingress (reception) rate limits on a particular Bridge Port, or set of Bridge Ports. Ethernet devices claiming Egress Hardware Rate Limiting capabilities indicate support for the configuration of egress (reception) rate limits on a particular Bridge Port, or set of Bridge Ports. This Test examines the DUT s egress rate limiting accuracy and the effect of untagged and VLAN-tagged frames on the DUT s Egress Hardware Rate Limiting capabilities. Test Layout: Figure 7 Ingress/Egress Hardware Rate Limiting 19 Jumbo Frame Feature Verification Test Suite

Procedure: Part A: Ingress Hardware Rate Limiting Verification 1. Ensure that the default values are configured on the DUT. 2. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 3. Set DUT.TS3 s Egress Hardware Rate Limit to 50% line rate. 4. Continuously transmit, from TS1, Dest22 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 5. Start capture on TS1, TS2 and TS3. 6. Wait until TS3 captures 1000 frames. 7. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 8. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 9. Repeat Steps 4 through 7. 10. Set DUT.TS1 s Ingress Hardware Rate Limit to 50% line rate. 11. Repeat Steps 4 through 7. Part B: Ingress Hardware Rate Limiting Verification 12. Ensure that the default values are configured on the DUT. 13. Set all DUT.TSs s VLAN membership to VID 2, tagged, and VID 1, untagged. 14. Set all DUT.TSs s PVID to 1. 15. Set DUT.TS1 s Ingress Hardware Rate Limit to 75% line rate. 16. Set DUT.TS3 s Egress Hardware Rate Limit to 50% line rate. 17. Continuously transmit, from TS1, Dest22_Tag2 frames, at 100% line rate, where X = 64 to Y, in increments of 1. 18. Start capture on TS1, TS2 and TS3. 19. Wait until TS3 captures 1000 frames. 20. Stop capture on TS1, TS2 and TS3, and observe the captured frames (if any). 21. Set DUT.TS3 s Egress Hardware Rate Limit to 25% line rate. 22. Repeat Steps 15 through 18. 23. Set DUT.TS1 s Ingress Hardware Rate Limit to 50% line rate. 24. Repeat Steps 15 through 18. 20 Jumbo Frame Feature Verification Test Suite

Observable Results: In Part A, during Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture 75% of bits transmitted by TS1. TS3 must capture 50% of bits transmitted by TS1. In Part A, during Step 9, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture 75% of bits transmitted by TS1. TS3 must capture 25% of the bits transmitted by TS1. In Part A, during Step 11, repetition of Step 6, TS1 must not capture any frames transmitted by TS1. TS2 must capture 50% of bits transmitted by TS1. TS3 must capture 25% of the bits transmitted by TS1. In Part B, during Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture 75% of bits transmitted by TS1, tagged for VID 2. TS3 must capture 50% of bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 20, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture 75% of bits transmitted by TS1, tagged for VID 2. TS3 must capture 25% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. In Part B, during Step 22, repetition of Step 17, TS1 must not capture any frames transmitted by TS1. TS2 must capture 50% of bits transmitted by TS1, tagged for VID 2. TS3 must capture 25% of the bits transmitted by TS1. All frames captured by TS3, transmitted by TS1, must be tagged for VID 2. All frames received during this Test must contain a CRC value equal to the frame s original CRC value. Possible Problems: This Test cannot be completed, if the DUT does not support Ingress and Egress Hardware Rate Limiting. No further Ingress/Egress Hardware Rate Limiting testing can be performed. In Part A, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. In Part B, this Test must be modified, if the DUT does not support the specified Ingress Hardware Rate Limit values. 21 Jumbo Frame Feature Verification Test Suite

TEST FRAMES The University of New Hampshire Src22 Octet(s) Description Value (all numbers are hexadecimal) 1-6 Destination MAC Address FF FF FF FF FF FF 7-12 Source MAC Address 00 22 22 22 22 22 13-14 Type/Length Pseudo-random Data Pattern - VLAN Tag Header None 15-60 Data Pseudo-random Data Pattern 61-64 Frame Check Sequence Calculated at runtime Dest22 Octet(s) Description Value (all numbers are hexadecimal) 1-6 Destination MAC Address 00 22 22 22 22 22 7-12 Source MAC Address <TS Source MAC> 13-14 Type/Length Pseudo-random Data Pattern - VLAN Tag Header None 15 - (X-4) Data Pseudo-random Data Pattern (X-3) - X Frame Check Sequence Calculated at runtime ***X = Frame Size*** Src22_Tag2 Octet(s) Description Value (all numbers are hexadecimal) 1 6 Destination MAC Address FF FF FF FF FF FF 7 12 Source MAC Address 00 22 22 22 22 22 13 14 Type/Length 81 00 15 16 VLAN Tag Header 00 02 17 60 Data Pseudo-random Data Pattern 61 64 Frame Check Sequence Calculated at runtime Dest22_Tag2 Octet(s) Description Value (all numbers are hexadecimal) 1-6 Destination MAC Address 00 22 22 22 22 22 7-12 Source MAC Address <TS Source MAC> 13 14 Type/Length 81 00 15 16 VLAN Tag Header 00 02 15 - (X-4) Data Pseudo-random Data Pattern (X-3) - X Frame Check Sequence Calculated at runtime ***X = Frame Size*** All frames must contain a valid FCS. 22 Jumbo Frame Feature Verification Test Suite