Resetting a node's password

Summary

Occasionally, you need to reset a TSM node's password. Here's how to do it.

Definitions

For this procedure, the following definitions apply:

MY-NODE

The name of the node you wish to update. Please use the fully qualified domain name of the machine in question.

SERVER

The TSM Server instance you are planning to use. For most local admins, the server in question is 'ext'. See the system structure document if you're unsure.

Procedure 1. Resetting a TSM node password. (command line)

  • Update the node's password

    Having connected to the correct SERVER, use the update node command:

      update node MY-NODE [new password] forcepwreset=yes

    now, perform procedure two to reacquaint client with server.

 

Procedure 2: re-introducing the node to the TSM server
  1. Initiate a client session from the target node


    On the client node, query the schedules with which the node is associated
    dsmc q sched


    this should result in a password transaction, in which you will have to enter the just-set password. You will see, amongst the connection diagnostics, an entry 'Password Updated'.

  2. Check that the password has been cached


    Run the q sched command again:

    dsmc q sched

    which should result in the same output, but not request a password, nor note a password update.

Bug.


We've seen an error condition occasionally, at least in Red Hat Linux installs. In this case, when you've just reset the password on the TSM server and attempt to run

 dsmc q sched 
you get an error:
ANS1262I Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
ANS1262I Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
I'm trying to hunt down this problem, but in any case a work-around is to remove the password cache on the client. This is usually
 
/etc/adsm/TSM.PWD
  1. remove the password cache
  2. reset the node password on the TSM server
  3. re-introduce the client to the server (as in procedure 2 above)