Michael, Yes my client and server are on different networks, as will be the GIGE card relative to other NICs on the client. I didn't want to get into maintaining a routing table, but if that's the only way to ensure communication over the GIGE in both directions, I guess that'll have to do. My next question, is that the only way to ensure bi-directional communication over the GIGE?
thx. -joe- -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of French, Michael Sent: Tuesday, March 23, 2004 10:38 AM To: [EMAIL PROTECTED] Subject: Re: GIGE connectivity via TSM Is your TSM server on a different network from the client? Is the GigE card on a different network then the other interface on the machine? I would assume so, if that is the case, just set a permenant route that points to the TSM server's network and tell it to go out the GigE interface to get there. Man route to see the exact syntax. Once the client connects over that interface, the TSM server should use that IP to call the box (if that's how you have scheduling setup). Michael French -----Original Message----- From: ADSM: Dist Stor Manager on behalf of Wholey, Joseph (IDS DM&DS) Sent: Tue 3/23/2004 9:28 AM To: [EMAIL PROTECTED] Cc: Subject: GIGE connectivity via TSM 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/> ==============================================================================
