Radware AD Farm Statistics Test
This test tracks the DNS, HTTP, SIP connections in the AD Farm and reports the count of requests received, requested, and/ or re-directed, thereby revealing error responses to administrators and their probable causes.
Target of the test : A Radware AppDirector
Agent deploying the test : An External agent
Outputs of the test : One set of results for each AD Farm configured on the target Radware Appdirector that is to be monitored.
Parameters | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The IP address of the target switch that is being monitored. |
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. |
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:
|
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:
|
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. |
Engine ID |
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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
DNS requests received |
Indicates the number of DNS requests received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of DNS requests. |
DNS requests answered |
Indicates the number of DNS requests that were answered by this AD farm during the last measurement period. |
Number |
A low value indicates that there are traffic issues in the AD farm. Compare the value of this measure across AD farms to identify the AD farm that is poor in answering the DNS requests received. |
DNS requests re-directed to remote server |
Indicates the number of DNS requests that were redirected to a remote server from this AD farm during the last measurement period. |
Number |
|
HTTP sessions received |
Indicates the number of HTTP sessions that were received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of HTTP requests. |
HTTP sessions re-directed to local server |
Indicates the number of HTTP sessions that were directed to a local server by this AD farm during the last measurement period. |
Number |
HTTP requests that are received beyond the capacity of the AD farm are redirected to a local server in order to balance the load. |
HTTP sessions re-directed to remote server |
Indicates the number of HTTP sessions that were redirected to remote server by this AD farm during the last measurement period. |
Number |
HTTP requests that are received beyond the capacity of the AD farm are redirected to a remote server in order to balance the load. |
Triangulation requests received |
Indicates the number of triangulation requests received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of triangulation requests. |
Triangulation requests answered |
Indicates the number of triangulation requests that were answered by this AD farm during the last measurement period. |
Number |
A low value indicates that there are traffic issues in the AD farm. Compare the value of this measure across AD farms to identify the AD farm that is poor in answering the triangulation requests received. |
Triangulation requests re-directed to remote server |
Indicates the number of triangulation requests redirected to a remote server from this AD farm during the last measurement period. |
Number |
Triangulation requests that are received beyond the capacity of the AD farm are redirected to a remote server in order to balance the load. |
RTSP requests received |
Indicates the number of RTSP requests received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of RTSP requests. |
RTSP requests re-directed to local server |
Indicates the number of RTSP requests that were redirected to a local server from this AD farm during the last measurement period. |
Number |
RTSP requests that are received beyond the capacity of the AD farm are redirected to a local server in order to balance the load. |
RTSP requests re-directed to remote server |
Indicates the number of RTSP requests that were redirected to a remote server from this AD farm during the last measurement period. |
Number |
RTSP requests that are received beyond the capacity of the AD farm are redirected to a remote server in order to balance the load. |
SIP requests received |
Indicates the number of SIP requests that were received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of SIP requests. |
SIP requests re-directed to local server |
Indicates the number of SIP requests that were redirected by this AD farm to a local server during the last measurement period. |
Number |
SIP requests that are received beyond the capacity of the AD farm are redirected to a local server in order to balance the load. |
SIP requests re-directed to remote server |
Indicates the number of SIP requests that were redirected by this AD farm to a local server during the last measurement period. |
Number |
SIP requests that are received beyond the capacity of the AD farm are redirected to a remote server in order to balance the load. |
Proxy sessions received |
Indicates the number of Proxy (Client NAT redirection) requests received by this AD farm during the last measurement period. |
Number |
This measure is a good indicator of load on the AD farm. Compare the value of this measure across AD farms to identify the AD farm that received maximum number of proxy requests. |
Proxy sessions re-directed to local server |
Indicates the number of Proxy (Client NAT redirection) requests received by this AD farm and were redirected to a local server during the last measurement period. |
Number |
Proxy requests that are received beyond the capacity of the AD farm are redirected to a local server in order to balance the load. |
Proxy sessions re-directed to remote server |
Indicates the number of Proxy (Client NAT redirection) received by this farm and were redirected to remote servers during the last measurement period. |
Number |
Proxy requests that are received beyond the capacity of the AD farm are redirected to a remote server in order to balance the load. |