Connection Status Test

This test displays the number of connection types (such as optimized, pass through, active, half-opened, half-closed, established, etc.) that pass through this device and alert administrators to promptly capture abnormalities in the device.

Target of the test : A Riverbed SteelHead

Agent deploying the test : An external agent

Outputs of the test : One set of results for the Riverbed SteelHead device is being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The IP address of the target host to be monitored.


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


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.


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.


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. 


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.


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.


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


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. 


If this 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
  • AES – Advanced Encryption Standard


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


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.

Measures made by the test
Measurement Description Measurement Unit Interpretation

Optimized connection

Indicates the number of optimized connections.


Optimized connections are connections that process request quickly by first searching in local cache i.e. datastore. If the request is available in datastore, data is fetched from the datastore. The request goes to the WAN, only on unavailability of that request in datastore. An optimized connection includes Half-closed, Half-opened, Active, Idle and Established connections in it.

Passthrough connection

Indicates the number of unoptimized connections that pass through.


Passthrough connections are connections that process request directly to WAN instead of searching in datastore i.e. local cache. Since the search request happens in WAN, which is time consuming, the passthrough connection will be an unoptimized one.

Half-Opened connection

Indicates the number of half opened active connections.


Half-opened connection is nothing but a TCP connection in which the connection has not been fully established. If you are experiencing a large number of half-opened connections, consider a more appropriately sized SteelHead.

Half-Closed connection

Indicates the number of half closed active connections.


Half-closed connections are connections that the SteelHead has intercepted and optimized but are in the process of being disconnected. If you are experiencing a large number of half-closed connections, consider a more appropriately sized SteelHead.


Half-closed connections might remain if the client or server doesn't close its connections cleanly.

Established connection

Indicates the number of established connections.


Established connection is nothing but a newly forming, initiating connections available in the Riverbed SteelHead device. The connection is being established but doesn't yet have an inner channel.

Active connection

Indicates the number of active connections.


An abnormally high value for this measure could indicate a probable virus or spam attack to this device.

Total connection

Indicates the total number of connections that pass through this device.


This measure is a sum total of all optimized connections.