Project

General

Profile

Actions
Copy link

Bug #2578

closed

Upgrade 1.2.3 to 2.0 CARP

Added by Gerald Abshez over 13 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/07/2012
Due date:
% Done:

0%

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

Description

When upgrading more then 9 Carp interfaces, if the interfaces start at 0 in 1.2.3 they start at 1 when upgraded to 2.0. This causes CARP to think one of the interfaces is "down" and the CARP IP stays with the secondary.

Actions
Copy link

Also available in: Atom PDF