If you use the GIGE address of the TSM server in your DSM.OPT file on the
client, then the BACKUP data will go over the GIGE card. Any data FROM the
TSM server TO the client will go out the network adapter on the TSM server
however TCPIP routing takes it. If you have multiple adapters in the TSM
server, the outbound traffic will first go the adapter that is on the same
subnet as the client. If the GIGE and client are not on the same subnet,
then the traffic will go out the default route unless you have a specific
ROUTE in effect. If you want ALL data to go in and out the GIGE card, either
disable the other adapters, or change the default route to be the GIGE
adapter.

I had a client that had in their AIX TSM server  1 10/100 card and 2 GIGE
cards ALL set to the same subnet. Backup inbound data to the TSM server came
in over the GIGE adapter, but since the 10/100 card was the default route,
all outbound traffic, and that included RESTOREs went out the 10/100. They
couldn't figure out why restores too so long.

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Dwight Cook
Sent: Tuesday, March 23, 2004 1:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: GIGE connectivity via TSM


Use a "traceroute" command from your client box to the specific ip address
you want to go into on your tsm server.
Your backups will take the same path.
That simple...

Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 925-8045




                      "Wholey, Joseph
                      (IDS DM&DS)"             To:
ADSM-L AT VM.MARIST DOT EDU
                      <joseph_wholey@ML        cc:
                      .COM>                    Subject:  Re: GIGE
connectivity via TSM
                      Sent by: "ADSM:
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      03/23/2004 10:28
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






OK... now things are getting fuzzy.  This was my initial concern.  Can
anyone confirm exactly what one needs to do to ensure one traverses the
GIGE NIC for both inbound and outbound traffic?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Dwight Cook
Sent: Tuesday, March 23, 2004 10:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: GIGE connectivity via TSM







tcpclientaddress only sets the initial address for the server to come in
on.... (last I remember)
beyond that, standard system/network routing takes over.
I'm still at 4.2 & 5.1 (moving to 5.2 in the next couple of months) but we
currently put route statements on the client nodes to ensure they exit out
their proper interfaces to access the tsm server(s).


Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 925-8045




                      "Wholey, Joseph
                      (IDS DM&DS)"             To:
ADSM-L AT VM.MARIST DOT EDU
                      <joseph_wholey@ML        cc:
                      .COM>                    Subject:  GIGE connectivity
via TSM
                      Sent by: "ADSM:
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      03/23/2004 09:28
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






This should be an easy one for most...  I have a Solaris client running TSM
v5.2.  It will be getting a GIGE card.  What is the best/recommended way to
ensure data is traversing the GIGE card (in both
directions... outbound/inbound) if it is not set up as the default NIC on
the client.  thx.

============================================================================
==



If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.

Click here for important additional terms relating to this e-mail.
     <http://www.ml.com/email_terms/>

============================================================================
==





============================================================================
==


If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.

Click here for important additional terms relating to this e-mail.
     <http://www.ml.com/email_terms/>

============================================================================
==