Date   

Re: Opendaylight

Ajay Chopra <chopraa@...>
 

Hi ,I am now able to add the flows .Can you tell me what all flows are needed to be added so that I can enable ping between two hosts .

-Ajay

From: Ajay Chopra
Sent: 26 April 2017 14:57
To: 'ccain@...' <ccain@...>; 'openflowjava-dev@...' <openflowjava-dev@...>
Subject: Opendaylight

 

Hi Opendaylight team ,

 

I am working on opendaylight controller ,can you help me in adding the flows using postman .

When I add flows  using the http://10.119.162.14:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0 or

Try to get information of flows that are there not able to get the information .

 

Is there any way we need to install some feature to enable the addition of flows ? Getting 404 not found .

 

 

Regards,

Ajay Chopra

 



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------


Opendaylight

Ajay Chopra <chopraa@...>
 

Hi Opendaylight team ,

 

I am working on opendaylight controller ,can you help me in adding the flows using postman .

When I add flows  using the http://10.119.162.14:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0 or

Try to get information of flows that are there not able to get the information .

 

Is there any way we need to install some feature to enable the addition of flows ? Getting 404 not found .

 

 

Regards,

Ajay Chopra

 



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------


ODL Openflow version 1.5 support

Ioakeim Samaras
 

Hello,

I would like to ask when the OpenDaylight will support Openflow protocol version 1.5.

Thank you in advance.

--
Dr. Ioakeim K. Samaras
Ph.D. in Electrical and Computer Engineering
Intracom-Telecom, Software Development Center, Thessaloniki Branch, Greece
Industrial Systems Institute, Greece
E-mail : iosam@...
samaras@...

The information in this e-mail message and any attachments are intended only for the individual or entity to whom it is addressed and may be confidential. If you have received this transmission in error, and you are not an intended recipient, be aware that any copying, disclosure, distribution or use of this transmission or its contents is prohibited. INTRACOM TELECOM and the sender accept no liability for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this email. Views or opinions expressed in this message may be those of the author and may not necessarily represent those of INTRACOM TELECOM.


Re: OPENFLOWJAVA Karaf 4 Migration

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Greetings Mike,
I confirm - openflowjava has been migrated to karaf4 and there is no pending item.

Regards,
Michal

________________________________________
From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Mike McCarthy <mike.cw.mccarthy@...>
Sent: Friday, March 24, 2017 01:36
To: openflowjava-dev@...
Subject: [openflowjava-dev] OPENFLOWJAVA Karaf 4 Migration

Based on our analysis, your project has completed Karaf 4 Migration as
part of the Carbon Simultaneous Release with no additional action
items pending. Please confirm the status of your Karaf 4 Migration
and let us know if there are any other issues, concerns, or red flag.
We would like to thank you in advance for your effort and engagement.

https://git.opendaylight.org/gerrit/#/c/51521/

M
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


OPENFLOWJAVA Karaf 4 Migration

mike.cw.mccarthy@gmail.com
 

Based on our analysis, your project has completed Karaf 4 Migration as
part of the Carbon Simultaneous Release with no additional action
items pending. Please confirm the status of your Karaf 4 Migration
and let us know if there are any other issues, concerns, or red flag.
We would like to thank you in advance for your effort and engagement.

https://git.opendaylight.org/gerrit/#/c/51521/

M


Re: jayRE: Open Day Light controllers

Luis Gomez <ecelgp@...>
 

Hi Ajoy,

405 Method not allowed -> You cannot use PUT method (write) on this URL (operational datastore): http://10.119.162.14:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0

Use this URL (config datastore) instead: http://10.119.162.14:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0

BR/Luis

On Mar 22, 2017, at 5:16 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:

Adding the OpenFlow plugin team.

On Tue, Mar 21, 2017 at 11:55 PM, Ajay Chopra <chopraa@...> wrote:
Hi ,

Please find the attached mail and let me know if we can get solution to below problem .



-Ajay





From: Casey Cain [mailto:ccain@...]
Sent: 22 March 2017 05:44
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers



I would guess it is because your PUT statement isn't properly formatted. However, I can't say that I know. You would need to ask the OpenFlow development team.

openflowjava-dev@...



Regards,

Casey



On Wed, Mar 8, 2017 at 9:55 PM, Ajay Chopra <chopraa@...> wrote:

Gentle reminder .



From: Ajay Chopra
Sent: 09 March 2017 04:27
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: jayRE: Open Day Light controllers



Hi Casey ,



Can you tell me what could be the reason for getting the 405 Method not allowed Error message ?



-Ajay



From: Casey Cain [mailto:ccain@...]
Sent: 07 March 2017 00:05

To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers



You may also want to consider installing odl-l2switch-hosttracker and odl-l2switch-arphandler into ODL.



Best,

Casey



On Mon, Mar 6, 2017 at 10:29 AM, Casey Cain <ccain@...> wrote:

If you wanted to make a flow rules pipeline, it would look something like this:



- ARP type flow rules:

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow116</flow-name>

<id>116</id>

<cookie_mask>255</cookie_mask>

<cookie>103</cookie>

<table_id>0</table_id>

<priority>1024</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<match>

<ethernet-match>

<ethernet-type>

<type>2054</type>

</ethernet-type>

<ethernet-destination>

<address>76:f4:64:79:a1:40</address>

</ethernet-destination>

<ethernet-source>

<address>ff:ff:ff:ff:FF:ff</address>

</ethernet-source>

</ethernet-match>

</match>

</flow>' "http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/flow-node-inventory:table/0/flow/116"



- ICMP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>134</id>

<cookie_mask>255</cookie_mask>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.1.0/24</ipv4-source>

<ipv4-destination>10.0.2.0/24</ipv4-destination>

<ip-match>

<ip-protocol>1</ip-protocol>

</ip-match>

</match>

<hard-timeout>1200</hard-timeout>

<cookie>11</cookie>

<idle-timeout>3400</idle-timeout>

<flow-name>FooXf11</flow-name>

<priority>200</priority>

</flow>' "http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/flow-node-inventory:table/0/flow/134"



- TCP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>119</id>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.2.0/24</ipv4-source>

<ipv4-destination>10.0.1.0/24</ipv4-destination>

<ip-match>

<ip-protocol>6</ip-protocol>

</ip-match>

</match>

<hard-timeout>0</hard-timeout>

<cookie>10</cookie>

<idle-timeout>0</idle-timeout>

<flow-name>flow118</flow-name>

<priority>200</priority>

</flow>' "http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/flow-node-inventory:table/0/flow/119"





On Mon, Mar 6, 2017 at 10:24 AM, Casey Cain <ccain@...> wrote:

The strict tag usually means strictly matching a particular flow - rather than a wildcard match.



I didn't need to specify an ethertype in that example. When you don't specify an ethertype it kind of matches all ethertypes. Unless you specify some IP field - in which it will implicitly assume the ethertype to be 0x800 (IP)



Regards,

Casey



On Mon, Mar 6, 2017 at 9:29 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,



There is no Ethernet type specified ?

Here the difference is that you are mentioning strict as false .



-Ajay

From: Casey Cain [mailto:ccain@...]
Sent: 06 March 2017 22:56
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers



Hello, Ajay.

A proper PUT command should look something more like this:



$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow3</flow-name>

<id>134</id>

<cookie_mask>255</cookie_mask>

<cookie>104</cookie>

<table_id>0</table_id>

<priority>0</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<match>

<in-port>2</in-port>

</match>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

</flow>' "http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/flow-node-inventory:table/0/flow/134"



Regards,

Casey



On Mon, Mar 6, 2017 at 9:22 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,



I have read the tutorial but there is no help ,I am having issue while adding the flows ,please let me know any references regarding the adding the flow . there is an error related to 405 method not allowed .



Ajay



From: Casey Cain [mailto:ccain@...]
Sent: 06 March 2017 21:33
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers



Hello, Ajay.

I am unsure how I can help you further without more information. It seemed that were not setting up your instance correctly for OpenFlow. The guides that I sent you should have given you the correct guidance on how to setup a OpenFlow route in your environment. If you're still unsure on how to proceed, I suggest reviewing the tutorials once again before posting your question on ask.opendaylight.org.



You can also reach out to the OpenFlow development team at openflowjava-dev@...



Regards,

Casey



On Sun, Mar 5, 2017 at 10:24 PM, Ajay Chopra <chopraa@...> wrote:

Hi ,



Any update ?



-Ajay



From: Ajay Chopra
Sent: 03 March 2017 16:20
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



HI ,



Any update ?



-Ajay
Sent: 03 March 2017 12:01
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



Hi Casey cain ,



The PUT command uses http://10.119.162.14:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0 .



-Ajay



From: Casey Cain [mailto:ccain@...]
Sent: 03 March 2017 11:47
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>


Subject: Re: Open Day Light controllers



Hi, Ajay.

I will try to help you moving forward with this issue.

There still seems to be some ambiguity in how you are connected to the switch.

Can you tell me what commands you are currently using for your put command?

Have you searched ask.opendaylight.org or posted your question there yet?



Another good resource for faster answers is our IRC channels.

https://wiki.opendaylight.org/view/IRC







On Thu, Mar 2, 2017 at 10:00 PM, Ajay Chopra <chopraa@...> wrote:

Hi Phil ,



Any update ?



-Ajay

From: Ajay Chopra
Sent: 02 March 2017 11:32
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



Hi Phil ,



Any update ?



-Ajay

From: Ajay Chopra
Sent: 01 March 2017 18:29
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



HI Phil ,



Got the below message when I try to push the Flows into the switch .

Error 405 Method not allowed .

<image001.jpg>



Please let me know how can I overcome it so that I can add the flows .



-Ajay

.

From: Ajay Chopra
Sent: 01 March 2017 11:51
To: 'Phil Robb' <probb@...>
Cc: info@...; Casey Cain <ccain@...>
Subject: RE: Open Day Light controllers



1)Switch is Brocade switch .

2) Yes , I have connectivity .

3) feature:install odl-restconf

feature:install odl-dlux-core

feature:install odl-mdsal-apidocs

feature:install odl-openflowplugin-flow-services-rest

feature:install odl-openflowplugin-flow-services-ui

feature:install odl-dlux-node

feature:install odl-dlux-yangui

feature:install odl-l2switch-switch

4)I am using Postman

5)I am trying to PUT the flows but not able to add the flows .



From: Phil Robb [mailto:probb@...]
Sent: 01 March 2017 09:36
To: Ajay Chopra <chopraa@...>
Cc: info@...; Casey Cain <ccain@...>


Subject: Re: Open Day Light controllers



hello Ajay:



I've cc-ed Casey Cain. Casey can help you to post this question to the OpenDaylight Q&A forum (ask.opendaylight.org) and help make sure you get an answer from the community.



Your question is too vague as of yet for anyone to help though. What switch are you trying to talking to?.... Are you sure you have connectivity to the switch?...What components of ODL did you install via Karaf?... what commands did you issue?.... what return codes did you get from the commands that you issued?.... etc.



When you go to post the question, please be specific with what you are using, what you did, and the results you saw. Otherwise, those that try to help on our Q&A forum won't have enough information to be able to respond.



Best,



Phil.





On Tue, Feb 28, 2017 at 3:35 AM, Ajay Chopra <chopraa@...> wrote:

HI phil,



I have installed open daylight but not able to add flows can u help how to add the flows ?



-Ajay



From: Ajay Chopra
Sent: 21 November 2016 12:36
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>
Subject: RE: Open Day Light controllers



Hello Phil,



I have installed the opendaylight Beryllium controller ,but when I login using web with login/pass as admin.

It is not logging in .

Is there any update there ?due to which I am not able to login .

Can you check at your side ?



-Ajay

From: Ajay Chopra
Sent: 06 July 2016 10:55
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



Gentle reminder .



From: Ajay Chopra
Sent: 05 July 2016 15:29
To: 'Phil Robb' <probb@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers



Can you share the link from where we can download the ODL controller ?



-Ajay

From: Phil Robb [mailto:probb@...]
Sent: 29 June 2016 21:10
To: Ajay Chopra <chopraa@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers



Hey Ajay:



As an open source project, OpenDaylight does not test/certify against any particular hardware. We support OpenFlow, along with many other protocols so to that extent we support Pica8 switches.



Vendors who provide controllers based on OpenDaylight will often test and document what hardware they've tested against, so that may be helpful to you as well.



Best,



Phil.



On Wed, Jun 29, 2016 at 8:16 AM, Ajay Chopra <chopraa@...> wrote:

Gentle Reminder .



From: Ajay Chopra
Sent: 29 June 2016 13:06
To: 'info@...' <info@...>
Cc: Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Open Day Light controllers



Hello OpenDayLight Team ,



Can you share the details of Open Day Light controllers which can support Pica8 or Edge Core Switch ?



-Ajay



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------






--

Phil Robb

Sr. Director Of Technical Operations

OpenDaylight Project

(O) 970-229-5949

(M) 970-420-4292

Skype: Phil.Robb






--

Phil Robb

Executive Director, OpenDaylight Project

VP Operations - Networking & Orchestration, The Linux Foundation

(O) 970-229-5949

(M) 970-420-4292

Skype: Phil.Robb






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6






--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6


_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


Re: jayRE: Open Day Light controllers

Abhijit Kumbhare
 

Adding the OpenFlow plugin team.

On Tue, Mar 21, 2017 at 11:55 PM, Ajay Chopra <chopraa@...> wrote:

Hi ,

Please find the attached mail and let me know if we can get solution to below problem .

 

-Ajay

 

 

From: Casey Cain [mailto:ccain@linuxfoundation.org]
Sent: 22 March 2017 05:44
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

I would guess it is because your PUT statement isn't properly formatted. However, I can't say that I know.  You would need to ask the OpenFlow development team.

 

Regards,

Casey

 

On Wed, Mar 8, 2017 at 9:55 PM, Ajay Chopra <chopraa@...> wrote:

Gentle reminder .

 

From: Ajay Chopra
Sent: 09 March 2017 04:27
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: jayRE: Open Day Light controllers

 

Hi Casey ,

 

Can you tell me what could be the reason for getting the 405 Method not allowed Error message ?

 

-Ajay

 

From: Casey Cain [mailto:ccain@linuxfoundation.org]
Sent: 07 March 2017 00:05

To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

You may also want to consider installing odl-l2switch-hosttracker and odl-l2switch-arphandler into ODL.

 

Best,

Casey

 

On Mon, Mar 6, 2017 at 10:29 AM, Casey Cain <ccain@...> wrote:

If you wanted to make a flow rules pipeline, it would look something like this:

 

- ARP type flow rules:

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow116</flow-name>

<id>116</id>

<cookie_mask>255</cookie_mask>

<cookie>103</cookie>

<table_id>0</table_id>

<priority>1024</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<match>

<ethernet-match>

<ethernet-type>

<type>2054</type>

</ethernet-type>

<ethernet-destination>

<address>76:f4:64:79:a1:40</address>

</ethernet-destination>

<ethernet-source>

<address>ff:ff:ff:ff:FF:ff</address>

</ethernet-source>

</ethernet-match>

</match>

 

-  ICMP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>134</id>

<cookie_mask>255</cookie_mask>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.1.0/24</ipv4-source>

<ipv4-destination>10.0.2.0/24</ipv4-destination>

<ip-match>

<ip-protocol>1</ip-protocol>

</ip-match>

</match>

<hard-timeout>1200</hard-timeout>

<cookie>11</cookie>

<idle-timeout>3400</idle-timeout>

<flow-name>FooXf11</flow-name>

<priority>200</priority>

 

- TCP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>119</id>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.2.0/24</ipv4-source>

<ipv4-destination>10.0.1.0/24</ipv4-destination>

<ip-match>

<ip-protocol>6</ip-protocol>

</ip-match>

</match>

<hard-timeout>0</hard-timeout>

<cookie>10</cookie>

<idle-timeout>0</idle-timeout>

<flow-name>flow118</flow-name>

<priority>200</priority>

 

 

On Mon, Mar 6, 2017 at 10:24 AM, Casey Cain <ccain@...> wrote:

The strict tag usually means strictly matching a particular flow - rather than a wildcard match.

 

I didn't need to specify an ethertype in that example.  When you don't specify an ethertype it kind of matches all ethertypes. Unless you specify some IP field - in which it will implicitly assume the ethertype to be 0x800 (IP)

 

Regards,

Casey

 

On Mon, Mar 6, 2017 at 9:29 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,

 

There is no Ethernet type specified ?

Here the difference is that you are mentioning strict as false .

 

-Ajay

From: Casey Cain [mailto:ccain@linuxfoundation.org]
Sent: 06 March 2017 22:56
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

Hello, Ajay.

A proper PUT command should look something more like this:

 

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow3</flow-name>

<id>134</id>

<cookie_mask>255</cookie_mask>

<cookie>104</cookie>

<table_id>0</table_id>

<priority>0</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<match>

<in-port>2</in-port>

</match>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

 

Regards,

Casey

 

On Mon, Mar 6, 2017 at 9:22 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,

 

I have read  the tutorial but there is no help ,I am having issue while adding the flows ,please let me know any references regarding the adding the flow . there is an error related to 405 method not allowed .

 

Ajay

 

From: Casey Cain [mailto:ccain@linuxfoundation.org]
Sent: 06 March 2017 21:33
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers

 

Hello, Ajay.

I am unsure how I can help you further without more information.  It seemed that were not setting up your instance correctly for OpenFlow.  The guides that I sent you should have given you the correct guidance on how to setup a OpenFlow route in your environment.  If  you're still unsure on how to proceed, I suggest reviewing the tutorials once again before posting your question on ask.opendaylight.org

 

You can also reach out to the OpenFlow development team at openflowjava-dev@lists.opendaylight.org

 

Regards,

Casey

 

On Sun, Mar 5, 2017 at 10:24 PM, Ajay Chopra <chopraa@...> wrote:

Hi ,

 

Any update ?

 

-Ajay

 

From: Ajay Chopra
Sent: 03 March 2017 16:20
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

HI ,

 

Any update ?

 

-Ajay
Sent: 03 March 2017 12:01
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Hi Casey cain ,

 

The PUT command uses http://10.119.162.14:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0 .

 

-Ajay

 

From: Casey Cain [mailto:ccain@linuxfoundation.org]
Sent: 03 March 2017 11:47
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>


Subject: Re: Open Day Light controllers

 

Hi, Ajay.

I will try to help you moving forward with this issue.

There still seems to be some ambiguity in how you are connected to the switch.

Can you tell me what commands you are currently using for your put command?

Have you searched ask.opendaylight.org or posted your question there yet?

 

Another good resource for faster answers is our IRC channels.

 

 

 

On Thu, Mar 2, 2017 at 10:00 PM, Ajay Chopra <chopraa@...> wrote:

Hi Phil ,

 

Any update ?

 

-Ajay

From: Ajay Chopra
Sent: 02 March 2017 11:32
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Hi Phil ,

 

Any update ?

 

-Ajay

From: Ajay Chopra
Sent: 01 March 2017 18:29
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

HI Phil ,

 

Got the below message when I try to push the Flows into the switch .

Error 405 Method not allowed .

 

Please let me know how can I overcome it so that I can add the flows .

 

-Ajay

                                                                                                                                                                                                     .

From: Ajay Chopra
Sent: 01 March 2017 11:51
To: 'Phil Robb' <probb@...>
Cc: info@...; Casey Cain <ccain@...>
Subject: RE: Open Day Light controllers

 

1)Switch is Brocade switch .

2) Yes , I have connectivity .

3) feature:install odl-restconf

    feature:install odl-dlux-core

    feature:install odl-mdsal-apidocs

   feature:install odl-openflowplugin-flow-services-rest

   feature:install odl-openflowplugin-flow-services-ui

   feature:install odl-dlux-node

   feature:install odl-dlux-yangui

   feature:install odl-l2switch-switch

4)I am using Postman

5)I am trying to PUT the flows but not able to add the flows .

 

From: Phil Robb [mailto:probb@linuxfoundation.org]
Sent: 01 March 2017 09:36
To: Ajay Chopra <chopraa@...>
Cc: info@...; Casey Cain <ccain@...>


Subject: Re: Open Day Light controllers

 

hello Ajay:

 

I've cc-ed Casey Cain.  Casey can help you to post this question to the OpenDaylight Q&A forum (ask.opendaylight.org)  and help make sure you get an answer from the community.

 

Your question is too vague as of yet for anyone to help though.  What switch are you trying to talking to?....  Are you sure you have connectivity to the switch?...What components of ODL did you install via Karaf?... what commands did you issue?.... what return codes did you get from the commands that you issued?.... etc.

 

When you go to post the question, please be specific with what you are using, what you did, and the results you saw.  Otherwise, those that try to help on our Q&A forum won't have enough information to be able to respond.

 

Best,

 

Phil.

 

 

On Tue, Feb 28, 2017 at 3:35 AM, Ajay Chopra <chopraa@...> wrote:

HI phil,

 

I have installed open daylight but not able to add flows can u help how to add the flows ?

 

-Ajay

 

From: Ajay Chopra
Sent: 21 November 2016 12:36
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>
Subject: RE: Open Day Light controllers

 

Hello Phil,

 

I have installed the opendaylight Beryllium controller ,but when I login using web with login/pass as admin.

It is not logging in .

Is there any update there ?due to which I am not able to login .

Can you check at your side ?

 

-Ajay

From: Ajay Chopra
Sent: 06 July 2016 10:55
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Gentle reminder .

 

From: Ajay Chopra
Sent: 05 July 2016 15:29
To: 'Phil Robb' <probb@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Can you share the link from where we can download the ODL controller ?

 

-Ajay

From: Phil Robb [mailto:probb@linuxfoundation.org]
Sent: 29 June 2016 21:10
To: Ajay Chopra <chopraa@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers

 

Hey Ajay:

 

As an open source project, OpenDaylight does not test/certify against any particular hardware.  We support OpenFlow, along with many other protocols so to that extent we support Pica8 switches. 

 

Vendors who provide controllers based on OpenDaylight will often test and document what hardware they've tested against, so that may be helpful to you as well.

 

Best,

 

Phil.

 

On Wed, Jun 29, 2016 at 8:16 AM, Ajay Chopra <chopraa@...> wrote:

Gentle Reminder .

 

From: Ajay Chopra
Sent: 29 June 2016 13:06
To: 'info@...' <info@...>
Cc: Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Open Day Light controllers

 

Hello OpenDayLight Team ,

 

Can you share the details of Open Day Light controllers which can support Pica8 or Edge Core Switch  ?

 

-Ajay



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------



 

--

Phil Robb

Sr. Director Of Technical Operations

OpenDaylight Project

Skype: Phil.Robb



 

--

Phil Robb

Executive Director, OpenDaylight Project

VP Operations - Networking & Orchestration, The Linux Foundation

Skype: Phil.Robb



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6


_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev



Re: jayRE: Open Day Light controllers

Ajay Chopra <chopraa@...>
 

Hi ,

Please find the attached mail and let me know if we can get solution to below problem .

 

-Ajay

 

 

From: Casey Cain [mailto:ccain@...]
Sent: 22 March 2017 05:44
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

I would guess it is because your PUT statement isn't properly formatted. However, I can't say that I know.  You would need to ask the OpenFlow development team.

 

Regards,

Casey

 

On Wed, Mar 8, 2017 at 9:55 PM, Ajay Chopra <chopraa@...> wrote:

Gentle reminder .

 

From: Ajay Chopra
Sent: 09 March 2017 04:27
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: jayRE: Open Day Light controllers

 

Hi Casey ,

 

Can you tell me what could be the reason for getting the 405 Method not allowed Error message ?

 

-Ajay

 

From: Casey Cain [mailto:ccain@...]
Sent: 07 March 2017 00:05

To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

You may also want to consider installing odl-l2switch-hosttracker and odl-l2switch-arphandler into ODL.

 

Best,

Casey

 

On Mon, Mar 6, 2017 at 10:29 AM, Casey Cain <ccain@...> wrote:

If you wanted to make a flow rules pipeline, it would look something like this:

 

- ARP type flow rules:

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow116</flow-name>

<id>116</id>

<cookie_mask>255</cookie_mask>

<cookie>103</cookie>

<table_id>0</table_id>

<priority>1024</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<match>

<ethernet-match>

<ethernet-type>

<type>2054</type>

</ethernet-type>

<ethernet-destination>

<address>76:f4:64:79:a1:40</address>

</ethernet-destination>

<ethernet-source>

<address>ff:ff:ff:ff:FF:ff</address>

</ethernet-source>

</ethernet-match>

</match>

 

-  ICMP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>134</id>

<cookie_mask>255</cookie_mask>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.1.0/24</ipv4-source>

<ipv4-destination>10.0.2.0/24</ipv4-destination>

<ip-match>

<ip-protocol>1</ip-protocol>

</ip-match>

</match>

<hard-timeout>1200</hard-timeout>

<cookie>11</cookie>

<idle-timeout>3400</idle-timeout>

<flow-name>FooXf11</flow-name>

<priority>200</priority>

 

- TCP type flow rules

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<installHw>false</installHw>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>2</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

<table_id>0</table_id>

<id>119</id>

<match>

<ethernet-match>

<ethernet-type>

<type>2048</type>

</ethernet-type>

</ethernet-match>

<ipv4-source>10.0.2.0/24</ipv4-source>

<ipv4-destination>10.0.1.0/24</ipv4-destination>

<ip-match>

<ip-protocol>6</ip-protocol>

</ip-match>

</match>

<hard-timeout>0</hard-timeout>

<cookie>10</cookie>

<idle-timeout>0</idle-timeout>

<flow-name>flow118</flow-name>

<priority>200</priority>

 

 

On Mon, Mar 6, 2017 at 10:24 AM, Casey Cain <ccain@...> wrote:

The strict tag usually means strictly matching a particular flow - rather than a wildcard match.

 

I didn't need to specify an ethertype in that example.  When you don't specify an ethertype it kind of matches all ethertypes. Unless you specify some IP field - in which it will implicitly assume the ethertype to be 0x800 (IP)

 

Regards,

Casey

 

On Mon, Mar 6, 2017 at 9:29 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,

 

There is no Ethernet type specified ?

Here the difference is that you are mentioning strict as false .

 

-Ajay

From: Casey Cain [mailto:ccain@...]
Sent: 06 March 2017 22:56
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: jayRE: Open Day Light controllers

 

Hello, Ajay.

A proper PUT command should look something more like this:

 

$ curl -X PUT -u admin:admin -H "Content-Type: application/xml" -H "Cache-Control: no-cache" -d '<flow xmlns="urn:opendaylight:flow:inventory">

<strict>false</strict>

<flow-name>flow3</flow-name>

<id>134</id>

<cookie_mask>255</cookie_mask>

<cookie>104</cookie>

<table_id>0</table_id>

<priority>0</priority>

<hard-timeout>1200</hard-timeout>

<idle-timeout>3400</idle-timeout>

<installHw>false</installHw>

<match>

<in-port>2</in-port>

</match>

<instructions>

<instruction>

<order>0</order>

<apply-actions>

<action>

<order>0</order>

<output-action>

<output-node-connector>3</output-node-connector>

<max-length>60</max-length>

</output-action>

</action>

</apply-actions>

</instruction>

</instructions>

 

Regards,

Casey

 

On Mon, Mar 6, 2017 at 9:22 AM, Ajay Chopra <chopraa@...> wrote:

Hi Casey ,

 

I have read  the tutorial but there is no help ,I am having issue while adding the flows ,please let me know any references regarding the adding the flow . there is an error related to 405 method not allowed .

 

Ajay

 

From: Casey Cain [mailto:ccain@...]
Sent: 06 March 2017 21:33
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers

 

Hello, Ajay.

I am unsure how I can help you further without more information.  It seemed that were not setting up your instance correctly for OpenFlow.  The guides that I sent you should have given you the correct guidance on how to setup a OpenFlow route in your environment.  If  you're still unsure on how to proceed, I suggest reviewing the tutorials once again before posting your question on ask.opendaylight.org

 

You can also reach out to the OpenFlow development team at openflowjava-dev@...

 

Regards,

Casey

 

On Sun, Mar 5, 2017 at 10:24 PM, Ajay Chopra <chopraa@...> wrote:

Hi ,

 

Any update ?

 

-Ajay

 

From: Ajay Chopra
Sent: 03 March 2017 16:20
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

HI ,

 

Any update ?

 

-Ajay
Sent: 03 March 2017 12:01
To: 'Casey Cain' <ccain@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Hi Casey cain ,

 

The PUT command uses http://10.119.162.14:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:224635998159098/table/0 .

 

-Ajay

 

From: Casey Cain [mailto:ccain@...]
Sent: 03 March 2017 11:47
To: Ajay Chopra <chopraa@...>
Cc: Jayavel Arumugam (IT Services), Noida <JayavelA@...>


Subject: Re: Open Day Light controllers

 

Hi, Ajay.

I will try to help you moving forward with this issue.

There still seems to be some ambiguity in how you are connected to the switch.

Can you tell me what commands you are currently using for your put command?

Have you searched ask.opendaylight.org or posted your question there yet?

 

Another good resource for faster answers is our IRC channels.

 

 

 

On Thu, Mar 2, 2017 at 10:00 PM, Ajay Chopra <chopraa@...> wrote:

Hi Phil ,

 

Any update ?

 

-Ajay

From: Ajay Chopra
Sent: 02 March 2017 11:32
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Hi Phil ,

 

Any update ?

 

-Ajay

From: Ajay Chopra
Sent: 01 March 2017 18:29
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; 'Casey Cain' <ccain@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

HI Phil ,

 

Got the below message when I try to push the Flows into the switch .

Error 405 Method not allowed .

 

Please let me know how can I overcome it so that I can add the flows .

 

-Ajay

                                                                                                                                                                                                     .

From: Ajay Chopra
Sent: 01 March 2017 11:51
To: 'Phil Robb' <probb@...>
Cc: info@...; Casey Cain <ccain@...>
Subject: RE: Open Day Light controllers

 

1)Switch is Brocade switch .

2) Yes , I have connectivity .

3) feature:install odl-restconf

    feature:install odl-dlux-core

    feature:install odl-mdsal-apidocs

   feature:install odl-openflowplugin-flow-services-rest

   feature:install odl-openflowplugin-flow-services-ui

   feature:install odl-dlux-node

   feature:install odl-dlux-yangui

   feature:install odl-l2switch-switch

4)I am using Postman

5)I am trying to PUT the flows but not able to add the flows .

 

From: Phil Robb [mailto:probb@...]
Sent: 01 March 2017 09:36
To: Ajay Chopra <chopraa@...>
Cc: info@...; Casey Cain <ccain@...>


Subject: Re: Open Day Light controllers

 

hello Ajay:

 

I've cc-ed Casey Cain.  Casey can help you to post this question to the OpenDaylight Q&A forum (ask.opendaylight.org)  and help make sure you get an answer from the community.

 

Your question is too vague as of yet for anyone to help though.  What switch are you trying to talking to?....  Are you sure you have connectivity to the switch?...What components of ODL did you install via Karaf?... what commands did you issue?.... what return codes did you get from the commands that you issued?.... etc.

 

When you go to post the question, please be specific with what you are using, what you did, and the results you saw.  Otherwise, those that try to help on our Q&A forum won't have enough information to be able to respond.

 

Best,

 

Phil.

 

 

On Tue, Feb 28, 2017 at 3:35 AM, Ajay Chopra <chopraa@...> wrote:

HI phil,

 

I have installed open daylight but not able to add flows can u help how to add the flows ?

 

-Ajay

 

From: Ajay Chopra
Sent: 21 November 2016 12:36
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>
Subject: RE: Open Day Light controllers

 

Hello Phil,

 

I have installed the opendaylight Beryllium controller ,but when I login using web with login/pass as admin.

It is not logging in .

Is there any update there ?due to which I am not able to login .

Can you check at your side ?

 

-Ajay

From: Ajay Chopra
Sent: 06 July 2016 10:55
To: 'Phil Robb' <probb@...>
Cc: 'info@...' <info@...>; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Gentle reminder .

 

From: Ajay Chopra
Sent: 05 July 2016 15:29
To: 'Phil Robb' <probb@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: RE: Open Day Light controllers

 

Can you share the link from where we can download the ODL controller ?

 

-Ajay

From: Phil Robb [mailto:probb@...]
Sent: 29 June 2016 21:10
To: Ajay Chopra <chopraa@...>
Cc: info@...; Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Re: Open Day Light controllers

 

Hey Ajay:

 

As an open source project, OpenDaylight does not test/certify against any particular hardware.  We support OpenFlow, along with many other protocols so to that extent we support Pica8 switches. 

 

Vendors who provide controllers based on OpenDaylight will often test and document what hardware they've tested against, so that may be helpful to you as well.

 

Best,

 

Phil.

 

On Wed, Jun 29, 2016 at 8:16 AM, Ajay Chopra <chopraa@...> wrote:

Gentle Reminder .

 

From: Ajay Chopra
Sent: 29 June 2016 13:06
To: 'info@...' <info@...>
Cc: Syed Tabrez Ahmed Shah <SyedS@...>; Jayavel Arumugam (IT Services), Noida <JayavelA@...>
Subject: Open Day Light controllers

 

Hello OpenDayLight Team ,

 

Can you share the details of Open Day Light controllers which can support Pica8 or Edge Core Switch  ?

 

-Ajay



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------



 

--

Phil Robb

Sr. Director Of Technical Operations

OpenDaylight Project

Skype: Phil.Robb



 

--

Phil Robb

Executive Director, OpenDaylight Project

VP Operations - Networking & Orchestration, The Linux Foundation

Skype: Phil.Robb



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6



 

--

Casey Cain

Technical Program Manager

Linux Foundation

_________________

IRC - CaseyODL

Skype - wrathwolfk

WeChat - okaru6


openflowjava - Carbon M5 Offset 1 Status

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Openflowjava:


  1. Please provide updates on any previously-incomplete items from prior milestone readouts.   N/A

  1. Has your project met code freeze, i.e., only bug fixes are allowed from now on?   Yes

  1. Are all externally visible strings frozen to allow for translation & documentation?   Yes

  2. Is your documentation complete such that only editing and enhancing should take place after this point?   Yes

https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/openflow-protocol-library-developer-guide.rst;h=37a8fcd85f0a2111ae59a7e2e74d60cd3ce5e110;hb=HEAD

  1. Were project-specific deliverables planned for this milestone delivered successfully?   No Deliverables

  2. Are you running at least one basic automated system test job for each top-level feature?   No

* system test waiver granted   

  1. please provide link to your project Karaf 4 migration patch  


Stables Features (only for projects with stable features)
  1. Do your stable features fulfill quality requirements (i.e. unit and/or integration test coverage of at least 75%)?   Yes

https://sonar.opendaylight.org/overview?id=11724


9. Are you running several automated system test jobs including functionality, cluster, scalability, performance, longevity/stability for each stable feature?   No

*  covered by openflowplugin project test suite




Regards,
Michal


Re: [netvirt-dev] ISE in openflowjava for msg deserialization failure

Aizer, Koby <koby.aizer@...>
 

Hi again,

Alon & I looked a little bit more into this issue and we found that the reason for the different size of the REG1 OXM is because the match is masked (comparing to the table=220 match which wasn't), and I think openflowplugin doesn't support this correctly.
I've updated bug [1] with this analysis, and moved the bug from netvirt to openflowplugin - it'd be great if someone can confirm this analysis is correct.

Thanks,
Koby

[1] https://bugs.opendaylight.org/show_bug.cgi?id=7897

-----Original Message-----
From: netvirt-dev-bounces@... [mailto:netvirt-dev-bounces@...] On Behalf Of Aizer, Koby
Sent: Thursday, March 9, 2017 10:31 PM
To: Jamo Luhrsen <jluhrsen@...>; Abhijit Kumbhare <abhijitkoss@...>
Cc: openflowjava-dev@...; netvirt-dev@...; openflowplugin-dev@...
Subject: Re: [netvirt-dev] [openflowjava-dev] ISE in openflowjava for msg deserialization failure

Hi,

I looked into this exception a little bit, and I think it is caused by flow stats received from table=49. This table includes rules like:
cookie=0x8600000, duration=1.507s, table=49, n_packets=0, n_bytes=0, hard_timeout=10, priority=0,reg1=0x2/0xfffff,dl_src=fa:16:3e:7d:5a:42 actions=load:0x1->NXM_NX_REG4[0..7]

I've tcpdumped the flowstats, and for some reason the REG1 OXM value is 8byte long, while openflowplugin assumes it is 4byte long - and I think this causes the decoder to fail (the exception is just a side effect of the decoder trying to decode the additional 4bytes as the next OXM field) . Other reg matches (for example, the ones from table=220) are indeed 4byte long.
Not sure why the table=49 reg matches have a different size, the only reason I can think of is that those matches are created by OVS learn action. My knowledge pretty much ends here - Could it be those are 64bit register matches or something?

I attached the pcap capture to the bug so others can take a look as well.

Koby

-----Original Message-----
From: netvirt-dev-bounces@... [mailto:netvirt-dev-bounces@...] On Behalf Of Jamo Luhrsen
Sent: Thursday, March 9, 2017 6:53 PM
To: Abhijit Kumbhare <abhijitkoss@...>
Cc: openflowjava-dev@...; netvirt-dev@...; openflowplugin-dev@...
Subject: Re: [netvirt-dev] [openflowjava-dev] ISE in openflowjava for msg deserialization failure

yeah, thats it.

JamO

On 03/09/2017 08:44 AM, Abhijit Kumbhare wrote:
Jamo,

So is this the new bug for this? https://bugs.opendaylight.org/show_bug.cgi?id=7897
<https://bugs.opendaylight.org/show_bug.cgi?id=7897> ?

Abhijit

On Tue, Mar 7, 2017 at 11:05 AM, Jamo Luhrsen <jluhrsen@... <mailto:jluhrsen@...>> wrote:

Hi,

I'm seeing this exception [0] in our karaf logs of our netvirt CSIT. It can get kind of
noisy and I'm not sure if it's some problem we need to debug or not. At first I assumed
it was bug 5173 [1], but Luis corrected me. We do have a new bug for it [2]. Is there
any update?

btw, here is a full karaf log [3] from one of our CSIT (it shows up 250 times)

Here is the first line of the exception:

2017-03-07 12:44:19,706 | WARN | entLoopGroup-7-2 | OFDecoder | 304 -
org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.0.SNAPSHOT | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass:
org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 15 oxm_field:
127 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly


Thanks,
JamO

[0] http://termbin.com/tkms
[1] https://bugs.opendaylight.org/show_bug.cgi?id=5173 <https://bugs.opendaylight.org/show_bug.cgi?id=5173>
[2] https://bugs.opendaylight.org/show_bug.cgi?id=7897 <https://bugs.opendaylight.org/show_bug.cgi?id=7897>
[3]
https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz
<https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz>
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@... <mailto:openflowjava-dev@...>
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
<https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev>

_______________________________________________
netvirt-dev mailing list
netvirt-dev@...
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
_______________________________________________
netvirt-dev mailing list
netvirt-dev@...
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev


Re: Adding support for TCP flags match via Experimenter Message

Thomas Ferrandiz
 

Hi Anil,

Thanks for the reference, I thought it wasn’t released yet.

 

Best regards,

Thomas

 

De : Anil Vishnoi [mailto:vishnoianil@...]
Envoyé : vendredi 10 mars 2017 02:38
À : Thomas FERRANDIZ <Thomas.FERRANDIZ@...>
Cc : openflowjava-dev@...
Objet : Re: [openflowjava-dev] Adding support for TCP flags match via Experimenter Message

 

Hi Thomas,

 

TCP Flags is approved openflow extension (EXT-109) and it's added in the boron release. Following are the relevant patches from openflowplugin and openflowjava project.

 

 

Thanks

Anil 

 

On Thu, Mar 9, 2017 at 8:19 AM, Thomas FERRANDIZ <Thomas.FERRANDIZ@...> wrote:

Hello all,

I'm trying to implement support for TCP flags match using the OF Experimenter Message for a project I'm working on.

The version of ODL I'm using is Beryllium-SR4 which does not seem to have support for this.
However, I saw in the master branch of openflowjava that there was at least a partial implementation.

So what I did was to try to move it into my own module and complete the implementation of the missing parts I could potentially need.
I followed these steps:
1/ Copy openflow-approved-extensions.yang in my module and remove the parts that do not concern the use of TCP flags.
2/ Copy the files AbstractOxmExperimenterMatchEntryDeserializer.java,  AbstractOxmExperimenterMatchEntrySerializer.java,  OnfOxmTcpFlagsDeserializer.java and  OnfOxmTcpFlagsSerializer.java in my module
3/ Register them in SwitchConnectionProvider
In order to do this, I added this in the section  'augment "/config:modules/config:module/config:configuration" ' of the yang declaration of my module:

list openflow-switch-connection-provider {
                uses config:service-ref {
                    refine type {
                        mandatory true;
                        config:required-identity openflow-switch-connection-provider:openflow-switch-connection-provider;
                    }
                }
}

And used this code:

private void registerSerializer() {
        for (SwitchConnectionProvider provider : providers) {
            MatchEntrySerializerKey<?, ?> key = new MatchEntrySerializerKey<>(version,
                    ExperimenterClass.class, TcpFlags.class);
            key.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
            provider.registerMatchEntrySerializer(key, new OnfOxmTcpFlagsSerializer());

            MatchEntryDeserializerKey key2 = new MatchEntryDeserializerKey(version,
                    OxmMatchConstants.EXPERIMENTER_CLASS, EncodeConstants.ONFOXM_ET_TCP_FLAGS);
            key2.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
            provider.registerMatchEntryDeserializer(key2, new OnfOxmTcpFlagsDeserializer());

        }
}

4/ I tried to write the message as follows:

//Flag specific part

TcpFlagsBuilder flagsBuilder = new TcpFlagsBuilder();
flagsBuilder.setFlags(TCP_FLAG_SYN);
TcpFlagsContainerBuilder tcpFlagContainerBuilder = new TcpFlagsContainerBuilder();
tcpFlagContainerBuilder.setTcpFlags(flagsBuilder.build());

ExperimenterIdCaseBuilder expIdCaseBuilder = new ExperimenterIdCaseBuilder();
ExperimenterBuilder expBuilder = new ExperimenterBuilder();
expBuilder.setExperimenter(new ExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID));
expIdCaseBuilder.setExperimenter(expBuilder.build());
expIdCaseBuilder.addAugmentation(TcpFlagsContainer.class, tcpFlagContainerBuilder.build());

MatchEntryBuilder matchEntryBuilder = new MatchEntryBuilder();
matchEntryBuilder.setHasMask(false);
matchEntryBuilder.setOxmMatchField(TcpFlags.class);
matchEntryBuilder.setOxmClass(ExperimenterClass.class);
matchEntryBuilder.setMatchEntryValue(expIdCaseBuilder.build());
List<MatchEntry> matchEntries = new ArrayList<>();
MatchEntry me = matchEntryBuilder.build();
matchEntries.add(me);

org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
                rev150203.actions.grouping.ActionBuilder actionBuilder
                = new org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
                rev150203.actions.grouping.ActionBuilder();

actionBuilder.setActionChoice(setFieldcaseBuilder.build());

The problem comes when I need to add actionBuilder.build() to a list of Action because there are two Action types that are not compatible:

final List<org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action> actionList = new ArrayList<>();
actionList.add(actionBuilder.build()); //Does not work

So my question is whether there is a way to convert between the two types of Action?
Or to create an Action of type org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action directly with a TcpFlagsContainer embedded somehow?

Thanks in advance for your help,
Thomas FERRANDIZ



_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev



 

--

Thanks

Anil


Re: Adding support for TCP flags match via Experimenter Message

Anil Vishnoi
 

Hi Thomas,

TCP Flags is approved openflow extension (EXT-109) and it's added in the boron release. Following are the relevant patches from openflowplugin and openflowjava project.


Thanks
Anil 

On Thu, Mar 9, 2017 at 8:19 AM, Thomas FERRANDIZ <Thomas.FERRANDIZ@...> wrote:
Hello all,

I'm trying to implement support for TCP flags match using the OF Experimenter Message for a project I'm working on.

The version of ODL I'm using is Beryllium-SR4 which does not seem to have support for this.
However, I saw in the master branch of openflowjava that there was at least a partial implementation.

So what I did was to try to move it into my own module and complete the implementation of the missing parts I could potentially need.
I followed these steps:
1/ Copy openflow-approved-extensions.yang in my module and remove the parts that do not concern the use of TCP flags.
2/ Copy the files AbstractOxmExperimenterMatchEntryDeserializer.java,  AbstractOxmExperimenterMatchEntrySerializer.java,  OnfOxmTcpFlagsDeserializer.java and  OnfOxmTcpFlagsSerializer.java in my module
3/ Register them in SwitchConnectionProvider
In order to do this, I added this in the section  'augment "/config:modules/config:module/config:configuration" ' of the yang declaration of my module:

list openflow-switch-connection-provider {
                uses config:service-ref {
                    refine type {
                        mandatory true;
                        config:required-identity openflow-switch-connection-provider:openflow-switch-connection-provider;
                    }
                }
}

And used this code:

private void registerSerializer() {
        for (SwitchConnectionProvider provider : providers) {
            MatchEntrySerializerKey<?, ?> key = new MatchEntrySerializerKey<>(version,
                    ExperimenterClass.class, TcpFlags.class);
            key.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
            provider.registerMatchEntrySerializer(key, new OnfOxmTcpFlagsSerializer());

            MatchEntryDeserializerKey key2 = new MatchEntryDeserializerKey(version,
                    OxmMatchConstants.EXPERIMENTER_CLASS, EncodeConstants.ONFOXM_ET_TCP_FLAGS);
            key2.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
            provider.registerMatchEntryDeserializer(key2, new OnfOxmTcpFlagsDeserializer());

        }
}

4/ I tried to write the message as follows:

//Flag specific part

TcpFlagsBuilder flagsBuilder = new TcpFlagsBuilder();
flagsBuilder.setFlags(TCP_FLAG_SYN);
TcpFlagsContainerBuilder tcpFlagContainerBuilder = new TcpFlagsContainerBuilder();
tcpFlagContainerBuilder.setTcpFlags(flagsBuilder.build());

ExperimenterIdCaseBuilder expIdCaseBuilder = new ExperimenterIdCaseBuilder();
ExperimenterBuilder expBuilder = new ExperimenterBuilder();
expBuilder.setExperimenter(new ExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID));
expIdCaseBuilder.setExperimenter(expBuilder.build());
expIdCaseBuilder.addAugmentation(TcpFlagsContainer.class, tcpFlagContainerBuilder.build());

MatchEntryBuilder matchEntryBuilder = new MatchEntryBuilder();
matchEntryBuilder.setHasMask(false);
matchEntryBuilder.setOxmMatchField(TcpFlags.class);
matchEntryBuilder.setOxmClass(ExperimenterClass.class);
matchEntryBuilder.setMatchEntryValue(expIdCaseBuilder.build());
List<MatchEntry> matchEntries = new ArrayList<>();
MatchEntry me = matchEntryBuilder.build();
matchEntries.add(me);

org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
                rev150203.actions.grouping.ActionBuilder actionBuilder
                = new org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
                rev150203.actions.grouping.ActionBuilder();

actionBuilder.setActionChoice(setFieldcaseBuilder.build());

The problem comes when I need to add actionBuilder.build() to a list of Action because there are two Action types that are not compatible:

final List<org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action> actionList = new ArrayList<>();
actionList.add(actionBuilder.build()); //Does not work

So my question is whether there is a way to convert between the two types of Action?
Or to create an Action of type org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action directly with a TcpFlagsContainer embedded somehow?

Thanks in advance for your help,
Thomas FERRANDIZ



_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev



--
Thanks
Anil


Re: [netvirt-dev] ISE in openflowjava for msg deserialization failure

Aizer, Koby <koby.aizer@...>
 

Hi,

I looked into this exception a little bit, and I think it is caused by flow stats received from table=49. This table includes rules like:
cookie=0x8600000, duration=1.507s, table=49, n_packets=0, n_bytes=0, hard_timeout=10, priority=0,reg1=0x2/0xfffff,dl_src=fa:16:3e:7d:5a:42 actions=load:0x1->NXM_NX_REG4[0..7]

I've tcpdumped the flowstats, and for some reason the REG1 OXM value is 8byte long, while openflowplugin assumes it is 4byte long - and I think this causes the decoder to fail (the exception is just a side effect of the decoder trying to decode the additional 4bytes as the next OXM field) . Other reg matches (for example, the ones from table=220) are indeed 4byte long.
Not sure why the table=49 reg matches have a different size, the only reason I can think of is that those matches are created by OVS learn action. My knowledge pretty much ends here - Could it be those are 64bit register matches or something?

I attached the pcap capture to the bug so others can take a look as well.

Koby

-----Original Message-----
From: netvirt-dev-bounces@... [mailto:netvirt-dev-bounces@...] On Behalf Of Jamo Luhrsen
Sent: Thursday, March 9, 2017 6:53 PM
To: Abhijit Kumbhare <abhijitkoss@...>
Cc: openflowjava-dev@...; netvirt-dev@...; openflowplugin-dev@...
Subject: Re: [netvirt-dev] [openflowjava-dev] ISE in openflowjava for msg deserialization failure

yeah, thats it.

JamO

On 03/09/2017 08:44 AM, Abhijit Kumbhare wrote:
Jamo,

So is this the new bug for this? https://bugs.opendaylight.org/show_bug.cgi?id=7897
<https://bugs.opendaylight.org/show_bug.cgi?id=7897> ?

Abhijit

On Tue, Mar 7, 2017 at 11:05 AM, Jamo Luhrsen <jluhrsen@... <mailto:jluhrsen@...>> wrote:

Hi,

I'm seeing this exception [0] in our karaf logs of our netvirt CSIT. It can get kind of
noisy and I'm not sure if it's some problem we need to debug or not. At first I assumed
it was bug 5173 [1], but Luis corrected me. We do have a new bug for it [2]. Is there
any update?

btw, here is a full karaf log [3] from one of our CSIT (it shows up 250 times)

Here is the first line of the exception:

2017-03-07 12:44:19,706 | WARN | entLoopGroup-7-2 | OFDecoder | 304 -
org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.0.SNAPSHOT | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass:
org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 15 oxm_field:
127 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly


Thanks,
JamO

[0] http://termbin.com/tkms
[1] https://bugs.opendaylight.org/show_bug.cgi?id=5173 <https://bugs.opendaylight.org/show_bug.cgi?id=5173>
[2] https://bugs.opendaylight.org/show_bug.cgi?id=7897 <https://bugs.opendaylight.org/show_bug.cgi?id=7897>
[3]
https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz
<https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz>
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@... <mailto:openflowjava-dev@...>
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
<https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev>

_______________________________________________
netvirt-dev mailing list
netvirt-dev@...
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev


Re: ISE in openflowjava for msg deserialization failure

Jamo Luhrsen <jluhrsen@...>
 

yeah, thats it.

JamO

On 03/09/2017 08:44 AM, Abhijit Kumbhare wrote:
Jamo,

So is this the new bug for this? https://bugs.opendaylight.org/show_bug.cgi?id=7897
<https://bugs.opendaylight.org/show_bug.cgi?id=7897> ?

Abhijit

On Tue, Mar 7, 2017 at 11:05 AM, Jamo Luhrsen <jluhrsen@... <mailto:jluhrsen@...>> wrote:

Hi,

I'm seeing this exception [0] in our karaf logs of our netvirt CSIT. It can get kind of
noisy and I'm not sure if it's some problem we need to debug or not. At first I assumed
it was bug 5173 [1], but Luis corrected me. We do have a new bug for it [2]. Is there
any update?

btw, here is a full karaf log [3] from one of our CSIT (it shows up 250 times)

Here is the first line of the exception:

2017-03-07 12:44:19,706 | WARN | entLoopGroup-7-2 | OFDecoder | 304 -
org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.0.SNAPSHOT | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass:
org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 15 oxm_field:
127 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly


Thanks,
JamO

[0] http://termbin.com/tkms
[1] https://bugs.opendaylight.org/show_bug.cgi?id=5173 <https://bugs.opendaylight.org/show_bug.cgi?id=5173>
[2] https://bugs.opendaylight.org/show_bug.cgi?id=7897 <https://bugs.opendaylight.org/show_bug.cgi?id=7897>
[3]
https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz
<https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz>
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@... <mailto:openflowjava-dev@...>
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
<https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev>


Re: ISE in openflowjava for msg deserialization failure

Abhijit Kumbhare
 

Jamo,

So is this the new bug for this? https://bugs.opendaylight.org/show_bug.cgi?id=7897 ?

Abhijit

On Tue, Mar 7, 2017 at 11:05 AM, Jamo Luhrsen <jluhrsen@...> wrote:
Hi,

I'm seeing this exception [0] in our karaf logs of our netvirt CSIT. It can get kind of
noisy and I'm not sure if it's some problem we need to debug or not. At first I assumed
it was bug 5173 [1], but Luis corrected me. We do have a new bug for it [2]. Is there
any update?

btw, here is a full karaf log [3] from one of our CSIT (it shows up 250 times)

Here is the first line of the exception:

2017-03-07 12:44:19,706 | WARN  | entLoopGroup-7-2 | OFDecoder                        | 304 -
org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.0.SNAPSHOT | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass:
org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 15 oxm_field:
127 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly


Thanks,
JamO

[0] http://termbin.com/tkms
[1] https://bugs.opendaylight.org/show_bug.cgi?id=5173
[2] https://bugs.opendaylight.org/show_bug.cgi?id=7897
[3]
https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


Adding support for TCP flags match via Experimenter Message

Thomas Ferrandiz
 

Hello all,

I'm trying to implement support for TCP flags match using the OF Experimenter Message for a project I'm working on.

The version of ODL I'm using is Beryllium-SR4 which does not seem to have support for this.
However, I saw in the master branch of openflowjava that there was at least a partial implementation.

So what I did was to try to move it into my own module and complete the implementation of the missing parts I could potentially need.
I followed these steps:
1/ Copy openflow-approved-extensions.yang in my module and remove the parts that do not concern the use of TCP flags.
2/ Copy the files AbstractOxmExperimenterMatchEntryDeserializer.java, AbstractOxmExperimenterMatchEntrySerializer.java, OnfOxmTcpFlagsDeserializer.java and OnfOxmTcpFlagsSerializer.java in my module
3/ Register them in SwitchConnectionProvider
In order to do this, I added this in the section 'augment "/config:modules/config:module/config:configuration" ' of the yang declaration of my module:

list openflow-switch-connection-provider {
uses config:service-ref {
refine type {
mandatory true;
config:required-identity openflow-switch-connection-provider:openflow-switch-connection-provider;
}
}
}

And used this code:

private void registerSerializer() {
for (SwitchConnectionProvider provider : providers) {
MatchEntrySerializerKey<?, ?> key = new MatchEntrySerializerKey<>(version,
ExperimenterClass.class, TcpFlags.class);
key.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
provider.registerMatchEntrySerializer(key, new OnfOxmTcpFlagsSerializer());

MatchEntryDeserializerKey key2 = new MatchEntryDeserializerKey(version,
OxmMatchConstants.EXPERIMENTER_CLASS, EncodeConstants.ONFOXM_ET_TCP_FLAGS);
key2.setExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID);
provider.registerMatchEntryDeserializer(key2, new OnfOxmTcpFlagsDeserializer());

}
}

4/ I tried to write the message as follows:

//Flag specific part

TcpFlagsBuilder flagsBuilder = new TcpFlagsBuilder();
flagsBuilder.setFlags(TCP_FLAG_SYN);
TcpFlagsContainerBuilder tcpFlagContainerBuilder = new TcpFlagsContainerBuilder();
tcpFlagContainerBuilder.setTcpFlags(flagsBuilder.build());

ExperimenterIdCaseBuilder expIdCaseBuilder = new ExperimenterIdCaseBuilder();
ExperimenterBuilder expBuilder = new ExperimenterBuilder();
expBuilder.setExperimenter(new ExperimenterId(EncodeConstants.ONF_EXPERIMENTER_ID));
expIdCaseBuilder.setExperimenter(expBuilder.build());
expIdCaseBuilder.addAugmentation(TcpFlagsContainer.class, tcpFlagContainerBuilder.build());

MatchEntryBuilder matchEntryBuilder = new MatchEntryBuilder();
matchEntryBuilder.setHasMask(false);
matchEntryBuilder.setOxmMatchField(TcpFlags.class);
matchEntryBuilder.setOxmClass(ExperimenterClass.class);
matchEntryBuilder.setMatchEntryValue(expIdCaseBuilder.build());
List<MatchEntry> matchEntries = new ArrayList<>();
MatchEntry me = matchEntryBuilder.build();
matchEntries.add(me);

org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
rev150203.actions.grouping.ActionBuilder actionBuilder
= new org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.
rev150203.actions.grouping.ActionBuilder();

actionBuilder.setActionChoice(setFieldcaseBuilder.build());

The problem comes when I need to add actionBuilder.build() to a list of Action because there are two Action types that are not compatible:

final List<org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action> actionList = new ArrayList<>();
actionList.add(actionBuilder.build()); //Does not work

So my question is whether there is a way to convert between the two types of Action?
Or to create an Action of type org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action directly with a TcpFlagsContainer embedded somehow?

Thanks in advance for your help,
Thomas FERRANDIZ


ISE in openflowjava for msg deserialization failure

Jamo Luhrsen <jluhrsen@...>
 

Hi,

I'm seeing this exception [0] in our karaf logs of our netvirt CSIT. It can get kind of
noisy and I'm not sure if it's some problem we need to debug or not. At first I assumed
it was bug 5173 [1], but Luis corrected me. We do have a new bug for it [2]. Is there
any update?

btw, here is a full karaf log [3] from one of our CSIT (it shows up 250 times)

Here is the first line of the exception:

2017-03-07 12:44:19,706 | WARN | entLoopGroup-7-2 | OFDecoder | 304 -
org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.0.SNAPSHOT | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass:
org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 15 oxm_field:
127 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly


Thanks,
JamO

[0] http://termbin.com/tkms
[1] https://bugs.opendaylight.org/show_bug.cgi?id=5173
[2] https://bugs.opendaylight.org/show_bug.cgi?id=7897
[3]
https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon/162/archives/odl1_karaf.log.gz


Re: Barrier Message Timeout - 500ms - Rational behind the value

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Muthukrishnan,


right - I was referring to 'Maximum outbound queue depth'.

25600 is not maximum amount of messages in outbound queue - it is just a threshold value and when crossed then automatically a barrier message is added to queue. But the weird thing about this is that the limit for barrier in queue (25.6k) should be actually smaller than rpc limit (20k). So if you are observing one switch throughput then I believe that by increasing rpc-limit to 30k or decreasing the barrier in queue limit to 15k will improve your performance.


See:

openFlowPlugin/openflowplugin-api/src/main/yang/openflow-provider-config.yang

openFlowPlugin/openflowplugin-blueprint-config/src/main/resources/initial/openflowplugin.cfg

rpc-requests-quota


Regards,

Michal




From: Muthukrishnan Thangasamy <muthukrishnan.t@...>
Sent: Wednesday, February 22, 2017 08:35
To: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco); openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: Re: [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value
 

Hi Michal ,


Thank you for your response , I agree with you , I need some clarity on your response


Also there is a complementary parameter - amount of messages in outbound queue without barrier inside. The more messages kept in queue the higher throughput you shall get.


Question : My understanding is that you are referring to Maximum outbound queue depth which is 25600 by default , here if we are sending the flow via SAL-RPC  and barrier timer is 500 ms 

how to achieve flow throughput of 1000 flows/sec ( total number of non-barrier message kept in queue as 1000) , since RPC call form northbound takes ( 500ms + 20 ms ) for writing single flow (assuming writing each flow sequentially in loop), throughput is less even you are sending 1000 flows/sec. If am sending via RPC how to keep 1000 openflow messages in queue without barrier ? is there any other parameter which is controlling the same ?



Regards

Muthukrishnan

9952012433








From: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>
Sent: Thursday, February 16, 2017 2:21 PM
To: Muthukrishnan Thangasamy; openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: Re: [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value
 

Hi Muthukrishnan,

there is no golden standard behind this value. Setting it to 100ms or even lower value will result into low latency system but this also decreases throughput of system.


If you have few switches and little no big requirement on flows per second throughput then 100ms might suit better to your setup. On the other hand if there are hundreds of devices and throughput of thousands of flows per second required then 500ms or even higher will improve overall performance.


Also there is a complementary parameter - amount of messages in outbound queue without barrier inside. The more messages kept in queue the higher throughput you shall get. But there is memory cost and also by extending size of those queues (per device) there comes overload risk of md-sal notification queue.


True - this value might be configurable. But that would solve the situation only for static requirements.



Regards,

Michal




From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Muthukrishnan Thangasamy <muthukrishnan.t@...>
Sent: Wednesday, February 15, 2017 08:13
To: openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value
 


Dear Team ,


I have been working in Lithium and Boron Stable Version .


Lets take Boron , In openflowplugin.cfg default timer for barrier message is 500ms is there any

rational behind the same ? why not 100ms ?


If I push via SAL-FLOW RPC , total time taken for flow push = Time taken for flow push + barrier delay  = ~ 30 ms + 520 ms (barrier ).


If I change the value from 500ms to 100 ms I am getting drastic performance improvement in flow push processing . Can anyone tell why we have gone for 500ms as default timer value ?

How we have arrived this golden value of 500ms ?



Reference.


File : openflowplugin.cfg

"#Timeout interval in milliseconds between each barrier message.

#Default value is set to 500 milliseconds
barrier-interval-timeout-limit=500"

Regards
Muthukrishnan
9952012433


Openflow Switch Connectio Provider Imp - Boss/Worker threads

Muthukrishnan T
 


Dear Team ,


I am using lithium/boron stable version. I would like to increase the boss/worker threads responsible for handling incoming connection to the port 6633/6653.


I have increased the boss-thread count to 10 to manage 500 incoming switch connection , but even after change only two threads are running ( verified the same in profiling tool visual VM ).

Can anyone tell me how to increase the boss threads/worker threads count and is there any login behind spawning of above threads based on number of incoming connection to the port 6633? 


Change:

<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
            <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
                <!-- default OF-switch-connection-provider (port 6633) -->
                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:openflow:switch:connection:provider:impl">
                        prefix:openflow-switch-connection-provider-impl
                    </type>
                    <name>openflow-switch-connection-provider-default-impl</name>
                    <port>6633</port>
                    <!--      Possible transport-protocol options: TCP, TLS, UDP -->
                    <transport-protocol>TCP</transport-protocol>
                    <switch-idle-timeout>15000</switch-idle-timeout>
   <threads>

                          <boss-threads>10</boss-threads>
                          <worker-threads>16</worker-threads>
                   </threads>



Reference File :

./openflowplugin-controller-config/src/main/resources/initial/42-openflowplugin-new.xml

./distribution/karaf/target/assembly/system/org/opendaylight/openflowplugin/openflowplugin-controller-config/0.1.5-SNAPSHOT/openflowplugin-controller-config-0.1.5-SNAPSHOT-config-Li.xml


Regards

Muthukrishnan

9952012433


Re: Barrier Message Timeout - 500ms - Rational behind the value

Muthukrishnan T
 

Hi Michal ,


Thank you for your response , I agree with you , I need some clarity on your response


Also there is a complementary parameter - amount of messages in outbound queue without barrier inside. The more messages kept in queue the higher throughput you shall get.


Question : My understanding is that you are referring to Maximum outbound queue depth which is 25600 by default , here if we are sending the flow via SAL-RPC  and barrier timer is 500 ms 

how to achieve flow throughput of 1000 flows/sec ( total number of non-barrier message kept in queue as 1000) , since RPC call form northbound takes ( 500ms + 20 ms ) for writing single flow (assuming writing each flow sequentially in loop), throughput is less even you are sending 1000 flows/sec. If am sending via RPC how to keep 1000 openflow messages in queue without barrier ? is there any other parameter which is controlling the same ?



Regards

Muthukrishnan

9952012433








From: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>
Sent: Thursday, February 16, 2017 2:21 PM
To: Muthukrishnan Thangasamy; openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: Re: [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value
 

Hi Muthukrishnan,

there is no golden standard behind this value. Setting it to 100ms or even lower value will result into low latency system but this also decreases throughput of system.


If you have few switches and little no big requirement on flows per second throughput then 100ms might suit better to your setup. On the other hand if there are hundreds of devices and throughput of thousands of flows per second required then 500ms or even higher will improve overall performance.


Also there is a complementary parameter - amount of messages in outbound queue without barrier inside. The more messages kept in queue the higher throughput you shall get. But there is memory cost and also by extending size of those queues (per device) there comes overload risk of md-sal notification queue.


True - this value might be configurable. But that would solve the situation only for static requirements.



Regards,

Michal




From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Muthukrishnan Thangasamy <muthukrishnan.t@...>
Sent: Wednesday, February 15, 2017 08:13
To: openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value
 


Dear Team ,


I have been working in Lithium and Boron Stable Version .


Lets take Boron , In openflowplugin.cfg default timer for barrier message is 500ms is there any

rational behind the same ? why not 100ms ?


If I push via SAL-FLOW RPC , total time taken for flow push = Time taken for flow push + barrier delay  = ~ 30 ms + 520 ms (barrier ).


If I change the value from 500ms to 100 ms I am getting drastic performance improvement in flow push processing . Can anyone tell why we have gone for 500ms as default timer value ?

How we have arrived this golden value of 500ms ?



Reference.


File : openflowplugin.cfg

"#Timeout interval in milliseconds between each barrier message.

#Default value is set to 500 milliseconds
barrier-interval-timeout-limit=500"

Regards
Muthukrishnan
9952012433

81 - 100 of 861