With IP range reservation, one can reserve a range of IPs in the network that's to be used for dhcp and reserve some for non-CloudStack purposes. But the new CIDR should be subset of the existing CIDR. I think Fabrice is talking about modifying the network CIDR but not within that subnet...?
-----Original Message----- From: S.M Basha [mailto:smbash...@gmail.com] Sent: Thursday, February 14, 2013 8:49 PM To: cloudstack-users@incubator.apache.org Subject: Re: DHCP IP range in the isolated network Fabice, https://cwiki.apache.org/CLOUDSTACK/fs-ip-range-reservation-within-a-network.html Regards Basha On Thu, Feb 14, 2013 at 7:52 PM, Sowmya Krishnan <sowmya.krish...@citrix.com > wrote: > Option of specifying custom dhcp range is available while creating a > new guest network - You can specify custom guest gateway and network > during network creation that would override the default zone level > CIDR. But this is not allowed if you choose a network offering that > uses external devices (like Netscaler for example). The CIDR is > generated by CloudStack in that case. > > For existing network, I think updateNetwork API does provide an option > to change cidr. But if you already have running VMs in the network, I > am not very sure of the behavior in that case. > > -----Original Message----- > From: Fabrice Brazier [mailto:fabrice.braz...@apalia.net] > Sent: Thursday, February 14, 2013 6:41 PM > To: cloudstack-users@incubator.apache.org > Subject: DHCP IP range in the isolated network > > Hi Folks, > > > > By default the guest CIDR for the advanced zone is 10.1.1.0/24 and the > dhcp ip range is on the entire subnet. > > Does it possible to modify the default dhcp ip range in this isolated > network ? > > > > Thanks, > > Fabrice > -- Thanks & Regards S.M.Basha "If opportunity doesn't knock the door; open the door and drag opportunity inside."
