Ask Your Question
2

One router port is always DOWN

asked 2014-03-13 08:30:47 -0600

senyapsudah gravatar image

updated 2014-03-14 09:55:06 -0600

darragh-oreilly gravatar image

hi guys,

So far my instance and most of the things are working now. but i'm a bit confuse. currently i have created two router for diffrent tenant and attached this two router to external network. i'm able to ping to this two routers. however, when i check the status of the port below are the status.

        root@opcontroller:/var/log/keystone# neutron port-list
    +--------------------------------------+---------------+-------------------+--------------------------------------------------------------------------------------+
    | id                                   | name          | mac_address       | fixed_ips                                                                            |
    +--------------------------------------+---------------+-------------------+--------------------------------------------------------------------------------------+
    | 011727c5-2a80-46c4-937e-326482ae9be3 |               | fa:16:3e:87:97:a0 | {"subnet_id": "209dcc05-3c73-49db-8e11-481afde98236", "ip_address": "192.168.100.2"} |
    | 2cc7dbea-cdc7-4a10-9b32-ffeb4f8dcd78 |               | fa:16:3e:4f:fe:cd | {"subnet_id": "8a667232-8307-49e6-8cd0-a8e01f60a9d6", "ip_address": "192.168.101.2"} |
    | 7b98f690-2aeb-4f5e-ab18-f4a39d823a43 |               | fa:16:3e:c7:b8:9b | {"subnet_id": "71b0fe5b-63c7-421a-a194-b23d2cf2fc7c", "ip_address": "192.168.8.200"} |
    | 819e0d68-8b37-4f23-8e1d-5b75654cd5e3 |               | fa:16:3e:5e:ca:24 | {"subnet_id": "8a667232-8307-49e6-8cd0-a8e01f60a9d6", "ip_address": "192.168.101.1"} |
    | 829efda0-9137-4c7f-a0d3-8cd502e0955f |               | fa:16:3e:ea:77:c9 | {"subnet_id": "14954880-e5c4-45ad-830c-e0cd7e63b25d", "ip_address": "10.0.27.1"}     |
    | 85140daf-cd24-46cc-b549-0e5704c753c6 |               | fa:16:3e:f6:a7:4a | {"subnet_id": "231ab841-3c10-4d65-99a3-d978438da4a0", "ip_address": "10.0.26.1"}     |
    | 93ca9d34-097a-4ecd-a3a3-908079c3bca8 |               | fa:16:3e:33:f1:b0 | {"subnet_id": "3683ad8c-263f-4cc0-bb0e-be82b135a84b", "ip_address": "10.0.25.1"}     |
    | 9ac65292-ed88-4875-8ef3-54493c4df363 |               | fa:16:3e:8e:24:fb | {"subnet_id": "8a667232-8307-49e6-8cd0-a8e01f60a9d6", "ip_address": "192.168.101.3"} |
    | bf32cc09-6858-44b0-8120-228e1cb24d3d |               | fa:16:3e:19:5c:23 | {"subnet_id": "71b0fe5b-63c7-421a-a194-b23d2cf2fc7c", "ip_address": "192.168.8.201"} |
    | cdb8a40a-0798-46f6-a194-1c84b587a5bf |               | fa:16:3e:f0:92:90 | {"subnet_id": "209dcc05-3c73-49db-8e11-481afde98236", "ip_address": "192.168.100.3"} |
    | f94e2f61-6211-47da-9d32-86c6c55ca945 |               | fa:16:3e:a6:f7:d3 | {"subnet_id": "209dcc05-3c73-49db-8e11-481afde98236", "ip_address": "192.168.100.1"} |
    | fe9f40c9-3ddb-4827-b4d4-cd663074156b | Public-Facing | fa:16:3e:f1:b1:8c | {"subnet_id": "71b0fe5b-63c7-421a-a194-b23d2cf2fc7c", "ip_address": "192.168.8.199"} |
    +--------------------------------------+---------------+-------------------+--------------------------------------------------------------------------------------+

when i check on the port status for 192.168.8.199/201. i can see two diffrent status shown.

root@opcontroller:/var/log/keystone# neutron port-show fe9f40c9-3ddb-4827-b4d4-cd663074156b
+-----------------------+--------------------------------------------------------------------------------------+
| Field                 | Value                                                                                |
+-----------------------+--------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                                 |
| allowed_address_pairs |                                                                                      |
| binding:capabilities  | {"port_filter": true}                                                                |
| binding:host_id       | opcompute01                                                                          |
| binding:vif_type      | ovs                                                                                  |
| device_id             | c03199ea-622d-4e25-8ca1-9d251bfa8a39                                                 |
| device_owner          | network:router_gateway                                                               |
| extra_dhcp_opts       |                                                                                      |
| fixed_ips             | {"subnet_id": "71b0fe5b-63c7-421a-a194-b23d2cf2fc7c", "ip_address": "192.168.8.199"} |
| id                    | fe9f40c9-3ddb-4827-b4d4-cd663074156b                                                 |
| mac_address           | fa:16:3e:f1:b1:8c                                                                    |
| name                  | Public-Facing                                                                        |
| network_id            | df813c6a-9c86-4e6b-a7df-61f70f7c285d                                                 |
| security_groups       |                                                                                      |
| status                | ACTIVE                                                                               |
| tenant_id             |                                                                                      |
+-----------------------+--------------------------------------------------------------------------------------+
root@opcontroller:/var/log/keystone# neutron port-show bf32cc09-6858-44b0-8120-228e1cb24d3d
+-----------------------+--------------------------------------------------------------------------------------+
| Field                 | Value                                                                                |
+-----------------------+--------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                                 |
| allowed_address_pairs |                                                                                      |
| binding:capabilities  | {"port_filter": true}                                                                |
| binding:host_id       | opcompute01                                                                          |
| binding:vif_type      | ovs                                                                                  |
| device_id             | c5c4c4d4-df1f-426d-930d-ab3fa38c33d6                                                 |
| device_owner          | network:router_gateway                                                               |
| extra_dhcp_opts       |                                                                                      |
| fixed_ips             | {"subnet_id": "71b0fe5b-63c7-421a-a194-b23d2cf2fc7c", "ip_address": "192.168.8.201"} |
| id                    | bf32cc09-6858-44b0-8120-228e1cb24d3d                                                 |
| mac_address           | fa:16:3e:19:5c:23                                                                    |
| name                  |                                                                                      |
| network_id            | df813c6a-9c86-4e6b-a7df-61f70f7c285d                                                 |
| security_groups       |                                                                                      |
| status                | DOWN                                                                                 |
| tenant_id             |                                                                                      |
+-----------------------+--------------------------------------------------------------------------------------+

i have to make sure the port status change to up i just go inside the dashboard>network>select the port connected to the router which shown down. i edit it and change the admin state to down by untick the admin state. then i edit it again and now i enable it and save. now the status of the port change to ACTIVE. but sadly i cannot ping anymore the router ip. what i do, i clear the router gateway and set the router gateway again to the same external network and i'm able to ping it again. but the status show down. So it seems like it only work when the port status shown as DOWN. is this the correct way or something like bug? please advise?

edit retag flag offensive close merge delete

Comments

Are you using the OVS or ML2 plugin on the server side? If you restart the L2 agent, does this port remain down?

darragh-oreilly gravatar imagedarragh-oreilly ( 2014-03-13 12:43:20 -0600 )edit

I'm having a similar issue. Please check your /var/log/neutron/l3-agent.log I'm seeing an error in mine saying it can't do a status report.

ten_ten_steve gravatar imageten_ten_steve ( 2014-03-13 14:32:59 -0600 )edit

i'm using OVS. i have tested restart all neutron service and interface. same thing happened. below are some of the error that i can find inside l3 agent log. 2014-03-11 13:35:36.930 2001 ERROR neutron.agent.l3_agent [-] Failed reporting state! 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent Traceback (most recent call last): 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/l3_agent.py", line 815, in _report_state 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent self.use_call) 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/rpc.py", line 72, in report_state 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent return self.call(context, msg, topic=self.topic) 2014-03-11 13:35:36.930 2001 TRACE neutron.agent.l3_agent File "/usr/lib/python2 ...(more)

senyapsudah gravatar imagesenyapsudah ( 2014-03-14 03:06:47 -0600 )edit

I don't think that message is relevant here. Can you try restarting *only* the L2 agent? You could try debug logging and following messages for these ports. But probably the best thing is to use a provider mapping for the external network.

darragh-oreilly gravatar imagedarragh-oreilly ( 2014-03-14 06:29:07 -0600 )edit

so restart the openvswitch plugin rite? correct me if i'm wrong..

senyapsudah gravatar imagesenyapsudah ( 2014-03-14 07:27:17 -0600 )edit
see more comments

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-03-14 09:43:58 -0600

darragh-oreilly gravatar image

updated 2014-03-14 09:52:48 -0600

I booted an Ubuntu Havana system with OVS 1.10.2 and found one problem in this area here. I have no idea what the purpose of these lines is, but on this system sudo ovs-vsctl br-get-external-id br-ex returns nothing, and so br-ex is excluded from the list of ancillary bridges and so the gateway port always shows as DOWN.

A workaround is to set the bridge-id to br-ex and restart the L2 agent:

sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex
sudo service neutron-plugin-openvswitch-agent restart

But I don't know will this solve the OP's problem where one port is working and the another is not. Anyway provider mappings would be a better long term way for external networks.

edit flag offensive delete link more

Comments

hmm...it seems working when i use your solution. the status change to ACTIVE now and i still can ping it.. so meaning that your suggestion is correct.. the missing brisge id is causing this.. anyway. .thanks man.. helps a lot.. :). i will take note on that..

senyapsudah gravatar imagesenyapsudah ( 2014-03-15 00:14:55 -0600 )edit

dang. This answer didn't work for me. All ports connected to my "public network", routers & floating IPs all show up as DOWN, though I can ping out and in.

ten_ten_steve gravatar imageten_ten_steve ( 2014-03-17 14:54:11 -0600 )edit

note: operational status for floating ips was only added in Icehouse.

darragh-oreilly gravatar imagedarragh-oreilly ( 2014-03-18 03:26:30 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

subscribe to rss feed

Stats

Asked: 2014-03-13 08:30:47 -0600

Seen: 4,952 times

Last updated: Mar 14 '14

Related questions

cannot ping tenant router gateway

Neutron L3-agent still enables ports at quantum-gw although using vyatta

After rebooting OpenStack host, router configuration is lost?

RDO Juno, Neutron, CentOS 7: external router port DOWN

create security group

Failed to bind port

Instance Internet connection problems

can't remove router, spanning tree

Problems with OVS: No Connectivity

Gateway always down [closed]