Recover inaccessible or invalid authentication keys
PDF of this doc site
- Install and maintain hardware
Manage storage with Element software
Manage your system
- Configure cluster settings
- Manage volumes and virtual volumes
Protect your data
- Use volume snapshots for data protection
- Perform remote replication between clusters running NetApp Element software
- Use SnapMirror replication between Element and ONTAP clusters
- Manage your system
- Manage and monitor storage with NetApp Hybrid Cloud Control
- Manage storage with Element API
- Work with the management node
Occasionally, an error can occur that requires user intervention. In the event of an error, a cluster fault (referred to as a cluster fault code) will be generated. The two most likely cases are described here.
The cluster is unable to unlock the drives due to a KmipServerFault cluster fault.
This can occur when the cluster first boots up and the key server is inaccessible or the required key is unavailable.
Follow the recovery steps in the cluster fault codes (if any).
A sliceServiceUnhealthy fault might be set because the metadata drives have been marked as failed and placed into the "Available" state.
Steps to clear:
Add the drives again.
After 3 to 4 minutes, check that the
sliceServiceUnhealthyfault has cleared.
See cluster fault codes for more information.