Resolution
1. Perform “DR079: Resolve Key Server Communication Issue” on page
6-83.
2. Perform EKM Path Diagnostics (Tools → Diagnostics → EKM → EKM Path
Diagnostics in the Web User Interface).
3. If the "Ping" test is unsuccessful, look for physical connection problems
and down server(s).
4. If "Ping" is successful, then do the following:
a. Verify that EKM is running.
b. Verify that the media is not from a different EKM environment.
c. Verify that the key server is present.
.
T027: Key Server Communication Failure
Description GUI Description: The library is unable to communicate with the configured
key server(s).
Explanation: The key management feature of the library allows the user to
connect to two key servers for redundancy. If communication to one of these
servers fails and a communication failover is not possible or not successful,
then this ticket will be generated. A separate ticket will be created for each
key server that fails..
Detection Scenarios Library detects that communication with a key server is not successful
Root Causes
1. Primary/Secondary Key Server is not connected properly.
2. Primary/Secondary Key Server is not configured properly.
3. Library Ethernet settings are not configured properly.
Resolution
1. Perform “DR079: Resolve Key Server Communication Issue” on page
6-83.
2. Perform EKM Path Diagnostics (Tools → Diagnostics → EKM → EKM Path
Diagnostics in the Web User Interface).
3. If the "Ping" test is unsuccessful, look for physical connection problems
and down server(s).
4. If "Ping" is successful, then do the following:
a. Verify that EKM is running.
b. Verify that the media is not from a different EKM environment.
c. Verify that the key server is present.
T028: Secondary Key Server Failover
Description GUI Description: The library performed a successful communication failover
to the primary key server.
Explanation: The key management feature of the library allows the user to
connect two key servers for redundancy. If communication to the secondary
server is interrupted, then the library will automatically switch or failover to
the primary server. This RAS ticket will be generated to notify the user that
communication to the secondary key server failed and that the library
performed a successful failover to the primary key server.
Detection Scenarios When the library detects that it can no longer communicate with the
secondary key server and automatically switches to the primary key server
where it established successful communication.
6-16 TS3310 Tape Library Maintenance Information
To Next Page
Loading...
Need help?
General
