You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by cr...@istream.today on 2018/09/01 12:54:28 UTC

Basic Network - Router IP allocated to VM ( Invalid IPs )

Hello,

 

       I have a issue with my CloudStack setup, looks like the same issue
persist in last version of CloudStack 4.11.1.  ( previous versions, 4.9,
4.5.2 etc.. )

 

       

        Current setup :

*	CloudStack 4.11.1
*	VMware 5.5
*	Basic Network
*	1(one) zone, multiple POD IP ranges (Guest)

 

         I use the Guest IP as Public IPs for my instances, each IP is
automatically assigned to VM by CloudStack, I didn't customized anything.

 

 

       Here is an example :

 

        IP range :

                                                              Gateway
Mask                                             Start IP
End IP

         


POD01

149.xxx.xx.62

255.255.255.240

149.xxx.xx.49

149.xxx.xx.61


 

 

 

 

 

 

 

      Router IP from this class is : 149.xxx.xx.53

 

 

     After I deploy few instances, one of the Instance will have the router
IP   149.xxx.xx.53 !!   in order to skip this I have to turn off this VM and
leave like this, if I destroy this will happen again.      ( invalid
IP/instance, I cannot use )

 

     On this setup I have 5 IPs ranges, this mean 5 Invalid VMs. 

 

     I have multiple CloudStack environments, I experience this issue only
on the setups with Basic Networking.

 

 

    

     Is there a way to fix this issue, problem?  ( block those IP by being
used for VMs, or.  )

 

   

   Thank you !

 

 

Regards, 

Cristian

 

 

   

 


Re: Basic Network - Router IP allocated to VM ( Invalid IPs )

Posted by Cristian Ciobanu <cr...@istream.today>.
Thanks for you reply, like I have told, this is a old  issue, I thought was
related to my previous versions, but after the upgrade I see the same
problem....

I don't see the logic why CloudStack is allocated an IP that is used by
router....

Also this is why I cannot figure out where is the error...

On Sep 1, 2018 16:03, "Ivan Kudryavtsev" <ku...@bw-sw.com> wrote:

Hello, Cristian. Don't see such effect in my 4.11.1 deployment with Basic
Zone, I use KVM environment, but hope the result should be the same.

Have you tried to find the IP records in the DB to find the source of the
problem?

сб, 1 сент. 2018 г., 19:54 <cr...@istream.today>:


> Hello,
>
>
>
>        I have a issue with my CloudStack setup, looks like the same issue
> persist in last version of CloudStack 4.11.1.  ( previous versions, 4.9,
> 4.5.2 etc.. )
>
>
>
>
>
>         Current setup :
>
> *       CloudStack 4.11.1
> *       VMware 5.5
> *       Basic Network
> *       1(one) zone, multiple POD IP ranges (Guest)

>
>
>
>          I use the Guest IP as Public IPs for my instances, each IP is
> automatically assigned to VM by CloudStack, I didn't customized anything.
>
>
>
>
>
>        Here is an example :
>
>
>
>         IP range :
>
>                                                               Gateway
> Mask                                             Start IP
> End IP
>
>
>
>
> POD01
>
> 149.xxx.xx.62
>
> 255.255.255.240
>
> 149.xxx.xx.49
>
> 149.xxx.xx.61
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>       Router IP from this class is : 149.xxx.xx.53
>
>
>
>
>
>      After I deploy few instances, one of the Instance will have the
router
> IP   149.xxx.xx.53 !!   in order to skip this I have to turn off this VM
> and
> leave like this, if I destroy this will happen again.      ( invalid
> IP/instance, I cannot use )
>
>
>
>      On this setup I have 5 IPs ranges, this mean 5 Invalid VMs.

>
>
>
>      I have multiple CloudStack environments, I experience this issue only
> on the setups with Basic Networking.
>
>
>
>
>
>
>
>      Is there a way to fix this issue, problem?  ( block those IP by being
> used for VMs, or.  )

>
>
>
>
>
>    Thank you !
>
>
>
>
>
> Regards,
>
> Cristian
>
>
>
>
>
>
>
>
>
>

Re: Basic Network - Router IP allocated to VM ( Invalid IPs )

Posted by Ivan Kudryavtsev <ku...@bw-sw.com>.
Hello, Cristian. Don't see such effect in my 4.11.1 deployment with Basic
Zone, I use KVM environment, but hope the result should be the same.

Have you tried to find the IP records in the DB to find the source of the
problem?

сб, 1 сент. 2018 г., 19:54 <cr...@istream.today>:

> Hello,
>
>
>
>        I have a issue with my CloudStack setup, looks like the same issue
> persist in last version of CloudStack 4.11.1.  ( previous versions, 4.9,
> 4.5.2 etc.. )
>
>
>
>
>
>         Current setup :
>
> *       CloudStack 4.11.1
> *       VMware 5.5
> *       Basic Network
> *       1(one) zone, multiple POD IP ranges (Guest)
>
>
>
>          I use the Guest IP as Public IPs for my instances, each IP is
> automatically assigned to VM by CloudStack, I didn't customized anything.
>
>
>
>
>
>        Here is an example :
>
>
>
>         IP range :
>
>                                                               Gateway
> Mask                                             Start IP
> End IP
>
>
>
>
> POD01
>
> 149.xxx.xx.62
>
> 255.255.255.240
>
> 149.xxx.xx.49
>
> 149.xxx.xx.61
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>       Router IP from this class is : 149.xxx.xx.53
>
>
>
>
>
>      After I deploy few instances, one of the Instance will have the router
> IP   149.xxx.xx.53 !!   in order to skip this I have to turn off this VM
> and
> leave like this, if I destroy this will happen again.      ( invalid
> IP/instance, I cannot use )
>
>
>
>      On this setup I have 5 IPs ranges, this mean 5 Invalid VMs.
>
>
>
>      I have multiple CloudStack environments, I experience this issue only
> on the setups with Basic Networking.
>
>
>
>
>
>
>
>      Is there a way to fix this issue, problem?  ( block those IP by being
> used for VMs, or.  )
>
>
>
>
>
>    Thank you !
>
>
>
>
>
> Regards,
>
> Cristian
>
>
>
>
>
>
>
>
>
>