ignoring the TCPCLIENTADDRESS address options (which I don't use), here is
my understanding off how things would work:

Client initiated connections should connect to your TSM server as defined
in dsm.sys (TCPServeraddress option), what IP it uses would be determined
using various methods (you could define it in dsm.sys, or DNS or
/etc/hosts). So after the Server IP is retrieved, the system will now send
out the TSM packets over the network as determined by your route tables
(netstat -r). If you have a default route set to go over the GIGE then your
traffic should go over it, unless there is another route that would be more
specific to the address of the TSM server.

Server initiated connections should follow similiar lines. Server looks up
client IP, packets travel to client over Interface as determined by routing
tables etc etc.

As mentioned, traceroute is your friend. Using the addresses for the
server/client on both machines will tell you what path TCP/IP
communications take, which unless you specify something different in
dsm.sys should be what you take when you back up. Of course, that's just my
opinion...


Jonathan Kaufman

Foot Locker Corporate Services, Inc.





                                               To:      ADSM-L AT VM.MARIST DOT 
EDU
                                               cc:
                        "PINNI,                Subject: Re: GIGE NIC
                        BALANAND
                        (SBCSI)"
                        <bp3965 AT SBC DOT COM
                        >
                        Sent by: "ADSM:
                        Dist Stor
                        Manager"
                        <ADSM-L AT VM DOT MARI
                        ST.EDU>


                        04/30/2003
                        10:46 AM
                        Please respond
                        to "ADSM: Dist
                        Stor Manager"







Use trace route cmd  to determine how the connection takes place to the TSM
Server from the client.You will also see Switch address too!! With no: of
Hops.

This will help in terms of path trace and timming.

Balanand

-----Original Message-----
From: Wholey, Joseph (IDS DM&DS) [mailto:JWholey AT EXCHANGE.ML DOT COM]
Sent: Wednesday, April 30, 2003 10:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: GIGE NIC

Situation:  have a GIGE card in one of my client nodes (SUN 5.8) running
TSM
client v 4,2,1.0 backing put to TSM server v 4,2,2.9.  Running across a
GIGE
network.  This client has multiple NICs, but
only one GIGE NIC.  In the client dsm.sys file, I've set TCPCLIENTADDRESS
to
the IP of the NIC, and TCPCLIENTPORT to 1500.

When TSM server initiates the daily backup, how does it know to connect and
transfer data over the GIGE NIC and not the 10/100 NICS?
How is the path up to the TSM server determined?  Can I be "coming off" the
GIGE network on my way up to the server, hence reducing my thruput?

Any suggestions would be greatly appreciated.

Regards, Joe