Maru,
I was trying to ping the 50.50.1.3 address of the VM from the controller as
that was where the doc told me to put the "route add 50.50.1.0/24 gw ….". I can
ping 50.50.1.1, but not .3.
I was getting a "destination not routable" or something like that…
Also, can ping the floatingip, but can not ping from 50.50.1.3 to its gateway
of 50.50.1.1?
Thanks,
Mark Langanki
EVP Operations and Engineering
605 Hwy. 169 N., Suite. 900
Minneapolis, MN 55441
T: 763.971.2185 | M: 612.865.2928
mark.langa...@spanlink.com<mailto:mark.langa...@spanlink.com>|
www.spanlink.com<http://www.spanlink.com/>
Spanlink Communications
We make it work.
On Jan 9, 2013, at 10:05 AM, Maru Newby wrote:
Hi Mark,
Where are you attempting to execute ping against the internal ip from? Based
on that guide, the internal ip would only be routable on the compute or network
nodes, and it should be possible to ping the VM from either.
If you are unable to ping the internal ip from one of those nodes, what error
do you see? If it is something like 'permission denied', then namespaces are
enabled and the ping command will need to be executed via 'sudo ip netns exec
[namespace id] ping [ip]'. The namespace id can be determined by executing 'ip
netns' and finding the namespace id whose prefix matches the router interface
associated with the tenant network (e.g. qrouter-).
Regardless, if you can ping the floating ip, and are able to ssh into the vm
via that floating ip, internal network connectivity is working correctly.
floating ip traffic uses DNAT at the network node, so the internal ip is used
once a packet transits the network node bound for the VM.
Thanks,
Maru
I'm nmot sure Being able to ping a VM's floating ip but not the internal ip is
a promising sign. The internal ip
If you are executing ping from the gateway host, Presuming you are executing
ping from off the gateway
If you can ping the associated floatingip, can you ssh into the vm using that
ip? If so, your vm has connectivity, and the issue is likely that the internal
network is not externaroutable
The internal network is
On 2013-01-09, at 7:19 AM, Mark Langanki
mailto:mark.langa...@spanlink.com>> wrote:
All,
I have an installation of 3 servers based on the Folsom guide :
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst
Following all the way through, I have quantum all configured per the bottom of
the doc : Your first VM.
I have the VM up in a VNC window and can access it.
Network is setup so that I have an internal net of 50.50.1.0/24 (exactly as the
doc), and an external net of 172.17.21.x/24 which is the public side.
I have floating IP's in the 172.17.21.x/24 net and I can ping the associated
floatingip of the VM instance, I can ping the 50.50.1.1 router, but i can not
ping, or access the 50.50.1.3 VM instance.
Where should I be troubleshooting?
How can I know which interface I should be looking at on which node (i.e. is it
a vnet, or qwe031qwr type of interface, and is it on the network or compute
node?)..
Kind of lost on where to go from here.
Thanks,
Mark Langanki
EVP Operations and Engineering
605 Hwy. 169 N., Suite. 900
Minneapolis, MN 55441
T: 763.971.2185 | M: 612.865.2928
mark.langa...@spanlink.com<mailto:mark.langa...@spanlink.com><mailto:mark.langa...@spanlink.com>|
www.spanlink.com<http://www.spanlink.com><http://www.spanlink.com/>
Spanlink Communications
We make it work.
___
Mailing list: https://launchpad.net/~openstack
Post to :
openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
