Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.futurex.com/llms.txt

Use this file to discover all available pages before exploring further.

This section provides guidance on ongoing RDL operations.

​
General notes for KMIP configurations

The following notes apply to KMIP:
  • You can only delete a certificate when no KMIP server uses it. Use the KMIP server to determine if it is in use through CryptoHub. The purecert command does not include information on whether a certificate is in use.
  • Currently, you cannot rename a KMIP server or a certificate used with a KMIP server.

​
How to block access to the FlashArray

If you need to block access to FlashArray data immediately, perform one of the following steps and then either power down the FlashArray or restart Purity:
  • On the KMIP server (CryptoHub), revoke the TLS certificate used for communication with the FlashArray. You can recover later by redoing the certificate setup steps.
  • On the KMIP server (CryptoHub), delete the secret key used for communication with the FlashArray. You cannot recover FlashArray data after this step. Use this process only to make the array data permanently inaccessible.
These steps do not block data availability until you restart Purity or power off the array.
All data on the FlashArray might become inaccessible if any of the following events happen after RDL is enabled on the array.
  • The KMIP server is removed or is not accessible.
  • The certificate used with the KMIP server expires.
In these cases, you see an alert, but data remains accessible until the next Purity restart or failover.