Dear HPE Community Support Team,
I appreciated your reply.
The issue of mismatch in the version has been resolved as I've changed
the options in switches.
However, the throughput issues have still remained the same regardless
of the openflow version.I am wondering if there is a rate limitation
when the packets are controlled by flow rules on software tables in
2920. Does SW table has lower performance (e.g., packets per second)
than HW table in switches?
When I have checked the throughput (data rate) by using web server,
the bandwidth was only 20 MB/s per an HTTP request.
I've set the rule of changing src_ip or dst_ip in the edge switch and
it leads that flow rule is added in software table according to your
manual (table_id == 200)
One HTTP request requires about 2900 packets to send the 4 MB bytes of
web pages between a client and a server. A rate-limit at the software
level of switches seems to affect the data limitation when L3
switching is required in switches.
Otherwise, I've checked L2 switching (table_id == 100) based on the
same configuration getting rid of L3 actions in flow rules (changing
src_ip or dst_ip) and its performance has marked about 115 MB/s. I
have guessed that L2 switching could cover full bandwidth of links
while L3 switching seems to have limitations to populate packets to
related output ports.
In summary, could you please confirm me if both HW and SW switching in
2920 can guarantee the same performance or not. If not, how to improve
the performance in terms of a data rate in transit when flow rules are
added into software table.
For your information, I'd like to list up the configuration of my experiment.
1. SDN controller: Ryu
2. Switch: HPE 2920-24G switches
Thank you for your support in advance.
Best regards,
Minjune Kim