Ask Your Question
7

Why is the router interface down and how do I bring it up?

asked 2013-06-05 12:19:23 -0500

mark0978 gravatar image

updated 2013-06-06 09:26:49 -0500

All this is using Grizzly with quantum

I have TenantA-Net (192.168.42.0/24) with a VM (192.168.42.2)

I have Ext-Net (192.168.20.224/27) and connected to that I have a Router R1 with interfaces (192.168.20.227, and 192.168.42.1)

I'm on my laptop (192.168.20.83) trying to access the VM and I can't get there. I back up a few steps and I can't even traceroute to the router

tracert -d 192.168.20.227
Tracing route to 192.168.20.227 over a maximum of 30 hops
  1  192.168.20.83  reports: Destination host unreachable.
Trace complete.

I'm suspecting it is because that interface is "DOWN" as indicated by this:

(quantum) router-port-list --column id --column status --column fixed_ips OutOfBox
+--------------------------------------+--------+------------------------------+
| id          | status | fixed_ips                                             |
+--------------------------------------+--------+------------------------------+
| c8cb677e... | DOWN   | {"subnet_id": "...", "ip_address": "192.168.20.227"}  |
| c98ca86e... | ACTIVE | {"subnet_id": "...", "ip_address": "192.168.42.1"}    |
+--------------------------------------+--------+------------------------------+

But I know of no way to turn it from DOWN to ACTIVE.

edit retag flag offensive close merge delete

Comments

having exactly the same question. The instance cannot ping any address outside of the openstack setup and vice versa.

Vic gravatar imageVic ( 2013-06-12 03:27:17 -0500 )edit

I have a similar issue. However I'm able to ping the router's interface. I'm also able to novnc into the cirros instance and ping out. | 37fac633-6c25-435a-a5df-6460d0d00d13 | DOWN | {"subnet_id": "d10b239a-5fd4-4a5a-b095-900aa2aa800a", "ip_address": "10.245.111.247"} | | 829e3a06-6ab6-4463

james.shimer gravatar imagejames.shimer ( 2013-06-14 14:16:29 -0500 )edit

You need to provide more information. Provide the quantum-l3-agent logs and quantum related configuration files. How many external networks do you have (you can only have 1 per instance). So you have other routers?

fmanco gravatar imagefmanco ( 2013-06-15 09:12:15 -0500 )edit

took the whole network down, will try to reproduce the situation in the weekend. However, I had only one external network as the gateway. I can ping the internal network gateway interface (10.0.0.1), but cannot ping the external network interface (192.168.1.241)

Vic gravatar imageVic ( 2013-06-21 03:00:29 -0500 )edit

I am also facing the same issue (not able to ping VM from within or outside)...can anyone help. I have already created rules to allow icmp/ssh traffic.

sngirame gravatar imagesngirame ( 2013-10-03 06:35:44 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2013-06-13 10:46:51 -0500

Vic gravatar image

updated 2013-06-13 10:59:35 -0500

The status can be influenced by flip the admin status

quantum port-update <port id> --admin_state_up true

However, the connection to outside is still not working.

ping command from instance to dhcp address is working, not the gateway address. I disabled the dhcp function, the address is still working...

edit flag offensive delete link more

Comments

Trying this with neutron and Havana (who has the same issue) this solution does not work.

sferich888 gravatar imagesferich888 ( 2014-01-17 09:05:04 -0500 )edit
1

Same here with liberty. There is a serious lack of troubleshooting documentation

AJ NOURI gravatar imageAJ NOURI ( 2016-05-08 12:37:07 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

3 followers

Stats

Asked: 2013-06-05 12:19:23 -0500

Seen: 8,514 times

Last updated: Jun 13 '13