Dell Compellent 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 Dell Compellent Ports test facilitates this port check. For every port configured for the controllers supported by the Storage Center, 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 Dell Compellent Storage Center

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each storage port on the Dell Compellent Storage Center.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The storage device for which the test is to be configured.

Port

The port number at which the specified storage device listens to. By default, this will be NULL.

User and Password

Specify the credentials of a user who has the right to execute API commands on the Dell Compellent Storage Center and pull out metrics. The specified user is the Pegasus CIM User who should possess Administator privileges and should be associated with the Logon as a Service policy. 

Confirm Password

Confirm the password by retyping it here.

SSL

Set this flag to Yes, if the storage device being monitored is SSL-enabled.

CIM Server Port

The SMI–S provider of the Dell Compellent Storage Center 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.

IsEmbedded

If this flag is set to True, it indicates that the SMI-S Provider is embedded on the Storage Center. On the other hand, if this flag is set to False, it indicates that the SMI-S Provider has been implemented as a proxy.

SerialNumber

If the SMI-S Provider has been implemented as a proxy, then such a provider can be configured to manage multiple Storage Centers. This is why, if the IsEmbedded flag is set to False, you will have to explicitly specify which Storage Center you want the eG agent to monitor. Since each Storage Center is uniquely identified by a serial number, specify the same in the SerialNumber text box.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against Detailed Diagnosis. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
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.

 

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.