Recently, we have been reconfiguring/locking down a lot of the TCPIP ports
in use by the TSM servers and clients, attempting to control/route TSM
traffic across a private subnet versus the more heavily used public
However, we have been having some TSM scheduler communications, due to
port blocking issues. I am trying to figure out if/how the TSM server can
be configured to control which of its 2-IP connections it uses to
communicate with the clients.
Here is my configuration:
TSM AIX 126.96.36.199 server. 2-IP connections, 188.8.131.52 (primary/public)
and 192.168.20.44 (private).
The TSM client in question only has 1-IP connection, 184.108.40.206. The
DSM.SYS (AIX) points to the server via DNS name that resolves to
My networking person says the traffic is flowing across the 6.201
connection, not the 20.44 private connection.
How, if possible, can I get the TSM server to use the private 20.44
connection to perform the backups ? Is there some server setting that can
control this ?
We are trying to get another connection to the client, using the private
subnet. Unfortunately, there aren't any available ports in the switch, at
this time. Yes, I know that when I get the other port in the client, I can
use the TCPNODEADDRESS options to control this.