Please see my response below.
> On Dec 15, 2015, at 6:28 AM, João Costa <[email protected]> wrote: > > Hi there, > > I'm trying to configure a testbed with opendaylight (odl) and > openvswitch(ovs) but I'm having some problems. Can someone give me a hand? > Until now I wasn't able to connect OVS to ODL and make ODL act as the network > controller. This is the info I'm getting now related to the controller: > > $ ovs-vsctl list controller > _uuid : 6ed37533-500f-47bc-8b79-249fc07af1b8 > connection_mode : [] > controller_burst_limit: [] > controller_rate_limit: [] > enable_async_messages: [] > external_ids : {} > inactivity_probe : [] > is_connected : false > local_gateway : [] > local_ip : [] > local_netmask : [] > max_backoff : [] > other_config : {} > role : other > status : {last_error="No route to host", > sec_since_disconnect="8", state=CONNECTING} > target : "tcp:10.0.0.200:6633" > > > <snip> > > What am I'm missing? Should I do things in a different way? > Since it's the 1st time I'm configuring OVS, do I have to configure any kind > of database? > Is the static routing not being well defined on the OVS machine? There may be reasons why you're taking the approach you're taking, but my initial recommendation would be to keep a physical interface out of OVS and use it for communications with the ODL controller. For example, let's say that eth1 is on the same network as the ODL controller---don't add eth1 to OVS and don't configure any OVS interfaces on the same network as eth1. Then see if OVS is able to communicate with the ODL controller. -- Scott _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
