Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Router status is down when integrated with OpenDayLight

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
81d7f08b-80cb-45d7-a7c6-adcd58c99fe7
    Manager "tcp:10.24.84.144:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:10.24.84.144:6653"
            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, a router and set the gateway on previous provider network. Still errors´╝Ü

2017-02-28 15:35:02,087 | ERROR | ool-46-thread-45 | InterfacemgrProvider             | 335 - org.opendaylight.genius.interfacemanager-impl - 0.1.2.Boron-SR2 | Interface f7fff1f5-fba2-492d-ab87-9b0246fd589e is not present
...
2017-02-28 15:35:02,172 | ERROR | ool-46-thread-45 | NAPTSwitchSelector               | 353 - org.opendaylight.netvirt.natservice-impl - 0.3.2.Boron-SR2 | NAT Service : NAPT SWITCH SELECTION STOPPED DUE TO NO DPNS SCENARIO FOR ROUTER 4bd93c7d-1b8f-420f-9e83-2cec61d93ffd
2017-02-28 15:35:02,172 | ERROR | ool-46-thread-45 | ExternalRoutersListener          | 353 - org.opendaylight.netvirt.natservice-impl - 0.3.2.Boron-SR2 | NAT Service : Unable to to select the primary NAPT switch
2017-02-28 15:35:02,172 | ERROR | ool-46-thread-45 | ExternalRoutersListener          | 353 - org.opendaylight.netvirt.natservice-impl - 0.3.2.Boron-SR2 | NAT Service: Failed to get or allocated NAPT switch
...

And from the horizon UI, I notice that the status of the gateway port is down and can't ping the IP address of gateway.

After that, two VMs are created. The goods news is that east-west traffic flow is ok. VMs in the same selfservice network and different selfservice network can reach each other. The bad news is that both two VMs can't access the public net. And I can't ping the floaing ip neither.

Can some one point out the reason? Any more information needed is welcomed, I will update. And any help will be appreciated.

Thx very much! Waiting online...