Brent, Sounds like you are assigning the same IP to two guest vms. Cloudstack will guard against that. It will allow for the redundancy in guest networks on the router and we are looking into implementing this on vpc routers as well. There are no plans for allowing this on regular vms.
Am I understanding your query correctly? On Wed, Jun 18, 2014 at 1:11 PM, Nux! <n...@li.nux.ro> wrote: > Sounds like you are trying to use vrrp/keepalive, I am not sure how this will > work. > > What kind of environment do you have? In basic or advanced network with > security groups will be tricky to get it working. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > > ----- Original Message ----- > From: "Brent Clark" <bcl...@tendrilinc.com> > To: users@cloudstack.apache.org > Sent: Tuesday, 17 June, 2014 4:14:22 PM > Subject: Floating IP for use between 2 VMs > > I have run into an issue that I need help in finding the proper solution. > > CloudStack version 4.2.1, KVM > > We have the need for 2 VMs to use the same IP. They wont be using it at the > same time. We have a tool that configures an IP on the interface of one VM > and when the other cannot detect it, it configures an interface on the > other for that same IP. > > I tried assigning a secondary IP to the VMs and I was able to for one, but > the other wont let me because the other already has it assigned. > > Is the secondary IP not the correct way to do what I am wanting? Is there a > better way or one that is supported? > > Many Thanks! > > > -- > Brent S. Clark > Senior Cloud & Infrastructure Systems Engineer > > 2580 55th St. | Boulder, Colorado 80301 > www.tendrilinc.com | blog <http://www.tendrilinc.com/news-room/blog/> > <http://www.tendrilinc.com/> > > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the sender. > Please note that any views or opinions presented in this email are solely > those of the author and do not necessarily represent those of the company. > Finally, the recipient should check this email and any attachments for the > presence of viruses. > The company accepts no liability for any damage caused by any virus > transmitted by this email. -- Daan
