[ovs-dev] [PATCH v1] ipfix: Add ingress and egress interface in exporting flows

[Ryan Moats]

"dev" <dev-bounces at openvswitch.org> wrote on 05/13/2016 03:46:50 AM:

> From: Daniel Benli Ye <daniely at vmware.com>
> To: <bpfaff at vmware.com>, <jpettit at vmware.com>, <wenyuz at vmware.com>,
> <dev at openvswitch.org>
> Cc: Daniel Benli Ye <daniely at vmware.com>
> Date: 05/13/2016 03:49 AM
> Subject: [ovs-dev] [PATCH v1] ipfix: Add ingress and egress
> interface in exporting flows
> Sent by: "dev" <dev-bounces at openvswitch.org>
>
> In virtual evironment, IPFIX is unable to differentiate flows
> between pair of VMs on different virtual network if their IP/mac
> are same.
>
> Network:
>     VM1 <---- VNI1 ----> VM3
>     VM2 <---- VNI2 ----> VM4
>
>     In terms of IP/mac:
>         VM1 == VM2
>         VM3 == VM4
>
> Send 10 packets each from VM1 - VM3 and VM2 - VM4
> Expectation:
> - Normal IPFIX record for 10 packets from VM1-VM3
> - Tunnel IPFIX record for 10 packets from VM1-VM3
> - Normal IPFIX record for 10 packets from VM2-VM4
> - Tunnel IPFIX record for 10 packets from VM2-VM4
> What really is:
> - Normal IPFIX record for 20 packets from VM1-VM3 (or VM2-VM4)
> - Tunnel IPFIX record for 10 packets from VM1-VM3
> - Tunnel IPFIX record for 10 packets from VM2-VM4
> IPFIX is unable to differentiate that VM1-VM3 and VM2-VM4 are actually
> 2 different flows for normal record.
>
> Add ingress and egress interface which are the ofp_port in the OVS
> bridge to differentiate the flows above.
>
> Signed-off-by: Daniel Benli Ye <daniely at vmware.com>
> ---

This looks like it will work, but before I give it an Ack,
I'm wondering if it makes sense to add the above scenario as
a unit test case along with this patch...

Ryan Moats