openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #23932
Re: Router internal interface is DOWN (Grizzly with Quantum)
Any suggestions folks ? I have tried even deleting the tenant, network,
subnet, router and then recreating. Still the same status.
On Fri, May 24, 2013 at 11:13 AM, Nikhil Mittal <mittalnikhil@xxxxxxxxx>wrote:
> I also noticed one more thing: everytime i run the command below, it shows
> me only dhcp elated entry. I manually enter the router entry each time.
> Could this point to the issue I am facing ?
> =========================
> root@osk-team:~# ip netns list
> qdhcp-52df3dd6-76f6-4036-855d-7f81d2b440b9
> =========================
> -Nikhil
>
>
> On Thu, May 23, 2013 at 9:01 PM, Nikhil Mittal <mittalnikhil@xxxxxxxxx>wrote:
>
>> Hi,
>> The command "ip netns exec qrouter-fd907599-60a2-4efa-9c7e-65fb8c8b0f77
>> ip addr" shows:
>> 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>
>> So only one interface is shown which is also DOWN.
>> BTW, I had changed the default security setting to port 22 for TCP and -1
>> for ICMP based on the guide given somewhere in Openstack documentation.
>> -Nikhil
>>
>>
>> On Thu, May 23, 2013 at 7:52 PM, Salvatore Orlando <sorlando@xxxxxxxxxx>wrote:
>>
>>>
>>>
>>> On 23 May 2013 13:15, Ashok Kumaran <ashokkumaran.b@xxxxxxxxx> wrote:
>>>
>>>> Since you have a single node installation , for connecting to the VM's
>>>> from the base host you won't need router/l3 stuffs.if its not happening
>>>> then you might need to check the secgroup rules.
>>>>
>>>
>>> This is true only if you're running without overlapping IPs. Otherwise
>>> the IP addresses for your instances will be stored in a network namespace
>>> called qdhcp-<network_id> and not reachable from the host machine, unless
>>> one eithers executes commands from within the namespace or goes through a
>>> Quantum router (and I believe you'd want to use floating IPs for that)
>>>
>>>
>>>>
>>>> Coming back to your question. Does the ifconfig shows internal router
>>>> interface ip ? have you added the routerid in the l3agent.ini . If not can
>>>> you add and restart the agent and check
>>>>
>>>
>>> Again if you're using namespaces, you'll need to run ifconfig or ip addr
>>> show from within that namespace with 'ip netns <ns-name> exec <command>'.
>>> The default security group already allow traffic between ports belonging
>>> to the same tenant, and this is apparently your case. If you've altered the
>>> default settings however, it might as well be that the security group is
>>> now blocking the traffic.
>>> If the interface does not show up this mean the l3 agent has either
>>> crashed or is tracebacking. The logs, as suggested by Endre, might clarify
>>> what is going on.
>>>
>>> Salvatore
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Ashok
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 23-May-2013, at 5:27 PM, Nikhil Mittal <mittalnikhil@xxxxxxxxx>
>>>> wrote:
>>>>
>>>> The /etc/quantum/l3-agent.ini file seems all correct. I didn't make any
>>>> changes to it except the following line:
>>>> interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
>>>>
>>>> Rest is default.
>>>> -Nikhil
>>>> On Thu, May 23, 2013 at 5:09 PM, Endre Karlson <endre.karlson@xxxxxxxxx
>>>> > wrote:
>>>>
>>>>> Have you checked your config for the agent and eventually
>>>>> /var/log/quantum/l3-agent.log or what the log file is called again ?
>>>>>
>>>>> Endre
>>>>>
>>>>>
>>>>> 2013/5/23 Nikhil Mittal <mittalnikhil@xxxxxxxxx>
>>>>>
>>>>>> Hi,
>>>>>> I am able to successfully spawn VMs on my single-node Grizzly setup
>>>>>> on Ubuntu 13.04. I can ping from one VM to another VM. But i can't ping the
>>>>>> internal router interface which resides on the same subnet as the VMs. I
>>>>>> have not yet configured external network and gateway this router. NOTE: I
>>>>>> can't ping to VMs from the host machine which I believe is because of
>>>>>> router not configured with external interface.
>>>>>> Any suggestions ?
>>>>>> Thanks,
>>>>>> Nikhil
>>>>>>
>>>>>> Below is the output of useful commands:
>>>>>>
>>>>>> ===========================================
>>>>>> root@osk-team:~# quantum port-list
>>>>>>
>>>>>> +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
>>>>>> | id | name | mac_address |
>>>>>> fixed_ips
>>>>>> |
>>>>>>
>>>>>> +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
>>>>>> | 53d63be8-967c-439c-8ffa-53ef1f7f3d37 | | fa:16:3e:09:99:b9 |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.84"} |
>>>>>> | 565eb936-fb89-42a9-9482-0f089907c35a | | fa:16:3e:96:78:92 |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.87"} |
>>>>>> | 6f01314f-6f47-4884-b812-1d66fae9ca3e | | fa:16:3e:b6:c6:fe |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.83"} |
>>>>>> | 7894091c-274a-48dd-8348-b3fd449b6705 | | fa:16:3e:bb:69:9e |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.85"} |
>>>>>> | 9c99fe76-4d74-44de-a2f5-3f3dc555c3d8 | | fa:16:3e:db:f6:6f |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.86"} |
>>>>>> | badec4e8-fa4f-47e3-a7a2-123d84d03337 | | fa:16:3e:79:01:50 |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.82"} |
>>>>>> | cfb7d5ba-3603-4448-9140-8c1d10ca2b2f | | fa:16:3e:a2:db:c4 |
>>>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>>>> "10.78.99.81"} |
>>>>>>
>>>>>> +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
>>>>>>
>>>>>> root@osk-team:~# quantum port-show
>>>>>> cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
>>>>>>
>>>>>> +----------------------+------------------------------------------------------------------------------------+
>>>>>> | Field |
>>>>>> Value
>>>>>> |
>>>>>>
>>>>>> +----------------------+------------------------------------------------------------------------------------+
>>>>>> | admin_state_up |
>>>>>> True
>>>>>> |
>>>>>> | binding:capabilities | {"port_filter":
>>>>>> false} |
>>>>>> | binding:vif_type |
>>>>>> ovs
>>>>>> |
>>>>>> | device_id |
>>>>>> fd907599-60a2-4efa-9c7e-65fb8c8b0f77
>>>>>> |
>>>>>> | device_owner |
>>>>>> network:router_interface
>>>>>> |
>>>>>> | fixed_ips | {"subnet_id":
>>>>>> "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address": "10.78.99.81"} |
>>>>>> | id |
>>>>>> cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
>>>>>> |
>>>>>> | mac_address |
>>>>>> fa:16:3e:a2:db:c4
>>>>>> |
>>>>>> | name
>>>>>> |
>>>>>> |
>>>>>> | network_id |
>>>>>> 52df3dd6-76f6-4036-855d-7f81d2b440b9
>>>>>> |
>>>>>> | status |
>>>>>> DOWN
>>>>>> |
>>>>>> | tenant_id |
>>>>>> e6a025539f2f4823b9ae25d17096efc2
>>>>>> |
>>>>>> ==============================================
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>> More help : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>
References
