Buffer Pool Statistics Test

This test monitors the memory allocation within Cisco ASR Router. The usage of the buffer memory and its size are tracked and reported through this test. This test also helps the administrators to monitor the failure of buffer creation.

Target of the test : A Cisco ASR Router

Agent deploying the test : An external agent

Outputs of the test : One set of results for each Buffer pool in the target Cisco ASR Router.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
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 the Username 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
Buffer size	Indicates the current size of this buffer pool.	MB	A well-tuned environment is the one where this buffer should be sufficiently sized. A low value of this measure is always unhealthy.
Number of buffers	Indicates the number of buffers in this buffer pool.	Number	It includes both the allocated and free buffers.
Free buffer	Indicates the number of unused buffer in this buffer pool.	Number
Buffer allocation hits	Indicates the number of buffers allocated to this buffer pool.	Number	A very low value could indicate that many allocations have failed owing to lack of adequate buffers. If the measure repeatedly reports low values, it could be indicative of memory bottleneck in the router.
Buffer allocation misses	Indicates the number of times buffer could not be allocated from this buffer pool.	Number	Ideally the buffer miss count should be 0. Repeated buffer misses indicate memory bottleneck in the router.
Buffer creation failed	Indicates the number of times the new buffers could not be created in this buffer pool.	Number	A low value is desired for this measure.
Buffers used	Indicates the number of used buffer space in this buffer pool.	Number
Buffer utilization	Indicates the percentage of buffer used currently in this buffer pool.	Percent	If the buffer size is less, then for many requests the buffer cannot be used leading to more swapping; therefore the buffer size needs to be increased.