This is similar to CSIT-1936, but different Trex error and different NIC.
Seen both with rdma_core [0] and mlx5 [1].
Only in coverage, as we do not run this combination in trending.

The error:
Traceback (most recent call last):
File "/tmp/openvpp-testing/GPL/tools/trex/trex_stl_profile.py", line 341, in <module>
main()
File "/tmp/openvpp-testing/GPL/tools/trex/trex_stl_profile.py", line 326, in main
simple_burst(
File "/tmp/openvpp-testing/GPL/tools/trex/trex_stl_profile.py", line 210, in simple_burst
client.stop()
File "/opt/trex-core-3.03/scripts/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py", line 51, in wrap2
ret = f(*args, **kwargs)
File "/opt/trex-core-3.03/scripts/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py", line 48, in wrapper
return func(self, *args, **kwargs)
File "/opt/trex-core-3.03/scripts/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py", line 894, in stop
raise TRexError(rc)
trex.common.trex_exceptions.TRexError: Port 0 : *** *** [RPC] - Failed to send message to server general exception
Port 1 : *** Not connected to server

[0] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-coverage-2406-2n-clx/8/log.html.gz#s1-s1-s1-s1-s4-t5-k2-k9-k24-k11
[1] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-coverage-2406-2n-clx/20/log.html.gz#s1-s1-s1-s1-s1-t4-k2-k9-k26-k11