Ask Your Question
1

"Verify Connectivity" part of openstack installation - Ubuntu 14.04 not working

asked 2015-01-24 03:59:22 -0600

pravinjoshi95 gravatar image

updated 2015-01-28 06:33:34 -0600

We have used 3 nodes (1 controller, 1 network and 1 compute) for installing openstack Juno. Since none of them have more than 1 NICs, we have used virtual interfaces. After creating demo-router, we are not able to ping its port (which by deafult takes up the first ip of Floating range - which it does take in our case).

We are able to ping the interface using - sudo ip netns exec qrouter-1141a29e-5728-4327-81f1-3519617e986e ping 10.1.7.220 from the network node. Following is some important information which might be useful for debugging - all commands are run on controller node:

user@c93: ~$ neutron net-list
+--------------------------------------+----------+-----------------------------------------------------+
| id                                   | name     | subnets                                             |
+--------------------------------------+----------+-----------------------------------------------------+
| dc825306-bbeb-410c-ac40-1da2b9c2307a | demo-net | fac8c0c8-aad3-4e3e-a9c6-b6af9fb721a5 192.168.1.0/24 |
| 2017a7a1-27c4-4d15-b988-aa9a698fdf86 | ext-net  | 273496fa-3ae5-43e3-b336-72d88104099a 10.1.7.0/24    |
+--------------------------------------+----------+-----------------------------------------------------+

user@c93:~$ neutron net-show demo-net
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | dc825306-bbeb-410c-ac40-1da2b9c2307a |
| name                      | demo-net                             |
| provider:network_type     | gre                                  |
| provider:physical_network |                                      |
| provider:segmentation_id  | 1                                    |
| router:external           | False                                |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | fac8c0c8-aad3-4e3e-a9c6-b6af9fb721a5 |
| tenant_id                 | 2c8136695b184bd797eeddfa534a81ef     |
+---------------------------+--------------------------------------+
user@c93:~$ neutron net-show ext-net
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | 2017a7a1-27c4-4d15-b988-aa9a698fdf86 |
| name                      | ext-net                              |
| provider:network_type     | flat                                 |
| provider:physical_network | external                             |
| provider:segmentation_id  |                                      |
| router:external           | True                                 |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | 273496fa-3ae5-43e3-b336-72d88104099a |
| tenant_id                 | 69fdf263f2674ede9268a77061acc738     |
+---------------------------+--------------------------------------+
user@c93:~$ neutron router-show demo-router
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                 | Value                                                                                                                                                                                  |
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                                                                                                                                   |
| distributed           | False                                                                                                                                                                                  |
| external_gateway_info | {"network_id": "2017a7a1-27c4-4d15-b988-aa9a698fdf86", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "273496fa-3ae5-43e3-b336-72d88104099a", "ip_address": "10.1.7.220"}]} |
| ha                    | False                                                                                                                                                                                  |
| id                    | cf6c1706-26e8-405a-9829-66dc775f810f                                                                                                                                                   |
| name                  | demo-router                                                                                                                                                                            |
| routes                |                                                                                                                                                                                        |
| status                | ACTIVE                                                                                                                                                                                 |
| tenant_id             | 2c8136695b184bd797eeddfa534a81ef                                                                                                                                                       |
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

user@c93:~$ neutron port-list
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 5bc70879-5c49-4d9e-9c6b-e4312ff2fd38 |      | fa:16:3e:77:bc:82 | {"subnet_id": "273496fa-3ae5-43e3-b336-72d88104099a", "ip_address": "10.1.7.220"}  |
| eb443ed5-72e1-4b63-ae30-1b437604fe55 |      | fa:16:3e:5e:e7:40 | {"subnet_id": "fac8c0c8-aad3-4e3e-a9c6-b6af9fb721a5", "ip_address": "192.168.1.1"} |
| f9889109-4895-47ef-ae92-642f73df9272 |      | fa:16:3e:40:44:22 | {"subnet_id": "fac8c0c8-aad3-4e3e-a9c6-b6af9fb721a5", "ip_address": "192.168.1.2"} |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
The IP 192.168.1.2 is shown to be attached to "network dhcp".

user@c93:~$ neutron router-port-list demo-router
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 5bc70879-5c49-4d9e-9c6b-e4312ff2fd38 |      | fa:16:3e:77:bc:82 | {"subnet_id": "273496fa-3ae5-43e3-b336-72d88104099a", "ip_address": "10.1.7.220"}  |
| eb443ed5-72e1-4b63-ae30-1b437604fe55 |      | fa:16:3e:5e:e7:40 | {"subnet_id": "fac8c0c8-aad3-4e3e-a9c6-b6af9fb721a5", "ip_address": "192.168.1.1"} |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+

user@c93:~$ cat /etc/hosts
127.0.0.1   localhost
//127.0.1.1 c93 //this was commented by pravin - as per suggestion in the installation manual

// The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
//controller
10.1.7.103  controller
//network
10.1.7.104  network
//compute1
10.1.7.105  compute1

On controller node
cat /etc/network/interfaces
// interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address 10.1.7.104
    netmask 255.255.255.0
    gateway 10.1.7.1
    dns-nameservers 10.1.1.61 10.1.1.62

auto eth0:1
iface eth0:1 inet static
    address 10.1.7.107
    netmask 255.255.255.0
    gateway 10.1.7.1
    dns-nameservers 10.1.1.61 10.1.1.62

//external network interface
auto eth0:2
iface eth0:2 inet static
    address 10.1.7.106
    netmask 255.255.255.0
    gateway 10.1 ...
(more)
edit retag flag offensive close merge delete
add a comment

2 answers

Sort by ยป oldest newest most voted
1

answered 2015-01-30 14:04:42 -0600

cxclark01 gravatar image

I would suggest that you look at output of "ovs-ofctl dump-flows br-tun" on both the network and compute nodes. Do this repeatedly while you ping from the VM instances to the router gateway IP.

It will help you decide if the problem is on the compute or network node. If you only have 1 compute node and 1 VM, then the 2 tables should be pretty much the same. You are looking for incrementing counters for any rows that have "actions=drop"

You can also look at "ovs-ofctl dump-ports br-tun". That should have RX and TX on port1 and port2

I have a recent OS install on 14.04 and Juno, where the flows are not getting added into br-tun OVS bridge on the network node. If the flows dont get inserted when the VM is created, then traffic will not pass from VM to qrouter. Still troubleshooting that one.

edit flag offensive delete link more
add a comment
0

answered 2015-01-25 07:01:49 -0600

schegi gravatar image

updated 2015-01-25 07:18:04 -0600

The qrouter in your ip netns exec call, should be qrouter-<id of your demo-outer> and this seems to be wrong in your example. If changing this does not work please provide ip netns and ovs-ctl show.

Stefan

edit flag offensive delete link more

Comments

Thanks for the reply...! We had found namespace id by typing "ip netns" on network node. That id is : 1141a29e-5728-4327-81f1-3519617e986e which I guess is also namespace of the router. That ping works. What doesnt work is a normal ping to router gateway (ping 10.1.7.220) . Thnx once again.

pravinjoshi95 gravatar imagepravinjoshi95 ( 2015-01-26 06:18:45 -0600 )edit

Please find the netns and ovs-vsctl outputs (network node) in the "more" part of the EDITED question. Thnx..!

pravinjoshi95 gravatar imagepravinjoshi95 ( 2015-01-26 23:11:47 -0600 )edit

Actually you do not have to guess if you run neutron router-show <router-name> you will find the id in the in the id field, in your example above it is cf6c1706-26e8-405a-9829-66dc775f810f, so 'ip netns exec qrouter-cf6c1706-26e8-405a-9829-66dc775f810f ping 10.1.7.220' should work.

schegi gravatar imageschegi ( 2015-01-27 09:13:25 -0600 )edit

What exactly do you mean with normal ping to the router gateway. pls provide the whole command here.

schegi gravatar imageschegi ( 2015-01-27 09:17:22 -0600 )edit

Yes. What you said is working - ip netns exec. What is not working is simply typing ping 10.1.7.220 in the terminal. i.e from external network - when I do a ping to router gateway - ping 10.1.7.220 it shows "Destination host unreacheable".

pravinjoshi95 gravatar imagepravinjoshi95 ( 2015-01-27 09:57:42 -0600 )edit
see more comments

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

subscribe to rss feed

Stats

Asked: 2015-01-24 03:59:22 -0600

Seen: 698 times

Last updated: Jan 28 '15

Related questions

Metadata Problem in Neutron Flat Network

l2 neutron port

neutron/ovs intermittent network failures

Newton - Instance can't access internet

Neutron Static IP

Imp::- Getting MessagingTimeout: Timed out waiting for a reply to message ID

missing public network

Linux bridge agent functioning on controller, but not compute node; both nodes visible to each other, services running

OS::Neutron::RouterInterface

Problem using pfSense VM inside a tenant