TSM Client authentication problems

A small note-ette here for client authentication problems.

After trying the usual upd no commands on the TSM server for a node that doesn’t want to authenticate, including using forcep and passexp, I found a resolution by finding the TSM.PWD file and deleting it. This forces the client to re-encrypt the password based on the hostname (this might be because things can go screwy if you’ve got multiple stanzas in dsm.sys for cluster instances).

In this case TSM.PWD was in /etc/security/adsm, but it could be elsewhere.

Re-run dsmc q file (with the -optfile= if necessary) command to re-enter the nodename and password and you should now be ok.

About

I'm a freelance UNIX engineer working in the UK. I'm married to Tina and between us we have six children. I'm a bit of an Apple fan boy, and all the Windows machines in the house are a thing of the past now.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: