Brocade Network Advisor SAN User Manual v12.0.0 (53-1002696-01, April 2013)

570 Brocade Network Advisor SAN User Manual
53-1002696-01
Steps for connecting to a TKLM appliance
20
Steps for connecting to a TKLM appliance
All switches you plan to include in an encryption group must have a secure connection to the Tivoli
Key Lifecycle Manager (TKLM). A local LINUX host must be available to transfer certificates.
NOTE
Ensure that the time zone and clock time setting on the TKLM server and encryption nodes are the
same. A difference of only a few minutes can cause the TLS connectivity to fail.
Repeat the same steps for configuring both the primary and secondary key vaults.
NOTE
The primary and secondary key vaults should be registered before you export the master key or
encrypting LUNs. If the secondary key vault is registered after encryption is done for some of the
LUNs, then the key database should be backed up and restored on the secondary TKLM from the
registered primary TKLM before registering the secondary TKLM.
The following is a suggested order for the steps needed to create a secure connection to TKLM:
1. Initialize all encryption nodes to generate KAC certificates and export the signed KAC
certificates to a local LINUX host. Refer to “Exporting the Fabric OS node self-signed KAC
certificates” on page 571.
2. Obtain the necessary user credentials and log in to the TKLM server appliance from the TKLM
management web console.
3. “Converting the KAC certificate format” on page 571.
4. Create a default key store on TKLM. Refer to “Establishing a default key store and device group
on TKLM” on page 571.
5. Create a device group named BRCD_ENCRYPTOR with device family LTO.
6. Add devices to the group. Refer to “Adding a device to the device group” on page 571.
7. Create a certificate for the TKLM server. Refer to “Creating a self-signed certificate for TKLM”
on page 572.
8. Import the node KAC certificates. Refer to “Importing the Fabric OS encryption node KAC
certificates to TKLM” on page 572.
9. Export the server CA certificate to a LINUX or Windows host. Refer to “Exporting the TKLM
self-signed server certificate” on page 572.
10. Add encryption group members as needed. The first node added to an encryption group
functions as the group leader. It is valid to have only one node in an encryption group.
11. Import the server CA certificate and register TKLM on the encryption group leader nodes. Refer
to the following:
- “Importing the Fabric OS encryption node KAC certificates to TKLM” on page 572.
- “Importing the TKLM certificate into the group leader” on page 573.
12. Enable the encryption engines.