Skip to main content
NetApp Knowledge Base

crypto.export.failed error detected post-motherboard replacement

Views:
16
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:
12/5/2024, 12:58:55 AM

Applies to

  • ONTAP 9.10.1P15
  • Replace Motherboard
  • Onboard Key Manager (OKM)

Issue

  • crypto.export.failed error detected post-motherboard replacement.

[node01: svc_queue_thread: crypto.export.failed:alert]: ERROR: Export of key with key ID 00000000000000000000000000000000000000000000000000000000000000000000000000000000 failed. Additional information: error creating a base hierarchy blob. 

  • security key-manager key show -detail show NSE-AK and SVM-KEK at partner node as no restored.

::> security key-manager key show -detail

Node: node1
Key Store: onboard
Key ID Key Tag         Used By    Stored In                            Restored
------ --------------- ---------- ------------------------------------ --------
00000000000000000
       node1            NSE-AK    local-cluster                        yes
00000000000000000
       c5               VEK       local-cluster                        yes
00000000000000000
       f1               VEK       local-cluster                        yes
00000000000000000
       SVM2             SVM-KEK   local-cluster                        yes
00000000000000000
       SVM1             SVM-KEK   local-cluster                        yes


Node: node2
Key Store: onboard
Key ID Key Tag         Used By    Stored In                            Restored
------ --------------- ---------- ------------------------------------ --------
00000000000000000
       node2           NSE-AK     local-cluster                        no
00000000000000000
       svm2            SVM-KEK    local-cluster                        no
00000000000000000
       avm1            SVM-KEK    local-cluster                        no

Error: One or more nodes have the Onboard Key Manager keys that need to be restored. Run the "security
       key-manager onboard sync" command to restore the onboard key hierarchy on those nodes.

 

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.