Skip to main content
NetApp Knowledge Base

NSE: How to enable drive authentication on a NSE spare drive replacement

  1. Last updated
  2. Save as PDF
Views:
2,563
Visibility:
Public
Votes:
4
Category:
data-ontap-8
Specialty:
core
Last Updated:

​

​

Applies to

  • Self-encrypting drive (SED)
  • NetApp Storage Encryption (NSE) drive
  • FIPS-certified drive
  • ONTAP

Description

This article describes the procedure to assign drive ownership of a replacement self-encrypting drive (SED) and to rekey the replacement drive.

  • NetApp Storage Encryption (NSE) and SED drives are always encrypted regardless of the key ID in use.
  • When a drive is replaced on a NSE storage system, the storage administrator must manually rekey the new spare drive with a valid key ID and authentication passphrase to protect the data on the drive.
  • By default, the replacement SED is set with the MSID (Mfg Secure ID) of 0x0 and the drive is not securely protected or locked.
  • An unlocked drive or a drive with an authentication key ID of 0x0 does not require a key ID or passphrase authentication for data access.
  • It is extremely important to rekey the spare drive with the current key ID and lock the drive (ONTAP 8.3 and lower) to protect the data, prior to using the drive in production.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.