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-309 OpenFlowPlugin <p>ADSAL Flow Programming Service and Forwarding Rule Manager does not support the Table-id specification. So by default it assumes Table0. As per OF 1.3 table ID specification must be added</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-309

Table Id could not specified when using IFlowProgrammerService or FowardingRulemanager to Programm Flow

Bug Resolved Won't Do Swarvanu Sengupta Swarvanu Sengupta Sat, 18 Oct 2014 15:54:43 +0000 Mon, 27 Sep 2021 09:01:22 +0000 Sun, 7 Jun 2015 14:25:58 +0000 General 0 4 <p>Hi Swarvanu,<br/> AD-SAL models, apps and plugins are aimed on OF-1.0. Extending them in order to support OF-1.3 is one possible way. The other is to migrate third part app to MD-SAL API.</p> <p>Could you share your usecase a bit? Is it necessary to add table id into AD-SAL? Would it be unreal to migrate the app?</p> <p>Thank you.</p> <p>Hi Michal,</p> <p>We are trying to write a plugins for basic network visualization (quite like VNP (Virtual Network Platform) by NEC). We have developed the plugins in ADSAL, and we are using mainly Forwarding Rule Manager to install the flow. </p> <p>By specifying rules in Multiple tables gives us the freedom to do multiple operation in a single rule. Like putting/stripping vlan id and forwarding packets to specific port etc.</p> <p>I'm not sure how I could use MDSAL api from a ADSAL plugin. Is it even possible ?</p> <p>But as per ADSAL I think the table id specification should be there, as it should support the OF 1.3 specification even if we have MDSAL as an alternatives. I'm not sure but I think otherwise we have to move our whole plugin in MDSAL.</p> <p>Thanks and Regards,<br/> Swarvanu Sengupta</p> <p> (In reply to Swarvanu Sengupta from comment #2)<br/> &gt; Hi Michal,<br/> &gt; <br/> &gt; We are trying to write a plugins for basic network visualization (quite like<br/> &gt; VNP (Virtual Network Platform) by NEC). We have developed the plugins in<br/> &gt; ADSAL, and we are using mainly Forwarding Rule Manager to install the flow. <br/> &gt; <br/> &gt; By specifying rules in Multiple tables gives us the freedom to do multiple<br/> &gt; operation in a single rule. Like putting/stripping vlan id and forwarding<br/> &gt; packets to specific port etc.<br/> &gt; <br/> &gt; I'm not sure how I could use MDSAL api from a ADSAL plugin. Is it even<br/> &gt; possible ?<br/> &gt; <br/> &gt; But as per ADSAL I think the table id specification should be there, as it<br/> &gt; should support the OF 1.3 specification even if we have MDSAL as an<br/> &gt; alternatives. I'm not sure but I think otherwise we have to move our whole<br/> &gt; plugin in MDSAL.<br/> &gt; <br/> &gt; Thanks and Regards,<br/> &gt; Swarvanu Sengupta</p> <p>Hi,</p> <p>I had another query related to the Table Id Specification. </p> <p>Currently Flow Manager and Flow Programmer Service doesn't really care about what type of plugins is used underneath. I that case the API set should be uniform (currently how it is). </p> <p>Now table id specification is mainly a OF 1.3 feature. So in that case what will be the API and how its going behave with other plugins for other switch keeping the uniform API set in mind.</p> <p>Thanks and regards,<br/> Swarvanu</p> <p>Sandeep,</p> <p>if you have a packet capture handy of the controller sending LLDP packet outs<br/> before and after this issue, could you please attach? I know you noticed that only one port was getting a packet out, instead of both.</p> <p>Hi Swarvanu,</p> <p>AD-SAL was deprecated in Helium release and will be removed in Lithium release.</p> <p>So i believe there is no work planned for extending the AD-SAL openflowplugin for OF 1.3.</p> Development External issue ID 2215 External issue URL Rank 0|i030cv: