User Manual

TRex 51 / 113
5.5.1 Latency with Cluster mode
Latency streams client IP is taken from the first IP in the default client pool. Each dual port will have one Client IP. In case of
cluster configuration this is a limitation as you can have a topology with many paths.
Traffic profile
- duration : 10.0
generator :
distribution : "seq"
clients_start : "16.0.0.1"
clients_end : "16.0.0.255"
servers_start : "48.0.0.1"
servers_end : "48.0.0.255"
dual_port_mask : "1.0.0.0"
cap_info :
- name: cap2/dns.pcap
cps : 1.0
ipg : 10000
rtt : 10000
w : 1
Cluster profile
vlan: true
groups:
- ip_start : 16.0.0.1
ip_end : 16.0.0.204
initiator :
vlan : 100
dst_mac : "00:00:00:01:00:00"
responder :
vlan : 200
dst_mac : "00:00:00:02:00:00"
count : 4
For example, in this case 16.0.0.1→48.0.0.1 ICMP will be the flow for latency. The Cluster configuration of this flow will be
taken from cluster file ( VLAN=100, dst_mac : "00:00:00:01:00:00" )
5.5.2 Clustering example
In this example we have one DUT with four 10gb interfaces and one TRex with two 40Gb/sec interfaces and we want to convert
the traffic from 2 TRex interfaces to 4 DUT Interfaces. The folowing figure shows the topology