PowerEdge Temperature Test

Temperature probes in the VRTX system are configured with threshold values, which when violated, automatically increases the speed of the corresponding fans, so that temperatures never rise beyond a permissible limit. In the absence of these temperature probes, such automated cooling actions will not occur, causing the internal temperature of the VRTX to soar uncontrollably, fatally damaging hardware components in the process. This is why, it is important that administrators periodically check that the temperature probes are up and operating without a glitch. 

Also, the threshold values defined for each of the temperature probes may have to be fine-tuned from time to time, so that the fan speed is changed only when there is a genuine need and not for marginal spikes in temperature. For this, the administrator should keep track of the temperature probe readings over time, understand whether/not that reading is good or bad as per the current threshold definition, and accordingly make changes (if required) to the configuration.

The PowerEdge Temperature test helps achieve both these ends. This test auto-discovers the temperature probes, reports the current status of each probe, reveals the current temperature reading of that probe, and indicates whether that reading is good or bad. This way, the test alerts administrators to unexpected probe failures and urges them to instantly initiate corrective action and restore normalcy. Additionally, the test also helps administrators quickly analyze the current temperature reading of a probe vis-a-vis its threshold setting, and thus helps them figure out whether the thresholds need to be refined or not.

Target of the test : A Dell PowerEdge VRTX

Agent deploying the test : An external agent

Outputs of the test : One set of results for each temperature probe n the VRTX being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

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

Port

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

SNMPPort

The port at which the monitored target exposes its SNMP MIB; The default value 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

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

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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Health status

Indicates how healthy this temperature probe currently is.

 

The values that this measure can report and their corresponding numeric values are discussed below:

Measure Value Numeric Value
Other 1
Unknown 2
Normal 3
NonCritical Upper 4
Critical Upper 5
NonRecoverable Upper 6
NonCritical Lower 7
Critical Lower 8
NonRecoverable Lower 9
Failed 10

Note:

By default, this measure reports one of the Measure Values listed above to indicate the current health of a temperature probe. In the graph of this measure however, the same is represented using the numeric equivalents only.

Temperature

Indicates the current temperature reading of this probe.

DegreeC

This measure reports values, only if the temperature probe is of a type other than ‘GenericDiscrete’.

A sudden and a significant rise in temperature may require closer scrutiny.

Temperature status

Indicates whether the temperature recording of this probe is good or bad.

 

 

The values that this measure can report and their corresponding numeric values are discussed below:

Measure Value Numeric Value
Good 1
Bad 2

Note:

By default, this measure reports one of the Measure Values listed above to indicate the current temperature status of a probe. In the graph of this measure however, the same is represented using the numeric equivalents only.

This measure reports values, only if the temperature probe is of a type other than ‘GenericDiscrete’.