Configuration of PureVolPerfTest

For users to be able to read from/write data into volumes quickly, adequate space must be available in the volumes and the I/O requests should be processed rapidly by the volumes. Slowdowns in data storage/retrieval can be attributed to storage space contentions experienced by one/more volumes or I/O processing bottlenecks. In the event of such slowdowns, administrators need to swiftly isolate the following:

• Which volumes are over-utilized?

• Which volumes are overloaded?

• Which volumes are experiencing serious latencies?

• When were these latencies observed most frequently - while reading or writing?

The PureVolPerfTest test provides accurate answers to these questions. With the help of these answers, you can quickly diagnose the root-cause of slowdowns when reading from/writing into a volume.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, specify the port at which the specified host listens to. By default, this is set to 9736.

• The eG agent collects the required metrics from the Pure Storage FlashArray by executing API commands using Pure Storage REST API on the FlashArray and pulls out critical metrics. In order to collect metrics, the eG agent should be provided with a valid API token. To know how to determine the API token, do the following:

  • Login to the Purity GUI as a user with administrator privileges.

  • Then, navigate to the System tab and click on the Users -> API Tokens. The API Tokens page will be displayed in the context-sensitive right panel. The API Tokens page displays a list of all users with API tokens and the dates on which the API tokens were created.

  • To view the API token of the created user, right click on that user. A drop-down list will appear next. Clicking the Show API Token option in that list reveals the API Token generated for the created user in a separate pop up window.

  • Copy this API token and specify the same in the API TOKEN text box while configuring the tests.

  Specify the determined API token in the API TOKEN text box.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.