How to change how the LM syncs across units in an HA pair

A change is made on the Shared IP that didn't replicate over to the standby unit.

Product: LoadMaster

Version: Any

Platform: Any

Application: Any

Changed the Verification File to Optional, but the standby unit still needs it. Why didn't it sync over?

• Navigate on the Shared IP to System Configuration > Miscellaneous Options > WUI Settings > change Update Verification Options to Optional. This will change System Configuration > System Administration > Update Software > Verification File to "Verification File (Optional)".
• On the individual IP of the standby unit, navigate to Local Administration > Update Software. Verification File still reads as "Verification File" (without the Optional notation).

• Configuration sync runs every 2 minutes and this change hadn't synced over yet.

• Configuration sync runs every 2 minutes and this change hadn't synced over yet.  In this case, just had to wait 2 minutes to see the change.
• Hostnames and Passwords for the bal account are not synchronized across HA pairs, so ensure to use the same password on both units. Problems may occur if different passwords are used.
• Additional parameters may be set within  Local Administration > HA Parameters:

  •  HA Update Interface - The interface used to synchronize the entire HA configuration within the HA cluster. Synchronization occurs every two minutes. The information is synchronized over SSH port 6973.

  • Force Partner Update - Immediately forces the configuration from the active to standby unit without waiting for a normal update. This option is only available if both units can see each other in an active/standby scenario.

  •  Inter HA L4 TCP Connection Updates - When using L4 services, enabling this option allows L4 connection information to be shared between the HA partners. If a failover occurs, the connection information will be available on the unit that assumes the master role. This option does not apply to L7 services.  If you do not allow multicast on the specific interface, inter-HA updates will not work. If you must have inter-HA updates, ensure to have a dedicated multicast-enabled interface for this purpose.

  •  Inter HA L7 Persistency Updates - When using L7 services, enabling this option allows L7 persistence information to be shared between the HA partners. If a failover occurs, the persistence information will be available on the unit that assumes the master role. This option does not apply to L4 services.  Enabling this option can have a significant performance impact.  If you do not allow multicast on the specific interface, inter-HA updates will not work. If you must have inter-HA updates, ensure to have a dedicated multicast-enabled interface for this purpose.