User Manual
TRex 58 / 113
5.6.1 Examples
simple HTTP traffic
[bash]>sudo ./t-rex-64 -f cap2/http_simple.yaml -c 4 -l 1000 -d 100000 -m 30 --learn-mode ←-
1
SFR traffic without bundling/ALG support
[bash]>sudo ./t-rex-64 -f avl/sfr_delay_10_1g_no_bundling.yaml -c 4 -l 1000 -d 100000 -m ←-
10 --learn-mode 2
NAT terminal counters:
-Global stats enabled
Cpu Utilization : 0.6 % 33.4 Gb/core
Platform_factor : 1.0
Total-Tx : 3.77 Gbps NAT time out : 917
v
1
(0 in wait for syn+ack)
v
2
Total-Rx : 3.77 Gbps NAT aged flow id: 0
v
3
Total-PPS : 505.72 Kpps Total NAT active: 163
v
4
(12 waiting for syn)
v
5
Total-CPS : 13.43 Kcps Total NAT opened: 82677
v
6
v
1
Number of connections for which TRex had to send the next packet in the flow, but did not learn the NAT translation yet.
Should be 0. Usually, a value different than 0 is seen if the DUT drops the flow (probably because it cannot handle the
number of connections).
v
3
Number of flows for which the flow had already aged out by the time TRex received the translation info. A value other
than 0 is rare. Can occur only when there is very high latency in the DUT input/output queue.
v
4
Number of flows for which TRex sent the first packet before learning the NAT translation. The value depends on the
connection per second rate and round trip time.
v
6
Total number of translations over the lifetime of the TRex instance. May be different from the total number of flows if
template is uni-directional (and consequently does not need translation).
v
2
Out of the timed-out flows, the number that were timed out while waiting to learn the TCP seq num randomization of the
server→client from the SYN+ACK packet. Seen only in --learn-mode 1.
v
5
Out of the active NAT sessions, the number that are waiting to learn the client→server translation from the SYN packet.
(Others are waiting for SYN+ACK from server.) Seen only in --learn-mode 1.
Configuration for Cisco ASR1000 Series:
This feature was tested with the following configuration and the
sfr_delay_10_1g_no_bundling.yaml
traffic profile. The client address range is 16.0.0.1 to 16.0.0.255
interface TenGigabitEthernet1/0/0
v
1
mac-address 0000.0001.0000
mtu 4000
ip address 11.11.11.11 255.255.255.0
ip policy route-map p1_to_p2
ip nat inside
v
2
load-interval 30
!
interface TenGigabitEthernet1/1/0
mac-address 0000.0001.0000