Skip to main content
NetApp Knowledge Base

Unassigned FIPS replacement drive reports incompatible

  1. Last updated
  2. Save as PDF
Views:
255
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

SANtricity OS 11.70 and below

Issue

  • ASUP recovery-guru-procedures.html file has an entry for SECURITY_GET_KEY
  • After replacing an unassigned FIPS drive, replacement drive status is Incompatible due to invalid security key:
Drive at Shelf 0, Bay 1
Status: Incompatible
Cause: FIPS drive security locked
Mode: Incompatible
...
Drive capabilities: Data Assurance (DA), FIPS Compliant
...
Security capable: Yes, FIPS Compliant (FIPS 140 - 2)
Secure-Enabled: Yes
Read/write accessible: No, invalid security key
Drive security key identifier

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.