In this chapter, you will find information on how to sync the master node and the slave node with regards to the HA configuration, to connection tracking, to logs and statistics and on sync constraints.
Configuration
All configuration changes are synced with the slave node. During the synchronization and activation process, the HA feature is displayed as Not in sync. A role switch during the synchronization process can lead to data loss or loss of configuration changes.
Configuration changes are synced after a 15 second delay to prevent unnecessary activations in the slave node.
Click 
Activate in the toolbar at the top of the desktop to to start a full sync.
Connection Tracking
Connection-based protocols, as TCP, are tracked in the firewall. The tracking tables are automatically synced with the slave node. Therefore, connections remain after a role switch, e. g. during a downloading process.
Logs and Statistics
Your LANCOM R&S®Unified Firewall synchronizes the log and statistics databases between the master and slave system. Logs of the slave node are not stored, as the slave database only provides read permissions.
Constraints
The UTM features only save the status of connections through the firewall.
Example: The DPI engine stored meta data of packets that have already been analyzed until the connection ends.
Your LANCOM R&S®Unified Firewall does not synchronize this connection status, but stores it in the master node. After a role switch, all connections that have been analyzed by the UTM feature, are interrrupted.
Example: A loss of meta data makes the DPI engine reject new packets of an older connection as unknown.
