Versions 7.1.8 and 8.1.3 of WDSF/ADSM/TSM/SP have now been made available containing substantial security upgrades. A bunch of security advisories were sent this week containing details of the vulner
Author: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
Date: Fri, 6 Oct 2017 09:19:57 +0200
Roger, There has been a discussion about a few things you are asking questions about just a day or so ago, I gave my view on the client and admin situation. I will use the same old and new definition
I spent some quality time digging through 7.1.8/8.1.3 docs yesterday and came to similar conclusions (my first thought was that 7.1.8 was just a maintenance release for 7.1.7 - did not realize they b
Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
Date: Fri, 6 Oct 2017 14:00:30 +0000
Content preview: We recently went from 7.1.7.300 to 7.1.8 in a 3-server environment (one library manager, two library clients). As always, do the library manager before any of the clients. We had som
Well, my testing of upgrading to 8.1.2/3 is not going well. Sure glad I am doing this on a test server, since it doesn't bode well for a production system. This is what we did in our testing. 1. Serv
Author: "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU>
Date: Fri, 6 Oct 2017 23:41:06 -0400
Hello all! I just discovered this thread today because I had been testing 8.1.1 server very recently. I had some issues with that on Thursday and then Friday I went further down the rabbit hole. Now
Thanks to all for this discussion of this 7.1.8/8.1.3 issue. I've heard enough to postpone our production upgrade to 7.1.8, scheduled for tomorrow. We've got to set up a test server and fiddle around
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Sat, 7 Oct 2017 17:29:33 -0400
Hello, See the reference information for REGISTER NODE and UPDATE NODE. Best regards, Andy ____________________________________________________________________________ Andrew Raibeck | IBM Spectrum P
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Sat, 7 Oct 2017 17:39:18 -0400
Hi Zoltan, I know you referenced http://www.ibm.com/support/docview.wss?uid=swg22004844 earlier, but have you gone back and revisited it? A couple of possible questions covered in that document: * If
before V7.1.8 or V8.1, then V7.1.8, V8.1.2, and V8.1.3 clients and the Operations Center are unable to connect to a V7.1.8, V8.1.2, V8.1.3 server We have never used/turned-on SSL on any of our SP/TS
Also, since SSLACCEPTCERTFROMSERV is on by default for 8.1.2 clients (*Specifies that the backup-archive client does automatically accept the IBM Spectrum Protect server's public certificate. Yes is
Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
Date: Mon, 9 Oct 2017 16:14:54 +0000
Content preview: I definitely agree with this; at least for TSM v7 it would have been far better to call it v7.2.0 to make it clear that it's a huge change with lots of caveats and potential failure
Author: "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU>
Date: Tue, 10 Oct 2017 10:00:09 -0400
I have one other question for any IBMers or people who may have had experience with this: If 8.1.2 clients can negotiate certificates with a 8.1.3 TSM server, does this mean that for users who use th
As I read it, "vendor-acquired certificates" need to be loaded/added to the server using the gsk8capicmd function. This link, while it's for 7.1.1, talks about it: https://www.ibm.com/support/knowled
Author: "Loon, Eric van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>
Date: Tue, 10 Oct 2017 15:06:11 +0000
Hi guys! I read all the discussions with interest and I'm getting more and more confused. I tend to shy away from installing the latest codes on my server and clients after seeing all the issues you
Author: "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU>
Date: Tue, 10 Oct 2017 11:58:22 -0400
My digicert signed certs are loaded into the server cert.kdb using the gsk8apicmd functions. That's working. My question was getting those non-existent root and intermediate CA certs loaded into the
That is probably due to: SSLACCEPTCERTFROMSERV - The default value Yes enables the client to automatically accept a self-signed public certificate from the server, and to automatically configure the
Author: "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU>
Date: Fri, 17 Nov 2017 13:55:44 -0500
I wanted to update this email thread with some of the gotchas that we have or are experiencing due to our upgrade from 7.1.7 to 8.1.3: - Watch out when using configuration management or a library man
Author: "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU>
Date: Fri, 17 Nov 2017 14:03:57 -0500
One thing I forgot to mention... if you use 3rd party CA certs anywhere, you'll want to store the password hash prior to performing the upgrade: Copy the password to clipboard In instance directory:
Author: Sasa Drnjevic <Sasa.Drnjevic AT SRCE DOT HR>
Date: Fri, 17 Nov 2017 20:11:06 +0100
First of all thank you so much for all the info! Can you please just clarify the following: "Licensing files need to be updated with the 8.1.0.x packages." Which/whose "Licensing files"? Client, serv