Thanks James!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
James Thorne
Sent: Thursday, November 07, 2013 11:07 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Today's self-inflicted wound: IC90735
You see the following in the scheduler log the next time the scheduler attempts
to connect following the server upgrade:
18-07-2013 12:10:37 ANS2050E TSM needs to prompt for the password but cannot
prompt because the process is running in the background.
18-07-2013 12:10:37 ANS1029E Communication with the TSM server is lost.
18-07-2013 12:10:37 Scheduler has been stopped.
Note that after the server upgrade the schedulers on affected clients can be
restarted and should function correctly. This was not an option for us as we
have thousands of clients and do not have admin access on the client machines.
James.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Prather, Wanda
Sent: 07 November 2013 15:53
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Today's self-inflicted wound: IC90735
Curious.
What is the symptom when this happens? Does the client just get "invalid
password", or is there some other error message?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
James Thorne
Sent: Thursday, November 07, 2013 10:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Today's self-inflicted wound: IC90735
APAR IC90735 was created in response to a PMR I raised after hitting this
problem on a 6.2 to 6.3 server upgrade. It is referring to the encryption used
during authentication and only affects 6.3 and 6.4 clients; from IBM:
"this does not affect TSM Client versions below 6.3, for the following reason.
The client implemented AES for this authentication was in 6.3, and the 6.2
clients can only use DES, so that 6.3 server won't try to use AES with them."
This was fixed in baclient 6.3.1.2 and 6.4.0.5 (6.4.0.6 for Windows) so any
clients at or above those versions should not hit the problem.
James.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nick Laflamme
Sent: 06 November 2013 16:53
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Today's self-inflicted wound: IC90735
After a few uneventful upgrades from 6.2 to 6.3 TSM servers in my most recent
TSM shop, my first such upgrade for my current client hit IC90735:
some clients using encryption don't correctly change to AES-128 and thus are
rejected for invalid passwords.
The APAR led to client changes, not server changes, and I for one don't know
how to determine ahead if time which clients are using encryption.
So, if you still have an upgrade to TSM 6.3 server (or 7.1?!?), here's one more
concern to note.
Off to bandage my feet,
Nick
|
