User Manual

TRex 48 / 113
• IP end range.
• Initiator side configuration: Parameters affecting packets sent from client side.
• Responder side configuration: Parameters affecting packets sent from server side.
Note
It is important to understand that this is complimentary to the client generator configured per profile. It only defines how the
clients will be spread between clusters.
In the following example, a profile defines a client generator.
[bash]>cat cap2/dns.yaml
- 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
Goal:
• Create two clusters with 4 and 3 devices, respectively.
• Send 80% of the traffic to the upper cluster and 20% to the lower cluster. Specify the DUT to which the packet will be sent by
MAC address or IP. (The following example uses the MAC address. The instructions after the example indicate how to change
to IP-based.)
Create the following cluster configuration file:
#
# Client configuration example file
# The file must contain the following fields
#
# ’vlan’ - if the entire configuration uses VLAN,
# each client group must include vlan
# configuration
#
# ’groups’ - each client group must contain range of IPs
# and initiator and responder section
# ’count’ represents the number of different DUTs
# in the group.
#
# ’true’ means each group must contain VLAN configuration. ’false’ means no VLAN config ←-
allowed.
vlan: true
groups:
- ip_start : 16.0.0.1
ip_end : 16.0.0.204