Ask Your Question
0

Can't able to ping any IP of Openstack setup, not even Router IP

asked 2017-03-06 07:23:02 -0500

Mohan gravatar image

I have setup a 2 node openstack with Controller (10.180.6.231) and Compute (10.180.4.183). I created a public network with subnet (10.180.6.232/29) and a private network (192.168.12.0/24) a router with interfaces (192.168.12.1 and 10.180.6.237 ) both are Up and Active. But the instances created can't be pinged from Controller node.

ifconfig at Controller

root@controller-ESPRIMO-P400:~# ifconfig

br-ex Link encap:Ethernet HWaddr 00:19:99:fc:05:cd
inet addr:10.180.6.231 Bcast:10.180.7.255 Mask:255.255.252.0 inet6 addr: fe80::219:99ff:fefc:5cd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:185488 errors:0 dropped:0 overruns:0 frame:0 TX packets:100368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:59415391 (59.4 MB) TX bytes:37135703 (37.1 MB)

brq2a08be34-4f Link encap:Ethernet HWaddr 82:af:08:f1:44:84
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1562 (1.5 KB) TX bytes:0 (0.0 B)

brq34431651-47 Link encap:Ethernet HWaddr 0e:62:f8:51:05:a3
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:86 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7596 (7.5 KB) TX bytes:0 (0.0 B)

brq5e8f0f7b-06 Link encap:Ethernet HWaddr 8e:4a:f2:4f:91:52
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:4133 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:119304 (119.3 KB) TX bytes:0 (0.0 B)

brqec44cfcd-bf Link encap:Ethernet HWaddr 0e:75:97:0b:bb:4e
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:664 (664.0 B) TX bytes:0 (0.0 B)

enp2s0 Link encap:Ethernet HWaddr 00:19:99:fc:05:cd
inet addr:10.180.6.231 Bcast:10.180.7.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:979133 errors:0 dropped:0 overruns:0 frame:0 TX packets:417906 errors:0 dropped:1 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:451395795 (451.3 MB) TX bytes:177764547 (177.7 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:9892072 errors:0 dropped:0 overruns:0 frame:0 TX ... (more)

edit retag flag offensive close merge delete

Comments

Do you try to ping their floating IP addresses? Static addresses in tenant networks are normally not reachable from outside.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-06 07:56:35 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2017-03-06 08:13:59 -0500

WigiPedia gravatar image

Have you allowed ping in your security group?

openstack security group rule create --protocol icmp default
edit flag offensive delete link more

Comments

https://goo.gl/ka5cq0 (Protocol Link)

Please checkout the image. I allowed any type of protocol in and out for both IPv4 and IPv6.

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-07 00:03:19 -0500 )edit

There must be a route in your physical router pointing to how to access the virtual subnet. The external IP address of your virtual router must be the next hop IP in the route to your virtual network.

WigiPedia gravatar imageWigiPedia ( 2017-03-08 12:40:08 -0500 )edit

@WigiPedia How can we access the routes inside the physical router?

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-08 12:54:33 -0500 )edit

That depends on the router. If it is Mikrotik, the routes are under IP -> Routes, Cisco, I don't remember off hand how to configure this and if you have a consumer-grade router, good luck. What type of router do you have?

WigiPedia gravatar imageWigiPedia ( 2017-03-08 13:25:33 -0500 )edit
0

answered 2017-03-06 12:29:08 -0500

amitabh sinha gravatar image

@Mohan lets tear it down one by one. 1. login into launched instance via console and check whether you are able to find any IP attached to eth0. 2. If yes then try to ping vms of same tenant.See whether in same subnet you are able to communicate or not 3. Then check from router whether you are able to ping the vms or not.

sudo ip netns list to see the qrouter details.

Hope It will help you to good extent. Do let me know whether your problem is solved or not.

edit flag offensive delete link more

Comments

Thank you @Amitabh for the reply.

I have network topology as follows: https://goo.gl/zTV4tg (Nework Topology) The instances in private network are getting IP addresses (192.168.12.x) with eth0 interface inside them. The instances created under public network are not getting any IP addresses.

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-06 23:37:45 -0500 )edit

The instances under private network can ping each other with the allocated private IPs as well as floating IPs. They are also able to ping Router IP (both interfaces- 10.180.6.237 & 192.168.12.1) The instance under public network can't ping itself with the allocated IP. https://goo.gl/bQLb6f (Inst)

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-06 23:54:12 -0500 )edit

I don't know how to ping in router.! The other way I did, to ping from instance under private network to router. It was able to ping.

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-06 23:57:57 -0500 )edit

The VM on the public network isn't allocated an IPv4 address. It has a IPv6 address on eth0

ShubhamMeshram gravatar imageShubhamMeshram ( 2017-03-07 00:09: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

Stats

Asked: 2017-03-06 07:23:02 -0500

Seen: 396 times

Last updated: Mar 06 '17