ANS1361E Node name currently locked

tsmhelum

Active Newcomer
Joined
Aug 24, 2006
Messages
450
Reaction score
0
Points
0
Hi,

We have a Solaris 5.5.0.1 client node that missed with the messages below I found in the dsmerror and dsmsched.logs

I tried to Unlock the node using the TSM Gui UNLOCK THIS NODE” method to no avail. I am unable to start the DSMCAD process, has anyone experience this type issue before?


10/15/08 08:17:17 ANS1025E Session rejected: Authentication failure
10/15/08 08:17:17 ANS1570E Registering this instance of the Cad with the server failed. Cad process continues.
10/15/08 08:18:17 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 08:38:17 ANS1029E Communication with the TSM server is lost.
10/15/08 08:38:27 ANS1977E Dsmcad schedule invocation was unsuccessful. This command will be tried again in 10 minutes.
10/15/08 08:48:27 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 09:08:28 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 09:28:28 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 09:48:28 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 10:08:28 ANS1361E Session Rejected: The specified node name is currently locked
10/15/08 10:28:28 ANS1361E Session Rejected: The specified node name is currently locked


Thanks in advance!
 
On the TSM Server what does q node <node_name> f=d say?

If it says it is lock, unlock it using the TSM Server command line.
 
On the TSM Server command line:

UNLOCK NODE <nodename>

You might need to reset the password (UPDATE NODE <nodename> <password>) after that and enter it during startup of the TSM Client CLI/GUI.
 
Moon-buddy…thanks for your response!

I did the command as you suggested >>> q node <node_name> f=d and it did show that it was locked. I issued the unlock command from the TSM Server command line >>unlock node testuinep02 but it locked again.



Node Name: TESTUINEP02
Platform: SUN SOLARIS
Client OS Level: 5.9
Client Version: Version 5, release 5, level 0.1
Policy Domain Name: PRODUCTION
Last Access Date/Time: 10/16/08 09:27:27
Days Since Last Access: <1
Password Set Date/Time: (?)
Days Since Password Set: (?)
Invalid Sign-on Count: 3
Locked?: Yes
Contact: xxxxxxx
Compression: No
Archive Delete Allowed?: Yes
Backup Delete Allowed?: Yes
Registration Date/Time: 08/16/07 13:25:22

tail dsmsched.log

10/16/08 09:28:03 ANS1361E Session Rejected: The specified node name is currently locked
10/16/08 09:28:03 Will attempt to get schedule from server again in 20 minutes.
10/16/08 09:46:47 ANS2820E An interrupt has occurred. The current operation will end and the
client will shut down.
10/16/08 09:49:18 Scheduler has been started by Dsmcad.
10/16/08 09:49:18 TSM Backup-Archive Client Version 5, Release 5, Level 0.1
10/16/08 09:49:18 Querying server for next scheduled event.
10/16/08 09:49:18 Node Name: TESTUINEP02
10/16/08 09:49:18 ANS1361E Session Rejected: The specified node name is currently locked


The dsmsched.log is also showing the following. I updated the password using the TSM Gui and used the “Force password reset option” but it’s still doing the same thing.

10/16/08 10:09:18 Querying server for next scheduled event.
10/16/08 10:09:18 Node Name: TESTUINEP02
10/16/08 10:09:18 ANS1262I Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
10/16/08 10:09:18 ANS1262I Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
10/16/08 10:09:18 ANS1262I Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
10/16/08 10:09:18 ANS1029E Communication with the TSM server is lost.
10/16/08 10:09:18 Scheduler has been stopped.
 
Last edited:
It looks like you have password issues. Do a "q status" to find out the minimum length of the password you need.

Reset the password using the "update node" command from the TSM Server. Do a "help update node" for details.
 
Moon-buddy...Thanks that worked! I had to repeat the steps of entering the password and unlocking the node a couple of times for some reason. I killed and restarted the DSMCAD process twice but I finally got it to take...

Thanks again I appreciate your help!

tsmhelum
 
Back
Top