Ask Your Question

Mansi Jain's profile - activity

2019-04-16 01:31:23 -0500 received badge  Famous Question (source)
2019-02-27 00:14:34 -0500 commented question OpenDaylight is not able to resolve the MAC address of the external gateway IP when integrated with OpenStack

ODL worked with OpenStack Pike but it is not working with Queens release.

2019-02-27 00:14:34 -0500 received badge  Commentator
2019-02-27 00:13:24 -0500 received badge  Notable Question (source)
2019-02-24 11:53:14 -0500 asked a question support of dpdk with opendaylight

Hi, Has anyone successfully integrated dpdk with opendaylight in openstack (queens) using kolla-ansible? If yes, what configuration is required. I tried but ODL does not create br-int after integration with DPDK. Please help.

2019-02-24 11:46:37 -0500 commented question OpenDaylight is not able to resolve the MAC address of the external gateway IP when integrated with OpenStack

I checked all the karaf logs but could not find anything related to public network.

2019-02-24 11:45:48 -0500 received badge  Popular Question (source)
2019-02-21 03:42:27 -0500 asked a question OpenDaylight is not able to resolve the MAC address of the external gateway IP when integrated with OpenStack

Hi, I integrated ODL(Carbon) with OpenStack (Queens) using kolla. But provider network(Flat,VLAN) was not working. After debugging, I found that ODL is not able to resolve the MAC address of the external gateway IP.

The below mentioned document says:

Verify OpenDaylight has successfully resolved the MAC address of the external gateway IP. This can be verified by searching for the line “Installing ext-net group” in the karaf.log.

I cannot find "Installing ext-net group” in karaf.log.

https://media.readthedocs.org/pdf/odl-netvirt/latest/odl-netvirt.pdf (https://media.readthedocs.org/pdf/odl...)

CONTROLLER NODE:

****(openvswitch-vswitchd)[root@CONTROLLER232585 /]# **ovs-vsctl show******
ecb7ea92-14d5-44cc-a75a-280f77149e1b
    Manager "tcp:172.16.140.23:6641"
        is_connected: true
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eno2"
            Interface "eno2"
        Port br-ex-int-patch
            Interface br-ex-int-patch
                type: patch
                options: {peer=br-ex-patch}
    Bridge br-int
        Controller "tcp:172.16.140.23:6653"
            is_connected: true
        fail_mode: secure
        Port "tap9aab0916-d4"
            tag: 4095
            Interface "tap9aab0916-d4"
                type: internal
        Port "tapdb35096f-bd"
            Interface "tapdb35096f-bd"
        Port br-int
            Interface br-int
                type: internal
        Port br-ex-patch
            Interface br-ex-patch
                type: patch
                options: {peer=br-ex-int-patch}
        Port "tap41518687-bb"
            Interface "tap41518687-bb"
        Port "tap6eb22bc3-70"
            tag: 4095
            Interface "tap6eb22bc3-70"
                type: internal
        Port "tund12616179b8"
            Interface "tund12616179b8"
                type: vxlan
                options: {key=flow, local_ip="172.16.140.23", remote_ip="172.16.140.42"}

DUMP FLOWS CONTROLLER NODE:

CONTROLLER

    (openvswitch-vswitchd)[root@CONTROLLER232585 /]#
    (openvswitch-vswitchd)[root@CONTROLLER232585 /]# **ovs-ofctl -OOpenFlow13 dump-flows br-int**
    cookie=0x8000001, duration=62384.328s, table=0, n_packets=261916, n_bytes=16668165, priority=5,in_port=tund12616179b8 actions=write_metadata:0xa0000000001/0xfffff0000000001,goto_table:36
    cookie=0x8000000, duration=65351.916s, table=0, n_packets=751966, n_bytes=61266807, priority=4,in_port="br-ex-patch",vlan_tci=0x0000/0x1fff actions=write_metadata:0x30000000001/0xffffff0000000001,goto_table:17
    cookie=0x8000000, duration=65346.686s, table=0, n_packets=566, n_bytes=48017, priority=4,in_port="tap9aab0916-d4",vlan_tci=0x0000/0x1fff actions=write_metadata:0x10000000000/0xffffff0000000001,goto_table:17
    cookie=0x8000000, duration=63578.321s, table=0, n_packets=387, n_bytes=41193, priority=4,in_port="tap6eb22bc3-70",vlan_tci=0x0000/0x1fff actions=write_metadata:0x40000000000/0xffffff0000000001,goto_table:17
    cookie=0x8000000, duration=63413.908s, table=0, n_packets=148, n_bytes=13764, priority=4,in_port="tapdb35096f-bd",vlan_tci=0x0000/0x1fff actions=write_metadata:0x50000000000/0xffffff0000000001,goto_table:17
    cookie=0x8000000, duration=62385.119s, table=0, n_packets=117, n_bytes=11230, priority=4,in_port="tap41518687-bb",vlan_tci=0x0000/0x1fff actions=write_metadata:0x70000000000/0xffffff0000000001,goto_table:17
    cookie=0x8000001, duration=65350.569s, table=17, n_packets=751960, n_bytes=61266165, priority=10,metadata=0x30000000000/0xffffff0000000000 actions=load:0x186a1->NXM_NX_REG3[0..24],write_metadata:0x9000030000030d42/0xfffffffffffffffe,goto_table:19
    cookie=0x8040000, duration=65350.569s, table=17, n_packets=751950, n_bytes=61265001, priority=10,metadata=0x9000030000000000/0xffffff0000000000 actions=load:0x3->NXM_NX_REG1[0..19],load:0x138a->NXM_NX_REG7[0..15],write_metadata:0xa00003138a000000/0xfffffffffffffffe,goto_table:43
    cookie=0x8000001, duration=65346.616s, table=17, n_packets=566, n_bytes=48017, priority=10,metadata=0x10000000000/0xffffff0000000000 actions=load:0x186a4->NXM_NX_REG3[0..24],write_metadata:0x9000010000030d48/0xfffffffffffffffe,goto_table:19
    cookie=0x8040000, duration=65346.616s, table=17, n_packets=566, n_bytes=48017, priority=10,metadata=0x9000010000000000/0xffffff0000000000 actions=load:0x1->NXM_NX_REG1[0..19],load:0x138a->NXM_NX_REG7[0..15],write_metadata:0xa00001138a000000/0xfffffffffffffffe,goto_table:43
    cookie=0x8000001, duration=63577.387s, table=17, n_packets=387, n_bytes=41193, priority=10,metadata=0x40000000000/0xffffff0000000000 actions=load:0x186a7->NXM_NX_REG3[0..24 ...
(more)
2019-02-21 00:59:37 -0500 received badge  Notable Question (source)
2019-02-19 06:51:26 -0500 received badge  Popular Question (source)
2019-02-18 03:00:20 -0500 asked a question OpenStack(Queens) and Opendaylight(Carbon) integration using kolla-anisble

Hi, After integration of ODL(Carbon) with OpenStack(Queens),flat network is not working(VM not able to ping external gateway). After debugging, I found that gateway MAC inside dhcp namespace is incorrect. It picks up the random MAC address everytime I create a new flat network. Anyone managed to work flat network with the same release or any other release?

2019-02-01 01:41:29 -0500 received badge  Notable Question (source)
2019-01-31 05:31:07 -0500 commented question Opendaylight integration with OpenStack Queens release

Is there no linux bridge in Openstack with ODL. If no, then how VM is connected to br-int.

2019-01-30 00:57:36 -0500 commented question Opendaylight integration with OpenStack Queens release

Shall I try different release of Opendaylight (either Nitrogen or Oxygen) with OpenStack(Queens)? Please refer to this link :

https://docs.opendaylight.org/en/stable-nitrogen/submodules/netvirt/docs/user-guide/support.html (https://docs.opendaylight.org/en/stab...)

2019-01-28 03:07:55 -0500 commented question Opendaylight integration with OpenStack Queens release

So, why my compute host VMs are not getting IP on external/Flat network. Am i doing something incorrect ?

2019-01-28 01:12:58 -0500 received badge  Enthusiast
2019-01-27 23:47:44 -0500 commented question Opendaylight integration with OpenStack Queens release

Cannot see Bridge br-tun in the output of ovs-vsctl command. Can you please tell why there is no br-tun?

2019-01-27 22:51:57 -0500 commented question Opendaylight integration with OpenStack Queens release

Anyone successfully integrated ODL with Openstack queens?

2019-01-27 22:41:52 -0500 received badge  Popular Question (source)
2019-01-24 23:39:57 -0500 commented question Opendaylight integration with OpenStack Queens release

Also I am not able to ping external gateway from DHCP namespace. After debugging I found that inside DHCP namespace mac address of external gateway is different than its actual mac address.

2019-01-24 23:15:33 -0500 commented question Opendaylight integration with OpenStack Queens release

DHCP is enabled in public network. Is my configuration correct? ODL version is 0.4.3.Carbon. But private network VMs are working fine with this configuration. Only public network VMs are not getting IP.

2019-01-23 05:34:31 -0500 commented question Opendaylight integration with OpenStack Queens release

Hi , Thanks for the response. I have updated my question with the output of docker exec openvswitch_vsiwtchd ovs-vsctl show on compute and network nodes.

2019-01-23 01:14:00 -0500 asked a question Opendaylight integration with OpenStack Queens release

Hi, I was trying to integrate ODL with OpenStack (Queens) using Kolla-ansible. I did the following configuration in globals.yaml:

neutron_plugin_agent: "opendaylight"
 enable_opendaylight: "yes"

Also, I have to do the following modifications in kolla-ansible (stable/queens) code for my setup to be up: https://review.openstack.org/#/c/571441/

After successful deployment, ml2_conf.ini looks like this:

[ml2]
type_drivers = flat,vlan,vxlan
tenant_network_types = vxlan
mechanism_drivers = opendaylight_v2
extension_drivers = port_security

[ml2_odl]
url = http://172.16.141.167:8088/controller/nb/v2/neutron
username = admin
password = gOI3BfzrDTNM2y7WFOkQavc6Z8EUe6BLhSBirgJN
port_binding_controller = pseudo-agentdb-binding

[ml2_type_vlan]
network_vlan_ranges =

[ml2_type_flat]
flat_networks = physnet1

[ml2_type_vxlan]
vni_ranges = 1:1000
vxlan_group = 239.1.1.1

[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver

[agent]
tunnel_types = vxlan
l2_population = true
arp_responder = true

[ovs]
bridge_mappings = physnet1:br-ex
datapath_type = system
ovsdb_connection = tcp:127.0.0.1:6640
local_ip = 172.16.141.39

docker exec openvswitch_vsiwtchd ovs-vsctl show on network node:

  (openvswitch-vswitchd)[root@CONTROLLER397662 /]# ovs-vsctl show
4369a98a-4108-415d-afb6-137a1d729056
    Manager "tcp:172.16.141.39:6641"
        is_connected: true
    Bridge br-int
        Controller "tcp:172.16.141.39:6653"
            is_connected: true
        fail_mode: secure
        Port "tap482b5942-2e"
            tag: 4095
            Interface "tap482b5942-2e"
                type: internal
        Port br-ex-patch
            Interface br-ex-patch
                type: patch
                options: {peer=br-ex-int-patch}
        Port "tapa79c00cd-de"
            tag: 4095
            Interface "tapa79c00cd-de"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tun4475255a1c1"
            Interface "tun4475255a1c1"
                type: vxlan
                options: {key=flow, local_ip="172.16.141.39", remote_ip="172.16.141.36"}
    Bridge br-ex
        Port "eno2"
            Interface "eno2"
        Port br-ex
            Interface br-ex
                type: internal
        Port br-ex-int-patch
            Interface br-ex-int-patch
                type: patch
                options: {peer=br-ex-patch}

docker exec openvswitch_vsiwtchd ovs-vsctl show on compute node:

(openvswitch-vswitchd)[root@COMPUTE362635 /]# ovs-vsctl show
9903fa01-adc8-4c8f-88b1-c5c779de46ae
    Manager "tcp:172.16.141.39:6641"
        is_connected: true
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eno2"
            Interface "eno2"
        Port br-ex-int-patch
            Interface br-ex-int-patch
                type: patch
                options: {peer=br-ex-patch}
    Bridge br-int
        Controller "tcp:172.16.141.39:6653"
            is_connected: true
        fail_mode: secure
        Port "tun2e2c38b74f9"
            Interface "tun2e2c38b74f9"
                type: vxlan
                options: {key=flow, local_ip="172.16.141.36", remote_ip="172.16.141.39"}
        Port br-ex-patch
            Interface br-ex-patch
                type: patch
                options: {peer=br-ex-int-patch}
        Port br-int
            Interface br-int
                type: internal

Also, I tested ODL integration with OpenStack with the following command:

curl -u admin:gOI3BfzrDTNM2y7WFOkQavc6Z8EUe6BLhSBirgJN http://172.16.141.167:8088/controller/nb/v2/neutron/networks (http://172.16.141.167:8088/controller...)

Output:

{
   "networks" : [ {
      "id" : "bd8db3a8-2b30-4083-a8b3-b3fd46401142",
      "tenant_id" : "bd8db3a82b304083a8b3b3fd46401142",
      "project_id" : "bd8db3a8-2b30-4083-a8b3-b3fd46401142",
      "name" : "Sync Canary Network",
      "admin_state_up" : false,
      "status" : "ACTIVE",
      "shared" : false,
      "router:external" : false,
      "provider:network_type" : "flat",
      "segments" : [ ]
   }, {
      "id" : "a280dcec-3402-46f6-9d95-39868bd36eda",
      "tenant_id" : "3a53dc2483564d8c9d993ead57da1362",
      "project_id" : "3a53dc2483564d8c9d993ead57da1362",
      "revision_number" : 2,
      "name" : "demo-net",
      "admin_state_up" : true,
      "status" : "ACTIVE",
      "shared" : false,
      "router:external" : false,
      "provider:network_type" : "vxlan",
      "provider:segmentation_id" : "25",
      "segments" : [ ]
   }, {
      "id" : "af3f87f8-ba87-4972-834b-81eb69c77bd0",
      "tenant_id" : "3a53dc2483564d8c9d993ead57da1362",
      "project_id" : "3a53dc2483564d8c9d993ead57da1362",
      "revision_number" : 5,
      "name" : "public1",
      "admin_state_up" : true,
      "status" : "ACTIVE",
      "shared" : false,
      "router:external" : true,
      "provider:network_type" : "flat",
      "provider:physical_network" : "physnet1",
      "segments" : [ ]
   } ]
}

But when I launched cirros instances on public network, My VMs donot get IP from DHCP. Although, VMs on private network are working fine.

Please help regarding this issue.

Regards, Mansi

2018-04-13 11:06:02 -0500 received badge  Popular Question (source)