Hi Eric,
Thank you. You were right! After we re-configure our switches to allow VLANs
traffic, the problem is gone and everything works like a charm...
All the best and thank you again!
On 2019/10/11 10:02:36, Ioan Marginean wrote:
> Hi Eric,
>
> Thank you so much for the reply and for such
With this thread, updates from the Primate project and its SIG will be shared
on a bi-weekly basis:
25 Oct 2019
SIG updates:
* Primate SIG nucleus formed, interest shared by collaborators from EWerk,
Indiqus, IPPathways and ShapeBlue (if you want to participate and contribute,
kindly drop
not gonna happen, can't have 2 different IPs served by dhcp server for the
same MAC address...
On Fri, 25 Oct 2019, 14:56 Fariborz Navidan, wrote:
> I hope in 4.14 we have dhcp handling secondary IPs as well.
>
> On Fri, Oct 25, 2019 at 4:13 PM Andrija Panic
> wrote:
>
> > nope. you can add "se
I hope in 4.14 we have dhcp handling secondary IPs as well.
On Fri, Oct 25, 2019 at 4:13 PM Andrija Panic
wrote:
> nope. you can add "secondary" IP addresses to the same nic - these are NOT
> handled by dhcp, you manually add the IP inside the OS.
>
> On Fri, 25 Oct 2019, 11:54 Fariborz Navidan,
nope. you can add "secondary" IP addresses to the same nic - these are NOT
handled by dhcp, you manually add the IP inside the OS.
On Fri, 25 Oct 2019, 11:54 Fariborz Navidan, wrote:
> It seems it is not possible to add multiple BICs connected to same network.
> It is possible on VMware vCenter.
It seems it is not possible to add multiple BICs connected to same network.
It is possible on VMware vCenter. Is there any way to do this on
CloudStack/KVM?
"host" setting is what is propagated to agents once they are connected -
check if that was for some reason set to "localhost".
Glad you solved the problem!
On Fri, 25 Oct 2019, 10:22 Alessandro Caviglione,
wrote:
> Hello Andija,
> thank you very much for your effort and explanations :)
> Actual
Hello Andija,
thank you very much for your effort and explanations :)
Actually we're in advanced zone but I saw in SSVM cloud.log that it's
trying to connect lo localhost:8250 so I understood that SSVM was trying to
connect to Management Server that, obviously, is not localhost.
It's still not clea