- [1.2. Scope](#Scope)
- [1.3. References](#References)
+
- [2. Details of the Level Test Design](#DetailsOfTheLevelTestDesign)
- [2.1. Features to be tested](#FeaturesToBeTested)
- [2.2. Approach](#Approach)
- [2.4. Feature pass/fail criteria](#PassFail)
- [2.5. Test deliverables](#TestDeliverables)
+
- [3. General](#General)
- [3.1. Glossary](#Glossary)
- [3.2. Document change procedures and history](#History)
- Low: May or may not be implemented at all.
#####DUT Setup
- The DUT should be configured to it's "default" state. The DUT's configuration or set-up must not change between tests in any way other than what is required to do the test. All supported protocols must be configured and enabled for each test set up.
+ The DUT should be configured to its "default" state. The DUT's configuration or set-up must not change between tests in any way other than what is required to do the test. All supported protocols must be configured and enabled for each test set up.
#####Port Configuration
The DUT should be configured with n ports where n is a multiple of 2. Half of the ports on the DUT should be used as ingress ports and the other half of the ports on the DUT should be used as egress ports. Where a DUT has more than 2 ports, the ingress data streams should be set-up so that they transmit packets to the egress ports in sequence so that there is an even distribution of traffic across ports. For example, if a DUT has 4 ports 0(ingress), 1(ingress), 2(egress) and 3(egress), the traffic stream directed at port 0 should output a packet to port 2 followed by a packet to port 3. The traffic stream directed at port 1 should also output a packet to port 2 followed by a packet to port 3.
#####Frame formats
- Layer 2 (data link layer) protocols:
+ Layer 2 (data link layer) protocols:
- - Ethernet II
+ - Ethernet II
- <pre><code>
+-----------------------------+-----------------------------------------------------------------------+---------+
| Ethernet Header | Payload |Check Sum|
|___________________________| |_____________________________________________________________________| |_______|
14 Bytes 46 - 1500 Bytes 4 Bytes
- </code></pre>
+ </code></pre>
- Layer 3 (network layer) protocols:
+ Layer 3 (network layer) protocols:
- - IPv4
+ - IPv4
- <pre><code>
+-----------------------------+-------------------------------------+---------------------------------+---------+
| Ethernet Header | IP Header | Payload |Check Sum|
|___________________________| |___________________________________| |_______________________________| |_______|
14 Bytes 20 Bytes 26 - 1480 Bytes 4 Bytes
- </code></pre>
+ </code></pre>
-- IPv6
+ - IPv6
- <pre><code>
+-----------------------------+-------------------------------------+---------------------------------+---------+
| Ethernet Header | IP Header | Payload |Check Sum|
|___________________________| |___________________________________| |_______________________________| |_______|
14 Bytes 40 Bytes 26 - 1460 Bytes 4 Bytes
- </code></pre>
-
- Layer 4 (transport layer) protocols:
+ </code></pre>
- - TCP
- - UDP
- - SCTP
+ Layer 4 (transport layer) protocols:
+ - TCP
+ - UDP
+ - SCTP
- <pre><code>
+-----------------------------+-------------------------------------+-----------------+---------------+---------+
| Ethernet Header | IP Header | Layer 4 Header | Payload |Check Sum|
|___________________________| |___________________________________| |_______________| |_____________| |_______|
14 Bytes 20 Bytes 20 Bytes 6 - 1460 Bytes 4 Bytes
- </code></pre>
+ </code></pre>
- Layer 5 (application layer) protocols:
+ Layer 5 (application layer) protocols:
- - RTP
- - GTP
+ - RTP
+ - GTP
- <pre><code>
+-----------------------------+-------------------------------------+-----------------+---------------+---------+
| Ethernet Header | IP Header | Layer 4 Header | Payload |Check Sum|
|___________________________| |___________________________________| |_______________| |_____________| |_______|
14 Bytes 20 Bytes 20 Bytes Min 6 Bytes 4 Bytes
- </code></pre>
+ </code></pre>
+
+ #####Packet Throughput
+ There is a difference between an Ethernet frame, an IP packet, and a UDP datagram. In the seven-layer OSI model of computer networking, packet refers to a data unit at layer 3 (network layer). The correct term for a data unit at layer 2 (data link layer) is a frame, and at layer 4 (transport layer) is a segment or datagram.
+
+ Important concepts related to 10GbE performance are frame rate and throughput. The MAC bit rate of 10GbE, defined in the IEEE standard 802 .3ae, is 10 billion bits per second. Frame rate is based on the bit rate and frame format definitions. Throughput, defined in IETF RFC 1242, is the highest rate at which the system under test can forward the offered load, without loss.
+
+ The frame rate for 10GbE is determined by a formula that divides the 10 billion bits per second by the preamble + frame length + inter-frame gap.
+
+ The maximum frame rate is calculated using the minimum values of the following parameters, as described in the IEEE 802 .3ae standard:
+
+ - Preamble: 8 bytes * 8 = 64 bits
+ - Frame Length: 64 bytes (minimum) * 8 = 512 bits
+ - Inter-frame Gap: 12 bytes (minimum) * 8 = 96 bits
+
+ Therefore, Maximum Frame Rate (64B Frames)
+
+ = MAC Transmit Bit Rate / (Preamble + Frame Length + Inter-frame Gap)
+
+ = 10,000,000,000 / (64 + 512 + 96)
+
+ = 10,000,000,000 / 672
+
+ = 14,880,952.38 frame per second (fps)
+
+ #####RFC 1242 Benchmarking Terminology for Network Interconnection Devices
+ RFC 1242 defines the terminology that is used in describing performance benchmarking tests and their results. Definitions and discussions covered include: Back-to-back, bridge, bridge/router, constant load, data link frame size, frame loss rate, inter frame gap, latency, and many more.
+
+ #####RFC 2544 Benchmarking Methodology for Network Interconnect Devices
+ RFC 2544 outlines a benchmarking methodology for network Interconnect Devices. The methodology results in performance metrics such as latency, frame loss percentage, and maximum data throughput.
+
+ In this document network “throughput” (measured in millions of frames per second) is based on RFC 2544, unless otherwise noted. Frame size refers to Ethernet frames ranging from smallest frames of 64 bytes to largest frames of 4K bytes.
+
+ Types of tests are:
+ 1. Throughput test defines the maximum number of frames per second that can be transmitted without any error.
+ 2. Latency test measures the time required for a frame to travel from the originating device through the network to the destination device. Please note that note RFC2544 Latency measurement will be superseded with a measurement of average latency over all successfully transferred packets or frames.
+ 3. Frame loss test measures the network’s response in overload conditions - a critical indicator of the network’s ability to support real-time applications in which a large amount of frame loss will rapidly degrade service quality.
+ 4. Burst test assesses the buffering capability of a switch. It measures the maximum number of frames received at full line rate before a frame is lost. In carrier Ethernet networks, this measurement validates the excess information rate (EIR) as defined in many SLAs.
+ 5. System recovery to characterize speed of recovery from an overload condition
+ 6. Reset to characterize speed of recovery from device or software reset. This type of test has been updated by [RFC6201] as such, the methodology defined by this specification will be that of RFC 6201.
+
+ Although not included in the defined RFC 2544 standard, another crucial measurement in Ethernet networking is packet delay variation. The definition set out by this specification comes from [RFC5481].
+
+ #####RFC 2285 Benchmarking Terminology for LAN Switching Devices
+ RFC 2285 defines the terminology that is used to describe the terminology for benchmarking a LAN switching device. It extends RFC 1242 and defines: DUTs, SUTs, Traffic orientation and distribution, bursts, loads, forwarding rates, etc.
+
+ #####RFC 2889 Benchmarking Methodology for LAN Switching
+ RFC 2889 outlines a benchmarking methodology for LAN switching, it extends RFC 2544. The outlined methodology gathers performance metrics for forwarding, congestion control, latency, address handling and finally filtering.
+
+ #####RFC 3918 Methodology for IP Multicast Benchmarking
+ RFC 3918 outlines a methodology for IP Multicast benchmarking.
+
+ #####RFC 4737 Packet Reordering Metrics
+ RFC 4737 describes metrics for identifying and counting re-ordered packets within a stream, and metrics to measure the extent each packet has been re-ordered.
+
+ #####RFC 5481 Packet Delay Variation Applicability Statement
+ RFC 5481 defined two common, but different forms of delay variation metrics, and compares the metrics over a range of networking circumstances and tasks. The most suitable form for vSwitch benchmarking is the "PDV" form.
+
+ #####RFC 6201 Device Reset Characterization
+ RFC 6201 extends the methodology for characterizing the speed of recovery of the DUT from device or software reset described in RFC 2544.
+
+
+<a name="TestIdentification"></a>
+###2.3. Test identification
+ <a name="ThroughputTests"></a>
+ ####2.3.1 Throughput tests
+ The following tests aim to determine the maximum forwarding rate that can be achieved with a virtual switch.
+
+ The following list is not exhaustive but should indicate the type of tests that should be required. It is expected that more will be added.
+
+ - #####Test ID: LTD.Throughput.RFC2544.PacketLossRatio
+
+ **Title**: RFC 2544 X% packet loss ratio Throughput and Latency Test
+
+ **Prerequisite Test**: N/A
+
+ **Priority**:
+
+ **Description**:
+
+ This test determines the DUT's maximum forwarding rate with X% traffic loss for a constant load (fixed length frames at a fixed interval time). The default loss percentages to be tested are:
+ - X = 0%
+ - X = 10^-7%
+
+ Note: Other values can be tested if required by the user.
+
+ The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams). The test can also be used to determine the average latency of the traffic.
+
+ Under the [RFC2544] test methodology, the test duration will include a number of trials; each trial should run for a minimum period of 60 seconds. A binary search methodology must be applied for each trial to obtain the final result.
+
+ **Expected Result**:
+ At the end of each trial, the presence or absence of loss determines the modification of offered load for the next trial, converging on a maximum rate, or [RFC2544] Throughput with X% loss. The Throughput load is re-used in related [RFC2544] tests and other tests.
+
+ **Metrics Collected**:
+
+ The following are the metrics collected for this test:
+
+ - The maximum forwarding rate in Frames Per Second (FPS) and Mbps of the DUT for each frame size with X% packet loss.
+ - The average latency of the traffic flow when passing through the DUT (if testing for latency, note that this average is different from the test specified in Section 26.3 of [RFC2544]).
+
+<br/>
+ - #####Test ID: LTD.Throughput.RFC2544.PacketLossRatioFrameModification
+ **Title**: RFC 2544 X% packet loss Throughput and Latency Test with packet modification
+
+ **Prerequisite Test**: N\A
+
+ **Priority**:
+
+ **Description**:
+
+ This test determines the DUT's maximum forwarding rate with X% traffic loss for a constant load (fixed length frames at a fixed interval time). The default loss percentages to be tested are:
+ - X = 0%
+ - X = 10^-7%
+
+ Note: Other values can be tested if required by the user.
+
+ The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams). The test can also be used to determine the average latency of the traffic.
+
+ Under the [RFC2544] test methodology, the test duration will include a number of trials; each trial should run for a minimum period of 60 seconds. A binary search methodology must be applied for each trial to obtain the final result.
+
+ During this test, the DUT must perform the following operations on the traffic flow:
+
+ - Perform packet parsing on the DUT's ingress port.
+ - Perform any relevant address look-ups on the DUT's ingress ports.
+ - Modify the packet header before forwarding the packet to the DUT's egress port. Packet modifications include:
+ - Modifying the Ethernet source or destination MAC address.
+ - Modifying/adding a VLAN tag.
+ - Modifying/adding a MPLS tag.
+ - Modifying the source or destination ip address.
+ - Modifying the TOS/DSCP field.
+ - Modifying the source or destination ports for UDP/TCP/SCTP (Recommended).
+ - Modifying the TTL.
+
+ **Expected Result**:
+ The Packet parsing/modifications require some additional degree of processing resource, therefore the [RFC2544] Throughput is expected to be somewhat lower than the Throughput level measured without additional steps. The reduction is expected to be greatest on tests with the smallest packet sizes (greatest header processing rates).
+
+ **Metrics Collected**:
+
+ The following are the metrics collected for this test:
+
+ - The maximum forwarding rate in Frames Per Second (FPS) and Mbps of the DUT for each frame size with X% packet loss and packet modification operations being performed by the DUT.
+ - The average latency of the traffic flow when passing through the DUT (if testing for latency, note that this average is different from the test specified in Section 26.3 of [RFC2544]).
+ - The [RFC5481] PDV form of delay variation on the traffic flow, using the 99th percentile.
+
+<br/>
+ - #####Test ID: LTD.Throughput.RFC2544.SystemRecoveryTime
+ **Title**: RFC 2544 System Recovery Time Test
+
+ **Prerequisite Test**: N\A
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to determine the length of time it takes the DUT to recover from an overload condition for a constant load (fixed length frames at a fixed interval time). The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams), traffic should be sent to the DUT under normal conditions. During the duration of the test and while the traffic flows are passing though the DUT, at least one situation leading to an overload condition for the DUT should occur. The time from the start of the overload condition to when the DUT returns to normal operations should be measured to determine recovery time. Prior to overloading the DUT, one should record the average latency for 100 packets forwarded through the DUT.
+
+ The suggested overload condition would be to transmit traffic at a very high frame rate to the DUT, for at least 60 seconds, then reduce the frame rate to the DUT by half; A number of time-stamps should be recorded:
+ - Record the time-stamp at which the frame rate was halved and record a second time-stamp at the time of the last frame lost. The recovery time is the difference between the two timestamps.
+ - Record the average Latency for 100 frames after the last frame loss and continue to record average latency measurements for every 100 frames, when latency returns to pre-overload levels record the time-stamp.
+
+ **Expected Result**:
+
+ **Metrics collected**
+
+ The following are the metrics collected for this test:
+
+ - The length of time it takes the DUT to recover from an overload condition.
+ - The length of time it takes the DUT to recover the average latency to pre-overload conditions.
- #####Packet Throughput
- There is a difference between an Ethernet frame, an IP packet, and a UDP datagram. In the seven-layer OSI model of computer networking, packet refers to a data unit at layer 3 (network layer). The correct term for a data unit at layer 2 (data link layer) is a frame, and at layer 4 (transport layer) is a segment or datagram.
+ **Deployment scenario**:
- Important concepts related to 10GbE performance are frame rate and throughput. The MAC bit rate of 10GbE, defined in the IEEE standard 802 .3ae, is 10 billion bits per second. Frame rate is based on the bit rate and frame format definitions. Throughput, defined in IETF RFC 1242, is the highest rate at which the system under test can forward the offered load, without loss.
+ - Physical → virtual switch → physical.
+
+<br/>
+ - #####Test ID: LTD.Throughput.RFC2544.BackToBackFrames
+ **Title**: RFC 2544 Back To Back Frames Test
+
+ **Prerequisite Test**: N\A
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to characterize the ability of the DUT to process back-to-back frames. For each frame size previously defined under [Default Test Parameters](#DefaultParams), a burst of traffic is sent to the DUT with the minimum inter-frame gap between each frame. If the number of received frames equals the number of frames that were transmitted, the burst size should be increased and traffic is sent to the DUT again. The value measured is the back-to-back value, that is the maximum burst size the DUT can handle without any frame loss.
+
+ **Expected Result**:
+
+ Tests of back-to-back frames with physical devices have produced unstable results in some cases. All tests should be repeated in multiple test sessions and results stability should be examined.
+
+ **Metrics collected**
+
+ The following are the metrics collected for this test:
+
+ - The back-to-back value, which is the the number of frames in the longest burst that the DUT will handle without the loss of any frames.
+
+ **Deployment scenario**:
+
+ - Physical → virtual switch → physical.
+
+<br/>
+ - #####Test ID: LTD.Throughput.RFC2544.Soak
+ **Title**: RFC 2544 X% packet loss Throughput Soak Test
+
+ **Prerequisite Test** LTD.Throughput.RFC2544.PacketLossRatio
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to understand the Throughput stability over an extended test duration in order to uncover any outliers. To allow for an extended test duration, the test should ideally run for 24 hours or, if this is not possible, for at least 6 hour. For this test, each frame size must be sent at the highest Throughput with X% packet loss, as determined in the prerequisite test. The default loss percentages to be tested are:
+ - X = 0%
+ - X = 10^-7%
+
+ Note: Other values can be tested if required by the user.
+
+ **Expected Result**:
+
+ **Metrics Collected**:
+
+ The following are the metrics collected for this test:
+
+ - Throughput stability of the DUT.
+ - Any outliers in the Throughput stability.
+ - Any unexpected variation in Throughput stability.
+
+<br/>
+
+ - #####Test ID: LTD.Throughput.RFC2544.SoakFrameModification
+ **Title**: RFC 2544 X% packet loss Throughput Soak Test with Frame Modification
+
+ **Prerequisite Test** LTD.Throughput.RFC2544.PacketLossRatioFrameModification
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to understand the Throughput stability over an extended test duration in order to uncover any outliers. To allow for an extended test duration, the test should ideally run for 24 hours or, if this is not possible, for at least 6 hour. For this test, each frame size must be sent at the highest Throughput with X% packet loss, as determined in the prerequisite test. The default loss percentages to be tested are:
+ - X = 0%
+ - X = 10^-7%
- The frame rate for 10GbE is determined by a formula that divides the 10 billion bits per second by the preamble + frame length + inter-frame gap.
+ Note: Other values can be tested if required by the user.
- The maximum frame rate is calculated using the minimum values of the following parameters, as described in the IEEE 802 .3ae standard:
+ During this test, the DUT must perform the following operations on the traffic flow:
- - Preamble: 8 bytes * 8 = 64 bits
- - Frame Length: 64 bytes (minimum) * 8 = 512 bits
- - Inter-frame Gap: 12 bytes (minimum) * 8 = 96 bits
+ - Perform packet parsing on the DUT's ingress port.
+ - Perform any relevant address look-ups on the DUT's ingress ports.
+ - Modify the packet header before forwarding the packet to the DUT's egress port. Packet modifications include:
+ - Modifying the Ethernet source or destination MAC address.
+ - Modifying/adding a VLAN tag.
+ - Modifying/adding a MPLS tag.
+ - Modifying the source or destination ip address.
+ - Modifying the TOS/DSCP field.
+ - Modifying the source or destination ports for UDP/TCP/SCTP (Recommended).
+ - Modifying the TTL.
- Therefore, Maximum Frame Rate (64B Frames)
+ **Expected Result**:
- = MAC Transmit Bit Rate / (Preamble + Frame Length + Inter-frame Gap)
+ **Metrics Collected**:
- = 10,000,000,000 / (64 + 512 + 96)
+ The following are the metrics collected for this test:
- = 10,000,000,000 / 672
+ - Throughput stability of the DUT.
+ - Any outliers in the Throughput stability.
+ - Any unexpected variation in Throughput stability.
- = 14,880,952.38 frame per second (fps)
+<br/>
+
+ - #####Test ID: LTD.Throughput.RFC6201.ResetTime
+ **Title**: RFC 6201 Reset Time Test
+
+ **Prerequisite Test**: N\A
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to determine the length of time it takes the DUT to recover from a reset. For each frame size previously defined under [Default Test Parameters](#DefaultParams), traffic should be sent to the DUT under normal conditions. During the duration of the test and while the traffic flows are passing through the DUT, the DUT should be reset and the Reset time measured. The Reset time is the total time that a device is determined to be out of operation and includes the time to perform the reset and the time to recover from it (cf. [RFC6201])
+
+ [RFC6201] defines two methods to measure the Reset time:
+ - Frame-Loss Method: which requires the monitoring of the number of lost frames and calculates the Reset time based on the number of frames lost and the offered rate according to the following formula:
+ <pre><code>
+ Frames_lost (packets)
+ Reset_time = -------------------------------------
+ Offered_rate (packets per second)
+ </code></pre>
+ - Timestamp Method: which measures the time from which the last frame is forwarded from the DUT to the time the first frame is forwarded after the reset. This involves time-stamping all transmitted frames and recording the timestamp of the last frame that was received prior to the reset and also measuring the timestamp of the first frame that is received after the reset. The Reset time is the difference between these two timestamps.
+
+ According to [RFC6201] the choice of method depends on the test tool's capability; the Frame-Loss method SHOULD be used if the test tool supports:
+ - Counting the number of lost frames per stream.
+ - Transmitting test frame despite the physical link status.
+
+ whereas the Timestamp method SHOULD be used if the test tool supports:
+ - Timestamping each frame.
+ - Monitoring received frame's timestamp.
+ - Transmitting frames only if the physical link status is up.
- #####RFC 1242 Benchmarking Terminology for Network Interconnection Devices
- RFC 1242 defines the terminology that is used in describing performance benchmarking tests and their results. Definitions and discussions covered include: Back-to-back, bridge, bridge/router, constant load, data link frame size, frame loss rate, inter frame gap, latency, and many more.
+ **Expected Result**:
+
+ **Metrics collected**
+
+ The following are the metrics collected for this test:
+ - Average Reset Time.
+
+ Results of this test should include the following information:
+ - Throughput in Fps and Mbps.
+ - Average Frame Loss.
+ - Average Reset Time in milliseconds.
+ - Number of trials.
+ - Protocol: IPv4, IPv6, MPLS, etc.
+ - Frame Size in Octets
+ - Port Media: Ethernet, Gigabit Ethernet (GbE), etc.
+ - Port Speed: 10 Gbps, 40 Gbps etc.
+ - Interface Encapsulation: Ethernet, Ethernet VLAN, etc.
+
+ **Deployment scenario**:
+
+ - Physical → virtual switch → physical.
+
+<br/>
- #####RFC 2544 Benchmarking Methodology for Network Interconnect Devices
- RFC 2544 outlines a benchmarking methodology for network Interconnect Devices. The methodology results in performance metrics such as latency, frame loss percentage, and maximum data throughput.
+ - #####Test ID: LTD.Throughput.RFC2889.ForwardingRate
- In this document network “throughput” (measured in millions of frames per second) is based on RFC 2544, unless otherwise noted. Frame size refers to Ethernet frames ranging from smallest frames of 64 bytes to largest frames of 4K bytes.
+ **Title**: RFC2889 Forwarding Rate Test
- Types of tests are:
- 1. Throughput test defines the maximum number of frames per second that can be transmitted without any error.
- 2. Latency test measures the time required for a frame to travel from the originating device through the network to the destination device. Please note that note RFC2544 Latency measurement will be superseded with a measurement of average latency over all successfully transferred packets or frames.
- 3. Frame loss test measures the network’s response in overload conditions - a critical indicator of the network’s ability to support real-time applications in which a large amount of frame loss will rapidly degrade service quality.
- 4. Burst test assesses the buffering capability of a switch. It measures the maximum number of frames received at full line rate before a frame is lost. In carrier Ethernet networks, this measurement validates the excess information rate (EIR) as defined in many SLAs.
- 5. System recovery to characterize speed of recovery from an overload condition
- 6. Reset to characterize speed of recovery from device or software reset. This type of test has been updated by [RFC 6201] as such, the methodology defined by this specification will be that of RFC 6201.
+ **Prerequisite Test**: LTD.Throughput.RFC2544.PacketLossRatio
- Although not included in the defined RFC 2544 standard, another crucial measurement in Ethernet networking is packet delay variation. The definition set out by this specification comes from [RFC 5481].
+ **Priority**:
- #####RFC 2285 Benchmarking Terminology for LAN Switching Devices
- RFC 2285 defines the terminology that is used to describe the terminology for benchmarking a LAN switching device. It extends RFC 1242 and defines: DUTs, SUTs, Traffic orientation and distribution, bursts, loads, forwarding rates, etc.
+ **Description**:
- #####RFC 2889 Benchmarking Methodology for LAN Switching
- RFC 2889 outlines a benchmarking methodology for LAN switching, it extends RFC 2544. The outlined methodology gathers performance metrics for forwarding, congestion control, latency, address handling and finally filtering.
+ This test measures the DUT's Max Forwarding Rate when the Offered Load is varied between the throughput and the Maximum Offered Load for fixed length frames at a fixed time interval. The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams). The throughput is the maximum offered load with 0% frame loss (measured by the prerequisite test), and the Maximum Offered Load (as defined by [RFC2885]) is _"the highest number of frames per second that an external source can transmit to a DUT/SUT for forwarding to a specified output interface or interfaces"_.
- #####RFC 3918 Methodology for IP Multicast Benchmarking
- RFC 3918 outlines a methodology for IP Multicast benchmarking.
+ Traffic should be sent to the DUT at a particular rate (TX rate) starting with TX rate equal to the throughput rate. The rate of successfully received frames at the destination counted (in FPS). If the RX rate is equal to the TX rate, the TX rate should be increased by a fixed step size and the RX rate measured again until the Max Forwarding Rate is found.
- #####RFC 4737 Packet Reordering Metrics
- RFC 4737 describes metrics for identifying and counting re-ordered packets within a stream, and metrics to measure the extent each packet has been re-ordered.
+ The trial duration for each iteration should last for the period of time needed for the system to reach steady state for the frame size being tested. Under [RFC2889] test methodology, the test duration should run for a minimum period of 30 seconds, regardless whether the system reaches steady state before the minimum duration ends.
- #####RFC 5481 Packet Delay Variation Applicability Statement
- RFC 5481 defined two common, but different forms of delay variation metrics, and compares the metrics over a range of networking circumstances and tasks. The most suitable form for vSwitch benchmarking is the "PDV" form.
+ **Expected Result**:
+ According to [RFC2889] The Max Forwarding Rate is the highest forwarding rate of a DUT taken from an iterative set of forwarding rate measurements. The iterative set of forwarding rate measurements are made by setting the intended load transmitted from an external source and measuring the offered load (i.e what the DUT is capable of forwarding). If the Throughput == the Maximum Offered Load, it follows that Max Forwarding Rate is equal to the Maximum Offered Load.
- #####RFC 6201 Device Reset Characterization
- RFC 6201 extends the methodology for characterizing the speed of recovery of the DUT from device or software reset described in RFC 2544.
+ **Metrics Collected**:
+ The following are the metrics collected for this test:
+
+ - The Max Forwarding Rate for the DUT for each packet size.
+
+<br/>
+ - #####Test ID: LTD.Throughput.RFC2889.ForwardPressure
+ **Title**: RFC2889 Forward Pressure Test
+
+ **Prerequisite Test**: LTD.Throughput.RFC2889.ForwardingRate
+
+ **Priority**:
+
+ **Description**:
+
+ The aim of this test is to determine if the DUT transmits frames with an inter-frame gap that is less than 12 bytes. This test overloads the DUT and measures the output for forward pressure. Traffic should be transmitted to the DUT with an inter-frame gap of 11 bytes, this will overload the DUT by 1 byte per frame. The forwarding rate of the DUT should be measured.
+
+ **Expected Result**:
+ The forwarding rate should not exceed the maximum forwarding rate of the DUT collected by LTD.Throughput.RFC2889.ForwardingRate.
+
+ **Metrics collected**
+
+ The following are the metrics collected for this test:
+
+ - Forwarding rate of the DUT.
+
+ **Deployment scenario**:
+
+ - Physical → virtual switch → physical.
+
+<br/>
[RFC1242]:(http://www.ietf.org/rfc/rfc1242.txt)
-[RFC5481]:(http://www.ietf.org/rfc/rfc5482.txt)
+[RFC2544]:(http://www.ietf.org/rfc/rfc2544.txt)
+[RFC2885]:(http://www.ietf.org/rfc/rfc2885.txt)
+[RFC2889]:(http://www.ietf.org/rfc/rfc2889.txt)
+[RFC5481]:(http://www.ietf.org/rfc/rfc5481.txt)
+[RFC6201]:(http://www.ietf.org/rfc/rfc6201.txt)
[DPDK]:http://www.dpdk.org/
-[RFC 6201]:http://tools.ietf.org/html/rfc6201
-[RFC 5481]:http://tools.ietf.org/html/rfc5481
\ No newline at end of file
Code Review / vswitchperf.git / blobdiff