• 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.

ANR0443W after Client update

Sunhillow

ADSM.ORG Senior Member
Joined
Oct 27, 2003
Messages
402
Reaction score
16
Points
0
Location
Stuttgart, Germany
Hello altogether,

after updating most TSM clients to 81.114.000 there were lots of these warnings:
16.08.2022 12:39:53 ANR0443W Protocol error on session 613556 for node Unknown () - invalid "sessType" field found in "Negotiate" verb (offset 26).

In the meantime I updated the clients to 8.1.15.000, the warnings remain. So I think there is something new in the communication protocol. Fortunately all operations work like before!

Server version 8.1.15.000 has been released a few weeks ago, should I upgrade? Of better wait for the fitst fix?

Thanks for reading :)
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,788
Reaction score
625
Points
0
Location
Canada
Website
www.ibm.com
Are there any errors in the dsmerrror.log around 16.08.2022 12:39:53 on that client?
What type of client is it? Just regular client for file backup, or a TDP?
 

Sunhillow

ADSM.ORG Senior Member
Joined
Oct 27, 2003
Messages
402
Reaction score
16
Points
0
Location
Stuttgart, Germany
I do not find anything peculiar in the client log files. In the server actlog, I cannot even find from which IP address the session has been initiated.
These are regular BA clients. Most sessions are being produced by MAGS backups of our Isilons.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,788
Reaction score
625
Points
0
Location
Canada
Website
www.ibm.com
Since the error message in the actlog doesn't show the node_name, likely because the error happens before it identifies itself to the server, maybe you can proceed by process of elimination. Look for nodes that failed or missed their backup schedules and check their logs.
 

Sunhillow

ADSM.ORG Senior Member
Joined
Oct 27, 2003
Messages
402
Reaction score
16
Points
0
Location
Stuttgart, Germany
In some client logs I found many GSkit errors, but their timestamps are not corresponding with the protocol errors on the server. Will have to investigate them too. They also appear on Linux clients, which were not updated.
16.08.2022 05:22:00 ANS1579E GSKit-Funktion gsk_secure_soc_init fehlgeschlagen mit 403: GSK_ERROR_NO_CERTIFICATE
 

LED888

ADSM.ORG Moderator
Joined
Oct 15, 2002
Messages
882
Reaction score
82
Points
0
Website
http
16.08.2022 12:39:53 ANR0443W Protocol error on session 613556 for node Unknown () - invalid "sessType" field found in "Negotiate" verb (offset 26).
From the message manual regarding ANR0443W.

"The server detects a protocol error on the specified session because an invalid field has been found in a verb sent from the client node."

Suspect an application, other than TSM, is trying to use a TSM reserve port.
No node name or session , that I have encounter, have been due to network port scanning the TSM Server port.

-Network port scan.
-ID the process that is attempting to use/access/probe/scan the port reserved for TSM
-Config the port monitoring/scan application to avoid probe/scan TSM ports


Good Luck,
Sias
 
Last edited:

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: 22 19.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 58.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.5%
  • Other (please comement)

    Votes: 9 8.1%

Forum statistics

Threads
31,829
Messages
134,881
Members
21,791
Latest member
fparrilla75
Top