Network Working Group                                      R. Mandeville
Request for Comments: 2889                                     CQOS Inc.
Category: Informational                                        J. Perser
                                                  Spirent Communications
                                                             August 2000
        
Network Working Group                                      R. Mandeville
Request for Comments: 2889                                     CQOS Inc.
Category: Informational                                        J. Perser
                                                  Spirent Communications
                                                             August 2000
        

Benchmarking Methodology for LAN Switching Devices

局域网交换设备的基准测试方法

Status of this Memo

本备忘录的状况

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2000). All Rights Reserved.

版权所有(C)互联网协会(2000年)。版权所有。

Table of Contents

目录

   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3. Test setup . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   4. Frame formats and sizes  . . . . . . . . . . . . . . . . . . .  3
   5. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . .  3
      5.1  Fully meshed throughput, frame loss and forwarding rates   4
      5.2  Partially meshed one-to-many/many-to-one  . . . . . . . .  7
      5.3  Partially meshed multiple devices . . . . . . . . . . . . 10
      5.4  Partially meshed unidirectional traffic . . . . . . . . . 13
      5.5  Congestion Control  . . . . . . . . . . . . . . . . . . . 16
      5.6  Forward Pressure and Maximum Forwarding Rate  . . . . . . 19
      5.7  Address caching capacity  . . . . . . . . . . . . . . . . 22
      5.8  Address learning rate . . . . . . . . . . . . . . . . . . 25
      5.9  Errored frames filtering. . . . . . . . . . . . . . . . . 27
      5.10 Broadcast frame Forwarding and Latency  . . . . . . . . . 28
   6. Security Considerations  . . . . . . . . . . . . . . . . . . . 30
   7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
   8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 30
      Appendix A: Formulas . . . . . . . . . . . . . . . . . . . . . 31
      Appendix B: Generating Offered Load  . . . . . . . . . . . . . 32
      Full Copyright Statement . . . . . . . . . . . . . . . . . . . 35
        
   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3. Test setup . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   4. Frame formats and sizes  . . . . . . . . . . . . . . . . . . .  3
   5. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . .  3
      5.1  Fully meshed throughput, frame loss and forwarding rates   4
      5.2  Partially meshed one-to-many/many-to-one  . . . . . . . .  7
      5.3  Partially meshed multiple devices . . . . . . . . . . . . 10
      5.4  Partially meshed unidirectional traffic . . . . . . . . . 13
      5.5  Congestion Control  . . . . . . . . . . . . . . . . . . . 16
      5.6  Forward Pressure and Maximum Forwarding Rate  . . . . . . 19
      5.7  Address caching capacity  . . . . . . . . . . . . . . . . 22
      5.8  Address learning rate . . . . . . . . . . . . . . . . . . 25
      5.9  Errored frames filtering. . . . . . . . . . . . . . . . . 27
      5.10 Broadcast frame Forwarding and Latency  . . . . . . . . . 28
   6. Security Considerations  . . . . . . . . . . . . . . . . . . . 30
   7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
   8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 30
      Appendix A: Formulas . . . . . . . . . . . . . . . . . . . . . 31
      Appendix B: Generating Offered Load  . . . . . . . . . . . . . 32
      Full Copyright Statement . . . . . . . . . . . . . . . . . . . 35
        
1. Introduction
1. 介绍

This document is intended to provide methodology for the benchmarking of local area network (LAN) switching devices. It extends the methodology already defined for benchmarking network interconnecting devices in RFC 2544 [3] to switching devices.

本文件旨在为局域网(LAN)交换设备的基准测试提供方法。它将RFC 2544[3]中已定义的网络互连设备基准测试方法扩展到交换设备。

This RFC primarily deals with devices which switch frames at the Medium Access Control (MAC) layer. It provides a methodology for benchmarking switching devices, forwarding performance, congestion control, latency, address handling and filtering. In addition to defining the tests, this document also describes specific formats for reporting the results of the tests.

此RFC主要处理在媒体访问控制(MAC)层交换帧的设备。它提供了一种对交换设备、转发性能、拥塞控制、延迟、地址处理和过滤进行基准测试的方法。除了定义测试外,本文件还描述了报告测试结果的具体格式。

A previous document, "Benchmarking Terminology for LAN Switching Devices" [2], defined many of the terms that are used in this document. The terminology document SHOULD be consulted before attempting to make use of this document.

先前的文档“LAN交换设备的基准术语”[2]定义了本文档中使用的许多术语。在尝试使用本文件之前,应查阅术语文件。

2. Requirements
2. 要求

The following RFCs SHOULD be consulted before attempting to make use of this document: RFC 1242 [1], RFC 2285 [2], and RFC 2544 [3].

在尝试使用本文件之前,应咨询以下RFC:RFC 1242[1]、RFC 2285[2]和RFC 2544[3]。

For the sake of clarity and continuity, this RFC adopts the template for benchmarking tests set out in Section 26 of RFC 2544.

为了清晰和连续性,本RFC采用RFC 2544第26节规定的基准测试模板。

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.

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119中的说明进行解释。

3. Test setup
3. 测试设置

This document extends the general test setup described in section 6 of RFC 2544 [3] to the benchmarking of LAN switching devices. RFC 2544 [3] primarily describes non-meshed traffic where input and output interfaces are grouped in mutually exclusive sending and receiving pairs. In fully meshed traffic, each interface of a DUT/SUT is set up to both receive and transmit frames to all the other interfaces under test.

本文件将RFC 2544[3]第6节中描述的一般测试设置扩展到LAN交换设备的基准测试。RFC 2544[3]主要描述非网状通信,其中输入和输出接口分组在互斥的发送和接收对中。在完全网状的业务中,DUT/SUT的每个接口都被设置为接收和发送帧到所有其他被测接口。

Prior to each test run, the DUT/SUT MUST learn the MAC addresses used in the test and the address learning SHOULD be verified. Addresses not learned will be forwarded as flooded frames and reduce the amount of correctly forwarded frames. The rate at which address learning frames are offered may have to be adjusted to be as low as 50 frames per second or even less, to guarantee successful learning. The DUT/SUT address aging time SHOULD be configured to be greater than

在每次测试运行之前,DUT/SUT必须学习测试中使用的MAC地址,并且应验证地址学习。未读入的地址将作为泛洪帧转发,并减少正确转发的帧数量。提供地址学习帧的速率可能必须调整为低至每秒50帧或更低,以确保成功学习。DUT/SUT地址老化时间应配置为大于

the period of the learning phase of the test plus the trial duration plus any configuration time required by the testing device. Addresses SHOULD NOT age out until the trial duration is completed. More than one learning trial may be needed for the association of the address to the port to occur.

测试学习阶段的时间加上试验持续时间加上测试设备所需的任何配置时间。在试用期结束之前,地址不应过期。要将地址与端口关联起来,可能需要进行多次学习试验。

If a DUT/SUT uses a hashing algorithm with address learning, the DUT/SUT may not learn the necessary addresses to perform the tests. The format of the MAC addresses MUST be adjustable so that the address mapping may be re-arranged to ensure that the DUT/SUT learns all the addresses.

如果DUT/SUT使用具有地址学习的哈希算法,则DUT/SUT可能无法学习执行测试所需的地址。MAC地址的格式必须是可调整的,以便可以重新安排地址映射,以确保DUT/SUT学习所有地址。

4. Frame formats and sizes
4. 帧格式和大小

The test frame format is defined in RFC 2544 section 8 [3] and MUST contain a unique signature field located in the UDP DATA area of the Test Frame (see Appendix C [3]). The purpose of the signature field is filter out frames that are not part of the offered load.

RFC 2544第8[3]节中定义了测试帧格式,并且必须包含位于测试帧UDP数据区域中的唯一签名字段(见附录C[3])。签名字段的用途是过滤掉不属于所提供负载的帧。

The signature field MUST be unique enough to identify the frames not originating from the DUT/SUT. The signature field SHOULD be located after byte 56 (collision window [4] ) or at the end of the frame. The length, contents and method of detection is not defined in this memo.

签名字段必须足够唯一,以识别非来自DUT/SUT的帧。签名字段应位于字节56(冲突窗口[4])之后或帧末尾。本备忘录未规定检测的长度、内容和方法。

The signature field MAY have a unique identifier per port. This would filter out misforwarded frames. It is possible for a DUT/SUT to strip off the MAC layer, send it through its switching matrix, and transmit it out with the correct destination MAC address but the wrong payload.

签名字段可以具有每个端口的唯一标识符。这将过滤掉方向错误的帧。DUT/SUT有可能剥离MAC层,通过其交换矩阵发送,并使用正确的目标MAC地址但错误的有效负载将其发送出去。

For frame sizes, refer to RFC 2544, section 9 [3].

有关机架尺寸,请参考RFC 2544第9节[3]。

There are three possible frame formats for layer 2 Ethernet switches: standard MAC Ethernet frames, standard MAC Ethernet frames with vendor-specific tags added to them, and IEEE 802.3ac frames tagged to accommodate 802.1p&Q. The two types of tagged frames may exceed the standard maximum length frame of 1518 bytes, and may not be accepted by the interface controllers of some DUT/SUTs. It is recommended to check the compatibility of the DUT/SUT with tagged frames before testing.

第2层以太网交换机有三种可能的帧格式:标准MAC以太网帧、添加了供应商特定标签的标准MAC以太网帧,以及为适应802.1p&Q而标记的IEEE 802.3ac帧。这两种类型的标记帧可能超过1518字节的标准最大长度帧,某些DUT/SUT的接口控制器可能不接受。建议在测试前检查DUT/SUT与标记框架的兼容性。

Devices switching tagged frames of over 1518 bytes will have a different maximum forwarding rate than untagged frames.

交换超过1518字节的标记帧的设备的最大转发速率将不同于未标记帧。

5. Benchmarking Tests
5. 基准测试

The following tests offer objectives, procedures, and reporting formats for benchmarking LAN switching devices.

以下测试提供了LAN交换设备基准测试的目标、程序和报告格式。

5.1 Fully meshed throughput, frame loss and forwarding rates
5.1 全网状吞吐量、帧丢失和转发速率
5.1.1 Objective
5.1.1 客观的

To determine the throughput, frame loss and forwarding rates of DUT/SUTs offered fully meshed traffic as defined in RFC 2285 [2].

确定DUT/SUT的吞吐量、帧丢失和转发速率,提供RFC 2285[2]中定义的全网状流量。

5.1.2 Setup Parameters
5.1.2 设置参数

When offering full meshed traffic, the following parameters MUST be defined. Each parameter is configured with the following considerations.

提供全网状流量时,必须定义以下参数。每个参数都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Interframe Gap (IFG) - The IFG between frames inside a burst MUST be at the minimum specified by the standard (9.6 us for 10Mbps Ethernet, 960 ns for 100Mbps Ethernet, and 96 ns for 1 Gbps Ethernet) of the medium being tested.

帧间间隙(IFG)-突发内帧之间的IFG必须为测试介质标准规定的最小值(10Mbps以太网为9.6 us,100Mbps以太网为960 ns,1Gbps以太网为96 ns)。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load, regardless of traffic orientation or duplex mode. Certain test configurations will theoretically over-subscribe the DUT/SUT.

ILoad—每个端口的预期负载以介质最大理论负载的百分比表示,而与流量方向或双工模式无关。某些测试配置在理论上会超过DUT/SUT。

In half duplex, an ILoad over 50% will over-subscribe the DUT/SUT.

在半双工中,超过50%的ILoad将过度订阅DUT/SUT。

Burst Size - The burst size defines the number of frames sent back-to-back at the minimum legal IFG [4] before pausing transmission to receive frames. Burst sizes SHOULD vary between 1 and 930 frames. A burst size of 1 will simulate constant load [1].

突发大小-突发大小定义在暂停传输以接收帧之前,以最小合法IFG[4]背靠背发送的帧数。突发大小应在1到930帧之间变化。突发大小为1将模拟恒定负载[1]。

Addresses per port - Represents the number of addresses which are being tested for each port. Number of addresses SHOULD be a binary exponential (i.e. 1, 2, 4, 8, 16, 32, 64, 128, 256, ...). Recommended value is 1.

每个端口的地址数-表示每个端口正在测试的地址数。地址数应为二进制指数(即1、2、4、8、16、32、64、128、256等)。建议值为1。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.1.3 Procedure
5.1.3 程序

All ports on the tester MUST transmit test frames either in a Frame Based or Time Based mode (Appendix B). All ports SHOULD start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames within 300 milliseconds of each other.

测试仪上的所有端口必须以基于帧或基于时间的模式传输测试帧(附录B)。所有端口应在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应在彼此之间300毫秒内开始传输帧。

Each port in the test MUST send test frames to all other ports in a round robin type fashion. The sequence of addresses MUST NOT change when congestion control is applied. The following table shows how each port in a test MUST transmit test frames to all other ports in the test. In this example, there are six ports with 1 address per port:

测试中的每个端口都必须以循环类型的方式向所有其他端口发送测试帧。应用拥塞控制时,地址序列不得更改。下表显示了测试中的每个端口必须如何将测试帧传输到测试中的所有其他端口。在此示例中,有六个端口,每个端口有一个地址:

Source Port Destination Ports (in order of transmission)

源端口目标端口(按传输顺序)

Port #1 2 3 4 5 6 2... Port #2 3 4 5 6 1 3... Port #3 4 5 6 1 2 4... Port #4 5 6 1 2 3 5... Port #5 6 1 2 3 4 6... Port #6 1 2 3 4 5 1...

端口#1 2 3 4 5 6 2。。。端口#2 3 4 5 6 1 3。。。端口#3 4 5 6 1 2 4。。。端口#4 5 6 1 2 3 5。。。端口#5 6 1 2 3 4 6。。。端口#6 1 2 3 4 5 1。。。

As shown in the table, there is an equal distribution of destination addresses for each transmit opportunity. This keeps the test balanced so that one destination port is not overloaded by the test algorithm and all ports are equally and fully loaded throughout the test. Not following this algorithm exactly will produce inconsistent results.

如表所示,每个传输机会的目标地址分布是相等的。这将保持测试的平衡,以便测试算法不会使一个目标端口过载,并且在整个测试过程中,所有端口的负载都是相等且完全的。不完全遵循此算法将产生不一致的结果。

For tests using multiple addresses per port, the actual port destinations are the same as described above and the actual source/destination address pairs SHOULD be chosen randomly to exercise the DUT/SUT's ability to perform address lookups.

对于每个端口使用多个地址的测试,实际端口目的地与上述相同,应随机选择实际源/目的地地址对,以锻炼DUT/SUT执行地址查找的能力。

For every address, learning frames MUST be sent to the DUT/SUT to allow the DUT/SUT update its address tables properly.

对于每个地址,必须向DUT/SUT发送学习帧,以允许DUT/SUT正确更新其地址表。

5.1.4 Measurements
5.1.4 测量

Each port should receive the same number of test frames that it transmitted. Each receiving port MUST categorize, then count the frames into one of two groups:

每个端口应接收与其传输的相同数量的测试帧。每个接收端口必须进行分类,然后将帧计数为两组中的一组:

1.) Received Frames: received frames MUST have the correct destination MAC address and SHOULD match a signature field.

1.)接收到的帧:接收到的帧必须具有正确的目标MAC地址,并且应与签名字段匹配。

2.) Flood count [2].

2.)洪水计数[2]。

Any frame originating from the DUT/SUT (spanning tree, SNMP, RIP, ...) MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT(生成树、SNMP、RIP等)的任何帧都不得算作接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

Frame loss rate of the DUT/SUT SHOULD be reported as defined in section 26.3 [3] with the following notes: Frame loss rate SHOULD be measured at the end of the trail duration. The term "rate", for this measurement only, does not imply the units in the fashion of "per second."

应按照第26.3节[3]的规定报告DUT/SUT的帧丢失率,并注意以下事项:应在试验持续时间结束时测量帧丢失率。术语“速率”仅用于此测量,并不意味着单位为“每秒”

5.1.4.1 Throughput
5.1.4.1 吞吐量

Throughput measurement is defined in section 26.1 [3]. A search algorithm is employed to find the maximum Oload [2] with a zero Frame loss rate [1]. The algorithm MUST adjust Iload to find the throughput.

第26.1[3]节定义了吞吐量测量。使用搜索算法来查找具有零帧丢失率[1]的最大Oload[2]。算法必须调整Iload以找到吞吐量。

5.1.4.2 Forwarding Rate
5.1.4.2 转发速率

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of test frames per second that the device is observed to successfully forward to the correct destination interface in response to a specified Oload. The Oload MUST also be cited.

DUT/SUT的转发速率(FR)应报告为每秒观察到设备响应指定Oload成功转发至正确目的地接口的测试帧数。还必须引用Oload。

Forwarding rate at maximum offered load (FRMOL) MUST be reported as the number of test frames per second that a device can successfully transmit to the correct destination interface in response to the MOL as defined in section 3.6 [2]. The MOL MUST also be cited.

最大提供负载下的转发速率(FRMOL)必须报告为设备能够响应第3.6节[2]中定义的MOL成功传输到正确的目标接口的每秒测试帧数。还必须引用MOL。

Maximum forwarding rate (MFR) MUST be reported as the highest forwarding rate of a DUT/SUT taken from an iterative set of forwarding rate measurements. The iterative set of forwarding rate measurements are made by adjusting Iload. The Oload applied to the device MUST also be cited.

最大转发速率(MFR)必须报告为从一组迭代转发速率测量值中获取的DUT/SUT的最高转发速率。通过调整Iload来进行转发速率测量的迭代集。还必须引用适用于设备的Oload。

5.1.5 Reporting format
5.1.5 报告格式

The results for these tests SHOULD be reported in the form of a graph. The x coordinate SHOULD be the frame size, the y coordinate SHOULD be the test results. There SHOULD be at least two lines on the graph, one plotting the theoretical and one plotting the test results.

这些试验的结果应以图表的形式报告。x坐标应为框架尺寸,y坐标应为测试结果。图表上至少应有两条线,一条绘制理论,另一条绘制试验结果。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.2 Partially meshed one-to-many/many-to-one
5.2 部分啮合的一对多/多对一
5.2.1 Objective
5.2.1 客观的

To determine the throughput when transmitting from/to multiple ports and to/from one port. As with the fully meshed throughput test, this test is a measure of the capability of the DUT to switch frames without frame loss. Results of this test can be used to determine the ability of the DUT to utilize an Ethernet port when switching traffic from multiple Ethernet ports.

确定从/到多个端口和从一个端口传输时的吞吐量。与全网格吞吐量测试一样,该测试是对DUT在无帧丢失的情况下切换帧的能力的测量。该测试的结果可用于确定DUT在从多个以太网端口交换流量时利用以太网端口的能力。

5.2.2 Setup Parameters
5.2.2 设置参数

When offering bursty meshed traffic, the following parameters MUST be defined. Each parameter is configured with the following considerations.

当提供突发网状流量时,必须定义以下参数。每个参数都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Traffic Direction - Traffic can be generated in one direction, the reverse direction, or both directions.

交通方向-可以在一个方向、反向或两个方向生成交通。

Interframe Gap (IFG) - The IFG between frames inside a burst MUST be at the minimum specified by the standard (9.6 us for 10Mbps Ethernet, 960 ns for 100Mbps Ethernet, and 96 ns for 1 Gbps Ethernet) of the medium being tested.

帧间间隙(IFG)-突发内帧之间的IFG必须为测试介质标准规定的最小值(10Mbps以太网为9.6 us,100Mbps以太网为960 ns,1Gbps以太网为96 ns)。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load, regardless of traffic orientation or duplex mode. Certain test configurations will theoretically over-subscribe the DUT/SUT.

ILoad—每个端口的预期负载以介质最大理论负载的百分比表示,而与流量方向或双工模式无关。某些测试配置在理论上会超过DUT/SUT。

In half duplex bidirectional traffic, an ILoad over 50% will over-subscribe the DUT/SUT.

在半双工双向通信中,超过50%的ILoad将过度订阅DUT/SUT。

Burst Size - The burst size defines the number of frames sent back-to-back at the minimum legal IFG [4] before pausing transmission to receive frames. Burst sizes SHOULD vary between 1 and 930 frames. A burst size of 1 will simulate constant load [1].

突发大小-突发大小定义在暂停传输以接收帧之前,以最小合法IFG[4]背靠背发送的帧数。突发大小应在1到930帧之间变化。突发大小为1将模拟恒定负载[1]。

Addresses per port - Represents the number of addresses which are being tested for each port. Number of addresses SHOULD be a binary exponential (i.e. 1, 2, 4, 8, 16, 32, 64, 128, 256, ...). Recommended value is 1.

每个端口的地址数-表示每个端口正在测试的地址数。地址数应为二进制指数(即1、2、4、8、16、32、64、128、256等)。建议值为1。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.2.3 Procedure
5.2.3 程序

All ports on the tester MUST transmit test frames either in a Frame Based or Time Based mode (Appendix B). Depending upon traffic direction, some or all of the ports will be transmitting. All ports SHOULD start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames within 300 milliseconds of each other.

测试仪上的所有端口必须以基于帧或基于时间的模式传输测试帧(附录B)。根据通信方向,部分或全部端口将进行传输。所有端口应在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应在彼此之间300毫秒内开始传输帧。

Test frames transmitted from the Many Ports MUST be destined to the One port. Test frames transmitted from the One Port MUST be destined to the Many ports in a round robin type fashion. See section 5.1.3 for a description of the round robin fashion.

从多个端口传输的测试帧必须发送到一个端口。从一个端口传输的测试帧必须以循环方式发送到多个端口。有关循环方式的说明,请参见第5.1.3节。

For tests using multiple addresses per port, the actual port destinations are the same as described above and the actual source/destination address pairs SHOULD be chosen randomly to exercise the DUT/SUT's ability to perform address lookups.

对于每个端口使用多个地址的测试,实际端口目的地与上述相同,应随机选择实际源/目的地地址对,以锻炼DUT/SUT执行地址查找的能力。

        +----------+
        |          |
        |   Many   | <--------
        |          |          \
        +----------+           \
                                \
        +----------+             \               +-------------+
        |          |              ------------>  |             |
        |   Many   |  <----------------------->  |     One     |
        |          |              ------------>  |             |
        +----------+             /               +-------------+
                                /
        +----------+           /
        |          |          /
        |   Many   |  <-------
        |          |
        +----------+
        
        +----------+
        |          |
        |   Many   | <--------
        |          |          \
        +----------+           \
                                \
        +----------+             \               +-------------+
        |          |              ------------>  |             |
        |   Many   |  <----------------------->  |     One     |
        |          |              ------------>  |             |
        +----------+             /               +-------------+
                                /
        +----------+           /
        |          |          /
        |   Many   |  <-------
        |          |
        +----------+
        

For every address, the testing device MUST send learning frames to allow the DUT/SUT to update its address tables properly.

对于每个地址,测试设备必须发送学习帧,以允许DUT/SUT正确更新其地址表。

5.2.4 Measurements
5.2.4 测量

Each receiving port MUST categorize, then count the frames into one of two groups:

每个接收端口必须进行分类,然后将帧计数为两组中的一组:

1.) Received Frames: received frames MUST have the correct destination MAC address and SHOULD match a signature field.

1.)接收到的帧:接收到的帧必须具有正确的目标MAC地址,并且应与签名字段匹配。

2.) Flood count [2].

2.)洪水计数[2]。

Any frame originating from the DUT/SUT MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT的任何帧不得被视为接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of test frames per second that the device is observed to successfully transmit to the correct destination interface in response to a specified Oload. The Oload MUST also be cited.

DUT/SUT的转发速率(FR)应报告为每秒观察到设备响应于指定的Oload成功传输到正确的目的地接口的测试帧数。还必须引用Oload。

Forwarding rate at maximum offered load (FRMOL) MUST be reported as the number of test frames per second that a device can successfully transmit to the correct destination interface in response to the MOL as defined in section 3.6 [2]. The MOL MUST also be cited.

最大提供负载下的转发速率(FRMOL)必须报告为设备能够响应第3.6节[2]中定义的MOL成功传输到正确的目标接口的每秒测试帧数。还必须引用MOL。

Maximum forwarding rate (MFR) MUST be reported as the highest forwarding rate of a DUT/SUT taken from an iterative set of forwarding rate measurements. The iterative set of forwarding rate measurements are made by adjusting Iload. The Oload applied to the device MUST also be cited.

最大转发速率(MFR)必须报告为从一组迭代转发速率测量值中获取的DUT/SUT的最高转发速率。通过调整Iload来进行转发速率测量的迭代集。还必须引用适用于设备的Oload。

5.2.5 Reporting Format
5.2.5 报告格式

The results for these tests SHOULD be reported in the form of a graph. The x coordinate SHOULD be the frame size, the y coordinate SHOULD be the test results. There SHOULD be at least two lines on the graph, one plotting the theoretical and one plotting the test results.

这些试验的结果应以图表的形式报告。x坐标应为框架尺寸,y坐标应为测试结果。图表上至少应有两条线,一条绘制理论,另一条绘制试验结果。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.3 Partially meshed multiple devices
5.3 部分啮合多器件
5.3.1 Objective
5.3.1 客观的

To determine the throughput, frame loss and forwarding rates of two switching devices equipped with multiple ports and one high speed backbone uplink (Gigabit Ethernet, ATM, SONET).

确定配备有多个端口和一个高速主干上行链路(千兆以太网、ATM、SONET)的两个交换设备的吞吐量、帧丢失和转发速率。

5.3.2 Setup Parameters
5.3.2 设置参数

When offering bursty partially meshed traffic, the following parameters MUST be defined. Each variable is configured with the following considerations.

当提供突发的部分网格化流量时,必须定义以下参数。每个变量都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Interframe Gap (IFG) - The IFG between frames inside a burst MUST be at the minimum specified by the standard (9.6 us for 10Mbps Ethernet, 960 ns for 100Mbps Ethernet, and 96 ns for 1 Gbps Ethernet) of the medium being tested.

帧间间隙(IFG)-突发内帧之间的IFG必须为测试介质标准规定的最小值(10Mbps以太网为9.6 us,100Mbps以太网为960 ns,1Gbps以太网为96 ns)。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load, regardless of traffic orientation or duplex mode. Certain test configurations will theoretically over-subscribe the DUT/SUT.

ILoad—每个端口的预期负载以介质最大理论负载的百分比表示,而与流量方向或双工模式无关。某些测试配置在理论上会超过DUT/SUT。

In half duplex, an ILoad over 50% will over-subscribe the DUT/SUT.

在半双工中,超过50%的ILoad将过度订阅DUT/SUT。

Burst Size - The burst size defines the number of frames sent back-to-back at the minimum legal IFG [4] before pausing transmission to receive frames. Burst sizes SHOULD vary between 1 and 930 frames. A burst size of 1 will simulate constant load [1].

突发大小-突发大小定义在暂停传输以接收帧之前,以最小合法IFG[4]背靠背发送的帧数。突发大小应在1到930帧之间变化。突发大小为1将模拟恒定负载[1]。

Addresses per port - Represents the number of addresses which are being tested for each port. Number of addresses SHOULD be a binary exponential (i.e. 1, 2, 4, 8, 16, 32, 64, 128, 256, ...). Recommended value is 1.

每个端口的地址数-表示每个端口正在测试的地址数。地址数应为二进制指数(即1、2、4、8、16、32、64、128、256等)。建议值为1。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

Local Traffic - A Boolean value of ON or OFF. The frame sequence algorithm MAY be altered to remove local traffic. With local traffic ON, the algorithm is exactly the same as a fully meshed throughput. With local traffic OFF, the port sends frames to all other ports on the other side of the backbone uplink in a round robin type fashion.

本地通信量-布尔值ON或OFF。可以改变帧序列算法以移除本地通信量。在启用本地流量的情况下,该算法与完全网格化吞吐量完全相同。在本地通信量关闭的情况下,端口以循环式方式将帧发送到主干上行链路另一侧的所有其他端口。

5.3.3 Procedure
5.3.3 程序

All ports on the tester MUST transmit test frames either in a Frame Based or Time Based mode (Appendix B). All ports SHOULD start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames with 300 milliseconds of each other.

测试仪上的所有端口必须以基于帧或基于时间的模式传输测试帧(附录B)。所有端口应在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应已开始传输彼此间隔300毫秒的帧。

Each port in the test MUST send test frames to all other ports in a round robin type fashion as defined in section 5.1.3. Local traffic MAY be removed from the round robin list in order to send the entire load across the backbone uplink.

测试中的每个端口必须以第5.1.3节中定义的循环方式向所有其他端口发送测试帧。本地业务可以从循环列表中删除,以便通过主干上行链路发送整个负载。

For tests using multiple addresses per port, the actual port destinations are the same as described above and the actual source/destination address pairs SHOULD be chosen randomly to exercise the DUT/SUT's ability to perform address lookups.

对于每个端口使用多个地址的测试,实际端口目的地与上述相同,应随机选择实际源/目的地地址对,以锻炼DUT/SUT执行地址查找的能力。

For every address, the testing device MUST send learning frames to allow the DUT/SUT to update its address tables properly.

对于每个地址,测试设备必须发送学习帧,以允许DUT/SUT正确更新其地址表。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.3.4 Measurements
5.3.4 测量

Each receiving port MUST categorize, then count the frames into one of two groups:

每个接收端口必须进行分类,然后将帧计数为两组中的一组:

1.) Received frames MUST have the correct destination MAC address and SHOULD match a signature field.

1.)收到的帧必须具有正确的目标MAC地址,并且应与签名字段匹配。

2.) Flood count [2].

2.)洪水计数[2]。

Any frame originating from the DUT/SUT MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT的任何帧不得被视为接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

Frame loss rate of the DUT/SUT SHOULD be reported as defined in section 26.3 [3] with the following notes: Frame loss rate SHOULD be measured at the end of the trial duration. The term "rate", for this measurement only, does not imply the units in the fashion of "per second."

应按照第26.3节[3]的规定报告DUT/SUT的帧丢失率,并注意以下事项:应在试验期间结束时测量帧丢失率。术语“速率”仅用于此测量,并不意味着单位为“每秒”

5.3.4.1 Throughput
5.3.4.1 吞吐量

Throughput measurement is defined in section 26.1 [3]. A search algorithm is employed to find the maximum Oload [2] with a zero Frame loss rate [1]. The algorithm MUST adjust Iload to find the throughput.

第26.1[3]节定义了吞吐量测量。使用搜索算法来查找具有零帧丢失率[1]的最大Oload[2]。算法必须调整Iload以找到吞吐量。

5.3.4.2 Forwarding rate
5.3.4.2 转发速率

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of test frames per second that the device is observed to successfully forward to the correct destination interface in response to a specified Oload. The Oload MUST also be cited.

DUT/SUT的转发速率(FR)应报告为每秒观察到设备响应指定Oload成功转发至正确目的地接口的测试帧数。还必须引用Oload。

Forwarding rate at maximum offered load (FRMOL) MUST be reported as the number of test frames per second that a device can successfully transmit to the correct destination interface in response to the MOL as defined in section 3.6 [2]. The MOL MUST also be cited.

最大提供负载下的转发速率(FRMOL)必须报告为设备能够响应第3.6节[2]中定义的MOL成功传输到正确的目标接口的每秒测试帧数。还必须引用MOL。

Maximum forwarding rate (MFR) MUST be reported as the highest forwarding rate of a DUT/SUT taken from an iterative set of forwarding rate measurements. The iterative set of forwarding rate measurements are made by adjusting Iload. The Oload applied to the device MUST also be cited.

最大转发速率(MFR)必须报告为从一组迭代转发速率测量值中获取的DUT/SUT的最高转发速率。通过调整Iload来进行转发速率测量的迭代集。还必须引用适用于设备的Oload。

5.3.5 Reporting format
5.3.5 报告格式

The results for these tests SHOULD be reported in the form of a graph. The x coordinate SHOULD be the frame size, the y coordinate SHOULD be the test results. There SHOULD be at least two lines on the graph, one plotting the theoretical and one plotting the test results.

这些试验的结果应以图表的形式报告。x坐标应为框架尺寸,y坐标应为测试结果。图表上至少应有两条线,一条绘制理论,另一条绘制试验结果。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.4 Partially meshed unidirectional traffic
5.4 部分网状单向业务
5.4.1 Objective
5.4.1 客观的

To determine the throughput of the DUT/SUT when presented multiple streams of unidirectional traffic with half of the ports on the DUT/SUT are transmitting frames destined to the other half of the ports.

确定DUT/SUT的吞吐量,当呈现多个单向流量流时,DUT/SUT上的一半端口正在发送发送到另一半端口的帧。

5.4.2 Setup Parameters
5.4.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Interframe Gap (IFG) - The IFG between frames inside a burst MUST be at the minimum specified by the standard (9.6 us for 10Mbps Ethernet, 960 ns for 100Mbps Ethernet, and 96 ns for 1 Gbps Ethernet) of the medium being tested.

帧间间隙(IFG)-突发内帧之间的IFG必须为测试介质标准规定的最小值(10Mbps以太网为9.6 us,100Mbps以太网为960 ns,1Gbps以太网为96 ns)。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load, regardless of traffic orientation or duplex mode. Certain test configurations will theoretically over-subscribe the DUT/SUT.

ILoad—每个端口的预期负载以介质最大理论负载的百分比表示,而与流量方向或双工模式无关。某些测试配置在理论上会超过DUT/SUT。

ILoad will not over-subscribe the DUT/SUT in this test.

在本测试中,ILoad不会过度订阅DUT/SUT。

Burst Size - The burst size defines the number of frames sent back-to-back at the minimum legal IFG [4] before pausing transmission to receive frames. Burst sizes SHOULD vary between 1 and 930 frames. A burst size of 1 will simulate constant load [1].

突发大小-突发大小定义在暂停传输以接收帧之前,以最小合法IFG[4]背靠背发送的帧数。突发大小应在1到930帧之间变化。突发大小为1将模拟恒定负载[1]。

Addresses per port - Represents the number of addresses which are being tested for each port. Number of addresses SHOULD be a binary exponential (i.e. 1, 2, 4, 8, 16, 32, 64, 128, 256, ...). Recommended value is 1.

每个端口的地址数-表示每个端口正在测试的地址数。地址数应为二进制指数(即1、2、4、8、16、32、64、128、256等)。建议值为1。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.4.3 Procedure
5.4.3 程序

Ports do not send and receive test frames simultaneously. As a consequence, there should be no collisions unless the DUT is misforwarding frames, generating flooded or Spanning-Tree frames or is enabling some flow control mechanism. Ports used for this test are either transmitting or receiving, but not both. Those ports which are transmitting send test frames destined to addresses corresponding to each of the ports receiving. This creates a unidirectional mesh of traffic.

端口不同时发送和接收测试帧。因此,除非DUT错误前进帧,生成泛洪或生成树帧,或启用某些流量控制机制,否则不应发生碰撞。用于此测试的端口可以是发送端口,也可以是接收端口,但不能同时是发送端口和接收端口。发送测试帧的那些端口发送到与每个接收端口对应的地址。这将创建一个单向的流量网格。

All ports on the tester MUST transmit test frames either in a Frame Based or Time Based mode (Appendix B). All ports SHOULD start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames with 300 milliseconds of each other.

测试仪上的所有端口必须以基于帧或基于时间的模式传输测试帧(附录B)。所有端口应在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应已开始传输彼此间隔300毫秒的帧。

Each transmitting port in the test MUST send frames to all receiving ports in a round robin type fashion. The sequence of addresses MUST NOT change when congestion control is applied. The following table shows how each port in a test MUST transmit test frames to all other ports in the test. In this 8 port example, port 1 through 4 are transmitting and ports 5 through 8 are receiving; each with 1 address per port:

测试中的每个发送端口必须以循环方式向所有接收端口发送帧。应用拥塞控制时,地址序列不得更改。下表显示了测试中的每个端口必须如何将测试帧传输到测试中的所有其他端口。在这个8端口示例中,端口1到4正在发送,端口5到8正在接收;每个端口都有一个地址:

Source Port, then Destination Ports (in order of transmission)

源端口,然后是目标端口(按传输顺序)

Port #1 5 6 7 8 5 6... Port #2 6 7 8 5 6 7... Port #3 7 8 5 6 7 8... Port #4 8 5 6 7 8 5...

端口#1 5 6 7 8 5 6。。。端口#2 6 7 8 5 6 7。。。端口#3 7 8 5 6 7 8。。。端口#4 8 5 6 7 8 5。。。

As shown in the table, there is an equal distribution of destination addresses for each transmit opportunity. This keeps the test balanced so that one destination port is not overloaded by the test algorithm and all receiving ports are equally and fully loaded throughout the test. Not following this algorithm exactly will product inconsistent results.

如表所示,每个传输机会的目标地址分布是相等的。这将保持测试的平衡,以便测试算法不会使一个目标端口过载,并且在整个测试过程中,所有接收端口的负载都是相等且完全的。不完全遵循此算法将产生不一致的结果。

For tests using multiple addresses per port, the actual port destinations are the same as described above and the actual source/destination address pairs SHOULD be chosen randomly to exercise the DUT/SUT's ability to perform address lookups.

对于每个端口使用多个地址的测试,实际端口目的地与上述相同,应随机选择实际源/目的地地址对,以锻炼DUT/SUT执行地址查找的能力。

For every address, the testing device MUST send learning frames to allow the DUT/SUT to load its address tables properly. The address table's aging time SHOULD be set sufficiently longer than

对于每个地址,测试设备必须发送学习帧,以允许DUT/SUT正确加载其地址表。地址表的老化时间应设置为比

the learning time and trial duration time combined. If the address table ages out during the test, the results will show a lower performing DUT/SUT.

学习时间和试验持续时间相结合。如果地址表在测试期间老化,结果将显示性能较低的DUT/SUT。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.4.4 Measurements
5.4.4 测量

Each receiving port MUST categorize, then count the frames into one of two groups:

每个接收端口必须进行分类,然后将帧计数为两组中的一组:

1.) Received Frames: received frames MUST have the correct destination MAC address and SHOULD match a signature field.

1.)接收到的帧:接收到的帧必须具有正确的目标MAC地址,并且应与签名字段匹配。

2.) Flood count [2].

2.)洪水计数[2]。

Any frame originating from the DUT/SUT MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT的任何帧不得被视为接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

Frame loss rate of the DUT/SUT SHOULD be reported as defined in section 26.3 [3] with the following notes: Frame loss rate SHOULD be measured at the end of the trial duration. The term "rate", for this measurement only, does not imply the units in the fashion of "per second."

应按照第26.3节[3]的规定报告DUT/SUT的帧丢失率,并注意以下事项:应在试验期间结束时测量帧丢失率。术语“速率”仅用于此测量,并不意味着单位为“每秒”

5.4.4.1 Throughput
5.4.4.1 吞吐量

Throughput measurement is defined in section 26.1 [3]. A search algorithm is employed to find the maximum Oload [2] with a zero Frame loss rate [1]. The algorithm MUST adjust Iload to find the throughput.

第26.1[3]节定义了吞吐量测量。使用搜索算法来查找具有零帧丢失率[1]的最大Oload[2]。算法必须调整Iload以找到吞吐量。

5.4.4.2 Forwarding rate
5.4.4.2 转发速率

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of test frames per second that the device is observed to successfully forward to the correct destination interface in response to a specified Oload. The Oload MUST also be cited.

DUT/SUT的转发速率(FR)应报告为每秒观察到设备响应指定Oload成功转发至正确目的地接口的测试帧数。还必须引用Oload。

Forwarding rate at maximum offered load (FRMOL) MUST be reported as the number of test frames per second that a device can successfully transmit to the correct destination interface in response to the MOL as defined in section 3.6 [2]. The MOL MUST also be cited.

最大提供负载下的转发速率(FRMOL)必须报告为设备能够响应第3.6节[2]中定义的MOL成功传输到正确的目标接口的每秒测试帧数。还必须引用MOL。

Maximum forwarding rate (MFR) MUST be reported as the highest forwarding rate of a DUT/SUT taken from an iterative set of forwarding rate measurements. The iterative set of forwarding rate measurements are made by adjusting Iload. The Oload applied to the device MUST also be cited.

最大转发速率(MFR)必须报告为从一组迭代转发速率测量值中获取的DUT/SUT的最高转发速率。通过调整Iload来进行转发速率测量的迭代集。还必须引用适用于设备的Oload。

5.4.5 Reporting format
5.4.5 报告格式

The results for these tests SHOULD be reported in the form of a graph. The x coordinate SHOULD be the frame size, the y coordinate SHOULD be the test results. There SHOULD be at least two lines on the graph, one plotting the theoretical and one plotting the test results.

这些试验的结果应以图表的形式报告。x坐标应为框架尺寸,y坐标应为测试结果。图表上至少应有两条线,一条绘制理论,另一条绘制试验结果。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

5.5 Congestion Control
5.5 拥塞控制
5.5.1 Objective
5.5.1 客观的

To determine how a DUT handles congestion. Does the device implement congestion control and does congestion on one port affect an uncongested port. This procedure determines if Head of Line Blocking and/or Backpressure are present.

确定DUT如何处理拥塞。设备是否实施拥塞控制,一个端口上的拥塞是否影响未阻塞的端口。本程序确定是否存在管路堵塞和/或背压。

5.5.2 Setup Parameters
5.5.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Interframe Gap (IFG) - The IFG between frames inside a burst MUST be at the minimum specified by the standard (9.6 us for 10Mbps Ethernet, 960 ns for 100Mbps Ethernet, and 96 ns for 1 Gbps Ethernet) of the medium being tested.

帧间间隙(IFG)-突发内帧之间的IFG必须为测试介质标准规定的最小值(10Mbps以太网为9.6 us,100Mbps以太网为960 ns,1Gbps以太网为96 ns)。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

Addresses per port - Represents the number of addresses which are being tested for each port. Number of addresses SHOULD be a binary exponential (i.e. 1, 2, 4, 8, 16, 32, 64, 128, 256, ...). Recommended value is 1.

每个端口的地址数-表示每个端口正在测试的地址数。地址数应为二进制指数(即1、2、4、8、16、32、64、128、256等)。建议值为1。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.5.3 Procedure
5.5.3 程序

This test MUST consist of a multiple of four ports with the same MOL. Four ports are REQUIRED and MAY be expanded to fully utilize the DUT/SUT in increments of four. Each group of four will contain a test block with two of the ports as source transmitters and two of the ports as receivers. The diagram below depicts the flow of traffic between the switch ports:

该测试必须由具有相同MOL的四个端口的倍数组成。需要四个端口,并且可以扩展为以四个为增量充分利用DUT/SUT。每组四个将包含一个测试块,其中两个端口作为源发射机,两个端口作为接收机。下图描述了交换机端口之间的流量:

        +----------+   50 % MOL                  +-------------+
        |          |  ------------------------>  |             |
        |          |   50 % MOL                  | uncongested |
        |          |  ---------                  |             |
        +----------+            \                +-------------+
                                 \
                                  \
                                   \
        +----------+                \            +-------------+
        |          |                 --------->  |             |
        |          |   100 % MOL                 | congested   |
        |          |  ------------------------>  |             |
        +----------+                             +-------------+
        
        +----------+   50 % MOL                  +-------------+
        |          |  ------------------------>  |             |
        |          |   50 % MOL                  | uncongested |
        |          |  ---------                  |             |
        +----------+            \                +-------------+
                                 \
                                  \
                                   \
        +----------+                \            +-------------+
        |          |                 --------->  |             |
        |          |   100 % MOL                 | congested   |
        |          |  ------------------------>  |             |
        +----------+                             +-------------+
        

Both source transmitters MUST transmit the exact number of test frames. The first source MUST transmit test frames at the MOL with the destination address of the two receive ports in an alternating order. The first test frame to the uncongested receive port, second test frame to the congested receive port, then repeat. The second source transmitter MUST transmit test frames at the MOL only to the congested receive port.

两个源发射机必须传输准确数量的测试帧。第一个源必须在MOL上传输测试帧,并以交替顺序使用两个接收端口的目标地址。第一个测试帧发送到未阻塞的接收端口,第二个测试帧发送到阻塞的接收端口,然后重复。第二个源发送器必须仅在MOL处将测试帧发送到拥挤的接收端口。

Both receive ports SHOULD distinguish between test frames originating from the source ports and frames originating from the DUT/SUT. Only test frames from the source ports SHOULD be counted.

两个接收端口应区分来自源端口的测试帧和来自DUT/SUT的帧。应仅统计来自源端口的测试帧。

The uncongested receive port should be receiving at a rate of half the MOL. The number of test frames received on the uncongested port SHOULD be 50% of the test frames transmitted by the first source transmitter. The congested receive port should be receiving at the MOL. The number of test frames received on the congested port should be between 100% and 150% of the test frames transmitted by one source transmitter.

未压缩接收端口的接收速率应为MOL的一半。在未压缩端口上接收的测试帧数量应为第一个源发射机发送的测试帧的50%。拥塞接收端口应在MOL处接收。拥塞端口上接收的测试帧数量应在一个源发射机发送的测试帧的100%到150%之间。

Test frames destined to uncongested ports in a switch device should not be dropped due to other ports being congested, even if the source is sending to both the congested and uncongested ports.

即使源发送到拥塞和未拥塞的端口,也不应由于其他端口拥塞而丢弃发送到交换机设备中未拥塞端口的测试帧。

5.5.4 Measurements
5.5.4 测量

Any frame received which does not have the correct destination address MUST not be counted as a received frame and SHOULD be counted as part of a flood count.

任何接收到的没有正确目标地址的帧都不能算作接收帧,而应算作洪水计数的一部分。

Any frame originating from the DUT/SUT MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT的任何帧不得被视为接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

Frame loss rate of the DUT/SUT's congested and uncongested ports MUST be reported as defined in section 26.3 [3] with the following notes: Frame loss rate SHOULD be measured at the end of the trial duration. The term "rate", for this measurement only, does not imply the units in the fashion of "per second."

必须按照第26.3节[3]的规定报告DUT/SUT拥塞和未拥塞端口的帧丢失率,并注意以下事项:应在试验期间结束时测量帧丢失率。术语“速率”仅用于此测量,并不意味着单位为“每秒”

Offered Load to the DUT/SUT MUST be reported as the number of test frames per second that the DUT/SUT observed to accept. This may be different that the MOL.

提供给DUT/SUT的负载必须报告为DUT/SUT观察到的每秒可接受的测试帧数。这可能不同于摩尔。

Forwarding rate (FR) of the DUT/SUT's congested and uncongested ports MUST be reported as the number of test frames per second that the device is observed to successfully transmit to the correct destination interface in response to a specified offered load. The offered load MUST also be cited.

DUT/SUT拥塞和未拥塞端口的转发速率(FR)必须报告为每秒测试帧数,观察到设备响应指定的提供负载成功传输到正确的目的地接口。还必须引用提供的荷载。

5.5.5 Reporting format
5.5.5 报告格式

This test MUST report the frame lost rate at the uncongested port, the forwarding rate (at 50% offered load) at the uncongested port, and the frame lost rate at the congested port. This test MAY report the frame counts transmitted and frame counts received by the DUT/SUT.

此测试必须报告未占用端口的帧丢失率、未占用端口的转发率(在50%提供负载下)以及拥塞端口的帧丢失率。该测试可报告DUT/SUT发送的帧计数和接收的帧计数。

5.5.5.1 HOLB
5.5.5.1 霍尔布

If there is frame loss at the uncongested port, "Head of Line" blocking is present. The DUT cannot forward the amount of traffic to the congested port and as a result it is also losing frames destined to the uncongested port.

如果在未阻塞的端口有帧丢失,则存在“线头”阻塞。DUT无法将通信量转发到拥塞的端口,因此也会丢失发送到未拥塞端口的帧。

5.5.5.2 Back Pressure
5.5.5.2 背压

If there is no frame loss on the congested port, then backpressure is present. It should be noted that this test expects the overall load to the congested port to be greater than 100%. Therefore if the load is greater than 100% and no frame loss is detected, then the DUT must be implementing a flow control mechanism. The type of flow control mechanism used is beyond the scope of this memo.

如果拥塞端口上没有帧丢失,则存在背压。应注意的是,该测试预计拥塞端口的总负载大于100%。因此,如果负载大于100%,且未检测到帧丢失,则DUT必须实施流量控制机制。所使用的流量控制机制类型超出了本备忘录的范围。

It should be noted that some DUTs may not be able to handle the 100% load presented at the input port. In this case, there may be frame loss reported at the uncongested port which is due to the load at the input port rather than the congested port's load.

应注意的是,一些DUT可能无法处理输入端口处的100%负载。在这种情况下,由于输入端口的负载而不是拥塞端口的负载,可能会在未阻塞端口报告帧丢失。

If the uncongested frame loss is reported as zero, but the maximum forwarding rate is less than 7440 (for 10Mbps Ethernet), then this may be an indication of congestion control being enforced by the DUT. In this case, the congestion control is affecting the throughput of the uncongested port.

如果未压缩的帧丢失报告为零,但最大转发速率小于7440(对于10Mbps以太网),则这可能表示DUT正在实施拥塞控制。在这种情况下,拥塞控制会影响未阻塞端口的吞吐量。

If no congestion control is detected, the expected percentage frame loss for the congested port is 33% at 150% overload. It is receiving 100% load from 1 port, and 50% from another, and can only get 100% possible throughput, therefore having a frame loss rate of 33% (150%-50%/150%).

如果未检测到拥塞控制,则在150%过载时,拥塞端口的预期帧丢失百分比为33%。它从一个端口接收100%的负载,从另一个端口接收50%的负载,并且只能获得100%的可能吞吐量,因此具有33%的帧丢失率(150%-50%/150%)。

5.6 Forward Pressure and Maximum Forwarding Rate
5.6 前进压力和最大前进速率
5.6.1 Objective
5.6.1 客观的

The Forward Pressure test overloads a DUT/SUT port and measures the output for forward pressure [2]. If the DUT/SUT transmits frames with an interframe gap less than 96 bits (section 4.2.3.2.2 [4]), then forward pressure is detected.

正向压力测试使DUT/SUT端口过载,并测量正向压力的输出[2]。如果DUT/SUT传输帧间间隙小于96位的帧(第4.2.3.2.2[4]节),则检测到正向压力。

The objective of the Maximum Forwarding Rate test is to measure the peak value of the Forwarding Rate when the Offered Load is varied between the throughput [1] and the Maximum Offered Load [2].

最大转发速率测试的目的是测量提供负载在吞吐量[1]和最大提供负载[2]之间变化时的转发速率峰值。

5.6.2 Setup Parameters
5.6.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

Step Size - The minimum incremental resolution that the Iload will be incremented in frames per second. The smaller the step size, the more accurate the measurement and the more iterations required. As the Iload approaches the MOL, the minimum step size will increase because of gap resolution on the testing device.

步长-Iload将以每秒帧数递增的最小增量分辨率。步长越小,测量越精确,需要的迭代次数越多。当Iload接近MOL时,由于测试设备上的间隙分辨率,最小步长将增加。

5.6.3 Procedure
5.6.3 程序
5.6.3.1 Maximum forwarding rate
5.6.3.1 最大转发速率

If the Throughput [1] and the MOL [2] are the same, then MFR [2] is equal to the MOL [2].

如果吞吐量[1]和摩尔[2]相同,则MFR[2]等于摩尔[2]。

This test MUST at a minimum be performed in a two-port configuration as described below. Learning frames MUST be sent to allow the DUT/SUT to update its address tables properly.

该测试至少必须在如下所述的双端口配置中执行。必须发送学习帧,以允许DUT/SUT正确更新其地址表。

Test frames are transmitted to the first port (port 1) of the DUT/SUT at the Iload. The FR [2] on the second port (port 2) of the DUT/SUT is measured. The Iload is incremented for each Step Size to find the MFR. The algorithm for the test is as follows:

测试帧被传输到Iload处DUT/SUT的第一个端口(端口1)。测量DUT/SUT第二个端口(端口2)上的FR[2]。对于每个步长,Iload都会递增以查找MFR。测试的算法如下所示:

    CONSTANT
      MOL = ... frames/sec; {Maximum Offered Load}
    VARIABLE
      MFR   := 0 frames/sec; {Maximum Forwarding Rate}
      ILOAD := starting throughput in frames/sec; {offered load}
      STEP  := ... frames/sec; {Step Size}
    BEGIN
      ILOAD := ILOAD - STEP;
      DO
      BEGIN
        ILOAD := ILOAD + STEP
        IF (ILOAD > MOL) THEN
        BEGIN
          ILOAD := MOL
        END
        AddressLearning; {Port 2 broadcasts with its source address}
        Transmit(ILOAD); {Port 1 sends frames to Port 2 at Offered load}
        IF (Port 2 Forwarding Rate > MFR) THEN
        BEGIN
           MFR := Port 2 Forwarding Rate; {A higher value than before}
        END
        
    CONSTANT
      MOL = ... frames/sec; {Maximum Offered Load}
    VARIABLE
      MFR   := 0 frames/sec; {Maximum Forwarding Rate}
      ILOAD := starting throughput in frames/sec; {offered load}
      STEP  := ... frames/sec; {Step Size}
    BEGIN
      ILOAD := ILOAD - STEP;
      DO
      BEGIN
        ILOAD := ILOAD + STEP
        IF (ILOAD > MOL) THEN
        BEGIN
          ILOAD := MOL
        END
        AddressLearning; {Port 2 broadcasts with its source address}
        Transmit(ILOAD); {Port 1 sends frames to Port 2 at Offered load}
        IF (Port 2 Forwarding Rate > MFR) THEN
        BEGIN
           MFR := Port 2 Forwarding Rate; {A higher value than before}
        END
        

END WHILE (ILOAD < MOL); {ILOAD has reached the MOL value} DONE

结束时(ILOAD<MOL);{ILOAD已达到MOL值}完成

5.6.3.2 Minimum Interframe Gap
5.6.3.2 最小帧间间隙

The Minimum Interframe gap test SHOULD, at a minimum, be performed in a two-port configuration as described below. Learning frames MUST be sent to allow the DUT/SUT to update its address tables properly.

最小帧间间隙测试至少应在如下所述的双端口配置中执行。必须发送学习帧,以允许DUT/SUT正确更新其地址表。

Test frames SHOULD be transmitted to the first port (port 1) of the DUT/SUT with an interframe gap of 88 bits. This will apply forward pressure to the DUT/SUT and overload it at a rate of one byte per frame. The test frames MUST be constructed with a source address of port 1 and a destination address of port 2.

测试帧应以88位帧间间隙传输至DUT/SUT的第一个端口(端口1)。这将向DUT/SUT施加正向压力,并以每帧一字节的速率使其过载。测试帧必须由端口1的源地址和端口2的目标地址构成。

The FR on the second port (port 2) of the DUT/SUT is measured. The measured Forwarding Rate should not exceed the medium's maximum theoretical utilization (MOL).

测量DUT/SUT第二个端口(端口2)上的FR。测量的转发速率不应超过介质的最大理论利用率(MOL)。

5.6.4 Measurements
5.6.4 测量

Port 2 MUST categorize, then count the frames into one of two groups:

端口2必须分类,然后将帧计数为两个组之一:

1.) Received Frames: received frames MUST have the correct destination MAC address and SHOULD match a signature field.

1.)接收到的帧:接收到的帧必须具有正确的目标MAC地址,并且应与签名字段匹配。

2.) Flood count [2].

2.)洪水计数[2]。

Any frame originating from the DUT/SUT MUST not be counted as a received frame. Frames originating from the DUT/SUT MAY be counted as flooded frames or not counted at all.

来自DUT/SUT的任何帧不得被视为接收帧。来自DUT/SUT的帧可被计为泛洪帧或根本不被计。

5.6.5 Reporting format
5.6.5 报告格式

MFR MUST be reported as the highest forwarding rate of a DUT/SUT taken from an iterative set of forwarding rate measurements. The Iload applied to the device MUST also be cited.

MFR必须报告为DUT/SUT的最高转发速率,该转发速率取自一组迭代转发速率测量值。还必须引用应用于设备的Iload。

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of frames per second that the device is observed to successfully transmit to the correct destination interface in response to a specified Oload. The Iload MUST be cited and the Oload MAY be recorded.

DUT/SUT的转发速率(FR)应报告为每秒观察到的设备响应于指定的Oload成功发送到正确的目的地接口的帧数。必须引用Iload,并且可以记录Oload。

If the FR exceeds the MOL during the Minimum Interframe gap test, this MUST be highlighted with the expression "Forward Pressure detected".

如果在最小帧间间隙试验期间FR超过MOL,则必须用“检测到的前向压力”的表达式突出显示。

5.7 Address Caching Capacity
5.7 地址缓存容量
5.7.1 Objective
5.7.1 客观的

To determine the address caching capacity of a LAN switching device as defined in RFC 2285, section 3.8.1 [2].

确定RFC 2285第3.8.1[2]节中定义的LAN交换设备的地址缓存容量。

5.7.2 Setup Parameters
5.7.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Age Time - The maximum time that a DUT/SUT will keep a learned address in its forwarding table.

老化时间-DUT/SUT在其转发表中保留读入地址的最长时间。

Addresses Learning Rate - The rate at which new addresses are offered to the DUT/SUT to be learned. The rate at which address learning frames are offered may have to be adjusted to be as low as 50 frames per second or even less, to guarantee successful learning.

地址学习速率-向DUT/SUT提供新地址以进行学习的速率。提供地址学习帧的速率可能必须调整为低至每秒50帧或更低,以确保成功学习。

Initial Addresses - The initial number of addresses to start the test with. The number MUST be between 1 and the maximum number supported by the implementation.

初始地址-开始测试的初始地址数。该数字必须介于1和实现支持的最大数字之间。

5.7.3 Procedure
5.7.3 程序

The aging time of the DUT/SUT MUST be known. The aging time MUST be longer than the time necessary to produce frames at the specified rate. If a low frame rate is used for the test, then it may be possible that sending a large amount of frames may actually take longer than the aging time.

必须知道DUT/SUT的老化时间。老化时间必须长于以指定速率生成帧所需的时间。如果测试使用低帧速率,则发送大量帧实际上可能需要比老化时间更长的时间。

This test MUST at a minimum be performed in a three-port configuration described below. The test MAY be expanded to fully utilized the DUT/SUT in increments of two or three ports. An increment of two would include an additional Learning port and Test port. An increment of three would include an additional Learning port, Test port, and Monitoring port.

该测试至少必须在下述三端口配置中执行。测试可以扩展到以两个或三个端口为增量充分利用DUT/SUT。增加两个将包括一个额外的学习端口和测试端口。增加三个将包括一个额外的学习端口、测试端口和监视端口。

The Learning port (Lport) transmits learning frames to the DUT/SUT with varying source addresses and a fixed destination address corresponding to the address of the device connected to the Test port (Tport) of the DUT/SUT. By receiving frames with varying source addresses, the DUT/SUT should learn these new addresses. The source addresses MAY be in sequential order.

学习端口(Lport)使用与DUT/SUT的测试端口(Tport)连接的设备的地址相对应的不同源地址和固定目的地址向DUT/SUT发送学习帧。通过接收具有不同源地址的帧,DUT/SUT应该学习这些新地址。源地址可以按顺序排列。

The Test port (Tport) of the DUT/SUT acts as the receiving port for the learning frames. Test frames will be transmitted back to the addresses learned on the Learning port. The algorithm for this is explained below.

DUT/SUT的测试端口(Tport)充当学习帧的接收端口。测试帧将被传输回在学习端口上学习到的地址。下面解释用于此的算法。

The Monitoring port (Mport) on the DUT/SUT acts as a monitoring port to listen for flooded or mis-forwarded frames. If the test spans multiple broadcast domains (VLANs), each broadcast domain REQUIRES a Monitoring port.

DUT/SUT上的监控端口(Mport)充当监控端口,用于侦听被淹没或转发错误的帧。如果测试跨越多个广播域(VLAN),则每个广播域都需要一个监视端口。

It is highly recommended that SNMP, Spanning Tree, and any other frames originating from the DUT/SUT be disabled when running this test. If such protocols cannot be turned off, the flood count MUST be modified only to count test frame originating from Lport and MUST NOT count frames originating from the DUT/SUT.

强烈建议在运行此测试时禁用SNMP、生成树和源自DUT/SUT的任何其他帧。如果无法关闭此类协议,则必须修改泛洪计数,仅对源自Lport的测试帧进行计数,不得对源自DUT/SUT的帧进行计数。

The algorithm for the test is as follows:

测试的算法如下所示:

   CONSTANT
      AGE = ...;  {value greater that DUT aging time}
      MAX = ...;  {maximum address support by implementation}
    VARIABLE
      LOW  := 0;    {Highest passed valve}
      HIGH := MAX;  {Lowest failed value}
      N    := ...;  {user specified initial starting point}
    BEGIN
      DO
        BEGIN
        PAUSE(AGE);   {Age out any learned addresses}
          AddressLearning(TPort); {broadcast a frame with its source
                                  Address and broadcast destination}
          AddressLearning(LPort); {N frames with varying source addresses
                                  to Test Port}
        Transmit(TPort); {N frames with varying destination addresses
                           corresponding to Learning Port}
        IF (MPort receive frame != 0) OR
           (LPort receive frames < TPort transmit) THEN
          BEGIN  {Address Table of DUT/SUT was full}
            HIGH := N;
          END
        ELSE
          BEGIN  {Address Table of DUT/SUT was NOT full}
            LOW := N;
          END
        N := LOW + (HIGH - LOW)/2;
      END WHILE (HIGH - LOW >= 2);
    END {Value of N equals number of addresses supported by DUT/SUT}
        
   CONSTANT
      AGE = ...;  {value greater that DUT aging time}
      MAX = ...;  {maximum address support by implementation}
    VARIABLE
      LOW  := 0;    {Highest passed valve}
      HIGH := MAX;  {Lowest failed value}
      N    := ...;  {user specified initial starting point}
    BEGIN
      DO
        BEGIN
        PAUSE(AGE);   {Age out any learned addresses}
          AddressLearning(TPort); {broadcast a frame with its source
                                  Address and broadcast destination}
          AddressLearning(LPort); {N frames with varying source addresses
                                  to Test Port}
        Transmit(TPort); {N frames with varying destination addresses
                           corresponding to Learning Port}
        IF (MPort receive frame != 0) OR
           (LPort receive frames < TPort transmit) THEN
          BEGIN  {Address Table of DUT/SUT was full}
            HIGH := N;
          END
        ELSE
          BEGIN  {Address Table of DUT/SUT was NOT full}
            LOW := N;
          END
        N := LOW + (HIGH - LOW)/2;
      END WHILE (HIGH - LOW >= 2);
    END {Value of N equals number of addresses supported by DUT/SUT}
        

Using a binary search approach, the test targets the exact number of addresses supported per port with consistent test iterations. Due to the aging time of DUT/SUT address tables, each iteration may take some time during the waiting period for the addresses to clear. If possible, configure the DUT/SUT for a low value for the aging time.

使用二进制搜索方法,测试以每个端口支持的地址的确切数量为目标,并具有一致的测试迭代。由于DUT/SUT地址表的老化时间,每次迭代可能需要一些时间等待地址清除。如果可能,将DUT/SUT配置为老化时间的低值。

Once the high and low values of N meet, then the threshold of address handling has been found.

一旦N的高值和低值满足要求,就找到了地址处理的阈值。

5.7.4 Measurements
5.7.4 测量

Whether the offered addresses per port was successful forwarded without flooding.

每个端口提供的地址是否成功转发而没有泛洪。

5.7.5 Reporting format
5.7.5 报告格式

After the test is run, results for each iteration SHOULD be displayed in a table to include:

测试运行后,每个迭代的结果应显示在表中,包括:

The number of addresses used for each test iteration (varied).

每个测试迭代使用的地址数(不同)。

The intended load used for each test iteration (fixed).

用于每个测试迭代的预期负载(固定)。

Number of test frames that were offered to Tport of the DUT/SUT. This SHOULD match the number of addresses used for the test iteration. Test frames are the frames sent with varying destination addresses to confirm that the DUT/SUT has learned all of the addresses for each test iteration.

提供给DUT/SUT Tport的测试机架数量。这应该与测试迭代使用的地址数量相匹配。测试帧是使用不同的目标地址发送的帧,以确认DUT/SUT已学习了每个测试迭代的所有地址。

The flood count on Tport during the test portion of each test. If the number is non-zero, this is an indication of the DUT/SUT flooding a frame in which the destination address is not in the address table.

在每次测试的测试部分,Tport上的洪水计数。如果数字不为零,则表示DUT/SUT淹没了目标地址不在地址表中的帧。

The number of frames correctly forwarded to test Lport during the test portion of the test. Received frames MUST have the correct destination MAC address and SHOULD match a signature field. For a passing test iteration, this number should be equal to the number of frames transmitted by Tport.

在测试的测试部分期间,正确转发到测试Lport的帧数。接收到的帧必须具有正确的目标MAC地址,并且应该与签名字段匹配。对于通过测试的迭代,该数量应等于Tport传输的帧数。

The flood count on Lport during the test portion of each test. If the number is non-zero, this is an indication of the DUT/SUT flooding a frame in which the destination address is not in the address table.

在每次试验的试验部分,Lport上的洪水计数。如果数字不为零,则表示DUT/SUT淹没了目标地址不在地址表中的帧。

The flood count on Mport. If the value is not zero, then this indicates that for that test iteration, the DUT/SUT could not determine the proper destination port for that many frames. In other words, the DUT/SUT flooded the frame to all ports since its address table was full.

洪水要靠港口。如果该值不为零,则这表示对于该测试迭代,DUT/SUT无法为这么多帧确定正确的目标端口。换言之,DUT/SUT由于其地址表已满,所以将帧淹没到所有端口。

5.8 Address Learning Rate
5.8 地址学习率
5.8.1 Objective
5.8.1 客观的

To determine the rate of address learning of a LAN switching device.

确定LAN交换设备的地址学习速率。

5.8.2 Setup Parameters
5.8.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Age Time - The maximum time that a DUT/SUT will keep a learned address in its forwarding table.

老化时间-DUT/SUT在其转发表中保留读入地址的最长时间。

Initial Addresses Learning Rate - The starting rate at which new addresses are offered to the DUT/SUT to be learned.

初始地址学习速率-向DUT/SUT提供新地址以进行学习的起始速率。

Number of Addresses - The number of addresses that the DUT/SUT must learn. The number MUST be between 1 and the maximum number supported by the implementation. It is recommended no to exceed the address caching capacity found in section 5.9

地址数-DUT/SUT必须学习的地址数。该数字必须介于1和实现支持的最大数字之间。建议不要超过第5.9节中的地址缓存容量

5.8.3 Procedure
5.8.3 程序

The aging time of the DUT/SUT MUST be known. The aging time MUST be longer than the time necessary to produce frames at the specified rate. If a low frame rate is used for the test, then it may be possible that sending a large amount of frames may actually take longer than the aging time.

必须知道DUT/SUT的老化时间。老化时间必须长于以指定速率生成帧所需的时间。如果测试使用低帧速率,则发送大量帧实际上可能需要比老化时间更长的时间。

This test MUST at a minimum be performed in a three-port configuration in section 5.9.3. The test MAY be expanded to fully utilized the DUT/SUT in increments of two or three ports. An increment of two would include an additional Learning port and Test port. An increment of three would include an additional Learning port, Test port, and Monitoring port.

本试验至少必须在第5.9.3节中的三端口配置中进行。测试可以扩展到以两个或三个端口为增量充分利用DUT/SUT。增加两个将包括一个额外的学习端口和测试端口。增加三个将包括一个额外的学习端口、测试端口和监视端口。

An algorithm similar to the one used to determine address caching capacity can be used to determine the address learning rate. This test iterates the rate at which address learning frames are offered

可以使用与用于确定地址缓存容量的算法类似的算法来确定地址学习速率。此测试迭代提供地址学习帧的速率

by the test device connected to the DUT/SUT. It is recommended to set the number of addresses offered to the DUT/SUT in this test to the maximum caching capacity.

通过连接到DUT/SUT的测试设备。建议将本测试中提供给DUT/SUT的地址数设置为最大缓存容量。

The address learning rate might be determined for different numbers of addresses but in each test run, the number MUST remain constant and SHOULD be equal to or less than the maximum address caching capacity.

地址学习速率可以为不同数量的地址确定,但在每次测试运行中,地址学习速率必须保持不变,并且应等于或小于最大地址缓存容量。

5.8.4 Measurements
5.8.4 测量

Whether the offered addresses per port were successful forwarded without flooding at the offered learning rate.

每个端口提供的地址是否以提供的学习速率成功转发,而不会发生泛洪。

5.8.5 Reporting format
5.8.5 报告格式

After the test is run, results for each iteration SHOULD be displayed in a table:

测试运行后,每次迭代的结果应显示在表格中:

The number of addresses used for each test iteration (fixed).

每个测试迭代使用的地址数(固定)。

The intended load used for each test iteration (varied).

用于每个测试迭代的预期负载(变化)。

Number of test frames that were transmitted by Tport. This SHOULD match the number of addresses used for the test iteration. Test frames are the frames sent with varying destination addresses to confirm that the DUT/SUT has learned all of the addresses for each test iteration.

Tport传输的测试帧数。这应该与测试迭代使用的地址数量相匹配。测试帧是使用不同的目标地址发送的帧,以确认DUT/SUT已学习了每个测试迭代的所有地址。

The flood count on Tport during the test portion of each test. If the number is non-zero, this is an indication of the DUT/SUT flooding a frame in which the destination address is not in the address table.

在每次测试的测试部分,Tport上的洪水计数。如果数字不为零,则表示DUT/SUT淹没了目标地址不在地址表中的帧。

The number of frames correctly forwarded to test Lport during the test portion of the test. Received frames MUST have the correct destination MAC address and SHOULD match a signature field. For a passing test iteration, this number should be equal to the number of frames transmitted by Tport.

在测试的测试部分期间,正确转发到测试Lport的帧数。接收到的帧必须具有正确的目标MAC地址,并且应该与签名字段匹配。对于通过测试的迭代,该数量应等于Tport传输的帧数。

The flood count on Lport during the test portion of each test. If the number is non-zero, this is an indication of the DUT/SUT flooding a frame in which the destination address is not in the address table.

在每次试验的试验部分,Lport上的洪水计数。如果数字不为零,则表示DUT/SUT淹没了目标地址不在地址表中的帧。

The flood count on Mport. If the value is not zero, then this indicates that for that test iteration, the DUT/SUT could not determine the proper destination port for that many frames. In other words, the DUT/SUT flooded the frame to all ports since its address table was full.

洪水要靠港口。如果该值不为零,则这表示对于该测试迭代,DUT/SUT无法为这么多帧确定正确的目标端口。换言之,DUT/SUT由于其地址表已满,所以将帧淹没到所有端口。

5.9 Errored frames filtering
5.9 错误帧滤波
5.9.1 Objective
5.9.1 客观的

The objective of the Errored frames filtering test is to determine the behavior of the DUT under error or abnormal frame conditions. The results of the test indicate if the DUT/SUT filters the errors, or simply propagates the errored frames along to the destination.

错误帧过滤测试的目的是确定DUT在错误或异常帧条件下的行为。测试结果表明DUT/SUT是否过滤错误,或者只是将错误帧传播到目的地。

5.9.2 Setup Parameters
5.9.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load possible. The actual transmitted frame per second is dependent upon half duplex or full duplex operation. The test SHOULD be run multiple times with a different load per port in each case.

ILoad-每个端口的预期负载以介质可能的最大理论负载的百分比表示。每秒实际传输的帧数取决于半双工或全双工操作。在每种情况下,测试应以每个端口不同的负载运行多次。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.9.3 Procedure
5.9.3 程序

Each of the illegal frames for Ethernet MUST be checked:

必须检查以太网的每个非法帧:

Oversize - The DUT/SUT MAY filter frames larger than 1518 bytes from being propagated through the DUT/SUT section 4.2.4.2.1 [4]. Oversized frames transmitted to the DUT/SUT should not be forwarded. DUT/SUT supporting tagged Frames MAY forward frames up to and including 1522 bytes long (section 4.2.4.2.1 [5]).

超大-DUT/SUT可过滤通过DUT/SUT第4.2.4.2.1节传播的大于1518字节的帧[4]。传输到DUT/SUT的超大帧不应转发。支持标记帧的DUT/SUT可转发长度不超过1522字节的帧(第4.2.4.2.1[5]节)。

Undersize - The DUT/SUT MUST filter frames less than 64 bytes from being propagated through the DUT/SUT (section 4.2.4.2.2 [4]). Undersized frames (or collision fragments) received by the DUT/SUT must not be forwarded.

尺寸过小-DUT/SUT必须过滤通过DUT/SUT传播的小于64字节的帧(第4.2.4.2.2[4]节)。DUT/SUT接收到的尺寸过小的帧(或冲突片段)不得转发。

CRC Errors - The DUT/SUT MUST filter frames that fail the Frame Check Sequence Validation (section 4.2.4.1.2 [4]) from being propagated through the DUT/SUT. Frames with an invalid CRC transmitted to the DUT/SUT should not be forwarded.

CRC错误-DUT/SUT必须过滤未通过帧检查序列验证(第4.2.4.1.2[4]节)的帧,防止其通过DUT/SUT传播。传输到DUT/SUT的CRC无效的帧不应转发。

Dribble Bit Errors - The DUT/SUT MUST correct and forward frames containing dribbling bits. Frames transmitted to the DUT/SUT that do not end in an octet boundary but contain a valid frame check sequence MUST be accepted by the DUT/SUT (section 4.2.4.2.1 [4]) and forwarded to the correct receive port with the frame ending in an octet boundary (section 3.4 [4]).

运球位错误-DUT/SUT必须纠正并转发包含运球位的帧。传输到DUT/SUT的帧不以八位字节边界结束,但包含有效的帧检查序列,必须被DUT/SUT接受(第4.2.4.2.1[4]节),并转发到正确的接收端口,帧以八位字节边界结束(第3.4[4]节)。

Alignment Errors - The DUT/SUT MUST filter frames that fail the Frame Check Sequence Validation AND do not end in an octet boundary. This is a combination of a CRC error and a Dribble Bit error. When both errors are occurring in the same frame, the DUT/SUT MUST determine the CRC error takes precedence and filters the frame (section 4.2.4.1.2 [4]) from being propagated.

对齐错误-DUT/SUT必须过滤未通过帧检查序列验证且不以八位字节边界结束的帧。这是CRC错误和运球位错误的组合。当两个错误发生在同一帧中时,DUT/SUT必须确定CRC错误优先,并过滤该帧(第4.2.4.1.2[4]节)。

5.9.5 Reporting format
5.9.5 报告格式

For each of the error conditions in section 5.6.3, a "pass" or "fail" MUST be reported. Actual frame counts MAY be reported for diagnostic purposes.

对于第5.6.3节中的每个错误情况,必须报告“通过”或“失败”。出于诊断目的,可能会报告实际帧计数。

5.10 Broadcast frame Forwarding and Latency
5.10 广播帧转发和延迟
5.10.1 Objective
5.10.1 客观的

The objective of the Broadcast Frame Forwarding and Latency Test is to determine the throughput and latency of the DUT when forwarding broadcast traffic. The ability to forward broadcast frames will depend upon a specific function built into the device for that purpose. It is therefore necessary to determine the ability of DUT/SUT to handle broadcast frames, since there may be many different ways of implementing such a function.

广播帧转发和延迟测试的目的是确定转发广播流量时DUT的吞吐量和延迟。转发广播帧的能力将取决于为此目的内置在设备中的特定功能。因此,有必要确定DUT/SUT处理广播帧的能力,因为可能有许多不同的方法来实现这种功能。

5.10.2 Setup Parameters
5.10.2 设置参数

The following parameters MUST be defined. Each variable is configured with the following considerations.

必须定义以下参数。每个变量都配置了以下注意事项。

Frame Size - Recommended frame sizes are 64, 128, 256, 512, 1024, 1280 and 1518 bytes, per RFC 2544 section 9 [3]. The four CRC bytes are included in the frame size specified.

帧大小-根据RFC 2544第9节[3],建议的帧大小为64、128、256、512、1024、1280和1518字节。四个CRC字节包含在指定的帧大小中。

Duplex mode - Half duplex or full duplex.

双工模式-半双工或全双工。

ILoad - Intended Load per port is expressed in a percentage of the medium's maximum theoretical load, regardless of traffic orientation or duplex mode. Certain test configurations will theoretically over-subscribe the DUT/SUT.

ILoad—每个端口的预期负载以介质最大理论负载的百分比表示,而与流量方向或双工模式无关。某些测试配置在理论上会超过DUT/SUT。

ILoad will not over-subscribe the DUT/SUT in this test.

在本测试中,ILoad不会过度订阅DUT/SUT。

Trial Duration - The recommended Trial Duration is 30 seconds. Trial duration SHOULD be adjustable between 1 and 300 seconds.

试验持续时间-建议的试验持续时间为30秒。试验持续时间应在1到300秒之间可调。

5.10.3 Procedure
5.10.3 程序

For this test, there are two parts to be run.

对于该测试,有两个部分需要运行。

Broadcast Frame Throughput - This portion of the test uses a single source test port to transmit test frames with a broadcast address using the frame specified in RFC 2544 [3]. Selected receive ports then measure the forwarding rate and Frame loss rate.

广播帧吞吐量-这部分测试使用单个源测试端口,使用RFC 2544[3]中指定的帧,通过广播地址传输测试帧。选定的接收端口然后测量转发速率和帧丢失率。

Broadcast Frame Latency - This test uses the same setup as the Broadcast Frame throughput, but instead of a large stream of test frames being sent, only one test frame is sent and the latency to each of the receive ports are measured in seconds.

广播帧延迟-此测试使用与广播帧吞吐量相同的设置,但不是发送大量测试帧,而是只发送一个测试帧,并以秒为单位测量每个接收端口的延迟。

5.10.4 Measurements
5.10.4 测量

Frame loss rate of the DUT/SUT SHOULD be reported as defined in section 26.3 [3] with the following notes: Frame loss rate SHOULD be measured at the end of the trial duration. The term "rate", for this measurement only, does not imply the units in the fashion of "per second."

应按照第26.3节[3]的规定报告DUT/SUT的帧丢失率,并注意以下事项:应在试验期间结束时测量帧丢失率。术语“速率”仅用于此测量,并不意味着单位为“每秒”

Forwarding rate (FR) of the DUT/SUT SHOULD be reported as the number of test frames per second that the device is observed to successfully forward to the correct destination interface in response to a specified Oload. The Oload MUST also be cited.

DUT/SUT的转发速率(FR)应报告为每秒观察到设备响应指定Oload成功转发至正确目的地接口的测试帧数。还必须引用Oload。

5.10.5 Reporting format
5.10.5 报告格式

The results for these tests SHOULD be reported in the form of a graph. The x coordinate SHOULD be the frame size, the y coordinate SHOULD be the test results. There SHOULD be at least two lines on the graph, one plotting the theoretical and one plotting the test results.

这些试验的结果应以图表的形式报告。x坐标应为框架尺寸,y坐标应为测试结果。图表上至少应有两条线,一条绘制理论,另一条绘制试验结果。

To measure the DUT/SUT's ability to switch traffic while performing many different address lookups, the number of addresses per port MAY be increased in a series of tests.

为了测量DUT/SUT在执行许多不同地址查找时切换流量的能力,可以在一系列测试中增加每个端口的地址数。

6. Security Considerations
6. 安全考虑

As this document is solely for the purpose of providing metric methodology and describes neither a protocol nor a protocol's implementation, there are no security considerations associated with this document.

由于本文件仅用于提供度量方法,并且既不描述协议也不描述协议的实现,因此本文件没有相关的安全注意事项。

7. References
7. 工具书类

[1] Bradner, S., Editor, "Benchmarking Terminology for Network Interconnection Devices", RFC 1242, July 1991.

[1] Bradner,S.,编辑,“网络互连设备的基准术语”,RFC 1242,1991年7月。

[2] Mandeville, R., "Benchmarking Terminology for LAN Switching Devices", RFC 2285, February 1998.

[2] Mandeville,R.,“局域网交换设备的基准术语”,RFC 2285,1998年2月。

[3] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, March 1999.

[3] Bradner,S.和J.McQuaid,“网络互连设备的基准测试方法”,RFC 25441999年3月。

[4] ANSI/IEEE, "CSMA/CD Access Method and Physical Layer Specifications," ISO/IEC 8802-3, ISBN 0-7381-0330-6, 1998.

[4] ANSI/IEEE,“CSMA/CD访问方法和物理层规范”,ISO/IEC 8802-3,ISBN 0-7381-0330-61998。

[5] IEEE Draft, "Frame Extensions for Virtual Bridged Local Area Networks (VLAN) Tagging on 802.3 Networks", 802.3ac/D3.1, July 1998.

[5] IEEE草案,“802.3网络上虚拟桥接局域网(VLAN)标记的帧扩展”,802.3ac/D3.11998年7月。

8. Authors' Addresses
8. 作者地址

Robert Mandeville CQOS Inc. 21 Technology Irvine, CA 92618 USA

Robert Mandeville CQOS Inc.美国加利福尼亚州欧文市21科技公司,邮编92618

   Phone: +1 (949) 400-4444
   EMail: bob@cqos.com
        
   Phone: +1 (949) 400-4444
   EMail: bob@cqos.com
        

Jerry Perser Spirent Communications 26750 Agoura Road Calabasas, CA 91302 USA

Jerry Perser Spirent Communications美国加利福尼亚州卡拉巴斯市Agoura路26750号,邮编:91302

   Phone: + 1 818 676 2300
   EMail: jerry_perser@netcomsystems.com
        
   Phone: + 1 818 676 2300
   EMail: jerry_perser@netcomsystems.com
        

Appendix A: Formulas

附录A:公式

A.1 Calculating the InterBurst Gap
A.1计算爆发间间隙

IBG is defined in RFC 2285 [2] as the interval between two bursts. To achieve a desired load, the following Input Parameter need to be defined:

在RFC 2285[2]中,IBG定义为两次爆发之间的间隔。为达到所需负载,需要定义以下输入参数:

LENGTH - Frame size in bytes including the CRC.

长度-帧大小(字节),包括CRC。

LOAD - The intended load in percent. Range is 0 to 100.

负载-以百分比表示的预期负载。范围是0到100。

BURST - The number of frames in the burst (integer value).

突发-突发中的帧数(整数值)。

SPEED - media's speed in bits/sec Ethernet is 10,000,000 bits/sec Fast Ethernet is 100,000,000 bits/sec Gigabit Ethernet is 1,000,000,000 bits/sec

速度-以比特/秒为单位的媒体速度以太网为10000000比特/秒快速以太网为100000000比特/秒千兆以太网为100000000比特/秒

IFG - A constant 96 bits for the minimum interframe gap.

IFG-最小帧间间隙的恒定96位。

The IBG (in seconds) can be calculated:

IBG(以秒为单位)可通过以下方式计算:

          [(100/LOAD - 1) * BURST * (IFG + 64 + 8*LENGTH)] + IFG
   IBG = -----------------------------------------------------------
                                  SPEED
        
          [(100/LOAD - 1) * BURST * (IFG + 64 + 8*LENGTH)] + IFG
   IBG = -----------------------------------------------------------
                                  SPEED
        
A.2 Calculating the Number of Bursts for the Trial Duration
A.2计算试验期间的爆破次数

The number of bursts for the trial duration is rounded up to the nearest integer number. The follow Input Parameter need to be defined:

试验期间的突发次数向上舍入至最接近的整数。需要定义以下输入参数:

LENGTH - Frame size in bytes including the CRC.

长度-帧大小(字节),包括CRC。

BURST - The number of frames in the burst (integer value).

突发-突发中的帧数(整数值)。

SPEED - media's speed in bits/sec Ethernet is 10,000,000 bits/sec Fast Ethernet is 100,000,000 bits/sec Gigabit Ethernet is 1,000,000,000 bits/sec

速度-以比特/秒为单位的媒体速度以太网为10000000比特/秒快速以太网为100000000比特/秒千兆以太网为100000000比特/秒

IFG - A constant 96 bits for the minimum interframe gap.

IFG-最小帧间间隙的恒定96位。

IBG - Found in the above formula

IBG-可在上述公式中找到

DURATION - Trial duration in seconds.

持续时间-以秒为单位的试验持续时间。

An intermediate number of the Burst duration needs to be calculated first:

首先需要计算突发持续时间的中间数:

    TXTIME  =  -----------------------------------------
                               SPEED
        
    TXTIME  =  -----------------------------------------
                               SPEED
        

Number of Burst for the Trial Duration (rounded up):

试验期间的爆破次数(四舍五入):

                     DURATION
    #OFBURSTS =   --------------
                  (TXTIME + IBG)
        
                     DURATION
    #OFBURSTS =   --------------
                  (TXTIME + IBG)
        

Example:

例子:

LENGTH = 64 bytes per frame LOAD = 100 % offered load BURST = 24 frames per burst SPEED = 10 Mbits/sec (Ethernet) DURATION = 10 seconds test

长度=每帧64字节负载=100%提供的负载突发=每突发24帧速度=10 Mbits/sec(以太网)持续时间=10秒测试

IBG = 1612.8 uS TXTIME = 1603.2 uS #OFBURSTS = 3110

IBG=1612.8 uS TXTIME=1603.2 uS#of bursts=3110

Appendix B: Generating Offered Load

附录B:提供的发电负荷

In testing, the traffic generator is configured with the Iload (Intended Load) and measures the Oload (Offered Load). If the DUT/SUT applies congestion control, then the Iload and the Oload are not the same value. The question arises, how to generate the Oload? This appendix will describe two different methods.

在测试中,流量生成器配置有Iload(预期负载)并测量Oload(提供负载)。如果DUT/SUT应用拥塞控制,则Iload和Oload的值不同。问题是,如何生成Oload?本附录将描述两种不同的方法。

The unit of measurement for Oload is bits per second. The two methods described here will hold one unit constant and let the DUT/SUT vary the other unit. The traffic generator SHOULD specify which method it uses.

Oload的测量单位为位/秒。这里描述的两种方法将保持一个单位不变,并使DUT/SUT改变另一个单位。流量生成器应指定它使用的方法。

B.1 Frame Based Load
B.1基于帧的负载

Frame Based Load holds the number of bits constant. The Trial Duration will vary based upon congestion control. Advantage is implementation is a simple state machine (or loop). The disadvantage is that Oload needs to be measured independently.

基于帧的加载保持比特数不变。试验持续时间将根据拥塞控制而变化。优点是实现是一个简单的状态机(或循环)。缺点是Oload需要独立测量。

All ports on the traffic generator MUST transmit the exact number of test frames. The exact number of test frames is found by multiplying the Iload of the port by the Trial Duration. All ports MAY NOT transmit the same number of frames if their Iload is not the same. An example would be the Partially meshed many-to-one test.

流量生成器上的所有端口都必须传输准确数量的测试帧。通过将端口的Iload乘以试验持续时间,可以找到测试帧的确切数量。如果Iload不相同,则所有端口可能不会传输相同数量的帧。例如,部分啮合多对一测试。

All ports SHOULD start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames within 300 milliseconds of each other.

所有端口应在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应在彼此之间300毫秒内开始传输帧。

The reported Oload SHOULD be the average during the Trial Duration. If the traffic generator continues to transmit after the Trial Duration due to congestion control, Oload MAY be averaged over the entire transmit time. Oload for the DUT/SUT MUST be the aggregate of all the Oloads per port. Oload per port MAY be reported.

报告的Oload应为试验期间的平均值。如果由于拥塞控制,业务生成器在试验持续时间之后继续传输,则可以在整个传输时间内平均Oload。DUT/SUT的Oload必须是每个端口所有Oload的总和。可以报告每个端口的Oload。

B.2 Time Based Load
B.2基于时间的负载

Time based load holds the Trial Duration constant, while allowing the number of octets transmitted to vary. Advantages are an accurate Trial Duration and integrated Oload measurement. Disadvantage is that the starting and stopping of the traffic generator MUST be more accurate.

基于时间的负载保持试验持续时间不变,同时允许传输的八位字节数变化。优点是准确的试验持续时间和完整的Oload测量。缺点是流量生成器的启动和停止必须更加精确。

All ports on the traffic generator are configured to transmit the Iload for a finite amount of time. Each port MUST count the number of octets successfully transmitted.

流量生成器上的所有端口都配置为在有限的时间内传输Iload。每个端口必须统计成功传输的八位字节数。

The start and stop is initiated at a layer defined by the test parameters. The layer can be the MAC layer, IP layer, or some other point in the protocol stack. The traffic generator MUST complete its layer specific transmit process when the stop time is reached (i.e. no fragments, finish the frame).

启动和停止在测试参数定义的层上启动。该层可以是MAC层、IP层或协议栈中的某个其他点。当达到停止时间(即无碎片,完成帧)时,流量生成器必须完成其特定于层的传输过程。

All ports MUST start transmitting their frames within 1% of the trial duration. For a trial duration of 30 seconds, all ports SHOULD have started transmitting frames within 300 milliseconds of each other.

所有端口必须在试验持续时间的1%内开始传输其帧。在30秒的试用期内,所有端口应在彼此之间300毫秒内开始传输帧。

All ports SHOULD stop transmitting frames after the specified trail duration within 0.01% of the trial duration. Each port's stop time MUST be reference to its start time. This trial duration error controls the accuracy of the Oload measurement and SHOULD be reported with the Oload measurement.

所有端口应在指定的试验持续时间后,在试验持续时间的0.01%内停止传输帧。每个端口的停止时间必须参考其开始时间。此试验持续时间误差控制Oload测量的准确性,应与Oload测量一起报告。

Each port is allowed an offset error of 0.1% and a trial duration error of 0.01%.

每个端口允许0.1%的偏移误差和0.01%的试验持续时间误差。

Oload is found by taking the number of octets successfully transmitted and dividing by the trial duration. Oload for the DUT/SUT MUST be the aggregate of all the Oloads per port. Oload per port MAY be reported for diagnostic purposes.

Oload是通过将成功传输的八位字节数除以试验持续时间得到的。DUT/SUT的Oload必须是每个端口所有Oload的总和。出于诊断目的,可以报告每个端口的Oload。

Full Copyright Statement

完整版权声明

Copyright (C) The Internet Society (2000). All Rights Reserved.

版权所有(C)互联网协会(2000年)。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人,对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发,不受任何限制,前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是,不得以任何方式修改本文件本身,例如删除版权通知或对互联网协会或其他互联网组织的引用,除非出于制定互联网标准的需要,在这种情况下,必须遵循互联网标准过程中定义的版权程序,或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

上述授予的有限许可是永久性的,互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

本文件和其中包含的信息是按“原样”提供的,互联网协会和互联网工程任务组否认所有明示或暗示的保证,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。