OceanStor Node Statistics Test
This test auto-discovers the nodes on the Huawei OceanStor, and reports the bandwidth usage of each node. With the help of this test, administrators can not only identify overloaded nodes, but can also predict the potential failure of the node, so that efforts can be undertaken to avert the same. In addition, the test also points administrators to the nodes that are handling more I/O requests than the rest, thus shedding light on irregularities in the distribution of I/O requests across nodes.
Target of the test: Huawei OceanStor
Agent deploying the test: A remote agent
Outputs of the test: One set of results for each node in the Huawei OceanStor that is being monitored.
Descriptor: Node
|
Parameter |
Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The IP address of the target host to be monitored. |
|
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; the default value is 161. |
|
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. |
|
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. |
|
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 switch. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear. |
|
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. |
|
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. |
|
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:
|
|
EncryptFlag |
This flag appears only when v3 is selected as the SNMPVersion. By default, the eG agent does not encrypt SNMP requests. Accordingly, 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:
|
|
EncryptPassword |
Specify the encryption password here. |
|
Confirm Password |
Confirm the encryption password by retyping it here. |
|
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. |
|
Measurement |
Description |
Measurement Unit |
Interpretation |
|---|---|---|---|
|
CPU utilization |
Indicates the percentage of CPU utilized in this node. |
Percent |
A low value is desired for this measure. |
|
Average cache utilization |
Indicates the percentage of average cache usage of this node. |
Percent |
|
|
Average IO latency |
Indicates the average I/O latency of this node. |
Milliseconds |
A very high value indicates the inability of the nodes to process requests quickly. This could be because the nodes are not configured with adequate space. You may want to consider resizing the nodes to ensure better I/O throughput. |
|
Read IOPS |
Indicates the rate of read I/O operations performed currently on this node. |
Operations/sec |
If the value of the Total IOPS measure is unusually high, then compare the value of Read IOPS and Write IOPS measures to know what is contributing to the unusual I/O activity levels - read requests? or write requests? |
|
Write IOPS |
Indicates the rate of write I/O operations performed currently on this node. |
Operations/sec |
|
|
Total IOPS |
Indicates the rate of I/O operations performed currently on this node. |
Operations/sec |
This measure is a good indicator of the level of I/O activity on each node. A steady and significant increase in the value of this measure could indicate a potential I/O overload. In such situations, you may want to compare the value of the Read IOPS and Write IOPSmeasures to know what type of IO operations are contributing to the overload. |
|
Read bandwidth |
Indicates the rate of bandwidth used by this node when processing read requests. |
MB/Sec |
If the value of the Total bandwidth measure is high, then you may want to compare the value of the Read bandwidth and Write bandwidth measures to know what type of requests are truly contributing to the excessive bandwidth consumption - read requests? or write requests? |
|
Write bandwidth |
Indicates the rate of bandwidth used by this node when processing write requests. |
MB/Sec |
|
|
Total bandwidth |
Indicates the bandwidth per second used by this node when processing requests. |
MB/Sec |
A high value for this measure denotes that the node is processing bandwidth-intensive requests. In such situations, you may want to compare the value of the Read bandwidth and Write bandwidthmeasures to know what type of requests are truly contributing to the excessive bandwidth consumptions - read requests? or write requests? |
|
File bandwidth |
Indicates the rate of file bandwidth for this node. |
Bytes/sec |
|
|
File operations |
Indicates the rate of file operations on this node. |
Operations/sec |
|
