Creating The Drive/Password Mapping Json Files And Using It To Initialize The System - Nvidia DGX A100 User Manual

Lock Enabled: Are locks enabled on this drive? It will be in this state after initialization (nv-

disk-encrypt init).
MBR done: This setting is only relevant for drives that support MBR shadowing. On drives

that support this feature, this will report 'Y' after initialization (nv-disk-encrypt init)
The following example output snippet shows drives than can be used for encryption. Notice
SED capable = Y and Boot disk = N.
The following example output snippet shows drives than cannot be used for encryption. Notice
SED capable = Y and Boot disk = Y, or SED capable = N.
Alternatively, you can specify the output be presented in JSON format by using the -j option.
$ sudo nv-disk-encrypt info -j
In this case, drives that can be used for encryption are indicate by the following:
"sed_capable": true "used_for_boot": false
And drives that cannot be used for encryption are indicated by one of the following:
"sed_capable": true "used_for_boot": true
Or
"sed_capable": false
6.6.1.2 Creating the Drive/Password Mapping JSON Files and
Using it to Initialize the System
Create a JSON file that lists all the eligible SED-capable drives that you want to manage.
1.
These are the list of drives that you obtained from "Determining Which Drives Can be
Managed as Self Encrypting".
The following example shows the format of the JSON file.
{
"/dev/nvme2n1": "<your-password>",
"/dev/nvme3n1": "<your-password>",
"/dev/nvme4n1": "<your-password>",
"/dev/nvme5n1": "<your-password>",
}
Be sure to follow the syntax exactly.
•
Passwords must consist of only upper-case letters, lower-case letters, digits, and/or
•
the following special characters: ~ : @ % ^ + = _ ,
DGX A100 System
Managing the DGX A100 Self-Encrypting Drives
DU-09821-001_v06 | 37