Enabling HTTP proxy settings on a single-port managed appliance using the CLI

Prev Next

Use the commands in this topic to enable a managed appliance that uses single-port communication to send DTI service requests through an HTTP proxy server.

To enable HTTP proxy settings for a DTI service:
  1. Go to CLI configuration mode:

    hostname > enable
    hostname # configure terminal
  2. View the current DTI service configuration:

    hostname (config) # show fenet dti configuration brief
  3. Move control of the DTI service to the managed appliance.

    • For the download service:

      hostname (config) # no fenet dti source override enable
    • For the enrollment, faude, mil, or virtual service:

      hostname (config) # no fenet dti <service> service override enable
    • For the upload destination service:

      hostname (config) # no fenet dti upload destination override enable
  4. View the current DTI service configuration:

    hostname (config) # show fenet dti configuration brief
  5. If the value for the service in the ACTIVE SETTINGS FOR HTTP PROXY section is no, enable proxy settings for the service.

    • For the source service:

      hostname (config) # fenet dti source proxy enable
    • For the enrollment, faude, or virtual service:

      hostname (config) # fenet dti <service> service proxy enable
    • For the upload destination service:

      hostname (config) # fenet dti upload destination proxy enable
  6. Verify your changes:

    hostname (config) # show fenet dti configuration brief
  7. Save your changes:

    hostname (config) # write memory

Examples

The following example moves control of the faude service to the managed appliance, which enables HTTP proxy settings for the service.

hostname (config) # show fenet dti configuration brief

DTI CLIENT CONFIGURATIONS:
  ACTIVE SETTINGS:
    
    Mode               : online
    Download source    : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    Upload destination : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    Mil service        : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    Faude service      : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    ...

  ACTIVE SETTINGS FOR HTTP PROXY: 

    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)

    Download source    : no (reason: singleport is in use)
    Upload destination : no (reason: singleport is in use)
    Mil service        : no (reason: singleport is in use)
    Faude service      : no (reason: singleport is in use) 
    ....

hostname (config) # no fenet dti faude service override enable
hostname (config) # show fenet dti configuration brief

DTI CLIENT CONFIGURATIONS:
  ACTIVE SETTINGS:
    
    Mode               : online
    Download source    : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    Upload destination : CMS (User8@10.4.5.6 : singleport) - Managed by CMS 
    Mil service        : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    Faude service      : DTI (User8@unity.fireeye.com) - Managed by Appliance
    ...

  ACTIVE SETTINGS FOR HTTP PROXY: 

    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)

    Download source    : no (singleport is in use)
    Upload destination : no (singleport is in use)
    Mil service        : no (singleport is in use)
    Faude service      : yes
    ...

The following example re-enables HTTP proxy settings for the source service.

hostname (config) # show fenet dti configuration brief

DTI CLIENT CONFIGURATIONS:
  ACTIVE SETTINGS:
    
    Mode               : online
    Download source    : DTI (User8@staticcloud.fireeye.com) - Managed by Appliance
    ...

  ACTIVE SETTINGS FOR HTTP PROXY: 

    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)
    Download source    : no (reason: administratively disabled)
    ...

hostname (config) # fenet dti source proxy enable
hostname (config) # show fenet dti configuration brief

DTI CLIENT CONFIGURATIONS:
  ACTIVE SETTINGS:
    
    Mode               : online
    Download source    : DTI (User8@staticcloud.fireeye.com) - Managed by Appliance
    ...

  ACTIVE SETTINGS FOR HTTP PROXY: 

    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)
    Download source    : yes
    ...