eG Monitoring
 

Measures reported by A10ServerPortTest

When client requests are sent to the real servers from the Virtual IP of the A10 Application Delivery Controller, the ports at the real servers receive such requests. If the ports are not available or if the ports are already processing too many requests, then the newer client requests may have to wait resulting in poor load balancing capabilities of the A10 Application Delivery Controller. To avoid such discrepancies, it is essential to monitor the current state and the client requests processing statistics of each port on the real servers. This is where the A10ServerPortTest test helps!

For each port of the real server configured on the A10 Application Delivery Controller, this test continuously monitors the current state of the port and reveals how well each port processes client requests.This way, administrators can detect inconsistencies in load-balancing early on and proactively take remedial measures before end users start complaining.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Port_status Indicates current state of this port of the real server.   The values of this measure and their corresponding numeric values are listed below:

Measure Value Numeric Value
Disabled 0
Up 1
Down 2

Note:

By default, this measure reports one of the Measure Values listed in the table above to indicate current state of this port of the real server. In the graph of this measure however, the port status will be represented using the numeric equivalents.
Data_transmitted Indicates the rate at which data was transmitted through this port during the last measurement period. MB/Sec Compare the value of these measures across the ports to identify the port that is experiencing the maximum traffic.
Data_received Indicates the rate at which data was received by this port during the last measurement period. MB/Sec
Packets_transmitted Indicates the rate at which the packets were transmitted through this port during the last measurement period. Packets/Sec Compare the value of these measures across the ports to identify the port that is experiencing the maximum load.
Packets_received Indicates the rate at which packets were received by this port during the last measurement period. Packets/Sec
Curr_connections Indicates the number of active connections that were established through this port. Number This measure is a good indicator of the load on the real server.
Tot_connections Indicates the total number of connections established this port since the start of the A10 Application Delivery Controller. Number  
Connection_rate Indicates the rate at which the connections were established through this port during the last measurement period. Conns/Sec A sudden increase in the value of this measure indicates an increase in the traffic handled by the port of the real server.
Conn_usage Indicates the percentage of active connections that were established through this port. Percent A value close to 100% indicates that the traffic through the port is abnormally high.

Compare the value across the ports to identify the port thorugh which the maximum number of connections were established.
Persistent_conns Indicates the number of connections that were persistent on this port. Number TCP connections that are kept open after transactions complete are called persistent connections. Persistent connections stay open across transactions, until either the client or the server decides to close them. These connections when reused can significantly rediuce the traffic overload on the port.
Peak_conns Indicates the maximum number of connections that were established through this port to the real server since the start of the A10 Application Delivery Controller. Number  
Curr_L7_requests Indicates the number of L7 requests currently processed through this port. Number Both these measures serve as effective pointers to the L7 requests processing in the A10 Application Delivery Controller.

Layer-7 load balancing, also known as application-level load balancing, is to parse L7 requests in application layer and distribute L7 requests to the servers based on different types of request content, so that it can provide quality of service requirements for different types of content and improve overall performance of the A10 Application Delivery Controller.
Tot_L7_requests Indicates the rate at which the L7 requests were processed through this port. Requests/Sec
Succ_L7_requests Indicates the number of L7 requests that were processed successfully through this port. Number Ideally, value of this measure should be high.