Re: AW: GIGE NIC

Distinguish which side initiates the connection:
1. Server "calls" the client to notify it about a schedule. Route from 
server to client is determined based on TCPCLIENTADDRESS. - low traffic, 
only schedule info.
2. Client sends/receives data from server. The connection is initiated 
from client to server and routed based on TCPSERVERADDRESS - real traffic, 
MBs/GBs/TBs.
2a. In version 5.2 there is possibility for server to initiate the data 
connection for security reasons.

Zlatko Krastev
IT Consultant






"Thomas Rupp, Vorarlberger Illwerke AG" <Thomas.Rupp AT ILLWERKE DOT AT>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
30.04.2003 18:40
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        AW: GIGE NIC


Hey Joe (couldn't resist :-) )
If you - as the TSM admin - want to control the path the data takes
you have to define the TCPCLIENTADDRESS. And then you *have to* start
the GUI or CLI on the client.
When client "ABC" connects to the TSM server it tells the server the 
IP-Address
under wich client "ABC" can be reached.
You can omit TCPCLIENTADDRESS when each NIC is in a different subnet so 
the OS knows
how to transmit the data. But if the network guys change anything ...

That's how I unterstand it - but I could be wrong

Greetings from Austria

Thomas Rupp
Vorarlberger Illwerke AG
Mail:   thomas.rupp AT illwerke DOT at
Tel:    +43/5574/601-2583


-----Ursprüngliche Nachricht-----
Von: Ben Bullock [mailto:bbullock AT MICRON DOT COM] 
Gesendet: Mittwoch, 30. April 2003 17:17
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: GIGE NIC


        Typically, it's all determined by you NIC configuration on the 
hosts. TSM hands the packets off to the OS and it determines the correct 
path to send it to the other host.
        If the NICS are masked correctly, and have the correct default 
routes, you can get the host to favor any NIC. You can even go as far as 
configuring host-specific routes to make sure the correct NIC is used, but 
that's typically not necessary.

        There ~is~ an option on the TSM client of "TCPCLIENTADDRESS" that 
you can set to favor a NIC, but I haven't used it as I've always been able 
to get traffic flowing correctly at the OS level.

        The "traceroute" and "netstat" commands can be helpful in seeing 
which NIC is being used. 

Ben

-----Original Message-----
From: Wholey, Joseph (IDS DM&DS) [mailto:JWholey AT EXCHANGE.ML DOT COM]
Sent: Wednesday, April 30, 2003 9: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