[ovs-dev] Failed to trace path into open flow groups

Ben Pfaff blp at ovn.org
Mon Nov 27 19:09:51 UTC 2017


On Mon, Nov 27, 2017 at 04:24:47PM +0800, Yongsheng Gong wrote:
> Hi,
> 
> Ovs version 2.5.2:
> Os: ubuntu 16.04
> 
> I have flows which in open flow groups, and I want to trace the path
> of one kind of flow to know how it is got to a certain open flow port:

I think that this is more of a bug in tracing write_actions().  It's
fixed in 2.8.0, which reports this sort of thing, e.g.:

    blp at sigabrt:~/nicira/ovs/_build(0)$ make sandbox
    ...
    blp at sigabrt:~/nicira/ovs/_build(0)$ ovs-vsctl add-br br0
    blp at sigabrt:~/nicira/ovs/tutorial(0)$ ovs-ofctl -OOpenflow11 add-flow br0 'priority=65535,actions=write_actions(1)'
    blp at sigabrt:~/nicira/ovs/tutorial(0)$ ovs-appctl ofproto/trace br0 in_port=local
    Flow: in_port=LOCAL,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x0000

    bridge("br0")
    -------------
     0. priority 65535
        write_actions(output:1)
         -> action set is: output:1
    --. Executing action set:
        output:1
         >> Nonexistent output port

    Final flow: in_port=LOCAL,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x0000
    Megaflow: recirc_id=0,eth,in_port=LOCAL,dl_type=0x0000
    Datapath actions: drop
    blp at sigabrt:~/nicira/ovs/tutorial(0)$ 


More information about the dev mailing list