Chapter 5, Best Practices And Special Topics; Key Vault Best Practices; Chapter 6, Maintenance And Troubleshooting; Manually Synchronizing The Security Database - Brocade Communications Systems SN3000B Documentation Update

Chapter 5, Best Practices and Special Topics

Key Vault Best Practices

•

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:
•
•
Fabric OS Documentation Updates
53-1002165-05
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.
Use the cryptocfg exportmasterkey
--
Use the cryptocfg recovermasterkey currentMK
--
Documentation updates for RKM
file option to export the master key to a file.
-
srcfile to recover the master key.
-
6
17