Hitachi Fan Modules Test

The cooling of the Hitachi Compute Blade is governed by six efficient, variable-speed, redundant fan modules. Each fan module includes three fans to tolerate fan failures within a module; an entire module can fail while the other fan modules continue to support the cooling requirements of the chassis. If the fan modules fail frequently, then the cooling of the hardware components of the Hitachi Compute Blade may fluctuate leading to abnormal rise in temperature. This may sometimes cause a permanent damage of the Hitachi Compute Blade. To avoid such critical damage, administrators should constantly monitor the health of the fan modules. The Hitachi Fan Modules test comes in handy to those administrators who would like to monitor the fan modules round the clock!

This test reports the current health of each fan module in the chassis, thus turning the spotlight on those modules that have failed. In addition, the test also checks the status of the power supply to each fan module and also alerts administrators to the redundancy status of each fan module.

Target of the test : Hitachi Compute Blade

Agent deploying the test : An external agent

Outputs of the test : One set of results for each fan module in the Hitachi Compute Blade being monitored.

Configurable parameters for the tests
  1. TEST PERIOD - How often should the test be executed
  2. Host – The IP address of the Hitachi Compute Blade.
  3. SnmpPort – The port at which the Hitachi Compute Blade exposes its SNMP MIB; the default is 161.
  4. 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.
  5. 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.
  6. 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. 
  7. 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.
  8. authpass– Specify the password that corresponds to the above-mentioned username. This parameter once again appears only if the snmpversion selected is v3.
  9. confirm password– Confirm the authpass by retyping it here.

  10. 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
  1. encryptflag– This flag appears only when v3 is selected as the snmpversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the encryptflagis set to no by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the yes option. 

  2. 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
  3. encryptpassword – Specify the encryption password here.
  4. confirm password – Confirm the encryption password by retyping it here.
  5. TIMEOUT - Specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 seconds.
  6. 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 the data over tcp flag to Yes. By default, this flag is set to No.
  7. 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
Health status

Indicates the current health of this fan module.

 

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

Measure Value Numeric Value

Normal

 1

Failed

 2

Unknown

 0

Note:

By default, this measure can report the Measure Values mentioned above while indicating the health of each fan module. However, the graph of this measure is indicated using the numeric equivalents.
PowerSupply status

Indicates the current power supply status of this fan module.

 

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

Measure Value Numeric Value

PowerOff

 1

Standby

 2

PowerOn

 3

Unknown

 4

PowerOn Executing

 5

PowerOff Executing

 6

Note:

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

Indicates the current redundancy status of this fan module.

 

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

Mode Numeric Value

Redundancy

 1

Non Redundancy

 2

Unknown

 3

Note:

By default, this measure can report the Modes mentioned above while indicating the redundancy status of each fan module. However, the graph of this measure is indicated using the numeric equivalents.