[geni-users] Unable to connect Open vSwitch to controller

[Aditi Ghag]

Hi,

I have a layer2 topology having 3 Open vSwitches. I am running Floodlight controller on one of the three switches. 

I have created bridges and added all the data interfaces on individual switches. I then pointed the switches to the controller using this command- 

sudo ovs-vsctl set-controller br0 tcp:<controller-ip-address>:6633

When I list the connected switches using Floodlight's REST API, I can see only the local switch ports. I don't see the remote switches. 

I made sure that the controller ip address is reachable from the other two switches by pinging to that ip-address from the switches. 

Am I missing something here? Any help would be appreciate. 

Thanks,

Aditi

 

[Niky Riga]

Hi Aditi,

Can you tell me what is the IP you used? Also can you try to telnet to 6633 from the remote OVS switches,
i.e. while logged in on a remote OVS switch do
  telnet <controller-ip-address> 6633

--niky

--
GENI Users is a community supported mailing list, so please help by responding to questions you know the answer to.
 
If this is your first time posting a question to this list, please review http://groups.geni.net/geni/wiki/GENIExperimenter/CommunityMailingList
---
You received this message because you are subscribed to the Google Groups "GENI Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geni-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
Niky Riga
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
Phone: 617 873 3160
Fax  : 617 873 6091

Please consider the environment before printing this e-mail

[Aditi Ghag]

Hey Niky,

I used the control ip address- 172.17.3.22.

I'm unable to telnet to 172:17.3.22:6633

Will I have to use a public IP address as the controller ip?

Thanks,

Aditi

[Niky Riga]

If you are running your controller  on port 6633 but you can not telnet then that means
that you do not have connectivity to this port from outside, which makes sense why
your switches are not connecting.

If I had to guess i would say that your controller is behind NAT, i.e. you have not
requested a public IP address when you did the reservation and thus starting
services on this node might be tricky, especially if the OVS hosts are on other
aggregates. Someone from Utah should be able to verify if that is the case and
whether there is a way around it that does not involve you recreating the slice with
requesting for a public IP address.

An easy way to fix this is to create a new slice, add a xen VM and request a public
IP address (in flack this is under the node properties, under the link tab. Just ignore
the warning that this is emulab only). Install Floodlight in this new VM and use this
for your controller for all your OVSs.

--niky

[Aditi Ghag]

Yes, I din't request a public ip for the switches. Originally my topology had three hosts connected via switches. I had requested public IPs for the three hosts. I was planning on installing Floodlight on the Utah VM, but there seems to be problem with the Utah resources. So I took a chance with one of the switches since I noticed that the control ip on the switch was reachable via other two switches, so I installed Floodlight on that switch node. 

I am able to telnet to 172.17.3.22  on port 22, and its establishing the connection, so there must be some firewall rules preventing the connections on port 6633.

I din't see any on the Ubuntu VM though. It might be the case that since its a control ip only port 22 is open for outside connections. 

Anyway, I will go ahead, and request a VM with public ip address, and install Floodlight on that host. 

Thanks Niky.