Ask is moving to Stack Overflow and! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode


VTN - L2 network multi-controller not working

asked 2015-08-20 08:09:49 -0700

Ufuntu gravatar image


Can anyone please advise on the following issue I am having with the multi-controller tutorial for VTN - L2NetworkWithMultipleControllers

Using the custom mininet script provided, I am able to connect to 2 controllers running in seperate Ubuntu 14.04 vm's, but when I try to create the VTN (vtn3 as per tutorial) it does not seem to work. Specifically, when I run through the commands in the tutorial everything seems fine, but when I query the status of vtn3 it is "operstatus:down"

I have confirmed that both Controllers/VTN Manager's are listening on required ports (6633(for mininet), 8282(for coordinator), as well as 6653 & 8181). I have also disabled the firewall's in both controller vm's (using "sudo ufw disable").

Incidentally, I have successfully ran through the single controller tutorial on the same servers/vm's without much issue. It is just the creation of the VTN in the multi-controller tutorial that does not work for me?

Is there any particular ports required on the VTN coordinator side? When I run lsof -iTCP | grep 66, or 82, I am not getting any response to those ports, although as I have already mentioned, the set up works for single controller?

Thank's in advance for any advice,

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-08-20 15:52:04 -0700

gvrangan gravatar image
  1. Was all the REST API successful?
  2. After adding controller, please check if the controller status become "up" in VTN Coordinator
  3. Once both controller status are "up"
  4. Please start the vtn, vbr and other commands

In the mininet VM, you can run sudo ovs-vsctl show to confirm if all the switches are correctly connected to the corresponding controllers by checking if the is_connected is "true"

edit flag offensive delete publish link more


1. Yes all REST API were successful (code 201 "Created" for POST, 204 "No Content" for PUT) 2. Yes status is "up" on both controllers 3&4 Both controllers are up and all commands (vtn, vbr, vlk, vif) appear to be successful, but VTN is either status "down" or "unkown" Mininet appears to be correct?

Ufuntu ( 2015-08-21 04:17:45 -0700 )edit

Update: After checking mininet with "sudo ovs-vsctl show" it does look like the issue may be mininet, as the command only returns the OVS Version? It does not appear that any switches were created! Any suggestions out there why it looks like mininet has created a network but there are no switches?

Ufuntu ( 2015-08-21 12:27:04 -0700 )edit

answered 2015-08-26 06:04:51 -0700

balakrishnan gravatar image

updated 2015-08-26 06:08:20 -0700

we have tested the multicontroller tutorial for VTN it was working fine in our environment. could you please tell me which karaf distribution your using. after creating mininet topology please execute below command in both controller see your able to get topology information curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X GET { "vtn-topology": { "vtn-link": [ { "destination": "openflow:1:1", "link-id": "openflow:2:3", "source": "openflow:2:3" }, { "destination": "openflow:1:2", "link-id": "openflow:3:3", "source": "openflow:3:3" }, { "destination": "openflow:3:3", "link-id": "openflow:1:2", "source": "openflow:1:2" }, { "destination": "openflow:2:3", "link-id": "openflow:1:1", "source": "openflow:1:1" } ] } } "sudo ovs-vsctl show" will list the switches connected to the controller as below you are getting only mininet version could be mininet issue. mininet@mininet-only:~$ sudo ovs-vsctl show [sudo] password for mininet: dedcbf5a-b730-4937-b453-6a36246917ae Bridge "s2" Controller "tcp:" is connected: true Controller "ptcp:6635" failmode: secure Port "s2-eth2" Interface "s2-eth2" Port "s2-eth3" Interface "s2-eth3" Port "s2" Interface "s2" type: internal Port "s2-eth1" Interface "s2-eth1" ...

edit flag offensive delete publish link more


I have actually tried in both Helium and Lithium distributions but both seem to give the same results, so it is most likely some issue with my set up. I will try the above command, when I get sometime later, to see what response I get. Thank you for the suggestion

Ufuntu ( 2015-08-26 08:07:04 -0700 )edit

Update: When I create controllers in vtn coordinator both controllers are operstatus:up but when I run the rest of the commands for vtn, vbr, vif everything - controllers, vtn etc. - are then operstatus:down or unknown. It also does not map the logical ports?

Ufuntu ( 2015-08-26 09:35:09 -0700 )edit

I think is mininet/OVS but I can't figure it out. Just in case it makes a difference, I created the custom topo in folder mininet/mininet and then just run sudo python I doubt the location of the file matters though as it seems to create the network, but it does not create the switches

Ufuntu ( 2015-08-26 09:39:00 -0700 )edit

did you changed the both controller IP in the script. initially VBR,VBRIF status will be unknown when you map the correct port to the VBRIF using port map the status became UP.

balakrishnan ( 2015-08-26 23:11:10 -0700 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2015-08-20 08:09:49 -0700

Seen: 413 times

Last updated: Aug 26 '15