Skip to main content
NetApp Knowledge Base

Troubleshooting replacing motherboard with TPM chip and OKM configured

  1. Last updated
  2. Save as PDF
Views:
5,017
Visibility:
Public
Votes:
3
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

Issue

  1. When replacing a FAS or AFF motherboard equipped with a TPM chip, TPM license installed and using encrypted data (non-root) volumes, NVE volumes will go offline if giveback vetoes are overridden. You will see gb.sfo.veto.kmgr.keysmissing events:

::> event log show  -message-name gb.sfo.veto.kmgr.keysmissing
<date> <time> <node-name> ERROR gb.sfo.veto.kmgr.keysmissing: Giveback of aggregate <aggr-name> failed due to unavailability of volume encryption keys for the encrypted volumes of the aggregate on the partner node <node-name>.

  1. When replacing a FAS or AFF motherboard equipped with a TPM chip, TPM license installed and using encrypted root volumes, the system will not boot while the TPM is configured and the root volume is encrypted (Bug ID 1480977).  Upon boot, you will see the error:

Jun 08 12:05:30 [node1:crypto.okmrecovery.failed:ALERT]: ERROR: Import of the onboard key hierarchy failed: failed to import key hierarchy. Additional information: error: ssal unseal failed.

  • Bug ID 1416279 is open as a request to automate this process.

 

 


 

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.