Project

General

Profile

Actions
Copy link

Bug #14340

closed

Unicast CARP XMLRPC sync does not adjust CARP peer address when sycnrhonizing

Added by Jim Pingle over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
XMLRPC
Target version:
23.05
Start date:
Due date:
% Done:

100%

Estimated time:
Release Notes:
Force Exclusion
Affected Plus Version:
23.05
Affected Architecture:

Description

When XMLRPC sync is enabled for VIPs and the primary has a unicast CARP VIP configured, the VIP is copied to the secondary without adjusting the peer address. As a consequence, the VIP status won't be correct in all cases because the secondary node won't have the proper peer address.

We should be able to adjust it similar to the method used for DHCP failover where it finds the appropriate interface address and copies that into the appropriate place before synchronizing.

To me, I have a working patch that covers the basics here.

Actions
Copy link

Also available in: Atom PDF