Hi Jithin, Thank you for the update.
Yes, I did try that, and the interface would get an additional IP address. However, we are unable to add the same IP to another VM as a secondary. For instance, in case of a DB cluster VM 1 (DB1) with nic ens3 and IP 10.1.1.6 VM 2 (DB2) with nic ens3 and IP 10.1.1.7 For these two virtual machines, I need to set up a floating IP with pacemaker, such as 10.1.1.8. As a result, my application can connect to this floating IP, and the pacemaker will display the IP address on VM2 (DB2) in the event that VM1 goes down. Hope you got my senario With Regards, Nixon Varghese On Tue, Jul 2, 2024 at 11:57 AM Jithin Raju <[email protected]> wrote: > Hi Nixon, > > Could you try acquiring the required IP as a secondary IP address in one > of the instances? I think that should work. > > -Jithin > > From: Nixon Varghese K S <[email protected]> > Date: Tuesday, 2 July 2024 at 11:38 AM > To: [email protected] <[email protected]> > Subject: Floating IP Assigning for Instance on Cloudstack > Hello, > > We have a requirement to run same service on a different instance and we > need floating IP between them to connect. We were successful in setting up > communication and floating IP on the virtual machine. CloudStack VR is not > aware of the floating IP configuration since it was done at the VM OS > level. As a result, we noticed that VR would use DHCP to assign the same IP > to another VM. Is it possible to add floating IP to an interface in a way > that makes CloudStack VR aware of it? I received very little documentation > regarding the same. Would someone kindly share their thoughts with me? > > Thank you.... > -- > With Regards, > Nixon Varghese > > > > -- With Regards, Nixon Varghese
