TCP Errors Server Connecting to itself

[CharlesTSM]

Hey all,

We have this strange issue whereby our TSM server looses access to itself.

It has four Teamed NIC's and a host file entry pointing to itself.

Then for hours on occasion we get these errors:

07/06/2015 08:00:36 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).
07/06/2015 08:00:36 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
07/06/2015 08:00:36 ANS1017E Session rejected: TCP/IP connection failure
07/06/2015 08:00:36 ANS8023E Unable to establish session with server.
07/06/2015 08:00:43 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).
07/06/2015 08:00:43 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
07/06/2015 08:00:43 ANS1017E Session rejected: TCP/IP connection failure
07/06/2015 08:00:43 ANS8023E Unable to establish session with server.
07/06/2015 08:00:51 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).
07/06/2015 08:00:51 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
07/06/2015 08:00:51 ANS1017E Session rejected: TCP/IP connection failure
07/06/2015 08:00:51 ANS8023E Unable to establish session with server.
07/06/2015 08:29:31 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).
07/06/2015 08:29:31 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
07/06/2015 08:29:31 ANS1017E Session rejected: TCP/IP connection failure
07/06/2015 08:29:31 ANS8023E Unable to establish session with server.
07/06/2015 08:32:27 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).
07/06/2015 08:32:27 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
07/06/2015 08:32:27 ANS1017E Session rejected: TCP/IP connection failure
07/06/2015 08:32:27 ANS8023E Unable to establish session with server.
07/06/2015 08:54:59 ANS5216E Could not establish a TCP/IP connection with address 'xxxxx:1500'. The TCP/IP error is 'Unknown error' (errno = 10061).

Server name replaced with xxxxx

Even if I load the TSM admin command line during this time I'm unable to log on.

I've tried to look on all the knowledge bases and google this error but they all discuss networking issues with clients connecting to the server but this is the server talking to itself.

Anything I can do to troubleshoot this issue whilst it is happening?

Thanks,

C

 

[marclant]

Actually, it is still the TSM Client attempting to communicate to the TSM Server, in your case it just happens that they are on the same machine. The client has no idea it's on the same machine, it just knows it has to use that IP to connect to it. The TSM Admin Command Line is also a client connecting to a server, so same thing applies as with the TSM Client.

The error "10061" is a Windows error code:

C:\>net helpmsg 10061

No connection could be made because the target machine actively refused it.

So it's something that needs to be addressed at the networking layer, not TSM. However, there is a workaround you can use in TSM. Since both the client and the server are on the same machine, you can change the COMMMETHOD to SHAREDMEM:
http://www-01.ibm.com/support/knowl...m.tshoot.doc/r_pdg_srv_config_shared_mem.html
Enable sharedmem on server first:
http://www-01.ibm.com/support/knowl...m.tshoot.doc/r_pdg_srv_config_shared_mem.html

Then configure client to use sharedmem:
http://www-01.ibm.com/support/knowl...com.ibm.itsm.client.doc/r_opt_commmethod.html

When on the same machine, SHAREDMEM is preferred, it's faster and more robust than TCP.