Unable to ping System VMs
Hi, I'm currently trying cloudstack on my college scientific project and I've been struggling with a few things. First of all, I have two machines with Ubuntu (where the firewall is unable in both of them), one is acting as the hypervisor (with primary local storage and KVM) and the other as the management server (with the secondary storage). These machines are at a lab where they are connected physically with each other and also with the internal network of the lab, that provides them access to internet. My network is like this: - I have the 10.16.22... range to connect the hypervisor and management server to the internet; - I have the 192.168.22... range to connect the hypervisor with the managament server. On my hypervisor I have 4 bridges, cloud0 (created automatically by cloudstack with IP 169.254.0.1), cloudbr1 (with IP 10.16.22.100), cloudbr2 (with IP 192.168.22.70) and virbr0 (created automatically by kvm with IP 192.168.122.1).When I type brctl show it shows the following message: bridge namebridge idSTP enabledinterfaces cloud08000.00e04c681730noeth0 vnet0 vnet3 vnet7 cloudbr18000.1c6f65d74a4bnoeth2 cloudbr28000.5cd998b16f2dnoeth1 vnet1 vnet2 vnet4 vnet5 vnet6 virbr08000.yes As we can see, cloud0 is linked to eth0, cloudbr1 is linked to eth2 and cloudbr2 is linked to eth1. On my Management Server I don't have any bridges, but I have 2 interfaces, eth0 (with IP 192.168.22.71) and eth2 (with IP 10.16.22.101). On both machines eth2 is the interface connecting them to the internet, and they are linked physically through eth1 (on the hypervisor) and eth0 (on the management server). I created a basic zone with the following informations: - IPv4 DNS1: 8.8.8.8, Internal DNS 1: 8.8.4.4, DefaultSharedNetworkOffering; - Pod has the IP range of 192.168.22.100 to 192.168.22.150 and the gateway 192.168.22.1; - The management traffic has the IP range of 192.168.22.2 to 192.168.22.20 and also the gateway 192.168.22.1; - I'm also using the 192.168.22.70 of my hypervisor as the host IP and the 192.168.22.71 as the secondary storage (since the secondary storage is at the management server); I enabled the zone and it created 2 System VMs. The VM Proxy has the following interfaces/IP Adresses: Public IP Address192.168.22.3 Private IP Address192.168.22.116 Link Local IP Address169.254.0.69 And the SSVM: Public IP Address192.168.22.2 Private IP Address192.168.22.135 Link Local IP Address169.254.0.55 I can ping all the interfaces of my hypervisor through the management server (except the cloud0) and vice versa. Both System VMs are as Running, but I'm unable to ping them through my hypervisor and I can't find why. If there is any information missing here that could help to resolve this problem I would gladly give to you. Thanks. -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
Hi, Have you tried pinging the Console Proxy from the SSVM? It is possible to login to these VMs using the following guidance. http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/accessing-system-vms.html Sorry about the old link, couldn't find this in the new documentation. Marty On 17 April 2014 20:23, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, I'm currently trying cloudstack on my college scientific project and I've been struggling with a few things. First of all, I have two machines with Ubuntu (where the firewall is unable in both of them), one is acting as the hypervisor (with primary local storage and KVM) and the other as the management server (with the secondary storage). These machines are at a lab where they are connected physically with each other and also with the internal network of the lab, that provides them access to internet. My network is like this: - I have the 10.16.22... range to connect the hypervisor and management server to the internet; - I have the 192.168.22... range to connect the hypervisor with the managament server. On my hypervisor I have 4 bridges, cloud0 (created automatically by cloudstack with IP 169.254.0.1), cloudbr1 (with IP 10.16.22.100), cloudbr2 (with IP 192.168.22.70) and virbr0 (created automatically by kvm with IP 192.168.122.1).When I type brctl show it shows the following message: bridge namebridge idSTP enabledinterfaces cloud08000.00e04c681730noeth0 vnet0 vnet3 vnet7 cloudbr18000.1c6f65d74a4bnoeth2 cloudbr28000.5cd998b16f2dnoeth1 vnet1 vnet2 vnet4 vnet5 vnet6 virbr08000.yes As we can see, cloud0 is linked to eth0, cloudbr1 is linked to eth2 and cloudbr2 is linked to eth1. On my Management Server I don't have any bridges, but I have 2 interfaces, eth0 (with IP 192.168.22.71) and eth2 (with IP 10.16.22.101). On both machines eth2 is the interface connecting them to the internet, and they are linked physically through eth1 (on the hypervisor) and eth0 (on the management server). I created a basic zone with the following informations: - IPv4 DNS1: 8.8.8.8, Internal DNS 1: 8.8.4.4, DefaultSharedNetworkOffering; - Pod has the IP range of 192.168.22.100 to 192.168.22.150 and the gateway 192.168.22.1; - The management traffic has the IP range of 192.168.22.2 to 192.168.22.20 and also the gateway 192.168.22.1; - I'm also using the 192.168.22.70 of my hypervisor as the host IP and the 192.168.22.71 as the secondary storage (since the secondary storage is at the management server); I enabled the zone and it created 2 System VMs. The VM Proxy has the following interfaces/IP Adresses: Public IP Address192.168.22.3 Private IP Address192.168.22.116 Link Local IP Address169.254.0.69 And the SSVM: Public IP Address192.168.22.2 Private IP Address192.168.22.135 Link Local IP Address169.254.0.55 I can ping all the interfaces of my hypervisor through the management server (except the cloud0) and vice versa. Both System VMs are as Running, but I'm unable to ping them through my hypervisor and I can't find why. If there is any information missing here that could help to resolve this problem I would gladly give to you. Thanks. -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
Hello, As I can't ping to the System VMs I also can't ssh to them. When I try this troubleshooting I receive the message: ssh: connect to host 169.254.0.** port 3922: No route to host 2014-04-17 17:29 GMT-03:00 Marty Sweet msweet@gmail.com: Hi, Have you tried pinging the Console Proxy from the SSVM? It is possible to login to these VMs using the following guidance. http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/accessing-system-vms.html Sorry about the old link, couldn't find this in the new documentation. Marty On 17 April 2014 20:23, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, I'm currently trying cloudstack on my college scientific project and I've been struggling with a few things. First of all, I have two machines with Ubuntu (where the firewall is unable in both of them), one is acting as the hypervisor (with primary local storage and KVM) and the other as the management server (with the secondary storage). These machines are at a lab where they are connected physically with each other and also with the internal network of the lab, that provides them access to internet. My network is like this: - I have the 10.16.22... range to connect the hypervisor and management server to the internet; - I have the 192.168.22... range to connect the hypervisor with the managament server. On my hypervisor I have 4 bridges, cloud0 (created automatically by cloudstack with IP 169.254.0.1), cloudbr1 (with IP 10.16.22.100), cloudbr2 (with IP 192.168.22.70) and virbr0 (created automatically by kvm with IP 192.168.122.1).When I type brctl show it shows the following message: bridge namebridge idSTP enabledinterfaces cloud08000.00e04c681730noeth0 vnet0 vnet3 vnet7 cloudbr18000.1c6f65d74a4bnoeth2 cloudbr28000.5cd998b16f2dnoeth1 vnet1 vnet2 vnet4 vnet5 vnet6 virbr08000.yes As we can see, cloud0 is linked to eth0, cloudbr1 is linked to eth2 and cloudbr2 is linked to eth1. On my Management Server I don't have any bridges, but I have 2 interfaces, eth0 (with IP 192.168.22.71) and eth2 (with IP 10.16.22.101). On both machines eth2 is the interface connecting them to the internet, and they are linked physically through eth1 (on the hypervisor) and eth0 (on the management server). I created a basic zone with the following informations: - IPv4 DNS1: 8.8.8.8, Internal DNS 1: 8.8.4.4, DefaultSharedNetworkOffering; - Pod has the IP range of 192.168.22.100 to 192.168.22.150 and the gateway 192.168.22.1; - The management traffic has the IP range of 192.168.22.2 to 192.168.22.20 and also the gateway 192.168.22.1; - I'm also using the 192.168.22.70 of my hypervisor as the host IP and the 192.168.22.71 as the secondary storage (since the secondary storage is at the management server); I enabled the zone and it created 2 System VMs. The VM Proxy has the following interfaces/IP Adresses: Public IP Address192.168.22.3 Private IP Address192.168.22.116 Link Local IP Address169.254.0.69 And the SSVM: Public IP Address192.168.22.2 Private IP Address192.168.22.135 Link Local IP Address169.254.0.55 I can ping all the interfaces of my hypervisor through the management server (except the cloud0) and vice versa. Both System VMs are as Running, but I'm unable to ping them through my hypervisor and I can't find why. If there is any information missing here that could help to resolve this problem I would gladly give to you. Thanks. -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
On 17.04.2014 22:30, Ana Paula de Sousa wrote: Hello, As I can't ping to the System VMs I also can't ssh to them. When I try this troubleshooting I receive the message: ssh: connect to host 169.254.0.** port 3922: No route to host Can you send the output of iptables-save and ebtables-save? Maybe put it in some pastebin. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: Unable to ping System VMs
Hi, The two are not strictly related, you should be able to connect to the VMs (link) local IP regardless of external connectivity. I have done this multiple times and it's common for troubleshooting these kind of issues. Can I check you are running the SSH command on your hypervisor? In the meantime please can you run 'route -n' on the hypervisor. Thanks, Marty On 17 Apr 2014 22:31, Ana Paula de Sousa apso0...@gmail.com wrote: Hello, As I can't ping to the System VMs I also can't ssh to them. When I try this troubleshooting I receive the message: ssh: connect to host 169.254.0.** port 3922: No route to host 2014-04-17 17:29 GMT-03:00 Marty Sweet msweet@gmail.com: Hi, Have you tried pinging the Console Proxy from the SSVM? It is possible to login to these VMs using the following guidance. http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/accessing-system-vms.html Sorry about the old link, couldn't find this in the new documentation. Marty On 17 April 2014 20:23, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, I'm currently trying cloudstack on my college scientific project and I've been struggling with a few things. First of all, I have two machines with Ubuntu (where the firewall is unable in both of them), one is acting as the hypervisor (with primary local storage and KVM) and the other as the management server (with the secondary storage). These machines are at a lab where they are connected physically with each other and also with the internal network of the lab, that provides them access to internet. My network is like this: - I have the 10.16.22... range to connect the hypervisor and management server to the internet; - I have the 192.168.22... range to connect the hypervisor with the managament server. On my hypervisor I have 4 bridges, cloud0 (created automatically by cloudstack with IP 169.254.0.1), cloudbr1 (with IP 10.16.22.100), cloudbr2 (with IP 192.168.22.70) and virbr0 (created automatically by kvm with IP 192.168.122.1).When I type brctl show it shows the following message: bridge namebridge idSTP enabledinterfaces cloud08000.00e04c681730noeth0 vnet0 vnet3 vnet7 cloudbr18000.1c6f65d74a4bnoeth2 cloudbr28000.5cd998b16f2dnoeth1 vnet1 vnet2 vnet4 vnet5 vnet6 virbr08000.yes As we can see, cloud0 is linked to eth0, cloudbr1 is linked to eth2 and cloudbr2 is linked to eth1. On my Management Server I don't have any bridges, but I have 2 interfaces, eth0 (with IP 192.168.22.71) and eth2 (with IP 10.16.22.101). On both machines eth2 is the interface connecting them to the internet, and they are linked physically through eth1 (on the hypervisor) and eth0 (on the management server). I created a basic zone with the following informations: - IPv4 DNS1: 8.8.8.8, Internal DNS 1: 8.8.4.4, DefaultSharedNetworkOffering; - Pod has the IP range of 192.168.22.100 to 192.168.22.150 and the gateway 192.168.22.1; - The management traffic has the IP range of 192.168.22.2 to 192.168.22.20 and also the gateway 192.168.22.1; - I'm also using the 192.168.22.70 of my hypervisor as the host IP and the 192.168.22.71 as the secondary storage (since the secondary storage is at the management server); I enabled the zone and it created 2 System VMs. The VM Proxy has the following interfaces/IP Adresses: Public IP Address192.168.22.3 Private IP Address192.168.22.116 Link Local IP Address169.254.0.69 And the SSVM: Public IP Address192.168.22.2 Private IP Address192.168.22.135 Link Local IP Address169.254.0.55 I can ping all the interfaces of my hypervisor through the management server (except the cloud0) and vice versa. Both System VMs are as Running, but I'm unable to ping them through my hypervisor and I can't find why. If there is any information missing here that could help to resolve this problem I would gladly give to you. Thanks. -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have.
Re: Unable to ping System VMs
could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.comwrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner
Re: Unable to ping System VMs
Hello, I tried ssh to both VMs through the hypervisor but I just can't. It keeps giving me the message ssh: connect to host 169.254.0.** port 3922: No route to host. I can't access the VMs in any way. 2014-04-17 18:54 GMT-03:00 Rafael Weingartner rafaelweingart...@gmail.com: could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
Hi Rafael, I tried to connect into the console but it asks me a login and password which I don't have. I tried the default password I used in the installation but I didn't succeeded. 2014-04-17 18:59 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hello, I tried ssh to both VMs through the hypervisor but I just can't. It keeps giving me the message ssh: connect to host 169.254.0.** port 3922: No route to host. I can't access the VMs in any way. 2014-04-17 18:54 GMT-03:00 Rafael Weingartner rafaelweingart...@gmail.com : could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
Hi Rafael, The problem is that if I try to access through console any of the system vms I get a message asking me the systemvm login and the password, so I can't actually know if the OS is up or running. All I can know is that they're up. 2014-04-17 19:07 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: The result of route -n is: http://pastebin.com/dUkueCCF 2014-04-17 19:02 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hi Rafael, I tried to connect into the console but it asks me a login and password which I don't have. I tried the default password I used in the installation but I didn't succeeded. 2014-04-17 18:59 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hello, I tried ssh to both VMs through the hypervisor but I just can't. It keeps giving me the message ssh: connect to host 169.254.0.** port 3922: No route to host. I can't access the VMs in any way. 2014-04-17 18:54 GMT-03:00 Rafael Weingartner rafaelweingart...@gmail.com: could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
Re: Unable to ping System VMs
I know that you cannot login, however that is at least a good sign. I had a problem that the OS was taking too long to boot, and that was the problem to lost pings. On Thu, Apr 17, 2014 at 7:12 PM, Ana Paula de Sousa apso0...@gmail.comwrote: Hi Rafael, The problem is that if I try to access through console any of the system vms I get a message asking me the systemvm login and the password, so I can't actually know if the OS is up or running. All I can know is that they're up. 2014-04-17 19:07 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: The result of route -n is: http://pastebin.com/dUkueCCF 2014-04-17 19:02 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hi Rafael, I tried to connect into the console but it asks me a login and password which I don't have. I tried the default password I used in the installation but I didn't succeeded. 2014-04-17 18:59 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hello, I tried ssh to both VMs through the hypervisor but I just can't. It keeps giving me the message ssh: connect to host 169.254.0.** port 3922: No route to host. I can't access the VMs in any way. 2014-04-17 18:54 GMT-03:00 Rafael Weingartner rafaelweingart...@gmail.com: could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Rafael Weingärtner
Re: Unable to ping System VMs
I thought that cs expected the management interface to be cloudbr0. You have it labeled cloudbr2. Other than that the route looks fine. Fyi I setup a kvm last week and tried my hardest to be able to ping the ssvm. It would respond from the real public but not the management. I gave up, setup xenserver and right out of the box the ssvm came up, it started downloading the templates and iso I wanted. I did the network the exact same way so I don't think I did it wrong. I'm sure the kvm works but I was unable to make the networking part of it good. Sent from my Galaxy S®III Original message From: Ana Paula de Sousa apso0...@gmail.com Date:04/17/2014 6:07 PM (GMT-05:00) To: users@cloudstack.apache.org Subject: Re: Unable to ping System VMs The result of route -n is: http://pastebin.com/dUkueCCF 2014-04-17 19:02 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hi Rafael, I tried to connect into the console but it asks me a login and password which I don't have. I tried the default password I used in the installation but I didn't succeeded. 2014-04-17 18:59 GMT-03:00 Ana Paula de Sousa apso0...@gmail.com: Hello, I tried ssh to both VMs through the hypervisor but I just can't. It keeps giving me the message ssh: connect to host 169.254.0.** port 3922: No route to host. I can't access the VMs in any way. 2014-04-17 18:54 GMT-03:00 Rafael Weingartner rafaelweingart...@gmail.com: could you try to connect into the VMs console? and check if the OS booted properly. On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa apso0...@gmail.com wrote: Hi, The output of iptables-save is: http://pastebin.com/fhA8UdSm When I typed ebtables-save I got the message bash: ebtables-save: comando não encontrado, but I verified if I had ebtables installed and I have. -- Rafael Weingärtner -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás -- Ana Paula de Sousa Oliveira Graduando em Ciência da Computação Universidade Federal de Goiás
