Measures reported by LBL4VSTest
The Load Balancer consists of multiple virtual servers which, in turn, consists of an IP address and port. This virtual server is bound to a number of physical servers a.k.a real servers within a server farm. A virtual server is capable of performing the following:
Distribute client requests across multiple servers to balance server load; Apply various behavioral settings to a specific type of traffic; Enable persistence for a specific type of traffic; Direct traffic according to user-written rules
In addition, virtual servers can also be used in the following ways:
Directing traffic to a load balancing pool; Sharing an IP address with a VLAN node; Forwarding traffic to a specific destination IP address; Increasing the speed of processing HTTP traffic; Increasing the speed of processing Layer 4 traffic; Relaying DHCP traffic
If the virtual servers are not able to manage the traffic and divert client requests to servers that are managing fewer requests, poor performance and outages cannot be avoided. Also, irregularities in load balancing can cause significant delay in request processing thus affecting the user experience with the load balancer. To avoid this, you can configure the periodic execution of the LBL4VSTest test.
For each virtual server configured on the target load balancer, this test continuously monitors the load on the load-balancing virtual servers and reveals how well each virtual server processes client requests. In addition, this test detects inconsistencies in load-balancing early on and warns administrators of possible deviations proactively.
Outputs of the test : One set of results for each Virtual server on the target load balancer being monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| rsCount |
Indicates the number of real servers associated with this virtual server. |
Number |
The detailed diagnosis of this measure lists the name of the real server associated with the virtual server and the IP address through which the real server was connected to the virtual server. |
| curCon |
Indicates the number of connections handled by this virtual server during the last measurement period. |
Number |
This measure is a good indicator of load on the virtual server. |
| vsInPkt |
Indicates the number of packets received by this virtual server during the last measurement period. |
Number |
Compare the value of this measure across the virtual servers to figure out the virtual server that is receiving the maximum number of packets. |
| vsOutPkt |
Indicates the number of packets transmitted by this virtual server during the last measurement period. |
Number |
Compare the value of this measure across the virtual servers to figure out the virtual server that is transmitting the maximum number of packets. |
| vsInData |
Indicates the amount of data received by this virtual server during the last measurement period. |
KB |
Compare the value of this measure across the virtual servers to figure out the virtual server that is receiving the maximum amount of data. |
| vsOutData |
Indicates the amount of data transmitted by this virtual server during the last measurement period. |
KB |
Compare the value of this measure across the real servers to figure out the virtual server that is transmitting the maximum amount of data. |
| vsInPktRate |
Indicates the rate at which packets were received by this virtual server. |
Packets/sec |
|
| vsOutPktRate |
Indicates the rate at which packets were transmitted by this virtual server. |
Packets/sec |
|
| vsInDataRate |
Indicates the rate at which data was received by this virtual server. |
KB/sec |
|
| vsOutDataRate |
Indicates the rate at which data was transmitted by this virtual server. |
KB/sec |
|
|