In this setting, the 2 physical interfaces for data plane traffic are simply hooked to the UCS-B fabric interconnect (no need to connect to a switch).

+

+Troubleshooting

+===============

+

+TrafficClientException: End-to-end connectivity cannot be ensured

+------------------------------------------------------------------

+Prior to running a benchmark, NFVbench will make sure that traffic is passing in the service chain by sending a small flow of packets in each direction and verifying that they are received back at the other end.

+This exception means that NFVbench cannot pass any traffic in the service chain.

+

+The most common issues that prevent traffic from passing are:

+- incorrect wiring of the NFVbench/TRex interfaces

+- incorrect vlan_tagging setting in the NFVbench configuration, this needs to match how the NFVbench ports on the switch are configured (trunk or access port)

+ - if the switch port is configured as access port, you must disable vlan_tagging in the NFVbench configuration

+ - of the switch port is configured as trunk (recommended method), you must enable it