Enabling or disabling Central Management System Peer Distributed Correlation using the CLI

Follow these steps to enable or disable the Central Management System Peer Distributed Correlation feature on each Central Management System peer using the CLI.

To enable the Central Management System Peer Distributed Correlation feature:

Go to CLI configuration mode.
```
CMS1 > enable
CMS1 # configure terminal
```
Enable the Central Management System Peer Distributed Correlation feature on a Central Management System peer.
```
CMS1 (config) # cms peer <peer_hostname> interaction dist-correlation enable
```
Save your changes.
```
CMS1 (config) # write memory
```

Verify the Distributed Correlation status on a CM peer. The following example verifies that Distributed Correlation is enabled on CMS2.

CMS1 (config) # show cms peer-service
CMS peer-service enabled:          yes
-----------------------------------------------------------------------
CMS peer CMS2:
Enabled:                     yes
Hostname:                    CMS2
   Address:                     172.16.216.51
   Auth-token checksum:         360a37cc532b9e2e75b674eb3b5fe2e0
   Interactions with peer: 
   Distributed CMS Correlation:
   Enabled:                        yes
   Status:                         OK          @ 2016/01/27 18:59:38
      Dynamic Threat Intelligence (DTI):
        Enabled:                        yes
        Proxy mode:                     No proxy
        Status:                         OK          @ 2016/01/27 18:59:38
      Update Peer:
         Enabled:                        yes
         Status:                         OK          @ 2016/01/27 19:02:23
-----------------------------------------------------------------------

To disable the Central Management System Peer Distributed Correlation feature:

Go to CLI configuration mode.
```
CMS1 > enable
CMS1 # configure terminal
```

Disable the CM Peer Distributed Correlation feature on a CM peer.

CMS1 (config) # no cms peer <peer_hostname> interaction dist-correlation enable

Verify the Distributed Correlation status on a CM peer. The following example verifies that Distributed Correlation is disabled on CMS2.

CMS1 (config) # show cms peer-service
CMS peer-service enabled:          yes
-----------------------------------------------------------------------
CMS peer CMS2:
  Enabled:                     yes
  Hostname:                    CMS2
   Address:                     172.16.216.51
   Auth-token checksum:         360a37cc532b9e2e75b674eb3b5fe2e0
   Interactions with peer:
      Distributed CMS Correlation:
         Enabled:                        no
         Status:                         UNKNOWN     @ N/A
      Dynamic Threat Intelligence (DTI):
         Enabled:                        yes
         Proxy mode:                     No proxy
         Status:                         OK          @ 2016/01/27 18:59:38
      Update Peer:
         Enabled:                        yes
         Status:                         OK        @ 2016/01/27 19:02:23
-----------------------------------------------------------------------