change the password of a Client Node

[spyderlinux]

Gentlemen,

How to proceed to change the password of a Client Node via Command Line?

 

[moon-buddy]

From the client or node:

Open the command line by using dsmc.

Enter:

SET Password old_password new_password

 

[spyderlinux]

And if not know and password

 

[n9hmg]

In the admin client: "upd node <nodename> <password>"
Then you can use that new password from the client side.

 

[spyderlinux]

When I go in and do TSM_SERVER:

After updated and will appear as the client to run dsmc and insert the username and password is the message below.
This is a mistake occurs or is this correct?


tsm:> update node zes-006 <PASSWORD_NEW>
Session established with server HYDRA: Linux/i386
Server Version 5, Release 3, Level 4.2
Server date/time: 07/16/2008 16:47:17 Last access: 07/16/2008 16:36:27

ANR2063I Node ZES-006 updated.


And When I go in TSM_CLIENT:

zes-006:/opt/tivoli/tsm/client/ba/bin # killall -9 dsmcad ; ps axf | grep dsmcad ; sleep 2 ; ./dsmcad
9112 pts/1 S+ 0:00 \_ grep dsmcad
zes-006:/opt/tivoli/tsm/client/ba/bin # ps axf | grep dsm
9121 pts/1 S+ 0:00 \_ grep dsm
9116 ? Sl 0:00 ./dsmcad

zes-006:/opt/tivoli/tsm/client/ba/bin # dsmc
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 4.0
Client date/time: 07/16/2008 16:48:28
(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

Node Name: ZES-006
Please enter your user id <ZES-006>: admin

Please enter password for user id "ADMIN":

Password updated.

ANS1352E The session is rejected. Your password has expired.

zes-006:/# dsmc

IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 4.0
Client date/time: 07/16/2008 16:48:35
(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

Node Name: ZES-006
Session established with server HYDRA: Linux/i386
Server Version 5, Release 3, Level 4.2
Server date/time: 07/16/2008 16:48:16 Last access: 07/16/2008 16:48:14

tsm> ANS2820E An interrupt has occurred. The current operation will end and the
client will shut down.



Why is this error message ?

 

[moon-buddy]

Why are you entering:

Node Name: ZES-006
Please enter your user id <ZES-006>: admin ??

the node is ZES-006 and the userid is NOT admin

enter ZES-006 as the node's userid.

 

[spyderlinux]

Let's see if I understood the procedures that have made daily.

I changed the password from the node (zes-006) within the web console example: admintsm
then it is the node zes-006 and password admintsm.
Since that when I go to log TSM to manage it and use the user admin password admintsm

When I access the client machine, killing the PID of the process of dsmcad and then start it again.
To test the connectivity that customer I type the command:
dsmc that tries to connect to TSM server.

And asks the user node where I tell admin which is the same user that I use to verify the processes in the TSM itself.

Because I let my user within the customers? Because at that point I want to reduce the problems that I am taking the backups are not made.

I am making procedure in an inappropriate manner?
I ask this because I am learning alone the administration of TSM and many questions about the procedure just taking.

 

[n9hmg]

kill the cad on the client
set the password via an admin client
on the client, dsmc
accept the default node id of zes-006 at the "Please enter your user id <ZES-006>:" prompt.
enter the new password. The one you just defined as the password of the node, not your administrative password.
go through the password change if that's how you're set up.
Once that works, restart the cad on the client.

 

[spyderlinux]

Trying to change the password via the command line.

tsm: HYDRA>update node ZES-005 admintsm
ANR2150E UPDATE NODE: Node ZES-005 is currently accessing the server.
ANS8001I Return code 12.


How to proceed because information that is in use.
But that backup would have to have happened as 2 o'clock in the morning and so far meets with status in progress.

And in the logs does not accuse any error that backup.

 

[moon-buddy]

Do a q sess and see if the node is accessing the TSM server. If it is, find out why and cancel if appropriate.