HP Brocade 8/12c Brocade Fabric OS Documentation Updates - Supporting Fabric O - Page 27

Best Practices and Special Topics, Key Vault Best Practices

Page 27 highlights

Documentation updates for RKM 6 Chapter 5, Best Practices and Special Topics Key Vault Best Practices • When encrypted disk LUNs are to be configured or moved to an Encryption Group that uses a different key vault, make sure to decommission the encrypted LUNs from the old Encryption Group. Chapter 6, Maintenance and Troubleshooting Manually synchronizing the security database This operation can resolve problems with master key propagation (and connectivity issues between peer node encryption engines in an encryption group). The synchronization occurs every time this command is executed regardless of whether or not the security database was synchronized across all nodes in the encryption group. Use the - -sync -securitydb command to distribute the security database from the group leader node to all member nodes. This command is valid only on the group leader. In scenarios where this master key propagation issue still persists, exporting the master key to a file and recovering it resolves the issue. To do this, use the following commands: • Use the cryptocfg --exportmasterkey -file option to export the master key to a file. • Use the cryptocfg --recovermasterkey currentMK -srcfile to recover the master key. Fabric OS Documentation Updates 17 53-1002165-05

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60

Fabric OS Documentation Updates
17
53-1002165-05
Documentation updates for RKM
6
Chapter 5, Best Practices and Special Topics
Key Vault Best Practices
When encrypted disk LUNs are to be configured or moved to an Encryption Group that uses a
different key vault, make sure to decommission the encrypted LUNs from the old Encryption
Group.
Chapter 6, Maintenance and Troubleshooting
Manually synchronizing the security database
This operation can resolve problems with master key propagation (and connectivity issues between
peer node encryption engines in an encryption group). The synchronization occurs every time this
command is executed regardless of whether or not the security database was synchronized across
all nodes in the encryption group.
Use the
- -sync -securitydb
command to distribute the security database from the group leader
node to all member nodes. This command is valid only on the group leader.
In scenarios where this master key propagation issue still persists, exporting the master key to a
file and recovering it resolves the issue. To do this, use the following commands:
Use the
cryptocfg
--
exportmasterkey
-
file
option to export the master key to a file.
Use the
cryptocfg
--
recovermasterkey currentMK
-
srcfile
to recover the master key.