跳转到主内容

更换主板后、板载keymanager sync失败

Views:
13
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2009580475</a>
Last Updated:

适用场景

  • 下面列出的ONTAP版本未修复 错误ID 1573150
    • 9.8P19和 9.8P20
    • 9.9.1P16和 9.9.1P17
    • 9.10.1P13和9.10.1P14
    • 9.11.1P8至9.11.1P11
    • 9.12.1P2至9.12.1P6.
    • 9.13.1和9.13.1P1
  • TPM 5.63
  • 板载密钥管理器(OKM)

问题描述

WARNING!
TPM is not initialized but OKM's key hierarchy is already protected with TPM 

  • 其他可能的错误包括:
Feb 28 14:45:52 [cluster1:crypto.ssal.failed:ALERT]: SSAL operation failed: SSAL Unseal operation failed
Feb 28 14:45:52 [cluster1:crypto.okmrecovery.failed:ALERT]: ERROR: Import of the onboard key hierarchy failed: failed to import key hierarchy. Additional information: error: ssal unseal failed
 

::> 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>.

  • 在恢复后、OKM同步将失败、并显示以下内容:
::> security key-manager onboard sync
 
Error: command failed: The Onboard Key Manager has failed to sync on the local node "cluster1-02", error: "Internal error". Failed to setup the Onboard Key Manager on node "cluster1-02"

 

 

 

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.