Ask Your Question

Router status is down when integrated with OpenDayLight

asked 2017-02-28 21:42:31 -0500

MonsieurWilson gravatar image

Hi there,

I am trying to integrate Opendaylight Boron with OpenStack Newton, but encouter some problems. I have followed the (OpenStack with NetVirt Docs) with three CentOS 7.1 servers.

At first, a deployment of 1 controller 1 network and 1 compute OpenStack is done, and everything works fine. (Not devstack)

Then, I install the Opendaylight odl-router on my OpenStack cloud, and make every configuration according to the previous link.

Here are some informations that may be important for you to help me:)

OpenStack Deployment:

  • Controller Node: (neutron-server)
    • neutron.conf is modified correctly
    • Opendaylight controller is started and ${CONTROLLER}:8181/index.html looks fine.
  • Network Node:
    • neutron-openvswitch-agent is shutted down
    • Open vSwitch configuration is empty and the manager is correctly set
  • Network Node: (neutron-dhcp-agent neutron-metadata-agent)
    • neutron-l3-agent is shutted down (Is it correct ? I'm not sure)
    • neutron-dhcp-agent & neutron-metadata-agent configuration is modified correctly
  • Each Node have two interfaces em1 em2. em1 for tunnel and em2 for provider network.

Opendaylight Boron version:

  • distribution-karaf-0.5.2-Boron-SR2

Open vSwitch version: (I have tested following two versions, but encountered the same problem)

  • 2.6.1
  • 2.5.0

The kernel modules releated with openvswitch looks like:

$lsmod | grep openvswitch
openvswitch           257678  4 vport_vxlan
nf_nat_ipv6            13279  1 openvswitch
nf_nat_ipv4            13263  2 openvswitch,iptable_nat
nf_defrag_ipv6         34651  2 openvswitch,nf_conntrack_ipv6
nf_defrag_ipv4         12729  2 openvswitch,nf_conntrack_ipv4
nf_nat                 21798  4 openvswitch,nf_nat_ipv4,nf_nat_ipv6,iptable_nat
nf_conntrack          101024  7 openvswitch,nf_nat,nf_nat_ipv4,nf_nat_ipv6,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6
gre                    13808  1 openvswitch
libcrc32c              12644  2 xfs,openvswitch

After configuring external network on Network Node, ovs-vsctl looks like:

$ovs-vsctl set Open_vSwitch . other_config:provider_mappings=provider:em2
$ovs-vsctl show
    Manager "tcp:"
        is_connected: true
    Bridge br-int
        Controller "tcp:"
            is_connected: true
        fail_mode: secure
        Port "em2"
            Interface "em2"
        Port br-int
            Interface br-int
                type: internal

But I got some errors in karaf.log:

2017-02-28 15:23:07,284 | ERROR | ool-46-thread-15 | InterfacemgrProvider             | 335 - org.opendaylight.genius.interfacemanager-impl - 0.1.2.Boron-SR2 | Interface 229203650765326:em2:flat is not present
2017-02-28 15:23:07,287 | ERROR | ool-46-thread-15 | VpnInterfaceManager              | 344 - org.opendaylight.netvirt.vpnmanager-impl - 0.3.2.Boron-SR2 | Handling addition of VPN interface 229203650765326:em2:flat skipped as interfaceState is not available 
2017-02-28 15:23:07,614 | ERROR | ool-46-thread-15 | NatInterfaceStateChangeListener  | 353 - org.opendaylight.netvirt.natservice-impl - 0.3.2.Boron-SR2 | Unable to process add for interface 229203650765326:em2 ,since Interface ConfigDS entry absent for the same
2017-02-28 15:23:07,614 | ERROR | ool-46-thread-15 | InterfaceStateChangeListener     | 344 - org.opendaylight.netvirt.vpnmanager-impl - 0.3.2.Boron-SR2 | Unable to process add for interface 229203650765326:em2 ,since Interface ConfigDS entry absent for the same
2017-02-28 15:23:07,617 | ERROR | ool-46-thread-15 | SubnetOpDpnManager               | 344 - org.opendaylight.netvirt.vpnmanager-impl - 0.3.2.Boron-SR2 | Cannot get, portOp for port 229203650765326:em2:flat is not available in datastore
2017-02-28 15:23:07,782 | ERROR | entLoopGroup-9-6 | DeviceFlowRegistryImpl           | 295 - org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 | Flow with flowId L2switch-5 already exists in table 0

Then I create a provider network and subnet ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2017-03-15 05:05:15 -0500

MonsieurWilson gravatar image

Good news. Network finally works fine with version distribution-karaf-0.4.4-Boron-SR2.

edit flag offensive delete link more

answered 2017-03-02 17:13:16 -0500

rvinkovic gravatar image

Having same problem. I but it was working yesterday normally but after restart everything is messed up. On this page (link text) it says that icmp is not working(that is true i did test it yesterday and ssh was working but ping didnt). I dont see any errors anywhere but it is still not working. Try to ssh into floating ip or ssh from vm to the compute server.

edit flag offensive delete link more


I'm afraid we encountered the different case? I can ssh into controller/compute/network node from VM, but can't ssh into VM from any node. But still thanks a lot. ODL Summit 2016 PPT shows that we can ping the VMs from outside, so I just believe that and had never try to ssh from VM.

MonsieurWilson gravatar imageMonsieurWilson ( 2017-03-02 20:50:06 -0500 )edit

May be there are still some problems with ODL DNAT? Any other ideas?

MonsieurWilson gravatar imageMonsieurWilson ( 2017-03-02 20:50:55 -0500 )edit

It's pretty strange that VM can't ssh outside nodes after associated a floating IP. Life sucks..

MonsieurWilson gravatar imageMonsieurWilson ( 2017-03-02 23:45:08 -0500 )edit

Bugs everywhere and no answers on forums and anywhere. I feel you. I was talking with my mentor today and i think will not use ODL for my Openstack because bugs and half of the things dont work still.

rvinkovic gravatar imagervinkovic ( 2017-03-03 05:02:02 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2017-02-28 21:42:31 -0500

Seen: 532 times

Last updated: Mar 15 '17