Allowing or preventing a Central Management System peer to use a proxy server using the CLI

Follow these steps to allow or to prevent a Central Management System peer to use a proxy server to connect to other remote Central Management System peers.

To allow a Central Management System peer to use a proxy server:

Go to CLI configuration mode.
```
CMS1 > enable
CMS1 # configure terminal
```
Identify a Central Management System peer to use the same proxy server settings that are configured for DTI interaction to connect to other remote Central Management System peers.
```
CMS1 (config) # cms peer <peer_hostname> interaction dti proxy mode use-fenet
```
Save your changes.
```
CMS1 (config) # write memory
```

Verify the proxy server status on a Central Management System peer. The following example verifies that CMS2 is allowed to use a proxy server.

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 19:12:59
      Dynamic Threat Intelligence (DTI):
         Enabled:                        yes
         Proxy mode:                     Use FENET proxy settings
         Status:                         OK          @ 2016/01/27 19:12:59
      Update Peer:
         Enabled:                        yes
         Status:                         OK          @ 2016/01/27 19:12:59
-----------------------------------------------------------------------

To prevent a Central Management System peer from using a proxy server:

Go to CLI configuration mode.
```
CMS1 > enable
CMS1 # configure terminal
```
Prevent a Central Management System peer from using any proxy server to connect to other remote Central Management System peers for DTI interaction.
```
CMS1 (config) # cms peer <peer_hostname> interaction dti proxy mode no-proxy
```
Save your changes.
```
CMS1 (config) # write memory
```

Verify the proxy server status on a Central Management System peer. The following example verifies that CMS2 is not allowed to use a proxy server.

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 19:07:26
      Dynamic Threat Intelligence (DTI):
         Enabled:                        yes
         Proxy mode:                     No proxy
         Status:                         OK          @ 2016/01/27 19:07:26
      Update Peer:
         Enabled:                        yes
         Status:                         OK          @ 2016/01/27 19:07:26
-----------------------------------------------------------------------