--- title: "Configuring security content replication using the CLI" slug: "configuring-security-content-replication-using-the-cli" tags: ["Central Management System", "Install and Get Started"] updated: 2026-10-01T08:29:31Z published: 2026-10-01T08:29:31Z canonical: "docs.trellix.com/configuring-security-content-replication-using-the-cli" --- > ## 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. # Configuring security content replication using the CLI Use the commands in this section to configure whether security content is continuously passed to the secondary node. By default, security content replication is enabled on both nodes. (See [Alert replication](/network-and-platform/docs/introduction-1#alert_replication) for information about this configuration option.) ### Note This is a global configuration. The configuration actions are performed from only one node, but are applied to the cluster. ### Disabling security content replication Stop the cluster engine on both nodes: 1. Log in to the secondary node. 2. Enable the CLI configuration mode: ```plaintext node-hostname > enable node-hostname # configure terminal ``` 3. Stop the cluster engine: ```plaintext node-hostname (config) # ha engine stop ``` 4. Repeat these steps on the primary node. Disable security content replication: 1. Disable alert replication: ```plaintext node-hostname (config) # no ha replicate updates enable ``` 2. Verify your change: ```plaintext node-hostname (config) # show ha configuration ``` 3. Save your change: ```plaintext node-hostname (config) # write memory ``` Restart the cluster engine on both nodes: 1. Restart the cluster engine on the primary node: ```plaintext node-hostname (config) # ha engine restart ``` 2. Repeat the previous step to restart the cluster engine on the secondary node. ### Enabling security content replication Stop the cluster engine on both nodes: 1. Log in to the secondary node. 2. Enable the CLI configuration mode: ```plaintext node-hostname > enable node-hostname # configure terminal ``` 3. Stop the cluster engine: ```plaintext node-hostname (config) # ha engine stop ``` 4. Repeat these steps on the primary node. Enable security content replication: 1. Enable security content replication: ```plaintext node-hostname (config) # ha replicate updates enable ``` 2. Verify your change: ```plaintext node-hostname (config) # show ha configuration ``` 3. Save your change: ```plaintext node-hostname (config) # write memory ``` Restart the cluster engine on both nodes: 1. Restart the cluster engine on the primary node: ```plaintext node-hostname (config) # ha engine restart ``` 2. Repeat the previous step to restart the cluster engine on the secondary node. ### Example The following example prevents security content updates on the primary node from being replicated to the secondary node. ```plaintext node2 (config) # ha engine stop ... ``` ```plaintext node1 (config) # ha engine stop node1 (config) # no ha replicate updates enable node1 (config) # show ha configuration CM HA Cluster Settings:   ...   Replicating:       Configuration:         yes       Alerts:                yes       Security content:      no ... node1 (config) # write memory node1 (config) # ha engine restart ... ``` ```plaintext node2 (config) # ha engine restart ... ``` :