メインコンテンツまでスキップ

Onboard key-manager is not synced after motherboard replacement

  1. 最後の更新
  2. PDFとして保存
Views:
1
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Onboard key-manager (OKM)
  • Encryption
  • Motherboard Replacement

Issue

  • When OKM is configured, encryption keys must be synced after a motherboard replacement, even if OKM was recovered from the boot menu
  • After a OKM recovery, a node will boot and volumes will be available, but the keys will not be persistent if the node is rebooted
  • This will cause giveback of the node to be vetoed, and volumes to go offline if the veto is overriden

 

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.