Re: GIGE NIC
2003-04-30 11:18:22
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
|
|
|