Re: GIGE connectivity via TSM
2004-03-23 11:51:02
FWIW, I found this sentence in another TSM book:
The value of the tcpclientaddress option must be the service IP address.
This is the IP address used for primary traffic to and from the node.
"Wholey, Joseph (IDS DM&DS)" <joseph_wholey AT ML DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/23/2004 11:28 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: GIGE connectivity via TSM
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/>
==============================================================================
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: GIGE connectivity via TSM, (continued)
- Re: GIGE connectivity via TSM, Josh-Daniel Davis
- Re: GIGE connectivity via TSM, French, Michael
- Re: GIGE connectivity via TSM, Richard Sims
- Re: GIGE connectivity via TSM, Dwight Cook
- Re: GIGE connectivity via TSM, Wholey, Joseph (IDS DM&DS)
- Re: GIGE connectivity via TSM, Wholey, Joseph (IDS DM&DS)
- Re: GIGE connectivity via TSM, Wholey, Joseph (IDS DM&DS)
- Re: GIGE connectivity via TSM,
Zoltan Forray/AC/VCU <=
- Re: GIGE connectivity via TSM, David Longo
- Re: GIGE connectivity via TSM, Dwight Cook
- Re: GIGE connectivity via TSM, Wholey, Joseph (IDS DM&DS)
|
|
|