Hi, Vadim, 1. route -n root@s-1-VM:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.100 0.0.0.0 UG 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3
Noted that to the same 192.168.0.0 network, eth1 is searched before eth2, while eth2 is supposed to be the public NIC. Should one change the order? 2. root@s-1-VM:~# arp -n cloud (192.168.0.100) at 84:2b:2b:01:c3:d0 [ether] on eth1 cloud (192.168.0.100) at <incomplete> on eth2 ? (169.254.0.1) at fe:00:a9:fe:01:7a [ether] on eth0 Noted that MAC is incomplete on eth2, while MAC detected on eth1 is the correct address of the internal NIC of the Management Server(the gateway for 192.168.0.0 subnet). 3. The network layout is quite simple here( basic network): Management Server external NIC:10.* Management Server internal NIC: 192.168.0.100 KVM host NIC: 192.168.0.101 SSVM and guest VMs are all in 192.168.0.*/24 network. 4. NAT is configured on the Management Server so 192.168.0.0/24 subnet could reach the internet(download packages from internet etc., e.g, from KVM host itself) Cheers, Dan 2014-11-19 1:23 GMT-06:00 Vadim Kimlaychuk <vadim.kimlayc...@elion.ee>: > Dan, > > I would suggest you to use external proxy/GW to hide you network. Not the > same host that contains management server. Because if you would like to > scale it up - how do you do it?? Management server should be rather simple > component of infrastructure and to put more functions on it is a bad idea. > > Anyway > 1. what does "route -n" says on your SSVM ?? > 2. If you use KVM your bridges tag the traffic. Are you sure that it is > properly handled on your switch?? Run "arp -a" at your SSVM and see if VM > "knowns" MAC of the gateway. > > I do expect you put the output of route and arp here otherwise we will > continue guessing. > > It would be even better if you describe your network layout like on the > first picture here: > http://cloudstack-administration.readthedocs.org/en/latest/networking_and_traffic.html > > Vadim. > > -----Original Message----- > From: Dan Dong [mailto:dongda...@gmail.com] > Sent: Tuesday, November 18, 2014 5:23 PM > To: users@cloudstack.apache.org > Subject: Re: To let SSVM reach outside network. > > Hi, Vadim, > We have to use 2 NICs on the management server as we want to hide the > cloudstack cluster behind the 10.* network, so all KVM hosts and guest VMs > are in the 192.168.0.* subnet, and they connect to the management server's > internal NIC(192.168.0.100). Is it a rule that the management server can > only use one NIC? And the KVM hypersior host can reach the internet and > download packages, but SSVM running on it could not see the internet. > > Cheers, > Dan > > > 2014-11-18 3:20 GMT-06:00 Vadim Kimlaychuk <vadim.kimlayc...@elion.ee>: > > > Hello Dan, > > > > It seems there is something wrong with your network setup and > > here are some places to search: > > 1. Why your management server has 2 NICs? It should not work as NAT, > > proxy or any kind of switch - keep this in mind. > > 2. SSVM normally has to have 3 interfaces (at least). One -- with > > public IP, one -- management network IP and one -- link local IP. If > > you have separate storage network -- it may have one more, but this is > > not your case. Check routing table for your SSVM with "route -n" > > command. Find your default gateway. It should be public interface. > > 3. Did you set up KVM hypervisor network correctly? Does it have 2 > > interfaces like in the setup guide? Does your hypervisor have access > > to internet to be able to download template? > > > > Vadim. > > > > -----Original Message----- > > From: Dan Dong [mailto:dongda...@gmail.com] > > Sent: Monday, November 17, 2014 7:02 PM > > To: users@cloudstack.apache.org > > Subject: To let SSVM reach outside network. > > > > Hi, All, > > I found I could not register my ISO image to the cloudstack( through > > URL of > http://releases.ubuntu.com/14.04.1/ubuntu-14.04.1-server-amd64.iso). > > The SSVM is running and health check show no problems on it. But it > > just could not see the outside network, although SSVM is on the same > > network as KVM host, i.e. 192.168.0.*. My setup is as following: > > > > Management Server external NIC:10.* > > Management Server internal NIC: 192.168.0.100 > > > > KVM host NIC: 192.168.0.101 > > guest VMs are all in 192.168.0.*/24 network. > > > > From SSVM I can ping the internal IP of the Management Server at > > 192.168.0.100, but could not ping the external IP of it at 10.*. > > > > From KVM host itself I can reach the outside internet as NAT is > > configured on the Management Server to let the 192.168.0.0 traffic > > through. Any hints how to let SSVM to reach the internet? > > > > > > Cheers, > > Dan > > >
