User Manual

TRex 49 / 113
initiator :
vlan : 100
dst_mac : "00:00:00:01:00:00"
responder :
vlan : 200
dst_mac : "00:00:00:02:00:00"
count : 4
- ip_start : 16.0.0.205
ip_end : 16.0.0.255
initiator :
vlan : 101
dst_mac : "00:00:01:00:00:00"
responder:
vlan : 201
dst_mac : "00:00:02:00:00:00"
count : 3
The above configuration divides the generator range of 255 clients to two clusters. The range of IPs in all groups in the client
configuration file must cover the entire range of client IPs from the traffic profile file.
MAC addresses will be allocated incrementally, with a wrap around after “count” addresses.
Example:
Initiator side (packets with source in 16.x.x.x net):
• 16.0.0.1 → 48.x.x.x - dst_mac: 00:00:00:01:00:00 vlan: 100
• 16.0.0.2 → 48.x.x.x - dst_mac: 00:00:00:01:00:01 vlan: 100
• 16.0.0.3 → 48.x.x.x - dst_mac: 00:00:00:01:00:02 vlan: 100
• 16.0.0.4 → 48.x.x.x - dst_mac: 00:00:00:01:00:03 vlan: 100
• 16.0.0.5 → 48.x.x.x - dst_mac: 00:00:00:01:00:00 vlan: 100
• 16.0.0.6 → 48.x.x.x - dst_mac: 00:00:00:01:00:01 vlan: 100
Responder side (packets with source in 48.x.x.x net):
• 48.x.x.x → 16.0.0.1 - dst_mac(from responder) : "00:00:00:02:00:00" , vlan:200
• 48.x.x.x → 16.0.0.2 - dst_mac(from responder) : "00:00:00:02:00:01" , vlan:200
and so on.
The MAC addresses of DUTs must be changed to be sequential. Another option is to replace: dst_mac :<ip-address>
with:
next_hop :<ip-address>
For example, the first group in the configuration file would be:
- ip_start : 16.0.0.1
ip_end : 16.0.0.204
initiator :
vlan : 100
next_hop : 1.1.1.1
src_ip : 1.1.1.100