• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Clients can't connect

chad_small

ADSM.ORG Moderator
#1
I have run into an issue after upgrading a SP server from 8.1.0.0 to 8.1.8.0. The issue is that the SP server shows a ton of the following errors...

08/22/2019 10:33:34 ANR3334W The server experienced a TCP/IP error while
receiving data on socket 229. Reason 73, Origin
Address 10.106.4.174:1501. (SESSION: 29)
08/22/2019 10:33:35 ANR3334W The server experienced a TCP/IP error while
receiving data on socket 230. Reason 73, Origin
Address 10.106.9.0:1501. (SESSION: 29)
08/22/2019 10:33:36 ANR3334W The server experienced a TCP/IP error while
receiving data on socket 232. Reason 73, Origin
Address 10.106.8.229:1501. (SESSION: 29)
The clients that are failing are all 8.1.4. Those that were 8.1.0 or 7.1.x all work fine. All clients have SESSIONSEC=TRANSITIONAL. If I go by the reason code then the API is saying incompatible client??? Here are sample errors from the dsmerror.log.

08/22/2019 08:36:54 ANS9020E A session could not be established with a IBM Spectrum Protect server or client agent. The return code is -362.
08/22/2019 08:36:54 ANS1029E Communication with the IBM Spectrum Protect server is lost.
08/22/2019 08:56:54 ANS1579E GSKit function gsk_secure_soc_init failed with 406: GSK_ERROR_IO
08/22/2019 08:56:54 ANS9020E A session could not be established with a IBM Spectrum Protect server or client agent. The return code is -362.
08/22/2019 08:56:54 ANS1029E Communication with the IBM Spectrum Protect server is lost.
So the clients don't show having a cert db created. I asked the admins to put the

SSLACCEPTCERTFROMSERV YES

But they said it didn't work. I really don't want to have to walk them through adding the cert to every client using dsmcert.
 

chad_small

ADSM.ORG Moderator
#4
ANR3334W is a new message since 8.1.7 or 8.1.8 (doesn't show in the message list for 8.1.6 or lower. Unfortunately it doesn't provide much to go on...
 

chad_small

ADSM.ORG Moderator
#5
OK we ientified the issue. The Network team was blocking SSL at the firewall. So once they applied a rule to allow SSL the 8.1.4 clients worked without issue. The one thing that kind of makes sense now is the ANR3334W error was showing the client IP attempt to connect but SP could not identify the node since no information was allowed to be exchanged.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 16 18.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 52 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.8%
  • Other (please comement)

    Votes: 7 8.2%

Forum statistics

Threads
31,447
Messages
133,958
Members
21,547
Latest member
Ramsol
Top