Ask Your Question
0

Issue on network access

asked 2014-04-11 06:39:21 -0500

verytest gravatar image

updated 2014-05-06 10:32:50 -0500

Hello

I have installed OpenStack (icehouse) using Packstack, all the installation goes well and I can access the dahsboard, creating instance... I have an issue on network

I have read a lot of posts here to find the way to correct it, but I am still blocking.

I am running OpenStack within a VirtualBox VM managed by Vagrant with the following settings.

My VM has 4 networks interfaces:

eth0: NAT, 10.0.2.15 
eth1: host only, 172.16.0.200 
eth2: host only, 10.10.0.200
eth3: host only, 192.168.0.200

I ran after installing packstack

ovs-vsctl add-port br-ex eth3

For OpenStack, I setup

10.10.3.0/24 for the data network 
192.168.100.0/24 for the external network with start=192.168.100.10 and end=192.168.100.20

I ran ovs-vsctl show

dd23105a-31e7-4bf3-9b76-86b1285349f9
    Bridge br-int
        Port "tap1a24ecf9-8b"
            tag: 1
            Interface "tap1a24ecf9-8b"
        Port "qvo9cfd8817-98"
            tag: 1
            Interface "qvo9cfd8817-98"
        Port "tap728369d2-35"
            tag: 1
            Interface "tap728369d2-35"
        Port br-int
            Interface br-int
                type: internal
        Port "qvof07afef6-ea"
            tag: 1
            Interface "qvof07afef6-ea"
    Bridge br-ex
        Port "tap7bfa779c-4e"
            Interface "tap7bfa779c-4e"
        Port "eth3"
            Interface "eth3"
        Port br-ex
            Interface br-ex
                type: internal
    ovs_version: "1.11.0"

I launch a first instance that got

IP: 10.10.3.2
Floating IP: 192.168.100.11

The instance is ACTIVE and Running according to nova list

Looking at network topology:

10.10.3.1 is router_interface and is ACTIVE 
192.168.100.10 is router_gateway and is DOWN

I still can not ping or ssh my instance (10.10.3.2 or 192.168.100.11)

Here are some commands I ran: ip netns

qdhcp-bec2edaf-7695-4a59-a27b-1a4485c464d7
qrouter-bf9049f2-c331-4e8b-981e-d2673f95e447

ip netns exec 'qrouter-bf9049f2-c331-4e8b-981e-d2673f95e447' ifconfig

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

qg-7bfa779c-4e Link encap:Ethernet  HWaddr FA:16:3E:E4:84:55  
          inet addr:192.168.100.10  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fee4:8455/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1404 (1.3 KiB)  TX bytes:846 (846.0 b)

qr-728369d2-35 Link encap:Ethernet  HWaddr FA:16:3E:CB:5D:3A  
          inet addr:10.10.3.1  Bcast:10.10.3.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fecb:5d3a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-04-11 10:02:11 -0500

Try executing commands on the virtual router with:

ip netns (it would respond with 'your-qrouter-name')

ip netns exec qrouter 'your-qrouter-name' ifconfig

Then try pinging the instance from the router (this assures that from the internal network point of view all is going fine):

ip netns exec qrouter <your-qrouter-name> ping 172.16.1.4

If you could ping it you could probably get ssh access with:

ip netns exec qrouter ssh user@172.16.1.4

Then you could try to ping your gateway from the router, and the floating-ip itself:

ip netns exec qrouter <your-qrouter-name> ping 10.10.1.1

ip netns exec qrouter <your-qrouter-name> ping 10.10.1.151

edit flag offensive delete link more

Comments

Ciao Antonio

It seems you point to the correct issue.

Indeed, when I ran the following command within the VM running OpenStack (172.16.0.201)

ip netns

I have an empty result (instead of having the qrouter name as you quoted) with "0" as return code

So what does wrong ?

Grazie Verytest

verytest gravatar imageverytest ( 2014-04-11 11:10:39 -0500 )edit

Ciao,

You could have a look in /var/log/neuron/ files; maybe there are some meaningful errors there. You could try to enable verbose and debug mode in neutron conf file (usually /etc/neutron/neutron.conf) and restart neutron related services.

Antonio G. gravatar imageAntonio G. ( 2014-04-14 04:59:10 -0500 )edit

What is output :-
$ neutron agent-list
$ service neutron-metadata-agent status

dbaxps gravatar imagedbaxps ( 2014-05-02 22:42:25 -0500 )edit

Hello

neutron agent-list

+--------------------------------------+--------------------+----------------+-------+----------------+
| id                                   | agent_type         | host           | alive | admin_state_up |
+--------------------------------------+--------------------+----------------+-------+----------------+
| 5c08a328-a249-4428-a758-2520b3343c6f | DHCP agent         | laya.openstack | :-)   | True           |
| 68ac0e71-967e-42eb-bd27-832e789cb98e | Metadata agent     | laya.openstack | :-)   | True           |
| 6aca29d7-2d95-43e9-8d88-a7cd00144f0e | Open vSwitch agent | laya.openstack | :-)   | True           |
| 83cf8a59-ddb4-4bd0-a36c-1998def10cc4 | L3 agent           | laya.openstack | :-)   | True           |
+--------------------------------------+--------------------+----------------+-------+----------------+

service neutron-metadata-agent status

neutron-metadata-agent (pid  2859) is running...

Regards

verytest gravatar imageverytest ( 2014-05-03 02:29:50 -0500 )edit

Good news... After rebooting, "ip netns exec qrouter-0c9ad418-c859-4d0c-a0f9-2091650d6036 ifconfig" returns something

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1008 (1008.0 b)  TX bytes:1008 (1008.0 b)

qg-95fdb670-e4 Link encap:Ethernet  HWaddr FA:16:3E:DE:7E:2C  
          inet addr:192.168.100.10  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fede:7e2c/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:216 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes ...
(more)
verytest gravatar imageverytest ( 2014-05-03 04:35:32 -0500 )edit
0

answered 2014-05-08 22:38:12 -0500

dbaxps gravatar image
So,long way troubleshoooting (view thread above) brought us to success
with outbound and inbound connectivity for VMs running in AIO IceHouse on VirtualBox VM managed by Vagrant.    Final steps  in thread above were

1. Recreating  external network as follows
$ neutron net-create net-external --router:external=True --shared
$ neutron subnet-create --gateway 192.168.0.200 --allocation-pool
start=192.168.0.100,end=192.168.0.120 --disable-dhcp --name subnet-external net-external 192.168.0.0/24

2.  Recreating  properly OVS bridge ond OVS port.
edit flag offensive delete link more

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

1 follower

Stats

Asked: 2014-04-11 06:39:21 -0500

Seen: 504 times

Last updated: May 08 '14