[OPNFLWPLUG-14] OSGI CLI Plugin unit tests 'addMDFlow openflow:1 f#' does not work with OVS mininet Created: 08/Jan/14  Updated: 27/Sep/21  Resolved: 20/Jan/14

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

Type: Bug
Reporter: Jan Medved Assignee: Deepthi V V
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: Macintosh

External issue ID: 273
Priority: High

 Description   

after issuing commands 'addMDFlow openflow:1 f1' to run OF1.3 tests, i get the following status messages:

Status of Flow Data Loaded Transaction: COMMITED
osgi> 2014-01-08 08:27:05.099 PST [nioEventLoopGroup-9-1] INFO o.o.o.p.impl.core.OFFrameDecoder - OF Protocol message received, type:1
2014-01-08 08:27:05.101 PST [pool-25-thread-1] ERROR o.o.o.o.m.c.t.ErrorTranslator - Error Message received: type=2[BADACTION], code=4[BADOUTPORT], data=X?

�������
�
[04 0e 00 58 00 00 00 3f 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 0a 02 00 00 00 00 00 00 02 ff ff ff ff 00 00 ff ff 00 00 00 02 00 01 00 00 00 01 00 16 80 00 0a 02 08 00 80 00 19 08 0a 00 ]
2014-01-08 08:27:05.101 PST [pool-22-thread-5] INFO o.o.c.sal.binding.impl.NotifyTask - Delivering notification NodeErrorNotification [_code=4, _data=X?

�������
�
, _type=BadAction, _transactionId=TransactionId [_value=63], augmentation=[]] to org.opendaylight.openflowplugin.test.OpenflowpluginTestCommandProvider$FlowEventListener$$Broker$ListenerInvoker@476ab2ae
2014-01-08 08:27:05.101 PST [pool-22-thread-4] INFO o.o.c.sal.binding.impl.NotifyTask - Delivering notification NodeErrorNotification [_code=4, _data=X?

�������
�
, _type=BadAction, _transactionId=TransactionId [_value=63], augmentation=[]] to org.opendaylight.controller.sal.compatibility.FlowProgrammerAdapter$$Broker$ListenerInvoker@491bcad7
Error notification flow Xid.........................63
-----------------------------------------------------------------------------------
2014-01-08 08:27:05.101 PST [pool-22-thread-4] INFO o.o.c.sal.binding.impl.NotifyTask - Notification delivered NodeErrorNotification [_code=4, _data=X?

�������
�
, _type=BadAction, _transactionId=TransactionId [_value=63], augmentation=[]] to org.opendaylight.controller.sal.compatibility.FlowProgrammerAdapter$$Broker$ListenerInvoker@491bcad7
2014-01-08 08:27:05.101 PST [pool-22-thread-5] INFO o.o.c.sal.binding.impl.NotifyTask - Notification delivered NodeErrorNotification [_code=4, _data=X?

�������

Mininet does not like the command (output port specified with a non-forwarding action). This was supposed to be fixed earlier. This behavior is similar to other OF commands

 Comments   
Comment by Deepthi V V [ 15/Jan/14 ]

As per Openflow 1.3 spec [pg 66]:
The out_port and out_group fields optionally filter the scope of OFPFC_DELETE and
OFPFC_DELETE_STRICT messages by output port and group. These fields are ignored by OFPFC_ADD, OFPFC_MODIFY or OFPFC_MODIFY_STRICT messages.

Also, if you try adding flow to ovs with command:
sudo ovs-ofctl -O Openflow13 add-flow s1 "table=0, priority=5109, out_port=1, dl_type=0x800, nw_src=10.1.1.1, action=goto_table:1"

Statistics:
sudo ovs-ofctl -O Openflow13 dump-flows s1
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=174.085s, table=0, n_packets=0, n_bytes=0, priority=5109,ip,in_port=1,nw_src=10.1.1.1 actions=goto_table:1

You can see that OVS ignores out_port as per the spec.

Comment by Jan Medved [ 18/Jan/14 ]

Your description is correct, but it does not address the problem. Mininet is still unusable with the OSGI test commands. Can you guys please fix?

Comment by Prasanna Huddar [ 20/Jan/14 ]

It looks like mininet issue.

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