[OPNFLWPLUG-309] Table Id could not specified when using IFlowProgrammerService or FowardingRulemanager to Programm Flow Created: 18/Oct/14  Updated: 27/Sep/21  Resolved: 07/Jun/15

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

Type: Bug
Reporter: Swarvanu Sengupta Assignee: Swarvanu Sengupta
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 2215

 Description   

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



 Comments   
Comment by Michal Rehak [ 21/Oct/14 ]

Hi Swarvanu,
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.

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?

Thank you.

Comment by Swarvanu Sengupta [ 26/Oct/14 ]

Hi Michal,

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.

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.

I'm not sure how I could use MDSAL api from a ADSAL plugin. Is it even possible ?

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.

Thanks and Regards,
Swarvanu Sengupta

Comment by Swarvanu Sengupta [ 26/Oct/14 ]

(In reply to Swarvanu Sengupta from comment #2)
> Hi Michal,
>
> 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.
>
> 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.
>
> I'm not sure how I could use MDSAL api from a ADSAL plugin. Is it even
> possible ?
>
> 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.
>
> Thanks and Regards,
> Swarvanu Sengupta

Hi,

I had another query related to the Table Id Specification.

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).

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.

Thanks and regards,
Swarvanu

Comment by Jamo Luhrsen [ 05/Jun/15 ]

Sandeep,

if you have a packet capture handy of the controller sending LLDP packet outs
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.

Comment by Anil Vishnoi [ 07/Jun/15 ]

Hi Swarvanu,

AD-SAL was deprecated in Helium release and will be removed in Lithium release.

So i believe there is no work planned for extending the AD-SAL openflowplugin for OF 1.3.

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