Well, I can tell you this, it is not required that the hypervisor hosts and 
mgmt. be in the same subnet. If you scale your environment you'll realize that 
won't actually be possible to have such a configuration. So you got to look at 
your networking. I can tell you that your gateway/s may not be correctly 
configured.

Somesh
CloudPlatform Escalations
Citrix Systems, Inc.

-----Original Message-----
From: Tilak Raj Singh [mailto:tila...@gmail.com] 
Sent: Monday, January 19, 2015 3:08 PM
To: users@cloudstack.apache.org
Subject: Re: does hosts and managementserver have to be in same subnet?

Yeah the gateway is working cool...the vm on the first host can access the
network ithout any problems...its the prob on the second vm whose host is
in a different subnet than the gyest ip range that is not able to access
the network...

What more data can i provide for aomeone to help ke through this???

On 12:52am, Tue 20-Jan-2015 Somesh Naidu <somesh.na...@citrix.com> wrote:

> Not really.
>
> Make sure your gateway for the given network is correctly routing the
> traffic. Since you are using Basic network, CS isn't really controlling how
> guest traffic is routed.
>
> Somesh
> CloudPlatform Escalations
> Citrix Systems, Inc.
>
> -----Original Message-----
> From: Tilak Raj Singh [mailto:tila...@gmail.com]
> Sent: Saturday, January 17, 2015 10:51 PM
> To: users@cloudstack.apache.org
> Subject: Re: does hosts and managementserver have to be in same subnet?
>
> One more information I would like to add is that I am using Basic
> Networking in my current cloudstack implementation..Can that be a cause to
> this issue??
>
> On Sun, Jan 18, 2015 at 9:13 AM, Tilak Raj Singh <tila...@gmail.com>
> wrote:
>
> > Hello All,
> >
> > I have a management having ip 172.31.101.202 having a network
> 172.31.100.0
> > and subnet of 255.255.252.0. The default gateway is at 172.31.100.1
> >
> > The private ip range in the zone is 172.31.101.210 - 172.31.101.220 and
> > guests ip range is 172.31.101.230 - 172.31.101.250
> >
> > The management server also acts as a host and has a VM running. Through
> > this VM I can connect to the internet and ping other systems all over the
> > network
> >
> > Now I added a host to this zone having ip 172.31.132.131, network
> > 172.31.132.0, gateway 172.31.132.1 and subnet 255.255.252.0. The host
> added
> > succesfully to the same cluster as the previous host. Now when I create a
> > VM on this host it is given a IP from the guest ip range i.e 172.31.101.0
> > network..But from this VM I cannot access either the internet or any
> other
> > machine.
> >
> > Am I somewhere wrong here? Do I need to create a seperate cluster for the
> > hosts in the other subnet?
> >
> > Regards
> >
>

Reply via email to