https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OPNFLWPLUG-263 OpenFlowPlugin <p>When I try to create a flow via restconf with IN_PORT as the action I see that no flow mod is sent to the corresponding switch (via pkt capture on mininet vm running OVS). Also in the OSGI console, the following errors are seen:</p> <p>2014-09-05 14:58:33.456 PDT <span class="error">&#91;OFRpc-2&#93;</span> ERROR o.o.o.o.m.c.s.c.ActionConvertor - Invalid Port specified null for Output Action for OF version:OF13<br/> 2014-09-05 14:58:33.456 PDT <span class="error">&#91;OFRpc-2&#93;</span> ERROR o.o.o.o.m.c.s.c.ActionConvertor - Invalid Port specified null for Output Action for OF version:OF13<br/> 2014-09-05 14:58:33.456 PDT <span class="error">&#91;nioEventLoopGroup-12-6&#93;</span> WARN o.o.o.protocol.impl.core.OFEncoder - Message serialization failed: null</p> <p>Here is the flow_mod XML:</p> <p>&lt;flow xmlns="urn:opendaylight:flow:inventory"&gt;&lt;instructions&gt;&lt;instruction&gt;&lt;order&gt;0&lt;/order&gt;&lt;apply-actions&gt;&lt;action&gt;&lt;order&gt;0&lt;/order&gt;&lt;output-action&gt;&lt;output-node-connector&gt;IN_PORT&lt;/output-node-connector&gt;&lt;/output-action&gt;&lt;/action&gt;&lt;/apply-actions&gt;&lt;/instruction&gt;&lt;/instructions&gt;&lt;match&gt;&lt;ethernet-match&gt;&lt;ethernet-type&gt;&lt;type&gt;0x800&lt;/type&gt;&lt;/ethernet-type&gt;&lt;ethernet-source&gt;&lt;address&gt;00:ab:cd:ef:01:23&lt;/address&gt;&lt;/ethernet-source&gt;&lt;ethernet-destination&gt;&lt;address&gt;ff:ff:ff:ff:ff:ff&lt;/address&gt;&lt;/ethernet-destination&gt;&lt;/ethernet-match&gt;&lt;ipv4-source&gt;11.3.0.0/16&lt;/ipv4-source&gt;&lt;ipv4-destination&gt;99.0.0.0/8&lt;/ipv4-destination&gt;&lt;/match&gt;&lt;strict&gt;false&lt;/strict&gt;&lt;hard-timeout&gt;60&lt;/hard-timeout&gt;&lt;idle-timeout&gt;30&lt;/idle-timeout&gt;&lt;flow-name&gt;No Name&lt;/flow-name&gt;&lt;priority&gt;0&lt;/priority&gt;&lt;barrier&gt;false&lt;/barrier&gt;&lt;cookie&gt;0&lt;/cookie&gt;&lt;cookie_mask&gt;0&lt;/cookie_mask&gt;&lt;table_id&gt;22&lt;/table_id&gt;&lt;id&gt;161&lt;/id&gt;&lt;/flow&gt;</p> <p>If it matters, the REST details are a PUT @ /restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/22/flow/161</p> <p>Attached are some robot test logs if it helps.</p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-263

IN_PORT Action flow mod not working

Bug Resolved Won't Do Jamo Luhrsen Jamo Luhrsen Fri, 5 Sep 2014 23:09:46 +0000 Mon, 27 Sep 2021 09:01:18 +0000 Thu, 25 Sep 2014 21:20:32 +0000 General Mon, 15 Sep 2014 00:00:00 +0000 0 5 <p>Attachment log.html has been added with description: robot log.html file</p> <p>Attachment output.xml has been added with description: robot output.xml</p> <p>Attachment report.html has been added with description: robot report.html file</p> <p>distro used was distributions-base-0.2.0-20140825.175909-538-osgipackage.zip</p> <p>For creation of flow with IN_PORT action via RESTCONF you should set in your XML "output - action" to:</p> <p>&lt;output-action&gt;<br/> &lt;output-node-connector&gt;INPORT&lt;/output-node-connector&gt;<br/> &lt;/output-action&gt;</p> <p>instead of:</p> <p>&lt;output-action&gt;<br/> &lt;output-node-connector&gt;IN_PORT&lt;/output-node-connector&gt;<br/> &lt;/output-action&gt;</p> <p>This change will fix the problem.</p> <p>I can confirm that INPORT works for the action when passing it to the controller, however I think we should stay consistent with the spec, which<br/> says:</p> <p>OFPP_IN_PORT = 0xfffffff8, /* Send the packet out the input port. This<br/> reserved port must be explicitly used<br/> in order to send back out of the input<br/> port. */</p> <p>Also, OVS uses the same format:</p> <p> cookie=0x0, duration=1.021s, table=22, n_packets=0, n_bytes=0, idle_timeout=30, hard_timeout=60, send_flow_rem priority=0,ip,dl_src=00:ab:cd:ef:01:23,dl_dst=ff:ff:ff:ff:ff:ff,nw_src=11.3.0.0/16,nw_dst=99.0.0.0/8 actions=IN_PORT</p> <p>Is it possible/worthwhile to change?</p> <p>Thanks.</p> <p>Moving to Lithium as we have only a week and half for Helium.</p> <p>For Helium we do not plan to implement unified action values for flows because of lack of time.<br/> However, it is not bad idea to change.<br/> It would be best if you create a new enhancement bug for this issue which would be solved in next releases.</p> <p>filed enhancement for Lithium as requested:<br/> <a href="https://bugs.opendaylight.org/show_bug.cgi?id=2095" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=2095</a></p> Development External issue ID 1725 External issue URL ODL SR Target Milestone Rank 0|i0302n: