Ask Your Question

ian.s.mcb's profile - activity

overview network karma followed questions activity
2015-06-02 14:59:29 -0600 received badge ● Nice Question (source)
2014-06-26 11:30:28 -0600 received badge ● Commentator
2014-06-26 11:30:28 -0600 commented question troubleshooting neutron - unreachable instance

Thanks for the help dbaxps! I ended up resolving my problem by reverting to nova-network, which is a lot easier to understand.
2014-06-21 23:06:59 -0600 commented question ERROR: HTTPConnectionPool(host='controller' , port=8774): Max retries exceeded with url: /v2/e843a13455614b638973dd0f6239a04/os-networks (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

Same problem here. All of my nova commands stopped working, and the nova-api service won't start.
2014-06-12 11:31:57 -0600 received badge ● Famous Question (source)
2014-06-11 15:08:01 -0600 received badge ● Enthusiast
2014-06-02 13:50:04 -0600 commented question troubleshooting neutron - unreachable instance

No network traffic was displayed. How do you recommend troubleshooting DNSMASQ?
2014-06-02 11:18:26 -0600 commented question troubleshooting neutron - unreachable instance

I added "dhcp_lease_time=120" to nova.conf. After setting up the tcpdump process, should I do anything from within the instance? And what output should I expect from tcpdump?
2014-06-02 09:58:00 -0600 commented question troubleshooting neutron - unreachable instance

This is the tcpdump output that I get when pinging google from within the instance:

$ ip netns exec qdhcp-05d575e6-f98e-41d1-b0c9-09ab9274f009 tcpdump -ln -i tap9d55e069-3a
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tap9d55e069-3a, link-type EN10MB (Ethernet), capture size 65535 bytes
10:33:50.657112 IP 10.0.0.6.44805 > 10.0.0.3.domain: 2+ A? google.com. (28)
10:33:50.657271 IP 10.0.0.3.domain > 10.0.0.6.44805: 2 Refused 0/0/0 (28)
10:33:50.658010 IP 10.0.0.6.34552 > 10.0.0.3.domain: 3+ A? google.com. (28)
10:33:50.658118 IP 10.0.0.3.domain > 10.0.0.6.34552: 3 Refused 0/0/0 (28)
10:33:50.658654 IP 10.0.0.6.60201 > 10.0.0.3.domain: 4+ A? google.com. (28)
10:33:50 ...
(more)
2014-06-02 09:52:09 -0600 commented question troubleshooting neutron - unreachable instance

Here's the output from the commands that you gave me.

$ ip netns exec qdhcp-05d575e6-f98e-41d1-b0c9-09ab9274f009 ip a
12: tap9d55e069-3a: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether fa:16:3e:13:75:18 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.3/24 brd 10.0.0.255 scope global tap9d55e069-3a
    inet6 fe80::f816:3eff:fe13:7518/64 scope link 
       valid_lft forever preferred_lft forever
13: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

$ ip netns exec qdhcp-05d575e6-f98e-41d1-b0c9-09ab9274f009 netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name   
tcp        0      0 10.0.0.3:53                 0.0.0.0:*                   LISTEN ...
(more)
2014-06-01 13:45:33 -0600 commented question troubleshooting neutron - unreachable instance

I rebooted my nodes without changing any config files and now I somehow have the qr-* and qg-* interfaces on the qrouter-* namespace. Nice!

Unfortunately, now my instances are completely unreachable, even from within the qdhcp-* namespace. Any suggestions?

Running "ip netns exec qdhcp-* ip a" shows a tap* interface and a loopback interface. No eth0 interface at all.
2014-06-01 13:39:44 -0600 commented question troubleshooting neutron - unreachable instance

There were a lot of differences between your .conf/ .ini sample files and my ones. My ones came straight from running packstack. Of course, I also applied the steps explained here to get ML2: http://openstack.redhat.com/ML2_plugin

For now, I am going to stick with my files because I am uncertain about your .conf/.ini sample files.
2014-05-31 10:27:26 -0600 received badge ● Notable Question (source)
2014-05-30 15:47:39 -0600 commented answer troubleshooting neutron - unreachable instance

This has the information I was looking for.
2014-05-30 15:47:24 -0600 received badge ● Scholar (source)
2014-05-30 15:47:12 -0600 commented question troubleshooting neutron - unreachable instance

Thanks for sharing your output. Now I now that I am missing the "qr" and "qg" devices within my "qrouter" namespace.
2014-05-30 09:12:49 -0600 received badge ● Popular Question (source)
2014-05-30 03:43:26 -0600 received badge ● Student (source)
2014-05-29 15:57:12 -0600 asked a question troubleshooting neutron - unreachable instance

Could someone share with me some advice on how to troubleshoot a broken neutron config?

I have an instance that is unreachable outside of the "qdhcp" network namespace, even though it has been assigned a floating IP address on an external network. Also, when I do a "ip a" on the "qrouter" network namespace, only a loopback device is displayed.

I am using the Icehouse release with the GRE ML2 plugin for Neutron. My setup consists of two nodes (one controller/network node and one compute node), and I used RDO/packstack to install everything.
2013-10-09 14:31:12 -0600 received badge ● Supporter (source)