[ovs-dev] actions in openflow rules

Ben Pfaff blp at ovn.org
Fri Nov 3 17:43:42 UTC 2017


On Thu, Nov 02, 2017 at 11:54:16PM +0000, Haitham Ghalwash wrote:
> I am a little bit confused when interpreting the action part for the following rule,  I got the rule by initiating the "ovs-ofctl dump-flows" on my mininet openflow switch.
> 
> 
> cookie=0x2b000000000000a5, duration=528.939s, table=0, n_packets=176, n_bytes=33116, idle_age=0, priority=2,in_port=1 actions=output:4,output:2
> 
> 
> we have multiple action ports in a certain order, when checking the "restconf/operational/opendaylight-inventory:nodes/" in the opendaylight controller we can see each action with different order
> 
>                 "action": [
>                           { "order": 0,"output-action": {
>                                        "max-length": 65535,
>                                         "output-node-connector": "2" }
>                           {"order": 1, "output-action": {
>                                         "max-length": 65535,
>                                         "output-node-connector": "4" }
>                                                 }
> 
> 
> I am not sure how the packets hitting such entry will be forwarded, are they replicated and send over both? are they load balanced over all ports?

OpenFlow actions are executed in the specified order, so these actions
will output the packet to port 4, then to port 2.  I can't speak for how
OpenDaylight orders or formats actions.


More information about the dev mailing list