The connection between the IBM Storage Protect server and the clients require the use of SSL to secure the connection. The IBM Storage Protect server also communicates with the IBM Storage Protect Plus server by using the SSL encrypted connection.
There are a number of reasons why the client's SSL certificates can become invalid. Though in most
cases the certificates are renewed automatically, in some cases you must resolve the problems that
are related to the certificates.
Before you begin
On the IBM Storage Protect server, update the value of the
SESSIONSECURITY parameter to TRANSITIONAL by issuing the
following command:
update node node_name sessionsecurity=transitional
Procedure
To resolve the connectivity problems, re-create the SSL certificates by completing the following
steps:
- Obtain the IBM Storage Protect server self-signed
certificate: cert256.arm.
Tip: Each IBM Storage Protect server stores its
certificate in the server’s instance directory similar to the following example:
/opt/tivoli/tsm/server/bin/cert256.arm.
- Copy this certificate into the IBM
Storage Protect
client installation directory.
- Stop any IBM
Storage Protect administrator and
backup-archive clients that are running on the affected system.
- From the IBM
Storage Protect client installation
directory, remove the following files, if they exist:
dsmcert.crl
dsmcert.idx
dsmcert.kdb
dsmcert.rdb
dsmcert.sth
- From the IBM
Storage Protect client installation
directory, issue the dsmcert command to import the
cert256.arm file with the correct server name. The command is similar to the
following
example:
dsmcert -add-server SERVER1 -file cert256.arm
where
SERVER1 is the name of the
IBM Storage Protect server.
The dsmcert command writes new dsmcert.* files.
- Issue the dsmc q session command to check the
connectivity.