# Revision history [back]

### Managing Pica8 switch using ovsdb

Hi,

I am trying to manage a Pica8 switch (192.168.15.250) through ovsdb southbound protocol. The switch is running a ovsdb server on port 6640

Currently I do have a working OpenFlow connection through port 6633, and I see my node in the inventory and flow topology tables of ODL (at 192.168.15.246)

I already managed to add other OVS instances of openstack nodes through the same ODL controller using OVSDB, these are working and visible in the ovsdb topology table.

However I do not see my Pica8 node in the ovsdb topology when doing a GET at: http://localhost:8181/restconf/operational/network-topology:network-topology/topology/ovsdb:1

For the Pica8 I added the ovs-vsctl set-manager "tcp:192.168.15.246:6640" command. This is the output of ovs-vsctl show

admin@PicOS-OVS$ovs-vsctl show a429f99b-0540-47d2-ac3d-c753d14d0343 Manager "tcp:192.168.15.246:6640" Bridge "br0" Controller "tcp:192.168.15.246:6633" is_connected: true Port "ge-1/1/2" tag: 1 Interface "ge-1/1/2" type: "pica8" Port "ge-1/1/1" tag: 1 Interface "ge-1/1/1" type: "pica8" Port "br0" Interface "br0" type: internal ovs_version: "2.3.0"  I do see an established TCP session between the ODL controller and the switch on port 6640: admin@PicOS-OVS$netstat -anp | grep 6640
tcp        0      0 192.168.15.250:6640     0.0.0.0:*               LISTEN      8717/ovsdb-server
tcp        0      0 192.168.15.250:50610    192.168.15.246:6640     ESTABLISHED 8717/ovsdb-server


But still it is not connected according to openvswitch, and ODL does not see it either.

If I do an ovsdb-client dump tcp:192.168.15.250:6440 command this works fine.

Does any one have any idea why the manager connection is not established? Are there some criteria that are not met for ODL / OVS to set up the connection?