summaryrefslogtreecommitdiffstats
path: root/doc/trex_config.asciidoc
blob: 742b9968131124aa5fad72f78f65e78b84d22036 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
TRex first time configuration 
=============================
:author: hhaim with the Help of Amir Kroparo. New rev fixes by Ido Barnea.
:email: <hhaim@cisco.com> 
:description: TRex Getting started - instalation guide
:revdate: 2014-11-01
:revnumber: 0.2
:deckjs_theme: swiss
:deckjs_transition: horizontal-slide
:scrollable:

include::trex_ga.asciidoc[]


++++++++++++++++++
<script type="text/javascript"
  src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML">
</script>

<script src="http://d3js.org/d3.v3.min.js" charset="utf-8"></script>

<script src="my_chart.js"></script>

<style>
.axis path,
.axis line {
  fill: none;
  stroke: #000;
  shape-rendering: crispEdges;
}

.dot {
  stroke: #000;
}
</style>


<style type="text/css">

h1 {
  font-size: 2.5em;
}

h2 {
  font-size: 1.5em;
  color: #CD7300;
  border-bottom-color: #000;
}

h7 {
  font-size: 4.5em;
  color: #CD7300;
  position: relative;
  top: auto;
  text-align: center;
  padding: 0;
  -webkit-transform: none;
  -moz-transform: none;
  -ms-transform: none;
  -o-transform: none;
  transform: none;
  padding: 0 48px;
  position: absolute;
  left: 0;
  right: 0;
  top: 50%;
}

h8 {
  font-size: 2.25em;
  font-weight: bold;
  padding-top: .5em;
  margin: 0 0 .66666em 0;
  border-top: 3px solid #888;
  color: #c00;
  border-top-color: #ccc;
  left: 0;
  right: 0;
  top: 40%;
}


html, body {
  height: 100%;
  margin:    0 auto;
  max-width: 1000px;
}

</style>

<script>
    $('#title-slide').css("background-image", "url('images/trex_logo.png')");
    $('#title-slide').css("background-repeat","no-repeat");
    $('#title-slide').css("background-position","center");
    $('h1').html('');
    $('h3').html('<font size="4">Hanoch Haim </font>');
    $('h4').html('<font size="4">Updated 10/2016</font>');
 </script>

++++++++++++++++++

== General info
* This guide will help you configure Cisco ASR1K as DUT connected to TRex running in stateful mode.
* This can be easily adopted for working with any L3 device. Equivalent commands for configuring Linux as your DUT are shown at the end as well.
* Two options are given for configuring the router. Policy based route, and static route. You should
choose the one appropriate for your needs.
* TRex should be directly connected to ASR1K ports, and will act  as both client and server.

== Setup description

* TRex will emulate the networks described in the figure below (on each side of the DUT, router connected to one or more clients/servers networks).

image::images/trex-asr-setup.png[title="TRex/Router setup"]

== Not supported setup description

* Notice that the following setup is *not* supported (Having TRex emulate a bunch of hosts connected by switch to the DUT).
This means that the TRex IP addresses defined in ``generator'' section should be in different network then the DUT addresses
and TRex addresses defined in port_info section.

image::images/trex-not-supported-setup.png[title="Not supported setup"]

== TRex configuration 

* You can specify config file to use by the `--cfg` command line argument
or use the default config file `/etc/trex_cfg.yaml`
* Below is an example of how to configure TRex IP addresses. TRex will issue ARP for default_gw,
and send gratuitous ARP for ip, on each port. This works, starting from TRex version 2.10.
If you want to configure MAC addresses manually (equivalent to static
ARP), or running older TRex version, information is available at the end of the presentation.
Full description of config file parameters can be found in the manual.


[source,python]
----
 - port_limit      : 2
    port_info       :
    - default_gw      : 11.11.11.1 #<1>
      ip              : 11.11.11.2 #<2>
    - default_gw      : 12.12.12.1 #<3>
      ip              : 12.12.12.2 #<4>
----
<1>  TRex port 0 config- should be router's TenG 0/0/0 IP. TRex will try to resolve this address by sending ARP request.
<2>  Next hop of router's TenG 0/0/0. TRex will send gratuitous ARP for this address.
<3>  TRex port 1 config- should be router's TenG 0/0/1 IP. TRex will try to resolve this address by sending ARP request.
<4>  Next hop of router's TenG 0/0/0. TRex will send gratuitous ARP for this address.

== TRex emulated server/client IPs definition in traffic config file

* You specify traffic config file by running TRex with -f <file name>  (TRex stateful mode).
* Examples for client config files exist in TREX_ROOT/scripts/cfg directory.
* Add following section to the traffic config file, to define the range of IPs for clients and servers.

[source,python]
----
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.240"
----

* In this example, there are:
** 255 clients talking to 240 servers

== Router config. Option 1 - static routes

[source,python]
----
interface TenGigabitEthernet0/0/0
 ip address 11.11.11.1 255.255.255.0
!
`
interface TenGigabitEthernet0/0/1
 ip address 12.12.12.1 255.255.255.0
!
ip route 16.0.0.0 255.0.0.0 11.11.11.2  <1>
ip route 48.0.0.0 255.0.0.0 12.12.12.2  <2>
----
<1> Route clients network to TRex server emulation interface.
<2> Route servers network to TRex client emulation interface.

== Router config. Option 2 - PBR part 1

* Router is configured to statically route packets from 0/0/0 to 0/0/1 and from 0/0/1 to 0/0/0.

*Router configuration:*::

[source,python]
----
interface TenGigabitEthernet0/0/0
 ip address 11.11.11.1 255.255.255.0           <1>
 ip policy route-map p1_to_p2                   <2>
 load-interval 30
!

interface TenGigabitEthernet0/0/1
 ip address 12.12.12.1 255.255.255.0           <1>
 ip policy route-map p2_to_p1                   <2>
 load-interval 30
!
----
<1> Configure ip address for the port.
<2> Configure PBR policy - see next slide

== Router config. Option 2 - PBR part 2

[source,python]
----

route-map p1_to_p2 permit 10
 set ip next-hop 12.12.12.2    <1>
!
route-map p2_to_p1 permit 10
 set ip next-hop 11.11.11.2    <2>

----

<1> Set the destination to be 12.12.12.2, in the subnet of TenG 0/0/1.
<2> Set the destination to be 11.11.11.2 , in the subnet to TenG 0/0/0.

== Verify cable connections

* To verify that TRex port-0 is really connected to Router 0/0/0, you can run the following.

...........................................
$./t-rex-64 -f cap2/dns.yaml -m 1  -d 10  -l 1000 --lo --lm 1
...........................................
* It sends packets only from TRex port-0 ( `--lm 1` ) 


* to send only from TRex port 1 do this:
...........................................
$./t-rex-64 -f cap2/dns.yaml -m 1  -d 10  -l 1000 --lo --lm 2
...........................................

* If you are connected to a switch, you must send packets from both directions for few seconds first, to allow
the switch to learn the MAC addresses of both sides.

...........................................
$./t-rex-64 -f cap2/dns.yaml -m 1  -d 10  -l 1000 
...........................................

== MAC based configuration

* If you use TRex version older than 2.10, or wish to have MAC based configuration, TRex config
file must contain the following (instead of the ``ip'' and ``default_gw'').
[source,python]
----
 - port_limit      : 2
    port_info       :  # set eh mac addr
    - dest_mac        :   [0x0,0x0,0x0,0x1,0x0,0x0] 
      src_mac         :   [0x0,0x0,0x0,0x2,0x0,0x0] 
    - dest_mac        :   [0x0,0x0,0x0,0x3,0x0,0x0] 
      src_mac         :   [0x0,0x0,0x0,0x4,0x0,0x0] 
----
=============================================================================
.  Should be Router's TenG 0/0/0 mac-address.
.  Router should be configured to send to this mac-address.
.  Should be Router's TenG 0/0/1 mac-address.
.  Router should be configured to send to this mac-address.
=============================================================================

* On the router side, you must add the following static ARP configuration.

[source,python]
----
 arp 12.12.12.2 0000.0002.0000 ARPA  #<1>
 arp 11.11.11.2 0000.0004.0000 ARPA  #<2>
----
<1> TRex port 0 source mac-address.
<2> TRex port 1 source mac-address.

== Linux config

* Assuming the same setup with Linux as DUT instead of the router, you can do the following.
* Configure IPs of Linux interfaces to 12.12.12.1 and 11.11.11.1
[source,python]
----
route add -net 48.0.0.0 netmask 255.0.0.0 gw 12.12.12.2
route add -net 16.0.0.0 netmask 255.0.0.0 gw 11.11.11.2
----
* If you have MAC based TRex config, you should also add:
[source,python]
----
arp -s 12.12.12.2 00:00:00:04:00:00
arp -s 11.11.11.2 00:00:00:04:00:00
----

== Static route configuration - IPV6

[source,python]
----
interface TenGigabitEthernet1/0/0
 ip address 11.11.11.1 255.255.255.0
 ip policy route-map p1_to_p2
 load-interval 30                        
 ipv6 enable                                                  #<1>
 ipv6 address 2001:DB8:1111:2222::1/64                        #<2>
 ipv6 policy route-map ipv6_p1_to_p2                          #<3>
!


ipv6 unicast-routing                                          #<4>

ipv6 neighbor 3001::2 TenGigabitEthernet0/1/0 0000.0002.0002  #<5>
ipv6 neighbor 2001::2 TenGigabitEthernet0/0/0 0000.0003.0002

route-map ipv6_p1_to_p2 permit 10                             #<6>
 set ipv6 next-hop 2001::2
!
route-map ipv6_p2_to_p1 permit 10
 set ipv6 next-hop 3001::2
!


csi-mcp-asr1k-40(config)#ipv6 route 4000::/64 2001::2                 
csi-mcp-asr1k-40(config)#ipv6 route 5000::/64 3001::2 
----
<1> Enable ipv6
<2> Add  ipv6 address
<3> Add pbr 
<4> Enable ipv6 routing 
<5> Mac-addr setting should be like TRex
<6> PBR configuraion