The Setup - Encryption System Configuration screen allows you to configure library access to a primary and secondary key management server. For KMIP key managers, you can configure up to eight additional key servers for increased failover capability. For an overview of library managed encryption, see About Library Managed Encryption.
|
NOTE: You cannot edit the encryption system configuration settings when any EKM partition is enabled for library managed encryption. If this happens, go to Setup > Encryption > Partition Configuration and change all EKM partition settings from Library Managed Encryption (Enabled) to Library Managed Encryption (Disabled). Then go to Setup > Encryption > System Configuration and make your changes to the system configuration settings. Finally, go back to Setup > Encryption > Partition Configuration and change all the EKM partition settings back to Library Managed Encryption (Enabled). (See Configuring Partition Encryption.) |
|
NOTE: This operation should not be performed concurrently by multiple administrators logged in from different locations. You can access the appropriate screens, but you cannot apply changes while another administrator is performing the same operation. |
You need administrator privileges to configure key server system settings.
|
NOTE: SKM does not actually perform SSL communication but instead uses Transport Layer Security (TLS) communication protocol. However, the check box is still called “SSL.” |
|
NOTE: Keys are always encrypted before being sent from the Q-EKM server to a drive, whether SSL is enabled or not. Enabling SSL provides additional security. |
|
NOTE: Keys are always encrypted before being sent from the TKLM server to a drive, whether SSL is enabled or not. Enabling SSL provides additional security. |
For an initial key request, the library tries server #1 (the primary server) first. If server #1 is not available to perform a key request, the library tries server #2. For KMIP key managers, if server #2 is not available, the library will try server #3, and so on, in order. Once the library identifies a server that can perform the request, this server remains the active server until it fails a key request or the library is rebooted. At that point, the library starts over and uses server #1 for key requests.
In the text boxes, type either:
|
NOTE: If you change the Q-EKM port number for the key server from the default setting on the library, you must also change the port number on the actual key server to match, or library managed encryption will not work properly. See the Quantum Encryption Key Manager User’s Guide for information on setting the port number on the Q-EKM key server. |
|
NOTE: If you are using a secondary key server for Q-EKM, then the port numbers for both the primary and secondary key servers must be set to the same value. If they are not, synchronization and failover will not occur. |
|
NOTE: If you change the TKLM port number for the key server from the default setting on the library, you must also change the port number on the actual key server to match, or library managed encryption will not work properly. See the Quantum Encryption Key Manager User’s Guide for information on setting the port number on the TKLM key server. |
|
NOTE: If you are using a secondary key server for TKLM, then the port numbers for both the primary and secondary key servers must be set to the same value. If they are not, synchronization and failover will not occur. |
The Progress Window displays. The Progress Window contains information on the action, elapsed time, and status of the requested operation. Do one of the following:
For instructions on how to save the library configuration, see Saving the Configuration.
You may also access the EKM Path Diagnostics from this screen. For more information, see EKM Path Diagnostics.
See also: