01-30-2022 02:14 PM - edited 01-30-2022 04:29 PM
Hello
My goal is to run TRex 4.5.6 GUI, and therefore I have stuck with Trex 2.87 has the last version that still support that API for the GUI.
OS is CentOS 7.6.1810 (64bit) -
I ran an update to reach CentOS 7.9 and same problem persists.
However, neither the 2.86 and 2.87 versions will start up, complaining about my VMWare vmxnet adapters.
The strange thing is, that the latest TRex 2.93 has no issues. But I cannot use 2.93 with the GUI due to the API incompatibility.
Any ideas what this means?
[root@trex02 v2.87]# ./t-rex-64 -i Starting Scapy server..... Scapy server is started The ports are bound/configured. Starting TRex v2.87 please wait ... set driver name net_vmxnet3 driver capability : TSO set dpdk queues mode to ONE_QUE Number of ports found: 4 zmq publisher at: tcp://*:4500 vmxnet3_v4_rss_configure(): Set RSS fields (v4) failed: 1 vmxnet3_dev_start(): Failed to configure v4 RSS vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL vmxnet3_dev_start(): Device activation: UNSUCCESSFUL EAL: Error - exiting with code: 1 Cause: rte_eth_dev_start: err=-22, port=0 Killing Scapy server... Scapy server is killed [root@trex02 v2.87]#
The Hypervisor is a UCS C220 M5 and we have a VIC 1457 (with port-channel removed) and 4 virtual interfaces.
The adapters are presented to ESXi 7.0.1 as 4 x VMXNET3 adapters and DPDK detection works:
[root@trex02 v2.87]# ./dpdk_setup_ports.py -s Network devices using DPDK-compatible driver ============================================ 0000:04:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3,vfio-pci,uio_pci_generic 0000:0c:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3,vfio-pci,uio_pci_generic 0000:13:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3,vfio-pci,uio_pci_generic 0000:1b:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3,vfio-pci,uio_pci_generic Network devices using kernel driver =================================== 0000:0b:00.0 'VMXNET3 Ethernet Controller' if=ens192 drv=vmxnet3 unused=igb_uio,vfio-pci,uio_pci_generic *Active* Other network devices ===================== <none> [root@trex02 v2.87]#
On the same CentOS I can get the TRex 2.93 version to work just fine
[root@trex02 v2.93]# ./t-rex-64 -i Starting Scapy server.... Scapy server is started The ports are bound/configured. Starting TRex v2.93 please wait ... set driver name net_vmxnet3 driver capability : TSO set dpdk queues mode to ONE_QUE Number of ports found: 4 zmq publisher at: tcp://*:4500 wait 1 sec . port : 0 ------------ link : link : Link Up - speed 10000 Mbps - full-duplex promiscuous : 0 port : 1 ------------ link : link : Link Up - speed 10000 Mbps - full-duplex promiscuous : 0 port : 2 ------------ link : link : Link Up - speed 10000 Mbps - full-duplex promiscuous : 0 port : 3 ------------ link : link : Link Up - speed 10000 Mbps - full-duplex promiscuous : 0 number of ports : 4 max cores for 2 ports : 1 tx queues per port : 3 <<< rest deleted >>>
03-28-2022 07:21 AM
If you are using source please see this link .
If you are not strict in using VMXNET3, you can change the interface to E1000E and problem should gone.
03-28-2022 01:21 PM
I have since been using v2.95 and that has no issues with VMXNET3. In my early days of learning TRex I was using the GUI and hence was bound to those older versions. But now I am doing all this stuff via CLI.
kind regards
Arne
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide