Configuring the managed appliances to use a cache proxy using the CLI

Use the commands in this topic to configure the managed appliances currently being managed by the Central Management System appliance to use a cache proxy. You must perform this configuration using the CLI on the managing Central Management System appliance. The managed appliance DTI source must be mapped to a cache proxy for software updates. You can configure only one cache proxy for each data center. You must create separate appliance profiles and appliance groups in each data center for the managed Release 7.5.0 (and later) appliances and managed Release 7.4.0 (and earlier) appliances.

Configuring the profile for the managed appliances

To configure the profile for the managed Release 7.5.0 and later appliances for each data center:

Go to CLI configuration mode.

cm-hostname > enable

cm-hostname # configure terminal

Prevent the Central Management System appliance from changing the managed appliance's DTI source server address, port, username, and password.
```
cm-hostname (config) # cmc profile profile_name command sequence_number "no fenet dti source override enable"
```
Specify the custom address for the cache proxy that will be used by the managed appliance.
```
cm-hostname (config) # cmc profile profile_name command sequence_number "fenet dti source type CUSTOM address address port port"
```
where:
- address is the IP address of the cache proxy.
- port is the source HTTPS port (443 by default).

Specify the custom username and password to authenticate access for the managed appliance to use the cache proxy.

cm-hostname (config) # cmc profile profile_name command sequence_number "fenet dti source type CUSTOM username CMS username password CMS password"

Specify the custom DTI download server for this appliance.

cm-hostname (config) # cmc profile profile_name command sequence_number "fenet dti source default CUSTOM"

Verify the custom configuration settings for the cache proxy for the managed appliance.

cm-hostname (config) # cmc profile profile_name command sequence_number "show fenet dti configuration"

Verify the profile that is configured for the managed Release 7.5.0 or later appliances.
```
cm-hostname (config) # show cmc profiles
```
Repeat this procedure for each data center.

Example

The following example shows how to configure the profile for the managed Release 7.5.0 or later appliances to use a local cache proxy:

cm-hostname (config) # cmc profile Profile1 command 1 "no fenet dti source override enable"

cm-hostname (config) # cmc profile Profile1 command 2 "fenet dti source type CUSTOM address 172.16.127.238 port 443"

cm-hostname (config) # cmc profile Profile1 command 3 "fenet dti source type CUSTOM username CMS username password CMS password"

cm-hostname (config) # cmc profile Profile1 command 4 "fenet dti source default CUSTOM"

cm-hostname (config) # cmc profile Profile1 command 5 "show fenet dti configuration"

To configure the profile for the managed Release 7.4.0 and earlier appliances for each data center:

Enable the CLI configuration mode.

cm-hostname > enable

cm-hostname # configure terminal

Specify the address and port 443 for the cache proxy.

cm-hostname (config) # cmc profile profile_name command sequence_number "fenet server CMS proxy IP address:443"

Specify the DTI network username and password for the managed Central Management System appliance.

cm-hostname (config) # cmc profile profile_name command sequence_number "fenet user CMS username password CMS password"

Verify the DTI client configuration settings for the managed Central Management System appliance.
```
cm-hostname (config) # cmc profile profile_name command sequence_number "show fenet"
```
Verify the profile that is configured for the managed Release 7.4.0 and earlier appliances.
```
cm-hostname (config) # show cmc profiles
```
Repeat this procedure for each data center.

Example

The following example shows how to configure the profile for the managed Release 7.4.0 and earlier appliances to use a local cache proxy:

cm-hostname (config) # cmc profile Profile2 command 1 "fenet server 172.16.127.238:443"

cm-hostname (config) # cmc profile Profile2 command 2 "fenet user CMSuser password CMS password"

cm-hostname (config) # cmc profile Profile2 command 3 "show fenet"

Creating a group for the managed appliances

You must create separate groups for the Release 7.5.0 (and later) and Release 7.4.0 (and earlier) appliances. You must create one group for each data center.

To create a group for the managed appliances for each data center:

Enable the CLI configuration mode.

cm-hostname > enable

cm-hostname # configure terminal

Add the appliance to the specified group.

cm-hostname (config) # cmc group group name appliance appliance name

Applying the profiles to the appliance group

You must apply the profiles to each appliance group for both the Release 7.5.0 (and later) and Release 7.4.0 (and earlier) appliances. The profiles must be applied for each data center.

To apply the profiles to the appliance group for Release 7.5.0 and later appliances:

Enable the CLI configuration mode.

cm-hostname > enable

cm-hostname # configure terminal

Apply the Release 7.5.0 or later appliance profile to the Release 7.5.0 and later group for each data center.

cm-hostname (config) # cmc profile profile name for Release 7.5.0 and later appliances apply group group name for Release 7.5.0 and later appliances

Repeat this procedure for each data center.

Example

The following example shows how to apply the profiles to the appliance group for Release 7.5.0 appliances:

cm-hostname (config) # cmc profile profile1 apply group group1

============ Release 7.5 Appliance Output ============

DTI CLIENT CONFIGURATIONS:

ACTIVE SETTINGS:

Mode               : online

Download source    : CUSTOM (CMSuser@172.16.127.238) - Managed by Appliance

Upload destination : CMS (CMSuser@172.16.127.214) - Managed by CMS

Mil service        : CMS (CMSuser@172.16.127.214) - Managed by CMS

AVAILABLE OPTIONS:

--------------------------------------------------------

Download   User                   Address

--------------------------------------------------------

CDN        CMSuser                cloud.fireeye.com

CMS        CMSuser                172.16.127.214

CUSTOM     CMSuser                172.16.127.238

DTI        CMSuser                staticcloud.fireeye.com

--------------------------------------------------------

Upload     User                   Address

--------------------------------------------------------

CMS        CMSuser                172.16.127.214

DTI        CMSuser                up-staticcloud.fireeye.com

--------------------------------------------------------

MIL        User                   Address

--------------------------------------------------------

CMS        CMSuser                172.16.127.214

DTI        CMSuser                mil-staticcloud.fireeye.com

To apply the profiles to the appliance group for Release 7.4.0 and earlier appliances:

Enable the CLI configuration mode.

cm-hostname > enable

cm-hostname # configure terminal

Apply the Release 7.4 and earlier appliance profile to the Release 7.4.0 and earlier group for each data center.

cm-hostname (config) # cmc profile profile name for Release 7.4.0 and earlier appliances  apply group group name for Release 7.4.0 and earlier appliances

Repeat this procedure for each data center.

Example

The following example shows how to apply the profiles to the appliance group for Release 7.4.0 and earlier appliances:

cm-hostname (config) # cmc profile profile2 apply group group2

============ Release 7.4 or Earlier Appliance Output ============

DTI CLIENT CONFIGURATION:

   Update source      : Managed by CMS (CMSuser@172.16.127.238:443)

   Update channel     : devel

   Http proxy         : None

   Connect timeout    : 30 (max tries: 3)

   Speed Time         : 60

   Max Time           : 14400

   Rate Limit         : None

   Lockdown enabled   : No