[CONTROLLER-485] Unable to contact the remote controller Created: 19/May/14  Updated: 19/Oct/17  Resolved: 05/May/15

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: 0.4.0
Fix Version/s: None

Type: Bug
Reporter: Sai MarapaReddy Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows
Platform: PC

Attachments: JPEG File 1.jpg    
External issue ID: 1032

 Description   

When I start running the controller, using sudo ./run.sh -of13 and then start sample configuration with 1 controller, 3 switches, 4 hosts. (In Virtual box VM fedora), I face this error. Could you please let me know the reason behind it. I face this issue frequently, but i don,t know the reason behind it frame a solution.

System COnfig:-
using VM provided by opendaylight, Fedora version.

Controller should be up and running and the topology should be created, but unable to contact the controller.

Attached a screenshot for your easy reference.

 Comments   
Comment by Sai MarapaReddy [ 19/May/14 ]

Attachment 1.jpg has been added with description: screenshot

Comment by Naresh kumar [ 20/Aug/14 ]

Hi Sujith,
The reason might be ovs-controller that runs in mininet. This controller also connected with the mininet in port 6633 just like Opendaylight. So before starting the mininet stop the ovs-controller and then proceed with you steps. It should work fine.

Command to stop ovs-conroller:
sudo service openvswitch-controller stop
sudo update-rc.d openvswitch-controller disable

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.

Comment by Tony Tkacik [ 05/May/15 ]

this run was done expecting openflowplugin for 1.3 working, using controller distribution from controller repo which does not contain openflow 1.3 plugin.

Use official opendaylight Helium / Lithium distribution when available.

Generated at Wed Feb 07 19:53:08 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.