[OPNFLWPLUG-274] of-flow: flows not added to the switch/device Created: 12/Sep/14  Updated: 27/Sep/21  Resolved: 19/Sep/14

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Peter Gubka Assignee: Martin Bobak
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 1846

 Description   

odl:
http://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distributions-base/0.2.0-SNAPSHOT/distributions-base-0.2.0-20140912.112728-708-osgipackage.zip

1) start odl
2) start ovs 2.0.0 with mininet 2.1.0
3) POST on /restconf/config/opendaylight-inventory:nodes/node/openflow:${switch_idx}/table/${table_id}, data=${data}
4) chack switch, no flow is added

you can take flows from integration.git test/csit/variables/xmls
files: f26.xml; 27,28,37,39,40,44 (probably some more, i havent pass through the all files yet)

i tried cpqd switch for f26 and f27;
f26 was not added nor to cpqd
f27 was added to cpqd

i expected all mentioned flows(26,27,28,37,39,40,44) to be present on the ovs switch

 Comments   
Comment by Martin Bobak [ 19/Sep/14 ]

This issue seems to be related to implementation of OVS which doesn't validate input XML correctly. I was observing packets using wireshark and after writing flow to config ds I could see OFPT_FLOW_MC followed by OPT_ERROR.

Code: Unsupported field type in the match - OFPBMC_BAD_FIELD (0x0006)

04:0e:00:b0:00:00:00:10:00:00:00:00:00:00:00:1a:00:00:00:00:00:00:00:ff:02:00:01:2c:02:58:00:1a:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:01:00:00:00:01:00:6f:80:00:0a:02:86:dd:80:00:10:01:3c:80

After testing this on cpqd, everything works fine.

Comment by Peter Gubka [ 19/Sep/14 ]

Is f26.xml added to cpqd switch too?
I havent added f26 not ro cpqd switch.

Comment by Peter Gubka [ 19/Sep/14 ]

Update on the test side needed.

Generated at Wed Feb 07 20:32:02 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.