Skip to main content
NetApp Knowledge Base

What is the correct setting for bootarg.storageencryption.support for NVMe SED drives?

Views:
693
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
encryption
Last Updated:

Applies to

  • NetApp Storage Encryption
  • NVMe drive

Answer

  • NVMe  SED (self-encrypting drive) that are not FIPS require  bootarg.storageencryption.support to be set to FALSE or UNSET.
    •  X4010A, X4011A, X4013A, X4014A
    • Able to mix these drives with the non-encrypting NVMe drives, such as X4001A, X4002A, X4004A, X4016A, X4018A
  • The ONLY NVMe  SED drives  that are  FIPS and require  bootarg.storageencryption.support to be set to TRUE.
    •  X4012A, X4019A
    • Mixing these drives with any other type of encrypting drives or non-encrypting drives is not supported in a stand-alone system or HA pair is not supported.

Additional Information

bootarg.storageencryption.support is typically set during the manufacturing process. However,if the encrypted disks do not show up at boot time, follow these steps to verify that the preceding bootarg is set to true: 

1. Halt ONTAP and stop at the LOADER-(A,B)>prompt and run the following command:

LOADER-A> setenv bootarg.storageencryption.support true

2. Confirm that this value is set.

LOADER-A> printenv bootarg.storageencryption.support

3. The output should look like this:

Variable Name                       Value
-------------------------------     ---------------------------------------
bootarg.storageencryption.support   true