Bluecoat HTTP Connections Test

The Blucoat ProxySG appliance supports HTTP streaming. The HTTP connections are established through port 80 that allows you to send streaming data from the origin server to the clients. The HTTP connections established should be closely monitored over time to identify the HTTP connection load pattern on the appliance so that unusual traffic spikes can be spotted at ease. This can be achieved using the Blucoat HTTP Connections test!

This test continuously tracks the HTTP connections, and reports the total number of HTTP connections that are made to the appliance from the server and the clients. In addition, this test also reveals the count of HTTP connections that are currently active and are idle in the server side/client side.

Target of the test : A Bluecoat ProxySG

Agent deploying the test : An external agent

Outputs of the test : One set of results for each fan sensor available in each module of the target Bluecoat ProxySG that is being monitored

Configurable parameters for the test
Parameters Description

Test period

How often should the test be executed

Host

The host for which the test is to be configured.

SNMPPort

The port at which the monitored target exposes its SNMP MIB; the default is 161.

SNMPversion

By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.

SNMPCommunity

The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the snmpversion chosen is v3, then this parameter will not appear.

Username

This parameter appears only when v3 is selected as the SNMPversion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. 

Context

This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the username in the Context text box.  By default, this parameter is set to none.

Authpass

Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3.

Confirm password

Confirm the Authpass by retyping it here.

Authtype

This parameter too appears only if v3 is selected as the SNMPversion. From the AuthType list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

  • MD5 - Message Digest Algorithm
  • SHA - Secure Hash Algorithm
  • SHA224 - Secure Hash Algorithm 224 bit
  • SHA256 - Secure Hash Algorithm 256 bit
  • SHA384 - Secure Hash Algorithm 384 bit
  • SHA512 - Secure Hash Algorithm 512 bit

Encryptflag

This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. 

Encrypttype

If the EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:

  • DES - Data Encryption Standard
  • 3DES - Triple Data Encryption Standard
  • AES - Advanced Encryption Standard
  • AES128 - Advanced Encryption Standard 128 bit
  • AES192 - Advanced Encryption Standard 192 bit
  • AES256 - Advanced Encryption Standard 256 bit

Encryptpassword

Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.

Timeout

Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds.

Data Over TCP

By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No.

EngineID

This parameter appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Total client connections

Indicates the total number of HTTP connections that were established by the clients on the ProxySG appliance.

Number

 

Active client connections

Indicates the number of currently active HTTP connections that were established by the clients on the ProxySG appliance.

Number

The value of this measure should not exceed the value of Total client connections measure. If the value of this measure exceeds the Total client connections measure, then, the appliance begins to terminate idle persistent connections to allow the processing of new incoming requests. If the value of this measure exceeds the Total client connections measure when all connections are active, then, processing of incoming requests would be delayed until the processing of existing requests is complete.

Idle client connections

Indicates the number of HTTP connections (established by the clients) that were currently idle.

Number

 

Total server connections

Indicates the total number of HTTP connections that were established on the ProxySG appliance from the sever.

Number

 

Active server connections

Indicates the number of currently active HTTP connections that were established on the ProxySG appliance from the server.

Number

 

Idle server connections

Indicates the number of HTTP connections (established from the server) that were currently idle.

Number