<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Hi Darragh,</div>
</div>
</div>
<div>Thanks a lot for your suggestion. It solved the issue for me also.</div>
<div>I also had the same issue on a Folsom install done by following the user guide:</div>
<div><a href="http://docs.openstack.org/folsom/basic-install/content/index.html">http://docs.openstack.org/folsom/basic-install/content/index.html</a></div>
<div>At that time I thought it was an issue with my setup and so I decided to upgrade to Grizzly.</div>
<div><br>
</div>
<div>Wouldn't this be an issue that everyone doing a plain openstack install would face? Its hard to imagine why it has not been noticed before.</div>
<div><br>
</div>
<div>Is there a way I can add the changing of the MTU to the meta data so that it automatically applies to new Vms?</div>
<div><br>
</div>
<div>Thanks again Darragh for all your time and help.</div>
<div><br>
</div>
<div>-Farhan.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Rahul Sharma <<a href="mailto:rahulsharmaait@gmail.com">rahulsharmaait@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, May 30, 2013 12:57 AM<br>
<span style="font-weight:bold">To: </span>Darragh O'Reilly <<a href="mailto:dara2002-openstack@yahoo.com">dara2002-openstack@yahoo.com</a>><br>
<span style="font-weight:bold">Cc: </span>Farhan Patwa <<a href="mailto:Farhan.Patwa@utsa.edu">Farhan.Patwa@utsa.edu</a>>, OpenStack Maillist <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi Darragh,
<p class=""> </p>
<p class="">Even I am facing the same issue of request getting timed out and even updates getting hanged up for very long time. I followed your step of reducing the MTU size from 1500 to 1454 and now everything works fine. I tried this on Ubuntu instances.</p>
<p class=""> </p>
<p class="">This seems to be an issue with the Grizzly release. I had already started email-thread earlier for this but was unable to find the root cause. Here is the link to it:-<br>
</p>
<p class=""><a href="https://lists.launchpad.net/openstack/msg23993.html">https://lists.launchpad.net/openstack/msg23993.html</a></p>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Thank you for your suggestion of reducing the MTU size as it solved the problem. You must file a bug for this so that this issue can be tracked.<br>
<br>
</div>
<div class="gmail_extra">Thanks and Regards<br>
Rahul Sharma<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, May 30, 2013 at 2:23 AM, Darragh O'Reilly <span dir="ltr">
<<a href="mailto:dara2002-openstack@yahoo.com" target="_blank">dara2002-openstack@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Farhan,<br>
<br>
I was able to reproduce this with curl from the cirros 0.3.1 that supports ssl.<br>
<br>
cirros$ curl -L <a href="http://github.com" target="_blank">github.com</a> # -L follow redirects<br>
<br>
it just hangs and I get these ICMPs on the netnode's physical nic. <br>
<br>
20:33:10.811485 IP (tos 0xc0, ttl 63, id 13647, offset 0, flags [none], proto ICMP (1), length 576)<br>
192.168.101.2 > <a href="http://204.232.175.90" target="_blank">204.232.175.90</a>: ICMP 192.168.101.2 unreachable - need to frag (mtu 1454), length 556<br>
IP (tos 0x0, ttl 51, id 54729, offset 0, flags [DF], proto TCP (6), length 1500)<br>
204.232.175.90.443 > 192.168.101.2.41237: Flags [.], seq 1:1449, ack 225, win 7, options [nop,nop,TS val 4208725487 ecr 171322], length 1448<br>
<br>
So I reduced the mtu from the default 1500 to 1454 on the instance and now 'curl -L
<a href="http://github.com" target="_blank">github.com</a>' works<br>
<br>
cirros$ sudo ip link set mtu 1454 dev eth0<br>
<br>
Will need to look into this more. Maybe to do with the GRE tunnels (+~20bytes?) or iptables. Anyway try reducing the mtu for now.<br>
<div class="im HOEnZb"><br>
Darragh.<br>
<br>
<br>
----- Original Message -----<br>
> From: Farhan Patwa <<a href="mailto:Farhan.Patwa@utsa.edu">Farhan.Patwa@utsa.edu</a>><br>
</div>
<div class="im HOEnZb">> To: Darragh O'Reilly <<a href="mailto:dara2002-openstack@yahoo.com">dara2002-openstack@yahoo.com</a>>; OpenStack Maillist <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Cc:<br>
</div>
<div class="HOEnZb">
<div class="h5">> Sent: Wednesday, 29 May 2013, 18:14<br>
> Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04<br>
><br>
> Hi Darragh,<br>
> Thank you soo Much! That was it! Now I am able to connect to the VM with<br>
> no issues.<br>
><br>
> But I am back to another network issue I had when I had Folsom installed<br>
> on the same setup.<br>
> I would really appreciate if you can provide any pointers here.<br>
><br>
><br>
> I able to spawn VM get IP, set floating IP and now am trying to do some<br>
> development within the VM.<br>
> I am unable to connect to certain sites and ports:<br>
> git clone <a href="https://github.com/openstack-dev/devstack.git" target="_blank">
https://github.com/openstack-dev/devstack.git</a> - <-- This just<br>
> times out.<br>
><br>
> ###########################################################################<br>
> #############<br>
> This is what works:<br>
> Wget <a href="http://google.com" target="_blank">google.com</a><br>
> Wget <a href="http://openstack.com" target="_blank">openstack.com</a><br>
> ###########################################################################<br>
> #############<br>
> This is what hangs and times out:<br>
><br>
> Wget <a href="http://yahoo.com" target="_blank">yahoo.com</a><br>
> Wget <a href="http://paypal.com" target="_blank">paypal.com</a><br>
> Wget <a href="http://facebook.com" target="_blank">facebook.com</a><br>
> Wget <a href="http://github.com" target="_blank">github.com</a><br>
> ubuntu@fpatwa-1:~$ wget <a href="http://github.com" target="_blank">github.com</a><br>
> --2013-05-10 19:08:19-- <a href="http://github.com/" target="_blank">http://github.com/</a><br>
> Resolving <a href="http://github.com" target="_blank">github.com</a> (<a href="http://github.com" target="_blank">github.com</a>)... 204.232.175.90<br>
> Connecting to <a href="http://github.com" target="_blank">github.com</a> (<a href="http://github.com" target="_blank">github.com</a>)|204.232.175.90|:80... connected.<br>
> HTTP request sent, awaiting response... 301 Moved Permanently<br>
> Location: <a href="https://github.com/" target="_blank">https://github.com/</a> [following]<br>
> --2013-05-10 19:08:20-- <a href="https://github.com/" target="_blank">https://github.com/</a><br>
> Connecting to <a href="http://github.com" target="_blank">github.com</a> (<a href="http://github.com" target="_blank">github.com</a>)|204.232.175.90|:443... connected.<br>
><br>
> ###########################################################################<br>
> #############<br>
><br>
> The same commands works on the network node.<br>
><br>
><br>
> The pattern that I can see is that any SSL website fails (port 443) but<br>
> then something like yahoo fails also and its at port 80.<br>
><br>
><br>
> Here are my security rules:<br>
> +-------------+-----------+---------+-----------+--------------+<br>
> | IP Protocol | From Port | To Port | IP Range | Source Group |<br>
> +-------------+-----------+---------+-----------+--------------+<br>
> | icmp | -1 | -1 | <a href="http://0.0.0.0/0" target="_blank">
0.0.0.0/0</a> | |<br>
> | tcp | 1 | 65535 | <a href="http://0.0.0.0/0" target="_blank">
0.0.0.0/0</a> | |<br>
> | tcp | 22 | 22 | <a href="http://0.0.0.0/0" target="_blank">
0.0.0.0/0</a> | |<br>
> | udp | 1 | 65535 | <a href="http://0.0.0.0/0" target="_blank">
0.0.0.0/0</a> | |<br>
> +-------------+-----------+---------+-----------+--------------+<br>
><br>
><br>
><br>
> I have messed around with all kinds of combinations of security rules but<br>
> no luck so far.<br>
><br>
> Thanks,<br>
><br>
> -Farhan.<br>
><br>
><br>
><br>
><br>
> On 5/28/13 3:28 PM, "Darragh O'Reilly"<br>
> <<a href="mailto:dara2002-openstack@yahoo.com">dara2002-openstack@yahoo.com</a>><br>
> wrote:<br>
><br>
>> Hi,<br>
>><br>
>> the ping error "connect: Network is unreachable" means a route<br>
> could not<br>
>> be found.<br>
>><br>
>> The gateway 10.245.124.253 for the external subnet is not in the subnet<br>
>> CIDR <a href="http://10.245.124.64/26" target="_blank">10.245.124.64/26</a>.<br>
>><br>
>><br>
>> So I guess a default route was not setup here:<br>
>> netnode$ ip netns exec <router ns> route -n<br>
>><br>
>> You will need to create the subnet with a CIDR that includes the gateway<br>
>> ip - something like this:<br>
>> quantum subnet-create <ext-net-id> <a href="http://10.245.124.192/26" target="_blank">
10.245.124.192/26</a> --gateway<br>
>> 10.245.124.253 --enable_dhcp False<br>
>><br>
>> Darragh.<br>
>><br>
>><br>
>> ----- Original Message -----<br>
>>> From: Farhan Patwa <<a href="mailto:Farhan.Patwa@utsa.edu">Farhan.Patwa@utsa.edu</a>><br>
>>> To: Darragh OReilly <<a href="mailto:darragh.oreilly@yahoo.com">darragh.oreilly@yahoo.com</a>>; OpenStack<br>
> Maillist<br>
>>> <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
>>> Cc:<br>
>>> Sent: Tuesday, 28 May 2013, 19:52<br>
>>> Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04<br>
>>><br>
>>> Hi Darragh,<br>
>>> Thanks a lot for your reply and suggestions.<br>
>>> I am not able to ping the gateway ip from the namespace.<br>
>>> Also eth0 is up but br-ex has unknown state?<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>> root@openstack-2:~# ip link<br>
>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state<br>
> UNKNOWN<br>
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
>>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq<br>
> state UP<br>
>>> qlen<br>
>>> 1000<br>
>>> link/ether 78:2b:cb:27:1f:c8 brd ff:ff:ff:ff:ff:ff<br>
>>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq<br>
> state UP<br>
>>> qlen<br>
>>> 1000<br>
>>> link/ether 78:2b:cb:27:1f:c9 brd ff:ff:ff:ff:ff:ff<br>
>>> 4: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue<br>
>>> state<br>
>>> UNKNOWN<br>
>>> link/ether f2:3b:f7:1b:b0:46 brd ff:ff:ff:ff:ff:ff<br>
>>> 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue state<br>
>>> UNKNOWN<br>
>>> link/ether 78:2b:cb:27:1f:c8 brd ff:ff:ff:ff:ff:ff<br>
>>> 32: br-tun: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue<br>
>>> state<br>
>>> UNKNOWN<br>
>>> link/ether 7e:6c:65:0f:c9:43 brd ff:ff:ff:ff:ff:ff<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>><br>
>>> Here is the result of the tcpdump as ping is being done:<br>
>>><br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>> root@openstack-2:~# ip netns exec<br>
>>> qrouter-32f35fb4-f9f1-4817-8818-fff832f73810 ping -c1 10.245.124.253<br>
>>> connect: Network is unreachable<br>
>>><br>
>>> root@openstack-2:~# tcpdump -nei eth0<br>
>>> tcpdump: WARNING: eth0: no IPv4 address assigned<br>
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol<br>
>>> decode<br>
>>> listening on eth0, link-type EN10MB (Ethernet), capture size 65535<br>
> bytes<br>
>>> 13:46:31.399055 00:26:88:7a:40:87 > 01:80:c2:00:00:00, 802.3, length<br>
> 60:<br>
>>> LLC, dsap STP (0x42) Individual, ssap STP (0x42) Command, ctrl 0x03:<br>
> STP<br>
>>> 802.1w, Rapid STP, Flags [Proposal], bridge-id<br>
>>> 8000.00:26:88:7a:40:81.8205, length 43<br>
>>> 13:46:33.259195 c2:35:07:e7:b0:10 > ff:ff:ff:ff:ff:ff, ethertype ARP<br>
>>> (0x0806), length 60: Reply 10.245.0.10 is-at c2:35:07:e7:b0:10, length<br>
>>> 46<br>
>>> 13:46:33.313988 00:26:88:7a:40:87 > 01:80:c2:00:00:00, 802.3, length<br>
> 60:<br>
>>> LLC, dsap STP (0x42) Individual, ssap STP (0x42) Command, ctrl 0x03:<br>
> STP<br>
>>> 802.1w, Rapid STP, Flags [Proposal], bridge-id<br>
>>> 8000.00:26:88:7a:40:81.8205, length 43<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>><br>
>>><br>
>>> The other information that you wanted is:<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>> root@openstack-2:~# ip link<br>
>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state<br>
> UNKNOWN<br>
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
>>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq<br>
> state UP<br>
>>> qlen<br>
>>> 1000<br>
>>> link/ether 78:2b:cb:27:1f:c8 brd ff:ff:ff:ff:ff:ff<br>
>>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq<br>
> state UP<br>
>>> qlen<br>
>>> 1000<br>
>>> link/ether 78:2b:cb:27:1f:c9 brd ff:ff:ff:ff:ff:ff<br>
>>> 4: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue<br>
>>> state<br>
>>> UNKNOWN<br>
>>> link/ether f2:3b:f7:1b:b0:46 brd ff:ff:ff:ff:ff:ff<br>
>>> 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue state<br>
>>> UNKNOWN<br>
>>> link/ether 78:2b:cb:27:1f:c8 brd ff:ff:ff:ff:ff:ff<br>
>>> 32: br-tun: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
> noqueue<br>
>>> state<br>
>>> UNKNOWN<br>
>>> link/ether 7e:6c:65:0f:c9:43 brd ff:ff:ff:ff:ff:ff<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>> root@openstack-2:~# ip netns exec<br>
>>> qrouter-32f35fb4-f9f1-4817-8818-fff832f73810 ip address<br>
>>> 25: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state<br>
> UNKNOWN<br>
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
>>> inet <a href="http://127.0.0.1/8" target="_blank">127.0.0.1/8</a> scope host lo<br>
>>> inet6 ::1/128 scope host<br>
>>> valid_lft forever preferred_lft forever<br>
>>> 39: qr-eebfe1cb-0f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500<br>
> qdisc<br>
>>> noqueue state UNKNOWN<br>
>>> link/ether fa:16:3e:08:16:19 brd ff:ff:ff:ff:ff:ff<br>
>>> inet <a href="http://50.50.1.1/24" target="_blank">50.50.1.1/24</a> brd 50.50.1.255 scope global qr-eebfe1cb-0f<br>
>>> inet6 fe80::f816:3eff:fe08:1619/64 scope link<br>
>>> valid_lft forever preferred_lft forever<br>
>>> 40: qg-910fef3b-cb: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500<br>
> qdisc<br>
>>> noqueue state UNKNOWN<br>
>>> link/ether fa:16:3e:e3:d5:fa brd ff:ff:ff:ff:ff:ff<br>
>>> inet <a href="http://10.245.124.65/26" target="_blank">10.245.124.65/26</a> brd 10.245.124.127 scope global<br>
> qg-910fef3b-cb<br>
>>> inet <a href="http://10.245.124.67/32" target="_blank">10.245.124.67/32</a> brd 10.245.124.67 scope global qg-910fef3b-cb<br>
>>> inet6 fe80::f816:3eff:fee3:d5fa/64 scope link<br>
>>> valid_lft forever preferred_lft forever<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>> root@openstack-2:~# quantum net-show<br>
>>> 37d27ee8-36a9-4cdb-9966-9b5571526b41<br>
>>> +---------------------------+--------------------------------------+<br>
>>> | Field | Value |<br>
>>> +---------------------------+--------------------------------------+<br>
>>> | admin_state_up | True |<br>
>>> | id | 37d27ee8-36a9-4cdb-9966-9b5571526b41 |<br>
>>> | name | ext_net |<br>
>>> | provider:network_type | gre |<br>
>>> | provider:physical_network | |<br>
>>> | provider:segmentation_id | 1 |<br>
>>> | router:external | True |<br>
>>> | shared | True |<br>
>>> | status | ACTIVE |<br>
>>> | subnets | dd6f08f5-bfbd-4bdb-b9e4-c5ca065f3750 |<br>
>>> | tenant_id | 2990df1bd46c4dda915b43558d591a2f |<br>
>>> +---------------------------+--------------------------------------+<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> root@openstack-2:~# quantum subnet-show<br>
>>> dd6f08f5-bfbd-4bdb-b9e4-c5ca065f3750<br>
>>><br>
>>> +------------------+-----------------------------------------------------<br>
>>> +<br>
>>> | Field | Value<br>
>>> |<br>
>>><br>
>>> +------------------+-----------------------------------------------------<br>
>>> +<br>
>>> | allocation_pools | {"start": "10.245.124.65",<br>
>>> "end": "10.245.124.126"} |<br>
>>> | cidr | <a href="http://10.245.124.64/26" target="_blank">10.245.124.64/26</a><br>
>>> |<br>
>>> | dns_nameservers | 10.245.0.10<br>
>>> |<br>
>>> | enable_dhcp | False<br>
>>> |<br>
>>> | gateway_ip | 10.245.124.253<br>
>>> |<br>
>>> | host_routes |<br>
>>> |<br>
>>> | id | dd6f08f5-bfbd-4bdb-b9e4-c5ca065f3750<br>
>>> |<br>
>>> | ip_version | 4<br>
>>> |<br>
>>> | name |<br>
>>> |<br>
>>> | network_id | 37d27ee8-36a9-4cdb-9966-9b5571526b41<br>
>>> |<br>
>>> | tenant_id | 2990df1bd46c4dda915b43558d591a2f<br>
>>> |<br>
>>><br>
>>> +------------------+-----------------------------------------------------<br>
>>> +<br>
>>><br>
>>> #########################################################################<br>
>>> ##<br>
>>> #######################<br>
>>><br>
>>><br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> -Farhan.<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> On 5/27/13 4:08 AM, "Darragh OReilly"<br>
>>> <<a href="mailto:darragh.oreilly@yahoo.com">darragh.oreilly@yahoo.com</a>> wrote:<br>
>>><br>
>>>><br>
>>>> I'd check the external network config first.<br>
>>>><br>
>>>> You should be able to ping the external subnet's gateway from<br>
> the<br>
>>>> router<br>
>>>> namespace.<br>
>>>> This gateway should correspond to some real external<br>
> gateway/router.<br>
>>>><br>
>>>> quantum subnet-show <ext sub id> -c gateway_ip #<br>
> 10.245.124.1 ?<br>
>>>> ip netns exec <router-ns> ping -c1 <ext sub gateway><br>
>>>><br>
>>>> If that is not working use tcpdump as you ping. Br-ex is using<br>
> eth0, is<br>
>>>> eth0 up? tcpdump -nei eth0<br>
>>>><br>
>>>><br>
>>>> If you are still having problems, post the above output and the<br>
>>>> following:<br>
>>>><br>
>>>> # network node<br>
>>>> ip link<br>
>>>> ip netns exec <router-ns> ip address<br>
>>>><br>
>>>> quantum net-show <uuid of external net><br>
>>>> quantum subnet-show <uuid of external subnet><br>
>>>><br>
>>>><br>
>>>>> ________________________________<br>
>>>>> From: Farhan Patwa <<a href="mailto:Farhan.Patwa@utsa.edu">Farhan.Patwa@utsa.edu</a>><br>
>>>>> To: OpenStack Maillist <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
>>>>> Sent: Friday, 24 May 2013, 20:28<br>
>>>>> Subject: [Openstack] VM Issues on Grizzly Install on Ubuntu<br>
> 12.04<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> Hello,<br>
>>>>> I followed the following guide to install Grizzly release on<br>
> 3-node<br>
>>>>> setup.<br>
>>>>><br>
>>>>> <a href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-insta" target="_blank">
http://docs.openstack.org/grizzly/basic-install/apt/content/basic-insta</a><br>
>>>>> ll<br>
>>>>> _intro.html<br>
>>>>><br>
>>>>><br>
>>>>> I am stuck at my last issue with Quantum networking (at least<br>
> that©ös<br>
>>>>> what I think).<br>
>>>>> The VM instance comes up and gets the private IP and the<br>
> metadata.<br>
>>>>> Also I have assigned the floating IP to it but am not able to<br>
> ping<br>
>>>>> either IP except when I use:<br>
>>>>><br>
>>>>><br>
>>>>> ip netns exec qrouter-32f35fb4-f9f1-4817-8818-fff832f73810 ping<br>
>>>>> 50.50.1.3 <- fixed IP ˇ© private network<br>
>>>>> ip netns exec qrouter-32f35fb4-f9f1-4817-8818-fff832f73810 ping<br>
>>>>> 10.24.124.4 <- floating IP ˇ© external network<br>
>>>>><br>
>>>>><br>
>>>>> Based on that I think the security rules are okay<br>
>>>>> The router is tied to the specified tenant and using gateway of<br>
> the<br>
>>>>> external network.<br>
>>>>> I think the issue is routing table or maybe firewall related<br>
> but not<br>
>>>>> sure how to debug this.<br>
>>>>><br>
>>>>><br>
>>>>> Some details of my environment are below.<br>
>>>>> Any one have any words of wisdom/guidance?<br>
>>>>><br>
>>>>><br>
>>>>> Thanks,<br>
>>>>><br>
>>>>><br>
>>>>> -Farhan.<br>
>>>>><br>
>>>>><br>
>>>>> Management Network: <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a><br>
>>>>> Data Network: <a href="http://10.5.5.0/24" target="_blank">10.5.5.0/24</a><br>
>>>>> External Network: <a href="http://10.245.124.0/24" target="_blank">10.245.124.0/24</a><br>
>>>>><br>
>>>>><br>
>>>>> Network Node: (192.168.0.2)<br>
>>>>> ovs-vsctl show<br>
>>>>> ea4fa894-5986-40f2-b10b-55eef2222408<br>
>>>>> Bridge br-tun<br>
>>>>> Port patch-int<br>
>>>>> Interface patch-int<br>
>>>>> type: patch<br>
>>>>> options: {peer=patch-tun}<br>
>>>>> Port "gre-1"<br>
>>>>> Interface "gre-1"<br>
>>>>> type: gre<br>
>>>>> options: {in_key=flow, out_key=flow,<br>
>>>>> remote_ip="192.168.0.3"}<br>
>>>>> Port br-tun<br>
>>>>> Interface br-tun<br>
>>>>> type: internal<br>
>>>>> Bridge br-int<br>
>>>>> Port "tap3fca71a9-c8"<br>
>>>>> tag: 4095<br>
>>>>> Interface "tap3fca71a9-c8"<br>
>>>>> type: internal<br>
>>>>> Port patch-tun<br>
>>>>> Interface patch-tun<br>
>>>>> type: patch<br>
>>>>> options: {peer=patch-int}<br>
>>>>> Port "tap4b8a22a2-9c"<br>
>>>>> tag: 4095<br>
>>>>> Interface "tap4b8a22a2-9c"<br>
>>>>> type: internal<br>
>>>>> Port "tap633ed611-a9"<br>
>>>>> tag: 1<br>
>>>>> Interface "tap633ed611-a9"<br>
>>>>> type: internal<br>
>>>>> Port "qr-eebfe1cb-0f"<br>
>>>>> tag: 1<br>
>>>>> Interface "qr-eebfe1cb-0f"<br>
>>>>> type: internal<br>
>>>>> Port br-int<br>
>>>>> Interface br-int<br>
>>>>> type: internal<br>
>>>>> Bridge br-ex<br>
>>>>> Port "eth0"<br>
>>>>> Interface "eth0"<br>
>>>>> Port br-ex<br>
>>>>> Interface br-ex<br>
>>>>> type: internal<br>
>>>>> Port "qg-910fef3b-cb"<br>
>>>>> Interface "qg-910fef3b-cb"<br>
>>>>> type: internal<br>
>>>>> ovs_version: "1.4.0+build0"<br>
>>>>><br>
>>>>><br>
>>>>> Kernel IP routing table<br>
>>>>> Destination Gateway Genmask Flags Metric<br>
> Ref<br>
>>>>> Use<br>
>>>>> Iface<br>
>>>>> 0.0.0.0 192.168.0.253 0.0.0.0 UG 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>> 10.5.5.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>> 10.245.124.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> br-ex<br>
>>>>> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>><br>
>>>>><br>
>>>>> Compute Node: (192.168.0.3)<br>
>>>>> ovs-vsctl show<br>
>>>>> f0fe78a5-dfd0-4f6b-87be-466dac0b4473<br>
>>>>> Bridge br-tun<br>
>>>>> Port patch-int<br>
>>>>> Interface patch-int<br>
>>>>> type: patch<br>
>>>>> options: {peer=patch-tun}<br>
>>>>> Port br-tun<br>
>>>>> Interface br-tun<br>
>>>>> type: internal<br>
>>>>> Port "gre-2"<br>
>>>>> Interface "gre-2"<br>
>>>>> type: gre<br>
>>>>> options: {in_key=flow, out_key=flow,<br>
>>>>> remote_ip="192.168.0.2"}<br>
>>>>> Bridge br-int<br>
>>>>> Port patch-tun<br>
>>>>> Interface patch-tun<br>
>>>>> type: patch<br>
>>>>> options: {peer=patch-int}<br>
>>>>> Port br-int<br>
>>>>> Interface br-int<br>
>>>>> type: internal<br>
>>>>> Port "tap6514a8cc-b2"<br>
>>>>> tag: 1<br>
>>>>> Interface "tap6514a8cc-b2"<br>
>>>>> ovs_version: "1.4.0+build0"<br>
>>>>><br>
>>>>><br>
>>>>> Kernel IP routing table<br>
>>>>> Destination Gateway Genmask Flags Metric<br>
> Ref<br>
>>>>> Use<br>
>>>>> Iface<br>
>>>>> 0.0.0.0 192.168.0.253 0.0.0.0 UG 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>> 10.5.5.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>> 10.245.124.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> eth0<br>
>>>>> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0<br>
>>>>> 0<br>
>>>>> eth1<br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>>>>> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>>>>> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>>>>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">
https://help.launchpad.net/ListHelp</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>>> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>>> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">
https://help.launchpad.net/ListHelp</a><br>
>>><br>
>><br>
><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>