This message was deleted.

ok, got it solved by manually reserving the VIPa and assigning a new IP for the second node, then rebooting that node while applying the config at the same time