Steps For Connecting To A Kmip-Compliant Keyauthority - Brocade Communications Systems WFT-2D User Manual

20

Steps for connecting to a KMIP-compliant keyAuthority

8. Under Restore Backup, select Upload from browser, then enter a file name or browse to the file
9. Enter the Backup Password in the field provided, then click Restore.
10. After the certificate is restored to the secondary node from the previously backed-up primary
FIGURE 312
11. Under Restart/Halt, select Restart, then click Commit and wait until the restart is completed.
Steps for connecting to a KMIP-compliant keyAuthority
If you are using a TEKA KMIP-compliant server, only Thales e-Security keyAuthority running version
4.0 is supported; however, before selecting KMIP as the key vault type, all nodes in an encryption
group must be running Fabric OS 7.2.0 or later.
For more information about configuration instructions, refer to Chapter 3 of the Fabric OS
Encryption Administrator's Guide Supporting Key Management Interoperability Protocol (KMIP)
Key-Compliant Environments.
762
location.
node, select Maintenance > Services.
The Services Configuration page displays. (Refer to
NOTE
A message displays, advising that the secondary node requires a restart.
KeySecure Services Configuration page
The primary and second KeySecure nodes are now in a cluster and active for use.
Figure 312.)
Brocade Network Advisor SAN User Manual
53-1003154-01