Hi Daniel.
As I understand it, the goal is to translate these OpenFlow actions:
sample(sampling_port=1), sample(sampling_port=2), 1, 2
into these datapath actions:
set(tunnel(...)), sample(...), 1,
set(tunnel(...)), sample(...), 7471
(For readability, I'm adding line breaks and omittin
Hi Ben,
Yes, my first idea is to do adjust_sample_acion() action in
commit_odp_tunnel_action(), but it can hardly
handle the problem that if there are two or more user world sample action and
each has a sampling_port, like the
last case in my new added testing. We add a flow in the user world l
On Fri, Jun 10, 2016 at 07:57:49PM +0800, Benli Ye wrote:
> Add support to export tunnel information for flow-based IPFIX.
Thanks a lot for the new version.
There is an easier way to create the records we want in OVSDB,
especially if we apply the patch I just sent:
https://patchwork.ozlab
Add support to export tunnel information for flow-based IPFIX.
The original steps to configure flow level IPFIX:
1) Create a new record in Flow_Sample_Collector_Set table:
'ovs-vsctl -- create Flow_Sample_Collector_Set id=1 bridge="Bridge UUID"'
2) Add IPFIX configuration which is re
