Hitachi Chassis Status Test

The Hitachi Compute Blade consists of a robust, fully-redundant 6U chassis i.e. 19-inch rack compatible. The chassis can house up to eight multi-core 2-socket processor half-wide blades or four multi-core 4-socket processor full-wide blades. The chassis is provided with hot-swappable management modules, switch modules, power supply modules and fan modules. These modules provide continuous management, network connectivity, power supply and cooling services to the blades.

Built-in logical partitioning, a key feature of Hitachi Compute Blade 500 complements existing software-based virtualization solutions and can be used in conjunction with VMware, Hyper-V or Red Hat KVM. These multiple virtualization platforms can be combined in a single chassis and can be configured to share the same physical resources. For these virtualization platforms to function without a glitch, it is essential that the chassis on which the physical resources are available should be operational round the clock. Frequent power failures, voltage and temperature fluctuations may damage the chassis resulting in the failure of the virtual platforms. Therefore, it is mandatory for the administrators to keep a constant vigil on the power supply, voltage and temperature of the chassis. This is exactly where the Hitachi Chassis Status test helps!

Using this test, administrators can determine the current power supply status of the chassis, the current temperature and voltage of the chassis as well as be proactively alerted if the chassis is under maintenance! This way, administrators can be alerted to abnormalities in the temperature and voltage of the chassis and rectify the same before end users utilizing the virtualized solutions provisioned from the Hitachi Compute Blade are not put into terrible hardship!

Target of the test : Hitachi Compute Blade

Agent deploying the test : An external agent

Outputs of the test : One set of results for the chassis on 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. authpassSpecify 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

PowerSupply status

Indicates the power supply status of the chassis.

 

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 power status of the chassis. However, the graph of this measure is indicated using the numeric equivalents.

Current voltage

Indicates the current voltage of the chassis.

Volts

A sudden / gradual rise in the value of this measure is a cause of concern.

Power consumption

Indicates the amount of power consumed by the chassis.

Amps

 

Temperature

Indicates the current temperature status of the chassis.

 

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

Higher Warning

2

Higher Error

3

Lower Warning

4

Lower Unknown

5

Note:

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

Maintenance mode

Indicates the current maintenance mode of the chassis.

 

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

CE Maintenance Mode

2

User Maintenance Mode

3

Unknown

4

Note:

By default, this measure can report the Measure Values mentioned above while indicating the current maintenance mode of the chassis. However, the graph of this measure is indicated using the numeric equivalents.