Skip to main content
NetApp Knowledge Base

CONTAP-663788: TPM Can Become Unavailable After Repeated Status Checks

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

On certain systems, repeated or concurrent security tpm show checks can cause the TPM to become inactive. Subsequent checks may fail with a resource-busy error, and the TPM may remain unavailable after the checks stop. This can affect operations that rely on TPM-backed onboard key management.

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.