IBM Support

How to upgrade to Tivoli Storage Manager 7.1.x when SMB1 is disabled

Troubleshooting


Problem

A connection cannot be established because SMB1 is disabled or blocked.

Symptom

The upgrade panel prompts you for instance credentials. You enter the correct user name and password, but verification fails.

Cause

Remote Execution and Access (RXA) is likely failing for one of the following reasons:

  1. SMB1 is disabled or being blocked. For more information, see How to determine if SMB1 is active.
  2. The Remote Registry service is disabled.
  3. Firewalls are blocking the RXA protocol.
  4. Virus protection is enabled and possibly interfering with the RXA protocol.

Environment

Platform: Windows

Diagnosing The Problem

The install logs contain the following message:
java.net.ConnectException: CTGRI0001E The application could not establish a connection to localhost.
Install logs are located in the directory C:\ProgramData\IBM\InstallationManager\logs

Resolving The Problem

To resolve this problem, you can either fix the RXA failure, or manually upgrade each TSM server instance.

Solution one: Fixing the RXA failure

  1. Make sure SMB1 is enabled and is not being blocked. For more information, see How to activate SMB1.
  2. Make sure Remote Registry service is enabled.
  3. Make sure firewalls are not blocking the RXA protocol.
  4. If virus protection is enabled, make sure it is not interfering with the RXA protocol.

Solution two: Manually Upgrade the Instance(s).
  1. Collect the DB2 variables by using the following command:
    db2set -all
    Important: Save the command output to a file so you can recreate the variables. Later in these steps, you remove and recreate the DB2 instance. You need this file to recreate the variables for the new instance.
  2. Start the upgrade process. When you are prompted to update each TSM Instance, select No.
  3. After the upgrade is complete, upgrade the instance manually by completing the following steps:
    1. Issue the following command to remove the DB2 instance.
      db2idrop InstanceName
    2. Recreate each of the instances by using the following command:
      db2icrt InstanceName -u InstanceUsername 
      The command will prompt you for a password.
    3. From the DB2 variable file you created in step 1, create all of the DB2 variables.
      For example, to recreate the variable DB2_SKIPINSERTED, issue the
      following command:
      db2set -i tsminst1 "DB2_SKIPINSERTED=ON"
  4. Stop and Start the database instance, by issuing the following commands:
    db2cmd
    set db2instance=
    InstanceName
    db2stop
    db2start
  5. Catalog and upgrade each database name by issuing the following commands. The InstancePath is the drive that holds the instance directory. This may not necessarily be where the database is located.
    db2 catalog db DatabaseNameon InstancePath
    db2 upgrade db DatabaseName
  6. Stop DB2 by issuing the following command:
    db2stop
  7. Start and run the Tivoli Storage Manager server.

[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Supported Versions","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
17 June 2018

UID

swg22012840