1

Unable to access instance via ssh

asked 2013-07-25 21:54:21 -0600

djangoat
75 ●11 ●12 ●16

Our static ip is 59.188.xxx.xxx We have Openstack Grizzly running in a single node

based on the network topology our ext_net is cluster_net (external) 50.50.1.0 and it was mark as green.

I have one instance running and it has 50.50.1.4 as floating ip and I can't access it using ( ssh -i ibm_keys.pem ubuntu@50.50.1.4 ) I can't Ping the server as well.

Is there anything wrong with the installation I made?

I have followed this tuts:

https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/master/OpenStack_Grizzly_Install_Guide.rst

I hope someone could explain it, Thanks a lot.

edit retag flag offensive close merge delete

3 answers

Sort by » oldest newest most voted

1

answered 2013-09-10 07:04:45 -0600

madhank
71 ●3 ●4

updated 2013-09-10 07:23:07 -0600

check in this /etc/nova/nova.conf where you have to add this lines in Metadata

metadata_host = 10.10.100.51(your host ip)

metadata_listen = 0.0.0.0

metadata_listen_port = 8775

add this lines and save it

then do

nova-manage db sync

restart the nova services

cd /etc/init.d/; for i in $( ls nova-* ); do sudo service $i restart; done

After this u can ssh using the .pem key with your floating ip (external ip)

it works

edit flag offensive delete link

0

answered 2013-07-26 00:49:31 -0600

thimble
1

Did you configure the security groups to allow ssh/ping?

edit flag offensive delete link

0

answered 2013-07-26 01:23:45 -0600

Bhavaniprasad
26 ●5 ●6 ●9

I guess the image which they are downloading not working properly. Even i have followed the same document but in single node.

try to use this image:

http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso

clean all the instances which you have before.

After changing image, boot an instance with nic id. once your vm gets into active and got ip address, try follow below commands.

ip netns

this command will give the dhcp namespace. it will be something like this "qdhcp-34bea55d-9467-4943-a175-357d59a15f99"

ip netns exec dhcpnamespace_id ping 50.50.1.3

example

ip netns exec qdhcp-34bea55d-9467-4943-a175-357d59a15f99 ping 50.50.1.3

ip netns exec qdhcp-34bea55d-9467-4943-a175-357d59a15f99 ssh username@50.50.1.3

This should work.

sorry for my poor english.

Regards, BhavaniPrasad.

edit flag offensive delete link

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2013-07-25 21:54:21 -0600

Seen: 3,887 times

Last updated: Sep 10 '13

Related questions