Ask Your Question
0

Openstack Mitaka: Network issue

asked 2016-10-12 17:07:08 -0500

chandu gravatar image

Openstack Mitaka: i deployed Mitaka with the help of Ansible playbooks. My issue is I am able to create network and assign an IP to instance but unable to ping VM from any of my node. I am not able to create network with FLAT or VLAN. I can just create a network with VXLAN. To check VM to VM communication I am unable to launch console.

edit retag flag offensive close merge delete

Comments

Since networking has MANY moving parts, many things can go wrong. Go to docs.openstack.org and read the Operation Guide, network troubleshooting section, and the parts of the Network guide that are relevant to your config. Also: https://assafmuller.com/2015/08/31/ne...

Bernd Bausch gravatar imageBernd Bausch ( 2016-10-13 01:21:29 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-10-14 08:33:15 -0500

Fenuks gravatar image

Unless you have assigned floating IP to instances they will not be accessible from physical nodes. You need to create external (one that your network node is connected to) network with subnet for it, internal (virtual) network with subnet for it and virtual router that would connect them. Then assign external IP to router as gateway and internal ip as port. After that you should be able to ping router IP from outside.
If not, first of all, check MTU on your networks. VXLAN is an overlay network and MTU has to be lower for it, like 1450 instead of 1500. If you're using Openstack-ansible those are default values, but manual will mention they can be changed, and that's what most people do at first.
Second, check your routing. If you've created bridges as described in manual, you have to setup routing for those IP's you'd assign as Floating (or router gateway) on the Controller node.

Good idea is to use tcpdump on various interfaces on Controller/Network node, lxc container with neutron-agents and network namespaces ('ip netns list' to list them, and 'ip netns exec <ns-name> <command>' to exec commands within them, like 'ip netns exec qrouter-666bd243-7b3e-432b-8b6b-85c237b15f14 ip a') to find where your ping stops.

edit flag offensive delete link more

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

1 follower

Stats

Asked: 2016-10-12 17:07:08 -0500

Seen: 138 times

Last updated: Oct 14 '16