Thanks for the update. I assume you have updated guest vlan range at *vnet* in cloud.physical_network table. Right?
My last email (below) has the steps to update the management IP range. - Suresh On Mon, Mar 18, 2019 at 10:58 PM Fariborz Navidan <mdvlinqu...@gmail.com> wrote: > Hello, > I found the solution. I modified the db by updating tables vlan related > tables > > On Mon, Mar 18, 2019 at 8:56 PM Suresh Kumar Anaparti < > sureshkumar.anapa...@gmail.com> wrote: > > > Hi Fariborz, Can you provide additional details - Any guest VMs, networks > > created & are in use? the underlying Hypervisor? > > > > When guest IPs are not allocated, try adding the new guest IP range at > > Infrastructure -> Zone -> Physical network -> Management -> IP Ranges and > > delete the old range. You can update from database (Ref tables: > > *host_pod_ref*, *op_dc_ip_address_alloc*) as well when IPs are not in use > > [Note: Make sure you take backup of cloud database before that.] > > > > - Suresh > > > > On Wed, Mar 13, 2019 at 9:21 PM Fariborz Navidan <mdvlinqu...@gmail.com> > > wrote: > > > > > Hello again, > > > > > > Is it possible to amend start and end IP addresses of a guest network? > > How? > > > From database? > > > > > >
