Re: Server IP controls

2004-04-13 13:42:45
Subject: Re: Server IP controls
From: Tom Kauffman <KauffmanT AT NIBCO DOT COM>
Date: Tue, 13 Apr 2004 12:26:17 -0500
Zoltan --

There is no magic involved here. Your client only has one network port, that
is the network that TSM will use. You can play all the aliasing games you
want on the client side; TSM is going to see the connection on the 6.201
port and that is the network that will be used.

Once you get the second network installed you can use TCPNODEADDRESS or just
set the client up to use the dns entry for the TSM server's 20.44 port as
the server address.

I have 4 networks to my tsm server: tsm (public); tsm-pri (private); tsm-bu1
(backup one); and tsm-bu2 (backup two). Some clients use tsm-bu1 as the
server address; some use tsm-bu2; a few use tsm-pri; and a couple access tsm
on the public network. Access on all of the nodes is by way of the dsm.sys


Tom Kauffman

-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:zforray AT VCU DOT EDU]
Sent: Tuesday, April 13, 2004 8:22 AM
Subject: Server IP controls

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 server.  2-IP connections, (primary/public)
and (private).

The TSM client in question only has 1-IP connection,   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.

<Prev in Thread] Current Thread [Next in Thread>