Enabling HTTP proxy settings for automatic failover using the CLI

Prev Next

You can configure a managed appliance that uses single-port communication to use the Central Management System appliance for DTI services, but to fail over to the HTTP proxy server if the Central Management System appliance becomes unavailable. This is the default behavior when an HTTP proxy server is configured and enabled on the appliance.

To enable automatic failover for DTI services:
  1. Go to CLI configuration mode:

    hostname > enable
    hostname # configure terminal
  2. Configure and enable the proxy server as described in Configuring HTTP proxy server settings using the CLI

  3. Verify that the Central Management System appliance controls the active settings for the DTI services, that the HTTP proxy server is enabled, and that HTTP proxy settings are disabled for DTI services:

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

    hostname (config) # write memory

Example

The following example configures minimal settings for an HTTP proxy server and then enables it. It then shows that the Central Management System appliance currently controls the active settings for DTI services, that the proxy server is configured and enabled on the appliance, and that proxy settings are currently disabled for DTI services.

If the Central Management System appliance becomes unavailable, the values in the ACTIVE SETTINGS section change to DTI, and the values in the ACTIVE SETTINGS FOR HTTP PROXY section change to yes.

hostname (config) # fenet proxy host 192.168.2.3
hostname (config) # fenet proxy 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      : CMS (User8@10.4.5.6 : singleport) - Managed by CMS
    ...

  ACTIVE SETTINGS FOR HTTP PROXY:

    Http proxy         : @192.168.2.3: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)
    ...