Key Path Diagnostics - IBM TS3310 Maintenance Information

Key Path Diagnostics

|
|
|
|
|
|
|
|
|
|
v Network settings:
– IP Address
– Subnet Mask & Gateway addresses
v Feature Code licenses keys
v Logical library configuration
v Cartridge slot assignments
v Cleaning slot configuration
v I/O Station configuration
v Drive IDs:
– SCSI ID
– Fibre Loop ID
– SAS ID
v Encryption method selections
v Administrator and user account information
From the Web User Interface: Service Library → Key Path Diagnostics
An Encryption Key path diagnostic function is provided to assist the
Administrative user in the setup, configuration, or troubleshooting of Library
Managed Encryption (LME) enabled libraries. This diagnostic consists of four tests:
1. Drive Test – This is a drive communication test to ensure that the Library-Drive
Interface (LDI) is functioning properly.
2. Ethernet Test – This is a key server 'ping' test of all IP addresses associated
with LME configured drives.
3. Key Path Diagnostic – This is a communication test used to establish a link to a
key manager and ensure that the communication paths between each drive and
the EKM have been correctly installed and setup.
4. EKM Config Test – This is a final test to establish a link to a key manager and
request a default key. This ensures that the drive has been correctly configured
in the EKM to service key requests.
To execute Key Path Diagnostics, from the web UI, go to Service Library → Key
Path Diagnostics and click Start Tests.
These tests are run sequentially on each IP address of each drive that is enabled for
LME. If a particular test fails, the subsequent tests for that same IP address are not
run, and the results will show N/A.
Note: The diagnostics tests may take several minutes to complete. To run any of
the tests, the tape drive used for the test must be unloaded, ready, and
online.
If any of the tests fail, try the following resolutions and run the test again to make
sure it passes:
v Ping Test Failure - Verify that the key server host is running and accessible from
the network the library is on.
Chapter 7. Service Procedures
7-13