Bug #2578

Upgrade 1.2.3 to 2.0 CARP

Added by Gerald Abshez 10 months ago. Updated 3 months ago.

Status:New Start date:08/07/2012
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
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.

History

#1 Updated by Jim P 3 months ago

Do you happen to have a copy of your config from before and after this upgrade to compare? You can e-mail it in if you don't want to post a sanitized version here.

Also available in: Atom PDF