DPSET: Multiple connections in Ryu SDN Controller

  • 2 Replies
  • 2840 Views
*

ar801112usa

  • Newbie
  • *
  • 8
    • View Profile
DPSET: Multiple connections in Ryu SDN Controller
« on: June 23, 2016, 06:30:43 PM »
I install latest Ryu controller from pip install(Python3) in Ubuntu 14.04 on VM(VM-A), and NIC configure as bridge mode(192.168.88.252).

I assume VM-A's host is "Host-A"

And connect physical Zodiac FX Openflow switch, port4(reserve for connect with controller, 192.168.88.252) to router(192.168.88.0/24)

Zodiac FX port3 connect to router(192.168.88.0/24)

And connect Two RPI(AKA Host-B,C) on Zodiac FX port 1,2(so, two rpi will get 192.168.88.250, 192.168.88.249)

And connect controller Host-A to router(192.168.88.253)

It work fine, and two rpi able to connect internet.

Host-A able to connect two rpi. But if I trying to use VM-A to do any kind of connect with two rpi.

Hole controller will stuck for few minute, an get message:

Quote
DPSET: Multiple connections {dpid}

I wounder to know there is illegal when I using SDN controller to communicate with openflow networking devices?

In my case, my ryu app run simple_switch_13.py.

Thanks!

*

Paul Zanna

  • Moderator
  • Sr. Member
  • *****
  • 370
    • View Profile
    • Northbound Networks
Re: DPSET: Multiple connections in Ryu SDN Controller
« Reply #1 on: June 23, 2016, 07:07:45 PM »
By default ports 1,2 & 3 are OpenFlow ports and Port 4 is a non-OpenFlow ports, they are actually separated by untagged VLANs within the Zodiac. It is not possible to communicate between OpenFlow and Non-OpenFlow ports (or VLANs), connecting them together as you have may even cause a loop in your network which is probably why you are getting the error. I would recommend using a seperate NIC for your VM and connecting it directly to port 4 on the Zodiac which will keep them isolated.

Regards,
Paul

*

ar801112usa

  • Newbie
  • *
  • 8
    • View Profile
Re: DPSET: Multiple connections in Ryu SDN Controller
« Reply #2 on: June 23, 2016, 08:17:03 PM »
By default ports 1,2 & 3 are OpenFlow ports and Port 4 is a non-OpenFlow ports, they are actually separated by untagged VLANs within the Zodiac. It is not possible to communicate between OpenFlow and Non-OpenFlow ports (or VLANs), connecting them together as you have may even cause a loop in your network which is probably why you are getting the error. I would recommend using a seperate NIC for your VM and connecting it directly to port 4 on the Zodiac which will keep them isolated.

Regards,
Paul

Thank you for your fast reply!

After tested, if I spread another subnet(192.168.80.0/24) for sdn switch communicate with controller.

This problem solved!, SDN controller need another NIC to connect another subnet.

I still can using SDN controller access 192.168.88.0/24 without DPSET problem.