We are setting up a backup on a cluster and when we configure the Scheduler Service on Node 1 (or Node 2 for that matter) we type the following command:
C:\Program Files\Tivoli\TSM\baclient>dsmcutil install sched /name:"TSM Scheduler Service: Server-A" /clientdir:"C:\Program Files\Tivoli\Tsm\Baclient" /optfile:Q:\TSM\DSM.OPT /node:Server-A /password:hello /validate:yes /autostart:yes /clusternode:yes /clustername:SERVERCLU
After typing this I get the following confirmation that everything was successful:
TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.
Last Updated May 24 2002
TSM Api Verison 5.1.1
Command: Install TSM Client Service
Machine: Server(Local Machine)
Locating the Microsoft Cluster Server service ...
Installing TSM Client Service:
Machine : Server
Service Name : TSM Scheduler Service: Server-A
Client Directory : c:\program files\tivoli\tsm\baclient
Automatic Start : yes
Logon Account : LocalSystem
The service was successfully installed.
Creating Registry Keys ...
Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'TSM Scheduler Service: Server-A' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ClusterNode' .
Updated registry value 'ClusterGroupName' .
Generating registry password ...
Authenticating TSM password for node Server-A ...
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Password authentication successful.
The registry password for TSM node Server-A has been updated.
Starting the 'TSM Scheduler Service: IDXRADDB-A' service ......
The service was successfully started.
After doing this the password should have been set to hello, however when I issue the following command :
C:\Program Files\Tivoli\TSM\baclient>dsmcutil showpw /name:"TSM Sched
e: SERVER-A" /optfile:q:\tsm\dsm.opt /node:SERVER-A
I get back the following results:
TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.
Last Updated May 24 2002
TSM Api Verison 5.1.1
Command: Display Registry Password
Machine: Server(Local Machine)
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Registry password for node Server-A = '2' .
Authenticating password with TSM for node Server-A ....
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Authentication of the specified password failed .
Password Authentication failed.
WHY WAS THE PASSWORD CHANGED TO 2. Removed the service and tried it again and I get something different everytime. One time it was P1| I dont see where this comes from. But because of this my service fails with a incorrect password in the dsmerrorlog.
DSMERRORLOG
10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
10/03/2002 09:05:51 sessOpen: Error 137 from signon authentication.
10/03/2002 09:06:07 sessOpen: Error 137 from signon authentication.
ANY ADVICE!
C:\Program Files\Tivoli\TSM\baclient>dsmcutil install sched /name:"TSM Scheduler Service: Server-A" /clientdir:"C:\Program Files\Tivoli\Tsm\Baclient" /optfile:Q:\TSM\DSM.OPT /node:Server-A /password:hello /validate:yes /autostart:yes /clusternode:yes /clustername:SERVERCLU
After typing this I get the following confirmation that everything was successful:
TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.
Last Updated May 24 2002
TSM Api Verison 5.1.1
Command: Install TSM Client Service
Machine: Server(Local Machine)
Locating the Microsoft Cluster Server service ...
Installing TSM Client Service:
Machine : Server
Service Name : TSM Scheduler Service: Server-A
Client Directory : c:\program files\tivoli\tsm\baclient
Automatic Start : yes
Logon Account : LocalSystem
The service was successfully installed.
Creating Registry Keys ...
Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'TSM Scheduler Service: Server-A' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ClusterNode' .
Updated registry value 'ClusterGroupName' .
Generating registry password ...
Authenticating TSM password for node Server-A ...
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Password authentication successful.
The registry password for TSM node Server-A has been updated.
Starting the 'TSM Scheduler Service: IDXRADDB-A' service ......
The service was successfully started.
After doing this the password should have been set to hello, however when I issue the following command :
C:\Program Files\Tivoli\TSM\baclient>dsmcutil showpw /name:"TSM Sched
e: SERVER-A" /optfile:q:\tsm\dsm.opt /node:SERVER-A
I get back the following results:
TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.
Last Updated May 24 2002
TSM Api Verison 5.1.1
Command: Display Registry Password
Machine: Server(Local Machine)
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Registry password for node Server-A = '2' .
Authenticating password with TSM for node Server-A ....
Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...
Authentication of the specified password failed .
Password Authentication failed.
WHY WAS THE PASSWORD CHANGED TO 2. Removed the service and tried it again and I get something different everytime. One time it was P1| I dont see where this comes from. But because of this my service fails with a incorrect password in the dsmerrorlog.
DSMERRORLOG
10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
10/03/2002 09:05:51 sessOpen: Error 137 from signon authentication.
10/03/2002 09:06:07 sessOpen: Error 137 from signon authentication.
ANY ADVICE!