6-66531-13 RevA SKM2.8 UserGuide
6-66531-13 RevA SKM2.8 UserGuide
6-66531-13 Rev A
Quantum Scalar Key Manager 2.8 User’s Guide, 6-66531-13 Rev A, September 2022, Product of USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not
limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this
publication from time to time without notice.
COPYRIGHT STATEMENT
Preface xiii
Chapter 1 Overview 1
Library Managed Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
How SKM Key Management Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Encryption Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Encryption Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Mirrored Hard Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Why You Need to Back Up Your SKM Servers . . . . . . . . . . . . . . . . . . . . 7
Glossary 267
Index 271
Figure 47 Replacing a Hard Disk Drive in SKM 2.6 Appliance Server 199
Figure 48 Sample libreplace.py Script Output, SKM 1.x . . . . . . . . . . 247
Figure 49 Sample libreplace.py Script Output, SKM 2.0. . . . . . . . . . 250
Figure 50 Scalar i3 Serial Number Label Location CM . . . . . . . . . . . 252
Figure 51 Scalar i3 Serial Number Label Location Side. . . . . . . . . . . 252
Figure 52 Scalar i3 Serial Number Label Location WebGUI . . . . . . . 253
Figure 53 Scalar i3 Serial Number Label Location CM . . . . . . . . . . . 254
Figure 54 Scalar i3 Serial Number Label Location Side. . . . . . . . . . . 254
Figure 55 Scalar i6 Serial Number Label Location WebGUI . . . . . . . 255
Figure 56 Scalar i40/i80 Serial Number Label and Location . . . . . . . 256
Figure 57 Scalar i500 Serial Number Label Location . . . . . . . . . . . . 257
Figure 58 Scalar i500 Serial Number/WWN Label. . . . . . . . . . . . . . . 257
Figure 59 Scalar i2000/i6000 Serial Number Label and Location . . . 258
Purpose This book contains information to help you install, configure, and run
your SKM system.
Definition of Terms Scalar Key Manager can be deployed in one of two ways:
• a physical pair of appliances (servers) purchased from Quantum, or
• a pair of virtual machines (VMs) installed in a VMware® or KVM
environment.
This guide uses the following terms to differentiate between the two
types of deployment:
• SKM appliance server — Physical key server purchased from
Quantum.
Product Safety Quantum will not be held liable for damage arising from unauthorized
Statements use of the SKM appliance server hardware. The user assumes all risk in
this aspect.
The SKM appliance server is engineered and manufactured to meet all
safety and regulatory requirements. Be aware that improper use may
result in bodily injury, damage to the equipment, or interference with
other equipment.
https://www.quantum.com/serviceandsupport/
softwareanddocumentationdownloads/skm/
index.aspx?whattab=Fifth
Documentation and The following publications provide information related to Scalar Key
Software Manager. For the latest versions of library documents, visit (click on
applicable library):
https://qsupport.quantum.com/kb/flare/Content/doc_portal/Content/
docs-portal/docs_portal.html
For the latest SKM documentation and firmware updates, see:
https://www.quantum.com/serviceandsupport/
softwareanddocumentationdownloads/skm/index.aspx?whattab=Fifth
Encryption-Enabled LTO-4, LTO-5, LTO-6, LTO-7, LTO-8, and LTO-9 Fibre Channel and SAS
Tape Drive tape drives are encryption capable. This means that they are functionally
capable of performing hardware encryption, but this capability has not
yet been activated. In order to perform hardware encryption, the tape
drives must be encryption enabled. They can be encryption enabled via
the tape library.
See Supported Libraries and Tape Drives on page 263 for a list of which
tape drives are supported by SKM on your library.
Encryption-Capable LTO-4 and higher tape cartridges are encryption capable. Data written
Media to encryption-supported and encryption-capable media in SKM-
supported tape drives will be encrypted unless data was previously
written to the media in a non-encrypted format. In order for data to be
encrypted, the media must be blank or erased (re-labeled), or have been
written to using library managed encryption at the first write operation
at the beginning of tape (BOT).
• You cannot append encrypted data to a non-encrypted tape.
• You cannot append non-encrypted data to an encrypted tape.
• You cannot encrypt data to an unlabeled tape.
Scalar Key Manager Encryption involves the use of several kinds of keys. How these keys are
(SKM) generated, maintained, controlled, and transmitted depends upon the
Encryption Keys
An encryption key is typically a random string of bits generated
specifically to encrypt and decrypt data. Encryption keys are created
using algorithms designed to ensure that each key is unique and
unpredictable. The longer the length of key used, the harder it is to
break the encryption code.
The LTO-4, LTO-5, LTO-6, LTO-7, LTO-8, and LTO-9 method of encryption
uses 256-bit AES algorithm to encrypt data. 256-bit AES is the
encryption standard currently recognized and recommended by the U.S.
government, which allows three different key lengths. 256-bit keys are
the longest allowed by AES.
SKM uses two types of encryption algorithms:
• Symmetric
• Asymmetric
Encryption Certificates
Each SKM server pair uses one unique encryption certificate. The
encryption certificate contains the public key of the public/private key
pair that protects data encryption keys during transit to another site.
The destination SKM server provides its public key to the source SKM
server as part of its encryption certificate, which the source SKM server
uses to wrap (encrypt) exported data encryption keys for transport.
Upon arrival, the file containing the wrapped data encryption keys can
only be unwrapped by the corresponding private key, which resides on
the destination SKM server and is never shared.
For more information, see the following:
• Encryption Keys on page 4
• Sharing Encrypted Tapes Offsite on page 161
• Sharing Encrypted Tapes Offsite on page 164
Keystore
The keystore contains:
• All of the data encryption keys generated by the SKM server on
which it resides. These keys are used for encrypting and decrypting
tapes.
• A copy of the data encryption keys generated by the other SKM
server in the pair.
• Data encryption keys that you imported (for example, keys that
other companies or individuals sent to you). These keys can be used
to decrypt tapes provided by the other companies or individuals.
• Your SKM server pair’s encryption certificate.
• Encryption certificates that you imported (for example, that other
companies or individuals sent to you). These are used to wrap your
data encryption keys for transit to another party to use in
decrypting tapes you may have provided to them.
• Public and private keys used for secure communication.
• Metadata (for example, which data encryption keys were used on
which tapes).
Caution: Do not remove any hard drive from the appliance server
unless it is failed or you are instructed to do so by Quantum
service. Removing any hard drive may render it unusable.
Each SKM appliance server contains two hard disk drives in a RAID 1
(mirrored) configuration. The two hard disk drives are constantly being
synchronized, so that each is an exact duplicate of the other. If one hard
disk drive fails, the other one contains all the required information to
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
SKM Appliance Server To maintain proper airflow and system cooling, observe the following:
Cooling and Airflow • Ensure there is adequate space around the server to allow the server
Requirements cooling system to work properly. Leave approximately 2 inches
(50 mm) of open space around the front and rear of the server.
• Do not place objects in front of the fans.
• Do not leave open space above or below an installed server in your
rack cabinet. To help prevent damage to server components, always
install a filler panel to cover the open space and to help ensure
proper air circulation.
SKM Appliance Server If the SKM appliance server is installed in a rack, consider the following:
Rack Considerations
WARNING: Do not place any object weighing more than 110 lb.
(50 kg) on top of rack-mounted devices.
• Install the server only in a rack cabinet that has perforated doors.
• Do not block any air vents. Usually 6 in. (15 cm) of air space
provides proper airflow.
• Plan the device installation starting from the bottom of the rack
cabinet.
• Install the heaviest device in the bottom of the rack cabinet.
• Do not leave open space above or below an installed server in your
rack cabinet. To help prevent damage to server components, always
install a filler panel to cover the open space and to help ensure
proper air circulation.
• Do not extend more than one device out of the rack cabinet at the
same time.
• Connect all power cords to properly wired and grounded electrical
outlets.
• Do not overload the power outlet when installing multiple devices
in the rack.
• Each library can only be configured to use one SKM server pair at a
time.
• Each library triggers the SKM servers to create a unique set of data
encryption keys. When more libraries are connected to an SKM
server, more initial data encryption keys will reside in the SKM
server’s keystore.
• Each library’s set of unique data encryption keys is maintained
separately on the SKM server. When you generate more keys for a
particular library, this does not affect any of the other libraries and
their sets of encryption keys. Each library only triggers creation of its
own set of keys.
Caution: Do not use SKM to encrypt the sole copy of your SKM
server backup. If both servers were to fail, you would
not be able to recover the encrypted backup and would
lose all data you had stored on all your encrypted
tapes.
• Remember your password. If you lose your password, you lose login
access to the SKM server, including backup and restore capability. If
you lose your password, Quantum will not be able to recover it for
you.
This chapter discusses the SKM appliance server safety, hardware, and
general operating instructions. Topics include:
• Safety
• SKM 2.7 Appliance Server (and later versions)
• SKM 2.6 Appliance (and Earlier Versions)
• Powering On the SKM Appliance Server
• Powering Off the SKM Appliance Server
Safety
This section provides some important information for handling the SKM
appliance server safely. Please also review the safety information in
Safety Information by Lenovo located at (Reference Guides):
https://www.quantum.com/ServiceandSupport/
SoftwareandDocumentationDownloads/SKM/Index.aspx?whattab=Fifth
This section covers:
• Electrical Safety
• Handling Static-Sensitive Devices
Electrical Safety WARNING: DANGER: Electrical current from power, telephone, and
communication cables is hazardous. To avoid a shock
hazard, follow all the warnings that follow:
Handling Static- Caution: Static electricity can damage the server and other
Sensitive Devices electronic devices. To avoid damage, keep static-sensitive
devices in their static-protective packages until you are
ready to install them. To reduce the possibility of damage
from electrostatic discharge, observe the following
precautions:
Caution: Do not leave the device where others can handle and
damage it.
Caution: Remove the device from its package and install it directly
into the server without setting down the device. If it is
necessary to set down the device, put it back into its static-
protective package. Do not place the device on the server
cover or on a metal surface.
Caution: Take additional care when you handle devices during cold
weather. Heating reduces indoor humidity and increases
static electricity.
Figure 2 SKM 2.7 Appliance The Ethernet ports on the rear of the server are as follows:
Server Rear Panel
• Unmarked port (far left: port) 10/100/1000 Mb Ethernet port
• Port 1 (middle port): 1GbE port
• Port 2 (far right: port): 1GbE port
The amber hard disk drive status LED will be solidly illuminated on a
failed hard disk drive.
• See Figure 3 for location of amber LED illuminated on the failed
drive (Slot 0, Callout 1).
• Notice that the drive in Slot 1 (Callout 2) has a green LED (meaning
the drive is operational).
CD drive activity LED CD eject button Hard disk drive 0 Hard disk drive 1
M4
Hard disk drive activity LED
Not used Hard disk drive 0
Reset button activity LED (green)
Server error LED
Power button
USB connector Hard disk drive 0
Power-on LED USB connector status LED (amber)
CD drive activity LED CD eject button Hard disk Hard disk drive 1 Hard disk drive Hard disk
drive 0 activity LED 1 status LED drive 1
(green) (amber)
Button, LED, or
Connector Function
Power-on LED • Off: Indicates AC power is not present, or the power supply or
the LED itself has failed.
Note: If this LED is off, it does not mean that there is no electrical
power in the server. The LED might be burned out. To remove all
electrical power from the server, you must disconnect the power
cord from the electrical outlet.
• On solid: Indicates the server is powered on.
• Blinking slowly (once per second): Indicates the server is
powered off and is ready to be powered on. You can press the
power button to power on the server.
• Blinking rapidly (4 times per second): Not present in all models.
Indicates the server is powered off and is not ready to be
powered on. The power button is disabled. This will last
approximately 1 to 3 minutes after connecting to AC power.
Power button Press this button to power on the server. To power off the server you
need to press and hold the button for more than four seconds. You
may need to use a pen to press the button.
Some servers come with a disc-shaped shield installed around the
button to prevent the server from being powered off accidentally.
You may remove the shield if you prefer.
Reset button Press this button to reset the server hardware and run the power-on
self-test (POST). You might need to use a pen or the end of a
straightened paper clip to press the button. Resetting takes 2 to 3
minutes.
Hard disk drive activity When this LED is blinking, it indicates that a hard disk drive is in use.
LED (Green)
Server error LED This amber LED has an exclamation point in it. When this LED is
illuminated, it indicates that a server error has occurred (including
when a hard disk drive is not in a slot; for example, when you
replace a damaged hard disk drive).
USB connectors You may connect a USB device such as a mouse or keyboard to
either of these connectors. The only reason you might use a USB
device is to connect directly to the command line interface without
using an SSH connection.
Button, LED, or
Connector Function
CD/DVD eject button Press this button to release a CD or DVD from the CD/DVD drive.
Note: Some server models have a CD drive; others have a DVD
drive.
CD/DVD drive activity When this LED is lit, it indicates that the CD/DVD drive is in use.
LED
Hard disk drive 0 and 1 These green LEDs blink either once every 16 seconds or several times
activity LEDs rapidly every 16 seconds (depending on server model) during
normal activity.
When the hard disk drive is being accessed, the LED blinks at a
faster rate. During RAID rebuild (which occurs when a hard disk
drive is replaced), the LED flickers very fast so that it may appear to
be on solid.
Hard disk drive 0 and 1 These amber LEDs will be on solid to indicate a the hard disk drive is
status LEDs faulty and needs to be replaced.
During a RAID rebuild (which occurs when a hard disk drive is
replaced), the LED of the hard disk drive that is updating will blink
slowly (once per second).
Rear Panel Connectors The following two figures show the connectors and LEDs on the rear of
and LEDs the server.
Figure 5 Rear Panel Figure 5 shows the connectors on the rear of the server. Your server will
Connectors look like one of the two drawings below.
M2 and earlier
Serial connector
Power cord
USB connector (reserved)
connector
Systems-management Video connector
connector (reserved) USB connector
Ethernet Port 2
(for network connection)
Ethernet Port 1
(for setup/configuration)
M5
Connector Function
Systems-management Reserved.
connector
Figure 6 Rear Panel LEDs Figure 6 shows the LEDs on the rear of the server. Your server will look
like one of the two drawings below.
M2 and earlier
M3 and M4
Ethernet Port 1 link LED Ethernet Port 2 activity LED
M5
Ethernet Port 2 link LED Ethernet Port 1 activity LED
LED Function
Ethernet link LED When this LED is on, it indicates that the
Ethernet controller is connected to the
network.
Note: If a power failure occurs while the server is powered on, the
server will restart automatically when power is restored.
Caution: The power button on the server does not turn off the
electrical current supplied to the device. To remove all
electrical current from the device, ensure that the power
cord is disconnected from the power source.
Caution: The SKM appliance servers are designed for one purpose
only—to store and manage your encryption keys. Do not
install additional hardware on the servers. Never install any
software, file, or operating system on the servers unless it is
an upgrade or patch supplied by Quantum. Doing so can
make your server inoperable and will void your warranty.
Items Required for You need the following to install and configure each SKM appliance
Setup server:
• (2) SKM appliance servers (each comes with two hard disk drives
installed).
• Power cord (supplied).
• Rackmount kit with installation instructions (supplied).
• CAT5e Ethernet cable, crossover (for initial configuration, not
supplied).
• CAT5e Ethernet cable, standard (for standard operation, not
supplied).
• Laptop or PC, to connect to each server to perform initial
configuration.
• To access all the features of SKM, the most recent library firmware is
recommended. See the Release Notes for your library for
information on the minimum firmware required to run SKM, and
most recent firmware versions available for your library.
• For Microsoft® Windows®, you may need to install utilities to use
secure shell (SSH) and secure file transfer protocol (SFTP). Two such
utilities are PuTTY, available at http://www.chiark.greenend.org.uk/
~sgtatham/putty/ and WinSCP, available at http://winscp.net.
Installing the SKM Follow the instructions below for both SKM appliance servers.
Appliance Servers
Caution: Do not remove any hard drive from the appliance server
unless it is failed or you are instructed to do so by Quantum
service. Removing any hard drive may render it unusable.
Note: The Scalar Key Manager rack box ships in each appliance/server
box. The “Rack Installation Guide” ship within the rack box.
2 Install the SKM appliance server in a rack. Follow the Scalar Key
Manager Rack Installation instruction sheet (included with the rail
kit and located at (Product Use Guides):
https://www.quantum.com/ServiceandSupport/
SoftwareandDocumentationDownloads/SKM/Index.aspx?whattab=Fifth
3 Connect the power cord into the rear of the SKM appliance server
(see Figure 7 or Figure 8) and plug it into a grounded power outlet.
Depending on the server model you have, it may take up to 20
seconds or more for power button to become active. During this
time, one or more fans might run loudly and then quiet down. On
some models, the power-on LED on the front panel (see Figure 9 or
Figure 10) blinks rapidly (4 times per second), indicating the power
button is not active yet.
Figure 7 provides an illustration of the SKM 2.7 Appliance Server (rear view).
• The power cord connector is located on the power supply unit
(PSU), at the right-rear of the server.
• The Ethernet ports on the rear of the server are as follows:
• Configuration/Mangement Port: Unmarked port (far left: port)
10/100/1000 Mb Ethernet port (Callout 2)
• Port 1 (middle port): 1GbE network port (Callout 3)
• Port 2 (far right: port): 1GbE network port (Callout 4)
Figure 8 SKM 2.6 Appliance Figure 8 shows the rear of the SKM 2.6 Appliance Server (and earlier
Server Rear Panel versions).
M2 and earlier
M3 and M4
M5
M6
Figure 9 SKM 2.7 Appliance Figure 9 shows the front of the SKM 2.7 Appliance Server (and later
Server Front Panel versions). It provides the location of the “power-on button and the
installed drives.
Figure 10 SKM 2.6 Appliance Figure 10 shows the rear of the SKM 2.6 Appliance Server (and earlier
Server Front Panel versions). It provides the location of the “power-on LED and the power
button).
M3 and earlier
6 Again observe the power-on LED on the front panel. Wait until it is
illuminated but not blinking, indicating the server is powered on.
7 Allow up to 3 minutes for the server to complete startup before you
connect via SSH in the next step.
Configuring the SKM Follow the instructions below for both SKM appliance servers.
Appliance Servers
Note: Both SKM appliance servers must be configured, operational,
and connected to the network before any libraries can be set
up to use them.
The configuration process requires you to read and accept the end user
license agreement, and then complete a setup wizard. The setup wizard
helps you configure the following values. Before beginning, decide what
you want each of these values to be. You can also change these values
in the future.
• Password
• Time zone, date, and time
• IP address, netmask, and gateway
Allow 30 minutes per server to complete the configuration.
1 Set the IP address of the laptop or PC you will use to connect to the
SKM appliance server to 192.168.18.100.
2 Connect a crossover CAT5e Ethernet cable from the laptop or PC to:
• SKM 2.7 Appliance Server (and later versions) Configuration/
Mangement Port on the rear of the SKM server (see Figure 7 on
page 30).
• SKM 2.6 Appliance Server (and earlier versions) Ethernet Port 1
on the rear of the SKM server (see Figure 8 on page 31).
3 Using SSH, connect to the server using the IP address for Ethernet
Port 1: 192.168.18.3.
4 At the login prompt, type the following (this is the user login ID
which will never change):
akmadmin
5 At the Password prompt, type the default password:
password
Each SKM server has its own password. If you set them
differently, you must remember both.
The IP address you are configuring is for Ethernet Port 2, the port
you will be using for network connection to SKM.
Ethernet Port 1 IP Address (never changes): 192.168.18.3
Note: Ports are identified on the back of the server as Port 1 and
Port 2, but when configuring SKM through the console the
ports are referred to onscreen as Ports 0 and 1 respectively.
(That is, labeled Port 1 = Port 0 in the console, and labeled
Port 2 = Port 1 in the console.)
Note: The netmask must match the netmask and gateway of the
connected libraries.
Note: You MUST quit at this point. Otherwise your changes will
not be saved and you will not be able to continue the
installation process.
14 Disconnect the crossover CAT5e Ethernet cable from the SKM 2.7
Appliance Server Configuration/Mangement Port and/or the SKM
2.6 Appliance Server Ethernet Port 1 (see Figure 7 on page 30 or
Figure 8 on page 31).
15 On the laptop you are using to configure SKM, change the hard-
coded IP address back to DHCP.
16 Connect a standard CAT5e Ethernet cable from Ethernet Port 2 on
the back of the SKM appliance server to your network (see Figure 8
on page 31). You will connect to this port using the IP address
assigned in Step 11 above.
17 Complete steps 1-16 on the secondary SKM server before
proceeding.
18 When you are finished, do one of the following:
• For pre-SKM 2.4 (240Q) systems, proceed to Installing TLS
Certificates on the SKM Server for Pre-SKM 2.4 (240Q) on
page 76.
• For SKM 2.4 (240Q) and later systems, proceed to Installing TLS
Certificates on the SKM Server for SKM 2.4 (240Q) or Later on
page 87.
Note: You can see the version of software you are running at the
top of the SKM Admin Commands menu. To view the
software version without accessing SKM Admin
Commands, refer to “Viewing the SKM Server Software
Version” in the SKM User’s Guide.
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
Equipment and You need the following to set up and configure the SKM VM servers:
Software Needed for • Scalar Key Manager VM Installation packages.
VMware
• SKM VM server software (.ova image)
• VMware® vSphere™ Client installed on a computer. The computer
may be the same as the server that hosts the VM but it does not
have to be. The vSphere Client is required for initial setup; after that,
you can use vSphere Client or another method to access the SKM
VM server.
Deploying the .ova Follow the instructions below for both SKM VM servers. The .ova
Image for VMware installation process is performed via VMware’s vSphere Client.
1 Access the Scalar Key Manager 2.x VM Installation software that you
will load on each server.
2 You may copy the .ova image to a shared network drive for faster
deployment if you wish.
3 Launch vSphere Client.
4 Log on to the VM host.
5 Highlight the IP address of the VM host.
6 Select File > Deploy OVF Template.
The Deploy OVF Template wizard opens.
7 Complete the wizard screens and click Finish when done.
A progress bar displays on the screen. When complete, the SKM VM
server name appears in the list of VMs on the screen. Deployment
takes a few minutes to several hours depending on network speed
and location of the .ova image in relation to the VM host. Wait until
the file deploys before continuing.
Configuring the SKM Follow the instructions below for both SKM VM servers.
VM Servers for VMware
Note: Both SKM VM servers must be configured, operational, and
connected to the network before any libraries can be set up to
use them.
Caution: You must use a different SKM software package for each
VM server. Keep track of which SKM software package you
use for which SKM server. The TLS certificates and serial
number/MAC address/license key are unique and you must
use the correct ones if you ever need to reinstall the SKM
server. Also, if you accidentally use the same SKM software
package for both VM servers, you will not be able to
complete the configuration.
The configuration process requires you to read and accept the end user
license agreement, and then complete a setup wizard. The setup wizard
helps you configure the following values. Before beginning, decide what
you want each of these values to be. You can also change these values
in the future.
• Password
• Time zone, date, and time
• IP address, netmask, and gateway
Allow 30 minutes per server to complete the configuration.
1 Using vSphere Client, make sure the SKM VM server you just created
is powered OFF (right-click the VM server, select Power, then select
Power Off).
2 Right-click the SKM VM server and select Edit Settings.
3 Configure the MAC address as follows (see Figure 13):
a Under the Hardware tab, select Network adapter 1.
b Under MAC Address, select Manual.
c In the MAC Address field, type the MAC ID from the label of
the SKM software package from which you deployed the .ova
image.
d Click OK.
Note: When using the console, you will lose the ability to use
your mouse/cursor. To regain the use of the mouse/cursor,
press <Ctrl+Alt>.
8 At the skmserver login prompt, type the following (this is the user
login ID which will never change):
akmadmin
9 At the Password prompt, type the default password:
password
10 At the akmadmin@skmserver prompt, type:
./skmcmds
11 At the Password prompt, type the default password:
password
12 When prompted for the license, type the 29-digit License Key
(including hyphens) from the label on the CD case of the CD from
which you deployed the .ova image, and press <Enter>. The license
is not case sensitive.
The license file is created.
13 When prompted, press <Enter>.
The End User License Agreement displays.
14 Read the license agreement. Press <Enter> to scroll through the
agreement. At the end, type y to accept and continue or n to
decline and stop the installation process.
15 When prompted, press <Enter> to set up the server.
16 The first setup wizard task prompts you to change the akmadmin
password (see Figure 15). There is only one password for SKM. It is
called the akmadmin password, and is required for all logins and
access to commands, including backup and restore.
Each SKM server has its own password. If you set them
differently, you must remember both.
Note: You MUST quit at this point. Otherwise your changes will
not be saved and you will not be able to continue the
installation process.
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
Equipment and You need the following to set up and configure the SKM VM servers:
Software Needed for • Two (2) Scalar Key Manager VM Installation CD packages. You must
KVM use a different CD package for each SKM server. Each CD package
contains:
• SKM VM server software (.raw.bz2 image)
• SKM server Quantum-provided TLS communication certificate
bundle (.tgz file)
• Printed label on the CD case containing a unique serial number,
MAC ID, and license key (required for installation)
• QEMU-KVM installed on a computer. The computer may be the
same as the server that hosts the VM but it does not have to be.
Access to QEMU-KVM is required for initial setup.
• Resources required for each SKM VM server:
• (1) Ethernet interface
• (1) CD ROM drive
• 1 GB RAM
• 8 GB of disk space
• KVM host software must Virtual Machine Manager 0.9.0 or
higher
• Library firmware must be at the following minimum versions to run
SKM. To access all the features of SKM 2.2 or later version, the most
recent library firmware is recommended.
Deploying the .raw Follow the instructions below for both SKM VM servers. The .raw
Image on KVM installation process is performed via QEMU-KVM.
1 Insert the Scalar Key Manager VM Installation CD into the your
computer’s CD ROM drive.
2 Decompress the .raw.bz2 image file to a known location. You may
copy the image to a shared network drive for faster deployment if
you wish.
For example: bunzip2 5-01071-01_220Q.GC00300.raw.bz2
3 Launch QEMU-KVM.
4 Log on to the VM host.
5 Under the local host, right-click and select New.
6 In the Name field, type the name of the new virtual machine.
7 Select Import existing disk image and click Forward.
9 For OS type select Linux and for Version select Ubuntu [version]
(Lucid Lynx). Click Forward.
10 For Memory (RAM) select 1024 and for CPUs select 2. Click
Forward.
Configuring the SKM Follow the instructions below for both SKM VM servers.
VM Servers for KVM
Note: Both SKM VM servers must be configured, operational, and
connected to the network before any libraries can be set up to
use them.
The configuration process requires you to read and accept the end user
license agreement, and then complete a setup wizard. The setup wizard
helps you configure the following values. Before beginning, decide what
you want each of these values to be. You can also change these values
in the future.
• Password
• Time zone, date, and time
• IP address, netmask, and gateway
Allow 30 minutes per server to complete the configuration.
Note: When using the console, you will lose the ability to use
your mouse/cursor. To regain the use of the mouse/cursor,
press <Ctrl+Alt>.
4 At the skmserver login prompt, type the following (this is the user
login ID which will never change):
akmadmin
5 At the Password prompt, type the default password:
password
6 At the akmadmin@skmserver prompt, type:
./skmcmds
7 At the Password prompt, type the default password:
password
8 When prompted for the license, type the 29-digit License Key
(including hyphens) from the label on the CD case of the CD from
which you deployed the .ova image, and press <Enter>. The license
is not case sensitive.
The license file is created.
9 When prompted, press <Enter>.
The End User License Agreement displays.
10 Read the license agreement. Press <Enter> to scroll through the
agreement. At the end, type y to accept and continue or n to
decline and stop the installation process.
11 When prompted, press <Enter> to set up the server.
12 The first setup wizard task prompts you to change the akmadmin
password (see Figure 15). There is only one password for SKM. It is
called the akmadmin password, and is required for all logins and
access to commands, including backup and restore.
Each SKM server has its own password. If you set them
differently, you must remember both.
d Press <Enter>.
13 Continue through the setup wizard to configure the rest of the
settings: time zone, date, time, IP address, netmask, and gateway. If
you press <Enter> without entering a value, the existing value
remains.
Note: You MUST quit at this point. Otherwise your changes will
not be saved and you will not be able to continue the
installation process.
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
Equipment and You need the following to set up and configure the SKM Hyper-V
Hardware Needed for servers:
SKM Hyper-V • Windows 2016 or greater with Hyper-V Manager installed.
• SKM version 270Q.
• Two (2) Scalar Key Manager Hyper-V Installation CD packages. You
must use a different CD package for each SKM server. Each CD
package contains:
• Hyper-V VM server software hard disk image file (.bz2).
• Unique serial number, MAC ID, and license key (required for
installation)
• Resources required for each SKM Hyper-V server:
• (1) Ethernet interface
• 1 GB RAM
• 8 GB of disk space
Deploying the SKM Follow the instructions below for both SKM Hyper-V servers.
Server for Hyper-V 1 Create the following folder on the Windows server:
c:\Quantum\skm\disks
2 Create the following folder for VM configurations:
c:\Quantum\skm\configurations
3 Copy the image file (.bz2) to the file location created in Step 1.
4 Bunzip2 the image file.
5 Rename the hard disk image file. Quantum recommends a naming
convention such as skmprimary for the primary SKM server and
skmsecondary for the secondary SKM server.
6 Launch the Hyper-V Manager.
8 Select Next.
Do the following:
10 Select Next.
11 Set the memory to 4096 MBs.
12 Select Next.
13 Select Virtual Switch from the Connection drop-down menu.
14 Select Next.
15 Select the Use an existing virtual hard disk radio button.
18 Select Finish.
19 The SKM virtual machine will now appear under Virtual Machines.
Configuring the SKM Follow the instructions below for both Hyper-V VM servers.
Hyper-V Servers
Note: Both Hyper-V VM servers must be configured, operational, and
connected to the network before any libraries can be set up to
use them.
The configuration process requires you to read and accept the end user
license agreement, and then complete a setup wizard. The setup wizard
helps you configure the following values. Before beginning, decide what
you want each of these values to be. You can also change these values
in the future.
• Password
• Time zone, date, and time
Each SKM server has its own password. If you set them
differently, you must remember both.
Note: You MUST quit at this point. Otherwise your changes will
not be saved and you will not be able to continue the
installation process.
Note: All TLS Certificates that were provided on the initial CDs are
likely already expired. New TLS Certificates must be generated
by the customer or obtained from Quantum.
TLS certificates are required on the SKM server. You can choose to use
the Quantum-provided TLS certificates or install your own, as follows:
• SKM appliance server: The SKM appliance server comes with
Quantum-provided TLS certificates already installed. You can install
your own TLS certificates (to overwrite the installed certificates) if
you wish.
Note: Any time you install TLS certificates, they will overwrite any TLS
certificates currently installed on the SKM server.
Requirements for When providing your own certificates, it is assumed you understand the
Installing User-provided concepts of PKI and can access the tools or third-party resources needed
TLS Certificates to generate or obtain certificates. See Importing TLS Communication
Certificates on the Library on page 159 and Exporting and Importing
Encryption Certificates on page 166 for more information.
Note: You must be running SKM 1.1 or higher on your SKM servers in
order to install your own TLS certificates.
Note: If you install your own TLS certificates on the SKM server, you
must also install your own certificates on the library. Similarly, if
you use the Quantum-provided TLS certificates on the SKM
server, you must also use the Quantum provided TLS certificates
on the library. Some newer libraries come with Quantum-
provided TLS certificates pre-installed, and other newer libraries
require certificate installation. See your library user’s guide for
instructions on how to verify whether TLS certificates are
installed on the library and how to install them.
Creation Process The process of creating TLS Certificates is outlined in the basic
procedure below. Be sure to follow these steps in the order shown.
Figure 21 Example of
Quantum Certificate Bundle
Displayed on Screen
Note: You MUST quit at this point. Otherwise the server will
remain stopped and you will not be able to continue the
configuration process on the library.
Note: Use the SKM server that has the earliest Date/Time/Time zone
configured for generating the TLS Certificates.
- If the TLS Certificates are generated on an SKM server that has
a Date/Time/Time zone that is later than the other server, then
the TLS Certs will now work on the other server until that Date/
Time has been reached.
- This has caused a lot of confusion and wasted a lot of time on
escalations in the past.
- This same requirement also applies to the Date/Time/Time
Zone configured on the tape libraries.
Note: The TLS certificate generation process must be run on only one
of the SKM servers, so there is no need to generate TLS
Certificates on both SKM servers. Either the Primary or
Secondary SKM server can be used to generate the certificates.
Begin the Installation 1 SSH in to the SKM server. (If you have an SKM VM server, you can
SSH in or continue to use the vSphere console and proceed to
Step 4 below.)
2 At the skmserver login prompt, type the login ID:
akmadmin
3 At the Password prompt, type your password.
Executing the Script Use the following procedure to generate certificates using the -d option,
Using the -d Option which uses default values. The generated certificates are valid for ten
years from the date on which they were generated.
1 Once logged into an SKM server running 240Q or greater, execute
genSKMcerts –d to generate certificates using the defaults.
The following illustration shows the default values (in brackets) used:
Executing the Script Use the following procedure to generate certificates without using the
Without Using the -d -d option. This method requires you to enter certificate values. If
Option desired, you can press Enter to accept the default value (displayed in
brackets) for any item.
2 Enter the size of the key in bits. Valid key sizes are 1024, 2048 or
4096 bits. The default size is 2048 bits.
3 Enter the duration in days for which the TLS certificates will be valid.
The default duration is 10 years (3650 days).
10 The next three entries are common names for the Tape libraries,
SKM primary server and SKM secondary server. The names must be
unique because these names will be used for the different sets of
certificates.
Executing the Script After certificates are generated, follow this procedure to generate a set
with the -Q Option of Quantum bundles that can be loaded onto the library and SKM
servers using the user interface.
1 Enter the command genSKMcerts -Q.
2 On screen messages provide status as the Quantum certificate
bundles are generated using the default values, so no user input is
required. (The generated bundle files are saved at /home/
akmadmin/generatedcerts/qbundles.)
Configuring the Perform these steps, in order, on the Scalar i500 libraries only.
Scalar i500 Tape See the library user’s guide or online help for detailed instructions on
Libraries how to complete each of these steps.
1 Install the Encryption Key Management (EKM) license on your
library.
2 Prepare partitions for library-managed encryption:
a Install LTO-4, LTO-5, LTO-6, LTO-7, LTO-8, and/or LTO-9 tape
drives in the library, if not already installed. Unload all tape
cartridges from these tape drives.
b Ensure that the partitions you want to configure for SKM
contain only LTO-4, LTO-5, LTO-6, LTO-7, LTO-8 and/or LTO-9
tape drives.
c On the tape drives, install the latest version of firmware that is
qualified for the library firmware installed on your library. Refer
to the library release notes for the correct version of tape drive
firmware.
3 TLS certificates must be installed on the library as well as on the
SKM server. Verify the appropriate TLS communication certificates
are installed on the library. If you installed your own TLS certificates
on the SKM servers, you must install your own TLS certificates on
the library. If you used Quantum-supplied TLS certificates on the
SKM servers, you must use Quantum-supplied certificates on the
library.
Some newer libraries ship with TLS certificates already installed, and
other newer libraries require certificate installation. See your library
user’s guide for instructions on how to check whether TLS
certificates are installed, where to download, and how to install
them.
Note these general guidelines:
• For pre-2.4 SKM servers, preloaded TLS certificates on the library
will work
• For 2.4 (240Q) and later SKM servers, preloaded TLS certificates
on the library will not work, and you must download the
generated library TLS certificate onto the library
4 Configure the SKM server IP addresses on the library.
a From the library’s Web client, navigate to the encryption system
configuration screen.
b Enter the primary and secondary SKM server IP addresses or
host names in the fields provided.
c Click Apply.
5 Run EKM Path Diagnostics and make sure all the tests pass. Pass/fail
status is displayed in a progress window after the diagnostics
completes (see Figure 22). This is required to make sure the library is
connected properly to both SKM servers. If any of the tests fail,
follow the instructions in the online help or library user’s guide to
troubleshoot and then run EKM Path Diagnostics again.
Configuring the Scalar Perform these steps, in order, on the Scalar i6000 library only.
i6000 Tape Library See the library user’s guide or online help for detailed instructions on
how to complete each of these steps.
1 Install the Encryption Key Management (EKM) license on your
library.
2 Prepare partitions for library-managed encryption by doing the
following:
a Install the following tape drives in the library, if not already
installed. Unload all tape cartridges from these tape drives.
For the Scalar i6000:
• HP LTO-4 through LTO-6
• IBM LTO-5 through LTO-9
b On the tape drives, install the latest version of firmware that is
qualified for the library firmware installed on your library. Refer
to the library release notes for the correct version of tape drive
firmware.
3 TLS certificates must be installed on the library as well as on the
SKM server. Refer to the following links to the Scalar i6000
Documentation Centers for instructions on how to install
certificates.
Configuring the Scalar Perform these steps, in order, on the Scalar i3 or i6 library only.
i3/i6 Tape Library Refer to the i3 or i6 Documentation Center for detailed instructions on
how to complete each of the following steps.
• Scalar i3 Documentation Center:
http://www.quantum.com/scalari3docs
• Scalar i6 Documentation Center:
http://www.quantum.com/scalari6docs
1 Install the Encryption Key Management (EKM) license on your
library.
2 Prepare partitions for library-managed encryption by doing the
following:
a Install the following tape drives in the library, if not already
installed. Unload all tape cartridges from these tape drives.
For the Scalar i3:
• IBM HH SAS LTO6
• IBM HH SAS LTO7
• IBM HH FC LTO6
• IBM HH FC LTO7
• IBM HH FC LTO8
• IBM HH SAS LTO8
For the Scalar i6:
• IBM FH FC LTO6
• IBM FH FC LTO7
• IBM FH FC LTO8
b On the tape drives, install the latest version of firmware that is
qualified for the library firmware installed on your library. Refer
to the library release notes for the correct version of tape drive
firmware.
3 TLS certificates must be installed on the library as well as on the
SKM server. Refer to the following links to the Scalar i3/i6
Documentation Centers for instructions on how to install
certificates.
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
Note: There is only one SKM server login ID, akmadmin. This login ID
cannot be changed.
To log on to the SKM server command line at any time after initial setup:
1 Connect to the SKM server.
• SKM appliance server: Use SSH.
• SKM VM server: You can connect using SSH or vSphere.
Caution: If you are using SSH to access SKM Admin Commands, your
session will automatically terminate after a period of
inactivity. If your session terminates before you quit, any
changes you made will not be saved.
Caution: If you are using the vSphere Client console to access SKM
Admin Commands (SKM VM servers only), your session will
never automatically terminate and the SKM server will
remain stopped. It is important that you remember to quit
your session so that encryption can continue.
To quit SKM Admin Commands and restart the server, type q and press
<Enter> at the Command prompt.
If you are using SSH, your session automatically logs off after a period of
inactivity. If you are using vSphere (SKM VM servers only), the session
never terminates and you remain logged on until you log off. In
addition, when you quit SKM Admin Commands, if you do not log off of
the command line interface, the system allows you to access SKM
Admin Commands again for 60 minutes without requiring you to enter
a password.
6 Update the IP address on each library that uses this SKM server, as
follows (see your library user’s guide or online help for details):
a Make sure that no tape cartridges are mounted in any of the
tape drives in any of the SKM partitions in the library.
b Access the library’s remote Web client.
c Navigate to the encryption partition configuration screen and
change the encryption method on all SKM partitions from
Enable Library Managed to Allow Application Managed.
d Navigate to the encryption system server configuration screen
and update the IP address of the SKM server.
To change the date and time at any time after initial configuration:
1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 At the Command prompt, type 6 and press <Enter> to Set SKM
server date and time.
5 Press <Enter>.
6 At the Command prompt, type q and press <Enter> to quit SKM
Admin Commands, save your changes, and restart the SKM server.
Displaying the TLS To view the certificates currently installed on the SKM server:
Certificates 1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 At the Command prompt, type d and press <Enter> to Display/
update TLS communication certificates.
The Display/update TLS communication certificates menu
displays.
4 At the Command prompt, type s and press <Enter> to Show
current communication certificate information.
The names and locations of the currently installed certificates
display.
5 To view certificate information, type the number of the certificate or
type a for all, and press <Enter>. To quit, type q and press
<Enter>.
6 At the Command prompt, type q to quit and return to SKM Admin
Commands.
Installing the TLS For detailed instructions on installing TLS certificates, see:
Certificates • Installing TLS Certificates on the SKM Server for Pre-SKM 2.4 (240Q)
on page 76.
• Installing TLS Certificates on the SKM Server for SKM 2.4 (240Q) or
Later on page 87
It is critical that you keep a current backup of each SKM server so that
you can restore it if the server were to become inoperable. This chapter
describes:
• Backing Up the SKM Server
• Restoring the SKM Server
Note: For multiple libraries accessing the same SKM server pair: If
you are configuring more than one library to use the same SKM
servers, be aware that each library triggers the SKM servers to
create a set of data encryption keys which are added to the
keystore. You need to make sure all the keys are included in
your backup before you start using those keys. If you are
configuring several libraries at the same time, you can wait
until all the keys are generated and then perform a single
backup of each server, provided that you do not use the keys
before you back them up. However, if there is a time delay
between the key generation during which you intend to begin
serving keys for encryption, you will need to perform multiple
backups — one after each key generation session.
There are two ways to back up the server. Both will stop the SKM server
process prior to backup and restart the server process after the backup
is complete. It is faster to use the command line interface unless you are
already in SKM Admin Commands.
• Backing Up Using SKM Admin Commands
• Backing Up Using the Command Line Interface
Backing Up Using SKM Perform the following steps for each SKM server separately.
Admin Commands 1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 At the Command prompt, type 7 to Back up SKM server.
4 Press <Enter>.
Backup files are created and consolidated into a single file, whose
name and location are displayed on the screen.
5 Note the name and location of the backup file:
/home/akmadmin/backups/SKM<version>KeyServer<serial
number><date><time>.tgz
6 Use SFTP to copy the backup file to a desired location.
Caution: You must copy the backup file to another location and
not just leave it on the SKM server. This is so that, if the
SKM server fails, you can restore the backup from the
remote location onto the new server.
7 Press <Enter>.
The SKM Admin Commands menu displays.
8 At the Command prompt, type q and press <Enter> to quit SKM
Admin Commands and restart the SKM key server.
9 Repeat the above steps on the other server in the SKM server pair.
Backing Up Using the Perform the following steps for each SKM server separately.
Command Line 1 Log on to the SKM server command line interface (see Logging on
Interface to the Command Line Interface on page 110).
2 At the akmadmin@<hostname> prompt (where <hostname> is
the SKM server hostname), issue the following command:
./skmcmds -B
Backup files are created and consolidated into a single file, whose
name and location are displayed on the screen.
3 Note the name and location of the backup file:
/home/akmadmin/backups/SKM<version>KeyServer<serial
number><date><time>.tgz
4 Use SFTP to copy the backup file to a desired location.
5 Repeat the above steps on the other server in the SKM server pair.
Caution: Make sure you use the backup for the failed server, not
the working server. The backups are not the same. The
filenames of the backup files contain the serial number
of the server.
5 Press <Enter>.
A message displays instructing you to copy a previous backup file to
the /home/akmadmin/backups folder on the SKM server using
SFTP.
Note: You cannot restore SKM 1.x backup files onto an SKM 2.0
or higher system.
6 Use SFTP to copy the file from your known location to the /home/
akmadmin/backups folder on the SKM server.
Caution: The library cannot use the restored SKM server to serve
new data encryption keys until you complete these
steps. Each library keeps track of the last data
encryption key served by the SKM server. These steps
reset the restored SKM server so that it does not serve
previously used data encryption keys.
The SKM server collects data about its activities that you may need to
access, primarily for troubleshooting purposes. This chapter describes
the various logs and reports you can access, in the following sections:
• Command Line Operations
• Displaying the Command Line Help Menu
• Viewing the SKM Server Software Version
• Capturing SKM Server Logs and Snapshots
• Displaying the End User License Agreement
• Turning Trace Level Logging On and Off
• Displaying SKM Server Reports
• List of Key Aliases (Option 2)
• Display Key Template Information (Option 3)
• Viewing the SKM Encryption Key Import Warning Log
Capturing the Snapshot The most efficient way to collect the logs from the SKM server is to do
From the Command so from the command line. This method is quicker and does not stop
Line Without Stopping the SKM server.
the Server 1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
Capturing the Snapshot An alternative method of collecting the SKM server logs is via SKM
Using SKM Admin Admin Commands. This method stops the SKM server. Normally you
Commands would not choose this method, but if the SKM server is stopped anyway
and you want to capture the logs at the same time, you can do so.
1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Enter 3 to Capture SKM server snapshot.
The logs are gathered and placed into a single .tgz file:
/home/akmadmin/
skm_logcapture_<serial number><date>_<time>.tgz
4 Use secure file transfer protocol (SFTP) to copy the file to a desired
location.
Accessing SKM Server To access the SKM server reports complete the following:
Reports
SKM 1.x
1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Issue the following command:
akmadmin 1037 | grep '^EK' | wc -l
The number of keys in the keystore displays.
SKM 2.x
1 Log on to the SKM server command line interface (see Logging on
to the Command Line Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 At the Command prompt, type v for View SKM server reports and
press <Enter>.
4 The SKM Server Reports menu displays (see Figure 26).
Number of SKM Server To list the number of SKM server keys complete the following:
Keys (Option 1)
List of Key Aliases This option displays a list all of the keys in the keystore. You should only
(Option 2) need to bring up this list if directed to do so by Quantum Support.
Looking at the key names can help verify whether the keys are being
copied from one server to the other. Keys generated on the primary
server begin with EKA and keys generated by the secondary server begin
with EKB. The server should contain keys that begin with both “EKA”
and “EKB”.
To view a list of all of the data encryption key aliases:
1 Type 2 at the SKM Server Reports menu and press <Enter> to
display the list of keys and their aliases.
The list displays (see Figure 28). The keys are all displayed in order,
with the “EKA” keys displayed first.
Display Key Template You should not need to run this report unless directed by Quantum
Information (Option 3) Support for troubleshooting. This report displays one template for each
library that is attached to the SKM server and is useful for seeing how
many libraries are attached. You can also look at the Next increment
value to see whether any keys have been used. If it is at “000000”, no
keys from that template have been used yet.
To view template information:
1 Type 3 at the SKM Server Reports menu and press <Enter> for
template information.
The template information displays (see Figure 29).
Figure 29 Template
Information With Next
Increment Identified
3 When “End” displays (Figure 33), type q and press <Enter> to quit
the SKM server reports menu.
Note: Scalar i6000, i3, i6, and i6H libraries reserve the first 33 keys for
key per partition use by the library (i.e.
EKA00E09E000000000000-EKA00E09E000000000000). The
first 33 keys of each template will show up as used in the
report.
1 Type 7 at the SKM Server Reports menu and press <Enter> for used
key information.
The used key information displays (see Figure 34).
See your library user’s guide or online help for instructions on how to
view the SKM Encryption Key Import Warning Log.
Note: Use the Enter key, Page Up/Down keys, or Up/Down arrows to
access additional information.
There are certain SKM operations and functions you need to perform
using your library remote Web client. These operations include:
• Generating Data Encryption Keys
• Importing TLS Communication Certificates on the Library
• Exporting and Importing Data Encryption Keys
• Exporting and Importing Encryption Certificates
• Sharing Encrypted Tapes Offsite
• Running EKM Path Diagnostics
In addition, you must initially configure your library to work with the
SKM servers. This is described in Configuring Your Library For SKM on
page 100.
This document provides an overview of SKM library functions. For more
detail and specifics, see your library user’s guide.
Note: Each library that you connect to an SKM server requires its own
set of data encryption keys. Each library only pulls data
encryption keys from the set that “belongs” to it. This means
that an SKM server may contain several distinct sets of data
encryption keys. When the data encryption keys for one library
have all been used, then more keys must be generated.
Generating Data At initial setup, the library triggers each SKM server to generate a set of
Encryption Keys at data encryption keys. The process is described in the following sections:
Initial Setup
Scalar i40 Step 6 on page 102, in section Configuring the
Scalar i80 Scalar i500 Tape Libraries
Scalar i500
Automatically When an SKM server has used 80 percent of the data encryption keys
Generating Data assigned to a particular library, that library attempts to automatically
Encryption Keys When generate data encryption keys on the SKM server. Both SKM servers
80% Depleted must be running and operational in order for key generation to succeed.
Generating Data If an SKM server completely runs out of data encryption keys for a
Encryption Keys When particular library, that library generates a RAS/diagnostic ticket, which
100% Depleted states that you have run out of data encryption keys and that the library
attempted to fail over to the other SKM server. If this happens, it is
imperative that you manually generate a new set of data encryption
keys on the depleted server immediately and then back up both SKM
servers. See Manually Generating Data Encryption Keys on page 157.
Manually Generating To manually generate data encryption keys, you need to temporarily
Data Encryption Keys disable library managed encryption on a partition, and then enable it
again. Enabling library managed encryption on a partition triggers the
library to check both SKM servers to see if new data encryption keys are
needed. If so, it creates the keys.
Note: Beginning with SKM 2.5, TLS certificates are no longer pre-
installed, and must be install on both the SKM server and tape
library.
Note: You must use the SKM Admin menu to export and import
encryption certificates.
Note: You must use the SKM Admin menu to share encrypted tapes
offsite.
Note: See your library user’s guide for a description including menu
paths to the appropriate screens.
In SKM, functions that were once only available on the library can now
be executed from the SKM command line interface. These operations
include:
• Exporting Encryption Certificates
• Importing Encryption Certificates
• Exporting All Encryption Keys
• Importing All Encryption Keys
• Exporting All Used Encryption Keys
• Importing All Used Encryption Keys
• Exporting Used Keys Based on Media Barcode
• Importing Used Keys Based on Media Barcode
Administrators using SKM 2.0 or older can download a utility script
which will add the new import and export functionality to their existing
SKM server installation. See Installing the Import/Export Utility on
page 234.
You must initially configure your library to work with the SKM servers.
This is described in Configuring Your Library For SKM on page 100.
This document provides an overview of SKM server functions.
Note: Native certificates will not be available if keys have not yet been
generated on the server.
See your library user’s guide or online help for instructions on exporting
and importing encryption certificates using your library.
Please see to Figure 37 on page 164 as a visual aid to completing this
procedure. The libraries and servers shown in Figure 37 on page 164 are
referenced in this procedure.
1 Secure copy the certificate file to the server you want to import the
certificate to.
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Type k and press <Enter>.
The IP Address prompt displays.
4 Type the IP address of the secondary SKM server associated with the
one you are running commands from (SKM server 2b in Figure 37
on page 164 ). Press <Enter>.
The Key/Certificate import and export displays.
Exporting All You can export all encryption keys associated with a library.
Encryption Keys 1 Log on to the first server pair’s primary server (1a) SKM server
command line interface (see Logging on to the Command Line
Interface on page 110).
Importing All 1 Log on to the first server pair’s primary server (2a) SKM server
Encryption Keys command line interface (see Logging on to the Command Line
Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Type k and press <Enter>.
4 Type the IP address of the primary server in the second server pair
(SKM server 2b in Figure 20 on page 98) you want to import the
certificate to and press <Enter>. For example, type 10.20.80.110
and press <Enter>.
5 Type 2 and press <Enter>.
Exporting All Used You can export all used encryption keys associated with a library.
Encryption Keys 1 Log on to the first server pair’s primary server (1a) SKM server
command line interface (see Logging on to the Command Line
Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Type k and press <Enter>.
The IP address of the SKM server command line displays.
4 Type the IP address of the remote SKM server (SKM server 1b in
Figure 37 on page 164 ) and press <Enter> to show the Import/
Export submenu.
5 Type 2 and press <Enter> to export the Encryption Key.
The Key import and export menu displays.
6 Type e and press <Enter>.
The Exporting keys menu displays.
7 Choose the menu item number corresponding to the Certificate file
that the keys you want to export are associated with. Type the menu
item number and press <Enter>.
The Exporting keys menu displays.
Importing All Used 1 Log on to the first server pair’s primary server (2a) SKM server
Encryption Keys command line interface (see Logging on to the Command Line
Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
Exporting Used Keys You can export the last data key associated with a specific media
Based on Media barcode on the library.
Barcode 1 Log on to the first server pair’s primary server (1a) SKM server
command line interface (see Logging on to the Command Line
Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Type k and press <Enter>.
The IP address of the SKM server command line displays.
4 Type the IP address of the remote SKM server (SKM server 1b in
Figure 37 on page 164 ) and press <Enter> to show the Import/
Export submenu.
5 Type 2 and press <Enter> to export the Encryption Key.
The Key import and export menu displays.
Importing Used Keys 1 Log on to the first server pair’s primary server (2a) SKM server
Based on Media command line interface (see Logging on to the Command Line
Barcode Interface on page 110).
2 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
3 Type y and press <Enter> twice
4 Type k and press <Enter>.
5 Type the IP address of the primary server in the second server pair
(SKM server 2b in Figure 20 on page 98) you want to import the
certificate to and press <Enter>. For example, type sftp
10.20.80.110 and press <Enter>.
6 Type 2 and press <Enter>.
7 Type i and press <Enter>.
The import process begins. When the process is complete, the Key
file list available for import menu displays.
8 Press <Enter> to display the Key export options menu.
9 Type q and press <Enter> twice to display the Exiting key export
message.
10 Press <Enter> to display the Key import and export menu.
11 Type q and press <Enter> twice to display the Key/Certificate
import and export menu.
12 Type q and press <Enter> twice to quit and return to SKM Admin
Commands.
Question Answer
How can I tell if the SKM server is Run EKM Path Diagnostics test from the library. If all tests
running? pass, the SKM server is running.
What is the difference between AME is not part of SKM. In AME, the ISV application
Application-Managed Encryption (AME) manages the interaction with the encryption-capable
and Library-Managed Encryption (LME) drive. The ISV application may or may not encrypt data.
and how do they work? With LME, the library (with the SKM server) manages the
interaction with the encryption-capable tape drive. LME
does not require any ISV support and is transparent to
the application.
What state must the media be in to be The media must be either blank or erased. If any
encrypted using SKM? unencrypted data is on the media, appended data will
not be encrypted.
If the media contains anything other than LME-encrypted
data, the data must be erased. Interleaving LME data
with non-encrypted or AME-encrypted data is not
supported.
How can I verify that tapes are being The library interface provides several reports that indicate
encrypted using SKM? which tapes are encrypted. See your library user’s guide
for details.
How can I tell which tapes are encrypted The library interface provides several reports that indicate
and which are not encrypted? which tapes are encrypted. See your library user’s guide
for details.
How will I be notified of write/read SKM does not report these types of errors. Errors are
errors? reported in the following ways:
• The host/ISV application reports read and write
failures.
• The library may issue a RAS/diagnostic ticket when a
write or read operation fails.
How will I be notified of SKM server The library issues a RAS/diagnostic ticket.
problems?
Question Answer
How will I know if one of the SKM The library issues RAS/diagnostic tickets when a server
servers in a pair goes down and fails failed and successfully failed over to the redundant server.
over to the other one?
How will I know if just the secondary When the library is power-cycled, it attempts to contact
SKM server goes down (while the both SKM servers. If one or both servers cannot be
primary is still working fine)? contacted, the library generates a RAS/diagnostic ticket.
During regular use, if Automatic EKM Path Diagnostics is
enabled, the library will issue a RAS ticket if it cannot
communicate with the secondary SKM server. If
Automatic EKM Path Diagnostics is not enabled, then you
will not be notified.
Note: Automatic EKM Path Diagnostics is enabled by
default and should be left enabled.
SKM 2.7 Appliance The two drives within the SKM 2.7 appliance server are located in Slot 0
Server (and later and 1 (left front). Refer to Figure 38 and Figure 39.
versions)
Figure 39 SKM 2.7 Appliance The Ethernet ports on the rear of the server are as follows:
Server Rear Panel
• Unmarked port (far left: port) 10/100/1000 Mb Ethernet port
• Port 1 (middle port): 1GbE port
• Port 2 (far right: port): 1GbE port
SKM 2.6 Appliance The LEDs on the front of the SKM appliance server can signal problems
Server (and earlier with the server. Figure 41 shows the location of the LEDs, and Table 2 on
versions) page 185 describes what the LED error codes mean. For additional
explanation of all the LEDs and their functions, see SKM 2.6 Appliance
(and Earlier Versions) on page 19.
Hard disk
drive status
LED
Hard disk
drive status
LED
Power-on LED Green Blinking Server is powered off but is still connected to an
AC power source. Power ON the server by pressing
the power button.
Server error LED Amber On solid This LED illuminates during hard disk drive
(with replacement when a hard disk drive is missing
exclama- from its slot. It should go off again when the hard
tion disk drive is replaced.
point) If this LED is illuminated and both hard disk drives
are properly installed, there is a problem with the
server. Contact Quantum Support.
Hard disk drive Amber On solid The hard disk drive is faulty and must be replaced.
status LED Contact Quantum Support.
More than one beep; POST detected a problem with the server.
any sequence of Contact Quantum Support.
beeps.
Troubleshooting Guide
Table 3 provides a list of problems and actions you can take to resolve
them.
Symptom Action
A problem occurs only occasionally Make sure that all cables and cords are connected securely to
and is difficult to diagnose. the rear of the server and attached devices.
Symptom Action
The SKM appliance server does not Make sure that the power button is working correctly:
boot up. The power button does 1 Disconnect the server power cords.
not work, and the reset button
2 Reconnect the power cords.
does work.
3 Press the power button.
Note: The power button will not
function for 20 seconds to three 4 If the server does not start, replace the server. Contact
minutes after the server has been Quantum Support for assistance.
connected to AC power.
The SKM appliance server 1 Make sure the power cord is connected to the server and
unexpectedly shuts down, and the plugged in to a working power source.
LEDs on the front panel are not on. 2 Turn the server back on and check the airflow from the fan.
When the server is powered on, air is flowing from the fan
grille. If there is no airflow, the fan is not working. This can
cause the server to overheat and shut down.
3 Contact Quantum Support for SKM server replacement.
The SKM appliance server fan is It is normal for the fan to be very noisy during initial startup for
very noisy. about 20 seconds, after which the fan should become quieter.
If the fan does not quiet down after about 20 seconds, contact
Quantum Support.
Symptom Action
The library cannot communicate Check all of the following. If you have tried all of these items
with the SKM server. and the problem still exists, contact Quantum Support.
• Check to see if there are any RAS/diagnostic tickets on the
library relating to SKM. If so, follow any instructions listed in
them.
• Verify IP address on the SKM server and make sure it is
configured correctly on the library.
• Ensure the SKM server Ethernet cables and power cords are
attached.
• Ensure that the SKM server is powered on and is running. If
you are currently accessing SKM Admin Commands, the
server will be stopped. Make sure to quit SKM Admin
Commands.
• Check the LEDs on the SKM appliance server and hard disk
drives to make sure that none indicate errors (see LED Error
Indicators on page 181).
• Make sure the date on both SKM servers and the library is
set to the current date. Incorrect date settings may interfere
with the TLS certificates and cause the library to stop
communicating with the SKM servers.
• Ensure that SKM TLS communication certificates are
installed on the library. If they are not installed, install them.
See your library user’s guide or online help for instructions.
Symptom Action
The library cannot communicate • Ensure the following ports are open in a bi-directional mode
with the SKM server (continued). on all firewalls in your network: 80, 6000, and 6001.
To verify port 80 is open:
1 Ping the SKM server’s IP address.
2 If the ping succeeds, then open a Web browser and type the
IP address in the URL search bar (for example: http://
12.34.56.78). If port 80 is open, a page containing the text
“Quantum Scalar Key Manager (SKM)” will display.
3 If the page does not display, reboot the SKM server and try
again. (On the SKM appliance, press the reset button or
press and hold the power button for four seconds to power
off the server, then press the button to power on the server.)
If the page still does not display, the port is not open.
You forgot the password. There is no way to retrieve or reset a forgotten password. You
will need to replace your SKM server following the instructions
in the sections listed below. The replacement process includes
restoring the latest backup.
Symptom Action
You installed you own TLS SKM appliance server: Contact Quantum Support to obtain
communication certificates on the Quantum-provided TLS certificates, then install them following
SKM server, which overwrote the the instructions in Installing TLS Certificates on the SKM Server
Quantum TLS certificates. Now, for Pre-SKM 2.4 (240Q) on page 76.
you want to put the Quantum TLS SKM VM server: The Quantum-provided TLS certificates are
certificates back on. located on the Scalar Key Manager 2.2 VM Installation CD. If
you still have the CD, follow the instructions in Installing TLS
Certificates on the SKM Server for Pre-SKM 2.4 (240Q) on
page 76. If you no longer have the CD, contact Quantum
Support to obtain TLS certificates.
You receive the following error 1 Make sure that you are indeed using a 64-bit host server.
message when you power on the 2 If so, change the VM host BIOS processor settings as follows:
SKM VM server using vSphere: - 64-bit: Yes
“This kernel requires an x86-64 - Virtual Technology: Enable
CPU, but only detected an - Execute Disable: Disable
xxxx CPU. Unable to boot - please 3 Follow the onscreen instructions.
use a kernel appropriate for your
CPU.”
You receive an “Incorrect MAC 1 Using vSphere Client, power OFF the VM server (right-click
address” message during setup the VM server, select Power, then select Power Off).
and cannot run the ./skmcmds 2 Power ON the VM server (right-click the VM server, select
command. Power, then select Power On).
3 Click the Console tab, log on to akmadmin again, and
run ./skmcmds again.
Caution: Do not remove any hard drive from the appliance server
unless it is failed or you are instructed to do so by Quantum
service. Removing any hard drive may render it unusable.
Caution: Never remove more than one hard disk drive while the
system is powered up.
Figure 43 SKM 2.7 Appliance The Ethernet ports on the rear of the server are as follows:
Server Rear Panel
• Unmarked port (far left: port) 10/100/1000 Mb Ethernet port
• Port 1 (middle port): 1GbE port
• Port 2 (far right: port): 1GbE port
The amber hard disk drive status LED will be solidly illuminated on the
failed hard disk drive.
• See Figure 44 for location of amber LED illuminated on the failed
drive (Slot 0, Callout 1).
• Notice that the drive in Slot 1 (Callout 2) has a green LED (meaning
the drive is operational).
Hard disk
drive status
LED
Hard disk
drive status
LED
3 Pull open the drive handle on the failed hard disk drive and remove
the hard disk drive from the bay (see Figure 46 or Figure 47).
Note: The amber Server Error LED illuminates on the SKM 2.6
appliance server (and earlier versions), indicating a server fault
due to a missing hard disk drive.
The SKM 2.7 appliance server (and later versions) does not have
an LED.
Note: The amber hard disk drive status LED illuminates. (This LED
indicates the hard disk drive is “defective” because it is not
mirrored yet, and it should turn off once the RAID rebuild is
complete.)
b The green activity LED on the existing good hard disk drive
blinks, indicating it is being accessed.
c After about 5 seconds, the RAID rebuild begins, during which
the green activity LEDs on both hard disk drives blink very fast
so that they may appear to be on solid.
• Rebuild process:
- The replacement hard disk drive’s amber status LED blinks
once per second.
- The amber server error LED turns off as soon as the RAID
rebuild process starts.
• The RAID rebuild process may take up to 45 minutes.
d When the RAID rebuild is complete, the green activity LEDs on
both hard disk drives blink in unison either once every 16
seconds or several times rapidly every 16 seconds (depending
on server model).
9 When the RAID rebuild is complete, check the hard disk drive
LEDs to make sure that the hard disk drive is operating correctly.
• The amber hard disk drive status LED should be OFF.
• If it is still on, the drive is faulty, and you should contact
Quantum Support.
Caution: Do not use the failed hard disk drive in any other SKM
server.
Caution: Do not remove the hard disk drives from the replacement
server. You will replace the entire unit, including the hard
disk drives.
Required Items • Replacement SKM appliance server with two installed hard disk
drives.
• CAT5e crossover Ethernet cable for initial configuration (not
supplied).
• Laptop or PC to connect to the replacement server for initial
configuration.
• The latest saved backup taken from the failed SKM appliance server,
placed in a retrievable location (see Backing Up the SKM Server on
page 121).
• Remote access to a library that is connected to the SKM server.
2 If not already powered off, power OFF the failed server by pressing
the power button on the front panel and holding for four seconds.
3 Unplug the power cord and CAT5e Ethernet cable from the back of
the server.
4 Remove the server from the rack.
5 Install and configure the replacement server following the
instructions in Installing and Configuring the SKM Appliance Servers
on page 28.
Note: Only install and configure the replacement server; leave the
currently working SKM server as is.
Caution: Do not use the failed hard disk drives in any other SKM
appliance server.
Required Items • The latest saved backup taken from the failed SKM VM server,
placed in a retrievable location (see Backing Up the SKM Server on
page 121).
• Remote access to your library.
• The original .ova image and TLS certificates that you used when you
originally deployed and configured the failed SKM VM server. The
.ova and Quantum-provided TLS certificates are located on the
Scalar Key Manager 2.2 VM Installation CD. Make sure you use the
correct CD for the SKM VM server you are replacing.
• All of the items required for installation as described in Equipment
and Software Needed for VMware on page 39.
Procedure Caution: If you do not have a saved backup, call Quantum Support
before starting this procedure. This procedure deletes your
failed SKM VM server.
Caution: Quantum requires that you do not install any software, file,
or operating system on the SKM appliance server or SKM
VM server unless it is an upgrade or patch supplied by
Quantum. Doing so may make your server inoperable and
will void the warranty.
Note: Before you begin the upgrade, backup your SKM server, disable
LME on all partitions. Otherwise, the library will generate SKM
Server Mismatch RAS tickets when upgrading one server at a
time.
Upgrading from SKM To upgrade to SKM 2.6 and later, you must always one version back
2.6 Using the Remote from the current version you plan to upgrade to. For example, if you are
Script upgrading to SKM 2.6, you must currently be at version SKM 2.5.
Contact Quantum Support to request the appropriate upgrade package
file:
2.8 280Q.GC00800remoteinstall-pkg.sh.gz.
2.7 270Q.GC00600remoteinstall-pkg.sh.gz.
2.6 260Q.GC00600remoteinstall-pkg.sh.gz.
Copy the package file to one of the SKM servers in the pair to be
upgraded, and then use scp, winscp or sftp to place it in /home/
akmadmin.
1 Using putty or ssh, log into the SKM server using the akmadmin
account.
2 Execute the command:
SKM 2.8
gunzip 280Q.GC00800remoteinstall-pkg.sh.gz.
SKM 2.7
gunzip 270Q.GC00600remoteinstall-pkg.sh.gz.
SKM 2.6
gunzip 260Q.GC00600remoteinstall-pkg.sh.gz.
4 Execute the following command Use the same password you used
to log in to the akmadmin account.
SKM 2.8
sudo ./280Q.GC00800remoteinstall-pkg.sh.
SKM 2.7
sudo ./270Q.GC00600remoteinstall-pkg.sh.
SKM 2.6
sudo ./260Q.GC00600remoteinstall-pkg.sh.
5 When the End User License Agreement (EULA) appears, read the
agreement and then accept by entering y.
Note: After accepting the EULA, the upgrade begins. Refer to the
next screen.
6 When you are notified that the upgrade has completed successfully,
press Enter to reboot the SKM server. (It will take a few minutes for
the system to reboot.)
7 After the system reboot completes, log into the SKM server as
akmadmin using putty or ssh.
8 Once you log into the system, the new version should be displayed.
Note: Before you begin the upgrade, disable LME on all partitions.
Otherwise, the library will generate SKM Server Mismatch RAS
tickets when upgrading one server at a time.
7 When the End User License Agreement (EULA) appears, read the
agreement and then accept by entering y.
8 When you are notified that the upgrade has completed successfully,
press Enter to reboot the SKM server. (It will take a few minutes for
the system to reboot.)
9 After the system reboot completes, log into the SKM server as
akmadmin using putty or ssh.
10 Once you log into the system, the new version should be displayed.
12 Copy from the system the backup that was created after the
upgrade. (Backups created after the upgrade are saved at /home/
akmadmin/backups.)
Place this backup copy where you normally keep backups.
13 Repeat all steps for the second SKM server in the pair.
Upgrading Using an Use this installation method to install from a DVD rather than from a
Installation DVD script.
1 Create an installation DVD using the
SKM_2_5_250Q.GC00100_cdimage.iso available on CSweb.
2 Insert the installation DVD into the SKM server you want to
upgrade.
3 Use putty or ssh to log onto the SKM server using the akmadmin
account.
6 When prompted to insert the DVD into the server, press Enter. (You
already inserted the DVD in step 2.)
7 When the End User License Agreement (EULA) appears, read the
agreement and then accept by enter y. The upgrade begins after
you accept the EULA and press Enter.
8 When you are notified that the upgrade has completed successfully,
press Enter to reboot the SKM server. (It will take a few minutes for
the system to reboot.)
9 After the system reboot completes, log into the SKM server as
akmadmin using putty or ssh.
10 Once you log into the system, the new version should be displayed.
12 Copy from the system the backup that was created after the
upgrade. (Backups created after the upgrade are saved at /home/
akmadmin/backups.)
Place this backup copy where you normally keep backups.
13 Repeat all steps for the second SKM server in the pair.
Note: The library may generate RAS/diagnostic tickets while you are
performing this procedure. Once the upgrade is complete, you
can ignore and close the tickets.
Note: If no DVD is loaded, you are again requested for the DVD.
Load the DVD and press <Enter>, or type q and press
<Enter> to quit and return to SKM Admin Commands.
c Once the backup file is created, SFTP the backup file to a safe
location.
d At the Command prompt, type q and press <Enter> to quit
SKM Admin Commands.
14 Resume using backup applications.
15 Save the DVD in case you need to perform a rollback in the future.
New VM Requirements Version 2.0 requires the following on VM servers, which were not
for SKM 2.0 required in 1.0 or 1.1.
• 1 GB RAM
• Video memory must be set to 3 MB (not 4 MB)
Note: The library may generate RAS/diagnostic tickets while you are
performing this procedure. Once the upgrade is complete, you
can ignore and close the tickets.
Note: The name of the 1.0 (GA) version was Quantum Key Manager
(QKM). The name changed to Scalar Key Manager (SKM) with
1.1. Names of menu items and some commands will therefore
be different in version 1.0 and 1.1.
Procedure 1 Go to the Quantum SKM Web site to see if software updates exist
(click Firmware):
https://www.quantum.com/serviceandsupport/
softwareanddocumentationdownloads/skm/index.aspx
2 Contact Quantum Support to request the update. Quantum Support
will send you an ISO image containing the version of software you
request (the filename contains the version).
3 Burn the ISO image onto a CD.
4 Stop all applications that require key exchanges from the SKM
server pair.
5 Log on to the command line interface of one of the SKM servers (see
Logging on to the Command Line Interface on page 110).
6 Access QKM Admin Commands by issuing the following command:
./qkmcmds
7 At the Command prompt, type u to Update SKM server software.
8 Load the CD containing the ISO image into the SKM server’s CD
ROM drive and press <Enter>.
The upgrade process runs.
Note: The library may generate RAS/diagnostic tickets while you are
performing this procedure. Once the upgrade is complete, you
can ignore and close the tickets.
Note: The name of the 1.0 (GA) version was Quantum Key Manager
(QKM). The name changed to Scalar Key Manager (SKM) with
1.1. Names of menu items and some commands will therefore
be different in version 1.0 and 1.1. To access the main menu
after installing the utility, type skmcmds and enter the
administrator password.
Procedure 1 Contact Quantum Support to request the SKM 2.2 Utility. Quantum
Support will send you an ISO image containing the version of
software you request (the filename contains the version).
2 Download the Utility file to the computer hard drive.
3 Burn the Utility file onto a DVD.
4 Stop all applications that require key exchanges from the SKM
server pair.
5 Log on to the command line interface of one of the SKM servers (see
Logging on to the Command Line Interface on page 110).
6 Read and accept the End User License Agreement.
7 At the Command prompt, type sudo ./skmieupdate-pkg.sh to
install the Utility.
8 Load the DVD containing the ISO image into the SKM server’s DVD
ROM drive and press <Enter>.
The utility installation process runs.
akmadmin@skmserver:~$
12 Remove the DVD from the DVD ROM drive.
13 Repeat the above steps on the other SKM server.
14 Back up both SKM server keystores as follows:
a At the prompt, access SKM Admin Commands by typing
./skmcmds.
b At the Command prompt, type 7 to Back up keystore.
c Once the backup file is created, SFTP the backup file to a safe
location.
d At the Command prompt, type q and press <Enter> to quit
SKM Admin Commands.
15 Resume using backup applications.
Save the DVD in case you need to perform a rollback in the future.
The procedure that follows applies only to rolling back version 1.1 to
1.0.
Perform the procedure on one server at a time. Make sure it is complete
before rolling back the other server. This will protect you in case a
rollback fails, because the other server will be able to continue
operations while you are recovering.
Note: The library may generate RAS/diagnostic tickets while you are
performing this procedure. Once the rollback is complete, you
can ignore and close the tickets.
Note: The name of the 1.0 (GA) version was Quantum Key Manager
(QKM). The name changed to Scalar Key Manager (SKM) with
1.1. Names of menu items and some commands will therefore
be different in version 1.0 and 1.1.
Rolling Back From 1 Obtain the CD containing the currently installed version of software.
Version 1.1 to Version 2 Stop all applications that require key exchanges from the SKM
1.0 server pair.
3 Log on to one of the SKM servers and access SKM Admin
Commands (see Accessing SKM Admin Commands on page 111).
4 Access SKM Admin Commands (see Accessing SKM Admin
Commands on page 111).
5 At the Command prompt, type r to Roll back SKM server software.
6 Insert the CD into the SKM server’s CD ROM drive and press <Enter>.
The rollback process runs.
• If the wrong upgrade CD is loaded, the rollback stops and you
receive an error message. Press <Enter> to return to SKM Admin
Commands.
• If no CD is loaded, you are again requested for the CD. Load the
CD and press <Enter>, or type q and press <Enter> to quit and
return to SKM Admin Commands.
7 When the rollback completes, press <Enter> to return to SKM Admin
Commands.
8 At the Command prompt, type q to quit SKM Admin Commands.
9 Issue the following command to confirm that the rollback version is
loaded.
./skmcmds -v
The correct SKM Admin Commands version should appear on the
screen.
Rolling Back From The procedure that follows applies only to rolling back version 2.1 or
Version 2.1 or higher to higher to 2.0. These instructions are also in the Scalar Key Manager
Version 2.0 User’s Guide.
Perform the procedure on one server at a time. Make sure it is complete
before rolling back the other server. This will protect you in case a
rollback fails, because the other server will be able to continue
operations while you are recovering.
Note: The library may generate RAS/diagnostic tickets while you are
performing this procedure. Once the rollback is complete, you
can ignore and close the tickets.
Equipment Required
To perform this procedure, you need:
• Remote access to your library.
• Physical access to your SKM servers.
• The CD used to load the current version of software.
Procedure
1 Obtain the CD containing the currently installed version of software.
2 Stop all applications that require key exchanges from the SKM
server pair.
3 Log on to one of the SKM servers and access SKM Admin
Commands (see Accessing SKM Admin Commands on page 111).
4 At the Command prompt, type r to Roll back SKM server
software.
5 Insert the CD into the SKM server’s CD ROM drive and press
<Enter>.
The rollback process runs.
• If the wrong upgrade CD is loaded, the rollback stops and you
receive an error message. Press <Enter> to return to SKM
Admin Commands.
• If no CD is loaded, you are again requested for the CD. Load the
CD and press <Enter>, or type q and press <Enter> to quit
and return to SKM Admin Commands.
6 When the rollback completes, press <Enter> to access to SKM
Admin Commands.
7 At the Command prompt, type q to quit SKM Admin Commands.
8 Issue the following command to confirm that the rollback version is
loaded.
./skmcmds -v
The screen should display this version: 200Q.GC01400
9 Remove the CD from the CD ROM drive.
If you are running SKM and you need to replace the control module in a
connected library (or the chassis in a Scalar i40/i80), you must run the
library serial number replacement script (named libreplac.py) on the
SKM server to ensure you do not lose “Export Used” key export
functionality.
The procedure is only necessary when the control module of a library
has been replaced because it changes the physical serial number of the
library so that it no longer matches what is in the metadata of the SKM
server.
If you replace one of the following types of modules, you will need to
run the script.
This process applies to both SKM appliance servers and SKM VM servers.
These steps must be performed on both servers in the pair. This chapter
covers:
/home/akmadmin
5 Log on to the command line interface of the SKM/QKM server (see
Logging on to the Command Line Interface on page 110).
6 Verify that the service script package servicescripts-pkg.sh is
located in the directory by issuing the following command:
ls -l
The /home/akmadmin directory should list servicescripts-pkg.sh.
7 Set the execute privilege for the package by issuing the following
command:
chmod 777 servicescripts-pkg.sh
8 Install the library serial number replacement script by issuing the
following command:
sudo ./servicescripts-pkg.sh
This installs the script (named libreplace.py) in the
/home/akmadmin/service directory.
9 Verify proper installation by issuing the following command:
ls -l /service
Confirm the /service directory lists the script named libreplace.py.
10 Remove the service script package from the /home/akmadmin
directory by issuing the following command:
rm servicescripts-pkg.sh
11 Back up the keystore as follows:
Caution: Be careful! Make sure you enter both the old and the
new library serial numbers correctly! Incorrect entries
will result in incorrect encryption key usage
associations.
Old Serial
Number
New Serial
Number
Caution: Be careful! Make sure you enter both the old and the
new library serial numbers correctly! Incorrect entries
will result in incorrect encryption key usage
associations.
Locating the Serial On the Scalar i3, the serial number label is located as follows:
Number on the i3 • On the inside of control module (CM).
• Left or right side of the chassis.
• You must remove the left or right magazine to view the serial
number.
• See Figure 50.
• You can also access the serial number from the WebGUI (Figure 52).
Locating the Serial On the Scalar i6, the serial number label is located as follows:
Number on the i6 • On the inside of control module.
• Left or right side of the chassis.
• You must remove the left or right magazine to view the serial
number.
• See Figure 53.
• You can also access the serial number from the WebGUI (Figure 52).
Locating the Serial On the Scalar i40/i80, the serial number label is located on the rear of
Number on the the chassis in the upper left corner. See Figure 56.
Scalar i40/i80 The Scalar i40 serial number is 10 digits long and starts with D0; for
example, D0H0029914.
The Scalar i80 serial number is also 10 digits long and starts with D1; for
example, D1H0029914.
You can also find the serial number on the library as follows:
• Operator panel — Select Reports > About Library.
• Web client — Select Reports > About > Scalar i40/i80.
Locating the Serial On the Scalar i500, the serial number label is located inside the control
Number on the module, on the horizontal bar at the back of the library. To see the label,
Scalar i500 open the front door. See Figure 57 for location and Figure 58 for an
example.
The serial number is listed first. The serial number is all of the characters
following the “%SN” on the serial number label. Do not enter the
“%SN” characters when typing the serial number into the SKM
command line.
You can also find the serial number on the library as follows:
• Operator panel — Select Tools > About Library.
• Web client — Select Reports > About > Scalar i500.
Locating the Serial On the Scalar i2000/i6000, the serial number label is located on the left
Number on the side of the library chassis from inside the rear of the library. See
Scalar i2000/i6000 Figure 59.
Serial Number Format: Serial numbers are nine digits. For new
manufactured Scalar i6000 libraries, the control module serial number
will begin with 2731 (for example, 273102351). However, a Scalar i2000
library upgraded to a Scalar i6000 will retain its original Scalar i2000
serial number (for example, 263104668).
The serial number is the nine digits following the “%SN” on the serial
number label. Do not enter the “%SN” characters when typing these
values on the SKM command line interface.
You can also find the serial number on the library as follows:
• Library Management Console — Select Monitor > System. The
serial number is in the ID column on the first line in the
Library:<library name> row.
Humidity
Server on 8% to 80%
SKM Appliance Server Approximate heat output in British thermal units (BTU) per hour in a
Heat Output typical configuration:
341 BTU per hour (100 watts)
VM Host Specifications
K keystore A database that contains the data encryption keys and their
associated metadata.
P private key One key in an asymmetric key pair, typically used for
decryption.
public key One key in an asymmetric key pair, typically used for
encryption.
C
D E
CD/DVD
drive activity LED 22 data encryption keys EKM path diagnostics 162
eject button 22 assignment 3
electrostatic considerations 16
depletion of 157
certificate exporting 160, 169 encrypted media 180
exporting 160, 166 generating 156 encryption
importing 160, 166 at initial setup 156 algorithms 4
certificates, encryption 5 automatic 157 asymmetric encryption 5
chassis replacement script 243 manual 158 certificate 5
importing 160, 169 keys 4
command line
list of 138 overview 2
help menu 130
number of 135 planning 9
logging on 110
reset button 21
O restoring the server 125
T
ova image 40 running out of keys 157 tape drive
encryption capable 2
encryption-enabled 2
tape drive code 264, 265
P S template, library 139
password serial connector 24 terminology 267
changing 35, 47, 56, 73, 115
serial number time zone, changing 117
lost 115, 189
Scalar i2000/i6000, locating time, setting 118
planning the SKM environment 9 258
Scalar i40/i80, locating 255 TLS certificates
POST beep codes 186
Scalar i500, locating 256 displaying on SKM server 119
POST error codes 186 installing on Scalar i40/i80/i500
SKM server, locating 190
power button 21 library 101
server installing on SKM server 76, 87
power cord connector 24 backing up 121 requirements, user provided 77
power failure 26 configuration 12
cover, opening 10 trace level logging 135
powering off the appliance server
26 error LED 21 troubleshooting 179
powering off 26
powering on the appliance server
powering on 26
26
replacing
private key 161, 164 appliance 201 U
public key 161, 164 VM 203
USB connectors 21, 24
publications xv restoring 125
software 131 user’s guides, library xvi
setup wizard 114
sharing encrypted tapes offsite 161,
Q 164 V
quitting 113 SKM
verbosity in logs 135
overview 2
process 3 video card settings 44
snapshot, capturing 132, 133 video connector 24
R
software
rack 11 version, SKM server 131
RAID rebuild 22, 185, 199 specifications 261
RAS tickets 185 symmetric encryption 5
rear panel, appliance server 22, 31 symmetric key 161, 164
replacement procedures systems-management connector 24
hard disk drive 194
library control module 243
SKM appliance server 201
SKM VM server 203