Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Neutron br-int LINK-DOWN on compute node

I'm running Icehouse on 3 nodes (Controller, Compute and Network (Neutron)) each on 3 different Ubuntu 14.04 servers and 1 instance running cirros.

On the compute node I get this:

    root@stack-compute:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:000066e04378a240
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:ce:a5:4f:62:57:b8
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(qvo3c316791-b1): addr:f2:0d:64:85:4d:93
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:f2:9b:e6:e2:e5:12
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

However it seems to be fine on the network/neutron node:

root@stack-network:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000967df0b79d4a
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:7a:f4:05:7c:df:72
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(tap79ea3f6c-ec): addr:6e:41:83:38:79:b5
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 3(tap2c8d29c1-50): addr:42:f8:53:3f:71:ba
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:96:7d:f0:b7:9d:4a
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

The main problem it's causing is related to the instance connectivity. I can ping its floating IP from the controller and network nodes however I cannot reach it from the compute node itself:

    root@stack-controller:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.75 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.45 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.17 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.174/3.796/6.756/2.096 ms


root@stack-network:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.08 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.69 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.56 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 2.563/3.780/6.083/1.630 ms


root@stack-compute:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
^C
--- 192.168.1.201 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2017ms

The instance does get a DHCP address fine however it cannot resolve any DNS names and cannot connect to the internet. The instance itself can ping the router address, the network/neutron node, the controller node but it can't ping the compute node.

I also cannot SSH to the instance from anywhere on my internal network despite of having the appropriate rules on nova:

    root@stack-controller:~# nova secgroup-list-rules default
+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range  | Source Group |
+-------------+-----------+---------+-----------+--------------+
| icmp        | -1        | -1      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
| tcp         | 22        | 22      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
+-------------+-----------+---------+-----------+--------------+

Here are the details on the instance:

   root@stack-controller:~# nova list
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| ID                                   | Name    | Status | Task State | Power State | Networks                           |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| 0d06960c-ebff-4e22-baf1-b5d0049f1705 | cirros1 | ACTIVE | -          | Running     | dmz-net=172.21.21.2, 192.168.1.201 |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+

And the simple topology I'm trying to accomplish is here: http://imgur.com/GNWrMoc

Any ideas on how to get my instance to be reachable from my network and to access the internet?

Neutron br-int LINK-DOWN on compute node

I'm running Icehouse on 3 nodes (Controller, Compute and Network (Neutron)) each on 3 different Ubuntu 14.04 servers and 1 instance running cirros.

The instance does get a DHCP address fine however it cannot resolve any DNS names and cannot connect to the internet. The instance itself can ping the router address, the network/neutron node, the controller node but it can't ping the compute node.

On the compute node I get this:

    root@stack-compute:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:000066e04378a240
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:ce:a5:4f:62:57:b8
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(qvo3c316791-b1): addr:f2:0d:64:85:4d:93
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:f2:9b:e6:e2:e5:12
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

However it seems to be fine on the network/neutron node:

root@stack-network:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000967df0b79d4a
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:7a:f4:05:7c:df:72
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(tap79ea3f6c-ec): addr:6e:41:83:38:79:b5
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 3(tap2c8d29c1-50): addr:42:f8:53:3f:71:ba
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:96:7d:f0:b7:9d:4a
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

The main problem it's causing is related to the instance connectivity. I can ping its floating IP from the controller and network nodes however I cannot reach it from the compute node itself:

    root@stack-controller:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.75 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.45 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.17 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.174/3.796/6.756/2.096 ms


root@stack-network:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.08 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.69 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.56 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 2.563/3.780/6.083/1.630 ms


root@stack-compute:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
^C
--- 192.168.1.201 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2017ms

The instance does get a DHCP address fine however it cannot resolve any DNS names and cannot connect to the internet. The instance itself can ping the router address, the network/neutron node, the controller node but it can't ping the compute node.

I also cannot SSH to the instance from anywhere on my internal network despite of having the appropriate rules on nova:

    root@stack-controller:~# nova secgroup-list-rules default
+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range  | Source Group |
+-------------+-----------+---------+-----------+--------------+
| icmp        | -1        | -1      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
| tcp         | 22        | 22      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
+-------------+-----------+---------+-----------+--------------+

Here are the details on the instance:

   root@stack-controller:~# nova list
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| ID                                   | Name    | Status | Task State | Power State | Networks                           |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| 0d06960c-ebff-4e22-baf1-b5d0049f1705 | cirros1 | ACTIVE | -          | Running     | dmz-net=172.21.21.2, 192.168.1.201 |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+

And the simple topology I'm trying to accomplish is here: http://imgur.com/GNWrMoc

Any ideas on how to get my instance to be reachable from my network and to access the internet?

Neutron br-int LINK-DOWN on compute node

I'm running Icehouse on 3 nodes (Controller, Compute and Network (Neutron)) each on 3 different Ubuntu 14.04 servers and 1 instance running cirros.

The instance does get a DHCP address fine however it cannot resolve any DNS names and cannot connect to the internet. The instance itself can ping the router address, the network/neutron node, the controller node but it can't ping the compute node.

On the compute node I get this:

    root@stack-compute:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:000066e04378a240
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:ce:a5:4f:62:57:b8
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(qvo3c316791-b1): addr:f2:0d:64:85:4d:93
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:f2:9b:e6:e2:e5:12
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

However it seems to be fine on the network/neutron node:

root@stack-network:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000967df0b79d4a
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-tun): addr:7a:f4:05:7c:df:72
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 2(tap79ea3f6c-ec): addr:6e:41:83:38:79:b5
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 3(tap2c8d29c1-50): addr:42:f8:53:3f:71:ba
     config:     0
     state:      0
     current:    10GB-FD COPPER
     speed: 10000 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:96:7d:f0:b7:9d:4a
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

On the dashboard I get:

Interfaces

Name                      Fixed IPs           Status           Type          Admin State
(2264a202)         172.21.21.1             ACTIVE       Internal Interface         UP
(7911b5f0)        192.168.1.200            DOWN         External Gateway           UP

The main problem it's causing is related to the instance connectivity. I can ping its floating IP from the controller and network nodes however I cannot reach it from the compute node itself:

    root@stack-controller:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.75 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.45 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.17 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.174/3.796/6.756/2.096 ms


root@stack-network:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=63 time=6.08 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=63 time=2.69 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=63 time=2.56 ms

--- 192.168.1.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 2.563/3.780/6.083/1.630 ms


root@stack-compute:~# ping 192.168.1.201 -c 3
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
^C
--- 192.168.1.201 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2017ms

I also cannot SSH to the instance from anywhere on my internal network despite of having the appropriate rules on nova:

    root@stack-controller:~# nova secgroup-list-rules default
+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range  | Source Group |
+-------------+-----------+---------+-----------+--------------+
| icmp        | -1        | -1      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
| tcp         | 22        | 22      | 0.0.0.0/0 |              |
|             |           |         |           | default      |
+-------------+-----------+---------+-----------+--------------+

Here are the details on the instance:

   root@stack-controller:~# nova list
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| ID                                   | Name    | Status | Task State | Power State | Networks                           |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| 0d06960c-ebff-4e22-baf1-b5d0049f1705 | cirros1 | ACTIVE | -          | Running     | dmz-net=172.21.21.2, 192.168.1.201 |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+

And the simple topology I'm trying to accomplish is here: http://imgur.com/GNWrMoc

Any ideas on how to get my instance to be reachable from my network and to access the internet?