[OPNFLWPLUG-79] LINC switch crashes OpenDaylight controller Created: 11/Mar/14  Updated: 27/Sep/21  Resolved: 18/Mar/14

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

Type: Bug
Reporter: Pauline Martial Assignee: Pauline Martial
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

Attachments: Text File opendaylight.log     Text File opendaylight_20140317.log    
External issue ID: 512

 Description   

Hi,

I am trying to use LINC virtual switch with OpenDaylight (using OpenFlow 1.3) but I’m having some problems. Here are the versions I installed:
OpenDaylight release downloaded on a virtual machine (Fedora20, 64 bits, using VirtualBox)
LINC last version downloaded on a virtual machine (Ubuntu 13.10, 64 bits, using VirtualBox)

I have installed LINC switch and OpenDaylight controller but whenever I try to connect them together, the OpenDaylight controller throws Null Pointer Java Exceptions. This happens whatever OpenDaylight edition I use (Base, Virtualization or ServiceProvider). Through the Web Interface, I see that the controller is connected to the switch but there are errors (Null Pointer Java Exception) in the controller’s log, which make it impossible to push any rule in the switch…

However, I have used LINC controller with the default Mininet controller and it works perfectly.
I have also used OpenDaylight controller with OpenvSwitch and it works perfectly too.

You will find enclosed the exceptions stacktraces (file opendaylight.log) produced when I tried to connect the switch to the controller.

Thanks,

Pauline

 Comments   
Comment by Pauline Martial [ 11/Mar/14 ]

Attachment opendaylight.log has been added with description: exceptions stacktraces

Comment by Michal Rehak [ 11/Mar/14 ]

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

Comment by Michal Rehak [ 11/Mar/14 ]

Hi Pauline,
could you retest? The fix has been merged and you can either build OFPlugin or just download and run the latest distribution-base zip: http://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/openflowplugin/distributions-openflowplugin-base/0.0.3-SNAPSHOT/

Comment by Pauline Martial [ 17/Mar/14 ]

Attachment opendaylight_20140317.log has been added with description: OpenDaylight log file when LINC switch tries to connect

Comment by Pauline Martial [ 17/Mar/14 ]

Hi,

I have downloaded the March 11th zip version (http://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/openflowplugin/distributions-openflowplugin-base/0.0.3-SNAPSHOT/distributions-openflowplugin-base-0.0.3-20140311.155110-18-osgipackage.zip) but I get Null Pointer Java Exceptions as soon I connect the LINC switch, eventhough I can see the switch on the web interface...

Configuration: Linux Debian 7.
You'll find enclosed the opendaylight.log attached (name: opendaylight_20140317.log).

Sorry for the delay and thanks for your help,

Pauline

Comment by Michal Rehak [ 17/Mar/14 ]

Hi Pauline,
this seems to be another bug affecting error message processing. Could you inspect communication through wireshark. This looks like there is a flow request sent to device and device responds with error message. Are you seeing any error responses from switch on the wire?

Thank you.

Comment by Michal Rehak [ 17/Mar/14 ]

Could you try to remove org.opendaylight.openflowplugin.test-provider-0.0.3-SNAPSHOT.jar from your plugins folder? Then the buggy testing implementation of SalFlowListener wont be active.

By the way - how are you creating flows. Looks like you are not using config context of dataStore.

Thank you.

Comment by Pauline Martial [ 18/Mar/14 ]

Hi,
I removed the jar file and now everything seems to work, thank you!

To answer your question, I am creating flow entries through the web interface, then I just run "pingall" command in Mininet to make sure the flow entries are properly installed. But I am not using config context of dataStore at all. Is this a problem?

Thanks again,
Pauline

Comment by Michal Rehak [ 18/Mar/14 ]

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

The NPE was thrown upon ErrorMessage without transactionUri. Most common reason for those errors is multipart stat request.

Comment by Michal Rehak [ 18/Mar/14 ]

merged

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