no ping/ssh “Destination Host Unreachable” to Instance from neutron-gateway/0












1















I performed a cluster node installation using this guide [OpenStack Charms Deployment Guide].(https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-maas.html), where the type of network is a Flat network and the components used are:




  • Maas

  • Juju

  • Openstack.


My lab is the following:



                         +-------------+
Firewall
10.20.81.254
+-------------+
|
+-------------------------------------------------------------+
Switch
vlan81 vlan81 vlan81
+-------------------------------------------------------------+
| | || || || ||
+--------------+ +------------+ +------------------+
|Maas+Juju |Juju Gui| |Openstack
|10.20.81.1 |10.20.81.2 |10.20.81.21-24
+--------------+ +-------------+ +------------------+
|
+--------------------------------------------+
Private Subnet-1 Public Subnet-2
10.0.0.0/24 10.20.81.0/24
+---+----+--+ +----+------+
| | +----+ |
| | | | |
| +--------+ VR +-------------+
| | |
+--+-+ +----+
| |
| VM |
| .9 |
| |


my lab:



1 IBM System 3540 M4 Maas (500GB HDD - 8GB RAM - 1 Nic)
1 IBM System 3540 M4 Juju (500GB HDD - 8GB RAM -1 Nic)
4 IBM System 3540 M4 Openstack (500GBx2 HDD - 16GB RAM - 2 Nic)
1 Palo Alto Network Firewall


IP plan:



Public Network: 10.20.81.0/24
Private Network: 10.0.0.0/24

Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
Gateway 10.20.81.254
Private Network 10.0.0.0/24
Instance: 10.0.0.9 - 10.20.81.215 (floating)


enter image description here



Openstack Router:
enter image description here



Openstack Security Group:
enter image description here



Maas route:



$: ip route
default via 10.20.81.254 dev enp2s0 proto static
10.20.81.0/24 dev enp2s0 proto kernel scope link src 10.20.81.1


Juju Controller:



ubuntu@juju-controller:~$ ip route
default via 10.20.81.254 dev enp8s0 proto static
10.20.81.0/24 dev enp8s0 proto kernel scope link src 10.20.81.2


Compute Nodes:



ubuntu@os-compute01:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.21
10.38.53.0/24 dev lxdbr0 proto kernel scope link src 10.38.53.1

ubuntu@os-compute02:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.22
10.104.230.0/24 dev lxdbr0 proto kernel scope link src 10.104.230.1

ubuntu@os-compute03:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.23
10.126.34.0/24 dev lxdbr0 proto kernel scope link src 10.126.34.1

ubuntu@os-compute04:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.24
10.72.47.0/24 dev lxdbr0 proto kernel scope link src 10.72.47.1


Router:



$:openstack router show u1804Ro
Password:
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up | UP |
| availability_zone_hints | |
| availability_zones | nova |
| created_at | 2019-02-28T22:27:36Z |
| description | |
| distributed | False |
| external_gateway_info | {"network_id": "e2ba9320-b1cb-4fd8-acd8-b4d9df9df819", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "b3ae37b6-487b-4063-8d69-ec849fd9c9c7", "ip_address": "10.20.81.212"}]} |
| flavor_id | None |
| ha | False |
| id | fc288112-3fce-405d-9c3f-5451253de4f0 |
| interfaces_info | [{"subnet_id": "c7fcfa82-ec70-4917-8f24-7074bf22743b", "ip_address": "10.0.0.1", "port_id": "84693247-3f86-4c84-b0f6-aa8bd95c6c16"}] |
| name | u1804Ro |
| project_id | 1f4809b5083549c1a35c4c023487752c |
| revision_number | 8 |
| routes | |
| status | ACTIVE |
| tags | |
| updated_at | 2019-03-01T14:02:46Z |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


Security Group list



$:openstack security group list
Password:
+--------------------------------------+----------+-----------------------------+----------------------------------+
| ID | Name | Description | Project |
+--------------------------------------+----------+-----------------------------+----------------------------------+
| 57f3fbd9-7574-4116-826f-083a1241bc0f | default | Default security group | 3e59e7cde179423abcdce8fe431fbea0 |
| c242b952-8b07-4d25-b24e-ada213cc116f | u1804Sec | Security Group for u1804Pro | 3e59e7cde179423abcdce8fe431fbea0 |
+--------------------------------------+----------+-----------------------------+----------------------------------+


Security Group rule list



$:openstack security group rule list
Password:
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| ID | IP Protocol | IP Range | Port Range | Remote Security Group | Security Group |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| 07b3bd3f-cc62-409c-bc65-62eea6c7b3ea | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 34216d9f-f5fc-44a3-9e1a-ac52b0cdc334 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 472eff92-c0f8-4a7e-806d-de98fe066d8f | tcp | 0.0.0.0/0 | 22:22 | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| 8f101215-759d-48bc-b665-bd72463ecb3d | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| a6a0e040-3cc8-4cc3-bedf-2aa1adc52018 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| d4346b18-65b3-49a6-9763-05229e468dac | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| dc9f8a32-7315-493a-b8ed-9b5919afc2c8 | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+


anyone can help me to solve that? thanks in advance










share|improve this question

























  • 1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

    – waltinator
    Feb 20 at 16:52
















1















I performed a cluster node installation using this guide [OpenStack Charms Deployment Guide].(https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-maas.html), where the type of network is a Flat network and the components used are:




  • Maas

  • Juju

  • Openstack.


My lab is the following:



                         +-------------+
Firewall
10.20.81.254
+-------------+
|
+-------------------------------------------------------------+
Switch
vlan81 vlan81 vlan81
+-------------------------------------------------------------+
| | || || || ||
+--------------+ +------------+ +------------------+
|Maas+Juju |Juju Gui| |Openstack
|10.20.81.1 |10.20.81.2 |10.20.81.21-24
+--------------+ +-------------+ +------------------+
|
+--------------------------------------------+
Private Subnet-1 Public Subnet-2
10.0.0.0/24 10.20.81.0/24
+---+----+--+ +----+------+
| | +----+ |
| | | | |
| +--------+ VR +-------------+
| | |
+--+-+ +----+
| |
| VM |
| .9 |
| |


my lab:



1 IBM System 3540 M4 Maas (500GB HDD - 8GB RAM - 1 Nic)
1 IBM System 3540 M4 Juju (500GB HDD - 8GB RAM -1 Nic)
4 IBM System 3540 M4 Openstack (500GBx2 HDD - 16GB RAM - 2 Nic)
1 Palo Alto Network Firewall


IP plan:



Public Network: 10.20.81.0/24
Private Network: 10.0.0.0/24

Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
Gateway 10.20.81.254
Private Network 10.0.0.0/24
Instance: 10.0.0.9 - 10.20.81.215 (floating)


enter image description here



Openstack Router:
enter image description here



Openstack Security Group:
enter image description here



Maas route:



$: ip route
default via 10.20.81.254 dev enp2s0 proto static
10.20.81.0/24 dev enp2s0 proto kernel scope link src 10.20.81.1


Juju Controller:



ubuntu@juju-controller:~$ ip route
default via 10.20.81.254 dev enp8s0 proto static
10.20.81.0/24 dev enp8s0 proto kernel scope link src 10.20.81.2


Compute Nodes:



ubuntu@os-compute01:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.21
10.38.53.0/24 dev lxdbr0 proto kernel scope link src 10.38.53.1

ubuntu@os-compute02:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.22
10.104.230.0/24 dev lxdbr0 proto kernel scope link src 10.104.230.1

ubuntu@os-compute03:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.23
10.126.34.0/24 dev lxdbr0 proto kernel scope link src 10.126.34.1

ubuntu@os-compute04:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.24
10.72.47.0/24 dev lxdbr0 proto kernel scope link src 10.72.47.1


Router:



$:openstack router show u1804Ro
Password:
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up | UP |
| availability_zone_hints | |
| availability_zones | nova |
| created_at | 2019-02-28T22:27:36Z |
| description | |
| distributed | False |
| external_gateway_info | {"network_id": "e2ba9320-b1cb-4fd8-acd8-b4d9df9df819", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "b3ae37b6-487b-4063-8d69-ec849fd9c9c7", "ip_address": "10.20.81.212"}]} |
| flavor_id | None |
| ha | False |
| id | fc288112-3fce-405d-9c3f-5451253de4f0 |
| interfaces_info | [{"subnet_id": "c7fcfa82-ec70-4917-8f24-7074bf22743b", "ip_address": "10.0.0.1", "port_id": "84693247-3f86-4c84-b0f6-aa8bd95c6c16"}] |
| name | u1804Ro |
| project_id | 1f4809b5083549c1a35c4c023487752c |
| revision_number | 8 |
| routes | |
| status | ACTIVE |
| tags | |
| updated_at | 2019-03-01T14:02:46Z |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


Security Group list



$:openstack security group list
Password:
+--------------------------------------+----------+-----------------------------+----------------------------------+
| ID | Name | Description | Project |
+--------------------------------------+----------+-----------------------------+----------------------------------+
| 57f3fbd9-7574-4116-826f-083a1241bc0f | default | Default security group | 3e59e7cde179423abcdce8fe431fbea0 |
| c242b952-8b07-4d25-b24e-ada213cc116f | u1804Sec | Security Group for u1804Pro | 3e59e7cde179423abcdce8fe431fbea0 |
+--------------------------------------+----------+-----------------------------+----------------------------------+


Security Group rule list



$:openstack security group rule list
Password:
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| ID | IP Protocol | IP Range | Port Range | Remote Security Group | Security Group |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| 07b3bd3f-cc62-409c-bc65-62eea6c7b3ea | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 34216d9f-f5fc-44a3-9e1a-ac52b0cdc334 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 472eff92-c0f8-4a7e-806d-de98fe066d8f | tcp | 0.0.0.0/0 | 22:22 | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| 8f101215-759d-48bc-b665-bd72463ecb3d | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| a6a0e040-3cc8-4cc3-bedf-2aa1adc52018 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| d4346b18-65b3-49a6-9763-05229e468dac | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| dc9f8a32-7315-493a-b8ed-9b5919afc2c8 | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+


anyone can help me to solve that? thanks in advance










share|improve this question

























  • 1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

    – waltinator
    Feb 20 at 16:52














1












1








1


1






I performed a cluster node installation using this guide [OpenStack Charms Deployment Guide].(https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-maas.html), where the type of network is a Flat network and the components used are:




  • Maas

  • Juju

  • Openstack.


My lab is the following:



                         +-------------+
Firewall
10.20.81.254
+-------------+
|
+-------------------------------------------------------------+
Switch
vlan81 vlan81 vlan81
+-------------------------------------------------------------+
| | || || || ||
+--------------+ +------------+ +------------------+
|Maas+Juju |Juju Gui| |Openstack
|10.20.81.1 |10.20.81.2 |10.20.81.21-24
+--------------+ +-------------+ +------------------+
|
+--------------------------------------------+
Private Subnet-1 Public Subnet-2
10.0.0.0/24 10.20.81.0/24
+---+----+--+ +----+------+
| | +----+ |
| | | | |
| +--------+ VR +-------------+
| | |
+--+-+ +----+
| |
| VM |
| .9 |
| |


my lab:



1 IBM System 3540 M4 Maas (500GB HDD - 8GB RAM - 1 Nic)
1 IBM System 3540 M4 Juju (500GB HDD - 8GB RAM -1 Nic)
4 IBM System 3540 M4 Openstack (500GBx2 HDD - 16GB RAM - 2 Nic)
1 Palo Alto Network Firewall


IP plan:



Public Network: 10.20.81.0/24
Private Network: 10.0.0.0/24

Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
Gateway 10.20.81.254
Private Network 10.0.0.0/24
Instance: 10.0.0.9 - 10.20.81.215 (floating)


enter image description here



Openstack Router:
enter image description here



Openstack Security Group:
enter image description here



Maas route:



$: ip route
default via 10.20.81.254 dev enp2s0 proto static
10.20.81.0/24 dev enp2s0 proto kernel scope link src 10.20.81.1


Juju Controller:



ubuntu@juju-controller:~$ ip route
default via 10.20.81.254 dev enp8s0 proto static
10.20.81.0/24 dev enp8s0 proto kernel scope link src 10.20.81.2


Compute Nodes:



ubuntu@os-compute01:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.21
10.38.53.0/24 dev lxdbr0 proto kernel scope link src 10.38.53.1

ubuntu@os-compute02:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.22
10.104.230.0/24 dev lxdbr0 proto kernel scope link src 10.104.230.1

ubuntu@os-compute03:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.23
10.126.34.0/24 dev lxdbr0 proto kernel scope link src 10.126.34.1

ubuntu@os-compute04:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.24
10.72.47.0/24 dev lxdbr0 proto kernel scope link src 10.72.47.1


Router:



$:openstack router show u1804Ro
Password:
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up | UP |
| availability_zone_hints | |
| availability_zones | nova |
| created_at | 2019-02-28T22:27:36Z |
| description | |
| distributed | False |
| external_gateway_info | {"network_id": "e2ba9320-b1cb-4fd8-acd8-b4d9df9df819", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "b3ae37b6-487b-4063-8d69-ec849fd9c9c7", "ip_address": "10.20.81.212"}]} |
| flavor_id | None |
| ha | False |
| id | fc288112-3fce-405d-9c3f-5451253de4f0 |
| interfaces_info | [{"subnet_id": "c7fcfa82-ec70-4917-8f24-7074bf22743b", "ip_address": "10.0.0.1", "port_id": "84693247-3f86-4c84-b0f6-aa8bd95c6c16"}] |
| name | u1804Ro |
| project_id | 1f4809b5083549c1a35c4c023487752c |
| revision_number | 8 |
| routes | |
| status | ACTIVE |
| tags | |
| updated_at | 2019-03-01T14:02:46Z |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


Security Group list



$:openstack security group list
Password:
+--------------------------------------+----------+-----------------------------+----------------------------------+
| ID | Name | Description | Project |
+--------------------------------------+----------+-----------------------------+----------------------------------+
| 57f3fbd9-7574-4116-826f-083a1241bc0f | default | Default security group | 3e59e7cde179423abcdce8fe431fbea0 |
| c242b952-8b07-4d25-b24e-ada213cc116f | u1804Sec | Security Group for u1804Pro | 3e59e7cde179423abcdce8fe431fbea0 |
+--------------------------------------+----------+-----------------------------+----------------------------------+


Security Group rule list



$:openstack security group rule list
Password:
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| ID | IP Protocol | IP Range | Port Range | Remote Security Group | Security Group |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| 07b3bd3f-cc62-409c-bc65-62eea6c7b3ea | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 34216d9f-f5fc-44a3-9e1a-ac52b0cdc334 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 472eff92-c0f8-4a7e-806d-de98fe066d8f | tcp | 0.0.0.0/0 | 22:22 | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| 8f101215-759d-48bc-b665-bd72463ecb3d | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| a6a0e040-3cc8-4cc3-bedf-2aa1adc52018 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| d4346b18-65b3-49a6-9763-05229e468dac | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| dc9f8a32-7315-493a-b8ed-9b5919afc2c8 | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+


anyone can help me to solve that? thanks in advance










share|improve this question
















I performed a cluster node installation using this guide [OpenStack Charms Deployment Guide].(https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-maas.html), where the type of network is a Flat network and the components used are:




  • Maas

  • Juju

  • Openstack.


My lab is the following:



                         +-------------+
Firewall
10.20.81.254
+-------------+
|
+-------------------------------------------------------------+
Switch
vlan81 vlan81 vlan81
+-------------------------------------------------------------+
| | || || || ||
+--------------+ +------------+ +------------------+
|Maas+Juju |Juju Gui| |Openstack
|10.20.81.1 |10.20.81.2 |10.20.81.21-24
+--------------+ +-------------+ +------------------+
|
+--------------------------------------------+
Private Subnet-1 Public Subnet-2
10.0.0.0/24 10.20.81.0/24
+---+----+--+ +----+------+
| | +----+ |
| | | | |
| +--------+ VR +-------------+
| | |
+--+-+ +----+
| |
| VM |
| .9 |
| |


my lab:



1 IBM System 3540 M4 Maas (500GB HDD - 8GB RAM - 1 Nic)
1 IBM System 3540 M4 Juju (500GB HDD - 8GB RAM -1 Nic)
4 IBM System 3540 M4 Openstack (500GBx2 HDD - 16GB RAM - 2 Nic)
1 Palo Alto Network Firewall


IP plan:



Public Network: 10.20.81.0/24
Private Network: 10.0.0.0/24

Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
Gateway 10.20.81.254
Private Network 10.0.0.0/24
Instance: 10.0.0.9 - 10.20.81.215 (floating)


enter image description here



Openstack Router:
enter image description here



Openstack Security Group:
enter image description here



Maas route:



$: ip route
default via 10.20.81.254 dev enp2s0 proto static
10.20.81.0/24 dev enp2s0 proto kernel scope link src 10.20.81.1


Juju Controller:



ubuntu@juju-controller:~$ ip route
default via 10.20.81.254 dev enp8s0 proto static
10.20.81.0/24 dev enp8s0 proto kernel scope link src 10.20.81.2


Compute Nodes:



ubuntu@os-compute01:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.21
10.38.53.0/24 dev lxdbr0 proto kernel scope link src 10.38.53.1

ubuntu@os-compute02:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.22
10.104.230.0/24 dev lxdbr0 proto kernel scope link src 10.104.230.1

ubuntu@os-compute03:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.23
10.126.34.0/24 dev lxdbr0 proto kernel scope link src 10.126.34.1

ubuntu@os-compute04:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.24
10.72.47.0/24 dev lxdbr0 proto kernel scope link src 10.72.47.1


Router:



$:openstack router show u1804Ro
Password:
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up | UP |
| availability_zone_hints | |
| availability_zones | nova |
| created_at | 2019-02-28T22:27:36Z |
| description | |
| distributed | False |
| external_gateway_info | {"network_id": "e2ba9320-b1cb-4fd8-acd8-b4d9df9df819", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "b3ae37b6-487b-4063-8d69-ec849fd9c9c7", "ip_address": "10.20.81.212"}]} |
| flavor_id | None |
| ha | False |
| id | fc288112-3fce-405d-9c3f-5451253de4f0 |
| interfaces_info | [{"subnet_id": "c7fcfa82-ec70-4917-8f24-7074bf22743b", "ip_address": "10.0.0.1", "port_id": "84693247-3f86-4c84-b0f6-aa8bd95c6c16"}] |
| name | u1804Ro |
| project_id | 1f4809b5083549c1a35c4c023487752c |
| revision_number | 8 |
| routes | |
| status | ACTIVE |
| tags | |
| updated_at | 2019-03-01T14:02:46Z |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


Security Group list



$:openstack security group list
Password:
+--------------------------------------+----------+-----------------------------+----------------------------------+
| ID | Name | Description | Project |
+--------------------------------------+----------+-----------------------------+----------------------------------+
| 57f3fbd9-7574-4116-826f-083a1241bc0f | default | Default security group | 3e59e7cde179423abcdce8fe431fbea0 |
| c242b952-8b07-4d25-b24e-ada213cc116f | u1804Sec | Security Group for u1804Pro | 3e59e7cde179423abcdce8fe431fbea0 |
+--------------------------------------+----------+-----------------------------+----------------------------------+


Security Group rule list



$:openstack security group rule list
Password:
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| ID | IP Protocol | IP Range | Port Range | Remote Security Group | Security Group |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| 07b3bd3f-cc62-409c-bc65-62eea6c7b3ea | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 34216d9f-f5fc-44a3-9e1a-ac52b0cdc334 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 472eff92-c0f8-4a7e-806d-de98fe066d8f | tcp | 0.0.0.0/0 | 22:22 | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| 8f101215-759d-48bc-b665-bd72463ecb3d | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
| a6a0e040-3cc8-4cc3-bedf-2aa1adc52018 | None | None | | None | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| d4346b18-65b3-49a6-9763-05229e468dac | None | None | | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| dc9f8a32-7315-493a-b8ed-9b5919afc2c8 | None | None | | None | c242b952-8b07-4d25-b24e-ada213cc116f |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+


anyone can help me to solve that? thanks in advance







juju maas openstack






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 18 hours ago







Riccardo Magrini

















asked Oct 15 '18 at 15:26









Riccardo MagriniRiccardo Magrini

73031326




73031326













  • 1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

    – waltinator
    Feb 20 at 16:52



















  • 1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

    – waltinator
    Feb 20 at 16:52

















1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

– waltinator
Feb 20 at 16:52





1. Don't post images. 2. "My issue is shown in the first picture"? <sarcasm>Looks fine to me</sarcasm>. What is your question? 3. Whar does ip route show on each system?

– waltinator
Feb 20 at 16:52










1 Answer
1






active

oldest

votes


















0














update 23/03/19:



I can ping the virtual eths from neutron-gateway:



From MAAS



$: juju ssh neutron-gateway/0


then



ubuntu@os-compute01:~$ ip netns list
qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 (id: 4)
qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f (id: 3)


ping result on the eth on router:



ubuntu@os-compute01:~$ ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.212
PING 10.20.81.212 (10.20.81.212) 56(84) bytes of data.
64 bytes from 10.20.81.212: icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from 10.20.81.212: icmp_seq=2 ttl=64 time=0.054 ms

ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.2
PING 10.0.0.1 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.32 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.096 ms


if I try to ping the instance or its floating IP assigned, they're unreachable



ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.9
PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
From 10.0.0.2 icmp_seq=2 Destination Host Unreachable

ubuntu@os-compute01:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.215
PING 10.20.81.215 (10.20.81.215) 56(84) bytes of data.
From 10.20.81.215 icmp_seq=1 Destination Host Unreachable
From 10.20.81.215 icmp_seq=2 Destination Host Unreachable


its route is:



ubuntu@os-compute03:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ip route
default via 10.20.81.254 dev qg-2af6bb57-15
10.0.0.0/24 dev qr-b089085a-11 proto kernel scope link src 10.0.0.1
10.20.81.0/24 dev qg-2af6bb57-15 proto kernel scope link src 10.20.81.212


ping the Gateway from neutron-gateway:



ubuntu@os-compute03:~$ sudo ip netns qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.254
PING 10.20.81.254 (10.20.81.254) 56(84) bytes of data.
From 10.20.81.222 icmp_seq=1 Destination Host Unreachable
From 10.20.81.222 icmp_seq=2 Destination Host Unreachable


update 26/03/19:



running the following command:



ubuntu@os-compute01:~$ sudo ovs-vsctl show
a58746ae-e621-4c22-a2a2-d41d297c56d0
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "tapa20ae295-5c"
tag: 1
Interface "tapa20ae295-5c"
Port "tapa0ce6645-2e"
tag: 2
Interface "tapa0ce6645-2e"
Port br-int
Interface br-int
type: internal
Port "tapc6b3e66d-8a"
tag: 2
Interface "tapc6b3e66d-8a"
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port "gre-0a145106"
Interface "gre-0a145106"
type: gre
options: {df_default="true", in_key=flow, local_ip="10.20.81.3", out_key=flow, remote_ip="10.20.81.6"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-ex
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-ex
Interface br-ex
type: internal
Port "eno2"
Interface "eno2"
error: "could not add network device eno2 to ofproto (Device or resource busy)"
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
ovs_version: "2.10.0"


I've found this error:



error: "could not add network device eno2 to ofproto (Device or resource busy)"


maybe it's that the cause of my problem..Someone knows how i can resolve that? thanks.



update 27/03/19:
On Juju gui I've that:



neutron-gateway:
bridge-mappings: physnet1:br-ex
data-port: br-ex:eno2
neutron-api:
flat-network-providers: physnet1
Before to make the deploy of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

neutron-gateway:
bridge-mappings: physnet1:br-ex
data-port: br-ex:eno3


The issue on eno2 is been resolved but the ping to instance is still present.






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083964%2fno-ping-ssh-destination-host-unreachable-to-instance-from-neutron-gateway-0%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    update 23/03/19:



    I can ping the virtual eths from neutron-gateway:



    From MAAS



    $: juju ssh neutron-gateway/0


    then



    ubuntu@os-compute01:~$ ip netns list
    qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 (id: 4)
    qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f (id: 3)


    ping result on the eth on router:



    ubuntu@os-compute01:~$ ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.212
    PING 10.20.81.212 (10.20.81.212) 56(84) bytes of data.
    64 bytes from 10.20.81.212: icmp_seq=1 ttl=64 time=0.085 ms
    64 bytes from 10.20.81.212: icmp_seq=2 ttl=64 time=0.054 ms

    ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.2
    PING 10.0.0.1 (10.0.0.2) 56(84) bytes of data.
    64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.32 ms
    64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.096 ms


    if I try to ping the instance or its floating IP assigned, they're unreachable



    ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.9
    PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
    From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
    From 10.0.0.2 icmp_seq=2 Destination Host Unreachable

    ubuntu@os-compute01:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.215
    PING 10.20.81.215 (10.20.81.215) 56(84) bytes of data.
    From 10.20.81.215 icmp_seq=1 Destination Host Unreachable
    From 10.20.81.215 icmp_seq=2 Destination Host Unreachable


    its route is:



    ubuntu@os-compute03:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ip route
    default via 10.20.81.254 dev qg-2af6bb57-15
    10.0.0.0/24 dev qr-b089085a-11 proto kernel scope link src 10.0.0.1
    10.20.81.0/24 dev qg-2af6bb57-15 proto kernel scope link src 10.20.81.212


    ping the Gateway from neutron-gateway:



    ubuntu@os-compute03:~$ sudo ip netns qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.254
    PING 10.20.81.254 (10.20.81.254) 56(84) bytes of data.
    From 10.20.81.222 icmp_seq=1 Destination Host Unreachable
    From 10.20.81.222 icmp_seq=2 Destination Host Unreachable


    update 26/03/19:



    running the following command:



    ubuntu@os-compute01:~$ sudo ovs-vsctl show
    a58746ae-e621-4c22-a2a2-d41d297c56d0
    Manager "ptcp:6640:127.0.0.1"
    is_connected: true
    Bridge br-int
    Controller "tcp:127.0.0.1:6633"
    is_connected: true
    fail_mode: secure
    Port patch-tun
    Interface patch-tun
    type: patch
    options: {peer=patch-int}
    Port "tapa20ae295-5c"
    tag: 1
    Interface "tapa20ae295-5c"
    Port "tapa0ce6645-2e"
    tag: 2
    Interface "tapa0ce6645-2e"
    Port br-int
    Interface br-int
    type: internal
    Port "tapc6b3e66d-8a"
    tag: 2
    Interface "tapc6b3e66d-8a"
    Port int-br-ex
    Interface int-br-ex
    type: patch
    options: {peer=phy-br-ex}
    Bridge br-tun
    Controller "tcp:127.0.0.1:6633"
    is_connected: true
    fail_mode: secure
    Port br-tun
    Interface br-tun
    type: internal
    Port "gre-0a145106"
    Interface "gre-0a145106"
    type: gre
    options: {df_default="true", in_key=flow, local_ip="10.20.81.3", out_key=flow, remote_ip="10.20.81.6"}
    Port patch-int
    Interface patch-int
    type: patch
    options: {peer=patch-tun}
    Bridge br-ex
    Controller "tcp:127.0.0.1:6633"
    is_connected: true
    fail_mode: secure
    Port br-ex
    Interface br-ex
    type: internal
    Port "eno2"
    Interface "eno2"
    error: "could not add network device eno2 to ofproto (Device or resource busy)"
    Port phy-br-ex
    Interface phy-br-ex
    type: patch
    options: {peer=int-br-ex}
    ovs_version: "2.10.0"


    I've found this error:



    error: "could not add network device eno2 to ofproto (Device or resource busy)"


    maybe it's that the cause of my problem..Someone knows how i can resolve that? thanks.



    update 27/03/19:
    On Juju gui I've that:



    neutron-gateway:
    bridge-mappings: physnet1:br-ex
    data-port: br-ex:eno2
    neutron-api:
    flat-network-providers: physnet1
    Before to make the deploy of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

    neutron-gateway:
    bridge-mappings: physnet1:br-ex
    data-port: br-ex:eno3


    The issue on eno2 is been resolved but the ping to instance is still present.






    share|improve this answer






























      0














      update 23/03/19:



      I can ping the virtual eths from neutron-gateway:



      From MAAS



      $: juju ssh neutron-gateway/0


      then



      ubuntu@os-compute01:~$ ip netns list
      qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 (id: 4)
      qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f (id: 3)


      ping result on the eth on router:



      ubuntu@os-compute01:~$ ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.212
      PING 10.20.81.212 (10.20.81.212) 56(84) bytes of data.
      64 bytes from 10.20.81.212: icmp_seq=1 ttl=64 time=0.085 ms
      64 bytes from 10.20.81.212: icmp_seq=2 ttl=64 time=0.054 ms

      ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.2
      PING 10.0.0.1 (10.0.0.2) 56(84) bytes of data.
      64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.32 ms
      64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.096 ms


      if I try to ping the instance or its floating IP assigned, they're unreachable



      ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.9
      PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
      From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
      From 10.0.0.2 icmp_seq=2 Destination Host Unreachable

      ubuntu@os-compute01:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.215
      PING 10.20.81.215 (10.20.81.215) 56(84) bytes of data.
      From 10.20.81.215 icmp_seq=1 Destination Host Unreachable
      From 10.20.81.215 icmp_seq=2 Destination Host Unreachable


      its route is:



      ubuntu@os-compute03:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ip route
      default via 10.20.81.254 dev qg-2af6bb57-15
      10.0.0.0/24 dev qr-b089085a-11 proto kernel scope link src 10.0.0.1
      10.20.81.0/24 dev qg-2af6bb57-15 proto kernel scope link src 10.20.81.212


      ping the Gateway from neutron-gateway:



      ubuntu@os-compute03:~$ sudo ip netns qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.254
      PING 10.20.81.254 (10.20.81.254) 56(84) bytes of data.
      From 10.20.81.222 icmp_seq=1 Destination Host Unreachable
      From 10.20.81.222 icmp_seq=2 Destination Host Unreachable


      update 26/03/19:



      running the following command:



      ubuntu@os-compute01:~$ sudo ovs-vsctl show
      a58746ae-e621-4c22-a2a2-d41d297c56d0
      Manager "ptcp:6640:127.0.0.1"
      is_connected: true
      Bridge br-int
      Controller "tcp:127.0.0.1:6633"
      is_connected: true
      fail_mode: secure
      Port patch-tun
      Interface patch-tun
      type: patch
      options: {peer=patch-int}
      Port "tapa20ae295-5c"
      tag: 1
      Interface "tapa20ae295-5c"
      Port "tapa0ce6645-2e"
      tag: 2
      Interface "tapa0ce6645-2e"
      Port br-int
      Interface br-int
      type: internal
      Port "tapc6b3e66d-8a"
      tag: 2
      Interface "tapc6b3e66d-8a"
      Port int-br-ex
      Interface int-br-ex
      type: patch
      options: {peer=phy-br-ex}
      Bridge br-tun
      Controller "tcp:127.0.0.1:6633"
      is_connected: true
      fail_mode: secure
      Port br-tun
      Interface br-tun
      type: internal
      Port "gre-0a145106"
      Interface "gre-0a145106"
      type: gre
      options: {df_default="true", in_key=flow, local_ip="10.20.81.3", out_key=flow, remote_ip="10.20.81.6"}
      Port patch-int
      Interface patch-int
      type: patch
      options: {peer=patch-tun}
      Bridge br-ex
      Controller "tcp:127.0.0.1:6633"
      is_connected: true
      fail_mode: secure
      Port br-ex
      Interface br-ex
      type: internal
      Port "eno2"
      Interface "eno2"
      error: "could not add network device eno2 to ofproto (Device or resource busy)"
      Port phy-br-ex
      Interface phy-br-ex
      type: patch
      options: {peer=int-br-ex}
      ovs_version: "2.10.0"


      I've found this error:



      error: "could not add network device eno2 to ofproto (Device or resource busy)"


      maybe it's that the cause of my problem..Someone knows how i can resolve that? thanks.



      update 27/03/19:
      On Juju gui I've that:



      neutron-gateway:
      bridge-mappings: physnet1:br-ex
      data-port: br-ex:eno2
      neutron-api:
      flat-network-providers: physnet1
      Before to make the deploy of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

      neutron-gateway:
      bridge-mappings: physnet1:br-ex
      data-port: br-ex:eno3


      The issue on eno2 is been resolved but the ping to instance is still present.






      share|improve this answer




























        0












        0








        0







        update 23/03/19:



        I can ping the virtual eths from neutron-gateway:



        From MAAS



        $: juju ssh neutron-gateway/0


        then



        ubuntu@os-compute01:~$ ip netns list
        qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 (id: 4)
        qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f (id: 3)


        ping result on the eth on router:



        ubuntu@os-compute01:~$ ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.212
        PING 10.20.81.212 (10.20.81.212) 56(84) bytes of data.
        64 bytes from 10.20.81.212: icmp_seq=1 ttl=64 time=0.085 ms
        64 bytes from 10.20.81.212: icmp_seq=2 ttl=64 time=0.054 ms

        ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.2
        PING 10.0.0.1 (10.0.0.2) 56(84) bytes of data.
        64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.32 ms
        64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.096 ms


        if I try to ping the instance or its floating IP assigned, they're unreachable



        ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.9
        PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
        From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
        From 10.0.0.2 icmp_seq=2 Destination Host Unreachable

        ubuntu@os-compute01:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.215
        PING 10.20.81.215 (10.20.81.215) 56(84) bytes of data.
        From 10.20.81.215 icmp_seq=1 Destination Host Unreachable
        From 10.20.81.215 icmp_seq=2 Destination Host Unreachable


        its route is:



        ubuntu@os-compute03:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ip route
        default via 10.20.81.254 dev qg-2af6bb57-15
        10.0.0.0/24 dev qr-b089085a-11 proto kernel scope link src 10.0.0.1
        10.20.81.0/24 dev qg-2af6bb57-15 proto kernel scope link src 10.20.81.212


        ping the Gateway from neutron-gateway:



        ubuntu@os-compute03:~$ sudo ip netns qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.254
        PING 10.20.81.254 (10.20.81.254) 56(84) bytes of data.
        From 10.20.81.222 icmp_seq=1 Destination Host Unreachable
        From 10.20.81.222 icmp_seq=2 Destination Host Unreachable


        update 26/03/19:



        running the following command:



        ubuntu@os-compute01:~$ sudo ovs-vsctl show
        a58746ae-e621-4c22-a2a2-d41d297c56d0
        Manager "ptcp:6640:127.0.0.1"
        is_connected: true
        Bridge br-int
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port patch-tun
        Interface patch-tun
        type: patch
        options: {peer=patch-int}
        Port "tapa20ae295-5c"
        tag: 1
        Interface "tapa20ae295-5c"
        Port "tapa0ce6645-2e"
        tag: 2
        Interface "tapa0ce6645-2e"
        Port br-int
        Interface br-int
        type: internal
        Port "tapc6b3e66d-8a"
        tag: 2
        Interface "tapc6b3e66d-8a"
        Port int-br-ex
        Interface int-br-ex
        type: patch
        options: {peer=phy-br-ex}
        Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port br-tun
        Interface br-tun
        type: internal
        Port "gre-0a145106"
        Interface "gre-0a145106"
        type: gre
        options: {df_default="true", in_key=flow, local_ip="10.20.81.3", out_key=flow, remote_ip="10.20.81.6"}
        Port patch-int
        Interface patch-int
        type: patch
        options: {peer=patch-tun}
        Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port br-ex
        Interface br-ex
        type: internal
        Port "eno2"
        Interface "eno2"
        error: "could not add network device eno2 to ofproto (Device or resource busy)"
        Port phy-br-ex
        Interface phy-br-ex
        type: patch
        options: {peer=int-br-ex}
        ovs_version: "2.10.0"


        I've found this error:



        error: "could not add network device eno2 to ofproto (Device or resource busy)"


        maybe it's that the cause of my problem..Someone knows how i can resolve that? thanks.



        update 27/03/19:
        On Juju gui I've that:



        neutron-gateway:
        bridge-mappings: physnet1:br-ex
        data-port: br-ex:eno2
        neutron-api:
        flat-network-providers: physnet1
        Before to make the deploy of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

        neutron-gateway:
        bridge-mappings: physnet1:br-ex
        data-port: br-ex:eno3


        The issue on eno2 is been resolved but the ping to instance is still present.






        share|improve this answer















        update 23/03/19:



        I can ping the virtual eths from neutron-gateway:



        From MAAS



        $: juju ssh neutron-gateway/0


        then



        ubuntu@os-compute01:~$ ip netns list
        qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 (id: 4)
        qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f (id: 3)


        ping result on the eth on router:



        ubuntu@os-compute01:~$ ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.212
        PING 10.20.81.212 (10.20.81.212) 56(84) bytes of data.
        64 bytes from 10.20.81.212: icmp_seq=1 ttl=64 time=0.085 ms
        64 bytes from 10.20.81.212: icmp_seq=2 ttl=64 time=0.054 ms

        ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.2
        PING 10.0.0.1 (10.0.0.2) 56(84) bytes of data.
        64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.32 ms
        64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.096 ms


        if I try to ping the instance or its floating IP assigned, they're unreachable



        ubuntu@os-compute01:~$ sudo ip netns exec qdhcp-feb5596f-b201-4e01-9c04-64abd1273d2f ping 10.0.0.9
        PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
        From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
        From 10.0.0.2 icmp_seq=2 Destination Host Unreachable

        ubuntu@os-compute01:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.215
        PING 10.20.81.215 (10.20.81.215) 56(84) bytes of data.
        From 10.20.81.215 icmp_seq=1 Destination Host Unreachable
        From 10.20.81.215 icmp_seq=2 Destination Host Unreachable


        its route is:



        ubuntu@os-compute03:~$ sudo ip netns exec qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ip route
        default via 10.20.81.254 dev qg-2af6bb57-15
        10.0.0.0/24 dev qr-b089085a-11 proto kernel scope link src 10.0.0.1
        10.20.81.0/24 dev qg-2af6bb57-15 proto kernel scope link src 10.20.81.212


        ping the Gateway from neutron-gateway:



        ubuntu@os-compute03:~$ sudo ip netns qrouter-fc288112-3fce-405d-9c3f-5451253de4f0 ping 10.20.81.254
        PING 10.20.81.254 (10.20.81.254) 56(84) bytes of data.
        From 10.20.81.222 icmp_seq=1 Destination Host Unreachable
        From 10.20.81.222 icmp_seq=2 Destination Host Unreachable


        update 26/03/19:



        running the following command:



        ubuntu@os-compute01:~$ sudo ovs-vsctl show
        a58746ae-e621-4c22-a2a2-d41d297c56d0
        Manager "ptcp:6640:127.0.0.1"
        is_connected: true
        Bridge br-int
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port patch-tun
        Interface patch-tun
        type: patch
        options: {peer=patch-int}
        Port "tapa20ae295-5c"
        tag: 1
        Interface "tapa20ae295-5c"
        Port "tapa0ce6645-2e"
        tag: 2
        Interface "tapa0ce6645-2e"
        Port br-int
        Interface br-int
        type: internal
        Port "tapc6b3e66d-8a"
        tag: 2
        Interface "tapc6b3e66d-8a"
        Port int-br-ex
        Interface int-br-ex
        type: patch
        options: {peer=phy-br-ex}
        Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port br-tun
        Interface br-tun
        type: internal
        Port "gre-0a145106"
        Interface "gre-0a145106"
        type: gre
        options: {df_default="true", in_key=flow, local_ip="10.20.81.3", out_key=flow, remote_ip="10.20.81.6"}
        Port patch-int
        Interface patch-int
        type: patch
        options: {peer=patch-tun}
        Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
        is_connected: true
        fail_mode: secure
        Port br-ex
        Interface br-ex
        type: internal
        Port "eno2"
        Interface "eno2"
        error: "could not add network device eno2 to ofproto (Device or resource busy)"
        Port phy-br-ex
        Interface phy-br-ex
        type: patch
        options: {peer=int-br-ex}
        ovs_version: "2.10.0"


        I've found this error:



        error: "could not add network device eno2 to ofproto (Device or resource busy)"


        maybe it's that the cause of my problem..Someone knows how i can resolve that? thanks.



        update 27/03/19:
        On Juju gui I've that:



        neutron-gateway:
        bridge-mappings: physnet1:br-ex
        data-port: br-ex:eno2
        neutron-api:
        flat-network-providers: physnet1
        Before to make the deploy of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

        neutron-gateway:
        bridge-mappings: physnet1:br-ex
        data-port: br-ex:eno3


        The issue on eno2 is been resolved but the ping to instance is still present.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 17 hours ago

























        answered Mar 1 at 14:37









        Riccardo MagriniRiccardo Magrini

        73031326




        73031326






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083964%2fno-ping-ssh-destination-host-unreachable-to-instance-from-neutron-gateway-0%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

            Eduardo VII do Reino Unido