User Manual

TRex 105 / 113
In case it is not configured correctly, this error will be seen
VIC error in case of wrong RQ/WQ
Starting TRex v2.15 please wait ...
no client generator pool configured, using default pool
no server generator pool configured, using default pool
zmq publisher at: tcp://
*
:4500
Number of ports found: 2
set driver name rte_enic_pmd
EAL: Error - exiting with code: 1
Cause: Cannot configure device: err=-22, port=0 #
v
1
<1>There is not enough queues
running it with verbose mode with CLI -v 7
[bash]>sudo ./t-rex-64 -f cap2/dns.yaml -c 1 -m 1 -d 10 -l 1000 -v 7
will give move info
EAL: probe driver: 1137:43 rte_enic_pmd
PMD: rte_enic_pmd: Advanced Filters available
PMD: rte_enic_pmd: vNIC MAC addr 00:25:b5:99:00:4c wq/rq 256/512 mtu 1500, max mtu:9190
PMD: rte_enic_pmd: vNIC csum tx/rx yes/yes rss yes intr mode any type min
PMD: rte_enic_pmd: vNIC resources avail: wq 2 rq 2 cq 4 intr 6 #
v
1
EAL: PCI device 0000:0f:00.0 on NUMA socket 0
EAL: probe driver: 1137:43 rte_enic_pmd
PMD: rte_enic_pmd: Advanced Filters available
PMD: rte_enic_pmd: vNIC MAC addr 00:25:b5:99:00:5c wq/rq 256/512 mtu 1500, max
v
1
,
v
1
rq is 2 which mean 1 input queue which is less than minimum required by trex (rq should be at least 5)
7.9.2 Limitations/Issues
• Stateless mode “per stream statistics” feature is handled in software (No hardware support like in X710 card).
• QSFP+ issue
• VLAN 0 Priority Tagging If a vNIC is configured in TRUNK mode by the UCS manager, the adapter will priority tag egress
packets according to 802.1Q if they were not already VLAN tagged by software. If the adapter is connected to a properly
configured switch, there will be no unexpected behavior. In test setups where an Ethernet port of a Cisco adapter in TRUNK
mode is connected point-to-point to another adapter port or connected though a router instead of a switch, all ingress packets
will be VLAN tagged. TRex can work with that see more upstream VIC Upstream the VIC always tags packets with an 802.1p
header.In downstream it is possible to remove the tag (not supported by TRex yet)
7.10 More active flows
From version v2.13 there is a new Stateful scheduler that works better in the case of high concurrent/active flows. In case of
EMIX 70% better performance was observed. In this tutorial there are 14 DP cores & up to 8M flows. There is a special config
file to enlarge the number of flows. This tutorial present the difference in performance between the old scheduler and the new.
7.10.1 Setup details