HP 3PAR Ports Test

Storage ports help the controllers receive and process I/O requests. By periodically checking port status and measuring the I/O load on the ports, you can identify overloaded ports and thus proactively detect potential/existing load-balancing irregularities and/or processing bottlenecks with the ports. The HP 3PAR Ports test facilitates this port check. For every port configured for the controllers supported by the Storage system, this test reports the port state, the I/O load on the ports, and the processing ability of the ports. In the process, the test not only points administrators to overloaded ports, but also puts a finger on ports that are slow when processing I/O requests.

Target of the test : A HP 3PAR Storage system

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each storage port on the HP 3PAR Storage system.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the Storage system.

Port

The port number at which the Storage system listens. The default is NULL.

User and Password

Specify the credentials of a user who has the right to execute API commands on the storage device and pull out metrics. To monitor the HP 3PAR Storage system,  you will have to provide the credential of a user who has been assigned the Browse role. To know how to create a user with Browser role, refer to How to Create a New User with Browser Role?

Confirm Password

Confirm the password by retyping it here.

SSL

Set this flag to True, if the storage system being monitored is SSL-enabled. By default this flag is set to False.

Using REST API

By default, this flag is set to False indicating that the eG agent by default, executes CIM API commands on the target storage server to collect the required metrics. However, to collect the required metrics from an SSL-enabled HP 3PAR Storage server, the eG agent is required to execute REST API commands on the target storage server. To enable the eG agent to execute REST API commands, set this flag to True.

IsEmbedded

This flag is not applicable when you set the Using REST API flag to True. By default, the target HP 3PAR Storage system is embedded within the storage platform. Therefore, this flag is set to True, by default.

Serial Number

If the SMI-S provider has been implemented as a proxy, then such a provider can be configured to manage multiple storage devices. This is why, if the IsEmbedded flag is set to False, you will have to explicitly specify which storage system you want the eG agent to monitor. Since each storage system is uniquely identified by a Serial Number, specify the same in this text box. The format of this number and where you can find it will differ from one storage system to another. You are hence advised to contact the storage administrator to know what to enter against this parameter. For example, the serial number for a HP 3PAR Storage system can be:16990.

CIM Server Port

This parameter is not applicable when you set the Using REST API flag to True. The SMI–S provider of the HP 3PAR Storage system provides access for monitoring and management via the HTTP and HTTPS protocols for CIM API request/response semantics. To enable the eG agent to access the SMI-S Provider, invoke the CIM API commands, and collect the required metrics, you need to specify the service port on the SMI- S provider in the CIM Server Port text box that listens for HTTP/HTTPS requests for CIM API semantics. By default, this is port 5988. If the service port on the SMI-S Provider listens only to HTTPS requests, then specify the port as 5989.

Jar

This flag is not applicable when you set the Using REST API flag to True. By default, this test uses the wbem.jar for metrics collection. This is why, the wbem option is selected by default. If you want the test to use the sblimCIMClient.jar for collecting metrics, choose the sblim option here.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Health state

Indicates how healthy this port currently is.

 

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

Numeric Value Measure Value
0 OK
1 Unknown
2 Degraded/Warning
3 Minor failure
4 Major failure
5 Critical failure
6 Non-recoverable error

Note:

By default, this measure reports the Measure Values discussed above to indicate the state of a port. In the graph of this measure however, states are represented using the numeric equivalents only.

Operational status

Indicates the current operational state of this port.

 

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

Numeric Value Measure Value
0 OK
1 In Service
2 Power Mode
3 Completed
4 Starting
5 Dormant
6 Other
7 Unknown
8 Stopping
9 Stressed
10 Stopped
11 Supporting Entity in Error
12 Degraded or Predicted Failure
13 Predictive Failure
14 Lost Communication
15 No Contact
16 Aborted
17 Error
18 Non-Recoverable Error

Note:

By default, this measure reports the Measure Values discussed above to indicate the operational state of a port. In the graph of this measure however, operational states are represented using the numeric equivalents only.

Detailed operational status

Describes the current operational state of this port.

 

This measure will be reported only if the API provides a detailed operational state.

Typically, the detailed state will describe why the port is in a particular operational state. For instance, if the Operational status measure reports the value Stopping for a port, then this measure will explain why that port is being stopped.

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

Numeric Value Measure Value
0 Online
1 Success
2 Power Saving Mode
3 Write Protected
4 Write Disabled
5 Not Ready
6 Removed
7 Rebooting
8 Offline
9 Failure

Note:

By default, this measure reports the Measure Values discussed above to indicate the detailed operational state of a port. In the graph of this measure however, detailed operational states are represented using the numeric equivalents only.

Data transmitted

Indicates the rate at which data was transmitted by this port.

MB/Sec

 

IOPS

Indicates the rate at which I/O operations were performed on this port.

IOPS

Compare the value of this measure across ports to know which port handled the maximum number of I/O requests and which handled the least. If the gap between the two is very high, then it indicates serious irregularities in load-balancing across ports.