-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error using Mininet in Vagrant option. #18
Comments
Just to clarify a bit more, the problem that @GonzaloFajardoMedina has is that Mininet is not able to connect to the Engine. Maybe some of the modules of the Engine are not running? |
No, all modules are running: Core, Shim and ryu-backend. And the shim and the ryu-backend connect to the Core. |
It's all a matter of time when it comes to OpenDaylight. If you wait for about half a minute, Mininet shouldn't print that error anymore. |
Although I wait that ODL initializes (about 2 minutes after it is initialized), Mininnet still does not go. I also tested the ryu-shim option and it still gives the error: unable to contact the remote controller at 127.0.0.1:6633 . |
Try to set the controller port in your model to 6644, then regenerate it. |
Hi @cstritzke, |
Hi @cstritzke , I have the same problem that @GonzaloFajardoMedina when using Ryu+Core+Ryu. I've tried stopping and restarting the backend, and also Mininet, but yet the same error: It's a bit strange, because Ryu should run quite fast, it shouldn't need extra time to be ready. I waited and tried again just in case with no success. I'm attaching below screenshots from the core, shim and backend just in case. I've also checked the Ryu starters and they look good. |
Did you try to change your controller port in the topology model to 6644? That might be the problem here. Maybe it makes sense to have another standard port here. |
Sorry, but why should I change it to 6644? It makes sense for ODL, because the ODL shim uses that port by default, but not for Ryu :( (I mean, it should not affect at all!). I haven't tried 6644 because I don't want the VM to be created once again from scratch, would that be avoided? If so, please let me know and I can have a try, but to me it does not make sense to change the port... In fact, I've executed every piece directly on the VM (no via the IDE, but directly on the Vagrant VM created) and the handshake works well, and the core lists components, etc. So there is clearly something different when using the IDE... Mininet is still not working though and I'm thinking on how to debug that without a visual interface and no Wireshark :( Could you please check if this is working for you please? Maybe if you film yourself deploying everything that would be great (in case we are missing something very trivial), but unfortunately things are not working and in this Vagrant VM is quite hard to debug the Engine behavior. |
Hi,
when I run Mininet, shows the next error:
Any idea?
Thanks everybody.
The text was updated successfully, but these errors were encountered: