R: [ADSM-L] Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Tommaso Bollini
Same issue in my environment: these ba clients seems too old from 5.5 to all 6.2 clients. I found the nodes with: select * from actlog where (msgno='428' and severity='W' and originator='SERVER' and DATE_TIME >=current_timestamp -24 hours) I have tried the REG ADMIN and the use of

Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Saravanan Palanisamy
IT33437 Regards Sarav +65 9857 8665 > On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM > wrote: > > Hi Sarav, > > You stated " There is also one more issue on v8.1.10 where server will crash > abruptly if you use directory container. It appears to be known issue and we >

Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Loon, Eric van (ITOP NS) - KLM
Hi Sarav, You stated " There is also one more issue on v8.1.10 where server will crash abruptly if you use directory container. It appears to be known issue and we have got efix to address it". I find this very alarming, because I'm about to start production on a new server running this level.

Re: AW: [ADSM-L] Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Erwann SIMON
Thanks Andreas, you gave me the right clue. Shame on me, it's in the fine manual... https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.10/srv.common/r_techchg_allowdesauth_8110.html With IBM Spectrum® Protect Version 8.1.10, the default value of the ALLOWDESAUTH option is changed to NO.

Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Saravanan Palanisamy
Thanks Erwann for the update. We are still facing intermittent hang and no progress on our case. If it’s one server then we could say it’s environment issue but 3 different pair and all are in different countries as well. We are holding upgrade for rest of countries until find out root cause.

AW: [ADSM-L] Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Andreas Boesler
Hi Erwann, perhaps you need: setopt ALLOWDESAUTH YES Kind regards, Andreas. i. A. Andreas Boesler Consultant Tel: +49 6151 8290-7780 Mobil: +49 163 8075141 Fax: +49 6151 8290-7692 E-Mail:a.boes...@profi-ag.de PROFI Engineering Systems AG Otto-Röhm-Straße 18 64293 Darmstadt

Re: Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Erwann SIMON
Hi Eric, Thanks for tour quick reply. Unfortunately, sessionsecurity is already transitional (and has not move from this). I've tried an update anymway but it did not solved my issue. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Eric van Loon (ITOP

Re: Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Loon, Eric van (ITOP NS) - KLM
Hi Erwan, The ANS1357S error is always very confusing. In most cases where I got this error it was certificate related. Try and update one of the nodes with sessionsecurity=transitional and see if the error is gone. Kind regards, Eric van Loon Air France/KLM Storage & Backup -Original

Old clients cannot connect to 8.1.10 server

2020-08-20 Thread Erwann SIMON
Hi all, I've just upgraded dome servers from 8.1.8.200 to 8.1.10 and it helped a lot by solving some issues. Anyway, some old B/A Clients cannot connect anymore : they were backing up just fine to a 8.1.8 server but they cannot connect to a 8.1.10 one. For instance :

Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Erwann SIMON
Hello, I've just upgraded some servers to that level and I do not encounter this king of issue (right now...). -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Saravanan Palanisamy" À: ADSM-L@VM.MARIST.EDU Envoyé: Mardi 21 Juillet 2020 00:37:41 Objet: