SolidFire Paired Clusters Test

You can use real-time replication (remote replication) functionality to connect (pair) two clusters and enable continuous data protection (CDP). When you pair two clusters, active volumes on one cluster can be continuously replicated to a second cluster to provide data recovery ability. Once the connection between two clusters has been established, you can identify volumes as being the source or target of the replication. Cluster pairing requires full connectivity between nodes on the management network. Replication requires connectivity between the individual nodes on the storage cluster network. Whenever connection between the paired clusters is down or if the connection is not configured properly, the replication of data may fail. This may cause severe data loss if failure is detected in the source SolidFire Cluster due to reasons such as damage, faults etc. To avoid such data loss, it is essential to keep track on the connectivity between the paired SolidFire Clusters. The SolidFire Paired Clusters test helps administrators in this regard!

This test auto-discovers the SolidFire Clusters that are paired with the target SolidFire Cluster, and for each paired SolidFire Cluster, this test reports the current connection status and the time taken for the target SolidFire Cluster to synchronize the data. Using this test, administrators can figure out the paired SolidFire Cluster that is slow to synchronize the data.

Target of the test : A SolidFire Storage

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each SolidFire Cluster that is paired to the target storage device.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

The port at which the server listens.

SolidFire API Version

Specify the API version of the SolidFire storage system to be monitored.

SolidFire Username and SolidFire Password

Provide the credentials of a user who has been assigned with a Monitor role to access the SolidFire storage system in the SolidFire Username and SolidFire Password text boxes.

Confirm Password

Confirm the SolidFire Password by retyping it here.

Detailed diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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. 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

Status

Indicates the current connection state of this SolidFire cluster that is paired with the target SolidFire Cluster.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Connected 1
Misconfigured 2
Disconnected 3

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of this SolidFire Cluster. The graph of this measure is however, represented using the numeric equivalents only i.e., 1 to 3.

Latency

Indicates the time taken by the target SolidFire Cluster to transfer the data to the SolidFire Cluster that is paired.

Milliseconds

This measure appears only if the Status measure displays the Connected state.

A high value for this measure indicates that the data synchronization is slower.

Comparing the value of this measure against all the paired clusters would reveal the paired cluster that is slow in data synchronization.