Hi Indra, Due to the lack of response I assume not, personally if I had this issue, I would familiarise myself with the database and do some manual edits (after a backup of course!).
Marty On Sat, Aug 31, 2013 at 7:09 PM, Indra Pramana <in...@sg.or.id> wrote: > Dear all, > > Anyone had changed their public IP allocation for the system VMs before and > can share some advice? :) > > Looking forward to your reply, thank you. > > Cheers. > > > > On Fri, Aug 30, 2013 at 12:01 PM, Indra Pramana <in...@sg.or.id> wrote: > > > Dear all, > > > > I am using CloudStack 4.1.1 with KVM hypervisors. I would like to change > > the public IP address range used by the system VMs (i.e. SSVM and CPVM). > > > > I went to CloudStack GUI > Infrastructure > Zones > Select my zone > > > Physical Network > cloudbr0 (the cloud interface used for public IP) > > > Public - Configure > IP Ranges. > > > > I added the new range of public IP addresses (Gateway, Netmask, VLAN, > > Start IP, End IP) and assigned to the "System" account, similar to the > > existing public IP addresses. However, when I tried to delete the > existing > > IP range, I encounter this error message: > > > > "The IP range can't be deleted because it has allocated public IP > > addresses." > > > > I tried to destroy the system VMs and quickly delete the existing IP > > range, but still not able to do so since it seems that the system VMs are > > quickly being re-created after being destroyed, and the system VMs are > > still using the old IP range when re-created. > > > > Note that I am using another different shared network range for the guest > > VMs and the virtual routers > > > > Is there a way how I can make system VMs to use the new IP range I have > > added, so that I can safely delete the old IP range? > > > > Looking forward to your reply, thank you. > > > > Cheers. > > >
