Project

General

Profile

Actions
Copy link

Bug #12006

closed
AW

CARP IP sometimes doesn't apply to CARP member

Bug #12006: CARP IP sometimes doesn't apply to CARP member

Added by Andrew Waranowski over 5 years ago. Updated about 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
-
Start date:
06/07/2021
Due date:
% Done:

0%

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

Description

I noticed this when a CARP member had no CARP status. I was told that this can happen if the VIP address isn't applied to a member.

I saw this recently on a pfSense VM, and confirmed that the member which had a blank CARP status didn't have VIP IP applied to it. In this case, it was the backup unit. I was able to fix it by editing the virtual IP address, and then clicking 'save'. Then the IP properly applied. I was told that this issue sometimes appears after a software upgrade. Indeed, that jives, because I had recently upgraded the VM.

I saw it on:
2.5.1-RELEASE

Related issues 1 (0 open — 1 closed)

Is duplicate of Bug #12202: When a CARP VIP VHID change is synchronized to a secondary node, the CARP VIP is removed from the interface and the old VHIDs remain activeResolved

Actions

VG Updated by Viktor Gurov about 5 years ago Actions
Copy link
 #1

seems to be related to #12202

JP Updated by Jim Pingle about 5 years ago Actions
Copy link
 #2

  • Status changed from New to Duplicate

Reads the same to me. Closing as a duplicate. Can always reopen if we can get more detail that shows it's a unique problem.

JP Updated by Jim Pingle about 5 years ago Actions
Copy link
 #3

  • Is duplicate of Bug #12202: When a CARP VIP VHID change is synchronized to a secondary node, the CARP VIP is removed from the interface and the old VHIDs remain active added
Actions
Copy link

Also available in: Atom