CARP under 10.3 - can't "ifconfig down" one or more VHIDs?

[Steven Hartland]

The underlying protocol hasn’t changed just the presentation so there
shouldn’t be any issues between 9 and 10.

On Sat, 23 Sep 2017 at 09:21, Karl Pielorz <kpielorz_lst at tdx.co.uk> wrote:

>
>
> --On 22 September 2017 at 20:16:25 +0100 Steven Hartland
> <killing at multiplay.co.uk> wrote:
>
> > CARP on 9 and 10 are very different its not a separate interface anymore,
> > its a property on the parent interface, so the behavior your described is
> > expected.
> >
> > If you want to disable carp just remove it, if however you want for fail
> > to the other virtual host, just bump the advskew or force the state
> > change.
>
> Ok, thanks for confirming that - bit of a shame 'ifconfig carpX down' was a
> very quick way of temporarily removing CARP (i.e. so the host didn't
> participate in the pool) for maintenance while leaving the base / parent
> interface available - and then putting it back 'as-was' with messing around
> with the other values.
>
> Do you know if there's any interoperability issues having some 9.x and some
> 10.x sharing the same CARP system?
>
>
> I'll probably replace with a script to store the skews, push them to a very
> high value, mark as 'BACKUP' all the VHID's - and something to undo it all
> again - though actually just removing it might be easier (providing adding
> it doesn't cause a moment of "I'm MASTER, uh, no, I'm BACKUP").
>
> -Karl
>