Actions
Bug #2578
closed
Upgrade 1.2.3 to 2.0 CARP
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.
Updated by Jim Pingle almost 13 years 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.
Updated by Chris Buechler over 10 years ago
- Status changed from New to Feedback
Gerald: could you provide your pre-upgrade config, or some further details, like what interfaces are you referring to re: "interfaces start at 0"?
Updated by Chris Buechler almost 10 years ago
- Status changed from Feedback to Closed
no apparent issues here, no response
Actions