Award Winning Solutions
Xena has won multiple global awards for price/performance and technical innovation. Learn more.
Technical Expertise
Copyright © 2009-2023 Teledyne LeCroy Xena ApS, Denmark
This is the User Manual for Valkyrie2889. Valkyrie2889 is a PC application that enables you to perform advanced network tests according to the RFC 2889 specification using one or more of the Xena Valkyrie test equipment chassis.
The Xena2889 application features the following capabilities:
Valkyrie2889 is a standard Windows .NET application supporting Windows XP (SP3) and all later Windows versions. It requires Microsoft .NET version 4.0.
After installation you can find a shortcut to the application either in the Start -> Programs -> Xena Networks menu or (if you have selected this during setup) on your desktop.
The application is installed as part of the Valkyrie software release package which can be obtained here.
Refer to this page for details on support for Linux.
The following RFC 2889 test types are fully supported by the Valkyrie2889:
The following RFC 2889 test types are partially supported by the Valkyrie2889:
This section provides explanations for the terminology used by the Valkyrie2889.
Test Type
Denotes one of the test types defined in RFC 3918, sections 4 to 8, such as “Mixed Class Throughput” and “Multicast Latency”.
Trial
A “trial” denotes a single execution of a test with a given set of test parameters. If the test configuration specifies that the tests shall be performed at various packet sizes a number of trials will then be executed – one for each packet size specified.
Iteration
Each test type can be configured to repeat the test a number of times. Each of these repetitions is called an iteration. One iteration may comprise several trials.
The main Valkyrie2889 application screen is shown in the image below.
Panel | Explanation |
---|---|
Start Page | The default main page shown to the user. This page contains a brief guide to assist you in creating an initial test configuration. You can close this panel once you feel that it is no longer useful to you. |
Selected Ports | This panel allows you to include Xena testports in your test and to configure the behavior of these ports. You select the ports in the Physical Ports view and drag them to theSelected Ports panel to include them in the test. |
General Test Configuration | This panel control the common aspects of the Test Configuration, such as frame sizes and port rates. |
Test Types Configuration | This panel control what tests you are actually going to execute and also handles the testtype-specific configuration options. |
Protocol Segment Profiles | This panel allow you to create and/or configure profiles for protocol segment headers. Each port can be assigned a different protocol header so that it is possible to give each port a different set of |
Reporting Options | This panel control all aspects of the reporting function. |
Panel | Explanation |
---|---|
Result Data | This panel displays the test result data in a grid view. Both the progress counters and the final test data is shown. Progress counters are shown using an italics font whereas the final data is shown with a normal font. |
Configuration Errors | This panel displays any configuration errors detected in your configuration when attempting to start a test. |
This section will help you getting started using the Valkyrie2889 by showing a few simple examples on how to create and to execute various tests.
The Valkyrie2889 program is installed as part of the Xena software tools installer. The latest version of the installer can always be downloaded at the Xena website.
The Valkyrie2889 tool requires the Microsoft .NET Client 4 framework.
Performing a Rate Test (Plain Ethernet)
This example explains how to create and execute a simple rate test using two testports.
A “rate test” is a test that focus on the throughput and forwarding aspects of the DUT. All the tests defined in RFC 2889 sections 5.1 to 5.4 are considered to be rate tests. These tests mainly differ in terms of the used network topology and traffic direction but the basic test methodology is the same for all rate tests.
In this example we will use a Full Mesh topology with three testports, using plain Ethernet traffic.
Perform the following steps to create and execute this test:
The overall result will contain one result for the throughput test and one result for the forwarding test.
This example will show how to expand the above rate test using IPv4 test traffic. It expands on the previous example so we will only describe the main differences in detail. For the sake of variety we will use a Pairs topology instead of the Full Mesh topology used in the previous example.
The overall result will contain one result for the throughput test and one result for the forwarding test.
This example will show how to configure and run one of the other test types.
The result will show the amount of frames transmitted and received in the various frame groups.
This section explains the options available in the various configuration panels.
This panel displays all available ports on the currently connected Xena chassis. It is possible to connect to multiple Xena chassis at the same time.
It also allows you to perform the following actions:
You can reserve or relinquish ownership of a port by right-clicking on it and selecting the appropriate action. Note that the Valkyrie3918 will automatically reserve ownership of used ports when a test is started.
This panel displays the ports that have been actively selected for use in the test configuration. The ports are shown in a grid view with the following columns:
Column | Explanation |
---|---|
Port Name | The name (ID and type) of the port. |
Port Speed | The physical port speed to use in the test. Normally this should be left at the default AUTO value, but certain DUTs require that the port speed is fixed to a specific rate. |
IP Address | The IP address that you want to use for the port. All ports in the configuration need an IP address. |
Prefix | The decimal network prefix for the address. |
Gateway Address | The gateway address for the assigned IP address. Usually this will be the address of the DUT port which the test port is connected to. |
Protocol Segment Profile | The protocol segment profile to use for this port. Profiles can be created, edited and deleted in the separate Protocol Segment Profiles panel. |
Below the grid view is a section with less-frequently-used settings:
Property | Explanation |
---|---|
Inter-Frame Gap | Specifies the minimum gap between frames generated for a port, expressed as a number of bytes. |
Speed Reduction: | Specifies an optional speed reduction on the transmit side of the port, expressed as a ppm value. |
Enable PAUSE Mode: | Controls whether the port responds to incoming PAUSE frames. |
Enable Auto Negotiation: | Controls whether auto-negotiation for the port is enabled or not. |
It is possible to change settings on multiple ports at the same time by selecting multiple ports in the grid view and then changing settings in either the grid view or the detailed settings panel below the grid. The only setting that does not allow this is the IP address field, as this must always be a unique value.
This panel controls the test options that are common for all tests. The various sections in the panel are described below.
This section allows you to specify the frame sizes to be used by the various tests. The available frame size options are divided into two groups, the “Fixed Sizes Per Trial” and the “Varying Sizes Per Trial”.
As the name indicates the “Fixed Sizes Per Trial” group uses a single frame size per trial. It is possible to specify multiple frame sizes which will cause the test to be repeated for each frame size. The “Varying Sizes Per Trial” group will use many frame sizes for each trial. This is controlled by the hardware. Note that when calculating bitrates the average frame size will be used.
Also note that the Errored Frames Filtering test will not used the frame size setting as it uses its own frame size setup as part of the test.
This section allow you to specify the overall rate used by the tests. You can specify the rate using one of the following methods:
Below the controls you can see the resulting percentages or rates for all selected port types.
Note that the Address Caching Capacity and Address Learning Rate tests do not use the overall test port rate as they utilize their own rate definition. The Congestion Control and Forward Pressure tests also do not use the overall test port rate as these tests are always performed at port line speed.
Option | Explanation |
---|---|
Use Micro-TPLD if needed: | The normal Xena test payload (TPLD) section takes up 20 bytes and is used for various purposes, such as latency measurements, loss and misordering monitoring, payload integrity, etc. Due to this test payload it may be impossible to make room for protocol headers such as IPv4+UDP for smaller framesizes (e.g. ~64 byte). By enabling this option you permit Valkyrie2889 to use the smaller “micro”-TPLD if needed by the current framesize. The consequence of this will be that realtime monitoring of packet loss is no longer possible. Note that Valkyrie2889 will only use the micro-TPLD for a testrun if the current framesize requires it. If you for instance use the default IEEE packet size distribution you may encounter that the micro-TPLD is only used for 64 byte packets but not for the other packet sizes. |
TID Alloc.Scope: | Determines how Valkyrie2889 allocates test payload identifier (TID) values.
|
Latency Mode: | Specifies the way the latency value is calculated. Refer to the description of P_LATENCYMODE in the ValkyrieCLI Manual for a description of the various values. |
Toggle Sync State: | If checked the sync state for all selected ports will be toggled off and on at the start of each test trial. This is done to ensure that the DUTs MAC-tables are cleared at the start of each test. Note that the Address Caching Capacity and Address Learning Rate tests do not use this option as they use their own definition. |
Sync State Off Period: | The number of seconds to keep the port sync state off. |
Option | Explanation |
---|---|
Use Port Sync. Start: | If this option is checked the Start button will activate a synchronized port start mechanism for the ports – if the chassis firmware version supports this feature. |
Port Stagger Steps: | This property delays start of traffic generation on one port relative to pressing Start button. The delay is programmed in steps of 64 microseconds. The Port Stagger function will work between ports on test modules installed in the same chassis. First port will not be delayed. Second port will be delayed with the Port Stagger Steps. Third port will be delayed with the Port Stagger Steps * 2. Fourth port will be delayed with the Port Stagger Steps * 3 etc. Maximum Port Stagger Steps value for a port is 31250. Therefore the programmed Port Stagger Steps must not exceed 31250/(number of ports). NB: This requires that “Use Port Sync Start” has been checked |
Resulting Delta: | The Port Stagger Steps * 64 microseconds |
Panel | Explanation |
---|---|
Stop on LOS: | If enabled, Valkyrie2889 will abort the test if a port loses the sync state during test. |
Delay After Reset: | When a Valkyrie2889 test is started, the selected ports will be reset to ensure a known starting point for the test. This parameter defines how long time Valkyrie2889 will wait after the reset before it continues with the test. |
This panel allows you to select which tests are executed and configure their parameters.
All available tests are shown in the treeview to the left. You can select if a test is executed by using the checkbox to the left of the test name. You can also use the two small buttons in the toolbar at the lower part of the treeview to quickly enable or disable all tests.
To inspect and optionally change the test options for a test, select the test in the treeview. The associated test options will then be displayed in the configuration panel to the right.
Each test contains a port role configuration control at the bottom of the associated configuration panel. This control enables you to select which of the selected ports should actually be used in the test and also to configure the role that each port should play in the test.
The RFC 2889 defines several types of rate tests, but these are typically not possible to execute using the same test setup as the required cabling and equipment will typically differ quite substantially. Instead the Valkyrie2889 allow you to create and define the number of rate tests relevant for the actual DUT.
Each rate test consist of two possible subtests:
You can enable either both these subtests or just one of them.
To create a new rate test press the Add button located at the bottom of the test treeview. You can configure both the topology and the direction for the rate test, and also set the port roles for the test.
To delete a rate test select the test and press the Remove button located at the bottom of the test treeview.
This section describes the options available for the various test types.
This section describes the test options found in all or most tests.
Option | Explanation |
---|---|
Duration: | The duration of each test trial in seconds. |
Iterations: | The number of times to repeat each test trial with the same set of test parameters. |
Option | Explanation |
---|---|
Common Test Options | |
Test Label: | A text label for this rate test. Use this to assign a short description of the purpose of the test. |
Traffic Setup | |
Topology: | The topology of the test traffic:
|
Direction: | Determines the direction of the test traffic. |
Throughput Test Options | |
Enable Throughput Test: | If checked, the Throughput test will be executed. This is an iterative test that will find the largest throughput rate with zero loss for the DUT. |
Initial Rate: | The starting rate to use. This is specified as a percentage of the overall port rate defined in the general test options panel. |
Maximum Rate: | The maximum rate to use. This is specified as a percentage of the overall port rate. |
Minimum Rate: | The minimum rate to use. This is specified as a percentage of the overall port rate. If the iteration reaches this value the test is stopped and the result will be FAILed. |
Resolution Rate: | The trial stops when the difference between the current and the last successful trial is less than the Resolution. |
Forwarding Test Options | |
Enable Forwarding Test | If checked the Forwarding test will be executed. This is a rate sweep test that will measure the forwarding rate and the loss for the DUT at various transmit rates. |
Start Rate: | The starting rate percentage used in the test. |
End Rate: | The ending rate percentage used in the test. |
Step Rate: | The rate step increment. |
Port Role Configuration | |
Used? | If checked the port will be used in this test. |
Port Role | Used to place the port in either the “East” or the “West” block. Only available when Topology is either “Blocks” and “Pairs” |
Port Peer | Used to pair the port with another port. Only available when Topology is “Pairs”. |
This test does not use specific test options apart from the common test options described above.
Option | Explanation |
---|---|
Interframe Gap Delta | The difference between the default Interframe Gap (IFG) value of 20 bytes and the reduced value used on the source port. |
Accept. Rx Util. Delta: | The acceptable receive rate utilization delta, i.e. the value with which the receive rate is allowed to exceed 100.0%. |
Option | Explanation |
---|---|
Rate Sweep Options | |
Start Rate: | The starting rate percentage used in the test. |
End Rate: | The ending rate percentage used in the test. |
Step Rate: | The rate step increment. |
Option | Explanation |
---|---|
MAC Address Settings | |
Initial Count: | The starting address count to use. |
Maximum Count: | The maximum address count to use. |
Minimum Count: | The minimum address count to use. If the trial reaches this value the test is stopped and the result will be FAILed. |
Resolution Count: | The trial stops when the difference between the current and the last successful trial is less than the Resolution. |
Learning Rate Settings | |
Learning Rate: | The learning rate in frames/second to use. |
DUT Address Learning Reset | |
Toggle Sync States: | If checked the sync state of the test ports will be toggled off and on between test trials. Enabling this may help clearing the MAC learning tables in the DUT and speed up the test. |
Sync State Off Period: | The amount of seconds the port sync states will be off. |
Switch Test Port Roles: | If checked the port with the Test and Learning roles will be swapped between test trials. Enabling this may help clearing the MAC learning tables in the DUT and speed up the test. |
DUT Aging Time: | If none of the two options above are checked the test will wait for the specified seconds between trials to ensure that the MAC table in the DUT has been cleared. |
Misc. Options | |
Fast Run Resolution: | Enable this option to perform fast resolution of a testrun based on polled data – the testrun will stop when a packet is received on monitoring port. |
Option | Explanation |
---|---|
MAC Address Settings | |
Learning Base Address: | The first 3 bytes of the MAC addresses used for the learning test. It is necessary to use a different base address than the default Xena base address (04.F4.BC) when running a test using multiple addresses to avoid conflicts with other unused ports on the Xena tester. |
Start Count: | The starting number of addresses used in the test. |
End Count: | The ending number of addresses used in the test. |
Step Count: | The address count step increment. |
Only Use Max. Capacity: | If checked the test will ignore the start, end and step options and only run the test at the max. capacity. This option is only used if an Address Caching Capacity test has previously been run as part of the same test and a capacity test result has been found for the frame size in question. Otherwise the test will default to use the start, end and step options. |
Set End = Max. Capacity | If checked the test will ignore the end count option value and use the max. capacity value instead. This option is only used if an Address Caching Capacity test has previously been run as part of the same test and a capacity test result has been found for the frame size in question. Otherwise the test will default to use the end option value. |
Learning Rate Settings | |
Base Learning Rate: | The basic (i.e. maximum) learning rate used in frames/second. Note that the general port rate defined for the test configuration is ignored for this test. |
Initial Rate: | The starting rate to use. This is specified as a percentage of the base learning rate. |
Maximum Rate: | The maximum rate to use. This is specified as a percentage of the base learning rate and will typically be 100%. |
Minimum Rate: | The minimum rate to use. This is specified as a percentage of the base learning rate. If the trial reaches this value the test is stopped and the result will be FAILed. |
Resolution Rate: | The trial stops when the difference between the current and the last successful trial is less than the Resolution. |
DUT Address Learning Reset | |
Refer to the description for the equivalent options in the Address Caching Capacity test. |
Option | Explanation |
---|---|
Rate Sweep Options | |
Start Rate: | The start rate to use in percent of the overall port rate defined. |
End Rate: | The end rate to use in percent of the overall port rate defined. |
Step Rate: | The step rate to use in percent of the overall port rate defined. |
Test Frame Options | |
Enable Oversize Test: | If checked the oversize frames test will be performed. You can disable this if your DUT generally supports very large frame sizes and you don’t want to bother testing this. |
Max. Valid Frame Size: | The maximum valid frame size you believe your DUT should support. |
Oversize Test Span: | The number of oversize frame sizes to use in the test. The frame sizes used will be in the range [max. valid size + 1, max. valid size + span]. |
Min. Valid Frame Size: | The minimum valid frame size you believe your DUT should support. This value should typically be 64. |
Undersize Test Span: | The number of undersize frame sizes to use in the test. The frame sizes used will be in the range [min. valid size – 1, min. valid size – span]. |
Option | Explanation |
---|---|
Throughput Test Options | |
Initial Rate: | The starting rate to use. This is specified as a percentage of the overall port rate defined in the general test options panel. |
Maximum Rate: | The maximum rate to use. This is specified as a percentage of the overall port rate. |
Minimum Rate: | The minimum rate to use. This is specified as a percentage of the overall port rate. If the iteration reaches this value the test is stopped and the result will be FAILed. |
Resolution Rate: | The trial stops when the difference between the current and the last successful trial is less than the Resolution. |
This panel allow you to manage the protocol segment profiles used for the test ports. The Valkyrie2889 enables you to define an asymmetric traffic setup so that each port potentially can be configured using a separate profile.
You can create and delete profiles to match the need of the current test scenario. To create a new profile press the Add Profile button. To delete a profile select it in the listview and press the Remove Profilebutton.
You can however not delete a profile that is currently being used by a testport. You can see the number of testports currently using a profile in the “Use Count” column in the listview at the top. To delete a profile that is in use you will first have to reassign all ports currently using that profile to another profile.
When you create a new Valkyrie2889 configuration it will be populated with a number of default profiles. You can however freely modify and even delete one or more of the default profiles.
If for some reason you want to restore the default profiles you can press the Restore Default Profiles button. This will unconditionally remove all current profiles (also those that are in use) and restore the default set. All test ports will be associated with the first default “Ethernet-only” profile.
You can edit each profile by selecting it in the top listview and using the treeview control below.
To add a new segment header press the Add button in the Segments section to the right. You will then be presented with a dialog listing all built-in segment types from which you can select one or more types to be included. If you want to use a segment not currently supported by the Valkyrie2889 you can add a raw segment and specify the length in bytes. You can then afterwards edit the values in the resulting segment using the hex editor at the bottom.
You can remove one or more segments by selecting them and pressing the Remove button in the Segments section. You can change the order in which the segment headers appear by using the Move Up/Down buttons.
The Valkyrie2889 will automatically adjust the value of any standard “next-protocol” field (such as the EtherType field) in the segment headers when other segments are added, removed or moved.
The segment editor provides a treeview similar to the one found in the Wireshark protocol analyzer. You can thus expand each segment branch to view and optionally modify the various field values. Each field title is preceded with a small icon indicating the type of field value (decimal, hexadecimal, binary or IPv4/IPv6 address).
Certain fields, such as the EtherType, are associated with a set of commonly used named values. These can be selected in the Named Values column. You are however free to enter any value you want in theRaw Value column.
You can also edit the hex value of the segment headers directly using the hex editor at the bottom if you are so inclined.
The address fields in the Ethernet and IP section headers will usually be overridden by the Valkyrie2889 when the teststreams are created:
This replacement will however only be performed if you leave the fields at their default (all-zeros) value. If you specify anything else this value will be used instead.
You can import the protocol segment structure from a PCAP file captured using Wireshark or any other capture application capable of generating a standard PCAP file. If the file contains multiple packets Valkyrie2889 will display a list allowing you to select the desired packet.
Valkyrie2889 will attempt to decode the packet and display the known protocol headers and their fields. Any unknown fields will be displayed as a raw segment. As there are limitations in the max.size of a custom segment the import may not be possible in some cases. The import dialog will inform you about this if the situation arises.
The Reporting Options panel contains a number of options that affect the way reports are generated for the test.
This section contains a number of options that can help identify the test context.
This section contains options that affect the way reports are generated.
This section allows you to select which types of reports will be generated. You can enable several types. The generated report files will be given a file extension that matches the selected type, i.e. “.pdf” for PDF files and so forth.
You can find the specification for the XML Report here.
In the Report formats section you can also activate the “Also Log Intermediate Results” option. It will log intermediate results for each test type to separate CSV logfiles (one for each enabled test type) located in the “ResultLog” subdirectory in the main Xena2889 Reports directory.
The Result Data panel will display both polled progress data and result data for the tests being executed in a grid view. Each result will be shown in a single line in the grid.
The polled progress data is updated periodically while the current test trial is executing and will be shown with an italics font. After the test trial has completed the result data for that trial will be calculated and shown with a normal font.
The Result State column will shown the state of the current trial run. While the test trial is in progress the state will always be “(pending)”. A trial result may be final in which case the column will show either PASS or FAIL, depending on the test outcome. If the test needs to perform another iteration the state will again be “(pending)”.
The columns used will depend of the test being performed. Most tests will provide a set of “totals” values and a set of per-port values but as stated this depends on the test.
Most cell values will be displayed using the normal font color. Values that indicate an error, such as a non-zero loss value, will be displayed with a red font color.
This panel will show any configuration errors detected by the program when you attempt to execute a configuration. If any such errors are found the panel will be shown and the execution attempt will be aborted. You will have to correct any reported errors before the program will allow you to execute the configuration.
Each error will be shown in a separate line in the panel. If you double-click on an error message you will be taken to the relevant configuration panel that will allow you to correct the error.
This panel is by default found in the lower auto-hiding panel group. By “auto-hiding” we mean that the panel is initially hidden but will popup either if the panel tab is clicked or if the Valkyrie2889 program decides that it is necessary to direct the attention of the user to the panel. You can make the panel visible always by clicking the little “pin” icon in the top-right of the panel header.
The Valkyrie3918 application features a number of application-level settings which are valid for all test configurations. These can be accessed in the Options menu item as shown in the figure below.
The Valkyrie2889 supports a number of command line options which can be used to automate the execution of a predefined configuration file.
Valkyrie2889 is part of a new series of Xena test tools series that does not require a separate executable file to perform the command line functionality. The same executable (xena2889_.exe) is used for both the GUI and the command line functions.
The valid command line options are as follows:
Command option | Explanation |
---|---|
-c, –config | Load a test configuration file with the specified path. |
-e, –execute | Execute the specified test configuration file (requires -c ). If this option is used the program will not show the GUI but will run in command line mode. |
-u, –user | Set the username used when logging on to Xena testers (default: xenarun). |
-r, –reportpath | Set the path where reports are saved. |
-o, –company | Set the company name used in reports. |
-l, –logo | Set the path to the report logo file. |
-h, –help | Display this help screen. |
Please refer to this page for further details about troubleshooting the Valkyrie2889.