<div dir="ltr"><div>I don't understand why do you use 2 bridges br-ex and br-ex.30.</div><div><br></div><div>Considering that you have ip 192.168.2.19 configured on ifcfg-eth0.30 you should use br-ex:eth0.30 mapping</div><div><br></div><div>Can you show interfaces configuration?<br></div><div><div>#ifconfig<br></div></div><div><br></div><div>And bridge_mappings on /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini?</div><div><br></div><div>Thanks<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 17, 2015 at 3:07 PM, pauline phaure <span dir="ltr"><<a href="mailto:phaurep@gmail.com" target="_blank">phaurep@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">this is my architecture , i don't know how to connecte br-ex to external and ping the router. any ideas ?<br><br><img alt="Images intégrées 2" src="cid:ii_14cc7b436fce3763" height="325" width="395"><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-17 16:00 GMT+02:00 <span dir="ltr"><<a href="mailto:rdo-list-request@redhat.com" target="_blank">rdo-list-request@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Rdo-list mailing list submissions to<br>
<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rdo-list-request@redhat.com" target="_blank">rdo-list-request@redhat.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rdo-list-owner@redhat.com" target="_blank">rdo-list-owner@redhat.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Rdo-list digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Problem with floating IP (pauline phaure)<br>
2. Re: Help getting started with rdo-manager (Lars Kellogg-Stedman)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 17 Apr 2015 15:55:08 +0200<br>
From: pauline phaure <<a href="mailto:phaurep@gmail.com" target="_blank">phaurep@gmail.com</a>><br>
To: Miguel Angel Ajo Pelayo <<a href="mailto:mangelajo@redhat.com" target="_blank">mangelajo@redhat.com</a>><br>
Cc: <a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a><br>
Subject: Re: [Rdo-list] Problem with floating IP<br>
Message-ID:<br>
<<a href="mailto:CAJM-u-X51u8xgEp9FQj4tmSbvG0GnUc0taj1SUMrx7rjzVXqLQ@mail.gmail.com" target="_blank">CAJM-u-X51u8xgEp9FQj4tmSbvG0GnUc0taj1SUMrx7rjzVXqLQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank you Miguel, my openstack is working fine on ESXi. But when I try to<br>
do the same things with my openstack installation on real servers it<br>
doesn't work. I'm still stuck with br-ex problem and the vlans in which my<br>
interfaces are. br-ex can't reach the outside because eth0 is in a vlan.<br>
any idea<br>
<br>
2015-04-17 14:23 GMT+02:00 Miguel Angel Ajo Pelayo <<a href="mailto:mangelajo@redhat.com" target="_blank">mangelajo@redhat.com</a>>:<br>
<br>
><br>
> The traffic shows that neutron is doing the right thing,<br>
><br>
> Check that your ESX is not applying any MAC anti spoof on the<br>
> vmware vswitch, it looks like the ARP requests could be blocked at switch<br>
> level<br>
> since every qrouter is going to have it?s own MAC address (separate from<br>
> your own<br>
> VM one).<br>
><br>
> Otherwise connect other machine to the physical switch on vlan30 and check<br>
> if<br>
> the ARP requests (it?s broadcast traffic) are arriving to confirm my above<br>
> theory.<br>
><br>
><br>
><br>
> On 17/4/2015, at 13:51, pauline phaure <<a href="mailto:phaurep@gmail.com" target="_blank">phaurep@gmail.com</a>> wrote:<br>
><br>
> i found these lines on the input file of<br>
><br>
> *tcpdump -e -n -v -v -v -i eth0 *192.168.2.72 > <a href="http://10.0.0.4" target="_blank">10.0.0.4</a>: ICMP host<br>
> 192.168.2.1 unreachable, length 92<br>
> 192.168.2.72 > <a href="http://10.0.0.4" target="_blank">10.0.0.4</a>: ICMP host 192.168.2.1 unreachable, length 92<br>
> 192.168.2.72 > <a href="http://10.0.0.4" target="_blank">10.0.0.4</a>: ICMP host 192.168.2.1 unreachable, length 92<br>
> 192.168.2.72 > <a href="http://10.0.0.4" target="_blank">10.0.0.4</a>: ICMP host 192.168.2.1 unreachable, length 92<br>
> 11:41:46.661008 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
> 192.168.2.72, length 28<br>
> 11:41:47.663307 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
> 192.168.2.72, length 28<br>
> 11:41:48.665301 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
> 192.168.2.72, length 28<br>
><br>
><br>
> 2015-04-17 11:52 GMT+02:00 pauline phaure <<a href="mailto:phaurep@gmail.com" target="_blank">phaurep@gmail.com</a>>:<br>
><br>
>> hey Miguel, thank you for your response, plz found below the output of<br>
>> the commands:<br>
>><br>
>><br>
>> *ip netns exec qrouter-f7194985-eb13-41bf-8158-f0e78fc932c4 ip a*<br>
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state 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>
>> valid_lft forever preferred_lft forever<br>
>> inet6 ::1/128 scope host<br>
>> valid_lft forever preferred_lft forever<br>
>> 12: qr-207805ae-39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> noqueue state UNKNOWN<br>
>> link/ether fa:16:3e:1c:62:a8 brd ff:ff:ff:ff:ff:ff<br>
>> inet <a href="http://10.0.0.1/24" target="_blank">10.0.0.1/24</a> brd 10.0.0.255 scope global qr-207805ae-39<br>
>> valid_lft forever preferred_lft forever<br>
>> inet6 fe80::f816:3eff:fe1c:62a8/64 scope link<br>
>> valid_lft forever preferred_lft forever<br>
>> 13: qg-52b4d686-58: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> noqueue state UNKNOWN<br>
>> link/ether fa:16:3e:34:d5:6e brd ff:ff:ff:ff:ff:ff<br>
>> inet <a href="http://192.168.2.70/24" target="_blank">192.168.2.70/24</a> brd 192.168.2.255 scope global qg-52b4d686-58<br>
>> valid_lft forever preferred_lft forever<br>
>> inet *<a href="http://192.168.2.72/32" target="_blank">192.168.2.72/32</a> <<a href="http://192.168.2.72/32" target="_blank">http://192.168.2.72/32</a>>* brd 192.168.2.72<br>
>> scope global *qg-52b4d686-58*<br>
>> valid_lft forever preferred_lft forever<br>
>> inet6 fe80::f816:3eff:fe34:d56e/64 scope link<br>
>> valid_lft forever preferred_lft forever<br>
>><br>
>><br>
>> *ip netns exec qrouter-f7194985-eb13-41bf-8158-f0e78fc932c4 tcpdump -e -n<br>
>> -v -v -v -i qg-52b4d686-58*<br>
>><br>
>> equest who-has 192.168.2.1 tell 192.168.2.72, length 28<br>
>> 11:49:19.705378 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:20.707292 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:22.706910 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:23.707412 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:24.709292 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:26.710264 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:27.711297 fa:16:3e:34:d5:6e > Broadcast, ethertype ARP (0x0806),<br>
>> length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell<br>
>> 192.168.2.72, length 28<br>
>> 11:49:28.002005 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.42<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>> 11:49:28.002064 fa:16:3e:34:d5:6e > 00:23:48:9e:85:7c, ethertype IPv4<br>
>> (0x0800), length 98: (tos 0x0, ttl 63, id 58298, offset 0, flags [DF],<br>
>> proto ICMP (1), length 84)<br>
>> 192.168.2.72 > <a href="http://192.168.2.1" target="_blank">192.168.2.1</a>: ICMP echo request, id 19201, seq 494,<br>
>> length 64<br>
>> 11:49:28.002079 fa:16:3e:34:d5:6e > 00:23:48:9e:85:7c, ethertype IPv4<br>
>> (0x0800), length 98: (tos 0x0, ttl 63, id 58299, offset 0, flags [DF],<br>
>> proto ICMP (1), length 84)<br>
>> 192.168.2.72 > <a href="http://192.168.2.1" target="_blank">192.168.2.1</a>: ICMP echo request, id 19201, seq 495,<br>
>> length 64<br>
>> 11:49:28.040439 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.5<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>> 11:49:28.079105 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.20<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>> 11:49:28.115671 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.34<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>> 11:49:28.179014 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.22<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>> 11:49:28.223391 00:23:48:9e:85:7c > Broadcast, ethertype ARP (0x0806),<br>
>> length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.240<br>
>> (Broadcast) tell 192.168.2.1, length 46<br>
>><br>
>><br>
>> *tcpdump -e -n -v -v -v -i eth0 *<br>
>><br>
>> 11:41:44.953118 00:0c:29:56:d9:09 > 74:46:a0:9e:ff:a5, ethertype IPv4<br>
>> (0x0800), length 166: (tos 0x10, ttl 64, id 10881, offset 0, flags [DF],<br>
>> proto TCP (6), length 152)<br>
>> 192.168.2.19.ssh > 192.168.2.99.53021: Flags [P.], cksum 0x8651<br>
>> (incorrect -> 0x9f53), seq 2550993953:2550994065, ack 2916435463, win 146,<br>
>> length 112<br>
>> 11:41:44.953804 74:46:a0:9e:ff:a5 > 00:0c:29:56:d9:09, ethertype IPv4<br>
>> (0x0800), length 60: (tos 0x0, ttl 128, id 31471, offset 0, flags [DF],<br>
>> proto TCP (6), length 40)<br>
>> 192.168.2.99.53021 > 192.168.2.19.ssh: Flags [.], cksum 0x7b65<br>
>> (correct), seq 1, ack 112, win 16121, length 0<br>
>> 11:41:45.017729 00:0c:29:91:4c:ea > 00:0c:29:56:d9:09, ethertype IPv4<br>
>> (0x0800), length 99: (tos 0x0, ttl 64, id 17044, offset 0, flags [DF],<br>
>> proto TCP (6), length 85)<br>
>> 192.168.2.22.45167 > 192.168.2.19.amqp: Flags [P.], cksum 0x7339<br>
>> (correct), seq 2968653045:2968653078, ack 1461763310, win 123, options<br>
>> [nop,nop,TS val 222978 ecr 218783], length 33<br>
>> 11:41:45.018242 00:0c:29:56:d9:09 > 00:0c:29:91:4c:ea, ethertype IPv4<br>
>> (0x0800), length 78: (tos 0x0, ttl 64, id 47485, offset 0, flags [DF],<br>
>> proto TCP (6), length 64)<br>
>> 192.168.2.19.amqp > 192.168.2.22.45167: Flags [P.], cksum 0x85ac<br>
>> (incorrect -> 0x4c5d), seq 1:13, ack 33, win 330, options [nop,nop,TS val<br>
>> 223746 ecr 222978], length 12<br>
>> 11:41:45.018453 00:0c:29:91:4c:ea > 00:0c:29:56:d9:09, ethertype IPv4<br>
>> (0x0800), length 66: (tos 0x0, ttl 64, id 17045, offset 0, flags [DF],<br>
>> proto TCP (6), length 52)<br>
>> 192.168.2.22.45167 > 192.168.2.19.amqp: Flags [.], cksum 0x8701<br>
>> (correct), seq 33, ack 13, win 123, options [nop,nop,TS val 222979 ecr<br>
>> 223746], length 0<br>
>><br>
>><br>
>><br>
>> 2015-04-17 10:42 GMT+02:00 Miguel Angel Ajo Pelayo <<a href="mailto:mangelajo@redhat.com" target="_blank">mangelajo@redhat.com</a>><br>
>> :<br>
>><br>
>>> To troubleshoot this I?d recommend you<br>
>>><br>
>>> 1) doing a tcpdump in the controller node, on the external interface<br>
>>> attached to br-ex,<br>
>>> and find what?s going on,<br>
>>><br>
>>> tcpdump -e -n -v -v -v -i ethX<br>
>>><br>
>>> note: as per your schema you may use an ?external flat network?<br>
>>> (no segmentation) from your network/controller node, so the packets<br>
>>> going out from the router<br>
>>> should not be tagged in your tcpdump.<br>
>>><br>
>>> If you set the external network as vlan tagged, you may have to change<br>
>>> it into flat. (such operation<br>
>>> may require removing the floating ips from instances, removing legs from<br>
>>> router (External, and internal),<br>
>>> and then removing the router, then the external network/subnet).<br>
>>><br>
>>><br>
>>> In a separate terminal, it may help to ..<br>
>>> 2) look for the router netns:<br>
>>><br>
>>> # ip netns<br>
>>> qrouter-8f2f7e69-02c3-4b75-9b25-e23b64757935<br>
>>><br>
>>> note : this is the ?virtual router?, it lives in a network namespace<br>
>>> which is another isolated<br>
>>> instance of the linux networking stack., you will find the interfaces<br>
>>> and IPs attached with<br>
>>> the following command:<br>
>>><br>
>>> # ip netns exec qrouter-8f2f7e69-02c3-4b75-9b25-e23b64757935 ip a<br>
>>><br>
>>> (here look for the external leg of the router, it will have the external<br>
>>> router IP and the floating ip attached)<br>
>>> it should look like qg-xxxxxxxx-xx<br>
>>><br>
>>><br>
>>> # ip netns exec qrouter-8f2f7e69-02c3-4b75-9b25-e23b64757935 tcpdump -e<br>
>>> -n -v -v -v -i qg-xxxxxxx-xx<br>
>>><br>
>>><br>
>>> Please tell us how is it going .<br>
>>><br>
>>><br>
>>><br>
>>> > On 17/4/2015, at 9:48, pauline phaure <<a href="mailto:phaurep@gmail.com" target="_blank">phaurep@gmail.com</a>> wrote:<br>
>>> ><br>
>>> > Hello everyone,<br>
>>> > I have some troubles making the floating IP work. When I associate a<br>
>>> floating IP to my instance, the instance can reach the neutron-router and<br>
>>> ping but cannot ping the external gateway. any ideas where to look?<br>
>>> ><br>
>>> ><br>
>>> > <image.png><br>
>>> > _______________________________________________<br>
>>> > Rdo-list mailing list<br>
>>> > <a href="mailto:Rdo-list@redhat.com" target="_blank">Rdo-list@redhat.com</a><br>
>>> > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
>>> ><br>
>>> > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">rdo-list-unsubscribe@redhat.com</a><br>
>>><br>
>>> Miguel Angel Ajo<br>
>>><br>
>>><br>
>>><br>
>>><br>
>><br>
><br>
> Miguel Angel Ajo<br>
><br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://www.redhat.com/archives/rdo-list/attachments/20150417/2f2d9cfd/attachment.html" target="_blank">https://www.redhat.com/archives/rdo-list/attachments/20150417/2f2d9cfd/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 17 Apr 2015 10:00:11 -0400<br>
From: Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com" target="_blank">lars@redhat.com</a>><br>
To: Omri Hochman <<a href="mailto:ohochman@redhat.com" target="_blank">ohochman@redhat.com</a>><br>
Cc: <a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a><br>
Subject: Re: [Rdo-list] Help getting started with rdo-manager<br>
Message-ID: <<a href="mailto:20150417140011.GF18285@redhat.com" target="_blank">20150417140011.GF18285@redhat.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
> I think you should have check that in /etc/edeploy/state you have<br>
> --> : [('control', 1), ('compute', '*')]<br>
<br>
Omri,<br>
<br>
Thanks, that did get me one step closer.<br>
<br>
The deploy is still failing, but now it's due to the following<br>
resource:<br>
<br>
| ControllerNodesPostDeployment | 9a24f414-4e35-4d27-b550-77d47651f56a<br>
| OS::TripleO::ControllerPostDeployment | CREATE_FAILED | 2015-04-17T01:28:32Z |<br>
<br>
--<br>
Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com" target="_blank">lars@redhat.com</a>> | larsks @ {freenode,twitter,github}<br>
Cloud Engineering / OpenStack | <a href="http://blog.oddbit.com/" target="_blank">http://blog.oddbit.com/</a><br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: not available<br>
URL: <<a href="https://www.redhat.com/archives/rdo-list/attachments/20150417/6e784186/attachment.bin" target="_blank">https://www.redhat.com/archives/rdo-list/attachments/20150417/6e784186/attachment.bin</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Rdo-list mailing list<br>
<a href="mailto:Rdo-list@redhat.com" target="_blank">Rdo-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
<br>
End of Rdo-list Digest, Vol 25, Issue 28<br>
****************************************<br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
Rdo-list mailing list<br>
<a href="mailto:Rdo-list@redhat.com">Rdo-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br></blockquote></div><br></div>