EQ Controllers Test

The Dell EqualLogic PS Series supports dual controllers, which are redundant and hot-swappable. The controller module features dual-core 64-bit processors with a HyperTransport™ I/O bus and twin 64-bit double data rate (DDR) channels. Each control module is equipped with 1GB of battery-backed DRAM.

To ensure that the controllers are functioning properly, the temperature of their processors and the strength of their battery backups should be periodically checked so that, abnormalities can be quickly detected and fixed. This test auto-discovers the available controllers in the PS Series array, and reports the above for each controller. In addition, this test also reveals which of the controllers is the primary controller in the redundant setup, and which is the secondary.

Target of the test : Dell EqualLogic PS Series SAN

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each available controller in the storage device 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
  • SHA224 - Secure Hash Algorithm 224 bit
  • SHA256 - Secure Hash Algorithm 256 bit
  • SHA384 - Secure Hash Algorithm 384 bit
  • SHA512 - Secure Hash Algorithm 512 bit

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

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.

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

Battery status

Indicates the current status of the battery present in this controller.

 

This measure reports one of the following values as the state of the battery present in a controller:

  • Ok
  • Failed
  • Good Battery
  • Low Voltage
  • Low Voltage Charging
  • Missing Battery

The numeric values that correspond to the above-mentioned states are as follows:

State Numeric Value
Ok 1
Failed 2
Good Battery 3
Low Voltage 4
Low Voltage Charging 5
Missing Battery 6

Note:

By default, this measure reports the above-mentioned states while indicating the state of the battery present in a controller. However, in the graph of this measure, battery states will be represented using their corresponding numeric equivalents - i.e., 1 - 6.

Total uptime

Indicates the time that elapsed since this controller was last booted.

Secs

By carefully observing the changes in the measure, you can promptly detect unexpected breaks in the availability of the controller.

Processor temperature

Indicates the current temperature of the processor supported by this controller.

Celsius

Ideally, this value should be low.

Chipset temperature

Indicates the current temperature of the chipset supported by this controller.

Celsius

A low value is desired for this measure.

Controller status

Indicates whether the controller is the primary controller or the secondary.

 

This measure reports the value Primary or Secondary depending upon whether the controller is the primary controller or the secondary controller in the redundant setup.  

The numeric values that correspond to the above-mentioned states are as follows:

State Numeric Value
Primary 1
Secondary 2

Note:

By default, this measure reports the above-mentioned States while indicating the status of the controller. However, the graph of this measure will be represent states using the corresponding numeric equivalents - 1 or 2 only.