Default Parameters for PureRepArrTest

The FlashArray enables connecting two arrays to provide high availability and data protection, and to prevent single point of failure. When the arrays are connected, the array where the data is being transferred from is called the source array, and the array where data is being transferred to is called the target array. After two arrays are connected, the target array must allow the connection from the source array to accept the data being transferred. If the connection is not established or lost between the arrays, the data will not be transferred to the target array. The very purpose of the high availability and data protection of the arrays may therefore, be defeated. To prevent such eventualities, administrators should continuously monitor the connection status between the source and target arrays. To achieve this, administrators can use the PureRepArrTest test.

This page depicts the default parameters that need to be configured for the PureRepArrTest test.

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

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

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.