Network Working Group S. Bradner
Request for Comments: 2544 Harvard University
Obsoletes: 1944 J. McQuaid
Category: Informational NetScout Systems
March 1999
Network Working Group S. Bradner
Request for Comments: 2544 Harvard University
Obsoletes: 1944 J. McQuaid
Category: Informational NetScout Systems
March 1999
Benchmarking Methodology for Network Interconnect 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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
IESG Note
IESG注释
This document is a republication of RFC 1944 correcting the values for the IP addresses which were assigned to be used as the default addresses for networking test equipment. (See section C.2.2 ). This RFC replaces and obsoletes RFC 1944.
本文件是RFC 1944的再版，修正了分配用作网络测试设备默认地址的IP地址值。（见第C.2.2节）。本RFC取代并淘汰了RFC 1944。
Abstract
摘要
This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. In addition to defining the tests this document also describes specific formats for reporting the results of the tests. Appendix A lists the tests and conditions that we believe should be included for specific cases and gives additional information about testing practices. Appendix B is a reference listing of maximum frame rates to be used with specific frame sizes on various media and Appendix C gives some examples of frame formats to be used in testing.
本文件讨论并定义了一系列可用于描述网络互连设备性能特征的测试。除了定义测试外，本文件还描述了报告测试结果的具体格式。附录A列出了我们认为应包括在特定情况下的测试和条件，并提供了有关测试实践的附加信息。附录B是各种媒体上特定帧大小使用的最大帧速率的参考列表，附录C给出了测试中使用的帧格式的一些示例。
Vendors often engage in "specsmanship" in an attempt to give their products a better position in the marketplace. This often involves "smoke & mirrors" to confuse the potential users of the products.
供应商经常采用“规格技巧”，试图让他们的产品在市场上占据更好的地位。这通常涉及“烟雾和镜子”，以混淆产品的潜在用户。
This document defines a specific set of tests that vendors can use to measure and report the performance characteristics of network devices. The results of these tests will provide the user comparable data from different vendors with which to evaluate these devices.
本文档定义了一组特定的测试，供应商可以使用这些测试来测量和报告网络设备的性能特征。这些测试的结果将为用户提供来自不同供应商的可比数据，用于评估这些设备。
A previous document, "Benchmarking Terminology for Network Interconnect Devices" (RFC 1242), 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.
先前的文档“网络互连设备的基准术语”（RFC 1242）定义了本文档中使用的许多术语。在尝试使用本文件之前，应查阅术语文件。
In producing this document the authors attempted to keep in mind the requirement that apparatus to perform the described tests must actually be built. We do not know of "off the shelf" equipment available to implement all of the tests but it is our opinion that such equipment can be constructed.
在编制本文件时，作者试图牢记执行所述测试的设备必须实际建造的要求。我们不知道是否有“现成”设备可用于实施所有测试，但我们认为可以建造此类设备。
There are a number of tests described in this document. Not all of the tests apply to all types of devices under test (DUTs). Vendors should perform all of the tests that can be supported by a specific type of product. The authors understand that it will take a considerable period of time to perform all of the recommended tests nder all of the recommended conditions. We believe that the results are worth the effort. Appendix A lists some of the tests and conditions that we believe should be included for specific cases.
本文档中描述了许多测试。并非所有测试都适用于所有类型的被测设备（DUT）。供应商应执行特定类型产品支持的所有测试。作者了解，在所有推荐条件下进行所有推荐试验需要相当长的时间。我们认为，这些结果是值得努力的。附录A列出了我们认为应包括在特定情况下的一些测试和条件。
Performing all of the recommended tests will result in a great deal of data. Much of this data will not apply to the evaluation of the devices under each circumstance. For example, the rate at which a router forwards IPX frames will be of little use in selecting a router for an environment that does not (and will not) support that protocol. Evaluating even that data which is relevant to a particular network installation will require experience which may not be readily available. Furthermore, selection of the tests to be run and evaluation of the test data must be done with an understanding of generally accepted testing practices regarding repeatability, variance and statistical significance of small numbers of trials.
执行所有推荐的测试将产生大量数据。这些数据中的大部分不适用于各种情况下的设备评估。例如，路由器转发IPX帧的速率对于为不（也不会）支持该协议的环境选择路由器几乎没有用处。即使评估与特定网络安装相关的数据，也需要经验，而这些经验可能并不容易获得。此外，选择要运行的测试和评估测试数据时，必须了解关于少量试验的重复性、方差和统计显著性的公认测试实践。
In this document, the words that are used to define the significance of each particular requirement are capitalized. These words are:
在本文件中，用于定义每个特定要求重要性的词语大写。这些词是：
* "MUST" This word, or the words "REQUIRED" and "SHALL" mean that the item is an absolute requirement of the specification.
* “必须”一词，或“要求”和“应”一词表示该项目是本规范的绝对要求。
* "SHOULD" This word or the adjective "RECOMMENDED" means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course.
* “应该”这个词或形容词“建议”意味着在特定情况下可能存在忽略该项目的正当理由，但在选择不同的课程之前，应理解其全部含义并仔细权衡情况。
* "MAY" This word or the adjective "OPTIONAL" means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item.
* “MAY”这个词或形容词“OPTIONAL”表示这个项目确实是可选的。一个供应商可能会选择包括该项目，因为特定的市场需要它，或者因为它增强了产品，例如；另一个供应商可以省略相同的项目。
An implementation is not compliant if it fails to satisfy one or more of the MUST requirements for the protocols it implements. An implementation that satisfies all the MUST and all the SHOULD requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the MUST requirements but not all the SHOULD requirements for its protocols is said to be "conditionally compliant".
如果一个实现未能满足其实现的协议的一个或多个必需要求，则该实现是不兼容的。满足其协议所有必须和应该要求的实现称为“无条件兼容”；满足其协议的所有必须要求但并非所有应该要求的协议称为“有条件地符合”。
The ideal way to implement this series of tests is to use a tester with both transmitting and receiving ports. Connections are made from the sending ports of the tester to the receiving ports of the DUT and from the sending ports of the DUT back to the tester. (see Figure 1) Since the tester both sends the test traffic and receives it back, after the traffic has been forwarded but the DUT, the tester can easily determine if all of the transmitted packets were received and verify that the correct packets were received. The same functionality can be obtained with separate transmitting and receiving devices (see Figure 2) but unless they are remotely controlled by some computer in a way that simulates the single tester, the labor required to accurately perform some of the tests (particularly the throughput test) can be prohibitive.
实现这一系列测试的理想方法是使用具有发送和接收端口的测试仪。从测试仪的发送端口连接到DUT的接收端口，从DUT的发送端口连接回测试仪。（参见图1）由于测试仪发送测试通信量并将其接收回，在通信量被转发但DUT未被转发后，测试仪可以轻松确定是否接收到所有发送的数据包，并验证是否接收到正确的数据包。使用单独的发送和接收设备可以获得相同的功能（见图2），但除非它们由某台计算机以模拟单个测试仪的方式进行远程控制，否则准确执行某些测试（特别是吞吐量测试）所需的人工可能会被禁止。
+------------+
| |
+------------| tester |<-------------+
| | | |
| +------------+ |
| |
| +------------+ |
| | | |
+----------->| DUT |--------------+
| |
+------------+
Figure 1
+------------+
| |
+------------| tester |<-------------+
| | | |
| +------------+ |
| |
| +------------+ |
| | | |
+----------->| DUT |--------------+
| |
+------------+
Figure 1
+--------+ +------------+ +----------+
| | | | | |
| sender |-------->| DUT |--------->| receiver |
| | | | | |
+--------+ +------------+ +----------+
Figure 2
+--------+ +------------+ +----------+
| | | | | |
| sender |-------->| DUT |--------->| receiver |
| | | | | |
+--------+ +------------+ +----------+
Figure 2
Two different setups could be used to test a DUT which is used in real-world networks to connect networks of differing media type, local Ethernet to a backbone FDDI ring for example. The tester could support both media types in which case the set up shown in Figure 1 would be used.
可以使用两种不同的设置来测试DUT，DUT在现实网络中用于连接不同媒体类型的网络，例如本地以太网到主干FDDI环。测试仪可以支持两种介质类型，在这种情况下，将使用图1所示的设置。
Two identical DUTs are used in the other test set up. (see Figure 3) In many cases this set up may more accurately simulate the real world. For example, connecting two LANs together with a WAN link or high speed backbone. This set up would not be as good at simulating a system where clients on a Ethernet LAN were interacting with a server on an FDDI backbone.
另一个测试设置中使用两个相同的DUT。（见图3）在许多情况下，这种设置可以更准确地模拟真实世界。例如，使用WAN链路或高速主干将两个LAN连接在一起。这种设置在模拟以太局域网上的客户机与FDDI主干上的服务器交互的系统方面不太好。
+-----------+
| |
+---------------------| tester |<---------------------+
| | | |
| +-----------+ |
| |
| +----------+ +----------+ |
| | | | | |
+------->| DUT 1 |-------------->| DUT 2 |---------+
| | | |
+----------+ +----------+
+-----------+
| |
+---------------------| tester |<---------------------+
| | | |
| +-----------+ |
| |
| +----------+ +----------+ |
| | | | | |
+------->| DUT 1 |-------------->| DUT 2 |---------+
| | | |
+----------+ +----------+
Figure 3
图3
Before starting to perform the tests, the DUT to be tested MUST be configured following the instructions provided to the user. Specifically, it is expected that all of the supported protocols will be configured and enabled during this set up (See Appendix A). It is expected that all of the tests will be run without changing the configuration or setup of the DUT in any way other than that required to do the specific test. For example, it is not acceptable to change the size of frame handling buffers between tests of frame handling rates or to disable all but one transport protocol when testing the throughput of that protocol. It is necessary to modify the configuration when starting a test to determine the effect of filters on throughput, but the only change MUST be to enable the specific filter. The DUT set up SHOULD include the normally recommended routing update intervals and keep alive frequency. The specific version of the software and the exact DUT configuration, including what functions are disabled, used during the tests MUST be included as part of the report of the results.
在开始执行测试之前，必须按照提供给用户的说明配置要测试的DUT。具体而言，预计在此设置期间将配置并启用所有受支持的协议（见附录A）。预计所有测试都将在不改变DUT配置或设置的情况下运行，而不是以进行特定测试所需的方式。例如，在测试帧处理速率之间更改帧处理缓冲区的大小或在测试该协议的吞吐量时禁用除一个之外的所有传输协议是不可接受的。在启动测试以确定过滤器对吞吐量的影响时，有必要修改配置，但唯一的更改必须是启用特定过滤器。DUT设置应包括通常建议的路由更新间隔和保持活动频率。测试期间使用的软件的特定版本和确切DUT配置，包括禁用的功能，必须作为结果报告的一部分。
The formats of the test frames to use for TCP/IP over Ethernet are shown in Appendix C: Test Frame Formats. These exact frame formats SHOULD be used in the tests described in this document for this protocol/media combination and that these frames will be used as a template for testing other protocol/media combinations. The specific formats that are used to define the test frames for a particular test series MUST be included in the report of the results.
用于以太网TCP/IP的测试帧格式如附录C：测试帧格式所示。这些精确的帧格式应用于本文档中描述的该协议/媒体组合的测试，并且这些帧将用作测试其他协议/媒体组合的模板。用于定义特定测试系列的测试框架的特定格式必须包含在结果报告中。
All of the described tests SHOULD be performed at a number of frame sizes. Specifically, the sizes SHOULD include the maximum and minimum legitimate sizes for the protocol under test on the media under test and enough sizes in between to be able to get a full characterization of the DUT performance. Except where noted, at least five frame sizes SHOULD be tested for each test condition.
所有描述的测试应在多种框架尺寸下进行。具体而言，尺寸应包括被测介质上被测协议的最大和最小合法尺寸，以及能够获得DUT性能完整特征的足够尺寸。除非另有说明，否则应针对每个试验条件对至少五种框架尺寸进行试验。
Theoretically the minimum size UDP Echo request frame would consist of an IP header (minimum length 20 octets), a UDP header (8 octets) and whatever MAC level header is required by the media in use. The theoretical maximum frame size is determined by the size of the length field in the IP header. In almost all cases the actual maximum and minimum sizes are determined by the limitations of the media.
理论上，最小大小的UDP回送请求帧将由一个IP报头（最小长度为20个八位字节）、一个UDP报头（8个八位字节）和所用媒体所需的任何MAC级报头组成。理论上的最大帧大小由IP报头中长度字段的大小决定。在几乎所有情况下，实际的最大和最小尺寸都是由介质的限制决定的。
In theory it would be ideal to distribute the frame sizes in a way that would evenly distribute the theoretical frame rates. These recommendations incorporate this theory but specify frame sizes which are easy to understand and remember. In addition, many of the same frame sizes are specified on each of the media types to allow for easy performance comparisons.
理论上，以一种能够均匀分布理论帧速率的方式来分布帧大小是理想的。这些建议结合了这一理论，但规定了易于理解和记忆的框架尺寸。此外，在每种介质类型上都指定了许多相同的帧大小，以便进行性能比较。
Note: The inclusion of an unrealistically small frame size on some of the media types (i.e. with little or no space for data) is to help characterize the per-frame processing overhead of the DUT.
注：在某些媒体类型上包含不现实的小帧大小（即数据空间很少或没有空间）有助于表征DUT的每帧处理开销。
64, 128, 256, 512, 1024, 1280, 1518
64, 128, 256, 512, 1024, 1280, 1518
These sizes include the maximum and minimum frame sizes permitted by the Ethernet standard and a selection of sizes between these extremes with a finer granularity for the smaller frame sizes and higher frame rates.
这些大小包括以太网标准允许的最大和最小帧大小，以及在这些极端之间的大小选择，对于较小的帧大小和较高的帧速率，具有更细的粒度。
54, 64, 128, 256, 1024, 1518, 2048, 4472
54, 64, 128, 256, 1024, 1518, 2048, 4472
The frame size recommendations for token ring assume that there is no RIF field in the frames of routed protocols. A RIF field would be present in any direct source route bridge performance test. The minimum size frame for UDP on token ring is 54 octets. The maximum size of 4472 octets is recommended for 16Mb token ring instead of the theoretical size of 17.9Kb because of the size limitations imposed by many token ring interfaces. The reminder of the sizes are selected to permit direct comparisons with other types of media. An IP (i.e. not UDP) frame may be used in addition if a higher data rate is desired, in which case the minimum frame size is 46 octets.
令牌环的帧大小建议假定路由协议的帧中没有RIF字段。RIF场将出现在任何直接源路线桥梁性能测试中。令牌环上UDP的最小帧大小为54个八位字节。由于许多令牌环接口的大小限制，建议16Mb令牌环的最大大小为4472个八位字节，而不是17.9Kb的理论大小。选择大小提醒以允许与其他类型的介质进行直接比较。如果需要更高的数据速率，则还可以使用IP（即非UDP）帧，在这种情况下，最小帧大小为46个八位字节。
54, 64, 128, 256, 1024, 1518, 2048, 4472
54, 64, 128, 256, 1024, 1518, 2048, 4472
The minimum size frame for UDP on FDDI is 53 octets, the minimum size of 54 is recommended to allow direct comparison to token ring performance. The maximum size of 4472 is recommended instead of the theoretical maximum size of 4500 octets to permit the same type of comparison. An IP (i.e. not UDP) frame may be used in addition if a higher data rate is desired, in which case the minimum frame size is 45 octets.
FDDI上UDP的最小帧大小为53个八位字节，建议最小帧大小为54，以便与令牌环性能进行直接比较。建议使用4472的最大大小，而不是4500个八位字节的理论最大大小，以允许进行相同类型的比较。如果需要更高的数据速率，则还可以使用IP（即非UDP）帧，在这种情况下，最小帧大小为45个八位字节。
When the interconnect DUT supports connecting links with disparate MTUs, the frame sizes for the link with the *larger* MTU SHOULD be used, up to the limit of the protocol being tested. If the interconnect DUT does not support the fragmenting of frames in the presence of MTU mismatch, the forwarding rate for that frame size shall be reported as zero.
当互连DUT支持连接具有不同MTU的链路时，应使用具有*更大*MTU的链路的帧大小，直至被测试协议的限制。如果互连DUT不支持MTU不匹配情况下的帧分段，则该帧大小的转发速率应报告为零。
For example, the test of IP forwarding with a bridge or router that joins FDDI and Ethernet should use the frame sizes of FDDI when going from the FDDI to the Ethernet link. If the bridge does not support IP fragmentation, the forwarding rate for those frames too large for Ethernet should be reported as zero.
例如，使用连接FDDI和以太网的网桥或路由器进行IP转发测试时，从FDDI到以太网链路时，应使用FDDI的帧大小。如果网桥不支持IP分段，那么对于以太网来说太大的帧的转发速率应报告为零。
The test equipment SHOULD discard any frames received during a test run that are not actual forwarded test frames. For example, keep-alive and routing update frames SHOULD NOT be included in the count of received frames. In any case, the test equipment SHOULD verify the length of the received frames and check that they match the expected length.
测试设备应丢弃在测试运行期间接收到的不是实际转发测试帧的任何帧。例如，“保持活动”和“路由更新”帧不应包含在接收帧的计数中。在任何情况下，测试设备都应验证接收帧的长度，并检查它们是否与预期长度匹配。
Preferably, the test equipment SHOULD include sequence numbers in the transmitted frames and check for these numbers on the received frames. If this is done, the reported results SHOULD include in addition to the number of frames dropped, the number of frames that were received out of order, the number of duplicate frames received and the number of gaps in the received frame numbering sequence. This functionality is required for some of the described tests.
优选地，测试设备应包括发送帧中的序列号，并在接收帧上检查这些序列号。如果这样做，报告的结果除应包括丢弃的帧数外，还应包括无序接收的帧数、接收到的重复帧数以及接收到的帧编号序列中的间隙数。某些所述测试需要此功能。
It might be useful to know the DUT performance under a number of conditions; some of these conditions are noted below. The reported results SHOULD include as many of these conditions as the test equipment is able to generate. The suite of tests SHOULD be first run without any modifying conditions and then repeated under each of the conditions separately. To preserve the ability to compare the results of these tests any frames that are required to generate the modifying conditions (management queries for example) will be included in the same data stream as the normal test frames in place of one of the test frames and not be supplied to the DUT on a separate network port.
了解DUT在多种条件下的性能可能很有用；其中一些情况如下所述。报告的结果应包括测试设备能够产生的所有这些条件。测试套件应首先在没有任何修改条件的情况下运行，然后在每个条件下分别重复。为了保持比较这些测试结果的能力，生成修改条件（例如，管理查询）所需的任何帧将被包括在与正常测试帧相同的数据流中，以代替其中一个测试帧，并且不会通过单独的网络端口提供给DUT。
In most router designs special processing is required when frames addressed to the hardware broadcast address are received. In bridges (or in bridge mode on routers) these broadcast frames must be flooded to a number of ports. The stream of test frames SHOULD be augmented with 1% frames addressed to the hardware broadcast address. The frames sent to the broadcast address should be of a type that the router will not need to process. The aim of this test is to determine if there is any effect on the forwarding rate of the other data in the stream. The specific frames that should be used are included in the test frame format document. The broadcast frames SHOULD be evenly distributed throughout the data stream, for example, every 100th frame.
在大多数路由器设计中，当接收到寻址到硬件广播地址的帧时，需要进行特殊处理。在网桥（或路由器上的网桥模式）中，这些广播帧必须被淹没到多个端口。测试帧流应增加寻址到硬件广播地址的1%帧。发送到广播地址的帧应该是路由器不需要处理的类型。此测试的目的是确定是否对流中其他数据的转发速率有任何影响。应使用的特定框架包含在测试框架格式文档中。广播帧应均匀地分布在整个数据流中，例如，每100帧。
The same test SHOULD be performed on bridge-like DUTs but in this case the broadcast packets will be processed and flooded to all outputs.
应在桥式DUT上执行相同的测试，但在这种情况下，将处理广播数据包并将其发送至所有输出。
It is understood that a level of broadcast frames of 1% is much higher than many networks experience but, as in drug toxicity evaluations, the higher level is required to be able to gage the effect which would otherwise often fall within the normal variability of the system performance. Due to design factors some test equipment will not be able to generate a level of alternate frames this low. In these cases the percentage SHOULD be as small as the equipment can provide and that the actual level be described in the report of the test results.
据了解，1%的广播帧水平远高于许多网络经验，但与药物毒性评估一样，需要更高的水平才能测量影响，否则影响通常会在系统性能的正常变化范围内。由于设计因素，一些测试设备将无法生成如此低水平的备用帧。在这些情况下，百分比应尽可能小，并在试验结果报告中说明实际水平。
Most data networks now make use of management protocols such as SNMP. In many environments there can be a number of management stations sending queries to the same DUT at the same time.
大多数数据网络现在使用管理协议，如SNMP。在许多环境中，可以有多个管理站同时向同一DUT发送查询。
The stream of test frames SHOULD be augmented with one management query as the first frame sent each second during the duration of the trial. The result of the query must fit into one response frame. The response frame SHOULD be verified by the test equipment. One example of the specific query frame that should be used is shown in Appendix C.
测试帧流应该增加一个管理查询，作为测试期间每秒发送的第一个帧。查询结果必须适合一个响应帧。响应框架应通过测试设备进行验证。应使用的特定查询框架的一个示例如附录C所示。
The processing of dynamic routing protocol updates could have a significant impact on the ability of a router to forward data frames. The stream of test frames SHOULD be augmented with one routing update frame transmitted as the first frame transmitted during the trial.
动态路由协议更新的处理可能对路由器转发数据帧的能力产生重大影响。测试帧流应增加一个路由更新帧，作为试验期间传输的第一个帧。
Routing update frames SHOULD be sent at the rate specified in Appendix C for the specific routing protocol being used in the test. Two routing update frames are defined in Appendix C for the TCP/IP over Ethernet example. The routing frames are designed to change the routing to a number of networks that are not involved in the forwarding of the test data. The first frame sets the routing table state to "A", the second one changes the state to "B". The frames MUST be alternated during the trial.
对于测试中使用的特定路由协议，应按照附录C中规定的速率发送路由更新帧。对于TCP/IP over Ethernet示例，附录C中定义了两个路由更新帧。路由帧用于将路由更改为不涉及测试数据转发的多个网络。第一帧将路由表状态设置为“A”，第二帧将状态更改为“B”。在试验期间，必须交替使用框架。
The test SHOULD verify that the routing update was processed by the DUT.
测试应验证路由更新是否由DUT处理。
Filters are added to routers and bridges to selectively inhibit the forwarding of frames that would normally be forwarded. This is usually done to implement security controls on the data that is accepted between one area and another. Different products have different capabilities to implement filters.
将过滤器添加到路由器和网桥，以选择性地抑制通常会转发的帧的转发。这样做通常是为了对一个区域和另一个区域之间接受的数据实施安全控制。不同的产品具有不同的功能来实现过滤器。
The DUT SHOULD be first configured to add one filter condition and the tests performed. This filter SHOULD permit the forwarding of the test data stream. In routers this filter SHOULD be of the form:
应首先将DUT配置为添加一个过滤器条件和执行的测试。该过滤器应允许转发测试数据流。在路由器中，此过滤器的形式应为：
forward input_protocol_address to output_protocol_address
将输入\协议\地址转发到输出\协议\地址
In bridges the filter SHOULD be of the form:
在桥梁中，过滤器的形式应为：
forward destination_hardware_address
转发目标\u硬件\u地址
The DUT SHOULD be then reconfigured to implement a total of 25 filters. The first 24 of these filters SHOULD be of the form:
然后应重新配置DUT，以实现总共25个过滤器。这些过滤器中的前24个应采用以下形式：
block input_protocol_address to output_protocol_address
阻止输入\协议\地址到输出\协议\地址
The 24 input and output protocol addresses SHOULD not be any that are represented in the test data stream. The last filter SHOULD permit the forwarding of the test data stream. By "first" and "last" we mean to ensure that in the second case, 25 conditions must be checked before the data frames will match the conditions that permit the forwarding of the frame. Of course, if the DUT reorders the filters or does not use a linear scan of the filter rules the effect of the sequence in which the filters are input is properly lost.
24个输入和输出协议地址不应是测试数据流中表示的任何地址。最后一个过滤器应允许转发测试数据流。通过“第一个”和“最后一个”，我们的意思是确保在第二种情况下，在数据帧与允许帧转发的条件匹配之前，必须检查25个条件。当然，如果DUT对滤波器进行重新排序或不使用滤波器规则的线性扫描，则滤波器输入顺序的效果将正确丢失。
The exact filters configuration command lines used SHOULD be included with the report of the results.
结果报告中应包括使用的确切过滤器配置命令行。
Two sets of filter addresses are required, one for the single filter case and one for the 25 filter case.
需要两组筛选器地址，一组用于单个筛选器，另一组用于25个筛选器。
The single filter case should permit traffic from IP address 198.18.1.2 to IP address 198.19.65.2 and deny all other traffic.
单一筛选器情况应允许从IP地址198.18.1.2到IP地址198.19.65.2的流量，并拒绝所有其他流量。
The 25 filter case should follow the following sequence.
25滤清器壳体应遵循以下顺序。
deny aa.ba.1.1 to aa.ba.100.1 deny aa.ba.2.2 to aa.ba.101.2 deny aa.ba.3.3 to aa.ba.103.3 ... deny aa.ba.12.12 to aa.ba.112.12 allow aa.bc.1.2 to aa.bc.65.1 deny aa.ba.13.13 to aa.ba.113.13 deny aa.ba.14.14 to aa.ba.114.14 ... deny aa.ba.24.24 to aa.ba.124.24 deny all else
拒绝aa.ba.1.1至aa.ba.100.1拒绝aa.ba.2.2至aa.ba.101.2拒绝aa.ba.3.3至aa.ba.103.3。。。拒绝aa.ba.12.12至aa.ba.112.12允许aa.bc.1.2至aa.bc.65.1拒绝aa.ba.13.13至aa.ba.113.13拒绝aa.ba.14.14至aa.ba.114.14。。。拒绝aa.ba.24.24至aa.ba.124.24拒绝所有其他
All previous filter conditions should be cleared from the router before this sequence is entered. The sequence is selected to test to see if the router sorts the filter conditions or accepts them in the order that they were entered. Both of these procedures will result in a greater impact on performance than will some form of hash coding.
在输入此序列之前，应清除路由器上以前的所有过滤条件。选择该序列以测试路由器是否对过滤条件进行排序，或是否按照输入的顺序接受过滤条件。这两个过程对性能的影响都比某种形式的散列编码更大。
It is easier to implement these tests using a single logical stream of data, with one source protocol address and one destination protocol address, and for some conditions like the filters described above, a practical requirement. Networks in the real world are not limited to single streams of data. The test suite SHOULD be first run with a single protocol (or hardware for bridge tests) source and destination address pair. The tests SHOULD then be repeated with using a random destination address. While testing routers the addresses SHOULD be random and uniformly distributed over a range of 256 networks and random and uniformly distributed over the full MAC range for bridges. The specific address ranges to use for IP are shown in Appendix C.
使用一个逻辑数据流、一个源协议地址和一个目标协议地址更容易实现这些测试，对于某些情况（如上述过滤器），这是一个实际需求。现实世界中的网络并不局限于单个数据流。测试套件应首先使用单个协议（或桥接测试的硬件）源地址和目标地址对运行。然后应使用随机目标地址重复测试。测试路由器时，地址应在256个网络范围内随机均匀分布，在网桥的整个MAC范围内随机均匀分布。IP使用的具体地址范围如附录C所示。
It is not reasonable that all of the routing information necessary to forward the test stream, especially in the multiple address case, will be manually set up. At the start of each trial a routing update MUST be sent to the DUT. This routing update MUST include all of the network addresses that will be required for the trial. All of the addresses SHOULD resolve to the same "next-hop". Normally this will be the address of the receiving side of the test equipment. This routing update will have to be repeated at the interval required by the routing protocol being used. An example of the format and repetition interval of the update frames is given in Appendix C.
将手动设置转发测试流所需的所有路由信息（尤其是在多地址情况下）是不合理的。在每次试验开始时，必须向DUT发送路由更新。此路由更新必须包括试用所需的所有网络地址。所有地址都应解析为相同的“下一跳”。通常，这是测试设备接收端的地址。必须按照所使用的路由协议要求的间隔重复此路由更新。附录C中给出了更新帧的格式和重复间隔示例。
Normal network activity is not all in a single direction. To test the bidirectional performance of a DUT, the test series SHOULD be run with the same data rate being offered from each direction. The sum of the data rates should not exceed the theoretical limit for the media.
正常的网络活动并非都是单向的。为了测试DUT的双向性能，测试系列应以每个方向提供的相同数据速率运行。数据速率之和不应超过介质的理论极限。
The full suite of tests SHOULD be run along with whatever modifier conditions that are relevant using a single input and output network port on the DUT. If the internal design of the DUT has multiple distinct pathways, for example, multiple interface cards each with multiple network ports, then all possible types of pathways SHOULD be tested separately.
使用DUT上的单个输入和输出网络端口，全套测试应与相关的任何修改器条件一起运行。如果DUT的内部设计有多个不同的路径，例如，多个接口卡，每个接口卡具有多个网络端口，则应单独测试所有可能的路径类型。
Many current router and bridge products provide many network ports in the same module. In performing these tests first half of the ports are designated as "input ports" and half are designated as "output ports". These ports SHOULD be evenly distributed across the DUT architecture. For example if a DUT has two interface cards each of which has four ports, two ports on each interface card are designated as input and two are designated as output. The specified tests are run using the same data rate being offered to each of the input ports. The addresses in the input data streams SHOULD be set so that a frame will be directed to each of the output ports in sequence so that all "output" ports will get an even distribution of packets from this input. The same configuration MAY be used to perform a bidirectional multi-stream test. In this case all of the ports are considered both input and output ports and each data stream MUST consist of frames addressed to all of the other ports.
当前许多路由器和网桥产品在同一模块中提供许多网络端口。在执行这些测试时，前一半端口被指定为“输入端口”，另一半被指定为“输出端口”。这些端口应均匀分布在DUT体系结构中。例如，如果DUT有两个接口卡，每个接口卡有四个端口，则每个接口卡上的两个端口指定为输入，两个端口指定为输出。使用提供给每个输入端口的相同数据速率运行指定的测试。应设置输入数据流中的地址，以便按顺序将帧定向到每个输出端口，以便所有“输出”端口将从该输入获得均匀的数据包分布。相同的配置可用于执行双向多流测试。在这种情况下，所有端口都被视为输入和输出端口，每个数据流必须由寻址到所有其他端口的帧组成。
Consider the following 6 port DUT:
考虑以下6个端口DUT：
--------------
---------| in A out X|--------
---------| in B out Y|--------
---------| in C out Z|--------
--------------
--------------
---------| in A out X|--------
---------| in B out Y|--------
---------| in C out Z|--------
--------------
The addressing of the data streams for each of the inputs SHOULD be:
每个输入的数据流寻址应为：
stream sent to input A: packet to out X, packet to out Y, packet to out Z stream sent to input B: packet to out X, packet to out Y, packet to out Z stream sent to input C packet to out X, packet to out Y, packet to out Z
发送至输入A的流：发送至输出X的数据包，发送至输出Y的数据包，发送至输入B的数据包：发送至输出X的数据包，发送至输出Y的数据包，发送至输入C的数据包，发送至输出X的数据包，发送至输出Y的数据包，发送至输出Z的数据包
Note that these streams each follow the same sequence so that 3 packets will arrive at output X at the same time, then 3 packets at Y, then 3 packets at Z. This procedure ensures that, as in the real world, the DUT will have to deal with multiple packets addressed to the same output at the same time.
请注意，这些流都遵循相同的顺序，因此3个数据包将同时到达输出X，然后在Y处到达3个数据包，然后在Z处到达3个数据包。此过程确保，与在现实世界中一样，DUT必须同时处理多个发往同一输出的数据包。
This document does not address the issue of testing the effects of a mixed protocol environment other than to suggest that if such tests are wanted then frames SHOULD be distributed between all of the test protocols. The distribution MAY approximate the conditions on the network in which the DUT would be used.
本文件不涉及测试混合协议环境效果的问题，只是建议如果需要此类测试，则应在所有测试协议之间分配帧。分布可能近似于DUT将在其中使用的网络上的条件。
This document does not address the issue of testing the effects of a mixed frame size environment other than to suggest that if such tests are wanted then frames SHOULD be distributed between all of the listed sizes for the protocol under test. The distribution MAY approximate the conditions on the network in which the DUT would be used. The authors do not have any idea how the results of such a test would be interpreted other than to directly compare multiple DUTs in some very specific simulated network.
本文件不涉及测试混合帧大小环境的影响的问题，只是建议如果需要此类测试，则帧应分布在测试协议的所有列出的大小之间。分布可能近似于DUT将在其中使用的网络上的条件。除了直接比较某些特定模拟网络中的多个DUT外，作者不知道如何解释此类测试的结果。
19. Testing performance beyond a single DUT.
19. 测试单个DUT之外的性能。
In the performance testing of a single DUT, the paradigm can be described as applying some input to a DUT and monitoring the output. The results of which can be used to form a basis of characterization of that device under those test conditions.
在单个DUT的性能测试中，范例可以描述为向DUT应用一些输入并监视输出。其结果可用于在这些试验条件下形成该装置特性的基础。
This model is useful when the test input and output are homogenous (e.g., 64-byte IP, 802.3 frames into the DUT; 64 byte IP, 802.3 frames out), or the method of test can distinguish between dissimilar input/output. (E.g., 1518 byte IP, 802.3 frames in; 576 byte, fragmented IP, X.25 frames out.)
当测试输入和输出是同质的（例如，64字节IP，802.3帧进入DUT；64字节IP，802.3帧输出）或测试方法可以区分不同的输入/输出时，该模型非常有用。（例如，1518字节IP，802.3帧输入；576字节，分段IP，X.25帧输出。）
By extending the single DUT test model, reasonable benchmarks regarding multiple DUTs or heterogeneous environments may be collected. In this extension, the single DUT is replaced by a system of interconnected network DUTs. This test methodology would support the benchmarking of a variety of device/media/service/protocol combinations. For example, a configuration for a LAN-to-WAN-to-LAN test might be:
通过扩展单个DUT测试模型，可以收集关于多个DUT或异构环境的合理基准。在此扩展中，单个DUT被互连网络DUT系统取代。该测试方法将支持各种设备/媒体/服务/协议组合的基准测试。例如，LAN到WAN到LAN测试的配置可能是：
(1) 802.3-> DUT 1 -> X.25 @ 64kbps -> DUT 2 -> 802.3
(1) 802.3-> DUT 1 -> X.25 @ 64kbps -> DUT 2 -> 802.3
Or a mixed LAN configuration might be:
或者，混合LAN配置可能是：
(2) 802.3 -> DUT 1 -> FDDI -> DUT 2 -> FDDI -> DUT 3 -> 802.3
(2) 802.3 -> DUT 1 -> FDDI -> DUT 2 -> FDDI -> DUT 3 -> 802.3
In both examples 1 and 2, end-to-end benchmarks of each system could be empirically ascertained. Other behavior may be characterized through the use of intermediate devices. In example 2, the configuration may be used to give an indication of the FDDI to FDDI capability exhibited by DUT 2.
在示例1和2中，可以根据经验确定每个系统的端到端基准。其他行为可通过使用中间装置来表征。在实例2中，该配置可用于给出DUT 2所展示的FDDI到FDDI能力的指示。
Because multiple DUTs are treated as a single system, there are limitations to this methodology. For instance, this methodology may yield an aggregate benchmark for a tested system. That benchmark alone, however, may not necessarily reflect asymmetries in behavior between the DUTs, latencies introduce by other apparatus (e.g., CSUs/DSUs, switches), etc.
由于多个DUT被视为单个系统，因此该方法存在局限性。例如，此方法可能会为测试系统生成一个聚合基准。然而，仅该基准不一定反映DUT之间行为的不对称性、由其他设备（例如，CSU/DSU、交换机）引入的延迟等。
Further, care must be used when comparing benchmarks of different systems by ensuring that the DUTs' features/configuration of the tested systems have the appropriate common denominators to allow comparison.
此外，在比较不同系统的基准时必须小心，确保被测系统的DUT特性/配置具有适当的公分母，以便进行比较。
The maximum frame rates that should be used when testing LAN connections SHOULD be the listed theoretical maximum rate for the frame size on the media.
测试LAN连接时应使用的最大帧速率应为介质上帧大小的理论最大速率。
The maximum frame rate that should be used when testing WAN connections SHOULD be greater than the listed theoretical maximum rate for the frame size on that speed connection. The higher rate for WAN tests is to compensate for the fact that some vendors employ various forms of header compression.
测试WAN连接时应使用的最大帧速率应大于该速度连接上帧大小的理论最大速率。广域网测试的较高速率是为了补偿一些供应商采用各种形式的报头压缩的事实。
A list of maximum frame rates for LAN connections is included in Appendix B.
LAN连接的最大帧速率列表包含在附录B中。
It is convenient to measure the DUT performance under steady state load but this is an unrealistic way to gauge the functioning of a DUT since actual network traffic normally consists of bursts of frames. Some of the tests described below SHOULD be performed with both steady state traffic and with traffic consisting of repeated bursts of frames. The frames within a burst are transmitted with the minimum legitimate inter-frame gap.
在稳态负载下测量DUT性能很方便，但这是一种不现实的方法来衡量DUT的功能，因为实际网络流量通常由突发帧组成。下面描述的一些测试应在稳态通信量和由重复帧突发组成的通信量情况下进行。突发中的帧以最小合法帧间间隔传输。
The objective of the test is to determine the minimum interval between bursts which the DUT can process with no frame loss. During each test the number of frames in each burst is held constant and the inter-burst interval varied. Tests SHOULD be run with burst sizes of 16, 64, 256 and 1024 frames.
测试的目的是确定DUT可以在无帧丢失的情况下处理的最小脉冲间隔。在每次测试期间，每次突发中的帧数保持不变，突发间隔变化。测试应以16、64、256和1024帧的突发大小运行。
Although it is possible to configure some token ring and FDDI interfaces to transmit more than one frame each time that the token is received, most of the network devices currently available transmit only one frame per token. These tests SHOULD first be performed while transmitting only one frame per token.
尽管可以将一些令牌环和FDDI接口配置为在每次接收令牌时发送多个帧，但是当前可用的大多数网络设备仅为每个令牌发送一个帧。这些测试应首先在每个令牌仅传输一帧时执行。
Some current high-performance workstation servers do transmit more than one frame per token on FDDI to maximize throughput. Since this may be a common feature in future workstations and servers, interconnect devices with FDDI interfaces SHOULD be tested with 1, 4, 8, and 16 frames per token. The reported frame rate SHOULD be the average rate of frame transmission over the total trial period.
当前的一些高性能工作站服务器确实在FDDI上每个令牌传输一个以上的帧，以最大限度地提高吞吐量。由于这可能是未来工作站和服务器中的常见功能，因此应使用每个令牌1、4、8和16帧测试具有FDDI接口的互连设备。报告的帧速率应为整个试验期间的平均帧速率。
A particular test consists of multiple trials. Each trial returns one piece of information, for example the loss rate at a particular input frame rate. Each trial consists of a number of phases:
一个特定的测试由多个试验组成。每次试验返回一条信息，例如特定输入帧速率下的丢失率。每个试验包括多个阶段：
a) If the DUT is a router, send the routing update to the "input" port and pause two seconds to be sure that the routing has settled.
a) 如果DUT是路由器，则将路由更新发送到“输入”端口，并暂停两秒钟，以确保路由已解决。
b) Send the "learning frames" to the "output" port and wait 2 seconds to be sure that the learning has settled. Bridge learning frames are frames with source addresses that are the same as the destination addresses used by the test frames. Learning frames for other protocols are used to prime the address resolution tables in the DUT. The formats of the learning frame that should be used are shown in the Test Frame Formats document.
b) 将“学习帧”发送到“输出”端口，并等待2秒钟以确保学习已完成。桥接学习帧是源地址与测试帧使用的目标地址相同的帧。其他协议的学习帧用于初始化DUT中的地址解析表。应使用的学习框架格式见测试框架格式文档。
c) Run the test trial.
c) 运行测试。
d) Wait for two seconds for any residual frames to be received.
d) 等待两秒钟以接收任何剩余帧。
e) Wait for at least five seconds for the DUT to restabilize.
e) 等待DUT重新稳定至少5秒钟。
The aim of these tests is to determine the rate continuously supportable by the DUT. The actual duration of the test trials must be a compromise between this aim and the duration of the benchmarking test suite. The duration of the test portion of each trial SHOULD be at least 60 seconds. The tests that involve some form of "binary search", for example the throughput test, to determine the exact result MAY use a shorter trial duration to minimize the length of the search procedure, but the final determination SHOULD be made with full length trials.
这些测试的目的是确定DUT持续支持的速率。测试测试的实际持续时间必须是该目标和基准测试套件持续时间之间的折衷。每次试验的试验部分的持续时间应至少为60秒。涉及某种形式的“二进制搜索”的测试，例如吞吐量测试，以确定准确的结果，可使用较短的试验持续时间来最小化搜索过程的长度，但最终的确定应采用全长试验。
The DUT SHOULD be able to respond to address resolution requests sent by the DUT wherever the protocol requires such a process.
DUT应能够响应DUT发送的地址解析请求，只要协议需要这样的过程。
26. Benchmarking tests:
26. 基准测试：
Note: The notation "type of data stream" refers to the above modifications to a frame stream with a constant inter-frame gap, for example, the addition of traffic filters to the configuration of the DUT.
注：“数据流类型”表示对具有恒定帧间间隙的帧流的上述修改，例如，向DUT的配置添加业务滤波器。
Objective: To determine the DUT throughput as defined in RFC 1242.
目的：确定RFC1242中定义的DUT吞吐量。
Procedure: Send a specific number of frames at a specific rate through the DUT and then count the frames that are transmitted by the DUT. If the count of offered frames is equal to the count of received frames, the fewer frames are received than were transmitted, the rate of the offered stream is reduced and the test is rerun.
程序：通过DUT以特定速率发送特定数量的帧，然后对DUT发送的帧进行计数。如果提供的帧的计数等于接收的帧的计数，则接收的帧比发送的帧少，提供的流的速率降低，并且重新运行测试。
The throughput is the fastest rate at which the count of test frames transmitted by the DUT is equal to the number of test frames sent to it by the test equipment.
吞吐量是DUT发送的测试帧数等于测试设备发送给它的测试帧数的最快速率。
Reporting format: The results of the throughput test SHOULD be reported in the form of a graph. If it is, the x coordinate SHOULD be the frame size, the y coordinate SHOULD be the frame rate. There SHOULD be at least two lines on the graph. There SHOULD be one line showing the theoretical frame rate for the media at the various frame sizes. The second line SHOULD be the plot of the test results. Additional lines MAY be used on the graph to report the results for each type of data stream tested. Text accompanying the graph SHOULD indicate the protocol, data stream format, and type of media used in the tests.
报告格式：吞吐量测试的结果应以图表的形式报告。如果是，则x坐标应为帧大小，y坐标应为帧速率。图表上至少应有两条线。应该有一行显示不同帧大小的媒体的理论帧速率。第二行应该是测试结果的曲线图。可以在图表上使用其他行来报告测试的每种数据流类型的结果。图表中的文字应说明测试中使用的协议、数据流格式和媒体类型。
We assume that if a single value is desired for advertising purposes the vendor will select the rate for the minimum frame size for the media. If this is done then the figure MUST be expressed in frames per second. The rate MAY also be expressed in bits (or bytes) per second if the vendor so desires. The statement of performance MUST include a/ the measured maximum frame rate, b/ the size of the frame used, c/ the theoretical limit of the media for that frame size, and d/ the type of protocol used in the test. Even if a single value is used as part of the advertising copy, the full table of results SHOULD be included in the product data sheet.
我们假设，如果出于广告目的需要单个值，则供应商将选择媒体最小帧大小的速率。如果这样做，则图形必须以每秒帧数表示。如果供应商愿意，速率也可以以每秒比特（或字节）表示。性能声明必须包括a/测量的最大帧速率，b/所用帧的大小，c/该帧大小的媒体理论极限，以及d/测试中使用的协议类型。即使单个值用作广告副本的一部分，完整的结果表也应包含在产品数据表中。
Objective: To determine the latency as defined in RFC 1242.
目的：确定RFC1242中定义的潜伏期。
Procedure: First determine the throughput for DUT at each of the listed frame sizes. Send a stream of frames at a particular frame size through the DUT at the determined throughput rate to a specific destination. The stream SHOULD be at least 120 seconds in duration. An identifying tag SHOULD be included in one frame after 60 seconds with the type of tag being implementation dependent. The time at which this frame is fully transmitted is recorded (timestamp A). The receiver logic in the test equipment MUST recognize the tag information in the frame stream and record the time at which the tagged frame was received (timestamp B).
程序：首先确定所列每种帧尺寸下DUT的吞吐量。以确定的吞吐量通过DUT将特定帧大小的帧流发送到特定目的地。流的持续时间应至少为120秒。识别标签应在60秒后的一帧中包含，标签类型取决于实现。记录该帧被完全传输的时间（时间戳A）。测试设备中的接收器逻辑必须识别帧流中的标签信息，并记录接收标签帧的时间（时间戳B）。
The latency is timestamp B minus timestamp A as per the relevant definition frm RFC 1242, namely latency as defined for store and forward devices or latency as defined for bit forwarding devices.
根据相关定义frm RFC 1242，延迟是时间戳B减去时间戳A，即为存储和转发设备定义的延迟或为比特转发设备定义的延迟。
The test MUST be repeated at least 20 times with the reported value being the average of the recorded values.
试验必须重复至少20次，报告值为记录值的平均值。
This test SHOULD be performed with the test frame addressed to the same destination as the rest of the data stream and also with each of the test frames addressed to a new destination network.
该测试应在测试帧寻址到与数据流其余部分相同的目的地，以及每个测试帧寻址到新的目的地网络的情况下执行。
Reporting format: The report MUST state which definition of latency (from RFC 1242) was used for this test. The latency results SHOULD be reported in the format of a table with a row for each of the tested frame sizes. There SHOULD be columns for the frame size, the rate at which the latency test was run for that frame size, for the media types tested, and for the resultant latency values for each type of data stream tested.
报告格式：报告必须说明此测试使用的延迟定义（来自RFC 1242）。延迟结果应以表格的形式报告，每个测试帧大小对应一行。对于帧大小、针对该帧大小运行延迟测试的速率、测试的媒体类型以及测试的每种数据流类型的结果延迟值，都应该有相应的列。
Objective: To determine the frame loss rate, as defined in RFC 1242, of a DUT throughout the entire range of input data rates and frame sizes.
目标：确定RFC 1242中定义的DUT在整个输入数据速率和帧大小范围内的帧丢失率。
Procedure: Send a specific number of frames at a specific rate through the DUT to be tested and count the frames that are transmitted by the DUT. The frame loss rate at each point is calculated using the following equation:
程序：通过待测DUT以特定速率发送特定数量的帧，并对DUT发送的帧进行计数。使用以下公式计算每个点的帧丢失率：
( ( input_count - output_count ) * 100 ) / input_count
( ( input_count - output_count ) * 100 ) / input_count
The first trial SHOULD be run for the frame rate that corresponds to 100% of the maximum rate for the frame size on the input media. Repeat the procedure for the rate that corresponds to 90% of the maximum rate used and then for 80% of this rate. This sequence SHOULD be continued (at reducing 10% intervals) until there are two successive trials in which no frames are lost. The maximum granularity of the trials MUST be 10% of the maximum rate, a finer granularity is encouraged.
第一次测试的帧速率应为输入媒体上帧大小最大速率的100%。对与所用最大速率的90%对应的速率重复该步骤，然后对该速率的80%重复该步骤。应继续此顺序（以减少10%的间隔），直到有两个连续的试验没有丢失帧。试验的最大粒度必须为最大速率的10%，建议使用更细的粒度。
Reporting format: The results of the frame loss rate test SHOULD be plotted as a graph. If this is done then the X axis MUST be the input frame rate as a percent of the theoretical rate for the media at the specific frame size. The Y axis MUST be the percent loss at the particular input rate. The left end of the X axis and the bottom of the Y axis MUST be 0 percent; the right end of the X axis and the top of the Y axis MUST be 100 percent. Multiple lines on the graph MAY used to report the frame loss rate for different frame sizes, protocols, and types of data streams.
报告格式：帧丢失率测试结果应绘制为图表。如果这样做，则X轴必须是输入帧速率，以特定帧大小下媒体理论速率的百分比表示。Y轴必须是特定输入速率下的损耗百分比。X轴左端和Y轴底部必须为0%；X轴的右端和Y轴的顶部必须为100%。图形上的多行可用于报告不同帧大小、协议和数据流类型的帧丢失率。
Note: See section 18 for the maximum frame rates that SHOULD be used.
注：有关应使用的最大帧速率，请参见第18节。
Objective: To characterize the ability of a DUT to process back-to-back frames as defined in RFC 1242.
目的：描述DUT处理RFC1242中定义的背对背帧的能力。
Procedure: Send a burst of frames with minimum inter-frame gaps to the DUT and count the number of frames forwarded by the DUT. If the count of transmitted frames is equal to the number of frames forwarded the length of the burst is increased and the test is rerun. If the number of forwarded frames is less than the number transmitted, the length of the burst is reduced and the test is rerun.
程序：向DUT发送具有最小帧间间隙的帧突发，并统计DUT转发的帧数。如果发送的帧数等于转发的帧数，则突发的长度增加，并重新运行测试。如果转发的帧数小于发送的帧数，则突发的长度减小，并重新运行测试。
The back-to-back value is the number of frames in the longest burst that the DUT will handle without the loss of any frames. The trial length MUST be at least 2 seconds and SHOULD be repeated at least 50 times with the average of the recorded values being reported.
背对背值是DUT将在不丢失任何帧的情况下处理的最长突发中的帧数。试验长度必须至少为2秒，并且应重复至少50次，并报告记录值的平均值。
Reporting format: The back-to-back results SHOULD be reported in the format of a table with a row for each of the tested frame sizes. There SHOULD be columns for the frame size and for the resultant average frame count for each type of data stream tested. The standard deviation for each measurement MAY also be reported.
报告格式：应以表格的格式报告背对背的结果，表格中的每一个测试帧大小都有一行。对于测试的每种类型的数据流，应该有用于帧大小和结果平均帧计数的列。还可以报告每次测量的标准偏差。
Objective: To characterize the speed at which a DUT recovers from an overload condition.
目的：描述DUT从过载状态恢复的速度。
Procedure: First determine the throughput for a DUT at each of the listed frame sizes.
程序：首先确定每个列出的帧大小下DUT的吞吐量。
Send a stream of frames at a rate 110% of the recorded throughput rate or the maximum rate for the media, whichever is lower, for at least 60 seconds. At Timestamp A reduce the frame rate to 50% of the above rate and record the time of the last frame lost (Timestamp B). The system recovery time is determined by subtracting Timestamp B from Timestamp A. The test SHOULD be repeated a number of times and the average of the recorded values being reported.
以记录吞吐量的110%或媒体的最大速率（以较低者为准）发送帧流至少60秒。在时间戳A处，将帧速率降低到上述速率的50%，并记录最后一帧丢失的时间（时间戳B）。通过从时间戳A中减去时间戳B来确定系统恢复时间。应重复多次测试，并报告记录值的平均值。
Reporting format: The system recovery results SHOULD be reported in the format of a table with a row for each of the tested frame sizes. There SHOULD be columns for the frame size, the frame rate used as the throughput rate for each type of data stream tested, and for the measured recovery time for each type of data stream tested.
报告格式：系统恢复结果应以表格的格式报告，表格中的每一个测试帧大小对应一行。对于帧大小、用作测试的每种类型的数据流的吞吐量的帧速率以及测试的每种类型的数据流的测量恢复时间，应该有列。
Objective: To characterize the speed at which a DUT recovers from a device or software reset.
目标：描述DUT从设备或软件复位中恢复的速度。
Procedure: First determine the throughput for the DUT for the minimum frame size on the media used in the testing.
程序：首先确定测试中使用的介质上最小帧大小的DUT吞吐量。
Send a continuous stream of frames at the determined throughput rate for the minimum sized frames. Cause a reset in the DUT. Monitor the output until frames begin to be forwarded and record the time that the last frame (Timestamp A) of the initial stream and the first frame of the new stream (Timestamp B) are received. A power interruption reset test is performed as above except that the power to the DUT should be interrupted for 10 seconds in place of causing a reset.
以确定的最小大小帧的吞吐量发送连续的帧流。使DUT复位。监视输出，直到帧开始转发，并记录接收到初始流的最后一帧（时间戳A）和新流的第一帧（时间戳B）的时间。除DUT的电源应中断10秒以代替复位外，电源中断复位测试如上所述进行。
This test SHOULD only be run using frames addressed to networks directly connected to the DUT so that there is no requirement to delay until a routing update is received.
该测试应仅使用直接连接到DUT的网络的帧来运行，以便在收到路由更新之前不需要延迟。
The reset value is obtained by subtracting Timestamp A from Timestamp B.
通过从时间戳B中减去时间戳A来获得重置值。
Hardware and software resets, as well as a power interruption SHOULD be tested.
应测试硬件和软件复位以及电源中断。
Reporting format: The reset value SHOULD be reported in a simple set of statements, one for each reset type.
报告格式：应在一组简单的语句中报告重置值，每种重置类型一个。
Security issues are not addressed in this document.
本文件未涉及安全问题。
Scott Bradner Harvard University 1350 Mass. Ave, room 813 Cambridge, MA 02138
斯科特·布拉德纳哈佛大学1350弥撒。马萨诸塞州剑桥大街813室，邮编02138
Phone: +1 617 495-3864
Fax: +1 617 496-8500
EMail: sob@harvard.edu
Phone: +1 617 495-3864
Fax: +1 617 496-8500
EMail: sob@harvard.edu
Jim McQuaid NetScout Systems 4 Westford Tech Park Drive Westford, MA 01886
Jim McQuaid NetScout Systems 4 Westford科技园大道Westford，马萨诸塞州01886
Phone: +1 978 614-4116
Fax: +1 978 614-4004
EMail: mcquaidj@netscout.com
Phone: +1 978 614-4116
Fax: +1 978 614-4004
EMail: mcquaidj@netscout.com
Appendix A: Testing Considerations
附录A：测试注意事项
This appendix discusses certain issues in the benchmarking methodology where experience or judgment may play a role in the tests selected to be run or in the approach to constructing the test with a particular DUT. As such, this appendix MUST not be read as an amendment to the methodology described in the body of this document but as a guide to testing practice.
本附录讨论了基准测试方法中的某些问题，其中经验或判断可能在选择运行的测试中发挥作用，或在使用特定DUT构建测试的方法中发挥作用。因此，本附录不得理解为对本文件正文中所述方法的修订，而应理解为测试实践指南。
1. Typical testing practice has been to enable all protocols to be tested and conduct all testing with no further configuration of protocols, even though a given set of trials may exercise only one protocol at a time. This minimizes the opportunities to "tune" a DUT for a single protocol.
1. 典型的测试实践是允许测试所有协议，并在不进一步配置协议的情况下执行所有测试，即使给定的一组试验一次只能执行一个协议。这将最小化为单个协议“调优”DUT的机会。
2. The least common denominator of the available filter functions should be used to ensure that there is a basis for comparison between vendors. Because of product differences, those conducting and evaluating tests must make a judgment about this issue.
2. 应使用可用过滤函数的最小公分母，以确保供应商之间有比较的基础。由于产品的差异，进行和评估测试的人员必须对此问题做出判断。
3. Architectural considerations may need to be considered. For example, first perform the tests with the stream going between ports on the same interface card and the repeat the tests with the stream going into a port on one interface card and out of a port on a second interface card. There will almost always be a best case and worst case configuration for a given DUT architecture.
3. 可能需要考虑架构方面的考虑。例如，首先使用流在同一接口卡上的端口之间执行测试，然后使用流进入一个接口卡上的端口并从第二个接口卡上的端口流出重复测试。对于给定的DUT架构，几乎总是存在最佳和最坏情况配置。
4. Testing done using traffic streams consisting of mixed protocols has not shown much difference between testing with individual protocols. That is, if protocol A testing and protocol B testing give two different performance results, mixed protocol testing appears to give a result which is the average of the two.
4. 使用由混合协议组成的流量流进行的测试并没有显示出使用单个协议进行测试之间的太大差异。也就是说，如果协议A测试和协议B测试给出两个不同的性能结果，则混合协议测试给出的结果似乎是这两个结果的平均值。
5. Wide Area Network (WAN) performance may be tested by setting up two identical devices connected by the appropriate short- haul versions of the WAN modems. Performance is then measured between a LAN interface on one DUT to a LAN interface on the other DUT.
5. 广域网（WAN）性能可以通过设置两个相同的设备来测试，这两个设备由广域网调制解调器的适当短途版本连接。然后在一个DUT上的LAN接口与另一个DUT上的LAN接口之间测量性能。
The maximum frame rate to be used for LAN-WAN-LAN configurations is a judgment that can be based on known characteristics of the overall system including compression effects, fragmentation, and gross link speeds. Practice suggests that the rate should be at least 110% of the slowest link speed. Substantive issues of testing compression itself are beyond the scope of this document.
LAN-WAN-LAN配置使用的最大帧速率是一种判断，可以基于整个系统的已知特性，包括压缩效果、碎片和总链路速度。实践表明，速率应至少为最慢链路速度的110%。测试压缩本身的实质性问题超出了本文档的范围。
Appendix B: Maximum frame rates reference
附录B：最大帧速率参考
(Provided by Roger Beeman, Cisco Systems)
（由思科系统公司Roger Beeman提供）
Size Ethernet 16Mb Token Ring FDDI (bytes) (pps) (pps) (pps)
大小以太网16Mb令牌环FDDI（字节）（pps）（pps）（pps）
64 14880 24691 152439 128 8445 13793 85616 256 4528 7326 45620 512 2349 3780 23585 768 1586 2547 15903 1024 1197 1921 11996 1280 961 1542 9630 1518 812 1302 8138
64 14880 24691 152439 128 8445 13793 85616 256 4528 7326 45620 512 2349 3780 23585 768 1586 2547 15903 1024 1197 1921 11996 1280 961 1542 9630 1518 812 1302 8138
Ethernet size Preamble 64 bits Frame 8 x N bits Gap 96 bits
以太网大小前导码64位帧8 x N位间隙96位
16Mb Token Ring size SD 8 bits AC 8 bits FC 8 bits DA 48 bits SA 48 bits RI 48 bits ( 06 30 00 12 00 30 ) SNAP DSAP 8 bits SSAP 8 bits Control 8 bits Vendor 24 bits Type 16 bits Data 8 x ( N - 18) bits FCS 32 bits ED 8 bits FS 8 bits
16Mb令牌环大小SD 8位AC 8位FC 8位DA 48位SA 48位RI 48位（06 30 00 12 00 30）SNAP DSAP 8位SSAP 8位控制8位供应商24位类型16位数据8 x（N-18）位FCS 32位ED 8位FS 8位
Tokens or idles between packets are not included
不包括数据包之间的令牌或空闲
FDDI size Preamble 64 bits SD 8 bits FC 8 bits DA 48 bits SA 48 bits SNAP
FDDI大小前导码64位SD 8位FC 8位DA 48位SA 48位SNAP
DSAP 8 bits SSAP 8 bits Control 8 bits Vendor 24 bits Type 16 bits Data 8 x ( N - 18) bits FCS 32 bits ED 4 bits FS 12 bits
DSAP 8位SSAP 8位控制8位供应商24位类型16位数据8 x（N-18）位FCS 32位ED 4位FS 12位
Appendix C: Test Frame Formats
附录C：测试帧格式
This appendix defines the frame formats that may be used with these tests. It also includes protocol specific parameters for TCP/IP over Ethernet to be used with the tests as an example.
本附录定义了可用于这些测试的框架格式。它还包括TCP/IP over Ethernet的特定于协议的参数，以测试为例。
The general logic used in the selection of the parameters and the design of the frame formats is explained for each case within the TCP/IP section. The same logic has been used in the other sections. Comments are used in these sections only if there is a protocol specific feature to be explained. Parameters and frame formats for additional protocols can be defined by the reader by using the same logic.
TCP/IP部分针对每种情况解释了参数选择和帧格式设计中使用的一般逻辑。其他章节也采用了相同的逻辑。只有在需要解释特定于协议的功能时，才会在这些章节中使用注释。读卡器可以使用相同的逻辑定义附加协议的参数和帧格式。
The following section deals with the TCP/IP protocol suite.
以下部分介绍TCP/IP协议套件。
C.2.1 Frame Type.
C.2.1 框架类型。
An application level datagram echo request is used for the test data frame in the protocols that support such a function. A datagram protocol is used to minimize the chance that a router might expect a specific session initialization sequence, as might be the case for a reliable stream protocol. A specific defined protocol is used because some routers verify the protocol field and refuse to forward unknown protocols.
应用程序级数据报回显请求用于支持此功能的协议中的测试数据帧。数据报协议用于最小化路由器可能期望特定会话初始化序列的可能性，就像可靠流协议一样。使用特定定义的协议是因为某些路由器验证协议字段并拒绝转发未知协议。
For TCP/IP a UDP Echo Request is used.
对于TCP/IP，使用UDP回显请求。
Two sets of addresses must be defined: first the addresses assigned to the router ports, and second the address that are to be used in the frames themselves and in the routing updates.
必须定义两组地址：第一组是分配给路由器端口的地址，第二组是要在帧本身和路由更新中使用的地址。
The network addresses 192.18.0.0 through 198.19.255.255 are have been assigned to the BMWG by the IANA for this purpose. This assignment was made to minimize the chance of conflict in case a testing device were to be accidentally connected to part of the Internet. The specific use of the addresses is detailed below.
为此，IANA已将网络地址192.18.0.0至198.19.255.255分配给BMWG。这项任务是为了在测试设备意外连接到部分互联网的情况下尽量减少冲突的可能性。地址的具体用途如下所述。
Half of the ports on a multi-port router are referred to as "input" ports and the other half as "output" ports even though some of the tests use all ports both as input and output. A contiguous series of IP Class C network addresses from 198.18.1.0 to 198.18.64.0 have been assigned for use on the "input" ports. A second series from 198.19.1.0 to 198.19.64.0 have been assigned for use on the "output" ports. In all cases the router port is node 1 on the appropriate network. For example, a two port DUT would have an IP address of 198.18.1.1 on one port and 198.19.1.1 on the other port.
多端口路由器上的一半端口称为“输入”端口，另一半称为“输出”端口，即使某些测试将所有端口都用作输入和输出。从198.18.1.0到198.18.64.0的一系列连续的IP C类网络地址已分配用于“输入”端口。从198.19.1.0到198.19.64.0的第二个系列已分配用于“输出”端口。在所有情况下，路由器端口都是相应网络上的节点1。例如，双端口DUT的一个端口的IP地址为198.18.1.1，另一个端口的IP地址为198.19.1.1。
Some of the tests described in the methodology memo make use of an SNMP management connection to the DUT. The management access address for the DUT is assumed to be the first of the "input" ports (198.18.1.1).
方法备忘录中描述的一些测试使用到DUT的SNMP管理连接。DUT的管理访问地址假定为第一个“输入”端口（198.18.1.1）。
Some of the described tests assume adjacent network routing (the reboot time test for example). The IP address used in the test frame is that of node 2 on the appropriate Class C network. (198.19.1.2 for example)
所描述的一些测试假设相邻网络路由（例如重新启动时间测试）。测试帧中使用的IP地址是相应C类网络上节点2的IP地址。（例如198.19.1.2）
If the test involves non-adjacent network routing the phantom routers are located at node 10 of each of the appropriate Class C networks. A series of Class C network addresses from 198.18.65.0 to 198.18.254.0 has been assigned for use as the networks accessible through the phantom routers on the "input" side of DUT. The series of Class C networks from 198.19.65.0 to 198.19.254.0 have been assigned to be used as the networks visible through the phantom routers on the "output" side of the DUT.
如果测试涉及非相邻网络路由，则幻影路由器位于每个适当C类网络的节点10处。已分配从198.18.65.0到198.18.254.0的一系列C类网络地址，用于通过DUT“输入”侧的幻影路由器访问的网络。从198.19.65.0到198.19.254.0的C类网络系列被指定为通过DUT“输出”侧的幻影路由器可见的网络。
The update interval for each routing protocol is may have to be determined by the specifications of the individual protocol. For IP RIP, Cisco IGRP and for OSPF a routing update frame or frames should precede each stream of test frames by 5 seconds. This frequency is sufficient for trial durations of up to 60 seconds. Routing updates must be mixed with the stream of test frames if longer trial periods are selected. The frequency of updates should be taken from the following table.
每个路由协议的更新间隔可能必须由各个协议的规范确定。对于IP RIP、Cisco IGRP和OSPF，路由更新帧应在每个测试帧流之前5秒。该频率足以进行长达60秒的试验。如果选择更长的试用期，则路由更新必须与测试帧流混合。更新频率应取自下表。
IP-RIP 30 sec IGRP 90 sec OSPF 90 sec
IP-RIP 30秒IGRP 90秒OSPF 90秒
In most protocols a procedure is used to determine the mapping between the protocol node address and the MAC address. The Address Resolution Protocol (ARP) is used to perform this function in TCP/IP. No such procedure is required in XNS or IPX because the MAC address is used as the protocol node address.
在大多数协议中，程序用于确定协议节点地址和MAC地址之间的映射。地址解析协议（ARP）用于在TCP/IP中执行此功能。XNS或IPX中不需要这样的过程，因为MAC地址用作协议节点地址。
In the ideal case the tester would be able to respond to ARP requests from the DUT. In cases where this is not possible an ARP request should be sent to the router's "output" port. This request should be seen as coming from the immediate destination of the test frame stream. (i.e. the phantom router (Figure 2) or the end node if adjacent network routing is being used.) It is assumed that the router will cache the MAC address of the requesting device. The ARP request should be sent 5 seconds before the test frame stream starts in each trial. Trial lengths of longer than 50 seconds may require that the router be configured for an extended ARP timeout.
在理想情况下，测试仪将能够响应来自DUT的ARP请求。在不可能的情况下，应将ARP请求发送到路由器的“输出”端口。该请求应被视为来自测试帧流的直接目的地。（即幻影路由器（图2）或终端节点（如果使用相邻网络路由）。假定路由器将缓存请求设备的MAC地址。ARP请求应在每次试验中测试帧流开始前5秒发送。超过50秒的试验长度可能要求路由器配置为延长ARP超时。
+--------+ +------------+
| | | phantom |------ P LAN
A
IN A------| DUT |------------| |------ P LAN
B
| | OUT A | router |------ P LAN
C
+--------+ +------------+
+--------+ +------------+
| | | phantom |------ P LAN
A
IN A------| DUT |------------| |------ P LAN
B
| | OUT A | router |------ P LAN
C
+--------+ +------------+
Figure 2
图2
In the case where full routing is being used
在使用完整路由的情况下
If the test does not involve adjacent net routing the tester must supply proper routing information using a routing update. A single routing update is used before each trial on each "destination" port (see section C.24). This update includes the network addresses that are reachable through a phantom router on the network attached to the port. For a full mesh test, one destination network address is present in the routing update for each of the "input" ports. The test stream on each "input" port consists of a repeating sequence of frames, one to each of the "output" ports.
如果测试不涉及相邻网络路由，测试仪必须使用路由更新提供正确的路由信息。在每个“目的地”端口上进行每次试验之前，使用一次路由更新（见第C.24节）。此更新包括可通过连接到端口的网络上的虚拟路由器访问的网络地址。对于全网状测试，每个“输入”端口的路由更新中都有一个目标网络地址。每个“输入”端口上的测试流由帧的重复序列组成，每个“输出”端口对应一个帧。
The management overhead test uses SNMP to query a set of variables that should be present in all DUTs that support SNMP. The variables for a single interface only are read by an NMS at the appropriate intervals. The list of variables to retrieve follow:
管理开销测试使用SNMP查询所有支持SNMP的DUT中应存在的一组变量。NMS仅在适当的时间间隔读取单个接口的变量。要检索的变量列表如下所示：
sysUpTime ifInOctets ifOutOctets ifInUcastPkts ifOutUcastPkts
系统正常运行时间ifInOctets IFOUTPKTS IFOUTPKTS IFOUTUCASTKTS IFOUTPKTS
The test frame is an UDP Echo Request with enough data to fill out the required frame size. The data should not be all bits off or all bits on since these patters can cause a "bit stuffing" process to be used to maintain clock synchronization on WAN links. This process will result in a longer frame than was intended.
测试帧是一个UDP回显请求，具有足够的数据来填充所需的帧大小。数据不应全部关闭或全部打开，因为这些模式可能导致使用“位填充”过程来维持WAN链路上的时钟同步。此过程将产生比预期更长的帧。
Each of the frames below are described for the 1st pair of DUT ports, i.e. "input" port #1 and "output" port #1. Addresses must be changed if the frame is to be used for other ports.
下面的每一帧都描述了第一对DUT端口，即“输入”端口1和“输出”端口1。如果帧要用于其他端口，则必须更改地址。
ARP Request on Ethernet
以太网上的ARP请求
-- DATAGRAM HEADER offset data (hex) description 00 FF FF FF FF FF FF dest MAC address send to broadcast address 06 xx xx xx xx xx xx set to source MAC address 12 08 06 ARP type 14 00 01 hardware type Ethernet = 1 16 08 00 protocol type IP = 800 18 06 hardware address length 48 bits on Ethernet 19 04 protocol address length 4 octets for IP 20 00 01 opcode request = 1 22 xx xx xx xx xx xx source MAC address 28 xx xx xx xx source IP address 32 FF FF FF FF FF FF requesting DUT's MAC address 38 xx xx xx xx DUT's IP address
--数据报报头偏移数据（十六进制）描述00 FF FF FF FF FF目标MAC地址发送到广播地址06 xx xx xx xx xx设置到源MAC地址12 08 06 ARP类型14 00 01硬件类型以太网=1 16 08 00协议类型IP=800 18 06硬件地址长度48位以太网19 04协议地址长度4个八位字节IP 20 00 01操作码请求=1 22 xx xx xxxx xx源MAC地址28 xx xx xx xx源IP地址32 FF FF FF FF FF FF请求被测设备的MAC地址38 xx xx xx被测设备的IP地址
-- DATAGRAM HEADER offset data (hex) description 00 FF FF FF FF FF FF dest MAC address is broadcast 06 xx xx xx xx xx xx source hardware address 12 08 00 type
--数据报报头偏移数据（十六进制）说明00 FF FF FF FF FF dest MAC地址为广播06 xx xx xx xx xx xx源硬件地址12 08 00类型
-- IP HEADER 14 45 IP version - 4, header length (4 byte units) - 5 15 00 service field 16 00 EE total length 18 00 00 ID 20 40 00 flags (3 bits) 4 (do not fragment), fragment offset-0 22 0A TTL 23 11 protocol - 17 (UDP) 24 C4 8D header checksum 26 xx xx xx xx source IP address 30 xx xx xx destination IP address 33 FF host part = FF for broadcast
--IP报头14 45 IP版本-4，报头长度（4字节单位）-5 15 00服务字段16 00 EE总长度18 00 ID 20 40 00标志（3位）4（不分段），分段偏移量-0 22 0A TTL 23 11协议-17（UDP）24 C4 8D报头校验和26 xx xx xx xx xx xx xx xx源IP地址30 xx xx xx xx xx目标IP地址33 FF主机部分=FF用于广播
-- UDP HEADER 34 02 08 source port 208 = RIP 36 02 08 destination port 208 = RIP 38 00 DA UDP message length 40 00 00 UDP checksum
--UDP报头34 02 08源端口208=RIP 36 02 08目标端口208=RIP 38 00 DA UDP消息长度40 00 UDP校验和
-- RIP packet 42 02 command = response 43 01 version = 1 44 00 00 0
--RIP数据包42 02命令=响应43 01版本=1 44 00 0
-- net 1 46 00 02 family = IP 48 00 00 0 50 xx xx xx net 1 IP address 53 00 net not node 54 00 00 00 00 0 58 00 00 00 00 0 62 00 00 00 07 metric 7
--网络1 46 00 02系列=IP 48 00 00 0 50 xx xx xx网络1 IP地址53 00网络非节点54 00 00 00 00 0 58 00 00 00 00 00 0 62 00 00 07公制7
-- net 2 66 00 02 family = IP 68 00 00 0 70 xx xx xx net 2 IP address
--网络2 66 00 02系列=IP 68 00 00 0 70 xx xx xx网络2 IP地址
73 00 net not node 74 00 00 00 00 0 78 00 00 00 00 0 82 00 00 00 07 metric 7
73 00净非节点74 00 00 00 78 00 00 00 00 82 00 00 00 07公制7
-- net 3 86 00 02 family = IP 88 00 00 0 90 xx xx xx net 3 IP address 93 00 net not node 94 00 00 00 00 0 98 00 00 00 00 0 102 00 00 00 07 metric 7
--网络3 86 00 02系列=IP 88 00 00 90 xx xx网络3 IP地址93 00网络非节点94 00 00 00 00 00 98 00 00 00 00 00 00 00 0 102 00 00 00 07公制7
-- net 4 106 00 02 family = IP 108 00 00 0 110 xx xx xx net 4 IP address 113 00 net not node 114 00 00 00 00 0 118 00 00 00 00 0 122 00 00 00 07 metric 7
--网络4 106 00 02系列=IP 108 00 00 0 110 xx xx网络4 IP地址113 00网络非节点114 00 00 00 0 118 00 00 00 00 00 0 122 00 00 00 07公制7
-- net 5 126 00 02 family = IP 128 00 00 0 130 00 net 5 IP address 133 00 net not node 134 00 00 00 00 0 138 00 00 00 00 0 142 00 00 00 07 metric 7
--网络5 126 00 02系列=IP 128 00 00 0 130 00网络5 IP地址133 00网络非节点134 00 00 00 00 00 00 00 0 142 00 00 00 00 07公制7
-- net 6 146 00 02 family = IP 148 00 00 0 150 xx xx xx net 6 IP address 153 00 net not node 154 00 00 00 00 0 158 00 00 00 00 0 162 00 00 00 07 metric 7
--网络6 146 00 02系列=IP 148 00 00 0 150 xx xx xx网络6 IP地址153 00网络非节点154 00 00 00 00 0 15800 00 00 00 0 16200 00 00 07公制7
To be defined.
待定义。
UDP echo request on Ethernet
以太网上的UDP回送请求
-- DATAGRAM HEADER offset data (hex) description 00 xx xx xx xx xx xx set to dest MAC address 06 xx xx xx xx xx xx set to source MAC address 12 08 00 type
--数据报报头偏移数据（十六进制）说明00 xx xx xx xx xx xx xx xx设置为目标MAC地址06 xx xx xx xx xx xx xx xx设置为源MAC地址12 08 00类型
-- IP HEADER
14 45 IP version - 4 header length 5 4
byte units
15 00 TOS
16 00 2E total length*
18 00 00 ID
20 00 00 flags (3 bits) - 0 fragment
offset-0
22 0A TTL
23 11 protocol - 17 (UDP)
24 C4 8D header checksum*
26 xx xx xx xx set to source IP address**
30 xx xx xx xx set to destination IP address**
-- IP HEADER
14 45 IP version - 4 header length 5 4
byte units
15 00 TOS
16 00 2E total length*
18 00 00 ID
20 00 00 flags (3 bits) - 0 fragment
offset-0
22 0A TTL
23 11 protocol - 17 (UDP)
24 C4 8D header checksum*
26 xx xx xx xx set to source IP address**
30 xx xx xx xx set to destination IP address**
-- UDP HEADER 34 C0 20 source port 36 00 07 destination port 07 = Echo 38 00 1A UDP message length* 40 00 00 UDP checksum
--UDP报头34 C0 20源端口36 00 07目标端口07=Echo 38 00 1A UDP消息长度*40 00 00 UDP校验和
-- UDP DATA
42 00 01 02 03 04 05 06 07 some data***
50 08 09 0A 0B 0C 0D 0E 0F
-- UDP DATA
42 00 01 02 03 04 05 06 07 some data***
50 08 09 0A 0B 0C 0D 0E 0F
* - change for different length frames
* -更改不同长度的帧
** - change for different logical streams
** - change for different logical streams
*** - fill remainder of frame with incrementing octets,
repeated if required by frame length
*** - fill remainder of frame with incrementing octets,
repeated if required by frame length
Values to be used in Total Length and UDP message length fields:
要在总长度和UDP消息长度字段中使用的值：
frame size total length UDP message length 64 00 2E 00 1A 128 00 6E 00 5A 256 00 EE 00 9A 512 01 EE 01 9A 768 02 EE 02 9A 1024 03 EE 03 9A 1280 04 EE 04 9A 1518 05 DC 05 C8
帧大小总长度UDP消息长度64 00 2E 00 1A 128 00 6E 00 5A 256 00 EE 00 9A 512 01 EE 01 9A 768 02 EE 02 9A 1024 03 EE 03 9A 1280 04 EE 04 9A 1518 05 DC 05 C8
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。