We have a server that has been getting the following sporadic
dsmerror.log errors:
12/19/09 14:07:02 ANS9020E Could not establish a session
with a TSM server or client agent.
The TSM return code is -50.
12/19/09 14:07:02 ANS1017E Session
Hi
q) Is there some way to get the BA client to list the IP address
it's trying to use?
It is using tsm4.fenetwork.com. From inside tsm you can't see what ip# it
resolves to, but here are a few other methods:
Ping tsm4.fenetwork.com
Nslookup
Richard,
The rc 50 could be caused by numerous scenarios (TCPPort change, flakey
cables, faulty hardware). You could run a Tracert
IP/HOSTNAME_TSM_SERVER to see where there could be data
loss/connectivity issue between the client and TSM server.
As far as listing the specific TCP address, you
Thanks for the info.
The tsm server has nothing in the actlog during the time frames of the
errors for this node. It DOES
have sessions being started for other nodes. That's why I'm thinking it's
a DNS/network problem.
Per suggestions . . .I'm putting together a little script to do tests every
