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 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
Disable security content replication:
Disable alert replication:
node-hostname (config) # no ha replicate updates enableVerify your change:
node-hostname (config) # show ha configurationSave your change:
node-hostname (config) # write memory
Enabling security content replication
Enable security content replication:
Enable security content replication:
node-hostname (config) # ha replicate updates enableVerify your change:
node-hostname (config) # show ha configurationSave your change:
node-hostname (config) # write memory
Example
The following example prevents security content updates on the primary node from being replicated to the secondary node.
node2 (config) # ha engine stop
...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
...node2 (config) # ha engine restart
...