PacketShaper Link Data Test

PacketShaper's access-link monitoring feature allows PacketShaper to deal with this "imperfect" load-balancing issue and has the ability to respond to the occurrence of WAN link failure. When access-link monitoring is enabled, PacketShaper can adjust partitions appropriately to prevent overloading any given WAN link and to account for lost available capacity due to router or link failure.

In order to optimize bandwidth usage, minimize traffic congestions, and maximize the speed of WAN links, administrators need to define the WAN links requiring traffic acceleration in the PacketShaper Load Balancer, set the bandwidth limit for each of the links for receiving/sending data, and associate each link with traffic shaping policies. But, once the configuration is complete, it is essential for the administrators to test the correctness of the configuration. For this, administrators can use the PacketShaper Link Data test. For each WAN link configured in the target load balancer, this test reports real-time metrics of the volume of traffic handled by the link and data retransmissions over the link. This way, the test reveals those links that are candidates for fine-tuning, owing to their low throughput despite the traffic shaping and acceleration rules that apply to them.

Target of the test : PacketShaper Load Balancer

Agent deploying the test : An external agent

Outputs of the test : One set of the results for each WAN link configured on the target PacketShaper Load Balancer that is being monitored

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The IP address of the target load balancer 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. 

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

Link rate

Indicates the rate at which the data is currently transmitted over this link.

Kbps

 

Link size

Indicates the current bandwidth size of this link.

Kbps

 

Low order data count

Indicates the total amount of low order data transmitted over this link during the last measurement period.

KB

 

High order data count

Indicates the total amount of high order data transmitted over this link during the last measurement period.

KB

 

Transmitted low order data

Indicates the amount of low order data without the dropped bytes transmitted over this link during the last measurement period.

KB

 

Received low order data

Indicates the amount of low order data excluding the dropped bytes received over this link during the last measurement period.

KB

 

Transmitted high order data

Indicates the amount of high order data without the dropped bytes transmitted over this link during the last measurement period.

KB

 

Received high order data

Indicates the amount of high order data without the dropped bytes that was received over this link during the last measurement period..

KB

 

Retransmitted low order data

Indicates the amount of low order data retransmitted over this link during the last measurement period.

KB

 

Retransmitted high order data

Indicates the amount of high order data retransmitted over this link during the last measurement period.

KB

 

Non compressed data

Indicates the amount of non-compressed data transferred by this partition during the last measurement period.

KB

 

High order non compressed data

Indicates the amount of high order non-compressed data transmitted over this link during the last measurement period.

KB

 

Received data before compression

Indicates the amount of data received over this link before compression during the last measurement period.

KB

 

Received high order data before compression

Indicates the amount of high order data received over this link before compression during the last measurement period.

KB

 

Received data after compression

Indicates the amount of data received over this link after compression during the last measurement period.

KB

 

Received high order data after compression

Indicates the amount of high order data received over this link after compression during the last measurement period.

KB