PROX Changes - msturagit66/samplevnf GitHub Wiki

In NFV platform performance testing setups like the one illustrated in the following diagram, where the traffic generator is deployed in a dedicated server (or dedicated appliance hardware) that is connected to the PROX (DUT) through switches and routers and may be using VRFs, it is necessary that the PROX properly reply to the ARP requests. We then chose to configure PROX in Routing mode and l3 sub mode.

The traffic generator can be TREX or any other, such as IXIA or Spirent.

When configured in routing mode and sub mode l3, the original code always trigger an ARP request to the main transmit port configured for the core that received the packet to be routed. However, the destination or the gateway may not be on that port. Therefore it is more appropriate to directly leverage the lua table and send the packets to the MAC address of the matching next hop, without triggering an ARP request on the wrong port. Changes have been made to address this problem.

Another aspect is that of configuring multiple Rx and Tx queues independently for the PROX, when configured in Routing mode and l3 sub mode. This is important to test the VMware Enhanced Data Path (EDP) switch performances emulating CNFs or VNFs that implement Rx and Tx queues, as well as verify RSS improvements. To achieve this behavior we use an architecture that leverages load balancer and workers, each configured with different number of cores. Changes have been made to make l3 working when receiving from rx software rings.