Spirent MethodologyCenter vswitch Benchmarking

Transcription

1 Spirent MethodologyCenter vswitch Benchmarking Throughput and Latency Profile Test case vswitch Throughput and Latency Profile Measurement 2 Overview 2 Objective 2 Configuring the test SUT 2 Configuring the test MethodologyCenter 3 Executing the test and analyzing the results 5 Result Metrics 6 Troubleshooting 7 References 8 Acronyms 8

2 Test case vswitch Throughput and Latency Profile Measurement Overview Virtualization of network functions is an essential step for deployment of NFV implementations. Although most of the key NEMs and network device vendors have virtualized network devices of some form, the challenge of providing the type of performance, reliability and resiliency offered by traditional network devices is still daunting. This test reveals how throughput and latency degrades as the offered rate varies in the region of the DUT s zero loss throughput rate. For example it can be used to determine if the degradation of throughput and latency as the offered rate increases is slow and graceful or sudden and severe. This is particularly important to understand the behavior of the vswitch when it is operating close to its performance limits. This is where the cause of vswitch performance limitations such as queue throttling or efficiency of the hashing algorithm employed at NIC level can be identified. A delta of 0% is equivalent to an offered traffic rate equal to the RFC 2544 Throughput; A delta of +50% indicates an offered rate half-way between the Throughput and line-rate, whereas a delta of -50% indicates an offered rate of half the maximum forwarding rate. Objective The test methodology provides an automated way to profile the throughput and latency of a vswitch (SUT) using Spirent MethodologyCenter application. The SUT may also consist of the combination of a vswitch and VNFs in a service chain. Configuring the test SUT STCv STCv STCv Virtual Switch Virtual Switch Virtual Switch NIC NIC NIC NIC Spirent TestCenter Spirent TestCenter (a) (b) (c) SUT Spirent Tester Figure 1 Test Deployment Scenarios 1. Configure the SUT to forward bi-directional L2/L3 traffic between the Spirent TestCenter ports. Note that test tool used here may be Spirent TestCenter chassis or Spirent TestCenter Virtual. 2 spirent.com

3 Configuring the test MethodologyCenter MethodologyCenter provides an easy to use web interface that reduces the test setup time and result analysis time significantly. 1. Select the Spirent TestCenter ports by clicking on the ports link and select the Spirent TestCenter ports for east and west side of the test. Note that east and west side is notations used to refer to the test traffic side with respect to the DUT/SUT. Select or add the Spirent TestCenter chassis that is connected to the SUT by clicking on the desired chassis. User can add the desired chassis to the list by using the IP address of the STC and adding to the resource list. Same procedure is to be followed to for Spirent TestCenter Virtual. Once the Spirent TestCenter resource is selected a sign appears on the top of the Spirent TestCenter resource. Select the desired ports on the selected chassis for both east and west side group as shown in the screenshots below. 2. Configuring test endpoints Click on the Configuration link as shown below to configure the Layer 2 and Layer 3 address information for the east and west test endpoints. 3. Setting test parameters vswitch flow scale test methodology consists of parameters that are easy to setup and at the same time provides ability to customize the test run. Following categories of test parameters are defined for vswitch flow scale methodology. a. Global Parameters IP version IPv4 / IPv6 Traffic Direction Bidirectional / East to West / West to East b. Traffic Configuration These set of parameters allow the configuration of test traffic. Enable UDP Echo Packet If enabled the packets used for test traffic would be UDP Echo packets else raw IP test packets will be used. Traffic Pattern: This field may be set to PAIR for 1:1 source to destination, BACKBONE for 1:N and MESH for N:N source to destination mapping. imix Frame Size: In addition to using a fixed size frame size, an imix or internet mix frame size distribution may be defined. For imix distribution each of the constituent frame sizes can be edited, new frame sizes may be added or the weight for each frame size may be modified. spirent.com 3

4 c. Flow Count List The list of flow counts for which the 2544 throughput test will be run. Flow counts may be added/removed/modified from the list. d. Frame Size List This parameter enables the user to configure the list of frame sizes for RFC 2544 throughput test. User can edit or remove the existing frame sizes from the list and add new frame sizes to the list. e. Address Learning This parameter is enables/disables sending L2/L3 learning frames before the throughput test is started. f. Rate Search Parameters These set of parameters allow the user to specify rate search and resolution for rate search. User can modify the value of these parameters to optimize the time taken for rate search for each trial as well as fine tune the resolution of the throughput result. 4 spirent.com

5 Executing the test and analyzing the results 4. Once the parameters are setup, click on the run button Run Time Results Run-time results include the graph for Tx/Rx frame rate, graph for trial results of the selected frame sizes and a table that consists of counters for trial updates. a. Run-time Tx/Rx frame rate b. Run-time trial graph: It provides the throughput for each frame size and number of flows. Hovering over the data points in the graph displays the Configured rate, throughput and frame size. c. Result counters for each trial. The table shows updated result counters at the end of each trial. Counters included are Tx Frame Count, dropped count, average latency and average jitter. spirent.com 5

6 Result Report The result report contains summary results and detailed results for each of the selected frame sizes and delta values. Following are the graphs as part of the test report that show the impact on forwarding performance and latency for the specified delta values. Result Metrics Result report contains the following metrics for each flow number and each iteration within the trial Throughput Latency (Avg) Jitter (Avg) Dropped Count, flooded packet count, out of sequence packet count 6 spirent.com

7 Troubleshooting No test frames received Check if there is L3 connectivity between the two test ports through the SUT Verify if the IP address for test endpoints and gateway address are on the same subnet and they are reachable Verify if the ARP between the test endpoint and gateway address can be resolved Verify the VLAN ID on both the test endpoints is set to same value Verify that SUT is configured to forward the test traffic with given IP address and VLAN ID Out of sequence frames or flooded frames received Check if the SUT has load balancing configured or if there are multiple paths for test packets between the interfaces connected to east and west test endpoints Verify that the queuing mechanisms on the vswitch are not causing excessive delay in processing for certain flows spirent.com 7

8 Spirent MethodologyCenter vswitch Benchmarking Throughput and Latency Profile References [1] draft-vsperf-bmwg-vswitch-opnfv-02 Acronyms DUT Device Under Test NFV Network Functions Virtualization SUT System Under Test VNF Virtualized Network Function VLAN Virtual Local Area Network spirent.com AMERICAS SPIRENT EUROPE AND THE MIDDLE EAST +44 (0) ASIA AND THE PACIFIC Spirent. All Rights Reserved. All of the company names and/or brand names and/or product names referred to in this document, in particular, the name Spirent and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners. The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent. The information in this document is believed to be accurate and reliable; however, Spirent assumes no responsibility or liability for any errors or inaccuracies that may appear in the document. Rev A 06/16