[ovs-discuss] question about ipfix

Ray Li rayli1107 at gmail.com
Tue Jun 5 22:12:30 UTC 2018


Any idea about this?
Thanks,
Ray

On Tue, Jun 5, 2018 at 1:33 AM, Ray Li <rayli1107 at gmail.com> wrote:

> I'm testing ipfix on OVS, but I can't get it to work for some reason. I'm
> running OVS 2.5.2
>
> Here's my OVS output. I've left out the irrelevant fields
>
> # ovs-vsctl list Flow_Sample_Collector_Set
> _uuid               : 5a4dacb6-034d-416a-861b-843a0f63bc9f
> bridge              : a1cfae07-227f-471b-a81a-c874eddc6b62
> external_ids        : {}
> id                  : 1
> ipfix               : 460d8e4f-3404-4dc6-a960-706a728d3f3c
>
>
> # ovs-vsctl list ipfix
> _uuid               : 460d8e4f-3404-4dc6-a960-706a728d3f3c
> cache_active_timeout: []
> cache_max_flows     : []
> external_ids        : {}
> obs_domain_id       : []
> obs_point_id        : []
> other_config        : {}
> sampling            : 16
> targets             : ["192.168.5.2:10000"]
>
> # ovs-vsctl list bridge a1cfae07-227f-471b-a81a-c874eddc6b62
> _uuid               : a1cfae07-227f-471b-a81a-c874eddc6b62
> ipfix               : []
> name                : br.mx
>
> # ovs-ofctl dump-flows br.mx
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=272.404s, table=0, n_packets=18392,
> n_bytes=14687347, idle_age=0, priority=1,in_port=2
> actions=sample(probability=65535,collector_set_id=1,obs_
> domain_id=20000,obs_point_id=30000),output:1
>
> I'm assuming that probability=65535 means that every packet gets sampled,
> according to OVS docs.
> As you can see, there are traffic hitting the sample() action but when I
> attach tcpdump to the interface I don't see any ipfix traffic. I've
> disabled the firewall on this machine, and the tcpdump shows other traffic
> to and from 192.168.5.2, so there shouldn't be any network issue.
>
> Am I missing something?
>
> Thanks,
> Ray
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180605/6e0e45bf/attachment.html>


More information about the discuss mailing list