diff options
Diffstat (limited to 'doc/trex_faq.asciidoc')
| -rw-r--r-- | doc/trex_faq.asciidoc | 54 |
1 files changed, 51 insertions, 3 deletions
diff --git a/doc/trex_faq.asciidoc b/doc/trex_faq.asciidoc index 44f4f237..eb6938a1 100644 --- a/doc/trex_faq.asciidoc +++ b/doc/trex_faq.asciidoc @@ -77,13 +77,18 @@ Limitations: 2. We have regression tests in our lab for each recommended NIC. We do not claim to support NICs we do not have in our lab. ==== Is Cisco VIC supported? -No. Currently its DPDK driver does not support the capabilities needed to run TRex. +Yes. Since version 2.12, with link:trex_manual.html#_cisco_vic_support[these limitations]. Especially note that +a new firmware version is needed. ==== Is 100Gbs NIC QSFP+ supported? Not yet. Support for FM10K and Mellanox Connectx5 is under development. ==== Is there a GUI? -TRex team is not developing it. Have a look link:https://groups.google.com/forum/#!searchin/trex-tgn/sari%7Csort:relevance/trex-tgn/R92-N2Yjy2Q/DIUe06YCBgAJ[here] for TRex Stateless mode GUI from Exalt company. +TRex team is not developing it. +You can find GUI for statless mode developed by Exalt company in +link:https://github.com/exalt-tech/trex-stateless-gui#trex-stateless-gui-beta[this link]. + +There is also work in progress for packet editor (not released yet) in link:https://github.com/cisco-system-traffic-generator/trex-packet-editor[here]. + +New stateless GUI features are developed in link:https://github.com/cisco-system-traffic-generator/trex-stateless-gui[here]. This is also work in progress, not released yet. ==== What is the maximum number of ports per TRex application? 12 ports @@ -118,7 +123,10 @@ This is still better than the Intel x520 (82559 based) which can reach ~30MPPS f ==== I have XL710 NIC with 2x40Gb/sec ports and I can not get line rate XL710-da2 with 2 40G ports can reach maximum of 40MPPS/50Gb (total for all ports) and not 60MPPS with small packets (64B) Intel had in mind redundancy use case when they produced a two port NIC. Card was not intended to reach 80G line rate. -see link:trex_stateless_bench.html[xl710_benchmark.html] for more info +see link:trex_stateless_bench.html[xl710_benchmark.html] for more info. + +==== How does TRex calculate the throughput and where is this part of source code located? +There is good answer in the mailing list link:https://groups.google.com/forum/#!topic/trex-tgn/Hk9IFJJ0KNs[here]. ==== I want to contribute to the project You have several ways you can help: + @@ -234,6 +242,40 @@ Default maximum supported flows is 1M (From TRex prespective. DUT might have muc To increase the number of supported active flows, you should add ``dp_flows'' arg in config file ``memory'' section. Look link:trex_manual.html#_memory_section_configuration[here] for more info. +.example of CFG file +[source,bash] +---- + + - port_limit : 4 + version : 2 + interfaces : ["02:00.0","02:00.1","84:00.0","84:00.1"] # list of the interfaces to bind run ./dpdk_nic_bind.py --status + memory : + dp_flows : 10048576 #<1> + +---- +<1> more flows 10Mflows + +==== Loading a big YAML file raise an error no enough memory for specific pool 2048? + +You should increse the pool with that raise an error, for example in case of 2048 + +.example of CFG file +[source,bash] +---- + + - port_limit : 4 + version : 2 + interfaces : ["02:00.0","02:00.1","84:00.0","84:00.1"] # list of the interfaces to bind run ./dpdk_nic_bind.py --status + memory : + traffic_mbuf_2048 : 8000 #<1> + +---- +<1> for mbuf for 2038 + +You can run TRex with `-v 7` to verify that the configuration has an effect + + + ==== I want to have more active flows on the DUT, how can I do this? After stretching TRex to its maximum CPS capacity, consider the following: DUT will have much more active flows in case of a UDP flow due to the nature of aging (DUT does not know when the flow ends while TRex knows). In order to artificialy increse the length of the active flows in TRex, you can config larger IPG in the YAML file. This will cause each flow to last longer. Alternatively, you can increase IPG in your PCAP file as well. @@ -438,6 +480,12 @@ You can see example for defining and using tunables link:trex_stateless.html#_tu Correct. We use NIC capabilities for counting the packets or directing them to be handled by software. Each NIC has its own capabilities. Look link:trex_stateless.html#_tutorial_per_stream_statistics[here] for per stream statistics and link:trex_stateless.html#_tutorial_per_stream_latency_jitter_packet_errors[here] for latency details. +===== I use per stream statistics on x710/xl710 card and rx-bps counter from python API (and rx bytes releated counters in console) +always show N/A + +This is because on these card types, we use hardware counters (as opposed to counting in software in other card types). +While this allows for counting of full 40G line rate streams, this does not allow for counting bytes (only packet +count available), because the hardware on these NICs lacks this support. |