Overview
You may be experiencing an issue with Configuring High Availability in Kerio Control, where the HA validation fails with the error Interface names are not matching
, despite the web administration UI showing identical interfaces and all HA configurations showing as per the recommendations.
The behavior affects specific configurations involving a Kerio Control appliance (usually the Master) that was upgraded over time, and new Kerio Control appliances (the Slave) that was deployed directly with the latest version.
Solution
The described behavior stems from a legacy defect related to the HA mechanism. That defect was fixed by changing the name of the Dial-in default interface (which does not show up in the web admin UI), and because of this name change, HA between new appliances and old appliances will fail with error Interface names are not matching
To resolve the issue with the High Availability (HA) setup in Kerio Control where the interface names do not match, follow these steps:
- SSH into the Master device.
- Run the following commands one by one:
mount -o remount,rw /
/opt/kerio/winroute/tinydbclient "update Interfaces_V2 set Name='Interface #2' where Id='Dial-In'"
reboot
- After the appliance reboots, re-establish the SSH connection and confirm that the Dial-in interface name persists:
cat /opt/kerio/winroute/winroute.cfg | grep -i "Interfaces_v2" -A 10
- Try to resync the HA devices again and check if the issue still occurs.
Summary
This article provides a solution to the issue of mismatched interface names in the High Availability (HA) setup in Kerio Control. The solution involves SSHing into the Master device, renaming the Dial-in interface, and then trying to resync the HA devices.
FAQ
-
What is the cause of the interface names mismatch in the HA setup in Kerio Control?
The issue stems from legacy defect related to a change in the interface names, affecting specific configurations involving a Kerio Control appliance that was upgraded over time, and new Kerio Control appliances. -
What is the solution to the interface names mismatch in the HA setup in Kerio Control?
The solution involves SSHing into the Master device, running specific commands, and then trying to resync the HA devices.