User Manual

TRex 29 / 113
v
1
,
v
2
Same CPS for both templates.
This creates the following output:
Table 4.7: DNS ipg from pcap file
pkt time sec template fid flow-
pkt-id
client_ip client_port server_ip desc
1 0.010000 0 1 1 16.0.0.1 1024 48.0.0.1 →
2 0.030944 0 1 2 16.0.0.1 1024 48.0.0.1 ←
3 0.093333 1 2 1 16.0.0.2 1024 48.0.0.2 →
4 0.104362 1 2 2 16.0.0.2 1024 48.0.0.2 ←
5 0.115385 1 2 3 16.0.0.2 1024 48.0.0.2 →
6 0.115394 1 2 4 16.0.0.2 1024 48.0.0.2 →
7 0.126471 1 2 5 16.0.0.2 1024 48.0.0.2 ←
8 0.126484 1 2 6 16.0.0.2 1024 48.0.0.2 ←
9 0.137530 1 2 7 16.0.0.2 1024 48.0.0.2 →
10 0.148609 1 2 8 16.0.0.2 1024 48.0.0.2 ←
11 0.148621 1 2 9 16.0.0.2 1024 48.0.0.2 ←
12 0.148635 1 2 10 16.0.0.2 1024 48.0.0.2 ←
13 0.159663 1 2 11 16.0.0.2 1024 48.0.0.2 →
14 0.170750 1 2 12 16.0.0.2 1024 48.0.0.2 ←
15 0.170762 1 2 13 16.0.0.2 1024 48.0.0.2 ←
16 0.170774 1 2 14 16.0.0.2 1024 48.0.0.2 ←
17 0.176667 0 3 1 16.0.0.3 1024 48.0.0.3 →
18 0.181805 1 2 15 16.0.0.2 1024 48.0.0.2 →
19 0.181815 1 2 16 16.0.0.2 1024 48.0.0.2 →
20 0.192889 1 2 17 16.0.0.2 1024 48.0.0.2 ←
21 0.192902 1 2 18 16.0.0.2 1024 48.0.0.2 ←
Template_id
0: DNS template 1: HTTP template
The output above illustrates two HTTP flows and ten DNS flows in 1 second, as expected.
4.7 SFR traffic YAML
SFR traffic includes a combination of traffic templates. This traffic mix in the example below was defined by SFR France. This
SFR traffic profile is used as our traffic profile for our ASR1k/ISR-G2 benchmark. It is also possible to use EMIX instead of
IMIX traffic.
The traffic was recorded from a Spirent C100 with a Pagent that introduce 10msec delay from client and server side.
- duration : 0.1
generator :
distribution : "seq"
clients_start : "16.0.0.1"
clients_end : "16.0.1.255"
servers_start : "48.0.0.1"
servers_end : "48.0.20.255"
clients_per_gb : 201
min_clients : 101
dual_port_mask : "1.0.0.0"