cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Özhan Rüzgar Karaman <>
Subject Re: Problem Releasing of Previously Allocated IP Address
Date Fri, 13 May 2016 06:43:27 GMT
But in my situation router vm gets different ip address after i destroyed
it. I could not delete that C class network there are some active vm's on
that network.


On Thu, May 12, 2016 at 5:21 PM, Sanjeev Neelarapu <> wrote:

> Router vm gets the same ip address even after destroying and recreating
> it. Since CS does not have a mechanism to notify the router vm after for
> existing guest vms it won't change the IP address. ASAIK the IP will be
> released only after deleting that network.
> Best Regards,
> Sanjeev N
> Chief Product Engineer, Accelerite
> Off: +91 40 6722 9368 | EMail:
> -----Original Message-----
> From: Özhan Rüzgar Karaman []
> Sent: Wednesday, May 11, 2016 8:35 PM
> To:
> Subject: Problem Releasing of Previously Allocated IP Address
> Hi;
> I have setup of advanced networking with security groups enabled.
> Yesterday i destroyed and restarted router-vm and after that i noticed that
> from the CloudStack dashboard on Shared Network IP's there is one more
> extra ip address allocated then its expected.
> I checked mysql db (select * from user_ip_address where
> state="Allocated";) to see which ip addresses are allocated and i noticed
> that there is an ip address like x.x.x.5 is allocated but its not used by
> any vm or systemvm's.
> After that i check management server log and i noticed that this ip is
> high probably router vm's previous ip address. Because on management server
> log i noticed lines like below:
> 2016-05-11 16:54:54,374 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-116:ctx-19aae9a4 job-1302/job-1303 ctx-eb95bef0)
> (logid:7f64e204) Seq 10-1563030545674275235: Sending  { Cmd , MgmtId:
> 345050167520, via: 10(kvma16), Ver: v1, Flags: 100011,
> [{"":{"vmMac":"06:49:d6:00:00:03","vmIpAddress":"x.x.x.4","vmName":"win10CreateTemp444","defaultRouter":"x.x.x.1","defaultDns":"x.x.x.5","duid":"00:00:00:00:00:00:xx:00:00:03","isDefault":true,"executeInSequence":false,"accessDetails":{"":"Advanced","router.guest.ip":"x.x.x.15","router.ip":"","
>":"r-91-VM"},"wait":0}}] }
> So the suspicious ip address is written in "defaultDns":"x.x.x.5" field
> and its not correct. I am not currently using dhcp addresses which
> CloudStack provides but 1 of my ip addresses are gone :)
> So why this could happen is this be a bug?
> I also checked logs that defaultDns entry is sometimes correct routervm
> ip(x.x.x.15) and sometimes old router vm's ip (x.x.x.5).
> Thanks
> Özhan Rüzgar Karaman
> ==========
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent Systems business. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Accelerite, a Persistent Systems business does not accept any
> liability for virus infected mails.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message