Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-24 Thread Nikhil Mittal
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 wrote: > I also noticed one more thing: everytime i run the command below, it shows > me only dhcp elated entry. I man

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
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

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
Hi, The command "ip netns exec qrouter-fd907599-60a2-4efa-9c7e-65fb8c8b0f77 ip addr" shows: 1: lo: 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 2

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Ashok Kumaran
Thanks Salv for the crystal clear explanation . Sorry my context was based on without namespaces scenario . I did not think from namespaces point of view . Regards Ashok Sent from my iPhone On 23-May-2013, at 7:52 PM, Salvatore Orlando wrote: On 23 May 2013 13:15, Ashok Kumaran wrote: >

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Salvatore Orlando
On 23 May 2013 13:15, Ashok Kumaran 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 overlapp

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Ashok Kumaran
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. Coming back to your question. Does the ifconfig shows internal router interface ip ? have you added the r

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
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 wrote: > Have you checked your config for th

[Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
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'