Skip to content

PCM replacement not clear when using NVE and OKM #376

@GlekkeV

Description

@GlekkeV

Page URL

https://docs.netapp.com/us-en/ontap-systems/fas8300/controller-replace-recable-reassign-disks.html

Page title

Recable the system and reassign disks - FAS8300 and FAS8700

Summary

Issue

When replacing a PCM. The following is stated if using NVE or NSE:

  1. If your storage system has Storage or Volume Encryption configured, you must restore Storage or Volume Encryption functionality by using one of the following procedures, depending on whether you are using onboard or external key management:
  1. Give back the controller:

If you have an OKM, no encrypted root volume, and ONTAP 9.6 or later you would assume to follow these steps:
ONTAP 9.6 and later

However, these commands are not possible as long as the controller is waiting for giveback.

How I resolved this (only using NVE, controller already at "...waiting for giveback")

  1. Perform giveback.
  2. Check if it was vetoed due to key manager (event log):
sfo.giveback.failed: Giveback of aggregate AGGR_NAME failed due to Giveback was vetoed..
sfo.sendhome.subsystemAbort: The giveback operation of 'AGGR_NAME' was aborted by 'keymanager'.
  1. Perform steps in ONTAP 9.6 and later
  2. Re-initiate giveback

Suggestion

I assume it would be best to follow these steps instead when performing a PCM replacement with OKM and NSE/NVE
ONTAP 9.8 or later with encrypted root volume. My suggestion would be to:

  1. Add this step to docs as requirement before booting to ONTAP
  2. Change the following line

If you are running ONTAP 9.8 and later, and your root volume is encrypted, you must set an onboard key management recovery passphrase with the boot menu. This process is also necessary if you do a boot media replacement.

To this.

If you are running ONTAP 9.8 and later, and your root volume is encrypted, you must set an onboard key management recovery passphrase with the boot menu.

Note

This process is also necessary if you do a boot media or PCM replacement.

Public issues must not contain sensitive information

  • This issue contains no sensitive information.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions