Fuel Gauge Test

To manage the power consumption of the components of the target chassis and provide power redundancy during failures, administrators create two power domains using the advanced management module Web interface. Each power domain is allocated with a specific amount of power which will be shared among the chassis components. The chassis components in each power domain are grouped based on their types and estimated power consumption. The power domains should be able to supply the adequate amount of power to power-on and ensure smooth functioning of the chassis components such as blade servers. If the power domains run out of the allocated power, the chassis components may start to malfunction or shut-down completely, which in turn stalls the operations of the target chassis. To avoid such eventualities, administrators should be alerted to the power shortage immediately before the chassis operations shut down. This can be easily done using the Fuel Gauge test!

This test auto-discovers the power domains on the target chassis and for each power domain, reports the current status and power utilization, thus turning the spotlight on the power domain that is being over-utilized.

Target of the test : An IBM BladeCenter Chassis

Agent deploying the test : An external agent

Outputs of the test : One set of results for each power domain in the BladeCenter chassis being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which this test is to be configured.


The port at which the device listens. By default, this will be NULL.


The port at which the monitored target exposes its SNMP MIB; The default value is 161.


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.


The SNMP community name that the test uses to communicate with the target host. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear.


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. 


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.


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.


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


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. 


If this 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
  • AES – Advanced Encryption Standard


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates the current status of this power domain.


The values that this measure can report and the numeric values they indicate have been listed in the table below:

Measure Value Numeric Value
Good 1
Warning 2
Bad 3


By default, this measure can report the Measure Values mentioned above while indicating the current status of each power domain. However, the graph of this measure is indicated using the numeric equivalents.

Total available power

Indicates the total amount of power that is available in this power domain.


Total power is calculated by the management module according to the rated capacities of the power modules that are installed in each power domain and the power-management policy that has been set for each power domain.

Reserved power

Indicates the amount of power reserved for use by the components in this power domain.



Available remaining power for use

Indicates the amount of power that is available for use in this power domain.


The value of this measure is calculated according to the Total available power and the Reserved power measures for each power domain.

Power in used

Indicates the amount of power that is being used in this power domain.


If the value of this measure is close to the value of the Total available power measure, it is a cause for a concern.

Comparing the value of this measure across the power domains can help you instantly identify the power domain that is being over-utilized.

Remaining power to be utilized

Indicates the percentage of power that is available for use in this power domain.