Project

General

Profile

Actions
Copy link

Bug #5625

closed

CARP VHID auto-incremented ?

Added by Stéphane Lapie almost 10 years ago. Updated almost 10 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
-
Start date:
12/10/2015
Due date:
% Done:

0%

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

Description

I am running pfSense as a virtual machine in VMware, and stumbled upon the following scenario :
  1. Several pfSense clusters running spanned on an existing ESXi cluster, and using the same subnet for CARP
  2. A new host was added to the ESXi cluster, which did not have the proper setting for Net.ReversePathFwdCheckPromisc
  3. One instance of pfSense was moved to said new host

This of course led to CARP going haywire (both nodes in the same cluster reporting BACKUP)
We realized our mistake quickly and set up the Net.ReversePathFwdCheckPromisc to make CARP work.
But then another cluster started acting up, and a tcpdump indicated that we had a VHID conflict.
Even though I initially had set the VHID for this cluster as 1, upon looking back, now the VHID had been incremented to 54, which overlapped with the VHID used by another cluster, bringing that VIP down.

I reckon encountering something similar two years ago, precisely while fumbling around with ESXi configuration for CARP, and stumbled upon it this week again.
Does this behavior ring bells with anyone?

Actions
Copy link

Also available in: Atom PDF