On Tue, Feb 16, 2016 at 9:22 PM, Ashraf Hassan
<asma2103(a)yahoo.com> wrote:
> Hi Marius,
> Thank you for your help, but I believe now I have seriously wrong stuff but I am
still not able to figure it out :-(
> 1. Check if you can reach the router's public IP
>
> --> I can reach the router public IP only from the network node, but not from any
other node even in the same public subnet.
OK, can you please paste the output of 'ip a', 'ip r' and 'ovs-vsctl
show' on the network node? Just to make sure I get it right - you are
able to ping 10.254.102.130 from the network node?
> 2. Check if you can reach the the default gateway from the router namespace:
> ip netns exec qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ip a
> ip netns exec qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ip r
> ip netns exec qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ping 10.254.102.1
> --> Here is the output of the commands:
http://pastebin.com/SAPpUXUV
>
> 3. Do you want to enable dhcp on the public subnet?
> --> Yes I want so.
>
> Second, check the instance log if it received an IP address via dhcp and it was able
to reach the metadata server. You should be able to see this via nova console-log or in
Horizon.
> --> I do not have console.log, I have only these files:
> nova-api.log nova-cert.log nova-compute.log nova-conductor.log
nova-consoleauth.log nova-manage.log nova-novncproxy.log nova-scheduler.log
Check the nova console-log $instance_name cli command or the Log tab in Horizon
> But I attach you a photo from the Horizon
>
> Since you are using vlan networks you should check that the
/etc/neutron/plugins/ml2/openvswitch_agent.ini contains the correct bridge_mappings -
physnet1 is mapped to the bridge that contains the physical nic where vlans 10,15 are
passed through.
> --> I do not have this file, here the list of files in the plugins directory:
http://pastebin.com/EMTzehnh
Check then /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
> Also check that external_network_bridge is set to an empty value in
/etc/neutron/l3_agent.ini
> --> Here is the content of the file, I do not anything wrong:
http://pastebin.com/nAiEnaTs
Try setting external_network_bridge =
> Here is a guide on how to deploy Neutron with an existing external network, hope it
helps:
>
https://www.rdoproject.org/networking/neutron-with-existing-external-netw...
> --> I believe there is something wrong in the installation, but I can not figure
out what I did wrong that I am missing the file
/etc/neutron/plugins/ml2/openvswitch_agent.ini!!!
>
> -----Original Message-----
> From: Marius Cornea [mailto:marius@remote-lab.net]
> Sent: Tuesday, 16 February 2016 8:18 PM
> To: Ashraf Hassan <asma2103(a)yahoo.com>
> Cc: rdo-list <rdo-list(a)redhat.com>
> Subject: Re: [Rdo-list] My router GWY is down and can not allocate floating IP
>
> Hi,
>
> There are a couple of things that you can check:
>
> First, let's see if the public facing connectivity to the router is working
properly:
>
> 1. Check if you can reach the router's public IP 2. Check if you can reach the
the default gateway from the router namespace:
> ip netns exec qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ip a ip netns exec
qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ip r ip netns exec
qrouter-2d9b71f1-6e54-4a05-a0fb-0680233d6dea ping 10.254.102.1 3. Do you want to enable
dhcp on the public subnet?
>
> Second, check the instance log if it received an IP address via dhcp and it was able
to reach the metadata server. You should be able to see this via nova console-log or in
Horizon.
>
> Since you are using vlan networks you should check that the
/etc/neutron/plugins/ml2/openvswitch_agent.ini contains the correct bridge_mappings -
physnet1 is mapped to the bridge that contains the physical nic where vlans 10,15 are
passed through. Also check that external_network_bridge is set to an empty value in
/etc/neutron/l3_agent.ini
>
> Here is a guide on how to deploy Neutron with an existing external network, hope it
helps:
>
https://www.rdoproject.org/networking/neutron-with-existing-external-netw...
>
> Thanks,
> Marius
>
> On Tue, Feb 16, 2016 at 4:38 PM, Ashraf Hassan <asma2103(a)yahoo.com> wrote:
>> Hi All,
>>
>> I found the problem, it was mistake, I forgot totally the DHCP
>> agent requires an IP, now I am using a bigger pool, I can assign a
>> floating IP, the router public interface is up.
>>
>> Unfortunately I cannot reach the instance, and of course I
>> cannot login from the console to see what is in the instance because I
>> do not have the default cloud-user password.
>>
>> Can someone guide me how to solve it?
>>
>> For neutron and nova checks:
http://pastebin.com/sxndErDC
>>
>> For troubleshooting to reach the instance:
>>
http://pastebin.com/KTtQ2DFw
>>
>> IFCFG for external interface on Controller (network node):
>>
http://pastebin.com/10MRZiM9
>>
>> IFCFG for external bridge on Controller (network node):
>>
http://pastebin.com/RsXb7wXH
>>
>> IFCFG for internal interface on Controller (network node):
>>
http://pastebin.com/jRKRSnc7
>>
>> IFCFG for internal bridge on Controller (network node):
>>
http://pastebin.com/sdNnsi85
>>
>> Output of ovs-vsctl show:
http://pastebin.com/agy1FxDx
>>
>>
>>
>> Can someone guide me how to solve the problem?
>>
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
One more thing. After changing the setting of external_network_bridge,
you need to restart Neutron services, and delete/recreate the networks.
Neutron needs to recreate the proper internal OVS patches between
br-int and the physical bridge.
--
Dan Sneddon | Principal OpenStack Engineer
dsneddon(a)redhat.com |