--- title: "Synchronizing configuration settings" slug: "synchronizing-configuration-settings" tags: ["Network Security (NX)", "Product Usage"] updated: 2026-10-01T14:01:12Z published: 2026-10-01T14:01:18Z canonical: "docs.trellix.com/synchronizing-configuration-settings" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Synchronizing configuration settings The configuration settings that affect detection must be identical for the two Network Security appliances in a Network Security HA pair, because each appliance must assume the detection functions of its peer if the peer fails. The Central Management System appliance warns you when the following settings do not match, and provides a way to synchronize the settings of one appliance with the other appliance: - Date and Time ### Important You can use the procedures in this section to synchronize NTP servers and the time zone. However, if the system time on the two appliances differs by more than 30 seconds, a status message will be displayed, and you must synchronize the time manually. You can change the system time on one appliance to match its peer, set the time in the Central Management System Web UI in the context of the pair, or enable NTP on the pair. - Email - DTI Network - Inline Operational Modes - Inline Policy Exceptions - Whitelists - IPS Policy and Policy Exceptions ### Note To successfully synchronize IPS settings, both appliances must have a valid IPS license. - Network IP Address Whitelists - Login Banner - Static Analysis tool settings, such as AV-Suite integration, AV-Check, YARA configuration, and dropper detection ### Note To successfully synchronize AV-Check settings, both appliances must have a valid AV_ENGINE_SOPHOS license. The Central Management System Web UI prevents you from making configuration changes in the wrong context. If the setting must be made on the pair, you cannot select the individual appliances from the appliance drop-down list. If the setting must be made on the individual appliance, you cannot select the pair. In the following examples, the pair name is **Acme_NXHA**, and the appliance names are **nx-1** and **nx-2**. The individual appliance names are not available in the list for the **DTI Network Settings** page, and the pair name is not available on the **User accounts** page. | ![NXHA_PairContext_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-6261386a-0056-5e17-a873-813d6c6209bf.png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A27%3A52Z&se=2026-11-20T08%3A27%3A52Z&sr=c&sp=r&sig=PNBXdfAtneKuwuAQrBZOV%2FHeiVqvluMO%2FOBKsYOTYio%3D) | | --- | | ![NXHA_IndividContext_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-6ac97890-a119-8886-9a8a-bae14f5953a4.png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A27%3A52Z&se=2026-11-20T08%3A27%3A52Z&sr=c&sp=r&sig=PNBXdfAtneKuwuAQrBZOV%2FHeiVqvluMO%2FOBKsYOTYio%3D) | ### Important The following settings must match, but the Central Management System appliance does not warn you if they are out-of-sync. You must check the settings on each appliance, and manually synchronize them if necessary. - YARA Rules - Custom Rules ( Network Security and IPS) - Custom MD5 Whitelists - Custom MD5 Blacklists - Custom Greylists #### Configuration mismatches As described in [Configuration replication](/network-and-platform/docs/about-network-security-high-availability#configuration-replication), these settings might be different. When this happens, a message is displayed in the Central Management System Web UI and on each page with settings that must be configured in the context of a pair. The **Appliances** > **Sensors** page provides sync controls and tooltips that display the mismatched settings when you hover your cursor over them. Examples of these messages follow. Web UI Example ![NXHA_HealthDashCM1_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-8da9fce1-7d5b-ce75-81be-8ee75b7f5974.png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A27%3A52Z&se=2026-11-20T08%3A27%3A52Z&sr=c&sp=r&sig=PNBXdfAtneKuwuAQrBZOV%2FHeiVqvluMO%2FOBKsYOTYio%3D) Appliances page examples ![NXHA_MismatchTooltip3_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-40a45442-24cd-a412-d7db-33eb32eedad0.png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A27%3A52Z&se=2026-11-20T08%3A27%3A52Z&sr=c&sp=r&sig=PNBXdfAtneKuwuAQrBZOV%2FHeiVqvluMO%2FOBKsYOTYio%3D) ![NXHA_MismatchTooltip_scap.PNG](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-7e1f1a91-c9dc-92f0-ce70-a7527be44f70.png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A27%3A52Z&se=2026-11-20T08%3A27%3A52Z&sr=c&sp=r&sig=PNBXdfAtneKuwuAQrBZOV%2FHeiVqvluMO%2FOBKsYOTYio%3D) The following sections describe how to use the Central Management System appliance to synchronize the configuration of one Network Security appliance to the peer appliance. ### Note Other items, such as the appliance model, software image, guest images, security content, detection-related feature licenses, and Network Security edition must also be identical. See [System requirements](/network-and-platform/docs/system-requirements-12) and [Viewing the Network Security HA status](/network-and-platform/docs/viewing-the-network-security-ha-status) for more information. #### Prerequisites - Operator or Admin access :