I don't disagree, but does this gaurantee that the data coming from the server will traverse the GIGE NIC as well?
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, March 23, 2004 11:07 AM To: [EMAIL PROTECTED] Subject: Re: GIGE connectivity via TSM My understanding of TCPCLIENTADDRESS is different. We use it for multi-homed boxes that have a separate NIC that connects to a private, internal, GIGE subnet so that the backups are pushed across it versus the public subnet. To verify this, when I check the details for a TSM node (on the TSM server), the IP address it shows changes to the private subnet, not the public one that was previously being used. Andrew Raibeck......care to confirm this ? Dwight Cook <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/23/2004 10:49 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc 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: [EMAIL PROTECTED] <[EMAIL PROTECTED] 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/> ==============================================================================
<<attachment: ATT58796.gif>>
<<attachment: ATT58797.gif>>
<<attachment: ATT58798.gif>>
