Bug #3407


Changing CARP IP to IP Alias doesn't work until failover is trigered

Added by Jason Litka almost 8 years ago. Updated over 7 years ago.

Virtual IP Addresses
Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


If you change an existing CARP IP Address to an IP Alias it does not work, even after hitting apply. Instead, you need to trigger a CARP failover to the backup and then move it back over to the master.

Actions #1

Updated by Chris Buechler almost 8 years ago

you mean on the secondary, the primary, or both? What does ifconfig look like on both systems afterwards?

Actions #2

Updated by Jason Litka almost 8 years ago

The config in the UI looks correct on both the master and the backup (listed as IP Alias in Virtual IPs screen, disappears from CARP status screen) but the IP address stops working immediately after you click "Apply" on the Virtual IPs screen.

To get it working again you need to go to the CARP Status screen on the first box and click Disable CARP. At this point the IP will work correctly on the second box. If you then reenable CARP on the first box so that the IPs transition back then it will work correctly there as well.

I added a CARP IP back to my systems to test (I migrated them all to IP Alias after I figured this out earlier). That CARP IP was named opt1_vip10.

The output of ifconfig changes exactly as expected at each step. As a baseline, there is an interface of opt1_vip10 with the IP address I assigned it. After switching the IP to an Alias that interface disappears from ifconfig and the address moves up as an additional on opt1_vip3. There is no difference between ifconfig at this point and again after initiating a carp failover/failback.

If there's an issue here it must be in the NAT or FW rules.

Actions #3

Updated by Renato Botelho almost 8 years ago

  • Assignee set to Renato Botelho
  • Target version set to 2.1.1

I reproduced it here, will work on a fix.

Actions #4

Updated by Renato Botelho almost 8 years ago

  • Status changed from New to Feedback

As you mentioned, when moved from CARP (WAN) to an IP alias (using other CARP IP as interface), the IP stops answering. But, after a short period of time (about 10 seconds) it starts to answer again and work fine. I'm using the most recent 2.1.1 snapshot to make the tests.

Actions #5

Updated by Jason Litka almost 8 years ago

That's not something I can duplicate under 2.1 or 2.1.1 built on "Wed Jan 22 04:46:20 EST 2014".

If I change a CARP IP to an IP Alias and make the parent the actual physical interface it works right away. If I make the parent a CARP IP then it doesn't come online until after a failover.

Actions #6

Updated by Chris Buechler over 7 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF