XClarity Fuel Gauge Status Test

The Fuel Gauge component in Lenovo XCalrity Controller is to manage the power supply for the server or group of servers managed by XClarity Controller. It controls server power usage and configure server power management. Fuel Gauge can be accessed from XClarity Command Line INterface (CLI) using command fuelg. You can control various important power management function using fuel gauge like enable/disable power management and capping on the server, set the power capping mode, get power consumption and performance history, set policy mode for loss of redundant power, get current power consumption etc.

Given that fuel gauge controls the entire power supply to controller and the server, it is really important to monitor the Fuel Gauge so that any issue with it can be investigated and understood at the earliest and fixed before the server power supply is affected.

This test auto discovers the Fuel Gauge and reports key statistics like current power usage by controller, remaining power, CPU and memory consumption etc.

Target of the test : A Lenovo XClarity Controller

Agent deploying the test : An external agent

Outputs of the test : One set of results for each XClarity Controller

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the target server that is being monitored.


The port at which the monitored target exposes its SNMP MIB;

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.


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.


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.


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.


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. 


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
  • SHA224 - Secure Hash Algorithm 224 bit
  • SHA256 - Secure Hash Algorithm 256 bit
  • SHA384 - Secure Hash Algorithm 384 bit
  • SHA512 - Secure Hash Algorithm 512 bit


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 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


Specify the encryption password here.


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

Total power in use

Indicates the total power in use by controller during the last measurement period.


The value of total power in use should be within the operating range, if it is out the range over multiple measurements there may be some issue with controller.

Total power available

Indicates the total power available with the controller during the last measurement period.


Available power is a good indicator of health of controller.

Power remaining

Indicates the total power available with the controller during the last measurement period.


Adequate power remaining is the indicator of efficient functioning of controller, if it is not adequate , you need to look into it.

CPU Power Consumption

Indicates the amount of power being consumed by controller CPU during the last measurement period.


Gives a clear indication of where the power is being consumed, if it is CPU, Memory or other entities. Anywhere if you feel the consumption is more than expected, you can start investigating,



Memory Power Consumption

Indicates the amount of power being consumed by controller memory during the last measurement period.


Other entities power consumption

Indicates the amount of power being consumed by other entities in the controller during the last measurement period.