Explore topic-wise InterviewSolutions in .

For now, none. You can CONNECT your router to a switch with TRex and a MACHINE RUNNING routes. Then, inject routes USING route, and other traffic using TRex.

For now, none. You can connect your router to a switch with TRex and a machine running routes. Then, inject routes using route, and other traffic using TRex.

YES. USING Field ENGINE you can BUILD streams with different TOS and get statistic/latency/jitter per stream.

Yes. Using Field Engine you can build streams with different TOS and get statistic/latency/jitter per stream.

TRex has MINIMAL and basic support for HLTAPI. For SIMPLE USE cases (without latency and per stream statistic) it will probably work. For advanced use cases, there is no REPLACEMENT for native API that has full control and in most cases is simpler to use.

TRex has minimal and basic support for HLTAPI. For simple use cases (without latency and per stream statistic) it will probably work. For advanced use cases, there is no replacement for native API that has full control and in most cases is simpler to use.

It is a great IDEA to ADD it; we are looking for SOMEONE to CONTRIBUTE this support.

It is a great idea to add it; we are looking for someone to contribute this support.

No. each STREAM has its own, SEPARATE FIELD ENGINE PROGRAM.

No. each stream has its own, separate field engine program.

Yes. You can BUILD any PACKET you like using Scapy. HOWEVER, there is no way to create corrupted L1 fields (Like Ethernet FCS), SINCE these are usually handled by the NIC HARDWARE.

Yes. You can build any packet you like using Scapy. However, there is no way to create corrupted L1 fields (Like Ethernet FCS), since these are usually handled by the NIC hardware.

Yes. MULTIPLE TREX clients can CONNECT to the same TRex SERVER.

Yes. Multiple TRex clients can connect to the same TRex server.

Default latency PACKETS are SCTP, you can OMIT the -l <num&GT; from COMMAND line, or change it to ICMP.

Default latency packets are SCTP, you can omit the -l <num> from command line, or change it to ICMP.

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 artificially increase 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 PH in your PCAP file as well.

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 artificially increase 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 PH in your PCAP file as well.

Yes. We know this is SOMETHING many people would like, and are working on this. No ETA yet. Once a progress is MADE, we will ANNOUNCE it on the T REX sight and mailing list.

Yes. We know this is something many people would like, and are working on this. No ETA yet. Once a progress is made, we will announce it on the T Rex sight and mailing list.

TREX performance depends on MANY factors:

• MAKE sure trexd_cfg.yaml is optimal see "platform" section in manual.
• More concurrent flows will REDUCE the performance.
• Short flows with one/two packets (e.g. cap2/dns.yaml) will GIVE the worst performance.

TRex performance depends on many factors:

A switch might be configured with spanning tree ENABLED. TRex reset the PORT at startup, making the switch reset it side as well, and spanning tree can drop the packets until it stabilizes. Disabling spanning tree can help. On CISCO nexus, you can do that using spanning-tree port type edge You can ALSO start TRex with -k <num> flag. This will send packets for k seconds before starting the actual test, letting the spanning tree time to stabilize. This issue will be fixed when we consolidate “Stateful” and “Stateless” RPC.

A switch might be configured with spanning tree enabled. TRex reset the port at startup, making the switch reset it side as well, and spanning tree can drop the packets until it stabilizes. Disabling spanning tree can help. On Cisco nexus, you can do that using spanning-tree port type edge You can also start TRex with -k <num> flag. This will send packets for k seconds before starting the actual test, letting the spanning tree time to stabilize. This issue will be fixed when we consolidate “Stateful” and “Stateless” RPC.

TREX uses DPDK which TAKES OWNERSHIP of the ports, so using Wire shark is not possible. You can USE SWITCH with port mirroring to capture the traffic.

TRex uses DPDK which takes ownership of the ports, so using Wire shark is not possible. You can use switch with port mirroring to capture the traffic.

• Fedora - during INSTALLATION, CHOOSE "TROUBLESHOOTING" → Install in basic graphic mode.
• UBUNTU - TRY Ubuntu server, which has textual installation.

It is a CONTINUOUS INTEGRATION. The latest internal version is under 24/7 regression on few steps in our LAB. Once we have enough content we release it to GitHub (Usually every few weeks). We do not send an email for every new release, as it COULD be too frequent for some people. We announce big feature releases on the mailing list. You can always check the GitHub of course.

It is a continuous integration. The latest internal version is under 24/7 regression on few steps in our lab. Once we have enough content we release it to GitHub (Usually every few weeks). We do not send an email for every new release, as it could be too frequent for some people. We announce big feature releases on the mailing list. You can always check the GitHub of course.

You have several ways you can help:

1. Download the product, use it, and report issues (If no issues, we will be very HAPPY to also HEAR success stories).
2. If you use the product and have improvement suggestions (for the product or documentation) we will be happy to hear.
3. If you fix a bug, or DEVELOP new feature, you are more than welcome to create PULL request in GitHub.

You have several ways you can help:

XL710-da2 with 2 40G ports can REACH maximum of 40 MPPS/50Gb (total for all ports) and not 60 MPPS 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.

XL710-da2 with 2 40G ports can reach maximum of 40 MPPS/50Gb (total for all ports) and not 60 MPPS 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.

X710da4fh with 4 10G ports can reach a maximum of 40MPPS (total for all ports) with 64 BYTES packets. (Can not reach the THEORETICAL 60MPPS limit). This is still better than the Intel x520 (82559 based) which can reach ~30MPPS for two ports with one NIC.

X710da4fh with 4 10G ports can reach a maximum of 40MPPS (total for all ports) with 64 bytes packets. (Can not reach the theoretical 60MPPS limit). This is still better than the Intel x520 (82559 based) which can reach ~30MPPS for two ports with one NIC.

BARE metal will have lower latency and better performance. VM has the ADVANTAGES you NORMALLY GET when using VMs.

Bare metal will have lower latency and better performance. VM has the advantages you normally get when using VMs.

No. All PORTS in the configuration file should be of the same NIC type.

The workaround is to run SEVERAL TREX INSTANCES.

No. All ports in the configuration file should be of the same NIC type.

The workaround is to run several TRex instances.

We PRESENT statistics only for first four ports because there is no console space. Global statistics (like TOTAL TX) is correct, taking into account all ports. You can USE the GUI/console or PYTHON API, to see statistics for all ports.

We present statistics only for first four ports because there is no console space. Global statistics (like total TX) is correct, taking into account all ports. You can use the GUI/console or Python API, to see statistics for all ports.

16 PORTS.

16 ports.

Mellanox Connectx 4 is SUPPORTED. Connect 3 and 5 STILL have issues (WIP to fix). Support for FM10K is under DEVELOPMENT.

Mellanox Connectx 4 is supported. Connect 3 and 5 still have issues (WIP to fix). Support for FM10K is under development.

Yes. Since VERSION 2.12, with these limitations. Especially NOTE that a NEW firmware version is NEEDED.

Yes. Since version 2.12, with these limitations. Especially note that a new firmware version is needed.

We are using specific NIC features. Not all the NICS have the capabilities we need.

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. You can FIND the LIST of supported NICs here. Look for “Supported NIcs” table.

Notice that some unsupported NICs can also be used using --SOFTWARE command line argument.

We are using specific NIC features. Not all the NICs have the capabilities we need.

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. You can find the list of supported NICs here. Look for “Supported NIcs” table.

Notice that some unsupported NICs can also be used using --software command line argument.

Yes. Currently there is a NEED for 2-3 cores and 4GB memory. For VM use case, memory requirement can be significantly reduced if NEEDED (at the cost of supporting less concurrent flows) by using the following CONFIGURATION.

LIMITATIONS:

• Using vSwitch will limit the maximum PPS to around 1MPPS (DPDK-OVS/VPP can SOLVE this).
• Latency results will not be accurate.
• For high performance setup (multi-rx-queue), it is better to add rx_desc: 4096 in the trexd_cfg.yaml see platform_yaml_cfg_argument and software mode.

Yes. Currently there is a need for 2-3 cores and 4GB memory. For VM use case, memory requirement can be significantly reduced if needed (at the cost of supporting less concurrent flows) by using the following configuration.

Limitations:

“Stateful” MODE is meant for testing networking gear which saves state per FLOW (5 tuple). Usually this is done by injecting pre-recorded CAPTURE files on pairs of interfaces of the DEVICE under TEST, and dynamically changing src/dst IP/port.

“Stateless” mode is meant to test networking gear that does not manage any state per flow (instead operating on a per packet basis). This is usually done by injecting customized packet streams to the device under test.

“Stateful” mode is meant for testing networking gear which saves state per flow (5 tuple). Usually this is done by injecting pre-recorded capture files on pairs of interfaces of the device under test, and dynamically changing src/dst IP/port.

“Stateless” mode is meant to test networking gear that does not manage any state per flow (instead operating on a per packet basis). This is usually done by injecting customized packet streams to the device under test.

CISCO SYSTEMS, INTEL, Imperva, Mellanox, Vasona NETWORKS and MUCH more.

Cisco systems, Intel, Imperva, Mellanox, Vasona networks and much more.

• HIGH scale BENCHMARKS for stateful NETWORKING gear. For example: Firewall/NAT/DPI.
• Generating high scale DDOS ATTACKS.
• High scale, flexible testing for switches (e.g. RFC2544)
• Scale tests for huge numbers of clients/servers for controller based testing.
• EVENT and production tests.

TREX is fast realistic OPEN source traffic generation tool, RUNNING on STANDARD Intel processors, based on DPDK. It SUPPORTS both stateful and stateless traffic generation modes.

TRex is fast realistic open source traffic generation tool, running on standard Intel processors, based on DPDK. It supports both stateful and stateless traffic generation modes.